Control Core Services v9.4 Release Notes: Foxboro Evo Process Automation System

Foxboro Evo™
Process Automation System
Control Core Services v9.4

Release Notes
*B0700SY* *c*
B0700SY
Rev C
May 11, 2018
Schneider Electric, Foxboro, Invensys, Foxboro Evo, and TriStation are trademarks of Schneider Electric SE, its
subsidiaries, and affiliates.
All other trademarks are the property of their respective owners.
Copyright 2018 Schneider Electric.

All rights reserved.
SOFTWARE LICENSE AND COPYRIGHT INFORMATION

Before using the Schneider Electric Systems USA, Inc. supplied software supported by this docu-
mentation, read and understand the following information concerning copyrighted software.
1. The license provisions in the software license for your system govern your obligations
and usage rights to the software described in this documentation. If any portion of
those license provisions is violated, Schneider Electric Systems USA, Inc. will no lon-
ger provide you with support services and assumes no further responsibilities for your
system or its operation.
2. All software issued by Schneider Electric Systems USA, Inc. and copies of the software
that you are specifically permitted to make, are protected in accordance with Federal
copyright laws. It is illegal to make copies of any software media provided to you by
Schneider Electric Systems USA, Inc. for any purpose other than those purposes men-
tioned in the software license.
Contents
Tables..................................................................................................................................... ix
Safety Information ................................................................................................................. xi
Preface................................................................................................................................. xiii
1. Read Me First.................................................................................................................... 1
1.1 Overview of the Control Core Services v9.4 Release ............................................................ 1
1.1.1 Local Edition and Enterprise Edition Control Core Services ....................................... 1
1.2 Hardware Requirements ...................................................................................................... 1
1.3 Domain Controllers ............................................................................................................ 2
1.4 Operating System Image Installation ................................................................................... 2
1.5 Control Core Services V9.4 Support for the Control Software ............................................ 2
1.6 Site Upgrades ...................................................................................................................... 2
1.6.1 Migrating Files ............................................................................................................ 3
1.6.2 Compound Summary Access (CSA) ............................................................................ 3
1.7 Installation Overview .......................................................................................................... 3
1.8 Maintain Up-to-Date Version of Adobe® Reader® for Foxboro Evo Documentation ....... 4
1.9 Foxboro Evo Product Rebranding ....................................................................................... 4
2. Features of Control Core Services V9.4 Release................................................................. 5

2.1 Support for Windows 10 and Windows Server 2016 Operating Systems ............................ 5
2.2 Support for the Microsoft Windows Server 2016 Active Directory domains ....................... 5
2.3 Local Edition User Account Updates .................................................................................. 5
2.4 Enterprise Edition User Account Updates ........................................................................... 6
2.5 Additional Security Settings for Both Local Edition and Enterprise Edition
Domain Clients ......................................................................................................................... 6
3. V9.4 Compatibility Considerations ................................................................................... 7

3.1 Site Upgrade Plans .............................................................................................................. 7
3.2 Control Software Support for Control Core Services V9.4 or Later ..................................... 7
3.3 Interoperability and Compatibility ...................................................................................... 8
3.3.1 AIM*API as a Replacement for FoxAPI ..................................................................... 12
3.3.2 Nodebus to Control Network Interoperability and Compatibility ............................. 12
3.3.3 Control Core Services Interoperability and Compatibility ......................................... 13
3.4 Supported Operations ....................................................................................................... 15
iii
B0700SY – Rev C Contents
4. V9.4 Hardware Requirements ......................................................................................... 17
5. V9.4 System Setup .......................................................................................................... 19

5.1 V9.4 Documentation ........................................................................................................ 19
5.2 V9.4 Media ....................................................................................................................... 19
5.3 Additional Software Packages ............................................................................................ 21
6. V9.4 Operational Recommendations............................................................................... 25

6.1 Workstation/Server Shutdown When Installing Windows 10 Patches or
Security Updates ..................................................................................................................... 25
6.2 Migrating Existing Workstation or Server
with Windows 7 or Windows Server 2008 R2 ........................................................................ 25
6.3 System Configuration ....................................................................................................... 25
6.3.1 Blue Screen Resulting from COMM10 Ports Configured with Printers .................... 25
6.3.2 Self-Hosting or Auto-Checkpoint Host Limitations (CP270s or Later CPs) .............. 26
6.4 Software Installation .......................................................................................................... 26
6.4.1 Resolving Suboptimal Conditions During Software Installation ................................ 26
6.4.2 Performing a Day 1 Installation Procedure with Address Translation Station (ATS) . 26
6.4.3 Successfully Creating and Appending to a Reconcile Diskette ................................... 27
6.4.4 Installations with Multiple CPU Core Feature .......................................................... 27
6.4.5 “Local Area Connection” Not To Be Renamed in Network Connections ................. 27
6.4.6 NIC Configuration Settings ...................................................................................... 27
6.4.7 User Accounts for Local Edition Installations ............................................................ 28
6.4.8 Terminal Services and Remote Desktop Services ....................................................... 28
6.4.9 Connecting a Station to an Off-Control Network Domain ...................................... 29
6.5 Windows Workstations ..................................................................................................... 29
6.5.1 Resolution and Color Settings of Multi-Headed Workstation Displays ..................... 29
6.5.2 Screen Savers ............................................................................................................. 30
6.5.3 Security Feature in Windows 10 and Windows Server 2016 ..................................... 30
6.5.4 System Monitor Messages Reporting Unavailable Workstations ................................ 30
6.5.5 System Monitor Behavior after Power Becomes Unavailable ..................................... 30
6.5.6 IP Address Displayed in the Exceed Icon ................................................................... 30
6.5.7 Additional Security for Plant Operators and View Only Users ................................. 31
6.5.8 User Accounts after an Active Directory Migration .................................................. 34
6.6 Foxboro Evo Control Core Services Startup and Security Options .................................... 35
6.6.1 Foxboro Evo Control Core Services Startup Options ................................................ 35
6.6.2 Autologon ................................................................................................................. 41
6.6.3 Restricted Desktop .................................................................................................... 42
6.6.4 Welcome Screen ........................................................................................................ 45
6.7 Control Core Services Log Off and Shut Down ................................................................ 47
6.7.1 Logging Off ............................................................................................................... 47
6.7.2 Shutting Down/Restarting the Station ...................................................................... 48
6.7.3 Shut Down Configuration ........................................................................................ 49
6.8 Virtual Machines (VMs) ................................................................................................... 50
6.8.1 Re-Enabling Functionality Typically Restricted on VMs ........................................... 50
6.9 Solaris 10 Stations ............................................................................................................. 51
6.9.1 GNOME Session Manager Segmentation ................................................................. 51
iv
Contents B0700SY – Rev C
6.10 Object Manager Software ................................................................................................ 51

6.10.1 OM API register_name Function ............................................................................ 51
6.11 Tools and Utilities ........................................................................................................... 51
6.11.1 Getpars Utility (CAR #1012329) ............................................................................ 51
6.12 Displays .......................................................................................................................... 51
6.12.1 Station Displays and Tool/Utilities List Same Number of Unique Points at
Different Values ................................................................................................................. 51
6.12.2 Detail Display Differences on Workstations on
The Nodebus and The Foxboro Evo Control Network ..................................................... 52
6.13 Application Software ....................................................................................................... 52
6.13.1 IFDC Software ........................................................................................................ 52
6.14 Alarm Management Subsystem ....................................................................................... 52
6.14.1 Clearing Alarms from Alarm Displays ..................................................................... 52
6.14.2 Alarm Counts and Page Counts .............................................................................. 52
6.14.3 Configuring Alarm Management Options for V8.x Systems Using ADMC ............ 53
6.14.4 Previously Deleted Alarm Manager Configuration Files .......................................... 54
6.14.5 Moveability of Full Screen Current Alarm Display (CAD) ...................................... 54
6.14.6 Message Manager Software ...................................................................................... 54
6.14.7 Running a Single Message Manager ....................................................................... 54
6.14.8 Configuring Default Alarm Manager ...................................................................... 54
6.14.9 Printing Alarm Priority to the Alarm Printer ........................................................... 55
6.15 Control Configuration Software ...................................................................................... 57
6.15.1 Detected Error Message When Deleting a Block or Compound in ICCAPI ............ 57
6.15.2 Inadvisable to Shutdown or Reboot Station While ICC is Open ............................. 58
6.16 Control Databases and Process Control ........................................................................... 58
6.16.1 Re-Alarming Change in FCP270 and ZCP270 CP Images V2.5 and Later ............. 58
6.16.2 Re-Alarming for Multiple Alarm Priority Types ...................................................... 58
6.16.3 Changing Block Modes on DO or AO Blocks ......................................................... 59
6.16.4 Dynamically Reconfiguring a Block Parameter ........................................................ 59
6.16.5 PAKOUT Block Limitations ................................................................................... 59
6.16.6 Using AOUTR Blocks with ECB38R for FBM46/FBM246 Applications ............... 60
6.16.7 Using the OSP 0 Instruction in the LOGIC Block .................................................. 60
6.17 Control Processor (FCP280, FCP270 and ZCP270) ....................................................... 60
6.17.1 Use of Self-Hosting Feature ..................................................................................... 60
6.17.2 Issuing a Reboot Command for a Shadow FCP280 or CP270 Module ................... 61
6.17.3 Addressing Stations with Numeric Letterbugs ......................................................... 61
6.17.4 Installing or Replacing FCP280, CP270, and FCM100
Modules in a Running System with I/A Series SoftwareV8.x or
Foxboro Evo Control Core Services v9.0 or Later ............................................................... 61
6.17.5 Setting Primary ECB Parameter BAUD2M for 100 Series FBMs ............................ 62
6.18 Field Device Controller 280 (FDC280) .......................................................................... 63
6.18.1 FDC280 IOM Image .............................................................................................. 63
6.18.2 Setting Timeout Option for Modbus TCP Client Driver for Interfacing
Tricon and Trident Devices ............................................................................................... 64
6.19 Address Translation Station (ATS) .................................................................................. 65
6.19.1 Communicating Directly to an ATS ........................................................................ 65
6.19.2 Station Support for Address Translation Station ...................................................... 65
6.19.3 Network Unavailability Detection Logs ................................................................... 66
v
6.20 Intrinsically Safe I/O Subsystem ...................................................................................... 67

6.20.1 Using SRD991 with the Intrinsically Safe I/O Subsystem ....................................... 67
6.21 Fieldbus Modules (FBMs) and Field Communication Modules (FCMs) ......................... 67
6.21.1 Redundant FBM248 Pulse Count ........................................................................... 67
6.21.2 Configuring the FBM206 Input Frequency Using the RES04 Parameter ................ 67
6.21.3 Master/Tracker FBM222 Role Switches .................................................................. 68
6.21.4 Signal Conditioning in RIN Block for FFH1 d/p Cell ............................................ 68
6.21.5 EEPROM Updating FBM216s with Software Prior to V2.35F ............................... 68
6.21.6 Duplicate Channel Numbers for FoxCom Transmitters (ECB18) and FoxCom
Valves (ECB74) .................................................................................................................. 69
6.21.7 Configuring FCMs for Simplex Operation .............................................................. 69
6.21.8 Validating Compact PROFIBUS Configuration File ............................................... 70
6.21.9 Performing General Downloads .............................................................................. 70
6.21.10 FBM216 Role Switch ........................................................................................... 70
6.21.11 200 Series FBM Rate of Change Alarms ................................................................ 70
6.21.12 Configuring Fail-Safe for Proper Operation of FBM218 ....................................... 71
6.21.13 EEPROM Updating FBM220 and FBM221 ........................................................ 71
6.21.14 Field Device System Integrator (FDSI) Subsystem ................................................ 71
6.21.15 Displaying FoxCom Device Information After General Download ....................... 72
6.21.16 FBM223 PROFIBUS Configurator ...................................................................... 72
6.21.17 Changing FSENAB for ECB200 (PROFIBUS-DP FBM223) ............................... 72
6.21.18 TIMSTP Parameter of the EVENT Block ............................................................. 72
6.21.19 Online/Offline States of SPECTRUM I/O Migration Modules under ZCP270 .. 73
6.22 FOUNDATION fieldbus, PROFIBUS-DP, HART, Modbus, DeviceNet, and FDSI .... 73
6.22.1 DeviceNet Baud Rate .............................................................................................. 73
6.23 Peer-to-Peer Connections of Real-Type Block Inputs ...................................................... 73
6.24 Data Transfers Between the Nodebus and The Foxboro Evo Control Networks ............. 74
7. V9.4 User Notes .............................................................................................................. 75

7.1 Software Installation .......................................................................................................... 75
7.1.1 Installation of Foxboro Evo Control Software 6.0.x, v6.1-v6.2, or v7.0-7.1 on
Control Core Services v9.4 ................................................................................................. 75
7.1.2 Reconcile Utility ....................................................................................................... 77
7.2 Windows Workstations ..................................................................................................... 78
7.2.1 Messages Appearing Post-Installation for Domain Controllers .................................. 78
7.2.2 Printer Monitor System Message in SMON Indicates Normal Operation ................ 78
7.2.3 System Manager Does Not Succeed In Removing Database Locks Resulting in
“Cannot Initiate Action” Message ...................................................................................... 78
7.2.4 User Cannot Perform Checkpoint Even After Removing Database Locks ................. 80
7.2.5 User Access Shared Folders Between Workstations with Windows 10 and
Windows XP ...................................................................................................................... 80
7.2.6 User Access Shared Folders from an Insecure Network File Device ........................... 81
7.3 Applications ...................................................................................................................... 82
7.3.1 FoxDraw ................................................................................................................... 82
7.4 Device Monitor ................................................................................................................. 82
7.4.1 Device Monitor Master Active on Isolated Segments of Foxboro Evo
Control Network ................................................................................................................ 82
7.5 Control Processors ............................................................................................................ 83
vi
Contents B0700SY – Rev C
7.5.1 I/O Load (Fieldbus Scan Load) Increase Due to Unavailable or Disconnected
Fieldbus Channel ............................................................................................................... 83
7.5.2 Removing Married FCP280s From Their Baseplate .................................................. 83
7.6 Control Network Interface ................................................................................................ 85
7.6.1 Disabling Reporting Unavailability of Single Power Supply for CNIs via System
Key in Foxboro Evo System Monitor Applications ............................................................. 85
7.6.2 Continuous Reboot of Fault-Tolerant CNI Pair Following Change in Letterbug ...... 85
7.6.3 Empty Engineering Units Field Can Lead to Delays in FoxView Trend Display
Callup ................................................................................................................................ 86
7.6.4 Resolving Graphical Corruption with Foxboro Evo Control HMI Displays
Showing Data from CNIs .................................................................................................. 87
7.6.5 Remote Attributes on Displays Take Minutes to Show Initial Values
On Invocation .................................................................................................................... 87
7.6.6 Monitoring Change Driven Updates per Second Between Connected
Control Network Interfaces ................................................................................................ 88
7.6.7 Virtual Router Redundancy Protocol (VRRP) Failover Performance ......................... 88
7.6.8 Access List Editor ...................................................................................................... 89
8. Customer Cases Resolved in V9.4 ................................................................................... 91
Appendix A. EEPROM Revision Levels............................................................................. 103

A.1 Image Revision Levels for Control Stations and
ATS with Control Core Services v9.4 .................................................................................... 103
A.2 100 Series FBM Software and EEPROM Versions ......................................................... 104
A.3 200 Series FBM Software and EEPROM Versions ......................................................... 108
vii
viii
Tables
1-1. Foxboro Evo Product Rebranding ................................................................................. 4
3-1. Overview of Control Core Services or I/A Series Software
Component Compatibility ............................................................................................ 8
4-1. Platforms Supporting Control Core Services v9.4 ....................................................... 17
5-1. Control Core Services v9.4 Day 0 Media Kit (K0204AR) ........................................... 19
5-2. Additional Packages for Foxboro Evo Control Core Services V9.4
with Media Kits .......................................................................................................... 21
6-1. Minimum Versions for Nodebus Stations Running on
The Foxboro Evo Control Network ............................................................................ 65
A-1. Control Core Services V9.4 Control Station and ATS EEPROM/Image
and Software Revision Levels ..................................................................................... 103
A-2. Control Core Services V9.4 Legacy Station EEPROM/Image
and Software Revision Levels ..................................................................................... 104
A-3. Software Versions of 100 Series FBMs (Y Form Factor) ............................................ 105
A-4. Software Versions for 200 Series FBMs (DIN Rail Mounted Form Factor) ............... 109
A-5. EEPROM Revision Levels for 200 Series FBMs
(DIN Rail Mounted Form Factor) ............................................................................ 113
ix
B0700SY – Rev C Tables
x
Safety Information
Important Information
Read these instructions carefully and look at the equipment to
become familiar with the device before trying to install, operate, ser-
vice, or maintain it. The following special messages may 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 either symbol to a "Danger" or

"Warning" safety label indicates that an electrical
hazard exists which will result in personal injury if
the instructions are not followed.
This is the safety alert symbol. It is used to alert you to

potential personal injury hazards. Obey all safety messages
that follow 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.
WARNING
WARNING indicates a hazardous situation which, if not avoided, could
result in death or serious injury.
CAUTION
CAUTION indicates a hazardous situation which, if not avoided, could
result in minor or moderate injury.
NOTICE
NOTICE is used to address practices not related to physical injury.
Please Note
Electrical equipment should be installed, operated, serviced, and main-
tained only 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 con-
struction, installation, and operation of electrical equipment and has
received safety training to recognize and avoid the hazards involved.
Preface
This document assists you in planning and executing an installation of the Foxboro Evo™
Control Core Services (hereinafter referred to as the Control Core Services) v9.4 and also
describes their features.
Throughout these release notes, references are made to contacting the Global Customer Support
(GCS) at https://pasupport.schneider-electric.com. 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 deters
confusion caused by changed wording, different section numbers, or mismatched
page numbers in your reference.
Revision Information
For this revision of this document (B0700SY, Rev. C), these changes were made:
Chapter 4 “V9.4 Hardware Requirements”
♦ Added note under H92 HP Z420 Workstation in Table 4-1.
♦ Added the V90 HP DL380 VM Host to Table 4-1.
Chapter 6 “V9.4 Operational Recommendations”
♦ Removed the “Windows XP” reference from “Message Manager Software” on
page 54.
Chapter 7 “V9.4 User Notes”
♦ Added “User Access Shared Folders from an Insecure Network File Device” on
page 81.
Reference Documents
The following documents provide detailed explanations on the topics described in this document.
Most of these documents are available on the Foxboro Evo Electronic Documentation media
(K0174MA). The latest revisions of each document are also available through our Global Cus-
tomer Support at https://pasupport.schneider-electric.com.
Control Core Services System and Control Configurators
♦ Integrated Control Block Descriptions (B0193AX)
♦ System Definition: A Step-By-Step Procedure (B0193WQ, Rev. L or later)
♦ System Definition V3.4 Release Notes for Windows 10 and Windows Server 2016
(B0700TA)
♦ I/A Series Configuration Component (IACC) User's Guide (B0700FE)
xiii
B0700SY – Rev C Preface
♦ I/A Series Configuration Component (IACC) V2.7 Release Notes (B0700SM)

Control Modules
♦ 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, Rev. E or later)
♦ Field Device Controller 280 (FDC280) User's Guide (B0700GQ)
♦ Field Control Processor 280 (FCP280) On-Line Image Update (B0700FX)
♦ Control Processor 270 (CP270) On-Line Image Update (B0700BY)
Network
♦ The Foxboro Evo Control Network Architecture Guide (B0700AZ)
♦ Address Translation Station User’s Guide (B0700BP)
Security and Virus Protection
♦ Security Implementation User's Guide for I/A Series and Foxboro Evo Workstations (Win-
dows 10 or Windows Server 2016 Operating Systems) (B0700HG)
♦ Installation and Configuration of the McAfee Products Endpoint Protection (B0700VU)
♦ Installation and Configuration of the McAfee ENS 10.5.2 with ePO 5.9.1 (B0700VW)
♦ Veritas System Recovery 2016 Desktop, Server and Virtual Editions Guide for I/A Series®
and Foxboro Evo™ Process Automation Systems (B0700HH)
Foxboro Evo Software Concepts
♦ Control Processor 270 (CP270) and Field Control Processor 280 (CP280) Integrated
Control Software Concepts (B0700AG)
Control Core Services Release Notes
♦ Control Core Services v9.4 Software Installation Guide (B0700SX)
♦ 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)
♦ 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.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)
xiv
Preface B0700SY – Rev C
♦V8.5 Release Notes (B0700SC)

