b0700tl B

Foxboro™ DCS
Control Core Services v9.6
Release Notes
*B0700TL* *B*
B0700TL, Rev B
May 2022
https://www.se.com
Legal Information
The Schneider Electric brand and any trademarks of Schneider Electric SE and its
subsidiaries referred to in this guide are the property of Schneider Electric SE or its
subsidiaries. All other brands may be trademarks of their respective owners.
This guide and its content are protected under applicable copyright laws and furnished
for informational use only. No part of this guide may be reproduced or transmitted in
any form or by any means (electronic, mechanical, photocopying, recording, or
otherwise), for any purpose, without the prior written permission of Schneider Electric.
Schneider Electric does not grant any right or license for commercial use of the guide
or its content, except for a non-exclusive and personal license to consult it on an "as is"
basis. Schneider Electric products and equipment should be installed, operated,
serviced, and maintained only by qualified personnel.
As standards, specifications, and designs change from time to time, information
contained in this guide may be subject to change without notice.
To the extent permitted by applicable law, no responsibility or liability is assumed by
Schneider Electric and its subsidiaries for any errors or omissions in the informational
content of this material or consequences arising out of or resulting from the use of the
information contained herein.
This document contains standardized industry terms that some customers might find
insensitive or offensive. These terms do not reflect the official policy or position of
Schneider Electric.
Control Core Services v9.6 Release Notes
Table of Contents
Preface ...............................................................................................................9
Revision Information.........................................................................................9
Related Documents..........................................................................................9
Schneider Electric Products Mentioned in this Document ..................................13
Global Customer Support ...............................................................................13
We Welcome Your Comments.........................................................................13
Chapter 1: Getting Started ............................................................................14
Local Edition and Enterprise Edition Control Core Services ...............................14
Hardware Requirements .................................................................................14
Domain Controllers ........................................................................................14
Operating System Image Installation ...............................................................15
Control Core Services v9.6 Support for the Control Software .............................15
Site Upgrades ................................................................................................15
Migrate Files ............................................................................................15
Compound Summary Access (CSA) ..........................................................15
Installation Overview ......................................................................................16
Installing CCS if Detail Displays Have Been Updated or Customized After
the Previous CCS Installation ....................................................................16
Maintain Up-to-Date Version of Adobe® Reader® for Foxboro DCS
Documentation ..............................................................................................17
Foxboro DCS Product Rebranding ..................................................................17
Chapter 2: Media for Control Core Services v9.6 ......................................18
v9.6 Media Kit ................................................................................................18
Additional Required Media for CCS v9.6 ..........................................................18
Additional Software Packages.........................................................................20
Chapter 3: Features of Control Core Services v9.6 Release ...................22
Support for EcoStruxure Foxboro DCS Edge I/O ..............................................22
Chapter 4: v9.6 Compatibility Considerations ............................................23
Site Upgrade Plans ........................................................................................23
ArchestrA and Microsoft Product Support for Control Core Services...................23
Control Software Support for Control Core Services v9.6 or Later ......................24
Interoperability and Compatibility.....................................................................24
AIM*API as a Replacement for FoxAPI.......................................................28
Nodebus to Control Network Interoperability and Compatibility.....................28
Control Core Services Interoperability and Compatibility..............................29
Supported Operations ....................................................................................31
Chapter 5: v9.6 Hardware Requirements ...................................................32
Chapter 6: v9.6 Operational Recommendations .......................................33
Shutting down Workstation/Server When Installing Windows 10 Patches or
Security Updates............................................................................................33
System Configuration .....................................................................................33
Self-Host or Auto-Checkpoint Host Limitations (CP270s or Later
CPs)........................................................................................................33
Software Installation .......................................................................................33
B0700TL, Rev B 3
Resolving Suboptimal Conditions During Software Installation .....................33

Performing a Day 1 Installation Procedure with Address Translation
Station (ATS)............................................................................................34
Creating and Appending to a Reconcile Diskette.........................................34
Installations with Multiple CPU Core Feature ..............................................35
NIC Configuration Settings ........................................................................35
Local User Accounts.................................................................................35
Share Permissions ...................................................................................36
Terminal Services and Remote Desktop Services .......................................36
Connect a Station to an Off-Control Network Domain ..................................37
Windows Workstations ...................................................................................37
Resolution and Color Settings of Multi-Headed Workstation
Displays...................................................................................................37
Screen Savers .........................................................................................38
Security Feature in Windows 10 and Windows Server 2016 .........................38
System Monitor Messages Reporting Unavailable Workstations ..................38
System Monitor Behavior after Power Becomes Unavailable .......................38
IP Address Displayed in the Exceed Icon....................................................38
Foxboro DCS Control Core Services Startup and Security Options ....................39
Foxboro DCS Control Core Services Startup Options ..................................39
Autologon ................................................................................................46
Restricted Desktop ...................................................................................47
Welcome Screen ......................................................................................49
Application Launcher Splash Screen..........................................................51
Control Core Services Log Off and Shut Down .................................................52
Logging Off ..............................................................................................53
Shutting Down/Restarting the Station.........................................................53
Shut Down Configuration ..........................................................................55
Virtual Machines (VMs)...................................................................................55
Re-enabling Functionality Typically Restricted on VMs ................................55
Solaris 10 Stations .........................................................................................56
GNOME Session Manager Segmentation...................................................56
Tools and Utilities ...........................................................................................56
Getpars Utility (CAR #1012329).................................................................56
Displays ........................................................................................................56
Station Displays and Tool/Utilities List Same Number of Unique Points at
Different Values ........................................................................................56
Detail Display Differences on Workstations on The Nodebus and The
Foxboro DCS Control Network ..................................................................57
Application Software.......................................................................................57
IFDC Software .........................................................................................57
Alarm Management Subsystem.......................................................................57
Alarm Counts and Page Counts.................................................................57
Configuring Alarm Management Options for V8.x Systems Using
ADMC .....................................................................................................58
Previously Deleted Alarm Manager Configuration Files ...............................59
Moveability of Full Screen Current Alarm Display (CAD) ..............................59
Message Manager Software......................................................................59
4 B0700TL, Rev B
Running a Single Message Manager..........................................................59

Configuring Default Alarm Manager ...........................................................59
Printing Alarm Priority to the Alarm Printer ..................................................60
Control Configuration Software .......................................................................62
Detected Error Message When Deleting a Block or Compound in
ICCAPI ....................................................................................................62
Inadvisable to Shutdown or Reboot Station While ICC is Open ....................62
Control Databases and Process Control...........................................................62
Re-Alarming Change in FCP270 and ZCP270 CP Images v2.5 and
Later........................................................................................................62
Re-Alarming for Multiple Alarm Priority Types .............................................62
Change Block Modes on DO or AO Blocks .................................................63
Dynamically Reconfiguring a Block Parameter............................................63
PAKOUT Block Limitations ........................................................................64
Using AOUTR Blocks with ECB38R for FBM46/FBM246
Applications .............................................................................................64
Using the OSP 0 Instruction in the LOGIC Block .........................................64
Control Processor (FCP280, FCP270 and ZCP270)..........................................65
Issuing a Reboot Command for a Shadow FCP280 or CP270
Module ....................................................................................................65
Address Stations with Numeric Letterbugs .................................................65
Installing or Replacing FCP280, CP270, and FCM100 Modules in a
Running System with I/A Series Software v8.x or Control Core Services
v9.0 or Later.............................................................................................65
Field Device Controller 280 (FDC280) .............................................................66
FDC280 IOM Image..................................................................................66
Setting Timeout Option for Modbus TCP Client Driver for Interfacing
Tricon and Trident Devices ........................................................................66
Address Translation Station (ATS) ...................................................................67
Communicating Directly to an ATS .............................................................67
Station Support for Address Translation Station ..........................................67
Network Unavailability Detection Logs........................................................68
Intrinsically Safe I/O Subsystem ......................................................................69
Using SRD991 with the Intrinsically Safe I/O Subsystem .............................69
Fieldbus Modules (FBMs) and Field Communication Modules (FCMs) ...............69
Redundant FBM248 Pulse Count...............................................................70
Configure the FBM206 Input Frequency Using the RES04
Parameter................................................................................................70
Main/Tracker FBM222 Role Switches.........................................................70
Signal Conditioning in RIN Block for FFH1 d/p Cell......................................70
EEPROM Updating FBM216s with Software Prior to v2.35F ........................70
Duplicate Channel Numbers for FoxCom Transmitters (ECB18) and
FoxCom Valves (ECB74) ..........................................................................71
Configuring FCMs for Simplex Operation....................................................72
Validating Compact PROFIBUS Configuration File ......................................72
Performing General Downloads on ZCP270 ...............................................73
FBM216 Role Switch ................................................................................73
200 Series FBM Rate of Change Alarms ....................................................73
B0700TL, Rev B 5
Configuring Fail-Safe for Proper Operation of FBM218 ................................73

EEPROM Updating FBM220 and FBM221 .................................................74
Field Device System Integrator (FDSI) Subsystem ......................................74
Display FoxCom Device Information After General Download ......................75
FBM223 PROFIBUS Configurator..............................................................75
Changing FSENAB for ECB200 (PROFIBUS-DP FBM223)..........................75
TIMSTP Parameter of the EVENT Block.....................................................75
Online/Offline States of SPECTRUM I/O Migration Modules under
ZCP270 ...................................................................................................75
Foundation Fieldbus, PROFIBUS-DP, HART, Modbus, DeviceNet, and
FDSI .............................................................................................................76
DeviceNet Baud Rate ...............................................................................76
Peer-to-Peer Connections of Real-Type Block Inputs ........................................76
Data Transfers Between the Nodebus and The Foxboro DCS Control
Networks .......................................................................................................77
Chapter 7: v9.6 User Notes...........................................................................78
Installing Software..........................................................................................78
New User Accounts on Local Edition System Installation .............................78
Dialog Box Shown When Saving Screen Capture with HyperSnap 8 for
the First Time ...........................................................................................78
Foxboro Classic Software Support .............................................................78
Workstations with Windows Operating System .................................................79
Printer Monitor System Message in SMON Indicates Normal
Operation.................................................................................................79
User Cannot Perform Checkpoint Even After Removing Database
Locks ......................................................................................................79
User Access to Shared Folders Between Workstations with Windows 10
or Windows Server 2016 and Workstations with Windows XP or Windows
Server 2003 .............................................................................................79
User Access Shared Folders from an Insecure Network File Device .............80
Potential Detected Startup Condition on Control Core Services
Workstations After a Detected Power Failure ..............................................81
Applications ...................................................................................................83
FoxDraw ..................................................................................................83
Device Monitor...............................................................................................84
Device Monitor Master Active on Isolated Segments of Foxboro DCS
Control Network .......................................................................................84
Control Processors.........................................................................................85
I/O Load (Fieldbus Scan Load) Increase Due to Unavailable or
Disconnected Fieldbus Channel ................................................................85
Removing Married FCP280s From Their Baseplate.....................................85
Chapter 8: Customer Cases Resolved in v9.6 ...........................................87
Appendix A: EEPROM Revision Levels ......................................................91
Image Revision Levels for Control Stations and ATS with Control Core
Services v9.6 .................................................................................................91
100 Series FBM Software and EEPROM Versions ............................................92
200 Series FBM Software and EEPROM Versions ............................................96
6 B0700TL, Rev B
Important Safety Instructions

Read these instructions carefully and look at the equipment to become familiar with it
before trying to install, operate, service, or maintain it. The following safety messages
might appear throughout this manual or on the equipment to warn of potential hazards
or to call attention to information that clarifies or simplifies a procedure.
The addition of this symbol to a “Danger” or “Warning” safety message

indicates that an electrical hazard exists that results in personal injury if
the instructions are not followed.
This safety alert symbol that lets you know about potential personal
injury hazards. Obey all safety messages with this symbol to avoid
possible injury or death.
DANGER
DANGER indicates a hazardous situation which, if not avoided, will result in death
or serious injury.
Failure to follow these instructions will result in death or serious injury.
WARNING
WARNING indicates a hazardous situation that, if not avoided, could result in
death or serious injury.
Failure to follow these instructions can result in death, serious injury, or
equipment damage.
CAUTION
CAUTION indicates a hazardous situation that, if not avoided, could result in
minor or moderate injury.
Failure to follow these instructions can result in injury or equipment damage.
NOTICE
NOTICE is used to address practices not related to physical injury.
Failure to follow these instructions can result in equipment damage.
Please Note
Electrical equipment should only be installed, operated, serviced, and maintained by
qualified personnel. No responsibility is assumed by Schneider Electric for any
consequences arising out of the use of this material.
A qualified person is one who has skills and knowledge related to the construction,
installation, and operation of electrical equipment and has received safety training to
recognize and avoid the hazards involved.
B0700TL, Rev B 7
n k
Bla
e f t
y L
a ll
i on
n t
n t e
geI
P a
h is
T
Preface Control Core Services v9.6 Release Notes
Preface
This document assists you in planning and executing an installation of the
EcoStruxure™ Foxboro™ DCS Control Core Services (“Control Core Services”) v9.6
and also describes their features.
Throughout these release notes, references are made to contacting Global Customer
Support at https://pasupport.schneider-electric.com (registration required). Outside
the U.S.A., contact your local (country) Schneider Electric® representative.
NOTE: Whenever you communicate with GCS about these release notes,
mention the date on the cover and the title of the document. Knowing the date on
the cover reduces confusion caused by changed wording, different section
numbers, or mismatched page numbers in your reference.
NOTE: This user manual contains standardized industry terms that might be
deemed inappropriate for our customers.
Revision Information
This revision of the document includes these changes:
Chapter 1 • Updated Domain Controllers, page 14 to indicate new

PDC and SDC requirements.
• Added CS v7.4 support to Control Core Services v9.6
Support for the Control Software, page 15.
Chapter 3 • Added that IACC cannot configure Edge I/O in Support for
EcoStruxure Foxboro DCS Edge I/O, page 22.
Chapter 6 • Updated Station Support for Address Translation Station,
page 67 to indicate correct Control Core Services
software version.
Chapter 8 • Removed CAR 58321139 from this chapter.
Appendix A • Updated FCP280 image number in Image Revision Levels
for Control Stations and ATS with Control Core Services
v9.6, page 91.
• Updated iom image versions for FBM207, FBM214,
FBM217, FBM219, FBM238, FBM239, FBM240, FBM241,
FBM242, FBM245, FBM247, and FBM248 in 200 Series
FBM Software and EEPROM Versions, page 96.
Related Documents
• Control Core Services v9.6 Software Installation Guide (B0700TK)
• Control Core Services v9.5 Software Installation Guide (B0700TC)
• Control Core Services v9.5 Release Notes (B0700TD)
• Control Core Services v9.4 Software Installation Guide (B0700SX)
• Control Core Services v9.4 Release Notes (B0700SY)
• Control Core Services v9.3 Software Installation Guide (B0700SW)
• Control Core Services v9.3 Release Notes (B0700SV)
• Control Core Services v9.2 Software Installation Guide (B0700SU)
B0700TL, Rev B 9
Control Core Services v9.6 Release Notes Preface
• Control Core Services v9.2 Release Notes (B0700ST)

• Control Core Services v9.1 Software Installation Guide (B0700SS)
• Control Core Services v9.1 Release Notes (B0700SR)
• Control Core Services v9.0 Software Installation Guide (B0700SP)
• Control Core Services v9.0 Release Notes (B0700SQ)
• I/A Series V8.8 Software Installation Guide (B0700SF)
• I/A Series System V8.8 Release Notes (B0700SG)
• I/A Series System V8.7 Release Notes and Installation Procedures (B0700SE)
• I/A Series System V8.6 Release Notes and Installation Procedures (B0700SD)
• V8.5 Software Installation Guide (B0700SB)
• V8.5 Release Notes (B0700SC)
• H92 EcoStruxure™ Foxboro™ DCS Standard Workstation (HP Z420) Windows
10 Enterprise 2016 LTSB User’s Guide (B0700HB)
• H92 Standard Workstation (HP Z440) User’s Guide (B0700HA)
• Hardware and Software Specific Instructions for Model H90 (HP DL380 Gen9)
Windows Server 2016 Operating System (B0700GZ)
• Model V91 Server Virtualization Host (HP DL380 Gen9) for Windows Server 2016
User's Guide (B0700HE)
• Model H90 (HP DL380 Gen10) for Windows Server 2016 User's Guide
(B0700HP)
• Model V91 Virtualization Host Server (HP DL380 Gen10) for Windows Server
2016 User's Guide (B0700HQ)
• Model H92 (HP Z4) Standard Workstation User's Guide (B0700HV)
• Control Core Services Security Implementation Guide (B0700HM)
• McAfee ENS 10.6.1 and ePO 5.10 Update 10 Installation Guide (B0700VT)
• Veritas System Recovery 18 User’s Guide (B0700HS)
• The Foxboro DCS Control Network Architecture Guide (B0700AZ)
• Address Translation Station User’s Guide (B0700BP)
• System Planning and Sizing User’s Guide (B0700AX)
• Virtualization for Windows Server 2016 User's Guide (B0700HD)
• Integrated Control Block Descriptions (B0193AX)
• Software Utilities Guide (B0193JB, Rev. T or later)
• System Definition User’s Guide (B0193WQ)
• System Definition V3.6 Release Notes (B0700TG)
• I/A Series Configuration Component (IACC) User's Guide (B0700FE)
• Peer-to-Peer Analyzer Tool (P2PAnalyzer) User’s Guide (B0700GY)
• I/A Series® Configuration Component (IACC) V2.8.1 Release Notes (B0700SM)
• Field Control Processor 280 (FCP280) User's Guide (B0700FW)
• Field Control Processor 280 (FCP280) Sizing Guidelines and Excel® Workbook
(B0700FY)
• Field Control Processor 270 (FCP270) Sizing Guidelines and Excel Workbook
(B0700AV)
• Z-Module Control Processor 270 (ZCP270) Sizing Guidelines and Excel
Workbook (B0700AW)
• Control Network Interface (CNI) User's Guide (B0700GE)
• Field Device Controller 280 (FDC280) User's Guide (B0700GQ)
• FDC280 Sizing User’s Guide (B0700GS)
10 B0700TL, Rev B
• FDC280 Modbus TCP and RTU /Serial Driver User’s Guide (B0700GT)
• Field Control Processor 280 (FCP280) On-Line Image Update (B0700FX)
• Control Processor 270 (CP270) On-Line Image Update (B0700BY)
• Integrated Control Software Concepts for CP270, FCP280, and FDC280 User’s
Guide (B0700AG)
• System Manager User’s Guide (B0750AP)
• System Manager V2.15 Release Notes (B0750RS)
• Foxboro™ DCS Control Database Deployment User’s Guide (B0750AJ)
• Foxboro DCS Control Software Installation Guide (B0750RA)
• Control Software v7.3 Release Notes (B0750SX)
• FoxView Software User’s Guide (B0700FC)
• FoxDraw Software User’s Guide (B0700FD)
• FoxView and FoxDraw Software V10.6.1 Release Notes (B0700TE)
• FERRET V6.5 Installation and Release Notes (B0860RU)
• Standard and Compact 200 Series Subsystem User's Guide (B0400FA)
• Intelligent Marshalling Fieldbus Modules - FBM247 and FBM248 (B0700GU)
• HART™ Communication Interface Modules User’s Guide (B0400FF)
• 100 Series Fieldbus Module Upgrade Subsystem Overview (B0700BQ)
• Standard 200 Series Subsystem Overview (PSS 41H-2SOV)
• 100 Series Fieldbus Module Upgrade Subsystem Overview (PSS 41H-2W100)
• Standard and Compact 200 Series I/O, Agency Certifications (PSS 41H-
2CERTS)
• Standard 200 Series Power Supply - FPS400-24 (PSS 41H-2FPS400)
• Termination Assembly Adapter Modules for 100 Series Upgrade (PSS 41H-2W4)
• Standard 200 Series Baseplates (PSS 41H-2SBASPLT)
• Standard 200 Series Power Supplies - FPS120-24 and FPS240-24 (PSS 41H-
2FPS)
• 100 Series Conversion Mounting Structures (PSS 41H-2W8)
• FBI200A Fieldbus Isolator/Filter (PSS 41H-2Y17)
• FBI200 Fieldbus Isolator/Filter (PSS 41H-2FBI200)
• FBM201/b/c/d Analog Input (0 to 20 mA, 0 to 100 mV, 0 to 5 V, 0 to 10 V dc)
Interface Modules (PSS 41H-2S201)
• FBM202, Thermocouple/mV Input Interface Module (PSS 41H-2S202)
• FBM203/b/c/d Platinum/Nickel/Copper RTD Input Interface Modules (PSS 41H-
2S203)
• FBM204 – Channel-Isolated, 0 to 20 mA, I/O Interface Module (PSS 41H-2S204)
• FBM205 – Channel-Isolated, Redundant-Ready 0 to 20 mA I/O Interface Module
(PSS 41H-2S205)
• FBM206, Pulse Input and FBM206b, Pulse I/O Interface Modules (PSS 41H-
2S20)
• Compact FBM207b Contact Sense Input Interface Modules (PSS 41H-2C207)
• FBM207/FBM207b/FBM207c – Channel-Isolated, Voltage Monitor/Contact
Sense Input Interface Module (PSS 41H-2S207)
• FBM208/208b, Redundant with Readback, 0 to 20 mA I/O Interface Module (PSS
41H-2S208)
• FBM211 – Differential 0 to 20 mA Input Interface Module (PSS 41H-2S211)
B0700TL, Rev B 11
Control Core Services v9.6 Release Notes Preface
• FBM212 – Differential Thermocouple/mV Input Interface Module (PSS 41H-

2S212)
• Compact FBM214b, HART® Communication Input Interface Module (PSS 41H-
2C214)
• FBM214b, HART® Communication Input Interface Module (PSS 41H-2S214)
• Compact FBM215 HART® Communication Output Interface Module (PSS 41H-
2C215)
• FBM215 – HART® Communication Input Interface Module (PSS 41H-2S215)
• Compact FBM216b, HART® Communication Redundant Input Interface Module
(PSS 41H-2C216)
• FBM216b HART® Communication Redundant Input Interface Module (PSS 41H-
2S216)
• FBM217 – Discrete Input Interface Module (PSS 41H-2S217)
• Compact FBM218 HART® Communication Redundant Output Interface Module
(PSS 41H-2C218)
• FBM218 – HART Communication Redundant Input Interface Module (PSS 41H-
2S218)
• FBM219 Discrete I/O Interface Module (PSS 41H-2S219)
• FBM222, Redundant PROFIBUS-DP Communication Interface Module (PSS
41H-2S222)
• FBM227, 0 to 10 V dc, Contact/dc I/O Interface Module with DPIDA and MDACT
Support (PSS 41H-2S227)
• FBM228 – FOUNDATION fieldbus H1 Redundant Communication Interface
Module (PSS 41H-2S228)
• FBM229, DeviceNet™ Communication Interface Module (PSS 41H-2S229)
• FBM230 – Field Device System Integrator (FDSI) Module, Four Serial Ports,
Single (PSS 41H-2S230)
• FBM231– Field Device System Integrator (FDSI) Module, Four Serial Ports,
Redundant (PSS 41H-2S231)
• FBM232 –Field Device System Integrator (FDSI) Module, 10/100 Mbps Ethernet,
Single (PSS 41H-2S232)
• FBM233 – Field Device System Integrator (FDSI) Module, 10/100 Mbps Ethernet,
Redundant (PSS 41H-2S233)
• FBM237, 0 to 20 mA Output Interface Module (Redundant Ready) (PSS 41H-
2S237)
• FBM238, Discrete 24DI/8DO Interface Module (PSS 41H-2S238)
• FBM239, Digital 16DI/16DO Interface Module (PSS 41H-2S239)
• FBM240 – Channel Isolated, Redundant with Readback, Discrete I/O Interface
• FBM241/FBM241b/FBM241c/FBM241d – Channel Isolated, Discrete I/O
Interface Module (PSS 41H-2S241)
• Compact FBM242, Externally Sourced, Discrete Output Interface Module (PSS
41H-2C242)
• FBM242 – Channel Isolated, Externally Sourced, Discrete Output Interface
• FBM243/243b, FoxCom™ Dual Baud Rate, Intelligent Device Interface Modules
(PSS 41H-2S243)
• FBM244, 0 to 20 mA I/O Interface Module with HART® Support (PSS 41H-2S244)
• FBM245, 0 to 20 mA I/O Interface Module with HART® Support (Redundant)
(PSS 41H-2S245)
12 B0700TL, Rev B
• FBM246/246b, FoxCom™ Redundant Dual Baud Rate, Intelligent Device

• FBM247, Current/Voltage Analog/Digital/Pulse I/O Configurable Channel
• FBM248, Current/Voltage Analog/Digital/Pulse I/O Configurable Module (PSS
41H-2S248)
• Extended Frame Services and Communication DTMs Installation and
Configuration Guide (B0400EF)
• Extended Frame Services 3.0 Release Notes (B0400EH)
The latest revisions of the documents are also available on the Global Customer
Support at https://pasupport.schneider-electric.com (registration required).
Schneider Electric Products Mentioned in this Document

EcoStruxure™ Foxboro™ DCS
EcoStruxure™ Foxboro™ DCS Control Core Services
EcoStruxure™ Foxboro™ DCS Control Network
EcoStruxure™ Foxboro™ DCS Control Software
EcoStruxure™ Foxboro™ DCS Field Device Expert
EcoStruxure™ Foxboro™ DCS Control Editors
EcoStruxure™ Foxboro™ DCS Control HMI
EcoStruxure™ Foxboro™ DCS FoxView/ FoxDraw
EcoStruxure™ Foxboro™ DCS System Manager
EcoStruxure™ Foxboro™ DCS System Definition
Global Customer Support

For support, visit https://pasupport.schneider-electric.com (registration required).
We Welcome Your Comments

To help us improve documentation, we want to know about any corrections,
clarifications, or further information you would find useful. Send us an email at
systemstechpubs@se.com.
This email address is only for documentation feedback. If you have a technical
problem or question, contact Global Customer Support.
B0700TL, Rev B 13
Control Core Services v9.6 Release Notes Chapter 1: Getting Started
Chapter 1: Getting Started

The new features of this release are described in Chapter 3: Features of Control Core
Services v9.6 Release, page 22.
Local Edition and Enterprise Edition Control Core Services

Workstations and servers can be installed with either the Local Edition (previously
known as Standard) or Enterprise Edition (previously known as Security Enhanced)
Control Core Services v9.6.
Within a Foxboro DCS, co-existence of both types of stations is possible. However,
the Local Edition does not have as many security enhancements as the Enterprise
Edition, so a system that includes the Local Edition will not be as secure as a system
that only employs the Enterprise Edition.
For more details on Enterprise Edition Control Core Services, see Control Core
Services Security Implementation Guide (B0700HM).
Hardware Requirements
Control Core Services v9.6 can be only installed on the H90, H92, and V91 platforms
listed in Related Documents, page 9, provided they meet the specifications listed in
Chapter 5: v9.6 Hardware Requirements, page 32 and are configured correctly.
On V91 platforms, Control Core Services v9.6 is installed on the virtual machines
(VMs) maintained by these platforms.
Memory requirements for Control Software workstations and servers, which run the
Foxboro DCS Control Software, differ from those which host the Control Core
Services only. See Control Software Deployment Guide (B0750BA) for memory
requirements for workstations and servers in systems with the Foxboro DCS Control
Software (hereinafter referred to as the Control Software).
For more information, see Chapter 5: v9.6 Hardware Requirements, page 32.
Domain Controllers
In order to install the Enterprise Edition Control Core Services (formerly known as
Security Enhanced, or SE, software) on your Foxboro DCS, you have to have a
dedicated domain controller(s) using Microsoft Active Directory® network services. If
the Primary Domain Controller (PDC) and Secondary Domain Controllers (SDCs) are
to be installed on the Foxboro DCS Control Network, they have to be included in a
system configurator application as servers. The PDC has to be the first station to be
installed with the Enterprise Edition Control Core Services.
If the PDC and SDC are to be installed on a separate network (not on the control
network), they will not be included in the system configuration (Commit media). For
more information, see Control Core Services v9.6 Software Installation Guide
(B0700TK).
NOTE: It is required to have at least one second server acting as an SDC to
provide redundancy.
14 B0700TL, Rev B
Chapter 1: Getting Started Control Core Services v9.6 Release Notes
Operating System Image Installation

When installing on workstations or servers, the operating system images for
Windows® 10 and Windows Server® 2016 stations have to be installed. See Related
Documents, page 9, sections “Hardware and Software Specific Documentation for
Windows 10 Operating System” and “Hardware and Software Specific Documentation
for Windows Server 2016 Standard Operating System”.
The Local Edition and Enterprise Edition Control Core Services can only be installed
on these operating system images.
Control Core Services v9.6 Support for the Control Software

Control Software v7.3 and v7.4 are compatible with Control Core Services v9.6. For
compatibility information, see Foxboro DCS Control Software Installation Guide
(B0750RA).
Site Upgrades
Given the complexity of the systems and different combinations of hardware and
software components that need to interoperate successfully to control a process, you
need to carefully plan your site upgrade. Chapter 3: Features of Control Core Services
v9.6 Release, page 22 provides detailed information on upgrading an existing system.
Migrate Files
To migrate databases and preserve customized files for use on a new system with
Control Core Services v9.6, you can copy them from your existing system. After the
new software is loaded, the databases and customized files can be restored to the
new workstation.
• See Control Core Services v9.6 Software Installation Guide (B0700TK) for
information about backing up specific Control Core Services software and control
databases to a new system with Control Core Services v9.6.
• See Control Software Installation Guide (B0750RA) and the version of the
Control Software Vx.x Release Notes included with your Control Software for
information about migrating specific Control Software and databases to a system
running Control Core Services v9.6 and the Control Software v7.3 or later.
Compound Summary Access (CSA)

CSA has to be run on a workstation with the latest version of the Control Core
Services. This enables it to process the latest control blocks and parameters. CSA
can interoperate with Foxboro DCS workstations with Enterprise Edition Control Core
Services installed and with a workstation with Local Edition Control Core Services
installed. It supports the earlier versions of the I/A Series® software.
If FDC280s or CNIs are configured in this system, CSA has to run on a host with
Control Core Services v9.3 or later.
B0700TL, Rev B 15
Control Core Services v9.6 Release Notes Chapter 1: Getting Started
Installation Overview
Control Core Services v9.6 can be installed as a Day 0 on a supported hardware
platform or via a Release Update or Day 1 on top of Control Core Services v9.4 or
v9.5. See Chapter 5: v9.6 Hardware Requirements, page 32 for a list of supported
hardware.
For upgrading workstations that are installed with I/A Series v8.8 or Control Core
Services v9.0 through v9.3, there are two possible scenarios.
• For a station with I/A Series software v8.8 or Control Core Services which is
installed on a hardware platform which supports Windows 10 or Server 2016: The
new OS platform image is loaded onto the workstation and a Day 0 installation is
performed, upgrading the station to Control Core Services v9.6.
• For a station with I/A Series software v8.8 or Control Core Services which is not
installed on a platform that supports Windows 10 or Server 2016: The new OS
platform image has to be loaded onto a workstation which supports Windows 10
or Windows Server 2016 and a Day 0 installation is performed, upgrading the
station to Control Core Services v9.6.
NOTE: If the existing hardware on which the workstation or server resides
does not support Windows 10 or Windows Server 2016, a new workstation or
server will be needed. See Chapter 5: v9.6 Hardware Requirements, page 32
for supported platforms.
For details on the Control Core Services v9.6 installation, see Control Core Services
v9.6 Software Installation Guide (B0700TK).
To run the Control Software with Control Core Services v9.6, you have to install the
Control Software v7.3 or later on your station. Installation instructions (and pre-
installation procedures such as migration) are provided in Foxboro DCS Control
Software Installation Guide (B0750RA, Rev. Z or later).
The latest revisions of these documents are available on the Global Customer
Support at https://pasupport.schneider-electric.com (registration required).
Installing CCS if Detail Displays Have Been Updated or Customized

After the Previous CCS Installation
When installing Control Core Services, it is possible that not all the detail displays will
be updated. This happens if the display has been modified after the installation of the
previous version.
Examples of when an update might have occurred:
• The file has been opened and saved in FoxDraw, possibly to switch Widescreen
mode.
• The file has been copied over with a different version of the file.
• Bulk edits have been made using dedit to assign access levels selectable fields in
the displays.
Since the installation process relies on the time stamps on the display file on the
target system to determine which files need to be updated, manual updates to a
display file after CCS installation might result in that file not being updated. To view the
time stamps of the detail displays, use File Explorer and the “Date Modified” column.
If detail displays have been modified, prior to starting the CCS installation:
1. Rename the directory D:\opt\fox\dd_1 to D:\opt\fox\dd_1_save.
2. Install CCS.
16 B0700TL, Rev B
Chapter 1: Getting Started Control Core Services v9.6 Release Notes
3. As needed, reapply the edits to the newly installed files.

Detail displays are released in wide screen mode, so there is no need to convert
the displays to wide screen.
Maintain Up-to-Date Version of Adobe® Reader® for Foxboro

DCS Documentation
If you have installed one of the vulnerable versions of Adobe Reader, obtain the latest
security update or full installation program for the Adobe Reader from:
https://get.adobe.com/reader/
For workstations or servers which cannot connect to the internet, download a full
installation program from the website listed above and then copy the program to the
workstation or server and install Adobe Reader on it.
To improve the cybersecurity hardening of your system, these are recommended
optimal practices:
• It is inadvisable to install Adobe Reader on a workstation or server on the
Foxboro DCS Control Network, or the I/A Series control network.
• Keep any installation of Adobe Reader up-to-date with the latest Adobe security
patches.
Foxboro DCS Product Rebranding

For the recent releases of the Foxboro DCS Process Automation System, the
products listed in the table were rebranded.
Table 1 - Foxboro DCS Product Rebranding
Product Name for Foxboro DCS

Process Automation System (and
Product Name - Previous Release Abbreviation)
I/A Series (Intelligent Automation Series) Foxboro DCS Process Automation
system System
Distributed Control System (DCS) (Foxboro DCS)
Foxboro DCS
I/A Series (Intelligent Automation Series) Foxboro DCS Control Core Services
software
(Control Core Services)
Security Enhanced Control Core Services Enterprise Edition Control Core
Services
Standard Control Core Services Local Edition Control Core Services
Foxboro Control Software (FCS)/InFusion Foxboro DCS Control Software
(Control Software)
FCS Configuration Tools/InFusion Foxboro DCS Control Editors
Engineering Environment
(Control Editors)
Foxboro Control Software InTouch® Foxboro DCS Control HMI
Application
(Control HMI)
B0700TL, Rev B 17
Control Core Services v9.6 Release Notes Chapter 2: Media for Control Core Services v9.6
Chapter 2: Media for Control Core Services v9.6

Use this chapter to verify that the identified components have been provided. If you
find or suspect any discrepancies, contact GCS for assistance. Once you verify the
needed documentation and media, proceed with the system installation.
v9.6 Media Kit

Use the checklists below to verify that you have the necessary media to install Control
Core Services v9.6.
NOTE: If you have a pre-v9.6 system, verify that the workstation meets the
Control Core Services v9.6 minimum hardware requirements (see Chapter 5: v9.6
Hardware Requirements, page 32) and that the Control Core Services v9.6 media
kit is available.
You need the media from the Control Core Services v9.6 kit to perform a Control Core
Services v9.6 installation.
Table 2 - Control Core Services v9.6 Day 0 Media Kit (K0204BK-A)
DVD/CD Part
Number Description
K0177DX Foxboro DCS Control Core Services v9.6 Windows 10/Server
2016 Day 0 DVD
K0200MG System Definition (SysDef) v3.6 CD-ROM
K0177DV System Manager v2.15 CD-ROM
K0177BV AIM*AT V3.6.1 CD ROM
K0174KK-A FRS for ADMC Interoperability CD-ROM between Control Core
Services software v9.0 and earlier versions of I/A Series software
K0177DY Foxboro DCS Control Core Services v9.6 Release Notes and
Installation Guide
• Control Core Services v9.6 Software Installation Guide
(B0700TK)
• Control Core Services v9.6 Release Notes (B0700TL)
Additional Required Media for CCS v9.6

This additional media is required or might be required on the system being configured.
The media is provided with all workstation and server platform hardware as well as in
the corresponding upgrade kits and is required to be installed on all platforms prior to
installing Control Core Services v9.6.
18 B0700TL, Rev B
Chapter 2: Media for Control Core Services v9.6 Control Core Services v9.6 Release Notes
Table 3 - Local Security Policy Settings Media
Part Number Description

K0177BY Local Security Policy Settings for Windows Server 2016
Required on all Windows Server 2016 Platform Images
K0177BZ Local Security Policy Settings for Windows 10
Required on all Windows 10 Platform Images
K0177CB Local Security Policy Settings for Centralized Virtual Machine
(CVM) for Windows Server 2016
This media is obtained separately from Control Core Services v9.6. We highly
recommend that you install this software on all platforms prior to installing Control
Core Services v9.6. Information on the security products is available in McAfee ENS
10.5.2 and ePO 5.9.1 Installation Guide (B0700VW).
Table 4 - McAfee Security Products Media

K0204BA McAfee Security Products ENS 10.6.1 with ePO 5.10
Provides the K0177CW media for installation
These media kits might be required if upgrading from Control Core Services v9.3 or
earlier.
Table 5 - Media to Upgrade from CCS v9.3 or Earlier

K0204AG H92 HP® Z440 Workstation Windows 10 Upgrade OS Kit
K0204AH H92 HP® Z420 Workstation Windows 10 Upgrade OS Kit
K0204AJ H90 HP® DL380 Gen9 Workstation Upgrade OS Kit
K0204AW H90 HP® DL380 Gen9 Workstation Upgrade OS Kit with remote
clients
K0204AK V91 HP® DL380 Gen9 Server 2016 VM Host Upgrade OS Kit
K0204AL V91 HP® DL380 Gen9 Server 2016 VM Host - Add two Virtual
Machines to K0204AK
These kits provide for system recovery and restoration. The restore media used with
these kits is included with the platform hardware or with the previously listed upgrade
kits.
Table 6 - System Recovery and Restore Media

K0204BC Veritas System Recovery Desktop Edition 2018 v18.0.2
For H92 HP® Z420 and Z440 Workstations
K0204BD Veritas System Recovery Server Edition v18.0.2
For H90 HP® DL380 Gen9 Server Workstations and Virtual
Machines
B0700TL, Rev B 19
Control Core Services v9.6 Release Notes Chapter 2: Media for Control Core Services v9.6
Table 6 - System Recovery and Restore Media (Continued)

K0204BE Veritas System Recovery 2018 Virtual Edition v18.0.2 Kit
For V91 HP® DL380 Gen9 VM Host Workstations
K0204BF Veritas System Recovery 2018 Workstation Edition v18.0.4
For H92 HP® Z4G4 Workstations
Additional Software Packages

Additional software packages are usually installed from their respective media via
standard installation procedures. They are not included on the Control Core Services
media. See the associated documentation that accompanies the software for exact
installation procedures.
This table provides a list of the additional software packages for v9.6, which are
available in media kits.
Table 7 - Additional Packages for Foxboro DCS Control Core Services v9.6 with Media Kits

K0177CY-A Foxboro Classic Software Support v1.0 CD-ROM for Windows 10/Server 2016
Available in Kit FX- Purchased separately from CCS v9.5 on a per workstation basis. Only required on CCS v9.5
ADD-EXCEED- or later if classic software applications including ICC, Operator Action Journal Configurator,
V152 PLB Monitor, and PLB Editor are also required.
K0177BS FoxView/FoxDraw v10.6.1 CD-ROM for Windows 10/Server 2016
K0177BT FoxDraw Standalone v10.6.1 CD-ROM for Windows 10/Server 2016
- Extended Frame Services (EFS) v3.0 Media Kits - order individually:
• PACTWARE - FDT Frame Application CD-ROM (K0203CB)
• HART Device Type Managers CD-ROM (K0201AW-G) - CodeWrights Third Party
Device DTM Library
• FDT Device Manager Components (EFS) v3.0 CD-ROM (K0201AX-H)
• Pass Thru DTMs for FoxCom and EFS HART (K0203CA)
• Extended Frame Services and Foxboro DCS or I/A Series Communication DTMs
(B0400EF-N)
• Extended Frame Services 2.6 Release Notes (B0400EH-J)
K0177CP Sequence of Events (SOE), includes:
• Sequence of Events (SOE) User's Guide (B0700AK-S or later)
• Sequence of Events (SOE) v1.7 Release Notes (B0700RM)
K0177CE Transient Data Recorder and Analyzer (TDR/TDA), includes:
• Transient Data Recorder and Analyzer (TDR/TDA) User's Guide (B0700AL-M or later)
• Transient Data Recorder and Analyzer (TDR/TDA) v1.6 Release Notes (B0700RL)
K0177BW I/A Series Systems Configuration Component (IACC) v2.8.1 CD-ROM for Windows
K0201AX-H I/A Series Systems FDT Device Manager Components v3.0 for HART® and FoxCom™
Devices
K0203CJ MODBUS Driver for FDSI Modules v2.5 Ethernet (TCP/IP) and Serial Media Kit, Includes:
20 B0700TL, Rev B
Chapter 2: Media for Control Core Services v9.6 Control Core Services v9.6 Release Notes
Table 7 - Additional Packages for Foxboro DCS Control Core Services v9.6 with Media Kits (Continued)

• Modbus TCP/IP and Serial Downloadable Driver For FDSI (K0173WW)
• FDSI Configurator CD-ROM (K0203CC)
K0203CH OPC Client Driver for FDSI Modules v1.5 for DA v2.05 Media Kit - Includes:
• OPC Client Driver for FDSI Modules CD-ROM (K0173WX-F)
• OPC Diagnostic CD-ROM (K0203CE)
• FDSI Configurator v1.5 CD-ROM (K0203CC)
K0177CH Sequential Function Chart Editor (FoxSFC) CD-ROM for Windows 10/Server 2016
The online help for this release of FoxSFC is displayed as “B0193UZ”. However, Sequential
Function Chart/Structured Text Configurator and Display Manager for Sequence Blocks
(B0193UZ) has been superseded by Sequential Function Chart/Structured Text Configurator
and Display Manager for Sequence Blocks (B0700FV), which is available on the Foxboro
DCS Electronic Documentation media (K0174MA) and the Global Customer Support
webpage https://pasupport.schneider-electric.com (registration required).
K0203CF FDSI Ethernet/IP Driver Media Kit - Includes:
• Field Device Systems Integrator Ethernet/IP Driver CD-ROM (K0174CP-D)
• FDSI Configurator V1.5 CD-ROM (K0203CC)
K0203CG Field Device Systems Integrator Triconex™ TSAA Driver v2.5 - Includes:
• Field Device Systems Integrator Triconex TSAA Driver and TSAA Workstation Driver
CD-ROM (K0203CD)
• FDSI Configurator v1.5 CD-ROM (K0203CC)
K0174MD-H FERRET v6.5 for Windows includes the FERRET installation CD-ROM and:
• FERRET v6.5 Installation and Release Notes (B0860RU)
K0177CB Local Security Policy Settings for Centralized Virtual Machine (CVM) for Windows Server
2016
K0204AT CVM Media Kit - includes:
• CVM Configuration Setup Media 2016 (K0177CC-B)
FX-MASQLSTD-K MRC 1.5
Maintenance • Maintenance Response Center Release Notes (B0750SN)
Response Center • Maintenance Response Center Installation Guide (B0750CQ)
Media Kit with SQL
Standard v1.5 • Maintenance Response Center User's Guide (B0750CQ)
FX-MASQLEXP-K
Maintenance
Response Center
Media Kit with SQL
Express v1.5
RH103DG Thin Client as Operator Workstation for Windows 10/Server 2016, Includes:
• Thin Client Software DVD (K0177AX)
K0177AH FDC280 Modbus TCP Client Driver v1.1
K0177CV FDC280 Modbus Serial RTU and ASCII Driver
B0700TL, Rev B 21
Control Core Services v9.6 Release Notes Chapter 3: Features of Control Core Services v9.6 Release
Chapter 3: Features of Control Core Services v9.6

Release
Support for EcoStruxure Foxboro DCS Edge I/O
Foxboro DCS Control Core Services now supports a new software configurable
universal I/O solution called Edge I/O.
The System Monitor is modified to be able to monitor the status of Edge I/O modules
including the Systems Communication Module (SCM) and the Universal I/O Module
(UIOM). Messages related to the new Edge I/O modules are displayed in the System
Monitor log (smon_log) file. For changes made to Foxboro DCS System Manager, see
System Manager User’s Guide (B0750AP).
NOTE: The Edge I/O hardware will be released at a later date, and will be advised
with a separate release note.
Three new Equipment Control Blocks have been added:
• ECB300 — Supports the Universal I/O Module (UIOM). Provides a control
configuration interface for 16 channels of universal input/output (I/O) connections
mounted on a single baseplate.
• ECB301 — Provides a control configuration interface for Universal I/O connected
HART devices. Standard HART variables (PV, SV, TV, FV, and STATUS(1-7)) are
directly visible from the ECB301 with extended variables accessible using DCI
blocks.
• ECB310 — Provides a Foxboro DCS interface between an FCP280 and a
redundant System Communication Module (SCM) pair.
Edge I/O can be configured with Control Software. The Integrated Control
Configurator (ICC) and the I/A Series® Configuration Component (IACC) cannot
configure Edge I/O.
22 B0700TL, Rev B
Chapter 4: v9.6 Compatibility Considerations Control Core Services v9.6 Release Notes
Chapter 4: v9.6 Compatibility Considerations

For more information specific to this release, see Chapter 6: v9.6 Operational
Recommendations, page 33.
Site Upgrade Plans

For information on site upgrade plans for Control Core Services v9.6, see Control
Core Services v9.6 Software Installation Guide (B0700TK).
ArchestrA and Microsoft Product Support for Control Core

Services
These tables provide a list of minimum versions of ArchestrA applications and
Microsoft products which can be used with Control Core Services.
Table 8 - ArchestrA and Microsoft Product Minimum Version Support for Control
Core Services v9.4 or Later on Windows 10 or Windows Server 2016
ArchestrA (WSP 2014 Microsoft Product

Control Core Services R3 SP1) Versions
Control Core Services Application Server Windows 10 LTSB
v9.4-v9.6 (Windows 10 4.2.24100 (Sys Plat Anniversary Edition
or Windows Server 2014 R3 SP1)
2016) Windows Server 2016
InTouch 11.2 P01
.NET Framework 4.6.2
Historian Server 11.6
P02 SQL Server 2014 SP1 (64
bit)
Historian Clients 10.6
P02 SQL Server Express 2014
SP1 (64 bit)
InBatch
• 11.5 (standard Visio Standard 2010 SP1
components) Excel 2016
• 12.1 (IA
Components)
B0700TL, Rev B 23
Control Core Services v9.6 Release Notes Chapter 4: v9.6 Compatibility Considerations
Table 9 - ArchestrA and Microsoft Product Minimum Version Support for Control
Core Services v9.1-v9.3 on Windows 7 or Windows Server 2008
ArchestrA (WSP 2014 Microsoft Product

Control Core Services R3 SP1) Versions
Control Core Services Application Server Windows 7 64 bit SP1
v9.1-v9.3 (Windows 7 or 4.2.24100 (Sys Plat
Windows Server 2008) 2014 R3 SP1) Windows Server 2008 R2
SP1
InTouch 11.2 P01
.NET Framework 4.5.2
Historian Server 11.6
P02 SQL Server 2008 SP3
Historian Clients 10.6 SQL Server Express 2008
P02 Edition SP3
Information Server 2014 Visio Standard 2010 SP1
R3
Excel 2016
InBatch
• 11.5 (standard
components)
• 12.1 (IA
Components)
Control Software Support for Control Core Services v9.6 or

Later
See Foxboro DCS Control Software Installation Guide (B0750RA, Rev. AC or later)
and Control Software v7.3 Release Notes (B0750SX) for planning your integration
with Control Software v7.3.
Interoperability and Compatibility

The table provides an overview of the interoperability and compatibility of various
commonly used Control Core Services or I/A Series software components:
Table 10 - Overview of Control Core Services or I/A Series Software Component Compatibility
I/A Series Software Control Core Services

Software Version v8.5 v8.6 v8.7 v8.8 v9.0 v9.1 v9.2 v9.3 v9.4 v9.5 v9.6
FoxView 10.1 x x x x x x x x x x x
10.2 x x x x x x x x x x x
10.2.1 x x x x x x x x x x x
10.2.2 √ √ x x x x x x x x x
10.2.3 √ √ √ x x x x x x x x
10.2.4 √ √ √ x x x x x x x x
10.3 x x x √ x x x x x x x
10.4.2 √ √ √ √ √ √ √ x x x x
24 B0700TL, Rev B
Table 10 - Overview of Control Core Services or I/A Series Software Component Compatibility (Continued)

10.4.3- √ √ √ √ √ √ √ √ x x x
10.4.4(a)
10.5 x x x √ √ √ √ √ √ x x
10.6 — x x x √ √ √ √ √ √ √ √
10.6.1
IACC 2.1 x x x x x x x x x x x
2.3.1 - 2.4 √ √ √ x √ √ √ √ x x x
2.5 x x x √ √ √ √ √ x x x
2.6-2.6.4(b) √ √ √ √ √ √ √ √ x x x
2.7 — x x x √ √ √ √ √ √ √ √
2.8.1
AIM*AT 3.4 √ √ √ √ x x x x x x x
3.4.1 √ √ √ √ √ x x x x x x
(installed
by
Q-
F1175712)
3.4.2 √ √ √ √ √ √ √ √ x x x
3.4.3 √ √ √ √ √ √ √ √ x x x
3.5 x x x √ √ √ √ √ √ x x
3.6 — x x x √ √ √ √ √ √ √ √
3.6.1
System 2.0 √ x x x x x x x x x x
Manager
2.1 √ √ x x x x x x x x x
2.2 √ √ √ x x x x x x x x
2.3 √ √ √ √ x x x x x x x
2.4 √ √ √ √ √ x x x x x x
2.5 √ √ √ √ √ √ x x x x x
2.6 √ √ √ √ √ √ √ x x x x
2.9(c) √ √ √ √ √ √ √ √ x x x
2.11 x x x √ √ √ √ √ √ √ √
2.12 x x x √ √ √ √ √ √ √ √
2.13 x x x √ √ √ √ √ √ √ √
2.14 x x x √ √ √ √ √ √ √ √
2.15 x x x x x x x x √ √ √
Foxboro 1.0 x x x x x x x x x √ √
Classic
Software
Support
B0700TL, Rev B 25

Foxboro 5.0 x x √ √ √ x x x x x x
DCS
Control 6.0-6.3(d) x x x √ √ √ √ √ x x x
Software x x x x x x
(“the 7.0 √ √ √ √ √
Control 7.1 x x x √ √ √ √ √ √ √ √
Software”)
7.2 x x x x x √ √ √ √ √ √
7.3 x x x x x x x x x x √
Foxboro 3.0 x √ x x x x x x x x x
Control
Software 3.1 x x √ x x x x x x x x
(Earlier x x x x x x x x x
Version of 4.0 √ √
Foxboro
DCS
Control
Software)
InFusion 1.0 x x x x x x x x x x x
(Earlier x x x x x x x x x x x
Version of 1.1
Foxboro 1.2.2 x x x x x x x x x x x
DCS
2.0 √ x x x x x x x x x x
Control
Software) x x x x x x x x x x
2.5 √
Field 2.0 x √ x x x x x x x x x
Device
Expert for 3.0 x x √ √ x x x x x x x
Foundation x x x x x x x x
Fieldbus 3.1.1 √ √ √
4.0 x x x √ √ √ √ √ x x x
4.1 x x x √ √ √ √ √ √ x x
4.2 x x x x x √ √ √ √ √ √
Field 3.0 x x √ √ x x x x x x x
Device
Expert for 3.1.1 x x √ √ √ x x x x x x
HART x x x x x x
4.0 √ √ √ √ √
4.1 x x x √ √ √ √ √ √ x x
4.2 x x x x x √ √ √ √ √ √
Field 2.0 x √ x x x x x x x x x
Device
Expert for 4.0 x x √ √ x x x x x x x
PROFIBUS x x x x x x x x
4.0.2 √ √ √
4.0.3 x x x √ √ √ √ √ x x x
26 B0700TL, Rev B

4.0.4 x x x √ √ √ √ √ x x x
4.1 x x x √ √ √ √ √ √ x x
4.2 x x x x x √ √ √ √ √ √
DeviceNet 1.0.2 x x √ √ √ √ √ √ √ √ √
Configura-
tor 1.3 x x x x x x x x x x √
System 2.8 x x x x x x x x x x x
Definition x x x x x x x x x x x
2.9
2.10 √ x x x x x x x x x x
2.11 √ √ √ x x x x x x x x
3.0 √ √ √ √ x x x x x x x
3.1 √ √ √ √ √ √ x x x x x
3.2 √ √ √ √ √ √ √ √ x x x
3.3 √ √ √ √ √ √ √ √ x x x
3.4 √ √ √ √ √ √ √ √ √ x x
3.5 √ √ √ √ √ √ √ √ √ √ √
3.6 √ √ √ √ √ √ √ √ √ √ √
FoxSFC 2.0 √ √ √ x x x x x x x x
2.1 x x x √ √ √ √ √ √ √ √
2.2 x x x √ √ √ √ √ √ √ √
IFDC 3.1 x Ö x x x x x x x x x
3.1.1 x x √ √ √ √ √ √ √ √ √
3.2 - 3.2.2 x √ √ √ √ √ √ √ √ √ √
EFS 2.2 x √ x x x x x x x x x
2.3 x x √ x x x x x x x x
2.4 x x √ √ √ √ √ √ x x x
3.0 x x x √ √ √ √ √ √ √ √
SOE/TDR 1.5.2-1.5.4 √ √ √ √ √ √ √ √ x x x
(e)
1.5.6(f) √ √ √ √ √ √ √ √ x x x
1.6(g) √ √ √ √ √ √ √ √ x x x
1.7 √ √ √ √ √ √ √ √ √ √ √
FDSI 1.6 x x x √ √ √ √ √ √ √ √
Configura-
tor
B0700TL, Rev B 27

TSAA SOE 2.3 x x x √ √ √ √ √ √ √ √
Worksta-
tion Driver 2.4 x x x x x x x x √ √ √
NOTE:
• Although I/A Series software v8.5 needs a version upgrade of FoxView™ software, it is not necessary to
convert standard definition FoxView .fdf files (for 4:3 aspect ratio monitors). You do need to update these .
fdf files for widescreen (16:9 aspect ratio) monitors as described in FoxDraw™ Software v10.4 (B0700FD).
FoxView v10.2.3 is the minimum version for I/A Series software v8.4.4.
• For System Manager Quick Fixes and other installation notes, see System Manager (B0750AP) and
System Manager Vx.x Release Notes (B0750RS) shipped with your Foxboro DCS.
(a) FoxView v10.4.4 is the minimum needed for monitoring FDC280s on Control Core Services v9.3 and earlier.
(b) Interoperable compatibility with FoxView/FoxDraw™ v10.3 and later only.
(c)System Manager v2.9 is the minimum needed version to monitor FBM248s.
(d) Control Software v6.0/6.0.1/6.0.2/6.0.3 needs QF1257756. This Quick Fix has to also be installed on every
workstation/server which runs the Foxboro DCS Control HMI. See the documentation included with this Quick Fix
for instructions on how to install it.
Control Software v6.0.4 and later include this QuickFix.
(e) SOE/TDR v1.5.2 is the minimum needed version to run FBM247s.
(f) SOE/TDR v1.5.6 is the minimum needed version to run FBM219s.
(g) SOE/TDR v1.6 is the minimum needed version to run FBM248s.
AIM*API as a Replacement for FoxAPI

As of I/A Series software v8.8, the ADDE7 package (FoxAPI) has been removed.
FoxAPI has been replaced with AIM*API, which need not be configured before it is
installed. AIM*API is included with the AIM*Historian component of AIM*AT. See the
AIM*AT Suite Installation Guide (B0193YM) for installation instructions.
Nodebus to Control Network Interoperability and Compatibility

In general, interoperability and compatibility of base software and application software
between Local Edition Control Core Services v9.6 and previous I/A Series software
releases have not changed except where noted in this document.
For information and general Foxboro DCS Control Network interoperability and
coexistence guidelines, see V8.2 Release Notes and Installation Procedures
(B0700RN) or V8.3 Software for the Solaris Operating System Release Notes and
Installation Procedures (B0700RR). These documents discuss these general Control/
Nodebus network interoperability guidelines:
• Control database interoperability
• Display interoperability
• Network Fault Detection (NFD)
• Compound Summary Access (CSA)
• System Management and System Monitor
28 B0700TL, Rev B
• Device Monitor
• Timekeeping
• Alarm processing
• Historian
• IP communications
• AIM*API software compatibility
Control Core Services Interoperability and Compatibility

The applications below are currently being validated to run on systems with Control
Core Service v9.6 (Local Edition or Enterprise Edition using default domain policies).
Contact Global Customer Support at https://pasupport.schneider-electric.com
(registration required) to discuss the availability of these applications.
• FoxCTS software v7.02.00
• Application Object Services (AOS) software v5.01.04
• FoxPage and Event Driven Scripts software v2.02.00
• FoxBridge software v8.02.01
• INI70 software v5.01.04
• Alarm Shelving Tool software v4.00.00
• OPC A&E Client software v3.01.00
• Foxboro DCS and I/A Series Tools Suite software v2.01.00
Active Directory Domain Compatibility

A Domain Controller that has been migrated (through multiple steps) from earlier
versions of I/A Series or CCS (back to I/A Series v8.5) to CCS v9.6 will be able to
govern clients running the older versions of the clients as well as CCS v9.6. This is
because the migration procedures preserve Organizational Units (OUs) and Group
Policy Objects (GPOs) used by prior versions of the Foxboro DCS software. However,
a client with CCS v9.6 must be part of an Active Directory domain with a CCS v9.6
domain controller. The CCS v9.6 domain controller must be installed prior to installing
the clients.
Day 0 Client installation of CCS v9.4 or earlier versions will still not be supported the
moment the PDC is at CCS v9.5 or v9.6. If you do require such a support as an
exception, there is a procedure to do this. For more information, see Control Core
Services v9.6 Software Installation Guide (B0700TK)
Limitations to Interoperability and Compatibility with ADMC

These limitations apply:
• ADMC display configuration files cannot be distributed from workstations or
servers with Local Edition Control Core Services to workstations or servers with
Enterprise Edition Control Core Services v9.6.
• ADMC display configuration files cannot be distributed from workstations or
servers with Security Enhanced I/A Series software v8.5-v8.7 to workstations or
servers with Enterprise Edition Control Core Services v9.4 or later unless the
ADMC compatibility utility is installed on the stations with Security Enhanced I/A
Series software v8.5-v8.7.
NOTE: Security Enhanced I/A Series software v8.8, Security Enhanced
Control Core Services v9.0-v9.3, and Enterprise Edition Control Core
Services v9.4 and later are compatible with respect to ADMC operations.
B0700TL, Rev B 29
Compatibility of Other Software in the Control Core Services

These applications have not been validated to run on systems with I/A Series software
v8.8 or Control Core Services v9.0-9.6. However, they have been validated to run on I/
A Series software v8.6 and v8.7 systems with the security enhancements using
default domain group policies installed.
Table 11 - Compatibility of Other Software in the Control Core Services

FoxCTS v4.0-v5.0.1 x x x x x x x x x x x
software x x x x x x x
v6.0.0 √ √ √ √(a)
v6.0.1 √ √ √ √ √ √ √ √ √ √ √
Application v4.0-v5.0 √ √ √ x x x x x x x x
Object
Services v5.0.1 √ √ √ √ √ √ √ √ √ √ √
(AOS)
software
FoxPage and v2.0-v2.0.1 √ √ √ x x x x x x x x
Event Driven
Scripts v2.0.2 √ √ √ √ √ √ √ √ √ √ √
software
FoxBridge v5.02-v6.0.1 √ √ √ x x x x x x x x
software
v7.00.00- √ √ √ √ √ √ √ √ √ √ √
v7.00.03
INI70 software v4.00- √ √ √ x x x x x x x x
v5.01.00
v5.01.02 √ √ √ √ √ √ √ √ √ √ √
Alarm Shelving v1.0-v2.01 √ √ √ x x x x x x x x
Tool software
v3.1 √ √ √ √ √ √ √ √ √ √ √
Isolation All versions √ √ √ √ √ √ √ √ √ √ √
Station
software
(a) For I/A Series software v8.8, only the Security Enhanced version is supported.
Contact the Global Customer Support at https://pasupport.schneider-electric.com

(registration required) to discuss the availability of these applications.
Boot Hosting Compatibility for CP Stations

These versions of I/A Series and Control Core Services software support the boot
hosting of the listed CP modules regardless of whether or not the workstation is a
member of an Active Directory domain or is on the workgroup.
• FDC280 – Control Core Services v9.3 and later
FDC280 Image 0901003000 supporting one Ethernet and four Serial port
connections beginning with CCS v9.5 or supported on CCS v9.3 and v9.4 with
MP47481162
30 B0700TL, Rev B
• CNI – Control Core Services v9.3 and later (data sharing and alarm messages)
CNI 1.2 supporting 100 sink IPC connections beginning with CCS v9.5 or
supported on CCS v9.3 and v9.4 with MP49924276
• FCP280 – Control Core Services v9.0 and later
• FCP270 – I/A Series v8.0b and later, Control Core Services v9.0 and later
• ZCP270 – I/A Series v8.0b and later, Control Core Services v9.0 and later
• ATS – I/A Series v8.1 and later, Control Core Services v9.0 and later
• Nodebus CPs– I/A Series v8.1 and later, Control Core Services v9.0 and later
Supported Operations
Unless specifically mentioned in this document, the same operations that were
supported in Windows I/A Series software v8.2-v8.8 and Control Core Services v9.0-
v9.3 for the Windows operating system are also supported in v9.4–v9.6. The
operations that could be performed from Nodebus to the Foxboro DCS Control
Network and vice versa, or Nodebus to Nodebus, via control network backbone, are
the same. See V8.2 Release Notes and Installation Procedures (B0700RN) or V8.3
Software for the Solaris Operating System Release Notes and Installation Procedures
(B0700RR). See the table “Supported Software and Operations” in B0700RN/
B0700RR.
B0700RN/B0700RR discusses these supported software and operations:
• Supported API functions in every direction
• Supported operations from any source to any destination
• Supported operations from the control network to Nodebus
• Supported operations from Nodebus to Nodebus
B0700TL, Rev B 31
Control Core Services v9.6 Release Notes Chapter 5: v9.6 Hardware Requirements
Chapter 5: v9.6 Hardware Requirements

Control Core Services v9.6 runs on these currently offered platforms and any later
versions of these platforms which are released.
Table 12 - Platforms Supporting Control Core Services v9.6
Station Type Platform with Multicore CPU Cores Enabled

Workstation H92 HP Z420 Workstation (Model H92, Style Style G/A to Style
H/A)
H92 HP Z440 Workstation (Model H92, Style J/A or newer style)
H92 HP Z4G4 Workstation (Model H92, Style S/A or newer style)
Server H90 HP DL380 Gen9 Server(a) (Model H90, Style G/A or newer
style)
H90 HP DL380 Gen10 Server (Model H90, Style M/A or newer
style)
Virtual Machine V90 HP DL380 VM Host
Host
NOTE: The V90 HP DL380 VM Host can be upgraded to a
V91 HP DL380 Gen9 Server 2016 VM Host. Its hardware can
run Windows Server 2016 but only after it has been upgraded
to become a V91 server.
V91 HP DL380 Gen9 Server 2016 VM Host (Model V91, Style A/
A or newer style)
V91 HP DL380 Gen10 Server 2016 VM Host (Model V91, Style
E/ A or newer style)
(a) BIOS must be updated to version 2.22 or later before upgrading the OS. Please
download the latest qualified BIOS update from the GCS site: (https://pasupport.
schneider-electric.com/content/Security/mspatch/mspatch.asp).
NOTE: This link is only accessible to registered users. First time users can register
at: https://pasupport.schneider-electric.com (registration required).
Allow three business days for validation of the application.
Additional hardware requirements are provided in the Hardware and Software

Specific Documentation listed in Related Documents, page 9 and these PSSes:
• Model H92 Workstation for Windows 10 Operating System (PSS 31H-4H92-10)
• Model H90 for Windows Server 2016 Operating System (PSS 41H-4H90)
• Virtualization Server Host Hardware Model V91 (PSS 41H-4V91)
32 B0700TL, Rev B
Chapter 6: v9.6 Operational Recommendations Control Core Services v9.6 Release Notes
Chapter 6: v9.6 Operational Recommendations

Shutting down Workstation/Server When Installing Windows
10 Patches or Security Updates
When shutting down a workstation or server before installing Windows 10 patches or
security updates:
1. Turn off Control Core Services using the Control Panel application and reboot the
workstation or server.
2. Turn on Control Core Services using the Control Panel application and apply the
Microsoft updates.
3. The update might require a reboot.
a. If the update requires a reboot then the reboot will occur automatically and
the workstation/server will load with Control Core Services running.
b. If the update does not require a reboot, it is recommended that you initiate a
reboot anyway. The workstation or server loads with Control Core Services
running.
System Configuration
Self-Host or Auto-Checkpoint Host Limitations (CP270s or Later
CPs)
When determining how many CP270s (FCP270s or ZCP270s) or FCP280s a boot
host can support, it is recommended that you host up to eight CP270s or FCP280s by
a single boot host when the CPs are configured for self-hosting and auto
checkpointing when auto-checkpoint is configured for two hours.
These loading requirements are based partially on CP idle time and CP database size
with a resulting total time from checkpoint start to “installed into flash memory”
message of 15 minutes per CP270/FCP280 and an auto-checkpoint rate of two hours
(15 minutes x 8 = 2 hours).
You can use an equivalent number of FCP280s or FDC280s as well.
Software Installation
Resolving Suboptimal Conditions During Software Installation
The Log Viewer opens automatically at the end of the installation. Before closing the
log viewer (which causes the installation to exit), record and review any detected
errors and other similar system messages in the log. Make certain that you address
every detected error and other similar system messages appropriately before
continuing with system setup.
The log viewer can be opened at any time after installation. Click the Start button, and
select Foxboro DCS Control Core Services > Log Viewer.
B0700TL, Rev B 33
Control Core Services v9.6 Release Notes Chapter 6: v9.6 Operational Recommendations
For detected errors or other similar system messages, contact the Global Customer
Support for assistance. See the contact information on Related Documents, page 9.
For installations that make changes to Active Directory domain structure or policies
(GPOs), log files are generated and placed in the C:\Windows\Temp folder locally
on the domain controller workstation.
Performing a Day 1 Installation Procedure with Address Translation

Station (ATS)
NOTICE
POTENTIAL DATA LOSS
When replacing a LAN Interface (LI) in the system with an ATS, the configuration of
each ATS must be updated to reflect the new network topology. Failure to do so can
cause communications to become unavailable between nodes as ATSs route
packets to the wrong destinations. This might cause a potential data loss. To
prevent this from happening, change the package install status of the ATS package
(OS1A70) in System Definition to "PCHANG", create a new set of committed
configuration install files (Commit Disk) within System Manager, and perform a Day
1 operation with the new Commit Disk on all of the workstations in the system.
Failure to follow these instructions can result in data loss.
This has to be performed in System Definition prior to generating new Commit media
for the installation. The general procedure for an installation with Commit media
includes:
• Installing Control Core Services Day 0 installation media.
• Creating reconcile media using your preferred system configurator.
• Updating System Definition configuration with reconcile media using your
preferred system configurator.
• Making custom changes to software install status (such as the above procedure)
using your preferred system configurator.
• Creating Commit media using your preferred system configurator.
• Installing Control Core Services Day 1 installation media.
The full procedure is provided in Control Core Services v9.6 Software Installation
Guide (B0700TK).
Creating and Appending to a Reconcile Diskette

A suboptimal condition occurs if you create a Reconcile diskette on a workstation
running a UNIX-based operating system. After creating the Reconcile diskette on the
UNIX-based workstation, you can successfully append the remaining UNIX platforms
and only the first Windows-based platform to the diskette. Appending subsequent
Windows platforms to the Reconcile diskette will not succeed, citing an incorrect
media type.
If you want to create a Reconcile diskette for a Day 1 installation:
1. Create the diskette on a workstation running the Windows operating system.
2. Append the remaining Windows-based platforms.
3. Append the UNIX platforms.
34 B0700TL, Rev B
Installations with Multiple CPU Core Feature

The multiple CPU core feature is auto-enabled on stations with Control Core Services
starting with these platform versions:
• For Windows Server 2016, DL380 Gen9 server and later
• For Windows 10, Z440 workstation and later
See the Hardware and Software Specific Instructions document included with your
workstation or server for details about the multiple CPU core feature as used with your
specific station. Be advised that Control Core Services v9.6 is intended to be run on
stations with the multiple CPU core feature turned on.
NOTE: Z420 workstations shipped with Windows 10 by Schneider Electric are
configured with settings which enabled multiple CPU cores. However, Z420
workstations shipped previously with Windows 7 had not already been configured
to use the multiple CPU core feature. These previously shipped workstations
require configuration changes prior to use. The instructions for making these
configuration changes can be found in Hardware and Software Specific
Instructions for Model H92 (HP Z420) Windows 10 Professional Operating System
(B0700HB).
NIC Configuration Settings

The settings of the network interface cards that connect to the Foxboro DCS Control
Network have to be configured such that Flow Control is disabled and Speed &
Duplex is 100 Mb full-duplex. Improperly configured NIC drivers will result in poor
network-based performance and/or unavailability to finish some operations such as
ePO distribution of software and policies, Foxboro Control Software client or server
activities, etc.
NOTICE
POTENTIAL DATA LOSS
Perform this procedure for 100Mbps fiber optic cards only. For copper NICs and for
Gigabit Fiber optic NICs, you must NOT perform this procedure.
Failure to follow these instructions can result in data loss.
NOTE: We recommend that you do not attempt to upgrade NIC driver versions
after installation of Control Core Services as this can result in detected errors.
Local User Accounts

During a Local Edition system installation, one new user account is created which is
the default user account for executing Control Core Services software. It is possible,
at installation time, to set this user account for auto-logon. There is also an existing
account (Account1) which will remain on the workstation after the installation is
completed. During installation, the password must be set for Account1. Beginning
with CCS v9.5, Account1 can no longer be used to operate Local Edition
workstations. Users should always log in with the Local Engineering User Account
(created at install time) to operate a Local Edition workstation.
During an Enterprise Edition domain client installation, the Account1 password must
be set. No other local accounts are created. In order to operate the Enterprise Edition
domain client, log in with one of the domain users created on the Foxboro DCS
Control Core Services domain controller workstation.
Always follow these guidelines regarding user accounts on the Foxboro DCS.
B0700TL, Rev B 35
• Always set the Account1 passwords differently on the Local Edition workstations
and the Enterprise Edition domain client workstations.
• Always set the Account1 password and the Local Engineering User Account
password differently on each Local Edition workstation.
• Always set the Local Engineering User Account user name and password to the
same value on all Local Edition workstations to maintain compatibility between
Local Edition stations.
For more information on setting local account user names and passwords, see
Foxboro DCS Control Core Services v9.6 Installation Guide (B0700TK).
Share Permissions
Beginning with Foxboro DCS Control Core Services v9.5, the permissions on the IA
share have changed. The new permissions on the IA share are:
• On Local Edition workstations, the IA share provides Read and Write access only
to the Local Edition Engineering User Account.
• On Enterprise Edition domain client workstations, the IA share provides Read
and Write access only to members of the standard Foxboro user groups in the
domain such as “IA Plant Admins”, “IA Plant Engineers”, “IA Plant Operators”,
and “IA Plant View Only”.
Terminal Services and Remote Desktop Services

In accordance with good security practice, by default the “Remote Desktop Services”
service is disabled on workstations (running Windows 10) and domain controller
servers (running Windows Server 2016). If you need remote access to these stations
and are willing to accept any resulting security concern, you would need to turn on
these services.
Be aware if you add the Remote Desktop Services role to a server post-installation,
the addition of that role results in a registry entry being made:
Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
\Terminal Server\TSAppSrv\TSMSI
Value: Enable (DWORD=1)
This registry entry is related to a feature of Remote Desktop Services on the Windows
Server 2016 operating system. This feature can interfere with Control Core Services
installation. After adding the Remote Desktop Services Session Host service, set the
value of this key to zero (0).
Also note these rules:
• The Remote Desktop Services role is removed during installation on the domain
controllers.
• The Remote Desktop Services role is not removed on domain clients or servers
with Local Edition Control Core Services.
• To enable on stations that have the Remote Desktop Services role, turn on the
service “Remote Desktop Services”.
• For workstations without the Remote Desktop Services role, the role has to be
enabled first through the Server Manager tool.
36 B0700TL, Rev B
Turning On Terminal and Remote Desktop Services

1. Log in using a user account with Administrative privileges.
2. Start the Control Panel from the Start menu, click Administrative Tools, and
then click Services.
3. On stations with Windows Server 2016:
a. Double-click the Remote Desktop Services service and change its Startup
type from Disabled to Manual (or Automatic if you want it started at every
boot).
b. Click OK.
c. Right-click the service and select Start from the menu.
4. On stations with Windows 10:
a. Double-click the Remote Desktop Services service and change its Startup
type from Disabled to Manual (or Automatic if you want it started at every
boot).
b. Click OK.
c. Right-click the service and select Start from the menu.
Connect a Station to an Off-Control Network Domain

When connecting to an Off-Control Network domain, the installation software is
unable to determine the remote system time. As a result, a system message is
generated. This does not mean that the local system time did not match the remote
system time, but it is vital to check the time and make certain that it matches before
proceeding. Make certain that the time zones and dates are taken into account when
comparing time in a system. Also be advised that when changing time zones on
Windows systems, it is possible for the AM/PM setting in the time to change.
Windows Workstations
Resolution and Color Settings of Multi-Headed Workstation
Displays
When configuring a multi-headed workstation, configure the secondary screen’s
resolution and color quality settings less than or equal to the primary screen’s
resolution and color quality settings. These settings are configurable in the Settings
tab of the Display Properties window.
Configuring the primary screen with a lower resolution or a lower color quality setting
than the secondary screen causes this detected error message to appear on bootup
of the workstation:
Your Xconfig Screen Definition settings are incompatible with your current
Display settings.
For example, the message appears if:
• The primary screen is set to “Medium (16 bit)” and the secondary screen is set to
“Highest (32 bit)”.
• The primary screen is set to “1024 by 768 pixels” and the secondary screen is set
to “1280 by 1024 pixels”.
Select 32 bit for each monitor.
B0700TL, Rev B 37
Screen Savers
As a general rule, it is not advisable to run screen savers on your Foxboro stations.
However, in the Enterprise Edition Control Core Services, you can enable the screen
saver policy settings if you want the logged on sessions to automatically lock when
there is no activity for a specified period of time. The Control Core Services Security
Implementation Guide (B0700HM) document has information related to these policy
settings (search for “screen saver” in that document).
Security Feature in Windows 10 and Windows Server 2016

Due to a security feature in Windows 10 and Windows Server 2016, files created by
one user might not be accessible by another user in normal (un-elevated) operations.
For example, workfiles created by a SaveAll script (which runs every night and is
scheduled via the AT command) are not accessible by the Integrated Control
Configurator (ICC). This results in a detected error reading File I/O (13).
In this example, since the script is executed under SYSTEM account, the workfile (if
created) is owned by the SYSTEM account. ICC is executed under an un-elevated
(non-administrative) user account, so ICC does not access the workfile. The fix to this
is to schedule the script via the Task Scheduler and run it under the same user
account. Visit this URL for more information and suggestions:
http://windows.microsoft.com/en-US/windows7/schedule-a-task.
The default settings in a Day 0 Control Core Services installation prevent this from
happening. However, users are allowed to have their own security policies and
account configurations where this concern might arise if permission settings are not
correctly configured.
System Monitor Messages Reporting Unavailable Workstations

On a heavily loaded system, System Monitor messages are issued indicating that
UNIX workstations on the Nodebus alternate between being available and
unavailable. This occurs as a result of performance limitations of older UNIX
workstations.
System Monitor Behavior after Power Becomes Unavailable

After power becomes unavailable, some of the System Monitors on Nodebus
workstations might not restart. The message System Monitor (LBUG) Premature
Exit --- Reason (17) appears on the system alarm printer. If the System Monitor does
not start, reboot the workstation.
IP Address Displayed in the Exceed Icon

The new version of Exceed software (v15) that is installed with Control Core Services
v9.5 or later displays an IP address in the Exceed icon in the taskbar . If the NIC
(network) connections are to the Foxboro DCS Control Network, then this IP address
corresponds to the address of that station on the control network. However, if there
are non-control network NIC connections that have IP addresses lower than the
control network NIC IP address, Exceed displays the lower address. In such cases,
Exceed continues to operate properly, but the IP address that is displayed is not the
control network address.
38 B0700TL, Rev B
Foxboro DCS Control Core Services Startup and Security

Options
Users with sufficient privileges can access and modify the Control Core Services start-
up and security options.
Foxboro DCS Control Core Services Startup Options

The Control Core Services Startup Options control panel applet allows users with
sufficient privileges to configure whether to start the Control Core Services when the
station is booted.
1. Do one of these:
• Click the Start button, and select Control Panel > Foxboro DCS Startup
Options.
• From FoxView software, click SftMnt on the top menu bar, and select
Startup Options. (Change to the Software Engineer’s environment if the
SftMnt menu is not available.)
NOTE: Security settings might disallow access to the Control Panel
applets. Enterprise Edition Control Core Services use Group Policy
Settings to restrict access. See Windows 10 and Server 2016
Workstations Security User’s Guide (B0700HM).
2. A User Account Control (UAC) prompt appears.
A dialog box similar to the version shown in this image is displayed for users with
administrative rights (such as the Local Engineering Fox user account or users in
the IA Plant Admins group). For this dialog box, click Yes.
A dialog box similar to the version shown in this image is displayed for users
without administrative rights (such as the ia user account or users in the IA Plant
Operators group). For this dialog box, enter an administrator user name and
password and then click Yes.
B0700TL, Rev B 39
40 B0700TL, Rev B
3. The Control Core Services Startup Options dialog box opens. This image
shows the dialog box with Enterprise Edition security.
B0700TL, Rev B 41
This image shows the dialog box with Local Edition security.
4. Select the appropriate option:

• Control Core Services On
• Autologon - enables Control Core Services on startup and automatically
logon to a specified account.
• Manual logon - enables Control Core Services on startup.
• Autologon, restricted desktop access - enables Control Core Services on
startup and automatically logon to a restricted environment, as described in
Restricted Desktop, page 47. This option is not present on Enterprise Edition
Control Core Services stations.
• Autologon, restricted desktop and shutdown access - enables the
Control Core Services on startup and automatically logon to a highly
restricted environment, as described in Restricted Desktop, page 47. This
option is not present on Enterprise Edition Control Core Services stations.
• Control Core Services Off
• Autologon - disables the Control Core Services from running on startup (for
example, to install additional software), disables access to the Foxboro DCS
Control Network and automatically logon to a specified account.
• Autologon with Mesh Networking - disables the Control Core Services
from running on startup (for example, to install additional software) but
retains access to the Foxboro DCS Control Network and automatically logon
to a specified account.
• Manual logon - disables the Control Core Services from running on startup
(for example, to install additional software), disables access to the Foxboro
DCS Control Network.
42 B0700TL, Rev B
• Manual logon with Mesh networking - disables the Control Core Services
from running on startup, (for example, to install additional software) but
retains access to the Foxboro DCS Control Network.
NOTE:
• If the option Autologon, restricted desktop and shutdown access is
selected, the access to Shutdown and Restart is removed for all users
signing into the workstation/server. In order to restore access to
Shutdown and Restart, the Startup Options must be changed back to a
setting which allows Shutdown and Restart. Once changed back,
Shutdown and Restart will be available through the Ctrl-Alt-Del Welcome
Screen. In order to get back full access to the desktop and start menu,
you have to sign out and then sign back into the workstation/server.
• Before selecting an Autologon option on Enterprise Edition Control Core
Services, you have to be logged on to the domain, and the computer has
to be a secure domain client.
5. Click OK.
6. If an Autologon option was selected, the Autologon Configurator is called. For
more information, see Autologon, page 46.
The restricted desktop options take effect on next logon and are described in
detail on Restricted Desktop, page 47. The other options take effect on station’s
reboot.
The Autologon options are not available on a Domain Controller. When the
control panel applet is opened on a Primary or Secondary Domain Controller,
these options are disabled. The restricted desktop options are not available
unless FoxView is installed. When the control panel is opened on such a station,
these options are disabled.
When options are disabled, an explanation is displayed near the bottom of the
dialog box. The next image shows this dialog box for domain controllers.
B0700TL, Rev B 43
44 B0700TL, Rev B
The next image shows this dialog box for stations not running FoxView.
If the startup options are invalid when the Control Core Services Startup
Options dialog box is opened, a system message is displayed near the bottom of
the dialog box. (This system message overwrites any descriptions of why options
are disabled). In this state, the OK button is disabled.
This image shows the dialog box for an Enterprise Edition station, indicating
invalid options have been set.
B0700TL, Rev B 45
To correct this condition, select one of the options in the dialog box. This enables
the OK button. Click OK.
NOTE: It is inadvisable to change the startup options in the middle of a
software installation unless directed by the documentation.
Autologon
The Autologon feature automates the logon process. Upon selecting autologon as an
option, the username and password will be collected and verified. These credentials
will be used on all subsequent logon attempts until at which time the Control Core
Services Startup Options utility is used to change the credentials in use. This
applies for both Enterprise Edition domain clients and Local Edition stations.
NOTICE
POTENTIAL SYSTEM COMPROMISE
While using this feature is more convenient than requiring users to log on manually,
be aware that it can pose a security risk as access to the desktop is provided
without requiring a user to provide appropriate credentials. Use this feature only in
areas that are secured by other means.
Failure to follow these instructions can result in system compromise.
46 B0700TL, Rev B
Autologon Configurator
After selecting an Autologon option from the control panel applet and clicking OK, you
are prompted for the logon credentials to use. Enter the user account, domain name
(only for Enterprise Edition domain clients), and the password (in both fields). Click
OK.
While entering the domain name, you have to use the short name (for example,
IASERIES), not the long name (for example, iaseries.local). A domain name is not
required for Local Edition settings.
Restricted Desktop
The restricted desktop options provide an option on Local Edition Control Core
Services to limit user access on operator stations. When a user enables one of the
Autologon, restricted desktop access or Autologon, restricted desktop access
and shutdown access options, it results in:
• Desktop icons are hidden.
• Access to desktop contextual menus are disabled.
• Access to taskbar contextual menus are disabled.
• Assorted Start menu options are removed, including All Programs and the
Control Panel.
• Search results are disabled in the Start menu.
B0700TL, Rev B 47
This image shows how you cannot change user settings, only sign out from the
account.
48 B0700TL, Rev B
This image shows how there is no option to restart or shutdown the workstation.
• Access to lock is disabled from the Start menu and removed from the Welcome
Screen.
• Access to the Task Manager is disabled.
When a user enables the Autologon, restricted desktop and shutdown access
option, it results in:
• The Shut down and Restart options are removed from the Start menu and
Welcome screen.
Once a restricted desktop option is in effect, it is not possible to directly access the
control panel and turn it off. Instead, access the Startup Options from FoxView. See
Foxboro DCS Control Core Services Startup Options, page 39.
Welcome Screen
The welcome screen is called by pressing Ctrl+Alt+Delete.
Only the commands you have privileges to access are enabled in this screen. The
next three images are examples of this screen for users with different type of
privileges.
B0700TL, Rev B 49
This image shows a sample Welcome screen for IA Plant Operators and for Restricted
Desktop and Shutdown Access.
This image shows a sample Welcome screen for Restricted Desktop Access.
50 B0700TL, Rev B
This image shows a sample Welcome screen for Local Edition User and IA Plant
Admins.
This screen provides access to these commands, depending on the current user’s
privileges:
• Lock - Disallows access to the station. The current user can unlock the station by
logging in. See Application Launcher Splash Screen, page 51.
• Sign out - Closes the current user’s programs without turning off the computer.
See Logging Off, page 53.
• Start Task Manager - Opens the Windows Task Manager.
• Shut down - Shuts down the station. See Shutting Down/Restarting the Station,
page 53.
• Restart - Reboots the station. See Shutting Down/Restarting the Station, page
53.
Application Launcher Splash Screen

This Application Launcher Splash Screen is called automatically when the system
starts up. It stays on the screen until all the required components are loaded and the
process is complete. A Spinner is shown at the center of this Application Launcher
Splash Screen to convey that a process is running and you must wait until the process
is completed. Once the process is completed the Application Launcher Splash Screen
is closed automatically. The Splash screen shows the product name, the components
that are getting loaded, and the version number.
B0700TL, Rev B 51
Control Core Services Log Off and Shut Down

These sections describe the methods of logging off and shutting down a Control Core
Services station, as well as the configuration information for the shut down process.
52 B0700TL, Rev B
Logging Off
Users can log off by performing one of these options:
• Press Ctrl+Alt+Del to call the Welcome Screen and click Sign Out.
• Click the Start button and then select the user account picture icon. Select Sign
out from the user account menu.
Once the station is shut down, every user on that station is logged off by the operating
system.
Shutting Down/Restarting the Station

Shut down a station by performing one of these options:
NOTE: Security settings might keep you from accessing to the Shut down and
Restart picks from the Welcome Screen and Start menu. Enterprise Edition
Control Core Services uses Group Policy Settings to restrict access. See Control
Core Services Security Implementation Guide (B0700HM). Local Edition Control
Core Services security settings are described in Restricted Desktop, page 47.
B0700TL, Rev B 53
• Press Ctrl+Alt+Delete to call the Welcome Screen. Click Shut down or Restart
from the power options menu on the lower-right.
• Click the Start button and click Shut down or Restart from the power options
menu.
• Use the menu selections in the SftMnt menu in the top menu bar of a FoxView
window. (Users have to be in the Process Engineering or Software Engineering
environment.)
NOTE:
• FoxView or the Control HMI are the preferred methods to shut down a station.
• Normally, when a shut down or reboot is called on a running station, the
requested action takes place. However, if a shut down or reboot is called
while a system is trying to boot up, the system might appear to get stuck. In
such cases, you have to manually shut down the system by holding the power
button on the front of the station for at least eight seconds. To reboot the
system, press the power button again.
54 B0700TL, Rev B
Shut Down Configuration

The Control Core Services stop services that are named in srvcs<DD>*.dat files and
terminates processes that are named in the procs<DD>*.dat file found in D:\usr
\fox\bin before shutting down the Control Core Services. The <DD> has to be of
two digits. Any text after these two digits is ignored, so that these filenames can be
self-documenting.
Examples of file names are:
• srvcs42pwrsoe.dat
• procs42pwrsoe.dat
• srvcs75_cogpkg.dat
• procs75_cogpkg.dat
• srvcs07powerapps.dat
• procs07powerapps.dat
This text is an example of the content in a srvcs25myapp.dat file:
# Names of services installed by the "myapp" package.
MyAppSvc1
MyAppSvc2
This text is an example of the content in a procs25myapp.dat file:
# Names of processes installed by the "myapp" package.
myapp_main.exe
myapp_evthndlr.exe
The files are not processed in order of the <DD> number. The srvcs<DD>*.dat files
are processed first, followed by the procs<DD>*.dat files, so as to terminate services
that might interfere with the shut down process by respawning.
After these files are processed, the remaining Control Core Services services are
stopped and processes are killed. The files are processed in this order:
• ia_srvcs.dat
• ia_procs.dat
Virtual Machines (VMs)

Re-enabling Functionality Typically Restricted on VMs
When setting up remotely accessed operator environments, such as access to a
virtual machine (VM) through a thin client or access to a VM through a Remote
Desktop session, the default environment restricts many activities on this session,
including but not limited to, acknowledging alarms, clearing alarms, and accessing
certain buttons from within FoxView.
There exists on the system several different scripting environments that must be set
up in order to allow access to various types of actions in the operator sessions.
Review these documents for more information:
• Alarm and Display Manager Configurator (ADMC) (B0700AM)
This document provides information on setting up the user environment for
alarming and display actions, including the various commands used to enable
and disable protections for certain actions.
• I/A Series System Alarm Management Commands and Keywords (B0700AP)
This document provides a complete description of all of the available alarm
management commands and syntax.
B0700TL, Rev B 55
• I/A Series Display Engineering for FoxView Software and Display Manager
Software (B0193MQ)
This document describes how to configure various settings in the FoxView
environments. See the “Security” section:
◦ Limiting Access to FoxView, DM, or AM from Remote Terminals
◦ Limiting Access within a DM or AM
• Workstation Alarm Management (B0700AT)
This document discusses security environments and access in the “Advanced
Operation Topics” chapter.
Solaris 10 Stations
GNOME Session Manager Segmentation
Solaris 10 workstations might experience a GNOME Session Manager
Segmentation Fault on the Foxboro DCS Control Network if there is a Domain
Controller (DC) running McAfee ePolicy Orchestrator/Host Intrusion Prevention.
Sun Microsystems has issued an Xsun patch resolving this condition. The patch
number is 119059, and you can acquire the latest patch version from Oracle Support
at: http://support.oracle.com/. You need to pre-associate your username with a valid
contract and CSI. Once you are logged on to the Oracle Support website, go to the
Patches & Updates tab and then search for the desired patch in the Patch Search
box on the right side.
Tools and Utilities

Getpars Utility (CAR #1012329)
The getpars utility accesses information of many storage sizes. These sizes are
converted to a signed character field within the program. Such conversions can result
in a negative signed value representing a positive unsigned number, for example 207
becomes -49 and 242 becomes -14.
Displays
Station Displays and Tool/Utilities List Same Number of Unique
Points at Different Values
The Object Manager calculates unique points because it is set up to minimize the
structure count of the Foxboro DCS. The station display reflects this design decision,
so when displaying 250 points with two duplicates, the display will show 248 unique
points total. Tools and utilities, such as DBVU, maintain as small a footprint as
possible to minimize their impact on system resources. Therefore, they simply
calculate the total points in use by going through the structure entries and adding
them up. So when displaying the same 250 points with two duplicates, these tool and
utilities display them as 250 points. Both numbers are correct.
56 B0700TL, Rev B
Detail Display Differences on Workstations on The Nodebus and

The Foxboro DCS Control Network
The operation and appearance of Detail displays is different for workstations on the
Nodebus side versus workstations on the Foxboro DCS Control Network side of two
networks connected by an ATS. First, the default Detail displays for the new v8.x
control blocks (for example, AI, AO, DI, DO) are not present on workstations on the
Nodebus side; the new control blocks are only installed on workstations with I/A
Series software v8.x or Control Core Services v9.0 or later.
The discrepancies in the appearances of the Detail displays are apparent if you are
running Display Manager, if you have not installed the enhanced Detail display, or if
the display was enhanced only for I/A Series software v8.x or Control Core Services
v9.0 or later.
Application Software
IFDC Software
The first time you use IFDC software after installing Security Enhanced I/A Series
software v8.8 or Control Core Services v9.0-v9.3, or Enterprise Edition Control Core
Services v9.4 or later, you have to log in as an Administrator. For example, a user
account which is a member of the “IA Plant Admins” group for I/A Series software v8.8
or Control Core Services v9.0-v9.3, or Enterprise Edition Control Core Services v9.4
or later, (which was the “Plant Maintenance” group for I/A Series software v8.5-8.7).
If you are not logged in as an Administrator, you will get a message stating that The
registry editor has been disabled by your administrator.
Alarm Management Subsystem

Alarm Counts and Page Counts
Alarm counts (for example, Alarm x of y) or page counts (for example, Page x of y), or
both, can be displayed in either the title bar or status bar.
When the alarm count is displayed, the ‘x’ value refers to the first alarm at the top of
the current display being viewed, and the ‘y’ value refers to the total number of alarms
on the display. The ‘x’ and ‘y’ values are accurate because the total alarm count is
incremented for each new alarm available.
This works somewhat differently for page counts. When the page count is displayed,
the ‘x’ value refers to the page on which the first alarm viewed is located, and the ‘y’
value refers to the total number of pages on the display.
The alarm count feature is designed to work with scrolling, and the page count feature
is designed to work with paging commands.
Using the scroll bar to scroll to the end of a display does not show empty cells. Unless
the last page of alarms is filled, the page count will appear inaccurate on the title and
status bars, but will actually be correct. For example, if you can view 10 alarms per
page on your CAD and you have 97 alarms scrolling to the end of the display, these
indicators are produced for alarm counts and page counts respectively:
Alarm 88 of 97
Page 9 of 10
B0700TL, Rev B 57
Scrolling to the very end of the display causes alarm 97 to be the last alarm on the
screen. Since 10 alarms are viewed on the display at one time, the first alarm on the
screen is alarm 88. However, alarm 88 is technically on page 9 of the display, so Page
9 of 10 appears as the page count.
If you are looking at page counts as reference points when navigating through a
display, use the paging commands. These commands are designed to work with the
page count feature.
With paging commands, you can “go to the last page”. This will display your alarm and
page counts as:
Alarm 91 of 97
Page 10 of 10
where alarms 91 through 97 are displayed in the top seven cells, and the remaining
three cells are empty. Scrolling to the end of the same display does not show empty
cells.
Configuring Alarm Management Options for V8.x Systems Using

ADMC
Alarm management options such as RTN_DROP, which removes alarms that have
returned-to-normal from the alarm database, are now configurable in ADMC. For
details on configuring these options in ADMC see Alarm and Display Manager
Configurator (ADMC) (B0700AM). \usr\fox\customer\alarms\cfg contains two
files, wp_am.cfg and am_def.cfg, that define the default settings for these and other
alarm management options.
If you have an existing (pre-v8.0) configuration that you would like to use on v8.0 or
later systems, you will need to copy your am_def.cfg file and any customer AM
specific configuration files (for example, AM0001.cfg) to \usr\fox\customer
\alarms\cfg and rename the wp_am.cfg file (to wp_am.cfg-80, for example). In
addition, you will need to copy your init.user file to \usr\fox\wp\data. (To use init.
user, you have to delete the wp_am.cfg file.) The alarm management software then
reads your custom configuration files and fills in defaults for new options. Any options
previously set in init.user are again read from that file.
Be advised that this applies to these alarm options:
ALMCLR ACKCLR RTNCLR RTN_DROP

SORT_CFG CLR_OPT MAX_ACTIONS MAX_CAD
HORN_OPT ACK_HORN RESOUND ALMPRI
ALMRTNS CONF_RTN LIA_OLDEST
ALMLNS and ALMTIM are configurable only through ADMC. This has been the case
since ADMC was available. The other options that are configurable through \usr
\fox\wp\bin\init.user remain unchanged.
One major advantage to configuring these options with ADMC is that a reboot is
usually not needed. The exceptions are for MAX_ACTIONS and MAX_CAD, because
configuring these options result in a change in size to the shared memory segment.
ADMC also provides a menu pick to distribute the configuration files to the
workstations. You can also select the type of action needed on each of the
workstations. Actions include rebooting the workstation or restarting selected alarm
management components (for example, Alarm Alert, Alarm Manager).
58 B0700TL, Rev B
Previously Deleted Alarm Manager Configuration Files

Previously deleted Alarm Manager configuration files are still shown in the Install Files
Distribution dialog box. Create Install Files does not remove the old .cfg files, and
Install Files Distribution distributes the .cfg files existing for a configuration in the file
system. Old .cfg files should be removed manually after the corresponding AMs have
been deleted in the database.
Moveability of Full Screen Current Alarm Display (CAD)

The Alarm Manager and FoxView software are two different applications. As such, if
FoxView windows are configured as unmovable, the Alarm Manager windows can still
be moved and vice versa.
Using the Alarm and Display Manager Configurator (ADMC), you can configure the
resizability and movability of the Alarm Manager displays. The Alarm Manager
Display Type dialog box has two checkboxes, Display is Resizeable and Display is
Moveable, that allow these configuration options. See Alarm and Display Manager
Configurator (ADMC) (B0700AM) for additional information.
Message Manager Software

The Message Manager User’s Guide (B0700AJ) states that Message Manager
workstations have to be dedicated to Message Manager and cannot run other
applications. This is true for both redundant and non-redundant control network
configurations, as stated in B0700AJ.
Although running other applications generally works, it adds an additional load to the
system so that applications might not run as expected. For example, if you attempt to
access the Current Alarms Display on a workstation running Message Manager
software, a message might appear, stating that the Alarm Manager is unable to
obtain new alarms because the Alarm Server Task is unavailable, although the
alarms do appear on the CAD.
Running a Single Message Manager

While running a single Message Manager (MM), if the MM server becomes
unavailable, then alarms might become unavailable as well. Though the alarms are
sent by the CP, they are lost by the MM in this case. This is not seen while running a
redundant Message Manager.
If you are missing alarms, restart MM to work around this condition. Restarting the MM
server forces a Current State Update (CSU) which forces the CP to send the current
alarm state. Be advised that the alarms are resent if in alarm, acknowledged, or in
neither state. As well, they are not resent if the alarms are returned-to-normal.
Configuring Default Alarm Manager

While configuring Default Alarm Manager (where AM name is same as the letterbug
name) through ADMC, check that the Screen parameter for Default Alarm Manager is
set to Both Heads. This setting makes default CAD non-quittable.
Set the Screen parameter.
1. From the select box in Display and Alarm Managers window, click Alarm
Managers.
B0700TL, Rev B 59
2. Select the existing Default Alarm Manager scheme in the list box and click Edit or
click New, to configure a new Default Alarm Manager.
Configuring the Alarm Manager scheme as described in this step, opens Alarm
Manager Dialog Box.
3. To enable Default Alarm Manager scheme, assign Both Heads to Screen
parameter in Alarm Manager Dialog Box and click OK.
Printing Alarm Priority to the Alarm Printer

PER1184037 provides the ability to print alarm priority to the alarm printer. To enable
alarm priority printing, set this registry entry on all workstations that host an alarm
printer.
Key: SOFTWARE\Wow6432Node\Invensys\IASeries\CSAlarm
For the original alarm printing style:
Value of type String:
MessagePriorityPrintStyle = UseOriginalAlarmPrintingStyle
For the enhanced alarm printing style, including alarm priority in the message
Value of type String:
MessagePriorityPrintStyle = UsePriorityAlarmPrintingStyle
If the entry is not present, the default will be the original alarm printing style. The
original alarm printing style is:
COMPOUND:BLOCK
HIABS
10-20-14 18:07:17:8 24.0IN ( 20.00) HIGH LEVEL
ALARM ALM
With the registry entry set, the alarm printing style is modified:
COMPOUND:BLOCK
HIABS 5
10-20-14 18:07:17:8 24.0IN ( 20.00) HIGH LEVEL
ALARM ALM
This image shows the use of priority alarm printing style.
60 B0700TL, Rev B
This image shows the use of the original alarm printing style.
B0700TL, Rev B 61
Control Configuration Software

Detected Error Message When Deleting a Block or Compound in
ICCAPI
Occasionally, when deleting a block using the ICCAPI, this detected error message
appears:
rm: cannot unlink entry “/opt/fox/ciocfg/<COMPOUND>/<BLOCK>.*”: The
system cannot find the file specified.
<COMPOUND> and <BLOCK> are the names of the block being deleted and its
associated compound. This message might also appear when a compound is deleted.
This message appears because the program is trying to delete a file that does not
exist. This condition does not in any way affect the block delete operation, and this
detected error message can be ignored.
Inadvisable to Shutdown or Reboot Station While ICC is Open

It is inadvisable to attempt to shutdown or reboot a station while ICC is open. First,
close ICC and then proceed with the shutdown or reboot operation.
Control Databases and Process Control

Re-Alarming Change in FCP270 and ZCP270 CP Images v2.5 and
Later
With the earlier FCP270 and ZCP270 v2.2 control images released with I/A Series
software v8.0 Revision B software, any change in alarm priority (higher to lower or
lower to higher, where 1 is the highest priority) caused the controller to send a re-
alarm message and set the alarm acknowledgement status to the Unacknowledged
state. That is, the block parameter UNACK was set to 1 when the priority of an alarm
was lowered.
By contrast, the later FCP270 and ZCP270 v2.5 control images, originally released
with Quick Fix 1007242 and Quick Fix 1007241 respectively, preserve the alarm
acknowledgement status for alarms that are changed from a higher to a lower priority.
Controller software does not automatically re-alarm to the Unacknowledged state
(UNACK=1) when you lower the priority of an alarm.
For example, if an alarm has been generated and acknowledged, lowering its priority
does not set the block alarm state to Unacknowledged. Alternately, if the same block
alarm was generated and acknowledged, raising its priority will set the block alarm
state to Unacknowledged.
Re-Alarming for Multiple Alarm Priority Types

If more than one alarm priority type is enabled for a single block, there are cases
where an acknowledged alarm can mandate an additional operator acknowledgment
if an alarm priority is lowered. This behavior occurs because a block has only one
boolean acknowledgment status parameter but can have multiple alarms with different
priorities.
62 B0700TL, Rev B
AIN Block Example

For example, take a situation where an AIN block has multiple active acknowledged
alarms (UNACK=0). Raising one alarm’s priority causes the block to go to the
Unacknowledged state (UNACK=1) as expected. Then, if you lower the priority of
another alarm from the same block, the Unacknowledged state of the block that
existed before alarm reprioritization is preserved, UNACK=1. Therefore, changing the
priority of the second alarm in this case has no effect on the block alarm state
because the block remains in the Unacknowledged state and an operator
acknowledgment is needed. The event history is:
• The AIN block has these alarms tripped:
◦ High Absolute Alarm Indicator (HAI)
◦ High-High Absolute Alarm Indicator (HHAIND)
◦ High Out-of-Range Alarm (HOR)
◦ Bad input (BAD)
• Alarms are acknowledged.
• Out-of-Range alarm priority (ORAP) is raised from 3 to 2. This action causes the
block alarm state to be set to Unacknowledged.
• High/Low alarm priority (HLPR) is lowered from 2 to 3. This action has no effect
on the block alarm state, which remains Unacknowledged.
When ORAP was raised, the Unacknowledged state was set. Lowering HLPR does
not change the Unacknowledged state of the block, which can be preserved.
The Integrated Control Software Concepts for CP270, FCP280, and FDC280 User’s
Guide (B0700AG) describes the details of alarm reprioritization, specifically, the
preservation of alarm acknowledgment status after re-alarming.
Change Block Modes on DO or AO Blocks

When changing block modes on a DO (digital output) or AO (analog output) block and
while the output value is simultaneously changing, the detail display might display a
detected CFG error indication, including the text message W73-FF Function Block
Configuration Error. This occurs because there is a “race” condition between the
mode change and the output data change. The message clears when the mode is
changed again. The block operates normally.
To avoid this situation, when changing modes, wait for the transition to the new mode
before changing the output value.
Dynamically Reconfiguring a Block Parameter

Dynamic reconfiguration is a procedure where a user modifies a block parameter with
a configuration tool like ICC while a loop containing the to-be-modified parameter is
running. Dynamically reconfiguring a block parameter might cause an unexpected
process upset or other subtle concerns.
Simply modifying a block’s parameter makes that block’s inputs and outputs go out-of-
service (OOS). Depending upon the size of the database and other factors (for
example, propagation options or block period/phasing), the OOS condition might
result in non-deterministic behavior. For example, blocks connected to the block being
modified might detect the OOS condition and assert “fail-safe” in the device under
control unexpectedly.
Optimal practices dictate that one or more loops be configured in a compound so that
the entire compound can be turned off before its blocks are reconfigured. To keep
accidental or intentional dynamic reconfiguration from occurring, set Bit 0 (CFG_
B0700TL, Rev B 63
SEC_OPT) in the STATION block’s CFGOPT parameter. See Integrated Control Block
Descriptions (B0193AX) for a description of this parameter.
PAKOUT Block Limitations

When using a PAKOUT block, the controller needs exclusive control of the PLC bits
associated with the PAKOUT registers. If a value is set by any source, Control Core
Services will overwrite the value the next time a write occurs.
NOTE: Unexpected results occur if you allow anything other than the Control Core
Services to modify bits and registers in a PLC associated with a PAKOUT control
block.
For example, take a PAKOUT block associated with registers 40010 through 40013 in
a Modbus device, and assume this sequence of steps occurs:
• If the Control Core Services initially set the bits to 0, each of the four registers in
the device are set to 0.
• Another source sets the value of register 40011 to 1.
• The Control Core Services want to set a bit in register 40010 to 1.
• When the Control Core Services write its value, it succeeds in setting the bit in
register 40010, but overwrites the value in register 40011 back to 0.
This concern applies to FBM224 as well as the FDSI drivers (FBM230 to FBM233)
that use the PAKOUT block.
Using AOUTR Blocks with ECB38R for FBM46/FBM246 Applications

The Redundant Equipment Control Block 38 (ECB38R) provides the software
interface for FBM46 or FBM246, which support redundant intelligent field device input,
and analog output signals.
If you are using an ECB38R, it is highly recommended that you use a Redundant
Analog Output (AOUTR) block with the FBM46/FBM246 and NOT Analog Output
(AOUT) block(s), even though the software allows it. It is especially vital that you do
use an AOUTR block instead of using one AOUT block for each partner in an FBM46/
FBM246 pair.
Using AOUT blocks with the ECB38R can cause situations in which one FBM takes
over properly for the other, or in which the CP might send empty packets to the FBMs
and cause traffic on the PIO bus.
Using the OSP 0 Instruction in the LOGIC Block

Using the instruction “OSP 0” (one-shot pulse timing function) in the LOGIC block of
the CP60 or the CP270 does not work properly. The block logic incorrectly uses the
value specified in RI01 instead of using a time constant of 0.5 second. If RI01 is
unused by the LOGIC block program, then the timer duration defaults to a value of 0,
and the expected pulse is not generated.
64 B0700TL, Rev B
Control Processor (FCP280, FCP270 and ZCP270)

Issuing a Reboot Command for a Shadow FCP280 or CP270 Module
If you call a Reboot command for the shadow module of a fault-tolerant FCP280s pair
from System Manager, and the shadow module is not physically present, the Shadow
Mode Equipment Status field in System Manager shows Downloading until a module
is inserted in the shadow slot.
Address Stations with Numeric Letterbugs

If you assign a hostname with only numeric characters to a station, you have to take
additional steps to disallow workstations from interpreting the hostname as a numeric
IP address:
• Enclose the hostname in single quotes in the HOSTS file.
• When executing command line utilities that reference the numeric hostname from
a Windows Command Prompt, enclose the hostname in single quotes.
• When executing command line utilities the reference the hostname from a shell
prompt, place backslashes before the single quotes.
For example, if a controller on the control network has a hostname of 123456 and its
numeric IP address is 151.128.152.60, the HOSTS file on workstations have to
contain an entry with the hostname enclosed in single quotes:
151.128.152.60 '123456'
To ping the station from a Windows Command Prompt, use single quotes:
ping '123456'
To ping the station from a shell prompt, use backslashed single quotes:
ping \'123456\'
Installing or Replacing FCP280, CP270, and FCM100 Modules in a

Running System with I/A Series Software v8.x or Control Core
Services v9.0 or Later
To install a “new” or “replacement” module in a running system with FCP280s,
FCP270s, or ZCP270s, take care to avoid the use of duplicate letterbugs, IP
addresses, and/or MAC addresses. To make sure that there are no duplicates, clear
the newly added station’s NVRAM before adding the module.
1. Power up the station without any cables.
2. For CP270, set the letterbug to “NOSUCH” with the PDA. See Letterbug
Configurator (B0700AY) for procedures on setting letterbugs. For FCP280, set
the letterbug, as described in Field Control Processor 280 (FCP280) User's
Guide (B0700FW), even if it is set to the same letterbug already set in the
module.
3. For CP270 only, after the station’s NVRAM is cleared, read the station’s status
with the PDA. If properly flushed, the PDA will read the “NOSUCH” letterbug and
an IP address such as 255.255.255.255 for a CP or 0.0.0.0 for an FCM
After the station is flushed, you can then add the station to the system.
B0700TL, Rev B 65
Adding a Module to an FCP280, CP270, or FCM Fault-tolerant Pair

1. Connect the cables to the modules as described in the module’s user’s guide.
2. Insert the module with its partner. The shadow station boots up and copies the
pertinent information it needs from the primary module.
The two modules then marry and begin running as a pair.
Adding a Single FCP280, CP270, or FCM

1. Power up the module without any cables. For CP270, set the system letterbug to
with the PDA. See Letterbug Configurator (B0700AY) for procedures on setting
letterbugs.
For FCP280, set the system letterbug as described in Field Control Processor
280 (FCP280) User's Guide (B0700FW).
2. Remove the module from the system, attach the cables, and replace the module
in the system. The module will reboot two times to collect the NVRAM information
from the host, and will then become an active station.
Make certain that your system does not contain duplicate letterbugs, IP
addresses, and/or MAC addresses using System Manager, SMDH, or the System
Monitor to make certain the expected devices are correctly in service.
Field Device Controller 280 (FDC280)

FDC280 IOM Image
The FDC280 firmware has had these major released versions:
• 0900009000 with CCS v9.3 (initial release supporting Ethernet support only)
• 0900010000 with CCS v9.4 and QF39115499 for CCS 9.3 (Ethernet support only)
• 0901003000 with MP47481162 on CCS v9.3, v9.4, and v9.5 (Ethernet and Serial
support)
You can check the image revision of your FDC280 using either:
• System Manager - FDC Equipment info field “Primary Core1 image version”
• FoxView - Station block field “Core1 Soft version”
CCS v9.6 install includes FDC280 image version 0901004000.
If your current CCS version is CCS v9.3 or CCS v9.4 and the FDC280 image version
is 0900009000, before you upgrade to CC v9.6, complete these steps:
• Install QF 39115449 and update the FDC280 image to 090001000.
• Install CCS v9.6 and update the FDC280 to 0901004000.
See Field Device Controller 280 (FDC280) User's Guide (B0700GQ) for image update
instructions.
Setting Timeout Option for Modbus TCP Client Driver for Interfacing
Tricon and Trident Devices
For interfacing to Tricon and Trident devices using the FDC280 Modbus TCP Client
driver, set the Timeout option (+TO=n) in the ECB201 Device Options to two seconds
66 B0700TL, Rev B
or more. Tricon/Trident devices sometimes need the extra time to respond after
connections are re-established.
Address Translation Station (ATS)

Communicating Directly to an ATS
If you want to communicate directly with an ATS in LI mode, don’t use a workstation
on a node with an LI. Communicate to the ATS from a workstation on the control
network or from a node with another ATS in LI mode.
Direct communication to ATSs include:
• Reading ATS OM variables, as described in the Address Translation Station
User’s Guide (B0700BP).
• Performing Nodebus Test Initiator actions, such as running a cable test. These
actions are sent to the Current Test Initiator, which by default is the ATS.
• Getting SGL cable indications. SMDH gets these indications from the Current
Test Initiator of each node, which by default is its ATS.
The restriction is a result of the address translation functions that the ATS performs.
As packets are forwarded through the ATS in Extender mode, it translates the source
Node ID so the packet looks as if it originated on the bridging node. ATSs in LI mode
use the LI MAC address 00-00-6c-c0-01-ff, so the translated packets appear to have
originated from the LI of the bridging node. Consequently, stations on nodes with LIs
end up directing communications for ATSs in LI mode to the LI on the bridging node
instead.
Stations on the control network and stations on nodes with ATSs in LI mode do not
exhibit these symptoms because these stations see the actual Node IDs, as opposed
to the translated IDs.
Station Support for Address Translation Station

Address Translation Stations (ATSs) support connections on the Foxboro DCS
Control Network for these Foxboro DCS and I/A Series stations:
• Triconex Advanced Communications Module in the Tricon™ controller (for
connections to the FoxGuard Manager).
• Allen-Bradley Integrator 30 Style B
• Modicon Integrator 30 Style B
• Device Integrator 30 Style B
• Legacy Control Processors (withdrawn from sale) CP30, CP30 Style B, CP40,
CP40 Style B, and CP60
These stations have to have the minimum firmware revisions listed in this table in
order to operate with the ATS.
Some firmware revisions and OS image versions in this table and chapter include
modules that are in the Lifetime and Obsolete lifecycle phase. Such modules are
under limited supported as defined in the Product Lifecycle User’s Guide, available on
the Global Customer Support website. Although Control Core Services software
versions 9.6 and earlier can boot host such modules with the minimum firmware and
OS versions listed, there is limited support for issues with the function of these
modules. It is always best practice to operate hardware and software that is in a fully
supported lifecycle phase. If you are operating with hardware or software in the
Lifetime or Obsolete lifecycle phase, we strongly recommend you upgrade to fully
supported hardware and software as soon as possible.
B0700TL, Rev B 67
Table 13 - Minimum Versions for Nodebus Stations Running on The Foxboro

DCS Control Network
Minimum Firmware
Station Type Revision Minimum OS Image
CP60 3.30 6.5.3
CP40B 3.30 6.1.6
CP40 3.30 6.1.5
CP30B 3.30 6.1.6
CP30 3.30 6.1.5
Device Integrator 30B 3.31 6.5.2
Allen Bradley Integrator 30B 3.31 6.1.6
Modicon Integrator 30B 3.31 6.1.6
Triconex ACM (FoxGuard 4.2.2 6.2.7
Manager)(a)
Communication Processor 10 2.20 6.5.1
(a) When the host station of the Triconex ACM on the control network is running I/A
Series software v8.5-v8.8 or the Control Core Services, QC1117037 is the only
recommended image to be installed on this host station.
NOTE: Though a COMM10 station can be hosted, it does not support printers in
this configuration. The only support on COMM10 station ports hosted by a
workstation on the Control Network is for a VT100 terminal (TERM) on COMM10
port 4. Configuring printers on a COMM10 port hosted by a workstation on the
Control Network results in a Windows OS bluescreen.
Network Unavailability Detection Logs

The NFD logging feature introduced on workstations with I/A Series software v7.x is
also available on Address Translation Stations. For each ATS hosted by a
workstation, these logs are available on the boot host:
• \opt\fox\sysmgm\nfd\nfd_log.LTRBUG.txt
• \opt\fox\sysmgm\nfd\nfd_debug.LTRBUG .txt
Where LTRBUG is the letterbug of ATS generating the messages.
Unlike on workstations with I/A Series software v7.x, the log files are configured
through the registry rather than by creating the file, and each entry is prepended with
the UTC time.
By default, only nfd_log.LTRBUG.txt files are maintained. This behavior can be
modified by configuring the ATS Monitor in the registry. The values below are present
under the key HKLM\SOFTARE\Invensys\IASeries\ATS Monitor:
• NfdLogEnabled - If set to 0, the nfd_log.LTRBUG.txt files are not maintained.
• NfdDebugEnabled - If set to 1, the nfd_debug.LTRBUG.txt files are maintained.
• LogDirectory - Change the default log file location from \opt\fox\sysmgm
\nfd\.
• MaxLogSize - Change the default maximum log file size from 1000kb.
These values are only read when the ATS Monitor starts (at boot). You can force the
values to be reloaded immediately by restarting the monitor: open the Task Manager,
select Show processes from all users, right-click the ATSMonitor.exe, and select
End Process Tree. The process and its agents restart and read the new values.
68 B0700TL, Rev B
If NfdLogEnabled and NfdDebugEnabled are both set to zero (0), the ATS Monitor
exits shortly after startup. To restore logging, change at least one of the values to 1
and reboot the station.
When a log file (nfd_log.LTRBUG.txt or nfd_debug.LTRBUG.txt) ) reaches
MaxLogSize, the contents are moved to a backup file (nfd_log_saved.LTRBUG.txt or
nfd_debug_saved.LTRBUG.txt), overwriting any existing contents. Then the log file is
emptied.
Startup detected errors and other similar system messages are logged to the Event
Viewer in the Application log, source “ATS Monitor” (for example, changing the
LogDirectory to a non-existent location).
NOTE: If you used stabin_tool.exe to disable NFD mastership on an ATS (for
example, using QF1008334, QF1009129, or QF1011230), remember to restore
the normal behavior after removing the workstations with I/A Series software v7.x
from the node. This makes certain there is a still a candidate NFD Master
available on the node. To enable NFD mastership on an ATS, run stabin_tool.exe
-a -nonfd 0 STALTRBUG.BIN on the ATS boot host, then reboot both sides of the
ATS together. The station reboots twice: once as directed from you and a second
time a minute later to reconfigure against the STABIN file changes.
If NFD mastership is disabled on an ATS, the nfd_log.LTRBUG.txt records “Nodebus
Master Permanently Disabled” each time it connects to the ATS.
Intrinsically Safe I/O Subsystem

Using SRD991 with the Intrinsically Safe I/O Subsystem
The revision 3.2 (firmware revision 14) or later SRD991 HART Intelligent Positioner
interoperates with the Intrinsically Safe I/O subsystem. If you are using the SRD991
with the ISCM, be sure that the SRD991 firmware meets these specifications. For
more information, see Intrinsically Safe I/O Subsystem User's Guide (B0700DP).
Fieldbus Modules (FBMs) and Field Communication

Modules (FCMs)
Due to a limitation in the IOM228 Version 3.36 (and earlier) it is not possible do an on-
line update from version 3.50 and backwards to version 3.36 or earlier. If a "down-
grade" is required, the FBMs in the redundant pair both must be set OFF LINE before
the EEPROM UPDATE. Even in OFF LINE mode, it's possible that the FBMs will not
operate properly after going back to an older version. There can be issues like:
• Devices or points remain disconnected with fault "UNRESOLVED
CONNECTION" reported in corresponding Detailed Display.
• Device or pointsm might report "DUPLICATE CONNECTION" condition in
corresponding Detailed Display.
After a downgrade (from version 3.50 to an earlier version) it is required to check all
devices (ECB201) and all points (AI, AO, etc.) for proper operation. To recover, it
might be required to:
• Un-deploy and deploy EDB201 or Block(s).
• Power cycle FF device.
B0700TL, Rev B 69
NOTICE
POTENTIAL EQUIPMENT DAMAGE
If a down-grade is required for IOM228 version 3.50, verify that both FBMs in the
redundant pair are set to OFFLINE before the EEPROM update. Even in the offline
state, note that it is possible that the FBMs will not operate properly after going back
to an older version. After downgrading the version to 3.36 or earlier, it is required to
check all devices and all points for proper operation prior to continuing with normal
operations.
Failure to follow these instructions can result in equipment damage.
Redundant FBM248 Pulse Count

Because of the way redundancy is implemented, some changes in redundancy status
(Active/Tracker settings, FBM being reset, or FBM module insertions) might result in
the pulse count indication to increment by one count on channels set as “pulse input”.
This happens only in voltage input pulse mode, and can be mitigated by carefully
inserting or extracting modules perpendicularly into the baseplate. Since resetting a
module is a redundancy status change, it might occur after a module is reset by an
operator using a control configurator application and the channel count might not
appear to stay at zero.
Configure the FBM206 Input Frequency Using the RES04 Parameter

If you upgrade to a new version of FBM206 software, you have to configure the
RES04 parameter to 4, in the ECB4, in order to keep the 1.0 Hz minimum input
frequency. Otherwise, the default value of RES04=3 will set the minimum input
frequency to 2.0 Hz.
Main/Tracker FBM222 Role Switches

When the FBM222 switches roles, that is, Main becomes Tracker and Tracker
becomes Main, a few messages on the PIO Bus might be lost and not responded to
by the FBM222. In some cases, this can result in the message PIO Bus Access
Error in the System Monitor log. This condition is normal since it takes the FBM222
some time to switch.
Signal Conditioning in RIN Block for FFH1 d/p Cell

The use of SCI=4 in the RIN block does not work properly when setting a flow
compensation loop from a FFH1 d/p cell. Perform the square root extraction of the
signal in the field device. Reference the manufacturer’s documentation for configuring
the AI function block within the device for flow compensation.
EEPROM Updating FBM216s with Software Prior to v2.35F

FBM216 software versions prior to 2.35F can cause points to go out of service after
the EEPROM update of the MAIN module pair. There are no concerns when the
BACKUP module is updated. To perform an on-line upgrade without having the points
go out of service, you have to follow either of the procedures below to perform the on-
line upgrade.
70 B0700TL, Rev B
The simplest procedure needs an unused slot pair in a system to perform the
upgrade. An alternate procedure is provided in case there are no unused slot pairs in
the system, but this needs the use of a spare FBM216.
If an Unused Slot Pair Is Available

1. Switch roles to the BACKUP module of the FBM216 pair to be updated.
2. Remove the MAIN module and install it in a spare slot.
3. Configure an ECB202 for the spare slot to allow you to EEPROM update the
module. It is not necessary to configure the device ECB201s.
4. EEPROM update this module to v2.35F. Verify this version using the EQUIP
INFO page of SMDH.
5. Remove the module and replace it in its original MAIN slot.
6. When the MAIN module comes on line, switch roles to the MAIN module.
7. EEPROM update the BACKUP module to v2.35F. Verify this version using the
EQUIP INFO page of SMDH.
8. Repeat steps 1 through 7 for any other FBM216 modules in the system.
If an Unused Slot Pair Is Unavailable

Perform these procedure if an unused slot pair is not available. This procedure needs
you to have a spare FBM216 module.
1. EEPROM update the BACKUP module of an FBM216 pair to v2.35F.
2. Remove this module and replace with a spare FBM216.
3. EEPROM update the spare module in the BACKUP slot to v2.35F. Verify this
version using the Equipment Information display in SMDH.
4. When the BACKUP module comes on line, switch roles to the BACKUP module.
5. Remove the MAIN module.
6. Replace the MAIN module with the one originally removed from the BACKUP slot
in Step 2 above.
7. When the MAIN module comes on line, switch roles to the MAIN module.
8. Remove the BACKUP module and replace with the module removed in Step 5.
9. EEPROM update the BACKUP module to v2.35F. Verify this version using the
Equipment Information display in SMDH.
10. The spare module can now be used to update other FBM216 pairs by repeating
Steps 2 through 9 above. (You do not need to EEPROM this module again in
Step 1 because it already has v2.35F software installed).
Duplicate Channel Numbers for FoxCom Transmitters (ECB18) and

FoxCom Valves (ECB74)
No checking is done for duplicate channel numbers when configuring ECBs for
FoxCom transmitters (ECB18) or FoxCom valves (ECB74). In general, be especially
careful the I/O points are both configured and wired correctly.
B0700TL, Rev B 71
Configuring FCMs for Simplex Operation

For an FCM, Bit 2 of the ECB210 FCMCFG parameter, where Bit 0 is the least
significant bit, is used to communicate to the system whether the FCM is running as a
single module or as a redundant pair. To configure the FCM as simplex, set the
FCMCFG parameter in the ECB210 to 0x04, which sets Bit 2 of FCMCFG.
The table shows the position of the FCMCFG bit that allows you to configure the FCM
for simplex operation. By default, FCMCFG is set for redundant operation of the FCM.
Figure 1 - Setting the FCMCFG Parameter for Simplex Operation of the FCM
FCMCFG Bit Numbers
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
B20
B21
B22
B23
B24
B25
B26
B27
B28
B29
B30
B31
B32
B12
B13
B14
B15
B16
B17
B18
B19
B10
B11
B1
B2
B3
B4
B5
B6
B7
B8
B9
A
Table 14 - Setting the FCMCFG Parameter for Simplex Operation of the FCM
Legend
A FCM100E Simplex/Redundant Configuration Bit
Simplex mode is defined as a single FCM module that is not configured to run with a
partner module. When the FCM is running in simplex mode, a system alarm is not
generated for the missing partner module. That is, a missing B FCM module will not
be shown as unavailable in SMDH, the FCM icon will not show a “warning” status
based on the missing partner module, and a system alarm will not be generated
based on the missing partner module.
The FCM defaults to a redundant configuration, in which Bit 2 of FCMCFG is set to 0.
In the redundant mode, a missing B FCM module is marked as “failed”, the FCM is
shown in a “warning” condition, and a system alarm is generated.
NOTE: A single FCM100E module configured for simplex operation has to reside
in an odd-numbered position of a 2-, 4-, or 8-position baseplate. Incorrect
placement of a single simplex module causes the module to become unavailable
in a constant reboot cycle.
Validating Compact PROFIBUS Configuration File

During the validation of the slave configuration file for any compact PROFIBUS
device, these messages appear:
Error validating device.
MAX_INPUT_LEN value is not specified
MAX_OUTPUT_LEN value is not specified
MAX_DATA_LEN value is not specified
MAX_MODULE value is not specified
Ignore these messages as they are not needed in the gsd file for compact PROFIBUS
devices.
72 B0700TL, Rev B
Performing General Downloads on ZCP270

This note only applies if a ZCP270 is being used.
When performing a general download after a LoadAll, click GENERAL DOWNLOAD
twice. The first click downloads each of the FCMs and the second downloads all the
FBMs.
FBM216 Role Switch

If an FBM216 was running v2.40J or v2.40L software and a role switch was
requested, one or more of the points would appear as out of service for a couple of
seconds. This only happened when the MASTER was running these software levels
and the tracker version was running software levels 2.40D or E (for example, during
an image upgrade).
This condition has been fixed for the I/A Series software v8.6-v8.8 or Control Core
Services v9.0 or later releases. However, this fix results in a minor incompatibility with
older versions of the IOM216 software. The incompatibility only occurs when
switching from a master module that is running newer software (2.40M or later) to a
new master module that is running old software (2.40L or earlier). The incompatibility
results in HART points being out of service for a period of up to 4 seconds.
Normal operation and normal upgrades will not have such a suboptimal condition.
However re-loading an older image will have that effect because module 1 gets the
older software. A role switch makes that downloaded version the new master (and
generates the out of service condition), and then the old master gets downloaded.
200 Series FBM Rate of Change Alarms

IOM files released with I/A Series v8.6-v8.8 or Control Core Services v9.0 or later
software correct a long-standing detected error in the Rate of Change alarming
performed by the 200 Series analog input FBMs.
The description of the ROC parameters for the ECBs define them as the maximum
number of raw counts per 100 milliseconds. Until now, the FBM was making the
calculation using the number of raw counts per second, which is actually 10 times the
desired value. This detected error has been fixed in this software version and this
means that if you set the ROC parameters to non-zero, you might find that the FBMs
are now getting rate of change alarms where they had not been getting them before
the FBM was updated.
Before updating your FBMs to the new software version provided with I/A Series
software v8.6 or v8.7, check the configuration of the ROC parameters first. If they are
all zero, then no additional checking is necessary. If any of the ROC parameter are
non-zero, be sure to confirm that the values are correct in light of the raw counts per
100 millisecond rule, as this is how the FBMs will show rate of change alarms once
they are updated with the new software. If the previous settings were experimentally
determined to alarm correctly for your process conditions, then a simple multiplication
by 10 of the current configured values makes the FBMs respond to rate of change as
they did before the software update.
Configuring Fail-Safe for Proper Operation of FBM218

Proper operation of the redundant FBM218 needs that the fail-safe parameters in the
ECBs associated with both FBMs (main and backup) be correctly configured. In
general, the FBM outputs has to be configured to fall to zero in order to allow the
B0700TL, Rev B 73
opposite (available) FBM to assume (or continue) control without interference from the
unavailable module.
EEPROM Updating FBM220 and FBM221

Before you perform an EEPROM update on an FBM connected to a Foundation
Fieldbus positioner, be certain that the ROUT block corresponding to the positioner
has recovered from any previous operation, such as an FBM reboot. If you do not
allow the ROUT block to finish its operation, the positioner might not retain its
configured faultstate value.
Field Device System Integrator (FDSI) Subsystem

Common Concern for FDSI Modules
When reinstalling an FDSI driver, Field Device System Integrators (FBM230/231/232/
233) User’s Guide (B0700AH) instructs you to remove the previously installed driver
by using the Add/Remove programs under the Windows Control Panel. In some
cases, the FDSI driver does not appear in the list of software packages that can be
removed. You can work around this concern by uninstalling the driver from the driver’s
installation CD-ROM. After inserting the CD-ROM, run the setup.exe program. A
dialog box appears offering three choices: Modify, Repair, and Remove. Click
Remove to uninstall the driver.
FDSI FBMs Might Suffer Temporary I/O Connections Unavailability while

Updating CP270s
After CP270s have been updated to a newer control image, using the COLD START
option of ON-LINE IMAGE UPDATE, the FDSI modules (FBM230, 231, 232, and 233)
might result in temporary I/O connections unavailability.
Unresolved Connection on FDSI Device ECB201

When an FDSI FBM port is disabled and a device associated with the FDSI FBM is
added by the CP, the device ECB201 displays a W62 - UNRESOLVED
CONNECTION detected error on the Default Detail display.
In certain situations, you might not realize that the FDSI FBM port is disabled. For
example, if you use ICC to add the FDSI FBM and the device immediately after
initializing the CP270 database, the port might still be disabled.
If an ECB201 displays this detected error on the Default Detail display, check the
parent ECB200/202 to see if the FBM port is disabled. If so, enabling the port via
SMDH resolves the W62 detected error. See Field Device System Integrators
(FBM230/231/232/233) User’s Guide (B0700AH) for instructions on checking the
status of and enabling/disabling FDSI FBM ports.
EEPROM Updating FDSI FBMs (FBM230 to FBM233)

After performing a Day 0 Control Core Services installation, EEPROM update the
FDSI FBMs (FBM230 to FBM233). After performing the EEPROM update, restart the
FBM and confirm that the FBM has the correct EEPROM revision level. For the latest
EEPROM revision levels, see Appendix A: EEPROM Revision Levels, page 91.
74 B0700TL, Rev B
When EEPROM updating these FBMs, you might encounter problems getting the
FBMs to go on-line. In extreme cases of difficulties making the FBM operational after
the update, it might be necessary to do a delete/undelete of the ECB for the FBM, or
even to reboot the controller that is hosting the FBM.
Display FoxCom Device Information After General Download

At the startup or initial General Download or Download function used to bring FoxCom
FBMs that support child devices on-line, the SMDH and Detail displays for these
devices might omit some transmitter information. To correct this concern, toggle the
FoxCom device off-line then on-line in the SMDH Equipment Change display, and the
transmitter information displays correctly. Once the FoxCom devices have been
toggled off-line and on-line, the concern no longer exists.
FBM223 PROFIBUS Configurator

The FBM223 PROFIBUS Configurator only supports GSD Revision 3. Request a
GSD file with Revision 3 from the device vendor.
Changing FSENAB for ECB200 (PROFIBUS-DP FBM223)

Changing the FSENAB (“fail-safe enable”) parameter from 0 to 1 on an ECB200 that
is configured for PROFIBUS-DP FBM223 might cause the associated DCI blocks to
go “fail-safe”. This is only true if the DCI blocks are configured for “fail-safe” due to
communications unavailability.
TIMSTP Parameter of the EVENT Block

The Time Stamp parameter (TIMSTP) in the EVENT block gives the time, in
milliseconds past midnight, when the FBM generates an event record. Occasionally,
the TIMSTP parameter of the EVENT block resets to 0 when the FBM is downloaded
or placed on-line. After the TIMSTP parameter resets, it starts counting the
milliseconds since the reset, instead of resuming counting at milliseconds since
midnight. After about 50 seconds, the parameter is synchronized correctly with the CP
time. This situation has been observed using an FBM207b attached to a ZCP270 via a
pair of Fieldbus Communication Modules.
Online/Offline States of SPECTRUM I/O Migration Modules under

ZCP270
Behind a ZCP, match the online state of a parent SPECTRUM I/O migration module
with the online state of its children modules. If the parent needs to be turned offline,
turn the children offline first. If this is not done, there are instances where the scan of
the children modules continues and every read of those modules results in a time out.
Since time outs take six times as long as normal reads, this might lead to CPU
overruns.
B0700TL, Rev B 75
Foundation Fieldbus, PROFIBUS-DP, HART, Modbus,

DeviceNet, and FDSI
DeviceNet Baud Rate
Modifying the DeviceNet Baud Rate is a very unusual configuration change, but if it is
necessary, consider these points:
• The recommended DeviceNet Baud Rate is 125 kBaud. It is very unusual that
higher Baud rates are needed.
• After changing the Baud Rate, all DeviceNet devices have to be power cycled.
There are DeviceNet devices configured for “Auto Baud” that will try to use the old
Baud Rate.
• Some devices are either not configured for “Auto Baud” or have other means
(DIP Switches, etc.) for changing the Baud Rate. These types of devices will
need to be reconfigured for the new Baud rate and then power cycled.
• If the device “Auto Baud” function is disabled, it can be difficult to get the device to
be operational again, since the network is now configured for a different Baud
Rate. The device might need to be moved to a different segment where a third
party tool can be used to change the Baud Rate settings.
• Any third party tool used for device configuration (for example RsNetworx) will
also need to be changed to the new Baud Rate.
Peer-to-Peer Connections of Real-Type Block Inputs

When a block input of type Real is configured to a parameter of a block in a different
control processor, a change-driven connection is established. The value of the
receiving or sink parameter is updated every time the value of the source parameter
changes more than a preset amount.
If the sink parameter has a configurable range (high and low scale values) and a
change delta value (typically DELT1, DELTI2, etc.), then the size of the change
needed to trigger the update is configurable.
Configuring a DELTI [1, 2, etc.] value of zero (0.0) will NOT result in the sink being
updated every cycle. Within the system, the zero (0.0) is replaced by the value 0.1
and the effective change delta is 0.1 percent of the sink parameter range (For
example, 0.1/100*(highscale-lowscale)).
When small changes have to be communicated, specify an appropriate small,
positive, non-zero change delta value. For example, DELTI [1,2,etc.] = 0.00001 on a
parameter with a range of 20 to 50 would result in an update for every change greater
than [(0.00001/100)*(50-20)] = 0.0000030 units.
If the sink parameter does not have a configurable range or change delta value, as is
the case with the real inputs RI01 - RI08 of the CALCA and MATH blocks, then the
change delta used for Peer-to-Peer connections is a fixed value of 0.0001 (units of the
source parameter, not percent of range).
When very small changes have to be communicated, consider scaling the value with
gain and bias at the source end. For example, scale from tons to kilograms.
76 B0700TL, Rev B
Data Transfers Between the Nodebus and The Foxboro DCS

Control Networks
I/A Series software v8.2-v8.8 or Control Core Services v9.0 and later supports inter-
network traffic between the Foxboro DCS Control Network and Nodebus networks
using ATSs. However, you need to make certain that stations that migrate to the
control network and continue to communicate with stations on the Nodebus adhere to
their original Nodebus communication limits. When the Nodebus is involved in the
transfer of large amounts of data, the Nodebus rules still apply. Normally, if the data
transfer starts to exceed 1.2 MB, control stations could island and hot remarry.
Copying large streams of data from a Nodebus through an ATS to the control network
is not recommended. Avoid using the Nodebus for large data transfers; use a
separate network instead.
B0700TL, Rev B 77
Control Core Services v9.6 Release Notes Chapter 7: v9.6 User Notes
Chapter 7: v9.6 User Notes

Installing Software
New User Accounts on Local Edition System Installation
During a Local Edition system installation, one new user account (Local Engineering)
is created which is the default user account for executing Control Core Services
software. It is possible, at installation time, to set
this user account for auto-logon. There is also an existing account (Account1) which
will remain on the workstation after the installation is completed. During installation,
the password must be set for Account1. Beginning with CCS v9.5 and later,
Account1 can no longer be used to operate Local Edition workstations. Users should
always log in with the Local Engineering User Account (created at install time) to
operate a Local Edition workstation.
During an Enterprise Edition domain client installation, the Account1 password must
be set. No other local accounts are created. In order to operate the Enterprise Edition
domain client, log in with one of the domain users created on the Foxboro DCS
Control Core Services domain controller workstation.
These guidelines should always be followed regarding user accounts on the Foxboro
DCS.
• Always set the Account1 passwords differently on the Local Edition workstations
and the Enterprise Edition domain client workstations.
• Always set the Account1 password and the Local Engineering User Account
password differently on each Local Edition workstation.
• Always set the Local Engineering User Account user name and password to the
same value on all Local Edition workstations to maintain compatibility between
Local Edition stations.
For more information on setting local account user names and passwords, see
Foxboro DCS Control Core Services Installation Guide (B0700TK).
Dialog Box Shown When Saving Screen Capture with HyperSnap 8

for the First Time
The first time logging onto a CCS v9.6 workstation with any user, the directory for
saving files with the HyperSnap 8 application is not set. On the first screen capture, it
is necessary to perform a Save As operation and navigate to a folder where the
snapshots will be stored. Alternatively, a normal Save operation will result in a dialog
with the message Error Saving File. Subsequent logins do not require the Save As to
be performed.
Foxboro Classic Software Support

Starting with Control Core Services v9.5 or later, Foxboro Classic Software Support
v1.0 provides the media for installing OpenText Exceed. This media is now purchased
separately from CCS and installed separately. Foxboro Classic Software Support v1.0
is only required if the workstation will be making use of at least one of these
applications: ICC, PLB Monitor, PLB Editor, or Operator Action Journal. This software
is licensed on a per-workstation basis, so if the software is only required on certain
workstation in a system, then only those workstations will require a license. Also, if a
workstation is being updated from CCS v9.4, then it is not necessary to purchase the
license for Exceed since it was included with CCS v9.4.
78 B0700TL, Rev B
Chapter 7: v9.6 User Notes Control Core Services v9.6 Release Notes
NOTE: Install the “Foxboro Classic Software Support” media to use ICC, Operator
Action Journal, PLB Monitor, or PLB Editor. If you already have Control Core
Services v9.4, then upgrade to Control Core Services v9.6 to use the features.
Workstations with Windows Operating System

Printer Monitor System Message in SMON Indicates Normal
Operation
The Printer Monitor process (PrnMon) monitors a network printer and periodically
polls the status of printer in every 30 seconds. Occasionally the network printer might
not respond to the poll and PrnMon sends this report to the System Monitor (SMON)
for the printer: Warning Condition Exist With Critical Alerts.
On the next cycle polling, the printer will respond to the query from PrnMon. SMON
will generate this message for the printer: Online And Available. These messages
can appear in the smon_log, but they do not indicate any harm to the system.
User Cannot Perform Checkpoint Even After Removing Database

Locks
During normal operation when the checkpoint server is running, it creates a file
“sm_chk_sync” in the folder d:\usr\fox\sysmgm\softmgr\file. When it
completes, it removes the file before it terminates. There is a possibility that, if a
previous checkpoint action aborted abnormally, it might not remove the file. As a
result, the operator would no longer be able to checkpoint any stations successfully.
If you run into this situation, you can either reboot workstation which will remove all
files with the prefix “sm_*” in the folder d:\usr\fox\sysmgm\softmgr\file, or
manually delete the file “sm_chk_sync” in the folder.
User Access to Shared Folders Between Workstations with

Windows 10 or Windows Server 2016 and Workstations with
Windows XP or Windows Server 2003
Share access between workstations with Windows XP or Windows Server 2003, and
Windows 10 or Windows Server 2016 using the \\<machinename> or \\<ipaddress>
syntax results in the system message:
The specified network name is no longer available.
This behavior is due to SMB1 feature being turned off by default in Windows 10.
When the SMB1 feature is turned on, the share access between workstations with
Windows XP and Windows 10 works.
NOTE: Microsoft and Schneider Electric do not recommend SMB1 protocol to be
used due to its known security vulnerabilities. Enabling this feature is not
recommended.
B0700TL, Rev B 79
Enabling SMB1 Features

1. Open PowerShell in admin mode (Run as Admin).
2. Execute the command:
Enable-WindowsOptionalFeature -Online -FeatureName
SMB1Protocol
3. The workstation asks for a reboot. Once the reboot is complete, verify that SMB1
is turned on by executing the command in PowerShell (in Admin mode):
Get-WindowsOptionalFeature –Online –FeatureName
SMB1Protocol
Now share access between workstations with Windows XP or Windows Server
2003 and Windows 10 or Windows Server 2016 works correctly.
By default, SMB1 is not enabled on Control Core Services v9.6 Windows 10 or
Windows Server 2016 workstations. SMB1 was enabled on CCS v9.4 Windows
10 workstations. A Windows 10 workstation which is upgraded from CCS v9.4 to
CCS v9.6 continues to have SMB1 enabled. It is highly recommended to turn off
SMB1 support on all CCS v9.6 Windows 10 workstations which have been
updated from CCS v9.4.
User Access Shared Folders from an Insecure Network File Device

After application of the Schneider Electric-supplied Local Group Policy on a V91 host,
the security environment on the V91 host restricts the access of untrusted network
devices, such as network file servers, to help protect against potential vulnerabilities.
If you need to access these untrusted network drives, you can enable access using
this procedure.
1. On the V91 host, login as a user with administrator privileges.
2. Right-click the Windows menu and select Run.
3. Type gpedit.msc and click OK.
4. In the User Access Control dialog box which appears, click Yes to open the
Local Group Policy Editor.
5. Navigate to Computer Configuration > Windows Settings > Security Settings
> Local Policies > Security Options node.
6. On the right-hand side, double-click the Microsoft network client: Digitally sign
communication (Always) setting and select Disabled. Click OK.
7. Navigate to Computer Configuration > Administrative Templates > Network
> Lanman Workstation node.
8. On the right-hand side, double-click the Enable insecure guest logons setting,
and select Enabled. Click OK.
9. Close the Local Group Policy Editor.
10. Right-click the Windows menu and select Command Prompt (Admin). In the
User Access Control dialog box which appears, click Yes.
80 B0700TL, Rev B
11. Type gpupdate /force and press Enter.

At this point, the network drive should be accessible.
NOTE: After using the network drive, it is recommended to reset the two
settings to their original values to return V91 security back to its original state.
These are the factory settings:
• Computer Configuration > Windows Settings > Security Settings >
Local Policies > Security Options
Microsoft network client: Digitally sign communication (Always) -
Enabled
• Computer Configuration > Administrative Templates > Network >
Lanman Workstation - Enable insecure guest logons - Disabled
Potential Detected Startup Condition on Control Core Services

Workstations After a Detected Power Failure
Occasionally after power becomes unavailable to Control Core Services workstations
running Control Core Services v9.4–v9.6, a detected issue occurs. On system startup
after the power becomes unavailable, the system might be affected by this behavior if
the Control Core Services splash screen indicates One or more tasks failed to start.
STARTUP ABORTED!
If this occurs:
1. Open the settings for the network adapters from the Control Panel > Network
and Sharing Center. Click Change Adapter Settings.
2. Select View > Details.
3. Check the Status of the “REDL Virtual Miniport Driver” and the Control Network
Physical NICs. All adapters for the Control Network should be enabled. If they are
disabled as shown below, they need to be re-enabled before the workstation can
be restarted. If all the adapters are enabled, the restoration procedure provided in
this user note is not applicable to your situation.
B0700TL, Rev B 81
4. Enable each of the physical NIC adapters by right-clicking on the entry in the list
and selecting Enable.
5. Then enable the REDL Virtual Miniport Adapter by right-clicking on the entry in
the list and selecting Enable.
82 B0700TL, Rev B
6. At this point, all adapters will be in the Enabled state. Note the status of the Off-
Control Network NIC adapter statuses. If these adapters are not enabled, verify
the expected status and set them as required for your system setup.
7. Restart the workstation.
Applications
FoxDraw
Zoom Out Option
In FoxDraw, the “zoom out” option does not work as designed when used with
widescreen format display files (wsmfdf) on a standard definition (4:3 aspect ratio)
monitor.
Due to the aspect ratio difference between the standard definition monitors and
display file, the “zoom out” option for a widescreen format display file on a standard
definition does not zoom out the display to the center of the screen.
Opening Legacy Display for a Widescreen

In FoxDraw, when opening a legacy (.fdf at 4:3 aspect ratio) display for a widescreen
(16:9 aspect ratio) monitor, a dialog box might appear, stating, Do you wish to
convert the display to Widescreen format? Moving this dialog box around the
screen leaves trails and obscures the background. This might also occur for the dialog
box that states, Opening a Display Configured in Widescreen Will be Read Only,
which opens when a widescreen (wsmfdf) display on a standard definition (4:3 aspect
ratio) monitor is opened. These trails might not disappear when the dialog boxes are
closed. We recommend that you do not move these dialog boxes when they appear.
B0700TL, Rev B 83
Device Monitor
Device Monitor Master Active on Isolated Segments of Foxboro
DCS Control Network
QF1302638 for Device Monitor is not released and is not required. Prior versions of
Device Monitor running on I/A Series v8.8 and Control Core Services v9.0 through
v9.2 are fully compatible with the version of Device Monitor running on CCS v9.3 and
above. In the absence of a suitable v9.3 workstation, there will be no loss of
functionality if Device Monitor takes over from another, lower versioned workstation.
The following issue persists on this and earlier versions of Device Monitor running on
Control Core Services.
If a network isolation has occurred where a station or multiple stations become
isolated from the rest of the control network, a Device Monitor Master station might
become active on the isolated portion of the network. When the network isolation is
resolved, the Device Monitor Master stations recognizes that there is more than one
Master station and the Master station with the highest version will take over. When this
happens, the Master station that takes over might not re-read the statuses of each of
the stations on the network (included the portion of the network which had been
isolated). The result of this scenario is that the Device Monitor Master station might
not have the latest up-to-date status of alarm destinations on that portion of the
network. A symptom of this is that alarms might not be delivered to those stations
even though they are online.
Issuing a Command to Force Device Monitor to Re-read Network Statuses

Another symptom of the Device Monitor showing an incorrect status can be control
processor slowdown due to the CPs trying to send alarms to destinations which are in
the “failed” state.
To fix this condition, issue a command to force Device Monitor to re-read the statuses
on the network.
The command can be issued from any station on the network which is visible to the
Device Monitor Master station.
1. Open a command prompt (cmd.exe).
2. Type this command and then press Enter: D:\usr\fox\cs\dm_recon
Retrieving a List of Each Alarm Destination Statuses

It is also possible to retrieve a list of each of the alarm destination statuses that Device
Monitor currently has:
1. Open a command prompt (cmd.exe).
2. Type this command and then press Enter: D:\usr\fox\cs\dm_recon d.
The status will be stored on the Device Monitor Master workstation in the file: D:
\usr\fox\cs\cs_dm.current
84 B0700TL, Rev B
NOTE: It is inadvisable to boot up a workstation while disconnected from the

Foxboro DCS Control Network and then connected to this network. When a
workstation is booted up offline, it assumes Device Monitor Mastership and
when connected to the control network, it causes a conflict with the existing
Device Monitor Master. This could result in the unavailability of alarms or
control processor slowdown. In addition, connecting a workstation to the
control network which was booted up offline will also cause a conflict with the
Master Timekeeper which might result in a time jump or other system
instability.
Control Processors
I/O Load (Fieldbus Scan Load) Increase Due to Unavailable or
Disconnected Fieldbus Channel
Be advised that an unavailable or disconnected fieldbus channel might actually
increase the I/O load (Fieldbus Scan Load). This is one of the reasons it is strongly
recommended that you apply an appropriate reserve. This is especially vital for the
FCP280 with the four HDLC fieldbus ports. If one heavily loaded channel is
disconnected from the FCP280’s baseplate, this causes an increased load and an
impact on the three HDLC fieldbus ports still in operation. The extra I/O load caused
by a disconnected or unavailable port depends on the FBM types, but can be as much
as 25% on systems using simple I/O modules. On systems with 200 Series DCI-type
FBMs (Foundation Fieldbus, HART, PROFIBUS, DeviceNet, Modbus, ISCM and
FDSI) the difference in load when an I/O cable is disconnected can be much higher,
possibly causing FCP280 overruns. To avoid these situations during system
maintenance, the corresponding CP channel can be set to off-line from the System
Manager or SMDH before its fieldbus cable is disconnected from the FCP280
baseplate.
Removing Married FCP280s From Their Baseplate

Before removing either member of a married fault-tolerant pair of FCP280s from their
baseplate, set that FCP280 to “Offline” in the System Manager.
1. Locate the FCP280 you want to take off-line in the System Manager.
2. Right-click the FCP280 and choose Offline Diagnostics from the context menu.
The Offline Diagnostics dialog box displays the current status of each FCP280
in the fault-tolerant pair and prompts you to select the FCP280 to take off-line
B0700TL, Rev B 85
3. Type an entry in the Reason field if the field is included in the dialog box.
4. Select the FCP280 to be taken off-line and click OK. The selected module goes
off-line, and its status changes to Diagnostics Active. The status of the other
module changes to Single Primary.
For more information about offline diagnostics, see System Manager User’s
Guide (B0750AP).
86 B0700TL, Rev B
Chapter 8: Customer Cases Resolved in v9.6 Control Core Services v9.6 Release Notes
Chapter 8: Customer Cases Resolved in v9.6

CAR Number Description Subsystem
52314758 Application Objects of type STRING created and initialized. Control Core Services
When AOS tools are used to retrieve the string value, it is
correctly retrieved.
When omget is used to retrieve the A:O.A value, the last character
is truncated from the string.
57626434 A station reboot (H92 Z440) can take between 5 and 30 minutes. Hardware Advisory
During this time a restarting screen is visible. Also the system
monitor log is filled with Device Monitor messages during that
time.
This is a different change than the one provided for 67938149
though the symptoms reported are similar.
64195983 On Veritas backup server (Gen 9 with Microsoft Windows Hardware Advisory
Server2016, Veritas 16 and CCS 9.4), the backup size is
increased above the normal.
For example: The size of the D:\ drive is 4 GB and the backup
folder is 20 GB.
65673729 Control HMI has error window popped up during the opening. Workstation software
Title of Windows:
Alarm Server.exe – System Error
Message of Windows:
The program can’t start because ICCRegistry.dll is
missing from your computer. Try reinstalling the
program to fix this problem.
From the Control HMI, the Alarm Button was showing cyan.
However, the Alarm Server.exe was running in the Services upon
checking.
66722087 During a workstation shutdown, the Device Monitor process would Workstation software
restart multiple times, causing system-wide network issues. Also,
67938149 during this time, the System Monitor log (smon_log) is filled up
with Device Monitor messages. Cyan fields may also be observed
in operator displays.
This is a different change than the one provided for 57626434
though the symptoms reported are similar.
66889697 CCS v9.5 Re-committal fail on both H90 and H92. Software Install
H90 gives this error:
The wizard was interrupted before Foxboro DCS
Control Core services could be completely
installed. your system has not been modified. To
complete installation at another time, please run
setup again.
69715012 On a system installed with October 2019 Microsoft security Workstation software
patches or later, CCS 9.4/CCS 9.5 installation will fail with an error
“MESH Configurator error.” CCS 9.4/CCS 9.5 must be
installed prior to installing the October 2019 patches or later.
B0700TL, Rev B 87
Control Core Services v9.6 Release Notes Chapter 8: Customer Cases Resolved in v9.6

69949628 On a System Installed with the October 2019 Microsoft security Workstation software
patches or later, it is not possible to re-bind the Control Network
NICs. While attempting to bind the NICs with the Control Network
Configurator utility, the operation will fail with the message “MESH
Configurator error.”
Internal If a newer x86 Visual C++ Runtime library is installed prior to CCS Workstation software
Reference v9.5 does not add the Visual C++ x64 runtime libraries during the
495109 CCS v9.5 installation. If a newer x64 Visual C++ Runtime library is
installed prior to CCS v9.5 fails during installation of Visual C++
x64 runtime libraries during the CCS v9.5 installation.
Internal In some Day 1 installation scenarios, the user may receive an Software Install
Reference error message at the beginning of the installation – “Please
497924 insert Disk 1”. The install cannot proceed.
70529839 After “Enabling Alarm” is selected in System Manager for a Workstation software
previously inhibited station, the entry from the d:\usr\fox
\sysmgm\sysmon\inhibited.txt has not be removed.
Upon reboot of the SMON host, all those stations will be Inhibited.
64197842 User cannot add more than 13 modules for a GSD in the Profibus Workstation software
Configurator for FBM222. A fix is needed for CCS 9.4/9.5
platform.
68257140 All the H90 GEN 10 servers at the site are showing as Degraded Workstation software
for the Cooling Redundant State in System Manager as attached
although 2 CPUs are installed with 6 FANs.
59736264 In ICC/ PLB ladder logic editor, the description for Rung 1 is not FoxView Detail Displays
visible. In FoxView ladder logic detail display, the rung description
for Rung 1 is visible breaking the connect up/dn lines.
• Create a PLB block
• Edit ladder logic
• Create a rung (e.g. rung 1)
• Add rung description
• Create another rung (i.e. rung 2)
• Add rung description
• Create a connect dn/up connection between rungs 1 and 2
55208207 An Integer value cannot be set to minimum signed integer value of Control Core Services
-2147483648 in a strategy of $IND type block in HLBL editor. This
value causes a memory violation.
66077314 When looking at equipment information in System Manager the Workstation software
Server Model field for the DL380 Gen 10 server shows up as "Not
Applicable".
For reference the Gen. 9 server showed up as "ProLiant DL380
Gen9".
Internal PAKIN/PAKOUT blocks are missing if the import alias list is not in Control Core Services
Reference order.
456539
The attached tagnames.txt file should create 8 PAKIN and 8
PAKOUT blocks instead of 6 PAKIN and 6 PAKOUT blocks.
63578641 In IACC, XD_SCALE, UNIT_INDEX, OUT_SCALE, and Workstation software
CHANNEL parameter values setting to ‘0’ while downloading to
65360365 the AI block. For some blocks W73-FF FUNCTION BLOCK
CONFIGURATION ERROR is coming. These parameters can
only be changed through FDM and not by the AI block. If we
88 B0700TL, Rev B
Chapter 8: Customer Cases Resolved in v9.6 Control Core Services v9.6 Release Notes

change scale and unit through HART Communicator from field
then range and units are getting update in Block detail display
after power reset of transmitter again issue remains same.
40160810 FoxPanels does not start up correctly and experiences Workstation software
intermittent issues sounding horns after a reboot.
63861626 Alarm Manager exits unexpectedly when refreshing the CAD after Workstation software
attempting to quit a non-quittable Alarm Manager.
59299704 User cannot add more than 13 modules for a GSD in the Profibus Workstation software
Configurator for FBM222.
Internal FDC280 ICC Companion Configurator does not show the TSAA Workstation software
Reference driver name.
436445
67761926 Via FoxView detailed display you are not able to enter up to 80 FoxView Detail Displays
characters for DEP, EXC and IND sequence blocks Restricted to
enter and show up to 71 characters. Issue reported for FoxView
10.4.1.
Internal FoxView FF AO.CAS_IN value is not dynamically updating when FoxView Detail Displays
Reference ramping values < 1.00
477498
67609188 During the BASF PO upgrade project in 2018, all control and Control Processor
display links were modified from AO.PV to AO.BCALCO (AO Firmware
being the FF block). This because of a change in CP image
71149737 Remote users, using published means of restricting the desktop, Workstation software
do not have audible alarms. Audible alarms are only present when
the FoxPanels application is running in the remote session. See
latest revision of B0700HM for instructions on using the new
ia_logon_foxpanels.cmd for remote logons. The new script is
included with CCS v9.6.
73445523 The System Monitor became not available when the user selects Workstation software
action “Acknowledge System Monitor Domain” on the System
Manager. The configuration that the customer uses is to set the
destination for all the events messages with both high and low
priority to the printer, historian and the system event. While in the
common configuration only those high priority event messages
are set to the printer and historian and the system event.
54281956 Alarms set up from 2 compounds around same time cause the Workstation software
USB Alarm Printer stop printing.
39922615 Control Network NTP clients need to be configured only to Workstation software
respond to Control Network Master Time on the Control Network
IP Subnet (151.128). Problems have been observed when the
time is provided on another IP Subnet. Currently all Control
Network workstations except the MTK and BMTK are configured
as NTP broadcast (bcast) clients. When these Control Network
workstations are connected to a second network, it is possible
that they could start receiving time from a different source besides
the MTK. This could create time problems in the system.
Internal On a system configured to use an off-Control Network NTP server Workstation software
Reference as its time source. After a weekend power outage, the time
463049 reported by the off-Control Network NTP server jumped
backwards an hour from time on the Control Network. This time
jump caused the NTP daemon on the MTK to panic-stop (a time
jump of greater than 1000 secs will cause a panic stop). This
caused the timekeeper on the primary to enter a cycle where the
MTK was continually restarting NTP after the panic stops. After
B0700TL, Rev B 89
Control Core Services v9.6 Release Notes Chapter 8: Customer Cases Resolved in v9.6

correcting the time on the off-Control Network NTP server, the
MTK recovered and resumed the master role. However, the
legacy thread on the MTK remained in a suspend state so the 10-
minute TimeAt message was not being transmitted.
Internal Following a 2-day power outage, the time on the off-Control Workstation software
Reference Network NTP server was 2 days behind actual time when it
463050 booted up. The Primary timekeeper workstation was configured to
reject times that was greater than 15 hours from current mesh
time. The Primary station detected the out-of-range (OOR)
condition and entered its error loop, but local time on the Primary
was still set to the OOR time.
60631152 Windows 10 stations do not support GPS Time Sync cards. Hardware Advisory
50389423 Setting the IRIG-B to 1 hour ahead caused NTP to step time on Workstation software
the standalone MTK workstation.
50389423 When a Windows shutdown / Fast startup is performed the TSync Workstation software
GPS card gets reset and starts reporting the year as 2000. If an
IRIG-B time source is being used, the year never gets corrected
(because the IRIG-B signal does not contain the year). The
timekeeper flags this as invalid time and will not resume normal
processing.
50389423 The TSYNC card of the MTK workstation year was set to the Workstation software
value of "2000". It should be 2019.
The bad year was displayed in the HPSTK.log when the work
station was started after a FVFD shutdown.
50389423 Bad IP addresses in tk.cfg cause hpstk crashes. Workstation software
50389423 The Windows 10 fast startup option is preventing the GPS card Workstation software
from operating normally on power-up.
41763433 Spectracom card frequently returning zeros for Year, Month, and Hardware Advisory
Day.
1319573 When the GPS antenna lost sync with satellites time jumped to Hardware Advisory
August 5, 2016.
1334057 Other cases involving time jump issues on the Control Network. Workstation software
1307599
1309363
1308662
1305907
1309677
1316000
81017322 Under certain conditions, particularly on workstations monitoring System Monitor
switches, there can be an issue with System Monitor experiencing
82949642 excessive System Monitor log (smon_log) messages, which can
eventually cause the loss of process alarms.
73445523 The System Monitor became not available when the user selects System Monitor
action “Acknowledge System Monitor Domain” on the System
Manager. The configuration that the customer uses is to set the
destination for all the events messages with both high and low
priority to the printer, historian and the system event. While In the
common configuration only those high priority event messages
are set to the printer and Historian and the system event.
90 B0700TL, Rev B
Appendix A: EEPROM Revision Levels Control Core Services v9.6 Release Notes
Appendix A: EEPROM Revision Levels

NOTE: On the GCS website, visit FAQ1522 to acquire the latest images: https://
pasupport.schneider-electric.com/km/index?page=content&id=FAQ1522
Image Revision Levels for Control Stations and ATS with

Control Core Services v9.6
This table lists the control station and ATS EEPROM revision levels that have
changed for this release.
Table 15 - Control Core Services v9.6 Control Station and ATS EEPROM/Image and Software Revision Levels
Software Revision Level

Station
Description Mnemonic V8.8 V9.0 V9.1 V9.2 V9.3 V9.4 v9.5 v9.6
Field Control FCP280 N/A 09002- 09002- 09100- 092012 092017 092032 093007
Processor 280 2 2 1
Control Network CNI N/A N/A N/A 09206- 093040 093042 094009 094009
Interface 5
Field Device FDC280 N/A N/A N/A N/A 090000- 090001- 090100- 090100-
Controller 280 9000 0000 3000 4000
Z-Module Control ZCP270 88000- 90000- 90001- 90003- 920040 920053 920057 920061
Processor 270 9 4 8 5
Field Control FCP270 88000- 90000- 90001- 90003- 920040 920053 920057 920061
Processor 270 9 4 8 5
Address ATS 88000- 90000- 90001- 90003- 920030 920053 920053 920053
Translation 9 4 8 5
Station
This table lists the legacy station software and EEPROM revision levels supported for
this release of the Control Core Services.
Table 16 - Control Core Services v9.6 Legacy Station EEPROM/Image and Software Revision Levels
EEPROM
Station Image Software Revision I/A Series
Description Mnemonic Name Version Level Release
Allen-Bradley Integrator 30 AB30B OS1A3B(a) 6.1.10 3.32 6.5.6
Style B
Control Processor 30 Style B CP30B OS1C3B 6.1.10 3.30 6.5.6
Control Processor 40 Style B CP40B OS1C4B QF1012278 3.30 9.3
Control Processor 60 CP60 OS1C60 QF1166819 3.30 9.1
Device Integrator 30B DI30B OS1FDB 6.5.6 3.32 7.1
(b)
Modbus Integrator 30 Style B MG30B OS1M3B 6.1.10 3.32 6.5.6

(c)
Communication Processor 10 COMM10 OS1CS 6.5.1 2.20 7.1

Triconex ACM (FoxGuard TACM OS1ACM 6.2.10 4.2.2 6.5.5
Manager)
B0700TL, Rev B 91
Control Core Services v9.6 Release Notes Appendix A: EEPROM Revision Levels
Table 16 - Control Core Services v9.6 Legacy Station EEPROM/Image and Software Revision Levels
(Continued)
EEPROM
Station Image Software Revision I/A Series
Description Mnemonic Name Version Level Release
Control Processor 30 Style A CP30 OS1C30 6.1.7 3.30 6.5.4
Control Processor 40 Style A CP40 OC1C40 6.1.7 3.30 6.5.4
(a) For the Allen-Bradley Integrator 30 Style B, the OS1A3B package includes two files: OS1A3B and
OS1A3B.186.
(b) For the Device Integrator 30B, the OS1FDB package includes two files: [*].386 and [*].186. The names of these
files are dependent on the driver interface used.
(c) For the Modbus Integrator 30 Style B, the OS1M3B package includes two files: OS1M3B and OS1M3B.186.
100 Series FBM Software and EEPROM Versions

The table lists 100 Series FBMs and their software versions. Software versions and
EEPROM revision levels for 100 Series FBMs and associated modules are displayed
in the System Management Equipment Information display:
SOFTWARE REV: <Software Version>

EEPROM REV: <EEPROM Version>
In this table, dashes indicate that the revision is unchanged from the previous release.
“N/A” indicates that the station or module is not available for that Control Core
Services or I/A Series software release.
92 B0700TL, Rev B
Table 17 - Software Versions of 100 Series FBMs (Y Form Factor)
EEPROM
Software Version Version
V8.6- V9.0-
Devices Using IOM ID V8.4.2 V8.4.3 V8.5 V8.6 V8.7-8.8 V9.0 8.8 V9.6
FBM01, FBM02, IOM01 42.4 – – – – – 61.1 61.1
FBM03, FBM03A,
FBM03B, FBM19,
FBM33, FBM33A,
FBM33B, FBM36,
BAMM01, BASM02,
BASM03, BASM33,
F1M01A, F1M01C,
F1M01E, F1M01F,
F1M02, F1M03A,
F1M03C, H2C02A,
H2C02B, H2C02D
through H, H2C02J
through N, H2C02P
through Z, H2D02A
through E, H2D02G,
H2D02H, H2J02A
through H, H2M01A
through D, H2M02,
H2M02A, H2M02B,
H2M02E, H2M03,
H2M03A through G,
H2V02B through H,
H2V02J, H2V02L
through N, H2V02P
through R, H2X02A
through H
FBM04, FBM05, IOM02 80.1 – – – – – 61.1 61.1
F1M04A, F1M04B,
H2M04
H2C02A, H2C02B, IOM03 42.2 – – – – – 61.1 61.1
H2C02F, H2C02G,
H2C02J, H2C02K,
H2C02P, H2C02Q,
H2C02S, H2C02T,
H2C02X, H2C02Y,
H2D02A through E,
H2D02G, H2D02H,
H2J02A, H2J02B,
H2J02F, H2J02G,
H2M01A, H2M02,
H2M02A, H2M02B,
H2M02E, H2M03A,
H2M03B, H2M03F,
H2M03G, H2V02B
through H, H2V02J,
H2V02L through N,
H2V02P through R,
H2X02A through H,
H3M03
FBM06, F1M06, IOM04 80.1 – – – – – 61.1 61.1
H2M06, H2M06A,
H3M06
B0700TL, Rev B 93
Table 17 - Software Versions of 100 Series FBMs (Y Form Factor) (Continued)
EEPROM
V8.6- V9.0-
FBM07, FBM07A, IOM05 80.1 – – – – – 61.1 61.1
FBM07B, FBM08,
FBM09, FBM09A
through D, FBM10,
FBM11, FBM12,
FBM12A, FBM12B,
FBM13, FBM14,
FBM14A through D,
FBM15, FBM16,
FBM20, FBM21,
FBM24, FBM24A
through C, FBM25,
FBM25A through C,
FBM26, FBM26A
through C, FBM27,
FBM27A through C,
FBM41, FBM41A,
FBM41C, FBM42,
FBM42A, FBM42C,
BDSI07, F1M07,
BDSM09, BDSM9A,
BDSM9B, F1M09,
BDSO10, BDSO26,
BDSO41, H2M07,
H2M07E, H2M09,
H2M24, H2M26,
H3M07, H3M09
<SOE> BSEM01, IOM06 42.1 – – – – – 61.1 61.1
FBM07A, FBM07B,
FBM08, FBM12A,
FBM12B, FBM13,
FBM20, FBM21,
FBM24, FBM24A
through C, FBM25,
FBM25A through C,
F1M07, H2M24,
H3M07
<PULSE> FBM07A, IOM07 41.1 – – – – – 61.1 61.1
FBM07B, FBM08,
FBM12A, FBM12B,
FBM13, FBM20,
FBM21, FBM24,
FBM24A through C,
FBM25, FBM25A
through C, F1M07,
H2M24, H3M07
<LADDER> FBM07A, IOM08 80.2 – – – – – 61.1 61.1
FBM07B, FBM08,
FBM09A through D,
FBM10, FBM11,
FBM12A, FBM12B,
FBM13, FBM14A
through D, FBM15,
FBM16, FBM20,
FBM21, FBM24,
94 B0700TL, Rev B
EEPROM
V8.6- V9.0-
FBM24A through C,
FBM25, FBM25A
through C, FBM26,
FBM26A through C,
FBM27, FBM27A
through C, FBM41,
FBM41A, FBM41C,
FBM42, FBM42A,
FBM42C, BDSO10,
BDSO26, BDSO41,
F1M07, H2M24,
H2M26, H3M07,
H3M09
FBM17, FBM17A IOM09 80.1 – – – – – 61.1 61.1
through D, FBM22,
H2M17
FBM18, FBM43 IOM12 84.1 – – 84.3 84.3 84.3 61.1 61.1
<HTG> FBM23(a) IOM13 40.2 – – – – – 40.1 40.1
Panel Display Station IOM14 80.1 – – – – – 61.1 61.1
FBM38 IOM22 40.4 – – – – – 61.1 61.1
FBM39, FBM44 IOM23 84.1 – – 84.3 84.3 84.3 61.1 61.1
<MDACT> FBM17, IOM34 80.1 – – – – – 61.1 61.1
FBM17A through D,
H2M17
<MDPUL> FBM17, IOM36 80.1 – – – – – 61.1 61.1
FBM17A through D,
H2M17
FBM43 IOM37 84.1 – – 84.3 84.3 84.3 61.1 61.1
<Multibaud> FBM39, IOM38 84.1 – – 84.3 84.3 84.3 61.1 61.1
FBM44
<Gas IOM39 40.1 – – – – – 42.2 42.2
Chromatograph>
FBM45
FBP10 IOM42 6.3.2 – – – 8.4.4 8.4.4 8.4.4 8.4.4
FBP11 (SMI, UCM) IOM43 6.3.2 – 8.4.2 8.4.2 8.4.2 8.4.2 8.4.2 8.4.2
FBP12 (FIO) IOM44 6.3.2 – 8.4.2 8.4.2 8.4.2 8.4.2 8.4.2 8.4.2
FBP13 (UFM) IOM45 6.3.2 – 8.4.2 8.4.2 8.4.2 8.4.2 8.4.2 8.4.2
FBP14 (UIO) IOM46 6.3.2 – 8.4.2 8.4.2 8.4.2 8.4.2 8.4.2 8.4.2
FBP10R IOM47 6.3.2 – 6.3.2 6.3.2 8.4.4 8.4.4 8.4.4 8.4.4
FBP11R IOM48 6.3.2 – 8.4.2 8.4.2 8.4.2 8.4.2 8.4.2 8.4.2
FBM46 IOM49 84.1 – – 84.3 84.3 84.3 61.1 61.1
<PID> FBM04, IOM52 80.1 – – – – – 61.1 61.1
FBM17, FBM17A
B0700TL, Rev B 95
EEPROM
V8.6- V9.0-
through D, FBM22,
H2M17
FBM37, BAOM37, IOM53 80.1 – – – – – 61.1 61.1
H3M37
H3M01 IOM54 4.21.0- – – – – – 4.21.- 4.21.0-
5.03 05.03 5.03
BASI03, BDSM06 IOM55 5.06.0- 5.06.11.- – – – 5.06.1- 5.06.- 5.06.1-
9.03 03 3.03 11.03 3.03
(BA- (BASI03) (BA- (BA- (BA-
SI03) 5.06.03.- SI03) SI03) SI03)
5.06.0- 03 5.06.0- 5.06.- 5.06.0-
3.03 (BSD- 3.03 03.03 3.03
(BSD- M06) (BSD- (BSD- (BSD-
M06) M06) M06) M06)
BASI01, BASM01, IOM56 4.21.0- 4.21.05.- – – – – 4.21.- 4.21.0-
BASO37 5.03 03 05.03 5.03
(BASI01, (BA- (BA-
BAS- SI01, SI01,
M01) BAS- BAS-
4.21.04.- M01) M01)
03 4.21.- 4.21.0-
(BA- 04.03 4.03
SO37) (BA- (BA-
SO37) SO37)
FRM701, FRM711, IOM57 4.21.0- – – – – – 4.21.- 4.21.0-
FRMMPU 7.03 07.03 7.03
F2M68A IOM58 4.21.0- – – – – – 4.21.- 4.21.0-
5.03 05.03 5.03
F2M67A IOM59 4.21.0- – – – – – 4.21.- 4.21.0-
6.03 06.03 6.03
<FoxCom> FBM43 IOM73 80.2 – – – – – 61.1 61.1
(a) Although FBM23 (HIU) IOM software is included with I/A Series software v8.5, the module’s configurator,
Intelligent Transmitter Maintenance Workbench (IT_Maint), is not supported. You must configure all FBM23s with
the handheld terminal FIU. See MI 020-065.
200 Series FBM Software and EEPROM Versions

The table lists 200 Series FBMs and their software versions. 200 Series FBMs and
communication modules have to be EEPROM updated if they are not at the current
revision level. Software and EEPROM revision levels for 200 Series FBMs and most
associated modules (except FCMs) are displayed in the System Management
Equipment Information display:
SOFTWARE <FBM> <Software Version> or <Software Version> <FBM>

REV:
EEPROM REV: ROM <Software Version>
96 B0700TL, Rev B
EEPROM revision levels for Fieldbus Communication Modules (FCMs) are indicated
in the SOFTWARE REV A and SOFTWARE REV B fields in the System Management
Equipment Information display.
NOTE: In the below tables, dashes indicate that the revision is unchanged from
the previous release. N/A indicates that the station or module is not available for
that Control Core Services or I/A Series software release.
Table 18 - Software Versions for 200 Series FBMs (DIN Rail Mounted Form Factor)
Software Version
Devices Using IOM ID V8.8 V9.0 V9.1 V9.2 V9.3 V9.4 V9.5 V9.6
FBM208 IOM80 1.40R 1.40V 1.40V 1.40V 1.40V 1.40V 1.40V 1.40V
FBM240 IOM81 1.40U 1.40U 1.41A 1.41A 1.41A 1.41A 1.41A 1.43J
FBI10E, FCM10E, IOM82 1.16 1.16 1.16 1.16 1.16 1.16 1.16 1.16
FBI10E, FCM10E,
FCM10Ef,
WFCM10E,
WFCM10Ef, DCM10E
FBM201, WAI01A IOM83 1.40R 1.40R 1.40R 1.40R 1.40R 1.40R 1.40R 1.40R
through D, WAW01A
through F, WAX01A
through C
FBM202, FBM202B, IOM84 1.40R 1.42 1.42 1.42 1.42 1.42 1.42 1.42
WAI02A, WAV02A,
WAX02A
FBM203, FBM203B, IOM85 1.40R 1.40R 1.40R 1.40R 1.40R 1.40R 1.40R 1.40R
FBM203C, WRF03A,
WRF03B, WRT03A,
WRT03B
FBM204, WLJ04A IOM86 1.40T 1.40T 1.40T 1.40T 1.40T 1.40T 1.40T 1.40T
through C
FBM205 IOM87 1.40R 1.40R 1.40R 1.40R 1.40R 1.40R 1.40R 1.40R
FBM206, WPA06A IOM88 1.40N 1.40N 1.40N 1.40N 1.40N 1.40N 1.40N 1.40N
FBM207, FBM207B, IOM89 1.40E 1.40E 1.40E 1.40E 1.40E 1.40E 1.40E 1.43H
FBM207C, WCI07A,
WDI01A through E,
WID07A through P
FBM211, WAH01A IOM90 1.40R 1.40R 1.40R 1.40R 1.40R 1.40R 1.40R 1.40R
through D
FBM212 IOM91 1.40R 1.40R 1.40R 1.40R 1.40R 1.40R 1.40R 1.40R
FBM213 IOM92 1.40R 1.40R 1.40R 1.40R 1.40R 1.40R 1.40R 1.40R
FBM237, WAO37A IOM93 1.40N 1.40N 1.40N 1.40N 1.40N 1.40N 1.40N 1.40N
through G
FBM241, FBM241B IOM94 1.40N 1.40N 1.40N 1.40N 1.40N 1.40N 1.40N 1.43H
through D
FBM242, WBO09A, IOM95 1.40N 1.40N 1.40N 1.40N 1.40N 1.40N 1.40N 1.43H
WBO09B, WRO09A
through D, WTO09A
FBM217 IOM96 1.40E 1.40E 1.40E 1.40E 1.40E 1.40E 1.40E 1.43H
FBM243, FBM246 IOM97 2.40N 2.46M 2.46M 2.46M 2.46M 2.46M 2.46M 2.46M
(FoxCom™)
B0700TL, Rev B 97
Table 18 - Software Versions for 200 Series FBMs (DIN Rail Mounted Form Factor) (Continued)
Software Version
FBM219 IOM98 1.40N 1.40N 1.40N 1.40N 1.41C 1.41C 1.41C 1.43H
FCM100Et IOM210 1.59 1.62 1.63 1.63 1.63 1.64 1.64 1.64
FCM100E IOM210- 2.06 2.08 2.08 2.08 2.08 2.08 2.08 2.08
E
FBM214 (HART) IOM214 2.46J 2.46J 2.47B 2.47B 2.50A 2.50A 2.50F 2.70I
FBM214E (HART) 16 IOM214- 2.70E
E
FBM215 (HART) IOM215 2.46J 2.46J 2.47B 2.47B 2.50A 2.50A 2.50F 2.50F
FBM216 (HART) IOM216 2.46J 2.46J 2.47B 2.47B 2.50A 2.50A 2.50F 2.50F
FBM218 (HART) IOM218 2.46J 2.46J 2.47B 2.47B 2.50A 2.50A 2.50H 2.50H
FBM220 (Foundation IOM220 2.20 2.20 2.20 2.20 2.20 2.20 2.20 2.20
fieldbus H1)
fieldbus H1)
FBM222 (Profibus- IOM222 2.12 2.15 2.15 2.15 2.15 2.16 2.19 2.19
DP)
FBM222 (Profibus- IOM222b NA NA NA NA NA 2.19 2.19 2.19
DP)
FBM223 (Profibus- IOM223 1.07 1.08 1.08 1.08 1.08 1.08 1.08 1.08
DP)
FBM224 (Modbus) IOM224 1.16 1.16 1.16 1.16 1.16 1.16 1.16 1.16
FBM227 IOM77 1.40U 1.40W 1.40W 1.40W 1.41B 1.41B 1.41B 1.41B
FBM228 (Redundant IOM128 6.15 6.19 6.19 6.21 6.23 6.27 6.27 6.28
Foundation Fieldbus
H1)
FBM228 (Redundant IOM128b 6.28
Foundation Fieldbus
H1)
Foundation Fieldbus
H1)
FBM229 (DeviceNet) IOM229 1.01 1.02 1.02 1.02 1.02 1.02 1.02 1.02
FBM230 (Simplex IOM230 1.34 1.35 1.35 1.35 1.36.3 1.36.4 1.36.5 1.36.5
Serial FDSI)
FBM231 (Redundant IOM231 1.34 1.35 1.35 1.35.1 1.36.3 1.36.4 1.36.5 1.36.5
Serial FDSI)
FBM232 (Simplex IOM232 1.34 1.35 1.35 1.35 1.36.3 1.36.4 1.36.5 1.36.5
Ethernet FDSI)
FBM233 (Redundant IOM233 1.34 1.35 1.35 1.35.1 1.36.3 1.36.4 1.36.5 1.36.5
Ethernet FDSI)
FBM234 (AEAM01) IOM234 1.25B 1.25B 1.25B 1.25B 1.25B 1.44 1.45 1.45
98 B0700TL, Rev B
Table 18 - Software Versions for 200 Series FBMs (DIN Rail Mounted Form Factor) (Continued)
Software Version
FBM235 (ASAM01) IOM235 1.25B 1.25B 1.25B 1.25B 1.25B 1.44 1.46 1.50A
FBM236 (ASDM24, IOM236 1.25B 1.25B 1.25B 1.25B 1.25B 1.44 1.45 1.45
ASDM48)
FBM238 IOM78 1.40N 1.40N 1.40N 1.40N 1.41C 1.41C 1.41C 1.43H
FBM239 IOM79 1.40N 1.40N 1.40N 1.40N 1.41C 1.41C 1.41C 1.43H
FBM244 IOM244 2.46J 2.46J 2.47B 2.47B 2.50A 2.50A 2.50F 2.50F
FBM245 IOM245 2.46J 2.46J 2.47B 2.47B 2.50A 2.50A 2.50H 2.70I
FBM247 IOM247 2.46J 2.46J 2.47B 2.47B 2.50A 2.50A 2.50G 2.70I
FBM248 IOM248 NA NA NA NA 2.70B 2.50E 2.50F 2.70I
FBM250 (ISCM) IOM250 2.40B 2.50H 2.50H 2.41C 2.41C 2.41C 2.41C 2.41C
Table 19 - EEPROM Revision Levels for 200 Series FBMs (only for modules where the EEPROM differs from
the Software Version)
EEPROM Revision Level