System Manager
♦ System Manager (B0750AP)
♦ System Manager V2.11 Release Notes (B0750RS)
Control Software
♦ Control Database Deployment User’s Guide (B0750AJ)
♦ Foxboro Evo Control Software Installation Guide (B0750RA)
♦ Control Software v7.1 Release Notes (B0750ST)
FoxView/FoxDraw
♦ FoxView Software v10.4 (B0700FC, Rev. D or later)
♦ FoxDraw Software v10.4 (B0700FD, Rev. E or later)
♦ FoxView™ and FoxDraw™ Software V10.5 Release Notes (B0700SZ)
FERRET
♦ FERRET V6.2 (Windows Platforms) and FERRET V6.2 (UNIX Platforms) Installation
and Release Notes (B0860RU)
System Sizing
♦ The Foxboro Evo Sizing Guidelines (B0700AX)
Virtualization
♦ Virtualization User's Guide for Windows Server 2012 R2 (B0700VQ)
Fieldbus Modules
♦ 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 User's Guide (B0700BQ)
♦ Standard 200 Series Subsystem Overview (PSS 31H-2SOV)
♦ 100 Series Fieldbus Module Upgrade Subsystem Overview (PSS 31H-2W100)
♦ Standard and Compact 200 Series I/O, Agency Certifications (PSS 31H-2CERTS)
♦ Standard 200 Series Power Supply - FPS400-24 (PSS 31H-2W3)
♦ Termination Assembly Adapter Modules for 100 Series Upgrade (PSS 31H-2W4)
♦ Standard 200 Series Baseplates (PSS 31H-2SBASPLT)
♦ Standard 200 Series Power Supplies - FPS120-24 and FPS240-24 (PSS 31H-2FPS)
♦ 100 Series Conversion Mounting Structures (PSS 31H-2W8)
♦ FBI200A Fieldbus Isolator/Filter (PSS 21H-2Y17)
♦ FBI200 Fieldbus Isolator/Filter (PSS 21H-2Y18)
♦ 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 31H-2S201)
♦ FBM201e Analog Input (0 to 20 mA) Interface Modules (PSS 21H-2Z1 B5)
♦ FBM202, Thermocouple/mV Input Interface Module (PSS 31H-2S202)
xv
♦ FBM203/b/c/d Platinum/Nickel/Copper RTD Input Interface Modules (PSS 31H-

2S203)
♦ FBM204 – Channel-Isolated, 0 to 20 mA, I/O Interface Module (PSS 31H-2S204)
♦ FBM205 – Channel-Isolated, Redundant-Ready 0 to 20 mA I/O Interface Module
(PSS 31H-2S205)
♦ FBM206, Pulse Input and FBM206b, Pulse I/O Interface Modules (PSS 31H-2S206)
♦ Compact FBM207b Contact Sense Input Interface Modules (PSS 31H-2C207)
♦ FBM207/FBM207b/FBM207c – Channel-Isolated, Voltage Monitor/Contact Sense Input
Interface Module (PSS 31H-2S207)
♦ FBM208/208b, Redundant with Readback, 0 to 20 mA I/O Interface Module
(PSS 31H-2S208)
♦ FBM211 – Differential 0 to 20 mA Input Interface Module (PSS 31H-2S211)
♦ FBM212 – Differential Thermocouple/mV Input Interface Module (PSS 31H-2S212)
♦ Compact FBM214b, HART® Communication Input Interface Module (PSS 31H-
2C214)
♦ FBM214b, HART® Communication Input Interface Module (PSS 31H-2S214)
♦ Compact FBM215 HART® Communication Output Interface Module (PSS 31H-
2C215)
♦ FBM215 – HART® Communication Input Interface Module (PSS 31H-2S215)
♦ Compact FBM216b, HART® Communication Redundant Input Interface Module
(PSS 31H-2C216)
♦ FBM216b HART® Communication Redundant Input Interface Module (PSS 31H-
2S216)
♦ FBM217 – Discrete Input Interface Module (PSS 31H-2S217)
♦ Compact FBM218 HART® Communication Redundant Output Interface Module
(PSS 31H-2C218)
♦ FBM218 – HART Communication Redundant Input Interface Module (PSS 31H-
2S218)
♦ FBM219 Discrete I/O Interface Module (PSS 31H-2S219)
♦ FBM220/221 – FOUNDATION fieldbus H1 Communication Interface Module
(PSS 21H-2Z20 B4)
♦ FBM222, Redundant PROFIBUS-DP Communication Interface Module (PSS 31H-
2Z22)
♦ FBM223 – PROFIBUS-DP Communication Interface Modules (PSS 21H-2Z23 B4)
♦ FBM224 – Modbus Communication Interface Module (PSS 31H-2S224)
♦ FBM227, 0 to 10 V dc, Contact/dc I/O Interface Module with DPIDA and MDACT
Support (PSS 31H-2S227)
♦ FBM228 – FOUNDATION fieldbus H1 Redundant Communication Interface Module
(PSS 31H-2Z28)
♦ FBM229, DeviceNet™ Communication Interface Module (PSS 31H-2Z29)
xvi
Preface B0700SY – Rev C
♦
FBM230 – Field Device System Integrator (FDSI) Module, Four Serial Ports, Single
(PSS 31H-2S230)
♦ FBM231– Field Device System Integrator (FDSI) Module, Four Serial Ports, Redundant
(PSS 31H-2S231)
♦ FBM232 –Field Device System Integrator (FDSI) Module, 10/100 Mbps Ethernet, Single
(PSS 31H-2S232)
♦ FBM233 – Field Device System Integrator (FDSI) Module, 10/100 Mbps Ethernet,
Redundant (PSS 31H-2S233)
♦ FBM237, 0 to 20 mA Output Interface Module (Redundant Ready) (PSS 31H-2S237)
♦ FBM238, Discrete 24DI/8DO Interface Module (PSS 31H-2S238)
♦ FBM239, Digital 16DI/16DO Interface Module (PSS 31H-2S239)
♦ FBM240 – Channel Isolated, Redundant with Readback, Discrete I/O Interface Module
(PSS 31H-2S240)
♦ FBM241/FBM241b/FBM241c/FBM241d – Channel Isolated, Discrete I/O Interface
Module (PSS 31H-2S241)
♦ Compact FBM242, Externally Sourced, Discrete Output Interface Module (PSS 31H-
2C242)
♦ FBM242 – Channel Isolated, Externally Sourced, Discrete Output Interface Module
(PSS 31H-2S242)
♦ FBM243/243b, FoxCom™ Dual Baud Rate, Intelligent Device Interface Modules
(PSS 31H-2S243)
♦ FBM244, 0 to 20 mA I/O Interface Module with HART® Support (PSS 31H-2S244)
♦ FBM245, 0 to 20 mA I/O Interface Module with HART® Support (Redundant)
(PSS 31H-2S245)
♦ FBM246/246b, FoxCom™ Redundant Dual Baud Rate, Intelligent Device Interface
♦ FBM247, Current/Voltage Analog/Digital/Pulse I/O Configurable Channel Interface
♦ FBM248, Current/Voltage Analog/Digital/Pulse I/O Configurable Module (PSS 31H-
2S248)
Extended Frame Services
♦ I/A Series Extended Frame Services 2.4 and I/A Series Communication DTMs
(B0400EF)
♦ I/A Series Extended Frame Services 2.4 Release Notes (B0400EH)
Hardware and Software Specific Documentation for Windows 10 Operating System
♦ Hardware and Software Specific Instructions for Model H92 (HP Z440) Windows 10
Professional Operating System (B0700HA)
♦ Hardware and Software Specific Instructions for Model H92 (HP Z420) Windows 10
Professional Operating System (B0700HB)
xvii
Hardware and Software Specific Documentation for Windows Server 2016 Standard
Operating System
♦ Hardware and Software Specific Instructions for Model H90 (HP DL380 Gen9) Win-
dows Server 2016 Operating System (B0700GZ)
♦ Hardware and Software Specific Instructions for Model V91 Server Virtualization Host
(HP DL380 Gen9) Windows Server 2016 Operating System (B0700HE)
xviii
1. Read Me First
This chapter contains an introduction to the Foxboro Evo Control Core Services (hereinafter
referred to as the Control Core Services) v9.4 release and an overview of its software
installation.
1.1 Overview of the Control Core Services v9.4

Release
The Control Core Services v9.4 release provides additional functionality to the Foxboro Evo Pro-
cess Automation System.
The new features of this release are described in Chapter 2 “Features of Control Core Services
V9.4 Release”.
1.1.1 Local Edition and Enterprise Edition Control Core Services

Workstations and servers can be installed with either the Local Edition (previously known as Stan-
dard) or Enterprise Edition (previously known as Security Enhanced) Control Core Services v9.4.
Within a Foxboro Evo system, 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
which includes the Local Edition will not be as secure as a system that only employs the Enter-
prise Edition.
For more details on Enterprise Edition Control Core Services, refer to Security Implementation
User's Guide for I/A Series and Foxboro Evo Workstations (Windows 10 or Windows Server 2016
Operating Systems) (B0700HG).
1.2 Hardware Requirements

The Control Core Services v9.4 can be only installed on the H90, H92, V90, and V911 platforms
listed in “Reference Documents” on page xiii, provided they meet the specifications listed in
Chapter 4 “V9.4 Hardware Requirements” and are configured correctly.
Memory requirements for Control Software2 workstations and servers differ from those which
host the Control Core Services only. Refer to Chapter 2, “Sizing and Performance” in Foxboro Evo
Process Automation System Deployment Guide (B0750BA) for memory requirements for worksta-
tions and servers in systems with the Foxboro Evo Control Software (hereinafter referred to as the
Control Software).
Refer to Chapter 4 “V9.4 Hardware Requirements” for additional information.
1. On V90 and V91 platforms, Control Core Services v9.4 is installed on the virtual machines (VMs)
maintained by these platforms.
2.
Control Software workstations and servers run the Foxboro Evo Control Software.
1
B0700SY – Rev C 1. Read Me First
1.3 Domain Controllers

In order to install the Enterprise Edition Control Core Services (formerly known as Security
Enhanced, or SE, software) on your Foxboro® system, you have to have a dedicated domain
controller(s) using Microsoft Active Directory® network services. If the Primary Domain
Controller (PDC) and optional Secondary Domain Controllers (SDCs) are to be installed on the
Foxboro Evo 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(s) 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,
refer to Control Core Services v9.4 Software Installation Guide (B0700SX).
NOTE
It is highly recommended that you have a second server acting as an SDC to provide
redundancy. As well, having a second domain controller will greatly facilitate per-
forming upgrades in the future.
1.4 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 with the media defined in Control Core Ser-
vices v9.4 Software Installation Guide (B0700SX).
The Local Edition and Enterprise Edition Control Core Services can only be installed on these
operating system images.
1.5 Control Core Services V9.4 Support for the

Control Software
Control Software v7.1 or later is compatible with I/A Series software v8.8 and Control Core Ser-
vices v9.0-v9.4. The previous versions of Foxboro Control Software (v3.x-v6.x) and InFusion®
software are not supported for Control Core Services v9.1 or later. Control Software installation is
described in Foxboro Evo Control Software Installation Guide (B0750RA).
NOTE
If you are installing any Control Software-based Field Device Manager on a station,
you have to install Control Software v7.1 or later with it.
1.6 Site Upgrades

Given the complexity of the systems and different combinations of hardware and software com-
ponents that need to interoperate successfully to control a process, you need to carefully plan your
site upgrade. Chapter 3 “V9.4 Compatibility Considerations” provides detailed information on
upgrading an existing system.
2
1. Read Me First B0700SY – Rev C
1.6.1 Migrating Files

To migrate databases and preserve customized files for use on a new system with Control Core
Services v9.4, 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.
♦ Refer to the “Backup and Restore” appendix in Veritas System Recovery 16 Desktop,
Server and Virtual Editions Guide for I/A Series® and Foxboro Evo™ Process Automa-
tion Systems (B0700HH) for information about backing up specific Control Core
Services software and control databases to a new system with Control Core Services
v9.4.
♦ Refer to Foxboro Evo 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 run-
ning Control Core Services v9.4 and the Control Software v7.1 or later.
1.6.2 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
Evo 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.
1.7 Installation Overview

The Control Core Services v9.4 has to be installed on new or supported existing stations (via a
Day 0 installation). Refer to Chapter 4 “V9.4 Hardware Requirements” for a list of supported
hardware.
♦ 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.4.
♦ 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 plat-
form 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.4.
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 4 “V9.4 Hardware Requirements” for supported platforms.
For details on the Control Core Services v9.4 installation, refer to Control Core Services v9.4 Soft-
ware Installation Guide (B0700SX).
3
B0700SY – Rev C 1. Read Me First
To run the Control Software with Control Core Services v9.4, you have to install the Control
Software v7.1 or later on your station. Installation instructions (and pre-installation procedures
such as migration) are provided in Foxboro Evo Control Software Installation Guide (B0750RA,
Rev. Z or later).
The latest revisions of these documents are available on the GCS webpage:
https://pasupport.schneider-electric.com.
1.8 Maintain Up-to-Date Version of Adobe® Reader®

for Foxboro Evo 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 the following website:
https://get.adobe.com/reader/
For workstations/servers which cannot connect to the internet, download a full installation pro-
gram from the website listed above and then copy the program to the workstation/server and
install Adobe Reader on it.
To improve the cybersecurity hardening of your system, these are recommended optimal prac-
tices:
♦ It is inadvisable to install Adobe Reader on a workstation or server on the Foxboro
Evo Control Network, or the I/A Series control network.
♦ Keep any installation of Adobe Reader up-to-date with the latest Adobe security
patches.
1.9 Foxboro Evo Product Rebranding

For the recent releases of the Foxboro Evo Process Automation System, the products listed in
Table 1-1 were rebranded as follows:
Table 1-1. Foxboro Evo Product Rebranding
Product Name for Foxboro Evo Process

Product Name - Previous Release Automation System (and Abbreviation)
I/A Series (Intelligent Automation Series) system Foxboro Evo Process Automation System
Distributed Control System (DCS) (Foxboro Evo System)
I/A Series (Intelligent Automation Series) software Foxboro Evo Control Core Services
(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 Evo Control Software
(the Control Software)
FCS Configuration Tools/InFusion Engineering Foxboro Evo Control Editors
Environment (Control Editors)
Foxboro Control Software InTouch® Application Foxboro Evo Control HMI
(Control HMI)
4
2. Features of Control Core Services
V9.4 Release
This chapter describes the major features and enhancements included with the Control Core
Services v9.4 release.
2.1 Support for Windows 10 and Windows Server

2016 Operating Systems
Control Core Services v9.4 runs on stations with Windows 10 or Windows Server 2016 operating
systems only.
2.2 Support for the Microsoft Windows Server 2016

Active Directory domains
Starting with Control Core Services v9.4, Microsoft Windows Active Directory domains running
on Windows Server 2016 are supported which can support Enterprise Edition domain clients
running OS versions Windows 7, Windows Server 2008 R2, Windows 10, and Windows Server
2016. They can also support domain clients running OS versions Windows XP and Windows
Server 2003 if the domain was migrated from the Windows Server 2003 version (I/A Series soft-
ware v8.5 through v8.7) prior to updating to Control Core Services v9.4.
2.3 Local Edition User Account Updates

For the Local Edition stations, the user account profile has changed on CCS V9.4. The built-in
Administrator account is disabled. The Fox account has been removed from all workstation
images. In its place, is a new default user account named Account1. During installation of a sta-
tion with Local Edition Control Core Services v9.4, the user is prompted to create a new pass-
word for Account1. They are also prompted to create a new user account which will be used for
operating the workstation. This is the replacement for the Fox account. A password must also be
set for this account which complies with the password complexity requirements. If the overall sys-
tem contains Control Core Services v9.3 stations which have been updated with QF33793871,
then the same user account and password should be used on all the Local Edition Control Core
Services v9.4 workstation as are used on the Control Core Services v9.3 stations with this QF
installed.
During installation of a Local Edition Control Core Services v9.4 station, the user is prompted to
create a new password for Account1.
5
B0700SY – Rev C 2. Features of Control Core Services V9.4 Release
2.4 Enterprise Edition User Account Updates

For Enterprise Edition domain client stations, the user account profile has changed. The built-in
Administrator account is disabled. The Fox account has been removed from all workstation
images. In its place is a new default user account named “Account1”.
2.5 Additional Security Settings for Both Local Edition

and Enterprise Edition Domain Clients
Further enhancements are made to local group policies for both Enterprise Edition domain clients
and Local Edition stations. Additionally, added group policies which apply to Windows 10 and
Server 2016 domain clients are put into place. These new policy settings will not be applied to
any existing or newly added Windows 7 or Server 2008 R2 stations on the domain or local.
On a CCS V9.4 domain controller, the built-in administrator account will be automatically
enabled for domain controller setup and the password will be set during the installation. After the
installation is complete, this account will be disabled.
6
3. V9.4 Compatibility
Considerations
This chapter describes compatibility considerations for Foxboro Evo software with Control Core
Services v9.4.
For more information specific to this release, refer to Chapter 6 “V9.4 Operational Recommenda-
tions”.
3.1 Site Upgrade Plans

For information on site upgrade plans for Control Core Services v9.4, refer to Control Core Ser-
vices v9.4 Software Installation Guide (B0700SX).
3.2 Control Software Support for Control Core

Services V9.4 or Later
Refer to Foxboro Evo Control Software Installation Guide (B0750RA, Rev. Z or later) and Control
Software V7.1 Release Notes (B0750ST) for planning your integration with Control Software v7.1.
7
B0700SY – Rev C 3. V9.4 Compatibility Considerations
3.3 Interoperability and Compatibility

Table 3-1 provides an overview of the interoperability and compatibility of various commonly
used Control Core Services or I/A Series software components:
Table 3-1. Overview of Control Core Services or I/A Series Software

Component Compatibility
I/A Series Software Control Core Services

v8.2
Software Version /8.3 v8.4.x v8.5 v8.6 v8.7 v8.8 v9.0 v9.1 v9.2 v9.3 v9.4
FoxView 10.1 √ √ x x x x x x x x x
10.2 √ √ x x x x x x x x x
10.2.1 √ √ x x x x x x x x x
10.2.2 √ √ √ √ x x x x x x x
10.2.3 √ √ √ √ √ x x x x x x
10.2.4 √ √ √ √ √ x x x x x x
10.3 x x x x x √ x x x x x
10.4.2 √ √ √ √ √ √ √ √ √ x x
10.4.3- √ √ √ √ √ √ √ √ √ √ x
10.4.41
10.5 x x x x x √ √ √ √ √ √
IACC 2.1 √ x x x x x x x x x x
2.3.1 - 2.4 √ √ √ √ √ x √ √ √ √ x
2.5 x x x x x √ √ √ √ √ x
2.6-2.6.42 √ √ √ √ √ √ √ √ √ √ x
2.7 x x x x x √ √ √ √ √ √
AIM*AT 3.4 x x √ √ √ √ x x x x x
3.4.1 x x √ √ √ √ √ x x x x
(installed by
QF1175712
)
3.4.2 x x √ √ √ √ √ √ √ √ x
3.4.3 x x √ √ √ √ √ √ √ √ x
3.5 x x x x x √ √ √ √ √ √
8
3. V9.4 Compatibility Considerations B0700SY – Rev C

Component Compatibility (Continued)

v8.2
System 2.0 √ √ √ x x x x x x x x
Manager 2.1 √ √ √ √ x x x x x x x
2.2 √ √ √ √ √ x x x x x x
2.3 √ √ √ √ √ √ x x x x x
2.4 x √ √ √ √ √ √ x x x x
(v8.4.4
&
later)
2.5 x √ √ √ √ √ √ √ x x x
(v8.4.4
&
later)
2.6 x √ √ √ √ √ √ √ √ x x
(v8.4.4
&
later)
2.93 x √ √ √ √ √ √ √ √ √ x
(v8.4.4
&
later)
2.11 x x x x x √ √ √ √ √ √
Foxboro Evo 5.0 x x x x √ √ √ x x x x
Control Soft- 6.0-6.24 x x x x x √ √ √ √ √ x
ware (“the
7.0 x x x x x √ √ √ √ √ x
Control Soft-
ware”) 7.1 x x x x x √ √ √ √ √ √
Foxboro 3.0 x x x √ x x x x x x x
Control Soft- 3.1 x x x x √ x x x x x x
ware (Earlier 4.0 x x x x √ √ x x x x x
Version of
Foxboro Evo
Control Soft-
ware)
InFusion 1.0 √ x x x x x x x x x x
(Earlier Ver- 1.1 x √ x x x x x x x x x
sion of 1.2.2 x √ x x x x x x x x x
Foxboro Evo
Control Soft- 2.0 x x √ x x x x x x x x
ware) 2.5 x x x √ x x x x x x x
9


v8.2
Field Device 2.0 x x x √ x x x x x x x
Manager for 3.0 x x x x √ √ x x x x x
FOUNDA-
3.1.1 x x x x √ √ √ x x x x
TION field-
bus 4.0 x x x x x √ √ √ √ √ x
4.1 x x x x x √ √ √ √ √ √
Field Device 3.0 x x x x √ √ x x x x x
Manager for 3.1.1 x x x x √ √ √ x x x x
HART 4.0 x x x x x √ √ √ √ √ x
4.1 x x x x x √ √ √ √ √ √
Field Device 2.0 x x x √ x x x x x x x
Manager for 4.0 x x x x √ √ x x x x x
PROFIBUS
4.0.2 x x x x √ √ √ x x x x
4.0.3 x x x x x √ √ √ √ √ x
4.0.4 x x x x x √ √ √ √ √ x
4.1 x x x x x √ √ √ √ √ √
DeviceNet 1.0.2 x x x x √ √ √ √ √ √ √
Configurator
System Defi- 2.8 √ x x x x x x x x x x
nition 2.9 √ √ x x x x x x x x x
2.10 √ √ √ x x x x x x x x
2.11 √ √ √ √ √ x x x x x x
3.0 √ √ √ √ √ √ x x x x x
3.1 √ √ √ √ √ √ √ √ x x x
3.2 √ √ √ √ √ √ √ √ √ √ x
3.3 √ √ √ √ √ √ √ √ √ √ x
3.4 √ √ √ √ √ √ √ √ √ √ √
FoxSFC 2.0 √ x x x x x x
2.1 x x x x x √ √ √ √ √ √
IFDC 3.1 x x x √ x x x x x x x
3.1.1 x x x x √ √ √ √ √ √ √
3.2 - 3.2.2 x x 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 x x √ √ √ √ √ √
10


v8.2
SOE/TDR 1.5.2-1.5.45 √ √ √ √ √ √ √ √ √ √ x
1.5.66 √ √ √ √ √ √ √ √ √ √ x
1.67 √ √ √ √ √ √ √ √ √ √ x
1.7 √ √ √ √ √ √ √ √ √ √ √
FDSI Config- 1.6 x x x x x √ √ √ √ √ √
urator
TSAA SOE 2.3 x x x x x √ √ √ √ √ √
Workstation
Driver
Notes:
1. Although I/A Series software v8.5 needs a version upgrade of FoxView™ software, it is not necessary to con-
vert 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.
2. For System Manager Quick Fixes and other installation notes, refer to “Interoperability Considerations” in the
revision of System Manager (B0750AP) and System Manager Vx.x Release Notes (B0750RS) shipped with your
Foxboro Evo system.
1. FoxView v10.4.4 is the minimum needed for monitoring FDC280s on Control Core Services v9.3 and earlier.
2. Interoperable compatibility with FoxView/FoxDraw™ v10.3 and later only.
3.
System Manager v2.9 is the minimum needed version to monitor FBM248s.
4. 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 Evo Control HMI. Refer to the documentation included with this
Quick Fix for instructions on how to install it.
Control Software v6.0.4 and later include this QuickFix.
5. SOE/TDR v1.5.2 is the minimum needed version to run FBM247s.
6.
SOE/TDR v1.5.6 is the minimum needed version to run FBM219s.
7. SOE/TDR v1.6 is the minimum needed version to run FBM248s.
These commonly used applications have been validated to run on Local Edition and Enterprise
Edition Control Core Services v9.4 systems:
♦ FoxView / FoxDraw software, v10.5
♦ System Manager software, v2.11
♦ AIM*AT software v3.5, available from https://pasupport.schneider-electric.com.
Includes:
♦ AIM*Historian software
♦ AIM*API software (NetMFC API)
♦ AIM*DataLink software
♦ AIM*Inform software
11
♦ AIM*I/O Gate Collector software

♦ AIM*OPC Server software
♦ System Definition software, v3.4
♦ FoxSFC Configurator and Run-Time software, v2.2
♦ SOE (Sequence of Events) software, v1.7
♦ TDR/TDA (Transient Data Recorder and Analyzer) software, v1.7
♦ I/A Series Configuration Component (IACC), v2.7
♦ Intelligent Field Device Configurator (IFDC) software1, v3.2.2
♦ Foxboro Evo Control Software v7.1 or later (this version is supported on I/A Series
software v8.7-v8,8 or Control Core Services v9.0 or later) - systems with I/A Series
software v8.7 also support earlier versions of this software, including Foxboro Control
Software v3.0
♦ EFS software, v3.0
♦ Maintenance Response Centre (MRC) v1.3
3.3.1 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. Refer to the AIM*AT Suite Installation Guide
(B0193YM) for installation instructions.
3.3.2 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.4 and previous I/A Series software releases have not
changed except where noted in this document.
For information and general Foxboro Evo Control Network interoperability and coexistence
guidelines, refer to Chapter 3 of 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 the following general Control/Nodebus network interoperability guide-
lines:
♦ Control database interoperability
♦ Display interoperability
♦ Network Fault Detection (NFD)
♦ Compound Summary Access (CSA)
♦ System Management and System Monitor
♦ Device Monitor
♦ Timekeeping
♦ Alarm processing
♦ Historian
1.
This software does not support the FBM248.
12
♦ IP communications
♦ AIM*API software compatibility
3.3.3 Control Core Services Interoperability and Compatibility

These editions can coexist on the Foxboro Evo Control Network and can be interoperable
depending on the functionality being employed.
♦ Enterprise Edition Control Core Services v9.4
♦ Local Edition Control Core Services v9.4
♦ Security Enhanced Foxboro Evo Control Core Services v9.0 through v9.3
♦ Standard Foxboro Evo Control Core Services v9.0 through v9.3
♦ Security Enhanced I/A Series v8.8
♦ Standard I/A Series v8.8
♦ Security Enhanced I/A Series v8.5 through v8.7
♦ Standard I/A Series v8.5 through v8.7
♦ I/A Series V8.0 through V8.4.4 running on the Windows XP operating system
♦ I/A Series V8.3 through V8.4.2 workstations running the Solaris 10 operating system
on The Mesh (former name for Foxboro Evo Control Network).
These editions are considered fully interoperable on the Foxboro Evo Control Network
♦ Enterprise Edition Control Core Service v9.4 is interoperable with Security Enhanced
I/A Series v8.8 and Security Enhanced Foxboro Evo Control Core Services v9.0 -
v9.3.
♦ Local Edition Control Core Services v9.4 is interoperable with Standard I/A Series
v8.8 and Standard Foxboro Evo Control Core Services v9.0 - v9.3.
3.3.3.1 Active Directory Domain Compatibility

Security Enhanced I/A Series software v8.8, and Control Core Services v9.0-9.3, and Enterprise
Edition Control Core Services v9.4 or later share the same Active Directory domain. They share
organizational units and user groups, but additional policies and policy settings apply to Windows
10 and Server 2016 clients. A client running I/A Series software v8.8 or Control Core Services
v9.0-9.3 can join a domain run by a server with Control Core Services v9.4. Group policies differ
between I/A Series software v8.5/6/7 and I/A Series software v8.8 or Control Core Services v9.0
or later. For networks using Off-Control Network PDCs, these PDCs are updated with the new
group policies. For networks using On-Control Network PDCs, these PDCs as a whole are
updated to Control Core Services v9.4.
3.3.3.2 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.4.
♦ 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
13
Enterprise Edition Control Core Services v9.4 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 Ser-
vices v9.0-v9.3, and Enterprise Edition Control Core Services v9.4 are compatible
with respect to ADMC operations.
3.3.3.3 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.4. 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.
♦ FoxCTS software:
♦ v4.0-v5.0.1 are not valid for I/A Series software v8.8 or Control Core Services
v9.0 or later
♦ v6.0.0 is not valid for Control Core Services v9.0 or later (and for I/A Series soft-
ware v8.8, only the Security Enhanced version is supported)
♦ v6.0.1 is valid for I/A Series software v8.5-v8.8 and every version of Control Core
Services
♦ Application Object Services (AOS) software:
♦ v4.0-v5.0 are not valid for I/A Series software v8.8 or Control Core Services v9.0
or later
♦ v5.0.1 is valid for every version of I/A Series software and Control Core Services
♦ FoxPage and Event Driven Scripts software:
v9.0 or later
♦ v2.0.2 is valid for every version of I/A Series software and Control Core Services
♦ FoxBridge software:
v9.0 or later
♦ v7.00.00-v7.00.03 are valid for I/A Series software v8.8 or Control Core Services
v9.0 or later
♦ INI70 software:
v9.0 or later
♦ v5.01.02 is valid for I/A Series software v8.8 or Control Core Services v9.0 or later
♦ Alarm Shelving Tool software:
♦ v1.0-v2.01 are not valid for I/A Series software v8.8 or Control Core Services v9.0
or later
♦ v3.1 is valid for every version of I/A Series software and Control Core Services
14
♦ Isolation Station software

Contact the Global Customer Support (GCS) at https://pasupport.schneider-electric.com, to discuss
the availability of these applications.
3.3.3.4 Boot Hosting Compatibility for CP Stations

The following 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
♦ CNI – Control Core Services v9.3 and later (data sharing and alarm messages)
♦ 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
3.4 Supported Operations

Unless specifically mentioned in this document, the same operations that were supported in Win-
dows I/A Series software v8.2-v8.8 and Control Core Services v9.0-v9.3 for the Windows operat-
ing system are also supported in v9.4. The operations that could be performed from Nodebus to
the Foxboro Evo Control Network and vice versa, or Nodebus to Nodebus, via control network
backbone, are the same. Refer to Chapter 3, of V8.2 Release Notes and Installation Procedures
(B0700RN) or V8.3 Software for the Solaris Operating System Release Notes and Installation Proce-
dures (B0700RR). Particularly, refer to Table 3-1, Supported Software and Operations, in
B0700RN/B0700RR.
B0700RN/B0700RR discusses the following 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
15
16
4. V9.4 Hardware Requirements
This chapter provides hardware and software requirements and lists supported hardware
requirements.
Control Core Services v9.4 runs on the following currently offered platforms and any later ver-
sions of these platforms which are released.
Table 4-1. Platforms Supporting Control Core Services v9.4
Station Type Platform with Multicore CPU Cores Enabled

Workstation H92 HP Z420 Workstation (Model H92, Style Style G/A to Style H/A)
NOTE
Older styles of the HP Z420 can be upgraded by
replacing the video card with new part number
P0928JF. Any continued use of on-board serial card
will be considered an engineered solution. Consult
your technical / sales representative for details.
H92 HP Z440 Workstation (Model H92, Style J/A or newer style)

Server H90 HP DL380 Gen9 Server1 (Model H90, Style G/A or newer style)
Virtual Machine V90 HP DL380 VM Host
Host
NOTE
The V90 HP DL380 VM Host may be upgraded to a
V91 HP DL380 Gen9 Server 2016 VM Host. Its hard-
ware 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)
1. 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/
Allow three business days for validation of the application.
Additional hardware requirements are provided in the Hardware and Software Specific Docu-
mentation listed in “Reference Documents” on page xiii and the following PSSes:
♦ Model H92 Workstation for Windows 10 Operating System (PSS 31H-4H92-10)
17
B0700SY – Rev C 4. V9.4 Hardware Requirements
♦ Model H90 Workstation Server for Windows Server 2016 Operating System
(PSS 31H-4H90-16)
♦ Virtualization Server Host Hardware Model V91 (PSS 31H-4V91)
18
5. V9.4 System Setup
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.
For detailed instructions to support you in installing Control Core Services v9.4 and preparing for
process operation, refer to Control Core Services v9.4 Software Installation Guide (B0700SX).
5.1 V9.4 Documentation

Verify that you have the necessary documentation needed for your installation. Refer to “Refer-
ence Documents” on page xiii for a list of the documentation related to the Control Core Services
v9.4 release. Most documents are located on the Foxboro Evo Electronic Documentation media
(K0174MA), and you can find the latest revisions of the documents on the Global Customer Sup-
port webpage https://pasupport.schneider-electric.com.
5.2 V9.4 Media

Use the checklists below to verify that you have the necessary media to install Control Core Ser-
vices v9.4.
Refer to the Hardware and Software Specific Instructions included with your station for the part
number of the restore DVD (Day 0 installation DVD) for your station.
NOTE
If you have a pre-v9.4 system, verify that the workstation meets the Control Core
Services v9.4 minimum hardware requirements (see Chapter 4 “V9.4 Hardware
Requirements”) and that the Control Core Services v9.4 media kit is available.
You need the media from the Control Core Services v9.4 kit to perform a Control Core Services
v9.4 Day 0 installation. Then you will need to install the trailer media if provided.
Table 5-1. Control Core Services v9.4 Day 0 Media Kit (K0204AR)
DVD/CD
Part Number Description
K0177BP Foxboro Evo Control Core Services v9.4 Windows 10/Server
2016 Day 0 DVD
K0200MG-W System Definition (SysDef ) v3.4 CD-ROM
K0177BU System Manager V2.11 CD-ROM
K0177BV AIM*AT V3.5 CD ROM
19
B0700SY – Rev C 5. V9.4 System Setup
Table 5-1. Control Core Services v9.4 Day 0 Media Kit (K0204AR) (Continued)
DVD/CD
K0174KK-A FRS for ADMC Interoperability CD-ROM between Control
Core Services software v9.0 and earlier versions of I/A Series soft-
ware
K0174NP-D Foxboro Evo Control Core Services V9.4 Release Notes and
Installation Guide
♦ Control Core Services v9.4 Software Installation Guide
(B0700SX)
♦ Control Core Services v9.4 Release Notes (B0700SY)
20
5. V9.4 System Setup B0700SY – Rev C
5.3 Additional Software Packages

Additional software packages are usually installed from their respective media via standard instal-
lation procedures. They are not included on the Control Core Services media. Refer to the associ-
ated documentation that accompanies the software for exact installation procedures.
Table 5-2 provides a list of the additional software packages for v9.4, which are available in media
kits.
Table 5-2. Additional Packages for Foxboro Evo Control Core Services V9.4
with Media Kits

K0201HH-A I/A Series software pre-v9.0 HART and FOUNDATION™ fieldbus
Update Media Kit for Foxboro Evo Control Software v6.0 - Includes CD-
ROM (K0174LV-A)
K0177BS FoxView/FoxDraw V10.5 CD-ROM for Windows 10/Server 2016
K0177BT FoxDraw Standalone V10.5 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) - Code-
Wrights 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 Evo 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-M)
♦ 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)
♦ Transient Data Recorder and Analyzer (TDR/TDA) V1.6 Release Notes
(B0700RL)
K0177BW I/A Series Systems Configuration Component (IACC) v2.7 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:
♦ Modbus TCP/IP and Serial Downloadable Driver For FDSI
(K0173WW)
♦ FDSI Configurator CD-ROM (K0203CC)
21
Table 5-2. Additional Packages for Foxboro Evo Control Core Services V9.4
with Media Kits (Continued)

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 superceded by Sequential
Function Chart/Structured Text Configurator and Display Manager for
Sequence Blocks (B0700FV), which is available on the Foxboro Evo Elec-
tronic Documentation media (K0174MA) and the Global Customer Sup-
port webpage https://pasupport.schneider-electric.com.
K0203CF FDSI Ethernet/IP Driver Media Kit - Includes:
♦ Field Device Systems Integrator Ethernet/IP Driver CD-ROM
(K0174CP-D)
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)
K0174MD-F FERRET v6.2 for Windows includes the FERRET installation CD-ROM
and:
♦ FERRET V6.2 (Windows Platforms) and FERRET V6.2 (UNIX Plat-
forms) Installation and Release Notes (B0860RU)
K0177BY Local Security Policy Settings for Windows Server 2016
K0177BZ Local Security Policy Settings for Windows 10
K0204AT CVM Media Kit - includes:
♦ V91 Security Group Policy Settings Media – Domain Controller 2012
Enhanced (K0177CA)
♦ V91 Security Local Policy Settings Media Host Server 2016
(K0177CB)
♦ V91 Virtualization Configuration Setup Media 2016 (K0177CC)
K0203BY MRC 1.3
RH103DG Thin Client as Operator Workstation for Windows 10/Server 2016,
Includes:
♦ Thin Client Software DVD (K0177AX)
Some Quick Fixes are not shipped with their associated products, and are only available from the
Global Customer Support website. These include the following:
♦ QF1287671 - the following applies to your Control Core Services v9.4 system only if
an FDC280 is being deployed in the system. To support detail displays updated for
22
5. V9.4 System Setup B0700SY – Rev C
Control Core Services v9.4 on legacy workstations and servers, workstations and serv-
ers with I/A Series software v8.2-v8.8 and Foxboro Evo Control Core Services v9.0-
9.2 have to have QF1287671 installed on them.
23
24
6. V9.4 Operational
Recommendations
This chapter provides recommendations that you may want to consider relating to Control Core
Services v9.4.
6.1 Workstation/Server Shutdown When Installing

Windows 10 Patches or Security Updates
When shutting down a workstation or server before installing Windows 10 patches or security
updates, follow these steps:
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 may or may not 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/server will load with Control Core Services run-
ning.
6.2 Migrating Existing Workstation or Server

with Windows 7 or Windows Server 2008 R2
Before migrating an existing workstation or server with a SoftIO card to Control Core Services
v9.4, you have to remove the SoftIO card from the workstation or server. The SoftIO card is not
supported on systems with Control Core Services v9.4.
6.3 System Configuration

6.3.1 Blue Screen Resulting from COMM10 Ports Configured
with Printers
With the release of Control Core Services v9.4, CCS does not boot host support COMM10s.
25
B0700SY – Rev C 6. V9.4 Operational Recommendations
6.3.2 Self-Hosting or Auto-Checkpoint Host Limitations (CP270s

or Later CPs)
When determining how many CP270s (FCP270s or ZCP270s) or FCP280s a boot host can sup-
port, it is recommended that you host up to eight1 CP270s or FCP280s by a single boot host
when the CPs are configured for self-hosting or auto-checkpointing.
These loading requirements are based partially on CP idle time and CP database size with a result-
ing 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 may use an equivalent number of FCP280s or FDC280s as well.
6.4 Software Installation

6.4.1 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 sys-
tem messages in the log. Make certain that you address every detected error and other similar sys-
tem messages appropriately before continuing with system setup.
The log viewer can be opened at any time after installation. Click the Start button, and select All
Programs -> Invensys -> IASeries -> Utilities -> Log Viewer.
For detected errors or other similar system messages, contact the Global Customer Support
(GCS) for assistance. Refer to the contact information on page xiii.
6.4.2 Performing a Day 1 Installation Procedure with Address

Translation Station (ATS)
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. If you do not do so, this can cause commu-
nications to become unavailable between nodes as ATSes route packets to the wrong destinations.
To stop this occurrence, change the install status to “PCHANG” for any existing OS1A70 (Opsys
for ATS) software package.
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.
1.
No more than eight when auto-checkpoint is configured for two hours.
26
6. V9.4 Operational Recommendations B0700SY – Rev C
The full procedure is provided in Control Core Services v9.4 Software Installation Guide
(B0700SX).
6.4.3 Successfully 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 worksta-
tion, 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 dis-
kette will not succeed, citing an incorrect media type.
If you want to create a Reconcile diskette for a Day 1 installation, first, create the diskette on a
workstation running the Windows operating system. Second, append the remaining Windows-
based platforms, and finally, append the UNIX platforms. Following this procedure allows you to
successfully create a Reconcile diskette.
6.4.4 Installations with Multiple CPU Core Feature