fieldbus H1)
fieldbus H1)
FBM222 (Profibus-DP) IOM222 1.10 1.10 1.10 1.10 1.10 1.10 1.10 1.10
FBM223 (Profibus-DP) IOM223 1.02 1.02 1.02 1.02 1.02 1.02 1.02 1.02
Foundation fieldbus H1)
Foundation fieldbus H1)
FBM229 (DeviceNet) IOM229 0.01 0.01 0.01 0.01 0.01 0.01 0.01 0.01
FBM230 (Simplex Serial IOM230 0114 0115 0115 0115 0115 0116 0116 0116
FDSI)
FBM231 (Redundant IOM231 0114 0115 0115 0115 0115 0116 0116 0116
Serial FDSI)
FBM232 (Simplex IOM232 0114 0115 0115 0115 0115 0116 0116 0116
Ethernet FDSI)
FBM233 (Redundant IOM233 0114 0115 0115 0115 0115 0116 0116 0116
Ethernet FDSI)
B0700TL, Rev B 99
Schneider Electric Systems USA, Inc.
70 Mechanic Street
Foxboro, Massachusetts 02035–2040
United States of America
Global Customer Support: https://pasupport.schneider-electric.com
As standards, specifications, and design change from time to time,

please ask for confirmation of the information given in this publication.
© 2022 Schneider Electric. All rights reserved.