The multiple CPU core feature is auto-enabled on stations with Control Core Services starting
with the following platform versions:
♦ For Windows Server 2016, DL380 Gen9 server and later
♦ For Windows 10, Z440 workstation and later
Refer to 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.4 is intended to be run on stations with the multiple CPU
core feature turned on.
NOTE
Z420 workstations with Windows 10 currently shipped by Schneider Electric are
configured with settings which enabled multiple CPU cores. However, Z420 work-
stations shipped previously were installed with earlier releases of Control Core Ser-
vices and had not already been configured to use the multiple CPU core feature.
These previously shipped workstations will 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).
6.4.5 “Local Area Connection” Not To Be Renamed in Network

Connections
In Control Panel -> Network Connections, which lists the available NICs, it is inadvisable to
change the name of any “Local Area Connection x” network connection. This can result in soft-
ware installation issues or system instability.
6.4.6 NIC Configuration Settings

The settings of the network interface cards that connect to the Foxboro Evo Control Network
have to be configured such that Flow Control is disabled and Speed & Duplex is 100 Mb full-
27
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, Fox-
boro Control Software client/server activities, etc.
NOTE
It is inadvisable attempt to upgrade driver versions after installation of Control Core
Services as this may result in detected errors.
6.4.7 User Accounts for Local Edition Installations

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.
While logging in, every user account by default runs the same set of applications. This is because
there is a shortcut in the All Users Startup folder that invokes the Application Launcher. To cus-
tomize this behavior, you can remove this shortcut from the All Users profile and move it to some
other profile. For example, to the user account created during the Local Edition Control Core
Services installation.
6.4.8 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 Win-
dows Server 2016). If you need remote access to these stations and are willing to accept any result-
ing 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 the following 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.
One way to turn on these services is as follows:
1. Log in using a user account with Administrative privileges.
28
2. Start the Control Panel from the Start menu, click Administrative Tools, then
Services.
3. On stations with Windows Server 2016, proceed as follows:
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 drop-down menu.
4. On stations with Windows 10, proceed as follows:
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 drop-down menu.
6.4.9 Connecting 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.
6.5 Windows Workstations

6.5.1 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 set-
tings. 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 the following detected error message to appear on bootup of the worksta-
tion:
Your Xconfig Screen Definition settings are incompatible with your
current Display settings.
For example, the message will appear 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.
29
6.5.2 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 may enable the screen saver policy settings if you
want the logged on sessions to automatically log off when there is no activity for a specified period
of time. The Security Implementation User's Guide for I/A Series and Foxboro Evo Workstations
(Windows 10 or Windows Server 2016 Operating Systems) (B0700HG) document has information
related to these policy settings (search for “screen saver” in that document).
6.5.3 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 may
not be accessible by another user in normal (un-elevated) operations. For example, workfiles cre-
ated 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. Refer to the following link for more informa-
tion 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.
6.5.4 System Monitor Messages Reporting Unavailable

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

Unavailable
After power becomes unavailable, some of the System Monitors on Nodebus workstations may
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.
6.5.6 IP Address Displayed in the Exceed Icon

The new version of Exceed software (v15) that is installed with Control Core Services v9.4 or later
displays an IP address in the Exceed icon in the taskbar. If the NIC (network) connections are to
the Foxboro Evo 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.
30
6.5.7 Additional Security for Plant Operators and View Only

Users
In the appendix “Comparison of “Invensys Plant” GPOs” in Security Implementation User's Guide
for I/A Series and Foxboro Evo Workstations (Windows 10 or Windows Server 2016 Operating Sys-
tems) (B0700HG), the table “Group Policy Settings for I/A Series v8.8” (which also applies to the
Control Core Services v9.4) compares the group policy settings for the following Control Core
Services/I/A Series security groups:
♦ IA Plant Admins (the least restrictive policies)
♦ IA Plant Engineers
♦ IA Plant Operators
♦ IA Plant View Only (the strictest policies).
As shipped, the IA Plant Operators and IA Plant View Only groups are fairly restricted. However,
there are additional policies that may be set to enhance the security even further. These policy set-
tings are:
♦ Do not search for files
♦ Do not search Internet
♦ Do not search programs and Control Panel items.
While the “How to Edit Group Policies” section in Security Implementation User's Guide for
I/A Series and Foxboro Evo Workstations (Windows 10 or Windows Server 2016 Operating Systems)
(B0700HG) describes a generic procedure for editing Group Policy Objects (GPOs), more spe-
cific steps are provided here. Proceed as follows to edit these GPOs:
1. Login to the domain controller with an account that has domain administrator privi-
leges.
2. Open the Group Policy Management console.
a. Click the Start button and click Control Panel -> Administrative Tools.
b. Double-click Group Policy Management.
3. In the left pane of the Group Policy Management console, expand the Group Policy
Objects node.
4. Before editing a policy, it is recommended that you create a backup first. To create a
backup, right-click on the GPO and select Back Up.... In this case, the two GPOs
to back up are Invensys Plant Operators Filtered v1.0 and Invensys Plant View Only
Filtered v1.0, as highlighted in Figure 6-1.
31
Figure 6-1. Invensys Plant Operators/View Only Filtered v1.0 GPOs
5. In the Back Up Group Policy Object dialog box, specify a location where to save the
GPO backup (and a description) and click Back Up.
6. To edit a policy, right-click on the GPO in the left pane and select Edit, as shown in
Figure 6-2.
32
Figure 6-2. Editing GPOs
7. . The Group Policy Management Editor opens for the selected GPO. Expand the User
Configuration node in the left pane and navigate to the Start Menu and Taskbar
policy:
User Configuration -> Administrative Templates -> Start Menu and
Taskbar
8. At the top of the right pane, click on the Setting column heading to sort it by name.
33
9. Edit the settings highlighted below by double-clicking on them. In the dialog box that
appears, set them to Enabled and click OK as shown in Figure 6-3.
Figure 6-3. Editing GPO Settings
Optimally, the result appears as shown in Figure 6-4.
Figure 6-4. Edited GPO Settings
10. Perform steps 4 to 9 for both the Invensys Plant Operators Filtered v1.0 GPO and the
Invensys Plant View Only Filtered v1.0 GPO.
To make certain the settings take effect on a station, log off the station and log on as a user who is
a member of the IA Plant Operators or IA Plant View Only groups.
6.5.8 User Accounts after an Active Directory Migration

When performing a migration from a security-enhanced 8.5/8.6/8.7 installation to a security-
enhanced v8.8 or later installation, a new Active Directory structure with new Organizational
Units (OUs), Group Policy Objects (GPOs), and security accounts is put in place for I/A Series
software v8.8 or Control Core Services v9.0 or later. The Active Directory objects in older ver-
sions of I/A Series software are imported into the new Active Directory structure under OUs
whose names are prefixed with “Pre-8.8”.
34
Be aware that user accounts belonging to the older “Plant Maintenance,” “Plant Engineers,” and
“Plant Operators” security groups are not allowed to log on to computers running I/A Series soft-
ware v8.8 or Control Core Services v9.0 or later. Similarly, user accounts belonging to the new
“IA Plant Admins,” “IA Plant Engineers,” “IA Plant Operators,” and “IA Plant View Only”
groups added for I/A Series software v8.8 or Control Core Services v9.0 or later are not allowed to
log on to the computers running earlier versions of I/A Series software. This avoids confusion over
group policy settings that are different between I/A Series software v8.8 or Control Core Services
v9.0 or later and the prior releases, and avoids the possibility of changing the behavior on the sta-
tions with earlier versions of I/A Series software that are still in place.
6.6 Foxboro Evo Control Core Services Startup and

Security Options
Users with sufficient privileges may access and modify the Control Core Services start-up and
security options.
6.6.1 Foxboro Evo Control Core Services Startup Options

The I/A Series Startup Options control panel applet allows users with sufficient privileges to con-
figure whether to start the Control Core Services when the station is booted. To configure,
perform the following steps:
1. Click the Start button, and select Control Panel > Foxboro Evo Startup
Options.
Or
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 may disallow access to the Control Panel applets. Enterprise Edi-
tion Control Core Services use Group Policy Settings to restrict access. Refer to
Security Implementation User's Guide for I/A Series and Foxboro Evo Workstations (Win-
dows 10 or Windows Server 2016 Operating Systems) (B0700HG). Local Edition Con-
trol Core Services security settings are described in “Restricted Desktop” on
page 42.
2. A User Account Control (UAC) prompt appears.

A dialog box similar to the version shown in Figure 6-5 is displayed for users with
administrative rights (such as the Fox user account or users in the IA Plant Admins
group). For this dialog box, click Yes.
35
Figure 6-5. User Account Control Prompt for Control Core Services Users
with Administrative Rights
A dialog box similar to the version shown in Figure 6-6 is displayed for users without administra-
tive 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.
Figure 6-6. User Account Control Prompt for Control Core Services Users
without Administrative Rights
3. The “I/A Series Startup Options” dialog box opens, as shown in Figure 6-7 and
Figure 6-8.
36
Figure 6-7. I/A Series Startup Options Dialog Box (Enhanced Security)
Figure 6-8. I/A Series Startup Options Dialog Box (Standard Security)
4. Select the appropriate option:
37
♦ I/A Series On, Autologon - enables Control Core Services on startup and auto-
matically logon to a specified account.
♦ I/A Series On, Manual logon - enables Control Core Services on startup.
♦ I/A Series On, Autologon, restricted desktop access - enables Control
Core Services on startup and automatically logon to a restricted environment, as
described in “Restricted Desktop” on page 42. This option is not present on
Enterprise Edition Control Core Services stations.
♦ I/A Series On, 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” on page 42. This
option is not present on Enterprise Edition Control Core Services stations.
♦ I/A Series Off, Autologon - disables the Control Core Services from running
on startup (for example, to install additional software), disables access to the Fox-
boro Evo Control Network and automatically logon to a specified account.
♦ I/A Series Off, 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 Evo Control Network and automatically logon
to a specified account.
♦ I/A Series Off, Manual logon - disables the Control Core Services from running
on startup (for example, to install additional software), disables access to the Fox-
boro Evo Control Network.
♦ I/A Series Off, Manual logon with Mesh networking - disables the Control
Core Services from running on startup, (for example, to install additional soft-
ware) but retains access to the Foxboro Evo 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.
NOTE
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 invoked. Refer to
“Autologon” on page 41.
The restricted desktop options take effect on next logon and are described in detail on page 42.
The other options take effect on station’s reboot.
38
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, as
shown in Figure 6-9 and Figure 6-10.
Figure 6-9. I/A Series Startup Options Dialog Box for Domain Controllers
39
Figure 6-10. I/A Series Startup Options Dialog Box for Stations Not Running FoxView
If the startup options are invalid when the I/A Series Startup Options dialog box is
opened, a system message is displayed near the bottom of the dialog box as shown in
Figure 6-11. (This system message overwrites any descriptions of why options are dis-
abled). In this state, the OK button is disabled.
40
Figure 6-11. I/A Series Startup Options Dialog Box with Invalid Options (Enterprise Edition)
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 installa-
tion unless directed by the documentation.
6.6.2 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 subse-
quent logon attempts until at which time the I/A Series Startup Options utility is used to change
the credentials in use. This applies for both Enterprise Edition domain clients and Local Edition
stations.
41
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.
6.6.2.1 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 Enter-
prise Edition domain clients), and the password (in both fields) as shown in Figure 6-12. Click
OK.
Figure 6-12. Sample Autologon Configuration
NOTE
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.
6.6.3 Restricted Desktop

The restricted desktop options provide a security option on Local Edition Control Core Services
to limit user access on operator stations. When a user enables one of the Autologon,
42
restricted desktop access or Autologon, restricted desktop access and shut-

down access options, it results in the following:
♦ 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.
Figure 6-13. Start Menu in a Restricted Desktop
43
Figure 6-14 shows how you cannot change user settings, only sign out from the
account.
Figure 6-14. Cannot Change User Settings, Only Sign Out From Account
44
Figure 6-15 shows how there is no option to restart or shutdown the workstation.
Figure 6-15. 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 following:
♦ 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. Refer to “Foxboro Evo Control
Core Services Startup Options” on page 35.
6.6.4 Welcome Screen

The welcome screen is invoked by pressing Ctrl+Alt+Delete.
Only the commands the user has privileges to access are enabled in this screen. Figure 6-16,
Figure 6-17, and Figure 6-18 are examples of this screen for users with different type of privileges.
45
Figure 6-16. Sample Welcome Screen for IA Plant Operators and for Restricted Desktop and
Shutdown Access
Figure 6-17. Sample Welcome Screen for Restricted Desktop Access
46
Figure 6-18. Sample Welcome Screen for Standard Fox User and IA Plant Admins
This screen provides access to the following commands, depending on the current user’s privi-
leges:
♦ Lock - Disallows access to the station. The current user can unlock the station by log-
ging in. Refer to “Control Core Services Log Off and Shut Down” on page 47.
♦ Sign out - Closes the current user’s programs without turning off the computer.
Refer to “Logging Off ” on page 47.
♦ Start Task Manager - Opens the Windows Task Manager.
♦ Shut down - Shuts down the station. Refer to “Shutting Down/Restarting the Sta-
tion” on page 48.
♦ Restart - Reboots the station. Refer to “Shutting Down/Restarting the Station” on
page 48.
6.7 Control Core Services Log Off and Shut Down

The following 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.
6.7.1 Logging Off

Users may log off by performing one of the following options:
♦ Press Ctrl+Alt+Del to invoke 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, as shown in Figure 6-19.
47
Figure 6-19. Sign Out from the Start Menu
Once the station is shut down, every user on that station is logged off by the operating system.
6.7.2 Shutting Down/Restarting the Station

Users may shut down a station by performing one of these options:
NOTE
Security settings may keep the user 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. Refer to Security Implementa-
tion User's Guide for I/A Series and Foxboro Evo Workstations (Windows 10 or Windows
Server 2016 Operating Systems) (B0700HG). Local Edition Control Core Services
security settings are described in “Restricted Desktop” on page 42.
♦ Press Ctrl+Alt+Delete to invoke the Welcome Screen. Select Shut down or

Restart from the power options menu on the lower-right, as shown in Figure 6-20.
Figure 6-20. Restart and Shut Down Picks
♦ Click the Start button and select Shut down or Restart from the power options
menu.
48
Figure 6-21. Restart and Shut Down Picks with Full Access
♦ Use the menu selections in the SftMnt menu in the top menu bar of a FoxView win-
dow. (Users have to be in the Process Engineering or Software Engineering
environment.)
NOTE
FoxView or the Control Editors are the preferred methods to shut down a station.
NOTE
Normally, when a shut down or reboot is invoked on a running station, the
requested action takes place. However, if a shut down or reboot is invoked while a
system is trying to boot up, the system may 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.
6.7.3 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 as follows:
♦ srvcs42pwrsoe.dat
♦ procs42pwrsoe.dat
♦ srvcs75_cogpkg.dat
♦ procs75_cogpkg.dat
♦ srvcs07powerapps.dat
♦ procs07powerapps.dat
The following text is an example of the content in a srvcs25myapp.dat file:

# Names of services installed by the "myapp" package.
MyAppSvc1
49
MyAppSvc2
The following 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 pro-
cessed 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 pro-
cesses are killed. The following files are processed in this order:
♦ ia_srvcs.dat
♦ ia_procs.dat
6.8 Virtual Machines (VMs)

6.8.1 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. The following documents may be
reviewed 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 pro-
tections 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 manage-
ment commands and syntax.
♦ I/A Series Display Engineering for FoxView Software and Display Manager Software
(B0193MQ)
This document describes how to configure various settings in the FoxView environ-
ments. Refer to 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 Opera-
tion Topics” chapter.
50
6.9 Solaris 10 Stations

6.9.1 GNOME Session Manager Segmentation
Solaris 10 workstations may experience a GNOME Session Manager Segmentation Fault on
the Foxboro Evo 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.ora-
cle.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.
6.10 Object Manager Software

6.10.1 OM API register_name Function
When created, Application:Object.Atrributes (AOAs) are registered with the Object Manager via
the “register_name” function. This function and its return codes are not documented in Object
Manager Calls (B0193BC).
The OM API “register_name” function can return with a detected error code of 104. You can try
the operation again.
6.11 Tools and Utilities

6.11.1 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.
6.12 Displays
6.12.1 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 Evo system. 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.
51
6.12.2 Detail Display Differences on Workstations on

The Nodebus and The Foxboro Evo Control Network
The operation and appearance of Detail displays is different for workstations on the Nodebus side
versus workstations on the Foxboro Evo 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 Dis-
play 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.
6.13 Application Software

6.13.1 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 Enter-
prise 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.
6.14 Alarm Management Subsystem

6.14.1 Clearing Alarms from Alarm Displays
Up to 1,000 alarms can be cleared from an AM display at a time. If more than 1,000 alarms are
selected, a dialog box will popup indicating that only the first 1,000 selected alarms are cleared.
6.14.2 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 avail-
able.
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 actu-
52
ally 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, the following indicators are produced for alarm counts
and page counts respectively:
Alarm 88 of 97
Page 9 of 10
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 though 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.
6.14.3 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 refer to 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 sys-
tems, 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 manage-
ment 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 the following 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.
53
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).
6.14.4 Previously Deleted Alarm Manager Configuration Files

Previously deleted Alarm Manager configuration files are still shown in the Install Files Distribu-
tion dialog box. Create Install Files does not remove the old .cfg files, and Install Files Distribu-
tion 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.
6.14.5 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 con-
figuration options. Refer to Alarm and Display Manager Configurator (ADMC) (B0700AM) for
additional information.
6.14.6 Message Manager Software

The “Network Architecture for the Message Management Subsystem” section in Message Manager
User’s Guide (B0700AJ) states that Message Manager workstations have to be dedicated to Mes-
sage Manager and cannot run other applications. This is true for both redundant and non-redun-
dant control network configurations, as stated in B0700AJ.
Although running other applications generally works, it adds an additional load to the system so
that applications may not run as expected. For example, if you attempt to access the Current
Alarms Display on a workstation running Message Manager software, a message may appear stat-
ing 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.
6.14.7 Running a Single Message Manager

While running a single Message Manager (MM), if the MM becomes unavailable, then alarms
may 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 restart MM to work around this condition. Restarting the
MM forces a Current State Update (CSU) which forces the CP to send the current alarm state.
The alarms are resent provided the alarms have not already been acknowledged.
6.14.8 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.
The procedure to set Screen parameter is as follows:
54
1. From the select box in Display and Alarm Managers window, click Alarm
Managers.
2. Select the existing Default Alarm Manager scheme in list box and click Edit or
click New, to configure a new Default Alarm Manager.
Configuring the Alarm Manager scheme as described in step 2, 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.
6.14.9 Printing Alarm Priority to the Alarm Printer

PER1184037 provides the ability to print alarm priority to the alarm printer. To enable alarm pri-
ority printing, set the following registry entry on all workstations which 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 as follows:
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 will be modified as follows:
COMPOUND:BLOCK HIABS 5
10-20-14 18:07:17:8 24.0IN ( 20.00) HIGH LEVEL ALARM ALM
55
Figure 6-22. Use Priority Alarm Printing Style
56
Figure 6-23. Use Original Alarm Printing Style
6.15 Control Configuration Software

6.15.1 Detected Error Message When Deleting a Block or
Compound in ICCAPI
Occasionally, when deleting a block using the ICCAPI, the following 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 com-
pound. This message may also appear when a compound is deleted.
This message appears because the program is trying to delete a file that does not exist. This condi-
tion does not in any way affect the block delete operation, and this detected error message may be
ignored.
57
6.15.2 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.
6.16 Control Databases and Process Control

6.16.1 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 acknowl-
edgement 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 automati-
cally 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.
6.16.2 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 acknowledgement if an alarm priority is
lowered. This behavior occurs because a block has only one boolean acknowledgement status
parameter but can have multiple alarms with different priorities.
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; the block remains in the Unacknowledged state and an operator acknowledge-
ment is needed. The event history follows:
1. The AIN block has the following alarms tripped:
♦ High Absolute Alarm Indicator (HAI)
♦ High-High Absolute Alarm Indicator (HHAIND)
♦ High Out-of-Range Alarm (HOR)
♦ Bad input (BAD)
2. Alarms are acknowledged.
58
3. Out-of-Range alarm priority (ORAP) is raised from 3 to 2. This action causes the
block alarm state to be set to Unacknowledged.
4. 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 chapter titled “Block/Process Alarming” in Control Processor 270 (CP270) and Field Control
Processor 280 (CP280) Integrated Control Software Concepts (B0700AG) describes the details of
alarm reprioritization, specifically, the preservation of alarm acknowledgement status following re-
alarming.
6.16.3 Changing 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 may 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.
6.16.4 Dynamically Reconfiguring a Block Parameter

Dynamic reconfiguration is a procedure where a user modifies a block parameter with a configu-
ration tool like ICC while a loop containing the to-be-modified parameter is running. Dynami-
cally reconfiguring a block parameter may 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 may result in non-deterministic behavior.
For example, blocks connected to the block being modified may 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_SEC_OPT) in the STATION block’s
CFGOPT parameter. Refer to Integrated Control Block Descriptions (B0193AX) for a description
of this parameter.
6.16.5 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 Ser-
vices to modify bits and registers in a PLC associated with a PAKOUT control
block.
59
For example, take a PAKOUT block associated with registers 40010 through 40013 in a Modbus
device, and assume the following sequence of steps occurs:
1. If the Control Core Services initially set the bits to 0, each of the four registers in the
device are set to 0.
2. Another source sets the value of register 40011 to 1.
3. The Control Core Services want to set a bit in register 40010 to 1.
4. When the Control Core Services write its value, it succeeds in setting the bit in regis-
ter 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.
6.16.6 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 may cause situations in which one FBM will not take over
properly for the other, or in which the CP may send empty packets to the FBMs and cause traffic
on the PIO bus.
6.16.7 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.
6.17 Control Processor (FCP280, FCP270 and

ZCP270)
6.17.1 Use of Self-Hosting Feature
The self-hosting feature is recommended only for use in FCP280s and CP270s which are used
with 200 Series FBMs, or similar modules such as those included in the intrinsically safe I/O sub-
system. It is not recommended for use when the FCP280s or CP270s are controlling any
100 Series FBMs (Y-module FBMs) or 100 Series FBM based migration cards including Cluster
I/O.
All the information that 200 Series FBMs (or similar modules in the intrinsically safe I/O subsys-
tem) need to operate correctly is either burned in the flash of the FCP280s and CP270s or is
included in the checkpoint file. This means that if a 200 Series FBM (or similar module) needs to
reboot and go on-line after a power cycle, it is able to do so without the presence of a boot host
60
workstation. However, 100 Series FBMs have a different behavior. If a 100 Series FBM is power-
cycled, it downloads information it needs to operate correctly from a boot host workstation. If an
FCP270 is running in self-hosting mode and the boot host workstation is unavailable, the
100 Series FBM will not be able to boot or go on-line.
If desired, you can minimize the occurrence that 100 Series FBMs will need to boot up by making
certain that the 100 Series FBMs are mounted on a rack with a battery back-up or an Uninter-
ruptable Power Supply (UPS). With this type of configuration, as long as the I/O source does not
need to boot up, the 100 Series FBMs will reconnect when an FCP270 comes back on-line.
6.17.2 Issuing a Reboot Command for a Shadow FCP280 or

CP270 Module
If you invoke 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.
6.17.3 Addressing 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\'
6.17.4 Installing or Replacing FCP280, CP270, and FCM100

Modules in a Running System with I/A Series SoftwareV8.x or
Foxboro Evo 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. Perform the following steps:
1. Power up the station without any cables.
2. For CP270, set the letterbug to “NOSUCH” with the PDA. Refer to Letterbug Con-
figurator (B0700AY) for procedures on setting letterbugs.
For FCP280, set the letterbug, as described in Field Control Processor 280 (FCP280)
61
User's Guide (B0700FW), even if it is set to the same letterbug already set in the mod-
ule.
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
Once the station is flushed, you can then add the station to the system.
To add 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 perti-
nent information it needs from the primary module.
3. The two modules will then marry and begin running as a pair.
To add a single FCP280, CP270, or FCM:
1. Power up the module without any cables. For CP270, set the system letterbug to with
the PDA. Refer to Letterbug Configurator (B0700AY) for procedures on setting letter-
bugs.
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.
6.17.5 Setting Primary ECB Parameter BAUD2M for 100 Series

FBMs
For Control Core Services v9.0 or later, the Primary ECB contains the BAUD2M parameter,
which is only used with the FCP280. This parameter defines the baud rate at which the HDLC
fieldbus (PIO channel) associated with the Primary ECB will operate:
♦ 1 = 2 Mbps (default) - for 200 Series FBM and similar modules
♦ 0 = 268 Kbps - for 100 Series FBM and competitive migration modules
These are named PRIMARY_ECB, PRIMARY_ECB2, PRIMARY_ECB3, and
PRIMARY_ECB4; PRIMARY_ECB2 is associated with the HDLC fieldbus for Fieldbus port 2
(PIO channel 2), etc. PRIMARY_ECB, the Primary ECB for Fieldbus port 1, excludes the PIO
channel number in its name to maintain compatibility with existing FCP270/ZCP270 databases
and applications to make migration easier.
If you are using 100 Series FBMs on an FCP280’s HDLC fieldbus, make certain that the
BAUD2M parameter in the Primary ECB for that HDLC fieldbuses is set to “0”.
For details on how to set this parameter with our control configurators, refer to:
♦ ICC - Integrated Control Configurator (B0193AV)
♦ IACC - I/A Series Configuration Component (IACC) User's Guide (B0700FE)
♦ Control Editors - Block Configurator User's Guide (B0750AH).
62
6.18 Field Device Controller 280 (FDC280)

6.18.1 FDC280 IOM Image
As indicated in Table A-1 “Control Core Services V9.4 Control Station and ATS
EEPROM/Image and Software Revision Levels” on page 103, FDC280s may exist with either
image revision 0900009000 (shipped with Control Core Services v9.3) or 0900010000 (shipped
with Control Core Services v9.4). 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”.
If your FDC280 has image revision 0900009000, it is highly recommended that you upgrade to
0900010000. The 0900010000 image is available on all workstations/servers with Control Core
Services v9.4. Install it as described in “Major Image Update Procedure for Upgrading FDC280s
Acquired Previous to Control Core Services v9.4” on page 63.
6.18.1.1 Major Image Update Procedure for Upgrading FDC280s

Acquired Previous to Control Core Services v9.4
Proceed as follows to perform a Major Image Update to update an FDC280 with image revision
0900009000 to 0900010000 via a workstation/server with Control Core Services v9.4. Be
advised that this procedure requires you to potentially remove hardware in the field.
1. Using the Control Software, un-deploy the complete FDC280 controller.
2. Reboot the FDC280 using the System Manager, as described in System Manager
(B0750AP).
3. Select the icon for the FDC280 in the Navigation Pane.
4. Confirm that the download operation is currently enabled in System Manager. If it is
not, right-click the FDC280 and click Enable Download.
To confirm that download is currently enabled, verify that the Equipment Change
submenu lists Disable Download as one of its selections.
5. If the FDC280 is running fault-tolerant, remove the Shadow module from the base-
plate so the FDC280 is now running in single mode. The Shadow module must be
removed to complete this procedure.
6. Right-click the FDC280 and click Major Image Update.
7. The Major Image Update confirmation dialog box appears. Click OK to confirm the
update.
8. The FDC280 downloads the image from the host, and messages are sent to the Sys-
tem Monitor log (smon_log) and the printer to indicate progress.
9. After the image is downloaded from the host and written to its flash memory, the
module reboots from the newly installed OS file.
10. The image update is complete. The total elapsed time for the update process is
approximately eight minutes.
11. To verify the new image revision levels, use the Equipment Information display in the
System Manager to view the updated image version in the “Primary Core 1 Image
Revision” and “Primary Core 2 Image Revision” fields.
63
12. To verify the FPGA revision levels, when the FDC280 completes its boot-up, a mes-
sage is sent to the SMON Log identifying “Revision D” of the FPGA is embedded in
the module.
13. If the FDC280 was running in fault-tolerant mode prior to the Major Image Update,
remove the running FDC280 from the baseplate and plug-in the module that was
removed in step 5. If the FDC280 was not running in fault-tolerant mode, skip to
step 22.
14. In System Manager, right-click the FDC280 and click Major Image Update.
15. The Major Image Update confirmation dialog box appears. Click OK to confirm the
update.
16. The FDC280 downloads the image from the host, and messages are sent to the Sys-
tem Monitor log (smon_log) and its printer to indicate progress.
17. After the image is downloaded from the host and written to its flash memory, the
FDC280 reboots from the newly installed OS file.
18. The image update is complete. The total elapsed time for the update process is
approximately eight minutes.
19. To verify the new image revision levels, use the Equipment Information display in the
System Manager to view the updated image version in the “Primary Core 1 Image
Revision” and “Primary Core 2 Image Revision” fields.
20. To verify the FPGA revision levels, when the FDC280 completes boot-up, a message
is sent to the smon_log identifying “Revision D” of the FPGA is embedded in the
module.
21. If the FDC280 was running fault-tolerant prior to installing the Quick Fix, insert the
module that was removed in step 13.
22. Redeploy the database that was saved at the beginning of this process.
6.18.2 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 or more. Tricon/Tri-
dent devices sometimes need the extra time to respond after connections are re-established.
64
6.19 Address Translation Station (ATS)

6.19.1 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.
6.19.2 Station Support for Address Translation Station

Address Translation Stations (ATSes) support connections on the Foxboro Evo Control Network
for the following Foxboro Evo and I/A Series stations:
♦ Triconex Advanced Communications Module in the Tricon™ controller (for connec-
tions to the FoxGuard Manager).
♦ Allen-Bradley Integrator 30 Style B
♦ Modicon Integrator 30 Style B
♦ Device Integrator 30 Style B
♦ Legacy Control Processors2 CP30, CP30 Style B, CP40, CP40 Style B, and CP60
These stations have to have the minimum firmware revisions listed in Table 6-1 in order to oper-
ate with the ATS:
Table 6-1. Minimum Versions for Nodebus Stations Running on

The Foxboro Evo Control Network
Minimum Firmware
Station Type Revision Minimum OS Image
CP60 3.30 6.5.3
CP40B 3.30 6.1.6
2.
These control processors have been withdrawn from sale.
65
Table 6-1. Minimum Versions for Nodebus Stations Running on

The Foxboro Evo Control Network (Continued)
Minimum Firmware
Station Type Revision Minimum OS Image
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)1
1.
When the host station of the Triconex ACM on the control network is run-
ning 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.
6.19.3 Network Unavailability Detection Logs

The NFD logging feature introduced on workstations with I/A Series software v7.x is also avail-
able on Address Translation Stations. For each ATS hosted by a workstation, the following 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 reg-
istry 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.
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 emp-
tied.
66
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-exis-
tent 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 the user, 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.
6.20 Intrinsically Safe I/O Subsystem

6.20.1 Using SRD991 with the Intrinsically Safe I/O Subsystem
The revision 3.2 (firmware revision 14) or later SRD991 HART Intelligent Positioner interoper-
ates 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, refer to Intrinsi-
cally Safe I/O Subsystem User's Guide (B0700DP).
6.21 Fieldbus Modules (FBMs) and Field

Communication Modules (FCMs)
6.21.1 Redundant FBM248 Pulse Count
Because of the way redundancy is implemented, some changes in redundancy status (Mas-
ter/Tracker settings, FBM being reset, or FBM module insertions) may result in the pulse count
indication to increment by one count on channels set as “pulse input”. This happens only in volt-
age input pulse mode, and can be mitigated by carefully inserting or extracting modules perpen-
dicularly into the baseplate. Since resetting a module is a redundancy status change, it may occur
after a module is reset by an operator using a control configurator application and the channel
count may not appear to stay at zero.
6.21.2 Configuring 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.
67
6.21.3 Master/Tracker FBM222 Role Switches

When the FBM222 switches roles, that is, Master becomes Tracker and Tracker becomes Master,
a few messages on the PIO Bus may be lost and not responded to by the FBM222. In some cases
this may result in the message PIO Bus Access Error in the System Monitor log. This condi-
tion is normal since it takes the FBM222 some time to switch.
6.21.4 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.
6.21.5 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.
The simplest procedure needs an unused slot pair in a system to perform the upgrade. An alter-
nate procedure is provided in case there are no unused slot pairs in the system, but this needs the
use of a spare FBM216.
Perform the following procedure 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 mod-
ule. 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.
Perform the following procedure if an unused slot pair is not available. This procedure needs for
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.
68
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 may 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).
6.21.6 Duplicate Channel Numbers for FoxCom Transmitters

(ECB18) and FoxCom Valves (ECB74)
No checking is done for duplicate channel numbers when configuring ECBs for FoxCom trans-
mitters (ECB18) or FoxCom valves (ECB74). In general, be especially careful the I/O points are
both configured and wired correctly.
6.21.7 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 redun-
dant pair. To configure the FCM as simplex, set the FCMCFG parameter in the ECB210 to
0x04, which sets Bit 2 of FCMCFG.
Figure 6-24 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.
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
FCM100E Simplex/Redundant
Configuration Bit
Figure 6-24. Setting the FCMCFG Parameter for Simplex Operation of the FCM
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 “warn-
ing” condition, and a system alarm is generated.
69
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 will cause the module to become unavailable in a constant
reboot cycle.
6.21.8 Validating Compact PROFIBUS Configuration File

During the validation of the slave configuration file for any compact PROFIBUS device, the fol-
lowing messages will 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 the above messages as they are not needed in the gsd file for compact PROFIBUS devices.
6.21.9 Performing General Downloads

This note only applies if a ZCP270 is being used.
When performing a general download after a LoadAll, you must pick the GENERAL DOWN-
LOAD key twice. The first pick downloads each of the FCMs and the second downloads all the
FBMs.
6.21.10 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 soft-
ware 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 condi-
tion), and then the old master gets downloaded.
6.21.11 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 cor-
rect 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 num-
70
ber 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 may find that the FBMs are now getting rate of change alarms where they had not been get-
ting 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 val-
ues 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 will make the FBMs respond to rate of
change as they did before the software update.
6.21.12 Configuring Fail-Safe for Proper Operation of FBM218

Proper operation of the redundant FBM218 needs that the fail-safe parameters in the ECBs asso-
ciated 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 opposite (available) FBM to assume (or
continue) control without interference from the unavailable module.
6.21.13 EEPROM Updating FBM220 and FBM221

Before you perform an EEPROM update on an FBM connected to a FOUNDATION fieldbus posi-
tioner, 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 may not retain its configured faultstate value.
6.21.14 Field Device System Integrator (FDSI) Subsystem

6.21.14.1 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. Select Remove to uninstall the driver.
6.21.14.2 FDSI FBMs May 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) may result in
temporary I/O connections unavailability.
6.21.14.3 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.
71
In certain situations, you may 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 may 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. Refer to 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.
6.21.14.4 EEPROM Updating FDSI FBMs (FBM230 to FBM233)

After performing a Day 0 Control Core Services installation, you have to 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 revi-
sion levels, refer to Appendix A “EEPROM Revision Levels”.
When EEPROM updating these FBMs, you may encounter problems getting the FBMs to go on-
line. In extreme cases of difficulties making the FBM operational after the update, it may be nec-
essary to do a delete/undelete of the ECB for the FBM, or even to reboot the controller that is
hosting the FBM.
6.21.15 Displaying 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 may 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.
6.21.16 FBM223 PROFIBUS Configurator

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

Changing the FSENAB (“fail-safe enable”) parameter from 0 to 1 on an ECB200 that is config-
ured for PROFIBUS-DP FBM223 may 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.
6.21.18 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.
72
6.21.19 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 contin-
ues and every read of those modules results in a time out. Since time outs take six times as long as
normal reads, this may lead to CPU overruns.
6.22 FOUNDATION fieldbus, PROFIBUS-DP, HART,

Modbus, DeviceNet, and FDSI
6.22.1 DeviceNet Baud Rate
Modifying the DeviceNet Baud Rate is a very unusual configuration change, but if it is necessary,
consider the following:
1. The recommended DeviceNet Baud Rate is 125 kBaud. It is very unusual that higher
Baud rates are needed.
2. 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.
3. 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.
4. 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 may need to be moved to a different segment where a third party tool can
be used to change the Baud Rate settings.
5. Any third party tool used for device configuration (for example RsNetworx) will also
need to be changed to the new Baud Rate.
6.23 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 pro-
cessor, 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 con-
figurable.
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
73
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.
6.24 Data Transfers Between the Nodebus and The

Foxboro Evo Control Networks
I/A Series software v8.2-v8.8 or Control Core Services v9.0 and later supports inter-network traf-
fic between the Foxboro Evo Control Network and Nodebus networks using ATSs. However, you
need to make certain that stations that migrate to the control network and continue to communi-
cate 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 rec-
ommended. Avoid using the Nodebus for large data transfers; use a separate network instead.
74
7. V9.4 User Notes
This chapter contains user notes for the Control Core Services v9.4 release.
7.1 Software Installation

7.1.1 Installation of Foxboro Evo Control Software 6.0.x, v6.1-
v6.2, or v7.0-7.1 on Control Core Services v9.4
Before Foxboro Evo Control Software 6.0.x, v6.1-v6.2, or v7.0-7.1 can be installed on a station
with Control Core Services v9.4 installed, you have to modify the SYSLVL file manually. Proceed
as follows:
1. Backup your existing SYSLVL file.
2. On the station with Control Core Services v9.4 installed, navigate to the folder
<IADrive>\usr\fox\sp\lastinst. In general, <IADrive> is D:\.
3. Verify the SYSLVL file is available in this directory as shown in Figure 7-1.
Figure 7-1. SYSLVL File Location
4. Open the SYSLVL file in Notepad, or a similar text editor.

5. Verify the entries in the file, as shown in Figure 7-2.
75
B0700SY – Rev C 7. V9.4 User Notes
Figure 7-2. SYSLVL File Contents - Default
6. Modify the entry “9.4.xx” to “9.2” and save the file, as shown in Figure 7-3.
Figure 7-3. SYSLVL File Contents - Modified
76
7. V9.4 User Notes B0700SY – Rev C
7. First install your version of Foxboro Evo Control Software 6.x as described in the ver-
sions of Foxboro Evo Control Software Installation Guide (B0750RA) and Foxboro Evo
Control Software Deployment Guide (B0750BA) included with the software.
8. After the successful installation of the control software, use Notepad (or similar text
editor) to replace the “9.2” value in the SYSLVL file with original value “9.3.xx”
and save the file.
9. Install Foxboro Evo Control Software 6.0.x, v6.1-v6.2, or v7.0-7.1 as described in the
versions of Foxboro Evo Control Software Installation Guide (B0750RA) and Foxboro
Evo Control Software Deployment Guide (B0750BA) included with the software.
7.1.2 Reconcile Utility

For general instructions on using the Reconcile utility, see the appropriate installation guide doc-
ument for the version of Foxboro Evo Control Core Services installed. The following minor
changes are made to the workflow:
♦ In order to retrieve reconcile files from Local Edition workstations, the credentials
must be entered for the newly named user account or for existing ‘Account1’ user
account workstations.
Figure 7-4. Retrieve Reconcile Files
While retrieving reconcile information, a station may not connect with the following message:
ERROR_SESSION_CREDENTIAL_CONFLICT. If this happens, check to see if the worksta-
tion is externally mapped as a network drive in Windows File Explorer. If the workstation is exter-
nally mapped, disconnect the mapped drive and resend the device configuration file. If the
workstation is not externally mapped, the workstation needs to be rebooted.
77
7.2 Windows Workstations

7.2.1 Messages Appearing Post-Installation for Domain
Controllers
After completing the Control Core Software installation on a domain controller and attempting
to log on with the “IA Installer” user account, the following messages may appear:
♦ “Remote procedure call failed”
♦ “Location is not available.” - This message refers to the following location:
“C:\Windows\system32\systemprofile\Desktop”
This is a transient condition. It may be necessary to reboot the domain controller once or
twice before the condition clears.
7.2.2 Printer Monitor System Message in SMON Indicates

Normal Operation
The Printer Monitor process (PrnMon) monitors a network printer and periodically polls the sta-
tus of printer in every 30 seconds. Occasionally the network printer may not respond to the poll
and PrnMon sends the following report to the System Monitor (SMON) for the printer: “Warn-
ing Condition Exist With Critical Alerts”
On the next cycle polling, the printer will respond to the query from PrnMon. SMON will gener-
ate the following message for the printer: “Online And Available”. These messages may appear in
the smon_log, but they do not indicate any harm to the system.
7.2.3 System Manager Does Not Succeed In Removing Database