B0700TL, Rev B

b0700tl B

Uploaded by

Copyright:

Available Formats

b0700tl B

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

b0700tl B

Uploaded by

Copyright:

Available Formats

Foxboro™ DCS

Control Core Services v9.6

Resolving Suboptimal Conditions During Software Installation .....................33

Running a Single Message Manager..........................................................59

Configuring Fail-Safe for Proper Operation of FBM218 ................................73

Important Safety Instructions

The addition of this symbol to a “Danger” or “Warning” safety message

Chapter 1 • Updated Domain Controllers, page 14 to indicate new

• Control Core Services v9.2 Release Notes (B0700ST)

• FBM212 – Differential Thermocouple/mV Input Interface Module (PSS 41H-

• FBM246/246b, FoxCom™ Redundant Dual Baud Rate, Intelligent Device

Schneider Electric Products Mentioned in this Document

Global Customer Support

We Welcome Your Comments

Chapter 1: Getting Started

Local Edition and Enterprise Edition Control Core Services

Operating System Image Installation

Control Core Services v9.6 Support for the Control Software

Compound Summary Access (CSA)

Installing CCS if Detail Displays Have Been Updated or Customized

3. As needed, reapply the edits to the newly installed files.

Maintain Up-to-Date Version of Adobe® Reader® for Foxboro

Foxboro DCS Product Rebranding

Table 1 - Foxboro DCS Product Rebranding

Product Name for Foxboro DCS

Chapter 2: Media for Control Core Services v9.6

v9.6 Media Kit

Table 2 - Control Core Services v9.6 Day 0 Media Kit (K0204BK-A)

Additional Required Media for CCS v9.6

Table 3 - Local Security Policy Settings Media

Part Number Description

Table 4 - McAfee Security Products Media

Part Number Description

Table 5 - Media to Upgrade from CCS v9.3 or Earlier

Part Number Description

Table 6 - System Recovery and Restore Media

Part Number Description

Table 6 - System Recovery and Restore Media (Continued)

Part Number Description

Additional Software Packages

Part Number Description

Part Number Description

Chapter 3: Features of Control Core Services v9.6

Chapter 4: v9.6 Compatibility Considerations

Site Upgrade Plans

ArchestrA and Microsoft Product Support for Control Core

ArchestrA (WSP 2014 Microsoft Product

ArchestrA (WSP 2014 Microsoft Product

Control Software Support for Control Core Services v9.6 or

Interoperability and Compatibility

I/A Series Software Control Core Services

I/A Series Software Control Core Services

I/A Series Software Control Core Services

I/A Series Software Control Core Services

I/A Series Software Control Core Services

AIM*API as a Replacement for FoxAPI

Nodebus to Control Network Interoperability and Compatibility

Control Core Services Interoperability and Compatibility

Active Directory Domain Compatibility