Locks Resulting in “Cannot Initiate Action” Message
If you initiate an action such as an EEPROM Update or Reboot on a station through System
Manager, it is possible for the station database to become locked. This happens when the System
Monitor (SMON) which hosts this station goes offline (such as if the SMON host workstation is
rebooted) prior to the action request but before System Manager has been notified that the
SMON is unavailable. This also could occur when the SMON is too busy to send the action
response message in time.
Once the SMON becomes available again, it will not be possible to perform any more actions on
this station until the lock is cleared. This would need a manual removal of the lock. The following
steps can lead to this result.
♦ Initiating EEPROM Update or Reboot action for a station
♦ Rebooting the SMON host workstation
♦ Waiting for the SMON host workstation to come back online
♦ Attempting to initiate an EEPROM Update or Reboot action for the same station
78
The following messages appear in the System Manager as a result of the initial action request
when SMON has stopped responding.
Figure 7-5. System Manager Messages for Initial Action Request Following SMON
Stopped Responding
Once the SMON becomes available, after the SMON host workstation reboot, the following
messages appear in the System Manager upon further requests to take an action on the affected
station.
Figure 7-6. System Manager Messages for Further Requests To Take Action On
Affected Station
In order to clear the lock file, navigate to the D:\usr\fox\sp\locks folder and remove the lock file
which will have the following name:
f<LETTERBUG>+
The file can be seen in Figure 7-7.
79
Figure 7-7. Clearing the f<LETTERBUG>+ Lock File
7.2.4 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 ter-
minates. There is a possibility that if a previous checkpoint action aborted abnormally it may not
remove the file. As a result, the operator would no longer be able to checkpoint any stations suc-
cessfully.
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.
7.2.5 User Access Shared Folders Between Workstations with

Windows 10 and Windows XP
Share access between workstations with Windows XP and Windows 10 using the \\<machine-
name> 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 Win-
dows 10 will work.
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.
To enable SMB1 feature, proceed as follows:

1. Open PowerShell in admin mode (Run as Admin)
2. Execute the command:
Enable-WindowsOptionalFeature -Online -FeatureName SMB1Protocol
80
3. The workstation will ask 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 and Windows 10 works correctly.
7.2.6 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 secu-
rity environment on the V91 host restricts the access of untrusted network devices, such as net-
work file servers, to protect against potential vulnerabilities. If you need to access these untrusted
network drives, you may enable access using this procedure.
Proceed as follows:
1. On the V91 host, login as a user with administrator privileges.
2. Right-click on 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 Set-
tings -> Local Policies -> Security Options node.
6. On the right-hand side, double-click on the Microsoft network client: Digi-
tally sign communication (Always) setting and select Disabled. Click OK.
7. Navigate to Computer Configuration -> Administrative Templates -> Net-
work -> Lanman Workstation node.
8. On the right-hand side, double-click on the Enable insecure guest logons set-
ting, and select Enabled. Click OK.
9. Close the Local Group Policy Editor.
10. Right-click on Windows menu and select Command Prompt (Admin). In the User
Access Control dialog box which appears, click Yes
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:
1) Computer Configuration -> Windows Settings -> Security Settings ->
Local Policies -> Security Options
Microsoft network client: Digitally sign communication (Always) - Enabled
2) Computer Configuration -> Administrative Templates -> Network ->
Lanman Workstation - Enable insecure guest logons - Disabled
81
7.3 Applications
7.3.1 FoxDraw
7.3.1.1 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.
7.3.1.2 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 may appear, which states, “Do you wish to convert the display to
Widescreen format?”. Moving this dialog box around the screen leaves trails and obscures the
background. This may also occur for the dialog box which states, “Opening a Display Configured
in Widescreen Will be Read Only”, which opens when a widescreen (wsmfdf ) display on a stan-
dard definition (4:3 aspect ratio) monitor is opened. These trails may not disappear when the dia-
log boxes are closed. It is recommended that you do not move these dialog boxes when they
appear.
7.4 Device Monitor

7.4.1 Device Monitor Master Active on Isolated Segments of
Foxboro Evo Control Network
It is recommended that you install QF1302638 on every station with I/A Series software v8.8
through Control Core Services v9.2 in order to provide the latest Device Monitor functionality
on those stations and consistency between these and the new workstations running Control Core
Services v9.4 and later. The following issue still persists, even in the presence of this Quick Fix.
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 may become active on the isolated
portion of the network. When the network isolation is resolved, the Device Monitor Master sta-
tions recognizes that there is more than one Master station and the Master station with the high-
est version will take over. When this happens, the Master station which takes over may 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 may not have
the latest up-to-date status of alarm destinations on that portion of the network. A symptom of
this is that alarms may not be delivered to those stations even though they are online.
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 net-
work. 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).
82
2. Type the following command and press <Enter>: D:\usr\fox\cs\dm_recon

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 the following command and 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
NOTE
It is inadvisable to boot up a workstation while disconnected from the Foxboro Evo
Control Network and then connected to this network. When a workstation is
booted up offline, it will assume Device Monitor Mastership and when connected
to the control network, it will cause a conflict with the existing Device Monitor
Master. This could result in the unavailability of alarms or control processor slow-
down. 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.
7.5 Control Processors

7.5.1 I/O Load (Fieldbus Scan Load) Increase Due to Unavailable
or Disconnected Fieldbus Channel
Be advised that an unavailable or disconnected fieldbus channel may 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 will cause
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 dif-
ference 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.
7.5.2 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. To do so, proceed as follows:
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
83
Figure 7-8. Offline Diagnostics dialog box
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.
Refer to “Offline Diagnostics” in System Manager (B0750AP) for more details about offline diag-
nostics.
84
7.6 Control Network Interface

7.6.1 Disabling Reporting Unavailability of Single Power Supply
for CNIs via System Key in Foxboro Evo System Monitor
Applications
By default, in an optimal situation, a single or fault-tolerant Control Interface Network (CNI) is
running with redundant power supplies. In the various Foxboro Evo system monitor applications
(System Manager, SMDH, FoxView, and Foxboro Evo Control HMI), if one of a pair of redun-
dant power supplies is missing or fails, the System key in the application monitoring the power
supplies remains in its original color and turns red.
Alternatively, for a CNI station with a single power supply, the System key can indicate an
unavailability or loss of this power supply by remaining the same color and not blinking. To use
this alternative behavior, you have to create a file named “rdpwer_noblink.cx”.
Also be aware that the System Monitor application controls the behavior of the System key based
on whether or not it can find the rdpwer_noblink.cx file. This rdpwer_noblink.cx file is not pres-
ent on a Foxboro Evo workstation/server by default.
To switch the System key from its default behavior to the alternate behavior to indicate a unavail-
ability or loss of a single power supply used with an CNI (detailed in Control Network Interface
(CNI) User's Guide (B0700GE)), proceed as follows:
1. Identify the host workstation for the CNI’s System Monitor application.
2. On the identified workstation, stop the System Monitor processes.
a. Open the Task Manager.
b. Select the Processes tab to organize processes by alphabetical order.
c. Highlight one of the smon_ech.exe processes and select End Process Tree.
3. Using Windows Explorer, navigate to the d:/usr/fox/sysmgm/sysmon directory.
4. In this directory, create a file named rdpwer_noblink.cx.
5. Restart the System Monitor.
a. In Windows Explorer, go back two folders to the d:/usr/fox/exten folder.
b. Double-click on the go_smon.cmd script.
The System key will no longer turn red and blink when the unavailability or loss of a CNI’s single
power supply is detected. It will exhibit the alternate behavior described above.
Repeat this procedure on the System Monitors hosting CNI stations.
7.6.2 Continuous Reboot of Fault-Tolerant CNI Pair Following

Change in Letterbug
When a fault-tolerant CNI pair are simultaneously powered up and have different assigned sta-
tion addresses (but share the same letterbug), they continuously try to synchronize their station
addresses and reboot.
To avoid this situation, make certain only one of the CNIs is powered, change the letterbug and
then connect the CNI to the Foxboro Evo Control Network so that it may obtain its new station
address. Then plug in the second CNI to form the fault-tolerant pair. In doing so, the second
CNI automatically obtains its letterbug and station address.
85
To recover from this continuous reboot scenario, proceed as follows:

1. Unplug one of the two CNIs.
2. Change the first CNI’s letterbug if needed.
3. Reconnect the CNI’s baseplate to the Foxboro Evo Control Network and power cycle
the baseplate. Wait for 30 seconds, during which the first CNI might reboot once.
4. Plug in the second CNI to form the fault-tolerant pair. During the marriage process,
the second CNI obtains the letterbug and station address automatically.
7.6.3 Empty Engineering Units Field Can Lead to Delays in

FoxView Trend Display Callup
The typical default method of displaying engineering units for a FoxView Trend display is by per-
centage “%”. If you change those units to be empty or blank, FoxView sends a message to retrieve
the engineering units. CNI does not fully support that message (“glof ”, a.k.a. “global_find”),
which can result in a garbage string being displayed (see the bottom half of Figure 7-9 below), and
a four second timeout per engineering units string on the display. Also, if the units contain gar-
bage character(s) from a previous display of the trend, the same timeout delay is experienced.
To resolve this concern, use FoxView's Trend Pen Configurator to enter a valid Engineering Units
string. If the block does not have Engineering Units (such as a sequence block), a suggested string
is the period character “.”, which avoids the four second timeout, would not be confused with a
real engineering units string, and is unobtrusive.
86
Figure 7-9. Trend Pen Configurator in FoxView With Garbage String Displayed
7.6.4 Resolving Graphical Corruption with Foxboro Evo Control

HMI Displays Showing Data from CNIs
If a Foxboro Evo Control HMI display is invoked while a remote CNI is rebooting, after the
remote CNI has finished rebooting, the display may show the following:
♦ Engineering Units show squares.
♦ Graphic bars do not appear.
♦ None of the above show expected cyan (OOS) values.
♦ Data values reconnect and update as expected.
To resolve this concern, refresh the display.
7.6.5 Remote Attributes on Displays Take Minutes to Show

Initial Values On Invocation
This event can occur any time after a CNI reboot if displays with remote attributes are opened
and closed during the CNI’s boot up and there is a significant number of static Historian or peer-
to-peer connections configured through the CNI.
This results in suboptimal grouping of points in the remote CNI, increasing the amount of time
it takes to remove points opened by displays being closed.
87
To recover from this condition, proceed as follows:

1. Stop closing and opening displays with remote points until each of the points show
values. This may take several minutes.
2. Once the attributes are connected, slow down the rate at which displays are closed to
less than 10 attributes per second on average to avoid recurrence.
If this action is not feasible, an alternative recovery action is as follows:
1. Close the displays which have remote attributes.
2. Reboot the local CNI, wait for the “STATION READY FOR IMAGE OPERA-
TIONS” message to appear on the System Monitor client by which time most of the
static connections are made.
Future display connections will not exhibit this behavior.
To disallow this condition from occurring, it is inadvisable to close and open displays with remote
attributes while rebooting the CNI.
For displays that are frequently opened and closed, configure Historian connections so that these
connections are always present.
7.6.6 Monitoring Change Driven Updates per Second Between

Connected Control Network Interfaces
A CNI supports 2000 change driven updates (value, status, timestamp) each second cumulative
between incoming and outgoing data. When online, it is possible to establish the approximate
number of incoming and outgoing updates per second to help determine the throughput capacity
that is being utilized.
There are two CNI-specific Object Manager shared variables available, _BPSIN and _BPSOUT,
that indicate the number of incoming and outgoing data bytes flowing between the CNIs.
Although these variables cover traffic for all messages between CNIs to acquire the most represen-
tative view of change driven updates the conditions below need to be met:
♦ Connections are already established and not changing
♦ Displays are not being opened/closed
♦ There are a negligible number of Alarm and Events being forwarded
Each change driven update consumes approximately 24 bytes, thus:
♦ _BPSOUT / 24 = outgoing change updates per second
♦ _BPSIN / 24 = incoming change updates per second
Monitoring these values for various plant operating conditions assists in determining the level of
throughput capacity that is being consumed under these different circumstances.
7.6.7 Virtual Router Redundancy Protocol (VRRP) Failover

Performance
Plants with multiple Foxboro Evo or I/A Series systems may share process control data among
these systems using the Control Network Interface (CNI). To connect the CNIs, the Foxboro Evo
Process Automation Systems or I/A Series systems use S-Series, N-Series, C5-Series, or X-Series
switches or SSA chassis managed switches configured as routers and implement VRRP for net-
work redundancy.
88
Failover times for conditions involving the unavailability of a single path between the routers of
the SSA chassis managed switches are typically one second. (This varies depending on the switch
used - refer to EcoStruxure Foxboro DCS Switch Configurator Application Software for the Control
Network User's Guide (B0700CA) for more information.) With active devices in the VRRP path,
failovers can take between 25 and 60 seconds.
The SSA chassis managed switches are discussed in The Foxboro Evo Control Network Hardware
Instructions for S-Series Switches (P0973KD/P0973KK/P0973LN) (B0700CE).
7.6.8 Access List Editor

For general instructions on using the Access List Editor for CNI deployment, refer to Control Net-
work Interface (CNI) User's Guide (B0700GE). The following minor changes are made to the
workflow:
1. In order to distribute the Device Monitor configuration files to Local Edition CCS
workstations, the credentials must be entered for the newly named user account or for
existing ‘Account1’ user account workstations.
2. After deployment to CNIs, it is possible to redeploy the Device Monitor configura-
tion file to workstations for which incorrect credentials have been provided. This
option will only be available as long as the Access List Editor remains open. Closing
the Access List Editor will require a fresh CNI deployment to be executed. To re-
deploy the file, click the button labeled Resend Dev Mon File.
Figure 7-10. Resend Dev Mon File Button
During device monitor configuration, a station may not receive the configuration file and display
this system message: ERROR_SESSION_CREDENTIAL_CONFLICT.
89
Figure 7-11. ERROR_SESSION_CREDENTIAL_CONFLICT
If this happens, check to see if the workstation is externally mapped as a network drive in Win-
dows File Explorer.
Figure 7-12. Windows File Explorer
If the workstation is externally mapped, disconnect the mapped drive and resend the device con-
figuration file. If the workstation is not externally mapped, the workstation needs to be rebooted.
90
8. Customer Cases Resolved in V9.4
This chapter describes the customer cases resolved in Control Core Services v9.4.
CAR Number Description

1054314 Message Manager does not seem to be handling the RTN state correctly.
1054366 Message Manager crashing when we have a significant number of message table
entries. The intmon log has the following line:
Wed May 11 14:12:22 2011WARNING: Starting dependent service
[MMPackRec] failed by calling StartService() with code [1053]! We have had a
request in for over a year requesting information om Message manager limita-
tions (301220989 Message manager limits)
1091872 D:optfoxmmMM-bindevserv.exe had a Runtime Error. A dialog box was on the
screen waiting for the user to select OK. Devserv.exe should exit and restart
without user intervention. It also appeared that after OK was selected that the
MMs switched roles. If these is any problem with alarm delivery of the primary
MM, the backup MM should take over.
1106399 When the Primary Message Manager is powered down, it takes 10 seconds for
the backup MM to take over. During this time, all alarms that are generated by
the control processors are not printed nor are they historized. The Current
Alarm Display does receive the alarms during the 10 second window as part of
the alarm recovery process. The alarm printer and the historian need similar
functionality otherwise there is no permanent record of the alarm.
1114374 When there are 4000 priority 2 alarms at a steady state. An alarm priority
change happens to make the all priority 2 alarms change to priority 1. The MM
devserv.exe process on the active MM begins to consume 10 handles a second.
Overnight the count went from 582 to greater than 500,000 handles being
used. If left unchecked all the handles could be used making it impossible to
launch other programs and running programs unable to open a new one.
1150818 When the log file size is increased to greater than 100KB in intmon.cfg, the
program CADF.exe will crash when the Message Manager is restarted.
1171645 When an alarm is acknowledged from the CAD a blank line is printed on the
alarm printer (with MM alarm delivery). This problem existed in QF1014494
and QF10156233.
1171652 Running the Main Message Manager (1AW065) active a large number of appli-
cation objects connected to the block alarm priority will show disconnected.
Looking at the detail displays of the affect blocks all show a connection status
disconnected, but some of the block alarm priority connections will not show
BAD (magenta for our site). All block alarm priority status using OMA show a
status of 0022 hex.
91
B0700SY – Rev C 8. Customer Cases Resolved in V9.4

1171398 Changing logsize settings in the intmon.cfg can cause Message Manager tasks to
stop executing including packrec.exe and devserv.exe. These settings with cause
packrec.exe to stop. #watching; timeout; trace; service_name; parameter_list
true; 2000; on; MMRedCtrl; -logsize 10000000 ; true; 5000; on; MMDevServ;
-logsize 10000000 -qsize 4000 -SOtime 20; true; 5000; on; MMCadf; -logsize
10000000; true; 5000; on; MMPackRec; -logsize 10000000 ;
1194119 During the testing of QF-1106399 with a single Message Manager running
after 30000 alarms had been generated from 11 ZCP2070s, the DevServ.exe
process was killed from the Windows Task Manager. IntMon.exe restarted
PackRec.exe and DevServ.exe which triggered a CSU from all 11 ZCPs. The
alarm shower that was greated triggered a peer recovery between all 14 alarm
destinations. It appears that all 14 destinations are trying to recover at the same
time which results in random alarm counts on all destinations. In some
instances, the peer recovery continues until the Message Manager is stopped.
1252882 After making a single FCP270 fault tolerant, we noticed that the measured
value of a specific channel is received on another channel of the same FBM. For
example: when they put a signal of 12mA on channel 3 of FBM 030144, we see
that CH8 responds on the signal increase. When they put a signal of 12mA on
CH8, CH3 didn't respond to it, so it doesn't work in both ways. This was seen
for multiple channels and FBM's. Also when using the omget command the
values weren't correct. We also verified the values using the live dataviewer in
IDE.
Important to know is that we ran into some problems when making the FCP
fault tolerant, as you can see in the smon_log. After a redeploy of the FBM's the
problem was solved. SMC log, checkpoint files from before and after the rede-
ploy, smon_log, OS1C70 file, etc are available for further analysis.
1258752 the last character of the MAC address is always missing i.e. it is reported as only
11 characters long instead of the actual 12 characters.
Because many sites use FT module pairs where the MAC address difference is
restricted to the last digit, such does not exactly help when investigating/debug-
ging problems.
Please correct the error reporting mechanism such that the full MAC address
gets printed/reported.
1264668 System was upgraded from IA v8.7 to Evo v9.1. ZCP270's and FCM100et's
were upgraded to the latest firmware. TimeSync stopped working when the
FCM100et's were upgraded to v1.63. A test was conducted to verify the issue
with the v1.63 firmware. A pair of FCM100et's, one at v1.58 and the other at
v1.63, was placed together in a baseplate. When the FCM running v1.63, was
connected TimeSync showed Network Time in the Sync State in System Man-
ager. When the FCM, running v1.58, was connected TimeSync began working
immediately and showed Sync Pulse in the Sync State in System Manager. We
have found that if the FCM's, running v1.63, were rebooted and a Switch Role
was performed TimeSync would show Sync Pulse.
92
8. Customer Cases Resolved in V9.4 B0700SY – Rev C

1271427 Issue is happening when the ROUT is in manual. With the latest image when
you enter a value of say 90.0, the output forces a value of 90.0 to OUTQ, then
a FBK comes back at 90.4, The output tracks this then forces another write to
OUTQ, a continuous loop occurs and that's how the winding up is happening.
On the older 843040 image, it seems that initial FBK value of 90.4 is not
forced back to OUTQ and everything holds at 90.4.
1271871 FSR installed QF1183358C while logged in as IADomainAdmin. Getting an
error when trying to perform block copy between CP's. File I/O (99)
,,,,Failed The ICC block copy procedure described in the QF allowed user to
copy blocks between CP's in different AWs.
This worked in previous versions 8.7 an lower. In 8.8 and higher, it does not.
1318488 EI5 to EI8 of SIGSEL block is forced into upper case when hitting Done.
1278737 An INFO message (priority 5 by default, cannot be changed) from an IND

block gets sent to the CAD and triggers the audible horn because priority 5 is
set up to trigger an output to a horn via the horn.cfg file. An IND sequence
string (SN0001) is sent to the CAD via the HLBL command "SENDMSG
(SN0001) TO MSGGR1". Message group 1 contains up to 8 devices that the
INFO message alarm can be sent to. In our case, that is the historian, message
logger service, and two operator workstations. Clicking the Process button in
the upper left of a FoxView display for either of the WP's in this group (both
WP's in the same CAG) will silence the audible, but if the message changes
before the alarm is cleared from the CAD, it does not trigger the audible horn
again.
1295305 I have a FT CP270 that I am having problems performing a load all on. They
are at IA 9.1. The CP has image 920030 loaded. I have tried different images
with the same results. To get them running I had to load the CP using an ICC
print and iccapi. I then manually copied their sequence and ladder then re-
compiled everything.
I successfully loaded the save all on a couple different virtual machines. One at
8.5 and one at 9.1. I also successfully loaded to a volume. When I try to load all
to the physical CP I lose communications to the CP. No log files are generated.
1297442 When an Operator silences the Horn via a single Ack Horn Key Press followed
by an annun key press to call a graphic, the Horn is silenced and the requested
Display is presented in the FoxView Window instantly.
However when the Operator is tapping the Ack Horn Key multiple times (10
X) followed by an annun key press to call a graphic, the Horn is silenced and
the requested Display is presented in the FoxView Windowwith a delay of
approx 5 seconds.
93

1292394 We have MTK (named EW1GR1) and a backup MTK (named EW1CTS)
configured to get time sync from external NTP server on secondary network.
On Saturday 24th October 4:15AM (Rome time) the time changed to
1/1/1900 12:00 AM on MTK, all the other stations changed to 28/8/2035
4:43:57 PM.
This change had destructive consequence on various systems:
- two AIMs data lost and files corrupted
- two Wonderware Historian data lost and file corrupted plus consig license
expiration
- Terminal server DB corrupted
- PAS Integry desync
- External Audit system problems
1287718 ROUT block is setup with a range of 0-100 with LOLIM 0 and HILIM 100.
LOLIM coming from external block. Clamp option is 2; SCO 3. The ROUT
block is not responding only when the output touches zero. The output can be
changed (increase and decrease) as long as output is not touching 0.
1297629 Two Blocks of Type = RIN which did not show an alarm status while being in a
situation where they should show an alarm status / process alarm.
Opening the ICC, selecting one of these Blocks and clicking on Done resulted
in an Alarm of this Block!
We have used omget.exe to document the alarm status (e.g. ALMSTA value)
and to avoid a possible Bug within FoxView. The parameter values retrieved by
using omget.exe did not show an alarm, means FoxView was right.
1302631 After changing HHAOPT from 1 to 2, HH limit cannot be set anymore
through the detail display. Putting HHAOPT back to 1 makes parameter setta-
ble again in PIDA's detail display. Overlay has to be closed and call it up again.
A value of 3 also allows the parameter to be set through the referred display
which doesnot make sense. According to B0193AX, a value of 3 means LO-LO
alarming only.
Customer reports that HHAOPT=2 only works by calling up an overlay of the
referred controller.
1303315 Upgraded S1CP04 CP40 with 100 series fbm and fbc cluster io fbp 3 chassis to
FCP280[S1CP14] with FBI200with all 100 series fbm and three fbp 10 chassis
on 25th feb 2016.
Upgraded eeprom of FBP10R 42.11 to 6.3.2
FBC21 AI tags were generating alarms at morning 10:30 once in 24 hours at
the time of upgrade.
94

1303948 Blocks default displays (DDs) opened on AW generate indefinite unwanted
network traffic (connectionless IPC communication -omgets) by constant
requesting ERCODE parameter from controller.
This behavior will appear for every DD opened in every Foxview.
Example: CALCA DD displays ERCODE value with the help of ACHNGE
parameter (GEN_ERCODE symbol) on the DD primary page.
GEN_ERCODE symbol stored under D:opt\fox\displib\Symbols is configured
in way that ERCODE valued is requested based on trigger. Trigger itself is
defined by the parameter ACHNGE and the delta is set to 0. This configura-
tion leads to indefinite omget requests sent from AW to CP (in trace I could see
up to 4 packets per second per one DD). Setting delta to 1 leads to "controlled"
state. Meaning once I set block from auto to manual ACHNGE parameter
increased by 1 that leads to one omget requesting ERCODE sent from AW to
CP.
1301558 MOVLV bloc processing differently when EEPROM are different in manual
mode. EEPROM 090032 is processed correctly.
1294935 100 series to 200 series FBM upgrade, went with HART FBM's to replace
FBM01, FBM04 and FBM37's. New HART FBM's are at firmare 2.47C
All ROUT outputs are set to "Current", positioner feedbacks are being read
through HART "FV" parameter, and DVOPTS for ECB201 is set to
NOALARM. Reasoning for this was that customer didnot want the HART sig-
nals or failures to interfere with the valve control as it has not been doing with
100 series FBM's.
During turnaround and through startup many positioners (mainly Fisher
DVC5000 and 6000) were, for various reasons, going into "field device mal-
function" and the valve output would go bad and hold.
his being unacceptable, it was found that there was a new option called
IOBAD, which provides the user to decide what function 48 bit will trigger the
"Field device malfunction" and therefore IOBAD.
The trouble is the bits are different for each positioner type so no one setting
can be used. Customer wants to disable the IOBAD completely rather than
have to select an unused bit in each device to mask it out.
1304555 SHADOW will not marry - OPTIC interlink problem
56CP08 Gone to Single. Try to Replace the Faulty CP, but New CP Not Mar-
ried with existing, again back to Single.
1305647 Recently, we were checking some of the HART Transmitter inputs as they were
showing bit of high as compared to normal. We were checking the Primary
Value with the help of Foxboro Evo Field Device Manager and PACTware, sur-
prisingly Primary Value was showing correct but RAWC (4-20mA) was show-
ing high around 20%. When we changed the RIN block Input from RAWC
value to PV, it started showing correct.
This happened to all the Transmitters (Channels) connected to that FBM214.
We have replaced this FBM214 by a new one in the field.
95

1305648 Recently, we were trying to operate the Control Valves but were not able to. On
System Manager it was showing a yellow warning message related to that
device. When we changed DeviceOption to 4-20, it started operating the valve
normally.
1306878 CP280 crashed with memory violation.
Last message from CP:
08-Apr-16 16:37:03 - OperationWarning VSWD1_T1AD:MTR_CHECK
<pipe> W60 - PARAMETER START/STOPMOTOR_07IST
1306143 CAR:1306143 MCOUT blk parameter GRPNUM=16 can cause loss of field-
bus
Upon updating a block linkage in an MCOUT block and clicking "Done"
fieldbus communication with the F270FT controller was lost and the shadow
controller failed. Displays linking to this controller's I/O went cyan (not updat-
ing) and the FBM's did not go to their fail state. The operational status LED on
several of the FBM's was blinking green. The only way to recover from the fault
situation was to re-boot the primary controller. This then caused the FBM's to
go to their fail state until the controller loaded from the checkpoint file off the
host. The shadow controller then had to be re-booted to get it to marry up with
the primary and restore fault tolerant control. Returning this linkage to the pre-
vious "good" link caused the issue to repeat itself.
1309367 ASDM24
- The configuration for this card is based on the document b0700bk_h.pdf
- The ECB200 and ECB201 communication is working but we only have 16
channels available, the other 16 are mark as Bad.
ASDM48
- The configuration for this card is based on the document b0700bk_h.pdf
- The ECB200 and ECB201 communication is NOT working, it is not possi-
ble to enable the communication.
- The System Manager send an action request to enable the communication but
nothing happens. There is no error message.
1302226 System crashed to Windows Blue Screen on 2 occasions recently
System installed late Nov, 2015, first blue screen occurred Dec 28, 2015, 2nd
on Feb 5, 2016
Both times, system was running fine, and just stopped and shows blue screen,
with faults indicated in pictures attached
1309846 FCP270 UPCP01 lost the FT pair after upgrading to new image 920041, The
image was updated on last week of April.
FT loss was reported on 3rd, 5th, 8th, and 9th (2 Times) May 2016 with the
following messages.
Process = WDT_TASK FTFCPS 000024 FT pair failed to get to consistent
state. ROMAddr 00006C220F45
The FT was established by rebooting the shadow module.
96

1315830 A number of changes were made for the FBM248. These changes need to be
shared with the entire HART family of products.
1318029 None of the currently available versions of the "rsom.exe" tool, is capable of dis-
playing Boolean values in any OM list.
1319569 ASAM01-FBM235 (PN P0922SW @ 1.25B) used with FCP280 ( 091016 )

All DO points on these cards show up labeled as having BAD IO when in Auto.
Only way to get rid of the alarm is to place the block in Manual which is obvi-
ously not acceptable.
1319755 To verify the system health for Object Manager OM connections we are using
RSOM and SOM to get the information on open list for the different stations.
SAV is using the FERRET collected data to check of the owner of OM Source
list (LetterbugStation Name and Process ID (PID)) are still a live, to determine
'ghost lists'.
Windows Workstations (Win7/ Server 2008) can have PID's that can be >
400.000 since RSOM and SOM have a data structure for the PID of 5 num-
bers, we do get 'ghost list' reported that are in reality valid OM Lists.
Please update RSOM and SOM to support a data structure for the PID that
can work with the current Windows operating systems.
1319786 The Galaxy was undeployed before shipment to site. Once at site, everything
was powered up and CPs were brought on-line. The ECB compound was
deployed, but no other compounds. When FBMs were brought on-line from
System Manager, outputs apparently energized and caused motors to start in
the field. All of the outputs were from ASAM01 modules. No custom failsafe
behavior was configured in the ECBs so everything should have been off.
1321366 Release vehicle for bringing the CCS 9.3 CP280 image up-to-date with the
most recent quick fixes.
1321337 the case details I/A version is CCS 9.2 and I could see the latest ferret uploaded
to GCS on 26th jul 16.
1316308 When the system time is being set back, the redundant FBM222 fails for about
2 seconds. In the smon_log following message was found every time the system
time was set back a couple of minutes:
XXXXXX -39 1 Norm PB 0 0 ERROR 3 0 0 0 B-HDLC Bus Rx Fault
Because of the loss of communication, some of the pumps in the system stalled.
97

1313962 We have found a serious problem with restarting alarm providers and block
alarms resetting unexpectedly on FCPs with MM mode turned on. You start
with a measurement alarm, high for example, and an FCP at IA version 8.7 and
image 920030. Configure a REALM block with high absolute alarm set to 55
and alarm deadband set to 7. Set the MEAS to 60 to generate a high alarm. Set
the MEAS to 54 to go below the limit but stay within the deadband, the block
stays in a high alarm state. Now undeploy and redeploy the alarm provider.
Monitor the SMC log of the alarm provider looking for a "Manager:: Connect-
ToCP()" message for the FCP that contains the REALM block. Once you see
the message in the SMC log look at the REALM block faceplate and you will
see that the HIGH alarm has incorrectly reset even though the MEAS has not
changed and is still within the deadband. I have tried this with the PIDA block
and see the same results. I also tried this on an FCP with version 920041 and
got the same results.
1323821 Client is trying to add a MA button with a raised Protection ID for the COUT
Detail display. He has copied the DD_MA button and renamed it DD_MA1
and modified the Protection ID to suit. He then imported the DD_MA1 but-
ton from the library into the COUT Detail display to replace the existing MA
button (as they have done so on other system) however the new button did not
work.
1307359 On one CP every two or three checkpoint the shadow gone.
when CP are married, during normal operation we have no trouble (run few
months).
We have try swap primary and shadow, same issue.
we try change CP, same issue.
we try change port switch same issue.
No self hosting.
auto checkpoint disable.
1325395 pref - C2P121 amcmd "almdisp CAD;setdisp CAD; save_to_file $txtfile"
command doesn't work on server 2008 and windows 7 stations, the display call
up time and report date is not showing anymore. It does work for server 2003
and Windows XP stations.
1327129 On November 21, 2016, US-CERT reported a vulnerability in the NTP soft-
ware. The CVSS score for it is 7.8 which puts it in the HIGH category. The
Foxboro Evo software includes NTP software built with the source code from
the Network Time Foundation's NTP Project site that has this vulnerability.
This software needs to be rebuilt with the latest version available on that site.
1328702 Not a Number (NaN) can be generated by Control HMI and sent to the FCP.
Object Manager to be changed to prevent/reject NaN being passed to the FCP
98

1328760 Some and not all 200 series FBM types (ECBs) are reported as negative num-
bers when running utilities such as DBVU or getpars. Even though by subtract-
ing 256 to these numbers the correct FBM type can be obtained, this case is to
request that the correct values are reported without having to do any further
manipulation.
Development is aware of this issue.
The car volume contains some communication e-mails discussing this topic in
more detail.
The latest version of dbvu280 (to be released soon under QF1317943) seems to
have this correction in place as it reports all FBMs correctly.
37987045 FCP270-FT Modules going Single Causing Non-Fault Tolerant Operation
Until Manual FCP Reset/Reboot
Using System Auditor, we queried the past 5 years of messages. The message
below is a new message not seen prior to updating our FCP image to 920041 :
- FTFCPS 000024 FT pair failed to get to consistent state. ROMAddr

00006C2xxxxx
ALL messages like the one above have happened since upgrading our FCP270
images from 843040 to the latest FCP270 image, (image 920041) in mid July
2016. From 2012 to July 2016 we had never seen this particular message so we
feel confident that the new message and maybe error checking algorithm
changed in the FCP270 image at some time between image 843040 and image
920041. Also our FCP270's were not randomly going single prior to the new
image being installed.
Just prior to receiving the message above, the FT FCP goes SINGLE/Non-FT.
When this occurs the FCP270 that fails does not fail RED-DEAD, but fails
GREEN/RED and can be manually Reset/Rebooted.
39088794 This issue will address the NAN issues
40010664 225-936-2992 sys mgr shows "unknown" for all stations because System Moni-
tors are not starting. Using CCS 9.3 and tk.cfg with 3 NTP servers (3 IP
addresses).
System Monitor doesn't start because tk.cfg has 3 IP addresses for NTP servers.
It can only read the first 50 characters.
40095779 ASAM01 Module (P0922SW) stopped updating raw counts on apparently all
channels (definitely 5, 10, and 14). This may be related to a "bad" status from
an Altivar 71 drive speed command on channel 25 of this card.
40243923 The following symptoms have occurred 3 times, on 3 different FBMs all
located in the same rack/slot at the customer site.
Several analog input channels on either group 3 or 4 (17-24 or 25-32) read
lower than expected values. All analog outputs in that group show BAD in Sys-
tem Manager. After a period of time all of channels 17-32 show BAD in System
Manager. Resetting the FBM (off-line/on-line) will allow it to recover for a
period of time.
99

38316009 CP01 shadow module LED status show Red and Green, Rebooted Shadow
Module, it's not married to primary and status remain same. we have change
shadow module with spare module and checked, found problem remain same,
shadow is not married to Primary, We have to shutdown plant and reboot both
FCP, problem remain same, we have change primary FCP, after that it's able to
marry shadow.
40298928 FBM222 iom2.12 or iom2.15. New out of the box PA divecs comes with slave
adress126. PA device with address 126 is visible in livelist. But livelist is crash-
ing. Unable to change address.
this functionality was available in IOM 2.05
FBM222 IOM 2.15 does not support the functionality provided by
QF10103444 which was released for IOM 222 rev 2.05. The corrections made
to the IOM by the QF should have been rolled into the later IOM images. This
did not happen, as evidenced by the results at customer site.
A QF for CCS 9.2 will be required which includes the fixes from QF1010344.
40709902 System Manager shows a status for each channel on the ASAM01. It is not pos-
sible to inhibit individual channels. When a block was configured for an analog
output that was not wired. The channel showed bad in System Manager. When
it was determined that the signal did not exist the block was deleted. However,
the channel continues to show bad in System Manager. This creates a situation
in which "fake" alarms are active and makes it much more difficult to deter-
mine if there is actually a hardware problem. This has been observed on multi-
ple FBMs running image 1.43.
40355810 when several ASAM01 modules were put on-line via a General Download,
motors wired on those outputs turned on for a second. This is with part num-
ber P0928RL ASAM01b modules. All compounds in the CP were turned off
except for the STATION and ECB compounds. This occurred on at least 3
outputs on two different cards. It is possible that it occurred on all P0928RL
but the other motors were locked out since they were in an outage.
37712783 FCP270 single and didn't wanted to marry with other modules, only reboot of
primary module resolved the redundancy. RED module not available onsite and
reboot of primary module was possible in this case with some mitigations. This
raise a concern as both modules were rev0W and the image was 900022, this
combination shouldn't have any problem with opto couplers.
1329876 Confirm or investigate the expected startup time of the FDSI Configuration
GUI.
It has been seen as starting after 30- 40 sec. (running on EWS001.) and this is
considered slow
39732378 NaN floating point values can be sent to a remote FCP via CNI
100

38601418 System was upgraded from IA v8.7 to Evo v9.1. ZCP270's and FCM100et's
were upgraded to the latest firmware. TimeSync stopped working when the
FCM100et's were upgraded to v1.63. A test was conducted to verify the issue
with the v1.63 firmware. A pair of FCM100et's, one at v1.58 and the other at
v1.63, was placed together in a baseplate. When the FCM running v1.63, was
connected TimeSync showed Network Time in the Sync State in System Man-
ager. When the FCM, running v1.58, was connected TimeSync began working
immediately and showed Sync Pulse in the Sync State in System Manager. We
have found that if the FCM's, running v1.63, were rebooted and a Switch Role
was performed TimeSync would show Sync Pulse.
37793871 These editions use fixed credentials. This should be a HOT CAR to provide
ability to change username and password.
101
102
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
A.1 Image Revision Levels for Control Stations and

ATS with Control Core Services v9.4
Table A-1 lists the control station and ATS EEPROM revision levels that have changed for this
release.
Table A-1. Control Core Services V9.4 Control Station and ATS EEPROM/Image
and Software Revision Levels
Software Revision Level

Station
Description Mnemonic V8.6 V8.7 V8.8 V9.0 V9.1 V9.2 V9.3 V9.4
Field Control Pro- FCP280 N/A N/A N/A 090022 090022 091001 092012 092017
cessor 280
Control Network CNI N/A N/A N/A N/A N/A 092065 093040 093042
Interface
Field Device Con- FDC280 N/A N/A N/A N/A N/A N/A 090000 0900010
troller 280 9000 000
Z-Module Control ZCP270 860016 870001 880009 900004 900018 900035 920040 920053
Processor 270
Field Control Pro- FCP270 860016 870001 880009 900004 900018 900035 920040 920053
cessor 270
Address Transla- ATS 860016 870001 880009 900004 900018 900035 920030 920053
tion Station
NOTE
To acquire the initial release of the Field Device Controller 280 (FDC280) image,
on the GCS website (https://pasupport.schneider-electric.com), select Support -> Fox-
boro Evo -> Product Info.
103
B0700SY – Rev C Appendix A. EEPROM Revision Levels
Table A-2 lists the legacy station software and EEPROM revision levels supported for this release
of the Control Core Services.
Table A-2. Control Core Services V9.4 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 OS1A3B1 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 OS1FDB2 6.5.6 3.32 7.1
Modbus Integrator 30 Style B MG30B OS1M3B3 6.1.10 3.32 6.5.6
Communication Processor 10 COMM10 OS1CS 6.5.1 2.20 7.1
1. For the Allen-Bradley Integrator 30 Style B, the OS1A3B package includes two files: OS1A3B and
OS1A3B.186.
2. 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.
3. For the Modbus Integrator 30 Style B, the OS1M3B package includes two files: OS1M3B and
OS1M3B.186.
A.2 100 Series FBM Software and EEPROM Versions

Table A-3 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 Manage-
ment Equipment Information display as follows:
SOFTWARE REV: <Software Version>

EEPROM REV: <EEPROM Version>
NOTE
In Table A-3, 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 Ser-
vices or I/A Series software release.
104
Appendix A. EEPROM Revision Levels B0700SY – Rev C
Table A-3. 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.4
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
105
Table A-3. Software Versions of 100 Series FBMs (Y Form Factor) (Continued)
EEPROM
V8.6 V9.0-
FBM06, F1M06, IOM04 80.1 – – – – – 61.1 61.1
H2M06, H2M06A,
H3M06
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
106
EEPROM
V8.6 V9.0-
<LADDER> IOM08 80.2 – – – – – 61.1 61.1
FBM07A, FBM07B,
FBM08, FBM09A
through D, FBM10,
FBM11, FBM12A,
FBM12B, FBM13,
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,
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
1
<HTG> FBM23 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 Chromato- IOM39 40.1 – – – – – 42.2 42.2
graph> 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
107
EEPROM
V8.6 V9.0-
<PID> FBM04, IOM52 80.1 – – – – – 61.1 61.1
FBM17, FBM17A
through D, FBM22,
H2M17
FBM37, BAOM37, IOM53 80.1 – – – – – 61.1 61.1
H3M37
H3M01 IOM54 4.21.05 – – – – – 4.21. 4.21.0
.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
(BASI0 (BASI03 (BASI0 (BAS (BASI0
3) ) 3) I03) 3)
5.06.0 5.06.03. 5.06.0 5.06. 5.06.0
3.03 03 3.03 03.03 3.03
(BSDM (BSDM0 (BSDM (BSD (BSD
06) 6) 06) M06) M06)
BASI01, BASM01, IOM56 4.21.05 4.21.05. – – – – 4.21. 4.21.0
BASO37 .03 03(BASI 05.03 5.03
01, (BAS (BASI0
BASM01 I01, 1,
) BAS BASM
4.21.04. M01) 01)
03 4.21. 4.21.0
(BASO3 04.03 4.03
7) (BAS (BASO
O37) 37)
FRM701, FRM711, IOM57 4.21.07 – – – – – 4.21. 4.21.0
FRMMPU .03 07.03 7.03
F2M68A IOM58 4.21.05 – – – – – 4.21. 4.21.0
.03 05.03 5.03
F2M67A IOM59 4.21.06 – – – – – 4.21. 4.21.0
.03 06.03 6.03
<FoxCom> FBM43 IOM73 80.2 – – – – – 61.1 61.1
1. 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. Refer to MI 020-065.
A.3 200 Series FBM Software and EEPROM Versions

Table A-4 lists 200 Series FBMs and their software versions. 200 Series FBMs and communica-
tion 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 as follows:
SOFTWARE REV: <FBM> <Software Version> or <Software Version> <FBM>

EEPROM REV: ROM <Software Version>
108
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 Informa-
tion display.
NOTE
In Table A-4 and Table A-5, 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 A-4. Software Versions for 200 Series FBMs (DIN Rail Mounted Form Factor)
Software Version
V9.0-
Devices Using IOM ID V8.4.2 V8.4.3 V8.5 V8.6 V8.7 V8.8 V9.4
FBM208 IOM80 1.25K 1.40D 1.40E 1.40R 1.40R 1.40R 1.40V
FBM240 IOM81 1.25G 1.40D – 1.40N 1.40U 1.40U 1.40U
(v9.0)
1.41A
(v9.1 or
later)
FBI10E, FCM10E, IOM82 1.16 – – – – 1.16 1.16
FBI10E, FCM10E,
FCM10Ef, WFCM10E,
WFCM10Ef, DCM10E
FBM201, WAI01A IOM83 1.25K 1.40D 1.40E 1.40R 1.40R 1.40R 1.40R
through D, WAW01A
through F, WAX01A
through C
FBM202, FBM202B, IOM84 1.25G 1.40D – 1.40R 1.40R 1.40R 1.40R
WAI02A, WAV02A,
WAX02A
FBM203C, WRF03A,
WRF03B, WRT03A,
WRT03B
FBM204, WLJ04A IOM86 1.25G 1.40D – 1.40T 1.40T 1.40T 1.40T
through C
FBM205 IOM87 1.25G 1.40D – 1.40R 1.40R 1.40R 1.40R
FBM206, WPA06A IOM88 1.25G 1.40D – 1.40N 1.40N 1.40N 1.40N
FBM207, FBM207B, IOM89 1.25H 1.40D 1.40E – – 1.40E 1.40E
FBM207C, WCI07A,
WDI01A through E,
WID07A through P
FBM211, WAH01A IOM90 1.25G 1.40D – 1.40R 1.40R 1.40R 1.40R
through D
FBM212 IOM91 1.25G 1.40D – 1.40R 1.40R 1.40R 1.40R
FBM213 IOM92 1.25G 1.40D – 1.40R 1.40R 1.40R 1.40R
FBM237, WAO37A IOM93 1.25G 1.40D – 1.40N 1.40N 1.40N 1.40N
through G
FBM241, FBM241B IOM94 1.25G 1.40D – 1.40N 1.40N 1.40N 1.40N
through D
109
Table A-4. Software Versions for 200 Series FBMs (DIN Rail Mounted Form Factor) (Continued)
Software Version
V9.0-
FBM242, WBO09A, IOM95 1.25G 1.40D – 1.40N 1.40N 1.40N 1.40N
WBO09B, WRO09A
through D, WTO09A
FBM217 IOM96 1.25H 1.40D 1.40E – – 1.40E 1.40E
FBM243, FBM246 IOM97 2.35G 2.40D – 2.40N 2.40N 2.40N 2.46M
(FoxCom™)
FBM219 IOM98 1.25G 1.40D – 1.40N 1.40N 1.40N 1.40N
(v9.0-
9.2)
1.41C
(v9.3+)
FCM100Et IOM210 1.54 1.56 – – 1.58 1.59 1.62
(v9.0)
1.63
(v9.1-
v9.3)
1.64
(v9.4)
FCM100E IOM210E 2.03 – 2.05 2.06 2.06 2.06 2.08
FBM214 (HART) IOM214 2.35G 2.40D 2.40E 2.40P 2.41B 2.46J 2.46J
(v9.0)
2.47B
(v9.1-
v9.2)
2.50A
(v9.3-
v9.4)
FBM215 (HART) IOM215 2.35G 2.40D – 2.40N 2.41B 2.46J 2.46J
(v9.0)
2.47B
(v9.1-
v9.2)
2.50A
(v9.3-
v9.4)
FBM216 (HART) IOM216 2.35G 2.40D 2.40E 2.40Q 2.41Ga 2.46J 2.46J
(v9.0)
2.47B
(v9.1-
v9.2)
2.50A
(v9.3-
v9.4)
FBM218 (HART) IOM218 2.35G 2.40D – 2.40Q 2.41Gb 2.46J 2.46J
(v9.0)
2.47B
(v9.1-
v9.2)
2.50A
(v9.3-
v9.4)
FBM220 (FOUNDATION IOM220 2.20 – – – – 2.20 2.20
fieldbus H1)
110
Software Version
V9.0-
FBM221 (FOUNDATION IOM221 2.20 – – – – 2.20 2.20
fieldbus H1)
FBM222 (Profibus-DP) IOM222 1.12 2.05 2.07 – 2.10 2.12 2.15
(v9.0-
v9.3)
2.16
(v9.4)
FBM223 (Profibus-DP) IOM223 1.06 – 1.07 – – 1.07 1.08
FBM224 (Modbus) IOM224 1.14 1.15 1.16 – 1.16 1.16 1.16
FBM227 IOM77 N/A N/A N/A 1.40U 1.40U 1.40U 1.40W
(v9.0-
9.2)
1.41B
(v9.3+)
FBM228 (Redundant IOM128 – – 5.00 6.02 6.10 6.15 6.19
FOUNDATION fieldbus (v9.0-
H1) 9.1)
6.21
(v9.2)
6.23
(v9.3)
6.27
(v9.4)
FBM228 (Redundant IOM228 3.09 3.18 3.24 3.25 3.31 3.33 3.36
FOUNDATION fieldbus
H1)
FBM229 (DeviceNet) IOM229 N/A N/A N/A N/A 1.01 1.01 1.02
FBM230 (Simplex IOM230 1.26 1.27 1.30 1.31 1.32 1.34 1.35
Serial FDSI) (v9.0-
9.2)
1.36.3
(v9.3)
1.36.4
(v9.4)
Serial FDSI) (v9.0-
9.1)
1.35.1
(v9.2)
1.36.3
(v9.3)
1.36.4
(v9.4)
FBM232 (Simplex IOM232 1.26 1.27 1.30 1.31 1.32 1.34 1.35
Ethernet FDSI) (v9.0-
9.2)
1.36.3
(v9.3)
1.36.4
(v9.4)
111
Software Version
V9.0-
Ethernet FDSI) (v9.0-
9.1)
1.35.1
(v9.2)
1.36.3
(v9.3)
1.36.4
(v9.4)
FBM234 (AEAM01) IOM234 1.25B – – – – 1.25B 1.25B
(v9.0-
v9.3)
1.44
(v9.4)
FBM235 (ASAM01) IOM235 1.25B – – – – 1.25B 1.25B
(v9.0-
v9.3)
1.44
(v9.4)
FBM236 (ASDM24, IOM236 1.25B – – – – 1.25B 1.25B
ASDM48) (v9.0-
v9.3)
1.44
(v9.4)
FBM238 IOM78 N/A N/A N/A 1.40N 1.40N 1.40N 1.40N
(v9.0-
9.2)
1.41C
(v9.3+)
(v9.0-
9.2)
1.41C
(v9.3+)
FBM244 IOM244 N/A N/A N/A 2.40N 2.41B 2.46J 2.46J
(v9.0)
2.47B
(v9.1-
v9.2)
2.50A
(v9.3-
v9.4)
FBM245 IOM245 N/A N/A N/A 2.40Q 2.41Gb 2.46J 2.46J
(v9.0)
2.47B
(v9.1-
v9.2)
2.50A
(v9.3-
v9.4)
112
Software Version
V9.0-
FBM247 IOM247 – – – – 2.42C 2.46J 2.46J
(v9.0)
2.47B
(v9.1-
v9.2)
2.50A
(v9.3-
v9.4)
FBM248 IOM248 – – – – – – 2.50A
(v9.3)
2.50E
(v9.4)
FBM250 (ISCM) IOM250 N/A 2.40 – – 2.40B 2.40B 2.50H
(v9.0-
9.1)
2.41C
(v9.2+)
Table A-5. EEPROM Revision Levels for 200 Series FBMs

(DIN Rail Mounted Form Factor)
EEPROM Revision Level

V9.0-
FBM208 IOM80 1.25K 1.40D 1.40E 1.40R 1.40R 1.40R 1.40V
FBM240 IOM81 1.25G 1.40D – 1.40N 1.40U 1.40U 1.40U
(v9.0)
1.41A
(v9.1 or
later)
FBI10E, FCM10E, FBI10E, IOM82 1.16 – – – – 1.16 1.16
FCM10E, FCM10Ef,
WFCM10E, WFCM10Ef,
DCM10E
FBM201, WAI01A through IOM83 1.25K 1.40D 1.40E 1.40R 1.40R 1.40R 1.40R
D, WAW01A through F,
WAX01A through C
WAI02A, WAV02A,
WAX02A
FBM203C, WRF03A,
WRF03B, WRT03A,
WRT03B
FBM204, WLJ04A through IOM86 1.25G 1.40D – 1.40T 1.40T 1.40T 1.40T
C
FBM205 IOM87 1.25G 1.40D – 1.40R 1.40R 1.40R 1.40R
FBM206, WPA06A IOM88 1.25G 1.40D – 1.40N 1.40N 1.40N 1.40N
113

(DIN Rail Mounted Form Factor) (Continued)

V9.0-
FBM207, FBM207B, IOM89 1.25H 1.40D 1.40E – – 1.40E 1.40E
FBM207C, WCI07A,
WDI01A through E, WID07A
through P
FBM211, WAH01A through IOM90 1.25G 1.40D – 1.40R 1.40R 1.40R 1.40R
D
FBM212 IOM91 1.25G 1.40D – 1.40R 1.40R 1.40R 1.40R
FBM213 IOM92 1.25G 1.40D – 1.40R 1.40R 1.40R 1.40R
FBM237, WAO37A through IOM93 1.25G 1.40D – 1.40N 1.40N 1.40N 1.40N
G
FBM241, FBM241B through IOM94 1.25G 1.40D – 1.40N 1.40N 1.40N 1.40N
D
FBM242, WBO09A, IOM95 1.25G 1.40D – 1.40N 1.40N 1.40N 1.40N
WBO09B, WRO09A
through D, WTO09A
FBM217 IOM96 1.25H 1.40D 1.40E – – 1.40E 1.40E
FBM243, FBM246 (Fox- IOM97 2.35G 2.40D – 2.40N 2.40N 2.40N 2.46M
Com™)
FBM219 IOM98 1.25G 1.40D – 1.40N 1.40N 1.40N 1.40N
(v9.0-
9.2)
1.41C
(v9.3+)
FCM100Et IOM210 1.54 1.56 – – 1.58 1.59 1.62
(v9.0)
1.63
(v9.1-
v9.3)
1.64
(v9.4)
FCM100E IOM210E 2.03 – 2.05 2.06 2.06 2.06 2.08
FBM214 (HART) IOM214 2.35G 2.40D 2.40E 2.40P 2.41B 2.46J 2.46J
(v9.0)
2.47B
(v9.1-
v9.2)
2.50A
(v9.3-
v9.4)
FBM215 (HART) IOM215 2.35G 2.40D – 2.40N 2.41B 2.46J 2.46J
(v9.0)
2.47B
(v9.1-
v9.2)
2.50A
(v9.3-
v9.4)
114


V9.0-
FBM216 (HART) IOM216 2.35G 2.40D 2.40E 2.40Q 2.41Ga 2.46J 2.46J
(v9.0)
2.47B
(v9.1-
v9.2)
2.50A
(v9.3-
v9.4)
FBM218 (HART) IOM218 2.35G 2.40D – 2.40Q 2.41Gb 2.46J 2.46J
(v9.0)
2.47B
(v9.1-
v9.2)
2.50A
(v9.3-
v9.4)
FBM220 (FOUNDATION field- IOM220 2.13 – – – – 2.13 2.20
bus H1)
FBM221 (FOUNDATION field- IOM221 2.13 – – – – 2.13 2.20
bus H1)
FBM222 (Profibus-DP) IOM222 1.00 1.10 – – – 1.10 1.10
FBM223 (Profibus-DP) IOM223 1.02 – – – – 1.02 1.02
FBM224 (Modbus) IOM224 1.10 1.15 1.16 – 1.16 1.16 1.16
FBM227 IOM77 N/A N/A N/A 1.40U 1.40U 1.40U 1.40W
(v9.0-
9.2)
1.41B
(v9.3+)
FBM228 (Redundant FOUN- IOM128 – – 1.0 1.00 1.00 1.00 1.00
fieldbus H1)
DATION
FBM228 (Redundant FOUN- IOM228 1.1 – – – – 1.1 1.1
fieldbus H1)
DATION
FBM229 (DeviceNet) IOM229 N/A N/A N/A N/A 0.01 0.01 0.01
FBM230 (Simplex Serial IOM230 0112 – 0113 – – 0114 0115
FDSI) (v9.0-
v9.3)
0116
(v9.4)
FBM231 (Redundant Serial IOM231 0112 – 0113 – – 0114 0115
FDSI) (v9.0-
v9.3)
0116
(v9.4)
FBM232 (Simplex Ethernet IOM232 0112 – 0113 – – 0114 0115
FDSI) (v9.0-
v9.3)
0116
(v9.4)
115


V9.0-
FBM233 (Redundant Ether- IOM233 0112 – 0113 – – 0114 0115
net FDSI) (v9.0-
v9.3)
0116
(v9.4)
FBM234 (AEAM01) IOM234 1.25B – – – – – 1.44
(v9.4)
FBM235 (ASAM01) IOM235 1.25B – – – – – 1.44
(v9.4)
FBM236 (ASDM24, IOM236 1.25B – – – – – 1.44
ASDM48) (v9.4)
(v9.0-
9.2)
1.41C
(v9.3+)
(v9.0-
9.2)
1.41C
(v9.3+)
FBM244 IOM244 N/A N/A N/A 2.40N 2.41B 2.46J 2.46J
(v9.0)
2.47B
(v9.1-
v9.2)
2.50A
(v9.3-
v9.4)
FBM245 IOM245 N/A N/A N/A 2.40Q 2.41Gb 2.46J 2.46J
(v9.0)
2.47B
(v9.1-
v9.2)
2.50A
(v9.3-
v9.4)
FBM247 IOM247 – – – – 2.42C 2.46J 2.46J
(v9.0)
2.47B
(v9.1-
v9.2)
2.50A
(v9.3-
v9.4)
FBM248 IOM248 – – – – – – 2.50A
(v9.3)
2.50E
(v9.4)
116


V9.0-
FBM250 (ISCM) IOM250 N/A 2.40 – – 2.40B 2.40B 2.50H
(v9.0-
9.1)
2.41C
(v9.2+)
117
Schneider Electric Systems USA, Inc.
38 Neponset Avenue
Foxborough, MA 02035-2037
United States of America
www.schneider-electric.com
Global Customer Support

https://pasupport.schneider-electric.com

Control Core Services v9.4 Release Notes: Foxboro Evo Process Automation System

Uploaded by

Copyright:

Available Formats

Control Core Services v9.4 Release Notes: Foxboro Evo Process Automation System

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

Control Core Services v9.4 Release Notes: Foxboro Evo Process Automation System

Uploaded by

Copyright:

Available Formats

Foxboro Evo™

Process Automation System

Control Core Services v9.4

Copyright 2018 Schneider Electric.

SOFTWARE LICENSE AND COPYRIGHT INFORMATION

Safety Information ................................................................................................................. xi

2. Features of Control Core Services V9.4 Release................................................................. 5

3. V9.4 Compatibility Considerations ................................................................................... 7

4. V9.4 Hardware Requirements ......................................................................................... 17

5. V9.4 System Setup .......................................................................................................... 19

6. V9.4 Operational Recommendations............................................................................... 25

6.10 Object Manager Software ................................................................................................ 51

6.20 Intrinsically Safe I/O Subsystem ...................................................................................... 67

7. V9.4 User Notes .............................................................................................................. 75

8. Customer Cases Resolved in V9.4 ................................................................................... 91

Appendix A. EEPROM Revision Levels............................................................................. 103

The addition of either symbol to a "Danger" or

This is the safety alert symbol. It is used to alert you to

♦ I/A Series Configuration Component (IACC) V2.7 Release Notes (B0700SM)

♦V8.5 Release Notes (B0700SC)

♦ FBM203/b/c/d Platinum/Nickel/Copper RTD Input Interface Modules (PSS 31H-

1.1 Overview of the Control Core Services v9.4

1.1.1 Local Edition and Enterprise Edition Control Core Services

1.2 Hardware Requirements

1.3 Domain Controllers

1.4 Operating System Image Installation

1.5 Control Core Services V9.4 Support for the

1.6 Site Upgrades

1.6.1 Migrating Files

1.6.2 Compound Summary Access (CSA)

1.7 Installation Overview

1.8 Maintain Up-to-Date Version of Adobe® Reader®

1.9 Foxboro Evo Product Rebranding

Table 1-1. Foxboro Evo Product Rebranding

Product Name for Foxboro Evo Process

2.1 Support for Windows 10 and Windows Server

2.2 Support for the Microsoft Windows Server 2016

2.3 Local Edition User Account Updates

2.4 Enterprise Edition User Account Updates

2.5 Additional Security Settings for Both Local Edition

3.1 Site Upgrade Plans

3.2 Control Software Support for Control Core

3.3 Interoperability and Compatibility

Table 3-1. Overview of Control Core Services or I/A Series Software

I/A Series Software Control Core Services

Table 3-1. Overview of Control Core Services or I/A Series Software

I/A Series Software Control Core Services

Table 3-1. Overview of Control Core Services or I/A Series Software

I/A Series Software Control Core Services

Table 3-1. Overview of Control Core Services or I/A Series Software

I/A Series Software Control Core Services

♦ AIM*I/O Gate Collector software

3.3.1 AIM*API as a Replacement for FoxAPI

3.3.2 Nodebus to Control Network Interoperability and

3.3.3 Control Core Services Interoperability and Compatibility

3.3.3.1 Active Directory Domain Compatibility

3.3.3.2 Limitations to Interoperability and Compatibility with ADMC

3.3.3.3 Compatibility of Other Software in the Control Core Services

♦ Isolation Station software