b0700sv F PDF

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

Release Notes
*B0700SV* *F*
B0700SV
Rev F
February 2, 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 2015-2018 Schneider Electric.

All rights reserved.
SOFTWARE LICENSE AND COPYRIGHT INFORMATION

Before using the Schneider Electric Systems USA, Inc. supplied software supported by this
documentation, 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
longer 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
mentioned in the software license.
Contents
Tables..................................................................................................................................... xi
Preface................................................................................................................................. xiii
1. Read Me First.................................................................................................................... 1
1.1 Overview of the Control Core Services v9.3 Release ............................................................ 1
1.2 Hardware Requirements ...................................................................................................... 1
1.3 Domain Controllers ............................................................................................................ 1
1.4 Operating System Image Installation ................................................................................... 2
1.5 Control Core Services Security Enhancements .................................................................... 2
1.6 Control Core Services V9.3 Support for the Control Software ............................................ 2
1.7 Site Upgrades ...................................................................................................................... 2
1.7.1 Migrating Files ............................................................................................................ 3
1.7.2 Compound Summary Access (CSA) ............................................................................ 3
1.8 Installation Overview .......................................................................................................... 3
1.8.1 Installing the Foxboro Evo Control Core Services v9.3 Trailer CD-ROM .................. 4
1.8.2 Quick Fix 1287671 for Legacy Workstations and Servers ............................................ 5
1.9 Migration Requirements ..................................................................................................... 5
1.9.1 Migrating a FCP270 or ZCP270 Control Database from a
System with I/A Series Software v8.6 or Earlier .................................................................... 5
1.9.2 Migration of Domain Controller from I/A Series Software v8.5 to v8.8 ...................... 6
1.10 Security Advisory for Adobe® Reader® ............................................................................ 6
1.11 Foxboro Evo Product Rebranding ..................................................................................... 6
2. Features of Control Core Services V9.3 Release................................................................. 9

2.1 Support for FBM248 .......................................................................................................... 9
2.2 Support for Field Device Controller 280 (FDC280) ........................................................... 9
2.3 Additional Features for the Control Network Interface (CNI) ............................................ 9
2.4 System Configuration Changes ......................................................................................... 10
2.4.1 Software Packages ...................................................................................................... 10
3. V9.3 Upgrade Considerations.......................................................................................... 13

3.1 Site Upgrade Plans ............................................................................................................ 13
3.2 Control Software Support for Control Core Services V9.0 or Later ................................... 13
3.3 Supported Topologies and System Rules ........................................................................... 13
3.4 System Configuration and Installation .............................................................................. 13
3.5 Interoperability ................................................................................................................. 14
3.5.1 AIM*API as a Replacement for FoxAPI ..................................................................... 18
iii
B0700SV – Rev F Contents
3.5.2 Control Core Services Interoperability and Compatibility ......................................... 18

3.5.3 Security Enhanced Control Core Services
Interoperability and Compatibility ..................................................................................... 19
3.6 Supported Operations ....................................................................................................... 21
3.6.1 Control Processor 270 and FCP280 Upgrade Recommendation ............................... 21
4. V9.3 Hardware Requirements ......................................................................................... 23
5. V9.3 System Setup .......................................................................................................... 25

5.1 V9.3 Documentation ........................................................................................................ 25
5.2 V9.3 Media ....................................................................................................................... 25
5.3 Additional Software Packages ............................................................................................ 27
6. V9.3 Installation Overview.............................................................................................. 31

6.1 Pre-Installation and Migration Procedures ........................................................................ 31
6.1.1 Backing Up the CSA Database .................................................................................. 31
6.2 Workstation and Server Software Installation .................................................................... 31
6.3 Post-Installation and Migration Procedures ....................................................................... 32
6.3.1 Restoring the CSA Database ...................................................................................... 32
6.3.2 Configuring Display Color Settings ........................................................................... 32
6.3.3 Updating FCP270s, ZCP270s, FCP280s, and ATS Images ....................................... 32
6.3.4 Performing EEPROM Updates ................................................................................. 33
6.3.5 Backing Up Hard Disks ............................................................................................ 33
6.3.6 Reconciling the Configuration .................................................................................. 33
7. V9.3 Operational Recommendations............................................................................... 35

7.1 Day 1 Installation of Control Core Services v9.3 ............................................................... 35
7.2 Installation of Foxboro Evo Control Software 6.0.x or v6.1-v6.2 on
Control Core Services v9.3 ...................................................................................................... 35
7.3 Installations with Multiple CPU Core Feature .................................................................. 37
7.3.1 Disabling the Microsoft Exchange Scan Add-In in
McAfee® VirusScan Enterprise (VSE) ............................................................................... 37
7.4 Control Core Services Security Enhancements .................................................................. 39
7.4.1 Using the Autologon Feature ..................................................................................... 39
7.4.2 Security Enhanced Foxboro Evo System Setup ......................................................... 39
7.4.3 Removal of the McAfee HIP Software ....................................................................... 39
7.4.4 Non-Expiring Password for ePO Console Logins ...................................................... 39
7.4.5 Terminal Services and Remote Desktop Services ....................................................... 40
7.4.6 Station Assessment Tool ............................................................................................ 41
7.4.7 Time Zone and Foxboro Station Assessment Tool ................................................... 41
7.4.8 Firewall Functionality ................................................................................................ 41
7.4.9 Guidelines for Using BESR for Backing Up and Restoring Domain Controllers ....... 41
7.4.10 Removing and Adding Stations from/to a Domain .................................................. 43
7.5 System Configuration ....................................................................................................... 50
7.5.1 Blue Screen Resulting from COMM10 Ports Configured with Printers .................... 50
7.6 User Accounts for Standard Installations ........................................................................... 50
iv
Contents B0700SV – Rev F
7.6.1 ia User Account ......................................................................................................... 51

7.6.2 Configuring a Remote User Account ......................................................................... 51
7.7 Software Installation .......................................................................................................... 56
7.7.1 Resolving Suboptimal Conditions During Software Installation ................................ 56
7.7.2 Migration from I/A Series Software v8.5 to
Foxboro Evo Control Core Services v9.0 ............................................................................ 56
7.7.3 Performing a Day 1 Installation Procedure with
Address Translation Station (ATS) ..................................................................................... 56
7.7.4 Successfully Creating and Appending to a Reconcile Diskette ................................... 57
7.8 Windows Workstations ..................................................................................................... 57
7.8.1 Self-Hosting or Auto-Checkpoint Host Limitations (CP270s or Later CPs) .............. 57
7.8.2 NIC Configuration Settings ...................................................................................... 57
7.8.3 Viewing the Exceed Log File from the Desktop Taskbar ........................................... 57
7.8.4 IP Netmask Settings of Windows Workstations on the Nodebus .............................. 58
7.8.5 Resolution and Color Settings of Multi-Headed Workstation Displays ..................... 59
7.8.6 Screen Savers ............................................................................................................. 59
7.8.7 Security Feature in Windows 7 and Windows Server 2008 R2 Standard ................... 59
7.9 Solaris 10 Stations ............................................................................................................. 60
7.9.1 GNOME Session Manager Segmentation Fault ........................................................ 60
7.10 System Monitor .............................................................................................................. 60
7.10.1 System Monitor Messages Reporting Unavailable Workstations .............................. 60
7.10.2 System Monitor Behavior after Power Becomes Unavailable ................................... 60
7.11 Object Manager Software ................................................................................................ 60
7.11.1 OM API register_name Function ............................................................................ 60
7.12 Displays .......................................................................................................................... 60
7.12.1 Detail Display Differences on Workstations on
The Nodebus and The Foxboro Evo Control Network ..................................................... 60
7.13 Application Software ....................................................................................................... 61
7.13.1 IFDC Software ........................................................................................................ 61
7.14 Alarm Management Subsystem ....................................................................................... 61
7.14.1 Clearing Alarms from Alarm Displays ..................................................................... 61
7.14.2 Alarm Counts and Page Counts .............................................................................. 61
7.14.3 Configuring Alarm Management Options for V8.x Systems Using ADMC ............ 62
7.14.4 Previously Deleted Alarm Manager Configuration Files .......................................... 63
7.14.5 Moveability of Full Screen Current Alarm Display (CAD) ...................................... 63
7.14.6 Message Manager Software ...................................................................................... 63
7.14.7 Running a Single Message Manager ....................................................................... 63
7.14.8 Configuring Default Alarm Manager ...................................................................... 63
7.15 Historian Software .......................................................................................................... 64
7.15.1 Assumptions ............................................................................................................ 64
7.15.2 Historian Installation .............................................................................................. 64
7.15.3 Historian Configuration .......................................................................................... 64
7.15.4 Historian Naming ................................................................................................... 65
7.15.5 Changing Points on a FoxView Trend Display to a New Historian Name .............. 66
7.16 Control Configuration Software ...................................................................................... 66
7.16.1 Detected Error Message When Deleting a Block or Compound in ICCAPI ............ 66
7.16.2 ECB Period for HART FBMs ................................................................................. 66
7.16.3 Station Must Not Be Shutdown or Rebooted While ICC is Open .......................... 66
v
7.17 Control Software ............................................................................................................. 66

7.17.1 Updating Sequence Block Code after Migration to a New Operating System or
NutCracker Version ........................................................................................................... 66
7.17.2 Re-Alarming Change in FCP270 and ZCP270 CP Images V2.5 and Later ............. 79
7.17.3 Re-Alarming for Multiple Alarm Priority Types ...................................................... 80
7.17.4 Migrating a Control Database to an FCP280, FCP270, or ZCP270 ....................... 80
7.17.5 Changing Block Modes on DO or AO Blocks ......................................................... 81
7.17.6 Dynamically Reconfiguring a Block Parameter ........................................................ 81
7.17.7 PAKOUT Block Limitations ................................................................................... 81
7.17.8 Using AOUTR Blocks with ECB38R for FBM46/FBM246 Applications ............... 82
7.17.9 Using the OSP 0 Instruction in the LOGIC Block .................................................. 82
7.18 Control Processor (FCP280, FCP270 and ZCP270) ....................................................... 82
7.18.1 Use of Self-Hosting Feature ..................................................................................... 82
7.18.2 Validating FCM100E and FCM100Et Settings (ZCP270 Only) ............................ 83
7.18.3 Issuing a Reboot Command for a Shadow FCP280 or CP270 Module ................... 83
7.18.4 Addressing Stations with Numeric Letterbugs ......................................................... 83
7.18.5 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 ............................................................... 84
7.18.6 Setting Primary ECB Parameter BAUD2M for 100 Series FBMs ............................ 85
7.19 Field Device Controller 280 (FDC280) .......................................................................... 85
7.19.1 Setting Timeout Option for Modbus TCP Client Driver for
Interfacing Tricon and Trident Devices .............................................................................. 85
7.20 Address Translation Station (ATS) .................................................................................. 86
7.20.1 Communicating Directly to an ATS ........................................................................ 86
7.20.2 Station Support for Address Translation Station ...................................................... 86
7.20.3 Network Fault Detection Logs ................................................................................ 87
7.21 Intrinsically Safe I/O Subsystem ...................................................................................... 88
7.21.1 Using SRD991 with the Intrinsically Safe I/O Subsystem ....................................... 88
7.22 Fieldbus Modules (FBMs) and Field Communication Modules (FCMs) ......................... 88
7.22.1 Redundant FBM248 Pulse Count ........................................................................... 88
7.22.2 Configuring the FBM206 Input Frequency Using the RES04 Parameter ................ 88
7.22.3 Master/Tracker FBM222 Role Switches .................................................................. 89
7.22.4 Signal Conditioning in RIN Block for FFH1 d/p Cell ............................................ 89
7.22.5 EEPROM Updating FBM216s with Software Prior to V2.35F ............................... 89
7.22.6 Duplicate Channel Numbers for FoxCom Transmitters (ECB18) and FoxCom
Valves (ECB74) .................................................................................................................. 90
7.22.7 Configuring FCMs for Simplex Operation .............................................................. 90
7.22.8 Validating Compact PROFIBUS Configuration File ............................................... 91
7.22.9 Performing General Downloads .............................................................................. 91
7.22.10 FBM216 Role Switch ........................................................................................... 91
7.22.11 200 Series FBM Rate of Change Alarms ................................................................ 91
7.22.12 Configuring Fail-Safe for Proper Operation of FBM218 ....................................... 92
7.22.13 EEPROM Updating FBM220 and FBM221 ........................................................ 92
7.22.14 Field Device System Integrator (FDSI) Subsystem ................................................ 92
7.22.15 Displaying FoxCom Device Information After General Download ....................... 93
7.22.16 FBM223 PROFIBUS Configurator ...................................................................... 93
7.23 FOUNDATION fieldbus, PROFIBUS-DP, HART, Modbus, DeviceNet, and FDSI .... 93
7.23.1 DeviceNet Baud Rate .............................................................................................. 93
vi
7.24 Tools and Utilities ........................................................................................................... 94

7.24.1 Getpars Utility (CAR #1012329) ............................................................................ 94
7.24.2 Run Utilities as Administrator ................................................................................. 94
7.25 Peer-to-Peer Connections of Real-Type Block Inputs ...................................................... 94
7.26 Virus Scan Exclusions ..................................................................................................... 95
7.27 Data Transfers Between the Nodebus and The Foxboro Evo Control Networks ............. 95
7.28 Control Blocks and Parameters ....................................................................................... 96
7.28.1 Changing FSENAB for ECB200 (PROFIBUS-DP FBM223) ................................. 96
7.28.2 TIMSTP Parameter of the EVENT Block ............................................................... 96
7.29 Exceed Software .............................................................................................................. 96
7.29.1 IP Address Displayed in the Exceed Icon ................................................................. 96
7.30 Foxboro Evo Control Core Services Startup and Security Options .................................. 96
7.30.1 Foxboro Evo Control Core Services Startup Options .............................................. 96
7.30.2 Autologon ............................................................................................................. 102
7.30.3 Restricted Desktop ................................................................................................ 104
7.30.4 Welcome Screen .................................................................................................... 105
7.30.5 Locking/Unlocking the Station ............................................................................. 107
7.30.6 Windows Task Manager ........................................................................................ 107
7.31 Control Core Services Log Off and Shut Down ............................................................ 107
7.31.1 Logging Off ........................................................................................................... 107
7.31.2 Shutting Down/Restarting the Station .................................................................. 108
7.31.3 Shut Down Configuration .................................................................................... 109
7.32 Migrating Existing Workstation or Server
with Windows XP or Windows Server 2003 ......................................................................... 110
7.33 Connecting a Station to an Off-Control Network Domain .......................................... 110
8. V9.3 User Notes ............................................................................................................ 111

8.1 Windows Workstations ................................................................................................... 111
8.1.1 Messages Appearing Post-Installation for Domain Controllers ................................ 111
8.1.2 “Local Area Connection” Not To Be Renamed in Network Connections ............... 111
8.1.3 Printer Monitor Warning in SMON Indicates Normal Operation ......................... 111
8.1.4 Additional Security for Plant Operators and View Only Users ............................... 111
8.1.5 User Accounts after an Active Directory Migration ................................................ 114
8.1.6 Inadvisable to Install USB Annunciator Keyboard Upgrade Media (K0174LG) on
Workstations/Servers with Control Core Services ............................................................. 115
8.1.7 System Manager Does Not Succeed In Removing Database Locks Resulting
in “Cannot Initiate Action” Message ................................................................................ 115
8.1.8 Administrator Password Not Set After Image Restoration for HP DL380 Gen9
and Later Servers .............................................................................................................. 117
8.2 Applications .................................................................................................................... 117
8.2.1 FoxDraw ................................................................................................................. 117
8.2.2 Station Assessment Tool (SAT) ............................................................................... 118
8.3 Application Software ....................................................................................................... 119
8.3.1 SOE and FoxHSDAI.exe Process ............................................................................ 119
8.3.2 TDR Does Not Succeed in Printing Reports to Network Printer ............................ 119
8.3.3 Printing Alarm Priority to the Alarm Printer ........................................................... 119
8.4 Device Monitor ............................................................................................................... 121
vii
8.4.1 Device Monitor Master Active on Isolated Segments of

Foxboro Evo Control Network ......................................................................................... 121
8.5 I/A Series Configuration Component (IACC) ................................................................. 122
8.5.1 Using User-Defined Formulas ................................................................................. 122
8.6 Control Processors .......................................................................................................... 122
8.6.1 I/O Load (Fieldbus Scan Load) Increase Due to Failed or
Disconnected Fieldbus Channel ....................................................................................... 122
8.6.2 Removing Married FCP280s From Their Baseplate ................................................ 123
8.7 Fieldbus Modules (FBMs) and Field Communication Modules (FCMs) ......................... 124
8.7.1 Online/Offline States of SPECTRUM I/O Migration Modules under ZCP270 .... 124
8.8 Time Synchronization ..................................................................................................... 124
8.8.1 Incorrect Card Shown After Spectracom Time Card Driver Installation .................. 124
8.8.2 KSI Clock Daemon Application Runs on Startup ................................................... 124
8.9 Device Monitor ............................................................................................................... 124
The Foxboro Evo Control Network ................................................................................. 124
8.10 Foxboro Evo Control Network ..................................................................................... 125
8.10.1 Virtual Router Redundancy Protocol (VRRP) Failover Performance ..................... 125
8.11 Control Network Interface ............................................................................................ 126
8.11.1 Initiating Reboot or Image Update Action on CNI using
System Manager v2.6 ....................................................................................................... 126
8.11.2 Disabling Reporting Unavailability of Single Power Supply for CNIs
via System Key in Foxboro Evo System Monitor Applications .......................................... 126
8.11.3 Continuous Reboot of Fault Tolerant CNI Pair Following Change
in Letterbug ..................................................................................................................... 127
8.11.4 Empty Engineering Units Field Can Lead to Delays in
FoxView Trend Display Callup ........................................................................................ 127
8.11.5 Resolving Graphical Corruption with Foxboro Evo Control HMI Displays
Showing Data from CNIs ................................................................................................ 128
8.11.6 Remote Attributes on Displays Take Minutes to Show Initial Values
On Invocation .................................................................................................................. 129
8.11.7 Monitoring Change Driven Updates per Second Between
Connected Control Network Interfaces ............................................................................ 129
9. Customer Cases Resolved in V9.3 ................................................................................. 131
Appendix A. Files to Back Up/Restore............................................................................... 151

A.1 Saving Files ..................................................................................................................... 151
A.2 Files to Back Up/Restore for Day 0 Migration ................................................................ 151
A.2.1 CNI Files ................................................................................................................ 151
A.2.2 Application Databases ............................................................................................. 151
A.2.3 Display-Related Files .............................................................................................. 152
A.2.4 System-Related Files ............................................................................................... 153
A.3 Backing Up and Restoring Compound Summary Access (CSA) ..................................... 154
A.3.1 Backing Up CSA (CSA_Save) ................................................................................. 154
A.3.2 Relocating CSA ....................................................................................................... 155
A.3.3 Restoring CSA (CSA_Merge) ................................................................................. 156
viii
Appendix B. EEPROM Revision Levels............................................................................. 157

B.1 Image Revision Levels for Control Stations and
ATS with Control Core Services v9.3 .................................................................................... 157
B.2 100 Series FBM Software and EEPROM Versions ......................................................... 158
B.3 200 Series FBM Software and EEPROM Versions ......................................................... 162
ix
x
Tables
1-1. Foxboro Evo Product Rebranding ................................................................................. 7
2-1. New Software Package for Control Core Services v9.3 ................................................ 10
2-2. Recommended Packages for On-Control Network Workstations ................................ 10
3-1. Overview of Control Core Services or I/A Series Software
Component Compatibility .......................................................................................... 14
4-1. Platforms Supporting Control Core Services v9.3 ....................................................... 23
5-1. Control Core Services v9.3 Day 0 Media Kit (K0201HY-H) ...................................... 25
5-2. Additional Packages for Foxboro Evo Control Core Services V9.3
with Media Kits .......................................................................................................... 27
7-1. General Migration Considerations .............................................................................. 67
7-2. HLBL Migration Considerations ................................................................................ 67
7-3. SFC Migration Considerations .................................................................................... 68
7-4. Minimum Versions for Nodebus Stations Running on
The Foxboro Evo Control Network ............................................................................ 86
B-1. Control Core Services V9.3 Control Station and ATS EEPROM/Image
and Software Revision Levels ..................................................................................... 157
B-2. Control Core Services V9.3 Legacy Station EEPROM/Image
and Software Revision Levels ..................................................................................... 158
B-3. Software Versions of 100 Series FBMs (Y Form Factor) ............................................ 159
B-4. Software Versions for 200 Series FBMs (DIN Rail Mounted Form Factor) ............... 163
B-5. EEPROM Revision Levels for 200 Series FBMs
(DIN Rail Mounted Form Factor) ............................................................................ 166
xi
B0700SV – Rev F Tables
xii
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.3 and also
describes their features.
Throughout these release notes, references are made to contacting the Global Customer Support
(GCS). In the U.S.A., call 1-866-746-6477, e-mail https://pasupport.schneider-electric.com or visit
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 release of this document (B0700SV, Rev. F), the following changes were made:
Chapter 7 “V9.3 Operational Recommendations”
♦ Added footnote under Table 7-4 “Minimum Versions for Nodebus Stations Running
on The Foxboro Evo Control Network” on page 86.
Appendix B “EEPROM Revision Levels”
♦ Added first footnote under Table B-1.
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.
♦ Integrated Control Block Descriptions (B0193AX)
♦ System Definition: A Step-By-Step Procedure (B0193WQ, Rev. L or later)
♦ System Definition Release Notes for Windows 7 and Windows Server 2008 (B0700SH)
♦ System Management Displays (B0193JC)
♦ I/A Series Configuration Component (IACC) User's Guide (B0700FE)
♦ I/A Series Configuration Component (IACC) V2.6 Release Notes (B0700SM)
♦ Field Control Processor 280 (FCP280) User's Guide (B0700FW)
♦ Field Control Processor 280 (FCP280) Sizing Guidelines and Excel® Workbook
(B0700FY)
xiii
B0700SV – Rev F Preface
♦ 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)
♦ The Foxboro Evo Control Network Architecture Guide (B0700AZ)
♦ Address Translation Station User’s Guide (B0700BP)
♦ Field Control Processor 280 (FCP280) On-Line Image Update (B0700FX)
♦ Control Processor 270 (CP270) On-Line Image Update (B0700BY)
♦ Security Enhancements User's Guide for I/A Series Workstations with Windows 7 or
Windows Server 2008 Operating Systems (B0700ET)
♦ Station Assessment Tool (SAT) User’s Guide (B0700DZ)
♦ Optional McAfee® Security Products Installation and Configuration Guide for DVD
K0174LX (B0700EZ)
♦ Optional McAfee® Security Products Installation and Configuration Guide (B0700EX)
♦ Symantec System Recovery 2013 Desktop, Server and Virtual Editions Guide for I/A Series
Systems (B0700EY)
♦ Control Core Services v9.3 Software Installation Guide (B0700SW)
♦ 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)
♦ V8.5 Release Notes (B0700SC)
♦ V8.3 Software for the Solaris Operating System Release Notes and Installation Procedures
(B0700RR)
♦ V8.3 Release Notes and Installation Procedures for the Windows Operating System
(B0700RP)
♦ V8.2 Release Notes and Installation Procedures (B0700RN)
♦ Control Database Deployment User’s Guide (B0750AJ)
♦ System Manager (B0750AP)
♦ System Manager V2.9 Release Notes (B0750RS)
♦ Foxboro Evo Control Software Installation Guide (B0750RA)
♦ Control Software v6.2 Release Notes (B0750SL)
xiv
Preface B0700SV – Rev F
♦ Control Software v6.1 Release Notes (B0750SJ)

♦ FoxView Software v10.4 (B0700FC, Rev. D or later)
♦ FoxDraw Software v10.4 (B0700FD, Rev. E or later)
♦ FoxView and FoxDraw V10.4.4 Release Notes (B0700SN)
♦ FERRET V6.0.3 (Windows Platforms) and FERRET V6.0 (UNIX Platforms) Installa-
tion and Release Notes (B0860RL)
♦ 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)
♦ Control Processor 270 (CP270) and Field Control Processor 280 (CP280) Integrated
Control Software Concepts (B0700AG)
♦ The MESH Control Network Sizing Guidelines (B0700AX)
♦ 100 Series Fieldbus Module Upgrade User's Guide (B0700BQ)
♦ Intelligent Field Device Configurator (IFDC) Version 3.2 Release Notes (Windows 7 and
Windows Server 2008 Platforms) (B0700SK)
♦ Intelligent Field Device Configurator IFDC for use with I/A Series Systems (B0700EU)
♦ Virtualization User’s Guide (B0700VM)
♦ 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)
♦ 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)
xv
♦ 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)
♦ 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)
xvi
Preface B0700SV – Rev F
♦
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)
♦ 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)
♦ Printer Installation for I/A Series Software v8.x (Windows 7 and Windows Server 2008
Platforms) (B0700EW)
Hardware and Software Specific Documentation for Windows 7 Operating System
♦ Hardware and Software Specific Instructions for Model H92 (HP Z440) (Windows 7
Operating System) (B0700GL)
♦ Hardware and Software Specific Instructions for Magelis 2U Rack Workstation
(Windows 7 Operating System) (B0700GF)
♦ Hardware and Software Specific Instructions for Model H92 Workstation (HP Z420)
(Windows 7 Operating System) (B0700FS)
♦ Hardware and Software Specific Instructions for Model H92 with Windows 7 Operating
System (Z400) (B0700FF)
♦
Hardware and Software Specific Instructions for Model P92 Workstation (T3500 Gen II)
with Windows 7 Operating System (B0700FM)
♦ Hardware and Software Specific Instructions for Model P92 Workstation (T3500) with
Windows 7 Operating System (B0700FJ)
Hardware and Software Specific Documentation for Windows Server 2008 R2 Standard
Operating System
xvii
♦ Hardware and Software Specific Instructions for Model H90 (HP DL380 Gen9) Win-
dows Server 2008 Operating System (B0700GK)
♦ Foxboro Evo Process Automation System Hardware and Software Specific Instructions for
Magelis 4U Rack Server (Windows Server 2008 Operating System) (B0700GG)
♦ Hardware and Software Specific Instructions for Model H90 (HP DL380 E5645 CPU)
Windows Server® 2008 Operating System (B0700GB)
♦ Hardware and Software Specific Instructions for Model P91 (T710 Gen II) with Win-
dows Server® 2008 Operating System (B0700FP)
♦ Hardware and Software Specific Instructions for Model P90 (R710 Gen II) with Windows
Server® 2008 Operating System (B0700FN)
♦ Hardware and Software Specific Instructions for Model P91 (T610) with Windows
Server® 2008 Operating System (B0700FL)
♦ Hardware and Software Specific Instructions for Model P90 (R710) with Windows
Server® 2008 Operating System (B0700FK)
♦ Hardware and Software Instructions for Model H91 Workstation (HP ML350) with
Windows Server 2008 Operating System (B0700FH)
♦ Hardware and Software Instructions for Model H90 Workstation (HP DL380) with
Windows Server 2008 Operating System (B0700FG)
Hardware and Software Specific Documentation for Windows Server 2008 R2 Enterprise
Operating System
♦ Hardware and Software Specific Instructions for Foxboro Evo™ Control Core Services and
I/A Series® Model V90 Server Virtualization Host (HP DL380 Gen9) Windows
Server® 2008 Enterprise Operating System (B0700GM)
♦ Hardware and Software Specific Instructions for I/A Series Model V90 Server Virtualiza-
tion Host (DL380) (Windows Server 2008 R2 Enterprise Operating System) (B0700VA)
♦ Hardware and Software Specific Instructions for I/A Series Model V90 Server Virtualiza-
tion Host (HP DL380 E5645 CPU) Windows Server 2008 R2 Enterprise Operating
System (B0700VB)
Hardware and Software Specific Documentation for Windows Server 2012 Standard Operating
System
♦ Hardware and Software Specific Instructions for Foxboro Evo Control Core Services and
I/A Series Model V91 Server Virtualization Host (HP DL380 Gen9) Windows Server
2012 Standard Operating System (B0700VS)
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.3 release and an overview of its software
installation.
1.1 Overview of the Control Core Services v9.3

Release
The Control Core Services v9.3 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.3 Release”.
1.2 Hardware Requirements

The Control Core Services v9.3 can be only installed on the H90/P90, H91/P91, and H92/P92
platforms listed in “Reference Documents” on page xiii, provided they meet the specifications
listed in Chapter 4 “V9.3 Hardware Requirements” and are configured correctly.
Memory requirements for Control Software1 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.3 Hardware Requirements” for additional information.
1.3 Domain Controllers

In order to install the security enhanced Control Core Services (also known as Security Enhanced,
or SE, software) on your Foxboro® system, you ave to have 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 security enhanced 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.3 Software Installation Guide (B0700SW).
1.
Control Software workstations and servers run the Foxboro Evo Control Software.
1
B0700SV – Rev F 1. Read Me First
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® 7 and
Windows Server® 2008 R2 Standard stations have to be installed with the media defined in Con-
trol Core Services v9.3 Software Installation Guide (B0700SW).
The standard Control Core Services (without security enhancements installed) and security
enhanced Control Core Services can only be installed on these operating system images.
1.5 Control Core Services Security Enhancements

Workstations and servers can be installed with either the standard Control Core Services v9.3
(without security enhancements installed) or security enhanced Control Core Services v9.3.
Within a Foxboro Evo system, co-existence of both types of stations is possible. However, an over-
all Control Core Services system with both standard and security enhanced software is not consid-
ered secure.
For more details on security enhancements, refer to Security Enhancements User's Guide for
I/A Series Workstations with Windows 7 or Windows Server 2008 Operating Systems (B0700ET).
1.6 Control Core Services V9.3 Support for the

Control Software
Control Software v6.0 or later is compatible with Control Core Services v9.3. The previous ver-
sions of Foxboro Control Software (v3.x-v4.x) and InFusion® software are not supported for
Control Core Services v9.1 or later. Control Software installation is described in Foxboro Evo Con-
trol 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 v6.0.2 or later with it.
1.7 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.3 Upgrade Considerations” provides detailed information on
upgrading an existing system.
2
1. Read Me First B0700SV – Rev F
1.7.1 Migrating Files

To migrate databases and preserve customized files for use on a new system with Control Core
Services v9.3, 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 Symantec System Recovery 2013 Desktop, Server and Virtual Editions Guide for
I/A Series Systems (B0700EY) for information about migrating specific Control Core
Services software and control databases to a new system with Control Core Services
v9.3.
♦ 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.3 and the Control Software v6.0 or later.
1.7.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 security enhancements installed and with a standard workstation without
security enhancements 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.8 Installation Overview

The Control Core Services v9.3 has to be installed either on new stations (a Day 0 installation), or
on stations with I/A Series software 8.8 or Control Core Services v9.0-9.2 via a Day 1 installation
or Release Update.
You can upgrade stations with older software to Control Core Services v9.3 via one of the follow-
ing scenarios:
♦ For a station with I/A Series software v8.7 or earlier which is installed on a hardware
platform which supports Windows 7 or Server 2008 R2: 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.3.
♦ For a station with I/A Series software v8.7 or earlier which is not installed on a plat-
form that supports Windows 7 or Server 2008 R2: The new OS platform image is
loaded onto a new workstation which supports Windows 7 or Windows Server 2008
R2 and a Day 0 installation is performed, upgrading the station to Control Core Ser-
vices v9.3.
♦ For a station with I/A Series software v8.8 or Control Core Services v9.0-v9.2, as a
Day 1 or release update installation on top of I/A Series software or Control Core
Services.
3
NOTE
If the existing hardware on which the workstation or server resides does not support
Windows 7 or Windows Server 2008 R2 Standard, a new workstation or server will
be needed. See Chapter 4 “V9.3 Hardware Requirements” for supported platforms.
For details on the Control Core Services v9.3 installation, refer to Control Core Services v9.3 Soft-
ware Installation Guide (B0700SW) and “Installing the Foxboro Evo Control Core Services v9.3
Trailer CD-ROM” on page 4.
To run the Control Software with Control Core Services v9.3, you have to install the Control
Software v6.0 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. V or later).
NOTE
The Control Software v6.0 or later supports I/A Series software v8.8, and Control
Core Services v9.0-v9.3. The initial installation and migration procedures for the
Control Software v6.0 or later are provided in Foxboro Evo Control Software Installa-
tion Guide (B0750RA, Rev. V or later).
The latest revisions of these documents are available on the GCS webpage:
https://pasupport.schneider-electric.com.
1.8.1 Installing the Foxboro Evo Control Core Services v9.3

Trailer CD-ROM
To finish the installation of Control Core Services v9.3, you have to install the V9.3 trailer CD-
ROM (K0174MZ-D) after having installed Control Core Services v9.3 (after a Day 0 operation).
This trailer also needs to be installed after you have completed the installation of a Release
Update.
(The trailer only needs to be installed once; therefore it does not have to be installed after a Day 1
operation unless it was not installed on the station previous to the Day 1 operation.)
The trailer CD-ROM has to be installed on stations running Windows 7 or Windows Server
2008 R2 Standard operating systems as follows:
1. Launch the trailer installation application (QF1305060.msi).
Insert the CD-ROM labeled “Foxboro Evo Control Core Services 9.3 Trailer CD-
ROM” (K0174MZ-D) into the station. Navigate to the CD-ROM with Windows
Explorer and double-click QF1305060.msi to launch the installation.
2. Click Next and then click Install to start the installation process.
If the user currently logged in is not an administrator, a User Account Control (UAC)
prompt may appear. Click Yes to accept the UAC prompt.
4
NOTE
During the trailer installation, if the following message appears, “The Setup must
update files or services that cannot be updated while the system is running. If we
choose to continue, reboot will be required to continue the setup,” click OK. The
installation continues as normal. Do not reboot the station if you see this message.
This message is shown in the event that you are installing the trailer after booting
into the Control Core Services software (which you should not have done if you are
performing this procedure as written in this section).
3. When the installation is finished, click Finish.

4. If you are installing the trailer via a CD-ROM, remove the trailer CD-ROM.
5. If prompted, reboot the workstation. To do this, click the Start button and click
Shut Down; select Restart from the pull-down menu and click OK.
1.8.2 Quick Fix 1287671 for Legacy Workstations and Servers

The following applies to your Control Core Services v9.3 system only if an FDC280 is being
deployed in the system.
To support detail displays updated for Control Core Services v9.3 on legacy workstations and
servers, install workstations and servers with I/A Series software v8.2-v8.8 and Foxboro Evo Con-
trol Core Services v9.0-9.2 with QF1287671.
1.9 Migration Requirements

1.9.1 Migrating a FCP270 or ZCP270 Control Database from a
System with I/A Series Software v8.6 or Earlier
I/A Series software v8.7-v8.8 and Control Core Services v9.0 and later versions include the
LASTGV parameter, which enables the Last Good Value functionality in the RIN and RINR
blocks, as mentioned in V8.7 Release Notes and Installation Procedures (B0700SE). When enabled,
this functionality causes the previous value of MEAS to be retained, and the value obtained from
the current cycle to be ignored for the block. Refer to the sections called “Last Good Value” in the
RIN and RINR chapters of Integrated Control Block Descriptions (B0193AX) for more informa-
tion with regards to this functionality.
Prior to I/A Series software v8.7, the LASTGV parameter did not exist for the RIN and RINR
blocks.
This LASTGV parameter defaults to a value of 1, which activates the Last Good Value functional-
ity (default setting, is not backward compatible with I/A Series software v8.6 or earlier). There-
fore, when migrating control databases from systems with I/A Series software v8.6 or earlier, the
LASTGV parameter on RIN and RINR blocks will default to 1, activating the Last Good Value
functionality on these blocks where this functionality did not previously exist.
Review your RIN and RINR blocks to determine the desired LASTGV parameter value and
update the parameter in your desired control configurator appropriately.
For more information on the RIN and RINR blocks, refer to Integrated Control Block Descriptions
(B0193AX).
5
1.9.2 Migration of Domain Controller from I/A Series Software

v8.5 to v8.8
Your Domain Controller needs to run Windows 2008. If you have already upgraded the system
with I/A Series software v8.5-v8.7 to I/A Series software v8.8 or above, you only need to update
your Domain Controllers with the new set of policies coming with CCS v9.3.
When performing a system migration from I/A Series software v8.5 directly to I/A Series software
v8.8, you have to install QF1023535 on the PDC with I/A Series software v8.5 and every AW in
its domain before performing the system migration process to I/A Series software v8.8. This is dis-
cussed in Control Core Services v9.3 Software Installation Guide (B0700SW). Quick Fixes are avail-
able through our Global Customer Support at https://pasupport.schneider-electric.com.
You can install the Quick Fix on AWs with I/A Series software v8.5 after the PDC’s migration to
I/A Series software v8.8 if needed, as there is nothing that disallows the Quick Fix from being
installed at I/A Series software v8.5.
If you have already upgraded the system with I/A Series software v8.5 to I/A Series software v8.6
or v8.7 prior to migration to v8.8, installing QF1023535 is not necessary as it is already included
and installed on systems with I/A Series software v8.6 and v8.7.
1.10 Security Advisory for Adobe® Reader®

The I/A Series Electronic Documentation media includes the Adobe® Reader® application to
allow users to view the PDF files on this media. For Control Core Services v9.0, the original
K0174MA-A/B DVDs were shipped with Adobe Reader v11.0.0.
On May 19, 2014, US-CERT published a security bulletin describing eight high vulnerabilities in
Adobe Reader. These vulnerabilities are present in Adobe Reader 10.x versions before 10.1.10 and
11.x versions before 11.0.07.
Therefore, it is recommended that 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: http://www.adobe.com/support/downloads/product.jsp?product=10&platform=
windows
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.
As a general recommendation, keep up with the latest security updates of the Adobe Reader.
To improve the security for your system, the following are recommended optimal practices:
♦ 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.11 Foxboro Evo Product Rebranding

For the release of the Foxboro Evo Process Automation System, the latest releases of the products
listed in Table 1-1 were rebranded as follows:
6
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)
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)
7
8
2. Features of Control Core Services
V9.3 Release
This chapter describes the major features and enhancements included with the Control Core
Services v9.3 release.
2.1 Support for FBM248

With Control Core Services v9.3, support for the FBM248, Current/Voltage Analog/Digi-
tal/Pulse I/O Configurable Redundant module was added. The FBM248 is a standard 200 Series
FBM, the redundant equivalent of the standard FBM247. It contains eight redundant channels
which can be individually configured for a range of analog, digital and pulse field I/O signals.
Refer to Intelligent Marshalling Fieldbus Modules - FBM247 and FBM248 (B0700GU) for details
on the FBM248.
NOTE
When adding FBM248s to your system, you have to upgrade your version of Sys-
tem Manager to v2.9 to monitor the FBM248s.
2.2 Support for Field Device Controller 280

(FDC280)
With Control Core Services v9.3, support for the Field Device Controller 280 (FDC280) was
added. The Field Device Controller 280 (FDC280) is a distributed, optionally redundant, field-
mounted controller module, whose primary purpose is for device integration, including interfac-
ing field devices, accessing data in those devices for display, historization, and performing control
tasks.
Creating a database for the FDC280 needs Foxboro Evo Control Software.
Refer to Field Device Controller 280 (FDC280) User's Guide (B0700GQ) for details on the
FDC280.
NOTE
Be aware that ICC does not support FDC280 configuration.
2.3 Additional Features for the Control Network

Interface (CNI)
With Control Core Services v9.3, the Control Network Interface (CNI) supports the distribution
of the following types of alarm and other types of messages among Foxboro Evo systems:
9
B0700SV – Rev F 2. Features of Control Core Services V9.3 Release
♦ Process Alarm messages sent via the APRINT mechanism. Acknowledgements

(ACK), such as horn ACK and horn silence commands, are sent through existing
Object Manager mechanisms.
♦ SOE messages from EVENT blocks
♦ SOE messages from Triconex System Access Application (TSAA)
♦ Sequence block messages
♦ Operator Action Journal (OAJ) messages
This hardware is described in Control Network Interface (CNI) User's Guide (B0700GE, Rev. E or
later).
2.4 System Configuration Changes

Refer to the Control Core Services v9.3 Software Installation Guide (B0700SW) for the software
needed to commit a station with Control Core Services v9.3.
NOTE
Control Core Services v9.0 and later is not supported on Application Workstations
(AW70P), Workstation Processors (WP70P), or FSIM Simulation Stations (FSIM).
2.4.1 Software Packages

For Control Core Services v9.3, the software package listed in Table 2-1 was added.
Table 2-1. New Software Package for Control Core Services v9.3
Name Description Software

OS3I80 FDC280 Image Controller image for the Field Device Controller 280
(FDC280).
Refer to Table 2-2 for recommended software packages, based on the designed role of the station.
This table assumes that the Domain Controller, Galaxy database, and EPO will be on the Fox-
boro Evo Control Network.
Table 2-2. Recommended Packages for On-Control Network Workstations
Station Operational Role Recommended Packages

Windows Domain Controller IAMESH only
Foxboro Evo Control Software Galaxy IAMESH only
Repository
McAfee EPO Server IAMESH only
Workstation Processor Replacement IAMESH, IASVCS, ADDISP, and ASMDW7
(Optionally AMSGM7 and ANSOF7).
Application Workstation Replacement IAMESH, IASVCS, IACTRL, ADDISP, and
ASMDW7 (Optionally ACSA7, AHIST7,
AMSGM7, ANSOF7, and ASMON7).
10
2. Features of Control Core Services V9.3 Release B0700SV – Rev F
If a package is not assigned, it will not be loaded onto the station.
NOTE
The Compound Summary Access (CSA) application package ACSA7 have to be
explicitly assigned to a WSTA70 or WSVR70 station for the program to be
installed. Prior to Control Core Services v9.0, CSA was loaded and available for
installation on an AW70P, even if the package was not assigned. Refer to “Relocat-
ing CSA” on page 155 to add or remove CSA.
11
B0700SV – Rev F 2. Features of Control Core Services V9.3 Release
12
3. V9.3 Upgrade Considerations
This chapter describes information to be considered while upgrading from I/A Series software
v8.5-8.8 or Control Core Services v9.0-v9.2 to Control Core Services v9.3.
3.1 Site Upgrade Plans

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

Services V9.0 or Later
Refer to Foxboro Evo Control Software Installation Guide (B0750RA, Rev. U or later) and Control
Software V6.0 Release Notes (B0750SF) or Control Software v6.0.2 Release Notes (B0750SH) for
planning your upgrade to the Control Software v6.0-6.0.2.
3.3 Supported Topologies and System Rules

There have been no changes to supported topologies and system rules since the v8.2 release.
Address Translations Stations (ATS) allow connection to Nodebus systems running I/A Series
software v4.3/v6.1 or later. Refer to Chapter 3, of V8.2 Release Notes and Installation Procedures
(B0700RN), for information on the Address Translations Stations (ATS), combined Nodebus and
the Foxboro Evo Control Network topologies, dump packets, and general control network
interoperability and coexistence guidelines. B0700RN also describes the general procedures for
transitioning to a combined control network and Nodebus network.
3.4 System Configuration and Installation

For a station with I/A Series software v8.8 or Control Core Services v9.0- v9.2, the Control Core
Services v9.3 can be installed via a Day 1 or Release Update installation.
For configuration and installation instructions specific to the Control Core Services v9.3 release,
refer to Control Core Services v9.3 Software Installation Guide (B0700SW).
Also, for more information specific to this release, refer to Chapter 6 “V9.3 Installation Over-
view”.
13
B0700SV – Rev F 3. V9.3 Upgrade Considerations
3.5 Interoperability
Table 3-1 provides an overview of the compatibility of various commonly used Control Core Ser-
vices 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
FoxView 10.1 √ √ x x x x x x x x
10.2 √ √ x x x x x x x x
10.2.1 √ √ x x x x x x x x
10.2.2 √ √ √ √ x x x x x x
10.2.3 √ √ √ √ √ x x x x x
10.2.4 √ √ √ √ √ x x x x x
10.3 x x x x x √ x x x x
10.4.21 √ √ √ √ √ √ √ √ √ x
10.4.3- √ √ √ √ √ √ √ √ √ √
10.4.42
IACC 2.1 √ x x x x x x x x x
2.3.1 - 2.4 √ √ √ √ √ x √ √ √ √
2.5 x x x x x √ √ √ √ √
2.6-2.6.43 √ √ √ √ √ √ √ √ √ √
AIM*AT 3.4 x x √ √ √ √ x x x x
3.4.1 x x √ √ √ √ √ x x x
(installed by
QF1175712
)
3.4.2 x x √ √ √ √ √ √ √ √
3.4.3 x x √ √ √ √ √ √ √ √
14
3. V9.3 Upgrade Considerations B0700SV – Rev F

Component Compatibility (Continued)

v8.2
System 2.0 √ √ √ x x x x x x x
Manager 2.1 √ √ √ √ x x x x x x
2.2 √ √ √ √ √ x x x x x
2.3 √ √ √ √ √ √ x x x x
2.4 x √ √ √ √ √ √ x x x
(v8.4.4
&
later)
2.5 x √ √ √ √ √ √ √ x x
(v8.4.4
&
later)
2.6 x √ √ √ √ √ √ √ √ x
(v8.4.4
&
later)
2.94 x √ √ √ √ √ √ √ √ √
(v8.4.4
&
later)
Foxboro Evo 5.0 x x x x √ √ √ x x x
Control Soft- 6.0-6.25 x x x x x √ √ √ √ √
ware (“the
Control Soft-
ware”)
Foxboro 3.0 x x x √ x x x x x x
Control Soft- 3.1 x x x x √ x x x x x
ware (Earlier 4.0 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
(Earlier Ver- 1.1 x √ x x x x x x x x
sion of 1.2.2 x √ x x x x x x x x
Foxboro Evo
Control Soft- 2.0 x x √ x x x x x x x
ware) 2.5 x x x √ x x x x x x
15


v8.2
Field Device 3.0 x x x x √ √ x x x x
Manager for 3.1.1 x x x x √ √ √ √ √ √
FOUNDA-
TION field-
bus
Manager for 3.1.1 x x x x √ √ √ √ √ √
HART
Manager for 4.0.1 x x x x √ √ √ √ √ √
PROFIBUS
Field Device 1.0.2 x x x x √ √ √ √ √ √
Manager for
DeviceNet
System Defi- 2.8 √ x x x x x x x x x
nition 2.9 √ √ x x x x x x x x
2.10 √ √ √ x x x x x x x
2.11 √ √ √ √ √ x x x x x
3.0 √ √ √ √ √ √ x x x x
3.1 √ √ √ √ √ √ √ √ x x
3.2 √ √ √ √ √ √ √ √ √ √
3.3 √ √ √ √ √ √ √ √ √ √
FoxSFC 2.0 √ x x x x x
2.1 x x x x x √ √ √ √ √
IFDC 3.1 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
2.3 x x x x √ x x x x x
2.4 x x x x √ √ √ √ √ √
SOE/TDR 1.5.2-1.5.46 √ √ √ √ √ √ √ √ √ √
1.5.67 √ √ √ √ √ √ √ √ √ √
1.68 √ √ √ √ √ √ √ √ √ √
16


v8.2
Notes:
1. Although I/A Series software v8.5 needs a version upgrade of FoxView™ software, it is not necessary to
convert standard definition FoxView .fdf files (for 4:3 aspect ratio monitors). You do need to update
these .fdf files for widescreen (16:9 aspect ratio) monitors as described in FoxDraw™ Software v10.4
(B0700FD.)
FoxView v10.2.3 is the minimum version for I/A Series software v8.4.4.
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.2 needs QuickFix 1269588. Later versions of FoxView software do not need this Quick-
Fix.
2. FoxView v10.4.4 is needed for monitoring FDC280s.
3.
Interoperable compatibility with FoxView/FoxDraw™ v10.3 and later only.
4. System Manager v2.9 is the minimum needed version to monitor FBM248s.
5.
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.
6. SOE/TDR v1.5.2 is the minimum needed version to run FBM247s.
7. SOE/TDR v1.5.6 is the minimum needed version to run FBM219s.
8.
SOE/TDR v1.6 is the minimum needed version to run FBM248s.
The following commonly used applications have been validated to run on Control Core Services
v9.3 systems with or without the security enhancements installed:
♦ FoxView software, v10.4.4
♦ FoxDraw software, v10.4.4
♦ System Manager software, v2.6, v2.9
♦ AIM*AT software v3.4.2, available from https://pasupport.schneider-electric.com.
Includes:
♦ AIM*Historian software
♦ AIM*API software (NetMFC API)
♦ AIM*DataLink software
♦ AIM*Explorer software
♦ AIM*Inform software
♦ AIM*I/O Gate Collector software
♦ AIM*OPC Server software
♦ System Definition software, v3.3
♦ FoxSFC Configurator and Run-Time software, v2.1
17
♦ SOE (Sequence of Events) software, v1.61

♦ TDR/TDA (Transient Data Recorder and Analyzer) software, v1.61
♦ I/A Series Configuration Component (IACC), v2.6.3
♦ Intelligent Field Device Configurator (IFDC) software, v3.2.2
♦ Foxboro Evo Control Software v6.0 or later with QF1257756 (this version is sup-
ported 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, v2.4
3.5.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.5.2 Control Core Services Interoperability and Compatibility

In general, interoperability and compatibility of base software and application software between
standard Control Core Services v9.3 without security enhancements installed 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
♦ IP communications
♦ AIM*API software compatibility
1.
Check with Global Customer Support for the availability of the TDR and SOE applications.
18
3.5.3 Security Enhanced Control Core Services

Interoperability and Compatibility
The security enhanced Control Core Services v9.3 are compatible with standard Control Core
Services v9.0-9.2 on Windows platforms, as well as with I/A Series software v8.8 or earlier releases
running on Windows and Solaris™ platforms.
In general:
♦ Workstations or servers running Control Core Services with security enhancements
installed can co-exist in a system with workstations running standard Control Core
Services v9.3 without security enhancements installed.
♦ Workstations or servers running Control Core Services with or without security
enhancements installed can co-exist in a system with workstations running I/A Series
software v8.8 or earlier.
♦ Workstations or servers running Control Core Services with security enhancements
installed can co-exist in a system with I/A Series software v8.3 or v8.4.2 workstations
running the Solaris 10 operating system on The Mesh (as the Foxboro Evo Control
Network was formerly known as - Solaris workstations cannot operate on the control
network).
♦ Be aware that security enhanced I/A Series software v8.8, and Control Core Services
v9.0-9.3 share the same Active Directory domain settings (group policies, organiza-
tional units, and so forth). A client running I/A Series software v8.8 or Control Core
Services v9.0-9.2 can join a domain run by a server with Control Core Services v9.3.
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.3
The following limitations apply:
♦ ADMC display configuration files cannot be distributed from workstations or servers
with standard Control Core Services to workstations or servers with security enhanced
Control Core Services v9.3.
♦ ADMC display configuration files cannot be distributed from workstations or servers
with security enhanced I/A Series software v8.7 to workstations or servers with secu-
rity enhanced Control Core Services v9.3 unless the ADMC compatibility utility is
installed on the stations with security enhanced I/A Series software v8.7.
NOTE
Security enhanced I/A Series software v8.8 and Security enhanced Control Core
Services v9.0-v9.3 are compatible with respect to ADMC operations.
♦ CP Blocks cannot be deployed or un-deployed to/from CPs hosted by work sta-

tions/servers with security enhanced Control Core Services v9.3 from IACC running
on workstations or servers with standard Control Core Services.
♦ CP blocks cannot be deployed or un-deployed to/from CPS hosted by worksta-
tions/servers with security enhanced Control Core Services v9.3 from IACC running
19
on workstations or servers with security enhanced Control Core Services v9.0-9.1 or

I/A Series software v8.8 or earlier.
♦ Station Assessment Tool running on stations with standard Control Core Services
cannot access workstations or servers with security enhanced Control Core Services
v9.3.
The following applications have not been validated to run on systems with I/A Series software
v8.8 or Control Core Services v9.0-9.3. 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 poli-
cies 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
♦ Isolation Station software
Contact the Global Customer Support (GCS) at https://pasupport.schneider-electric.com, to discuss
the availability of these applications.
20
3.6 Supported Operations

Unless specifically mentioned in this document, the same operations that were supported in Win-
dows I/A Series software v8.2 through v8.8 for the Windows operating system are also supported
in v9.3. The operations that could be performed from Nodebus to the Foxboro Evo Control Net-
work 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 Procedures (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
3.6.1 Control Processor 270 and FCP280 Upgrade

Recommendation
After the installation of the workstation software, it is recommended that Control Processor 270s
(FCP270 and ZCP270) and FCP280s hosted by workstations with Control Core Services v9.2
have an image update. If this action is desired, careful planning is needed.
For replacing workstations/servers with Windows XP or earlier operating systems with worksta-
tion/servers with later operating systems without rebooting their CPs and without loading a dif-
ferent image version in them, refer to Procedure for Workstation Upgrade without Control Processor
(CP) Reboot (B0860CP).
For legacy control processors, refer to Appendix B “EEPROM Revision Levels” for the latest
image version numbers for these modules.
21
22
4. V9.3 Hardware Requirements
This chapter provides hardware and software requirements and lists supported hardware
requirements.
Control Core Services v9.3 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.3
Station Type Platform with Multicore CPU Cores Enabled

Workstation H92 HP Z400 Workstation (Model H92, Style B)
H92 HP Z420 Workstation (Model H92, Style D/A)
H92 HP Z440 Workstation
Server H90 HP DL380 Server (Model H90, Style B, E, or newer style)
H90 HP DL380 with E5645 CPU Server (Model H90, Style D/C/A)
Magelis M92 P0928KK Magelis Workstation
M90 P0928KM Magelis Server
Virtual Machine V90 HP DL380 VM Host
Host V91 HP DL380 Server 2013 VM Host
NOTE
With the current Foxboro Evo Control Core Services software, the default station
state is to enable multicore CPU usage. Older hardware may not be officially
qualified to run Control Core Services software in multicore.
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 Workstations Windows® 7 Professional Operating System (PSS 31H-4H92)
♦ Model H90 Workstation Servers for the Windows Server® 2008 R2 Operating System
(PSS 31H-4H90)
♦ Virtualization Server Host Hardware Model V90 (PSS 31H-4V90)
♦ Virtualization Server Host Hardware Model V91 (PSS 31H-4V91)
If you need a serial port in your H90 and H92, the serial card has to be added. Refer to the Hard-
ware and Software Specific Instructions for the card appropriate for your specific station.
23
B0700SV – Rev F 4. V9.3 Hardware Requirements
24
5. V9.3 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.3 and preparing for
process operation, refer to Control Core Services v9.3 Software Installation Guide (B0700SW) and
“Installing the Foxboro Evo Control Core Services v9.3 Trailer CD-ROM” on page 4.
5.1 V9.3 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.3 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.3 Media

Use the checklists below to verify that you have the necessary media to install Control Core Ser-
vices v9.3.
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.3 system, verify that the workstation meets the Control Core
Services v9.3 minimum hardware requirements (see Chapter 4 “V9.3 Hardware
Requirements”) and that the Control Core Services v9.3 media kit is available.
You need the media from the Control Core Services v9.3 kit to perform a Control Core Services
v9.3 Day 0 installation or Day 1 upgrade. Then you will need to install the trailer media as
described in “Installing the Foxboro Evo Control Core Services v9.3 Trailer CD-ROM” on
page 4.
Table 5-1. Control Core Services v9.3 Day 0 Media Kit (K0201HY-H)
Media Kit DVD/CD

Part Number Part Number Description
K0174MS-C Foxboro Evo Control Core Services v9.3 Windows 7/Server 2008
R2 Day 0 DVD
K0174MZ-D Foxboro Evo Control Core Services v9.3 Trailer Media
25
B0700SV – Rev F 5. V9.3 System Setup
Table 5-1. Control Core Services v9.3 Day 0 Media Kit (K0201HY-H) (Continued)
Media Kit DVD/CD

Part Number Part Number Description
K0201HU-D SysDef v3.3 Media Kit, includes:
♦ System Definition V3.3 CD-ROM (K0174MC-C)
♦ System Definition: A Step-By-Step Procedure (B0193WQ-M)
♦ System Definition Release Notes for Windows 7 and Windows
Server 2008 (B0700SH-G)
K0201HT-F System Manager V2.9 Kit, includes:
♦ System Manager Software CD-ROM (K0174MB-E)
♦ System Manager Release Notes (B0750RS-K)
♦ System Manager User Guide (B0750AP-S)
K0174KF-C AIM*AT V3.4.3 CD ROM
K0174MD- FERRET v6.1.1 for Windows includes the FERRET installation
D CD-ROM and:
♦ FERRET V6.0.3 (Windows® Platforms) and FERRET V6.0
(UNIX® Platforms) User's Guide (B0860BH-D)
♦ FERRET V6.0.3 (Windows Platforms) and FERRET V6.0
(UNIX Platforms) Installation and Release Notes (B0860RL-
D)
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-C Foxboro Evo V9.3 Electronic Documentation DVD-ROM,
Includes:
♦ Control Core Services v9.3 Software Installation Guide
(B0700SW)
♦ Control Core Services v9.3 Release Notes (B0700SV)
26
5. V9.3 System Setup B0700SV – Rev F
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.3, which are available in media
kits.
Table 5-2. Additional Packages for Foxboro Evo Control Core Services V9.3
with Media Kits
Part Number Description

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)
K0201GD-F FoxView/FoxDraw V10.4.4 Media Kit for Windows 7/Server 2008 R2
Standard - Includes:
♦ FoxView/FoxDraw V10.4.4 Software CD-ROM (K0174KH-F)
♦ FoxView Software v10.4 (B0700FC, Rev. D or later)
♦ FoxView and FoxDraw V10.4.4 Release Notes (B0700SN-G)
K0201GE-F FoxDraw V10.4.4 Media Kit for Windows 7/Server 2008 R2 Standard -
Includes:
♦ FoxDraw Standalone V10.4.4 Software CD-ROM (K0174KJ-F)
♦ FoxView and FoxDraw V10.4.4 Release Notes (B0700SN-G)
- Extended Frame Services (EFS) V2.6 Media Kits - order individually:
♦ PACTWARE - FDT Frame Application CD-ROM (K0201AV-E)
♦ HART Device Type Managers CD-ROM (K0201AW-G) - Code-
Wrights Third Party Device DTM Library
♦ FDT Device Manager Components (EFS) v2.6 CD-ROM
(K0201AX-G)
♦ Extended Frame Services and Foxboro Evo or I/A Series Communication
DTMs (B0400EF-N)
♦ Extended Frame Services 2.6 Release Notes (B0400EH-J)
K0201GW-B Intelligent Field Device Configurator (IFDC) for Windows 7/Server 2008
R2 Media Kit, includes:
♦ IFDC Software CD-ROM (K0174KV-B)
♦ Intelligent Field Device Configurator (IFDC) V3.2 2 Release Notes
(Windows 7 and Windows Server 2008 Platforms) (B0700SK-C)
♦ Intelligent Field Device Configurator IFDC for use with I/A Series Systems
(B0700EU-A)
K0173WH-E Sequence of Events (SOE), includes:
♦ Sequence of Events (SOE) User's Guide (B0700AK-L)
♦ Sequence of Events (SOE) v1.6 Release Notes (B0700RM-G)
27
with Media Kits (Continued)

K0173WJ-E Transient Data Recorder and Analyzer (TDR/TDA), includes:
♦ Transient Data Recorder and Analyzer (TDR/TDA) User's Guide
(B0700AL-K)
♦ Transient Data Recorder and Analyzer (TDR/TDA) V1.6 Release Notes
(B0700RL-E)
K0201GC-F I/A Series Systems Configuration Component (IACC) v2.6.4 for Windows
Media Kit - Includes:
♦ IACC V2.6.x CD-ROM (K0174KG-F)
♦ I/A Series Systems Configuration Component (IACC) User's Guide
(B0700FE-C)
♦ I/A Series Systems Intelligent Design Studio (IDS) Library for IACC
(B0400BQ-C)
♦ I/A Series Systems Learning to Use IACC (B0400BT-C)
♦ I/A Series Systems High Level Language (HLBL) User's Guide
(B0400DF-J)
♦ I/A Series Configuration Component (IACC) V2.6.4 Release Notes
(B0700SM-J)
K0201AX-G I/A Series Systems FDT Device Manager Components v2.6 for HART®
and FoxCom™ Devices
K0173XC-H MODBUS Driver for FDSI Modules v2.5 Ethernet (TCP/IP) and Serial
Media Kit
K0173XD-F 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 Interface Downloadable Driver for FDSI CD-ROM
(K0173WG-C)
♦ FDSI Configurator V1.5 CD-ROM (K0173WZ-F)
K0201GX-A Sequential Function Chart Editor (FoxSFC) for Windows 7/Server 2008 R2
Media Kit - Includes CD-ROM (K0174KW-A)
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.
K0201BM-C FDSI Ethernet/IP Driver Media Kit - Includes:
♦ Field Device Systems Integrator Ethernet/IP Driver CD-ROM
(K0174CP-D)
♦ FDSI Driver - Allen-Bradley Ethernet/IP Driver (B0700BU-H)
♦ Allen Bradley Integrator 30 to FDSI Migration (DI700BS-A)
28
5. V9.3 System Setup B0700SV – Rev F
with Media Kits (Continued)

Q0301FZ-E AIM*AT I/A Series Information Suite - Includes:
♦ AIM*AT V3.4.3 CD ROM (K0174KF-C)
♦ I/A Series Report Package for Windows 7/Server 2008 R2 V5.2
CDROM (K0174KX-A)
K0201BJ-G Field Device Systems Integrator Triconex™ TSAA Driver V2.5 - Includes:
♦ Field Device Systems Integrator Triconex TSAA Driver and TSAA
Workstation Driver CD-ROM (K0174DT-H)
K0201FV-A System McAfee® Products Media Kit: ePolicy Orchestrator 4.6, Host Intru-
sion Prevention 8.0 P1, Device Control 9.2, Integrity Control 6.0 and
Installation and Configuration Guide for Control Core Services Systems
with install media and documentation
- Includes:
♦ Installation CD-ROM (K0174JZ)
♦ Optional McAfee® Security Products License Keys (J0201FL)
♦ Optional McAfee(R) Security Products Installation and Configuration
Guide for DVD K0174LX (B0700EZ-C)
As well, some software packages compatible with Control Core Services v9.3 are only available
from the Global Customer Support website: https://pasupport.schneider-electric.com
These include the following:
♦ Transient Data Recording and Analysis v1.6 - also download the following books with
this package:
♦ Transient Data Recorder and Analyzer (TDR/TDA) User's Guide (B0700AL-K)
♦ Transient Data Recorder and Analyzer (TDR/TDA) v1.6 Release Notes
(B0700RL-E)
Some Quick Fixes are not shipped with their associated products, and are only available from the
Global Customer Support website. These include the following:
♦ QF1257756 for Foxboro Evo Control Software v6.0 or later - this is an update to
Control Software 6.0, 6.0.1, 6.0.2, or 6.0.3
♦ QF1287671 - the following applies to your Control Core Services v9.3 system only if
an FDC280 is being deployed in the system. To support detail displays updated for
Control Core Services v9.3 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.
♦ QF1302638 for Device Monitor - it is inadvisable to install this on workstations/serv-
ers with Control Core Services v9.3. This provides the same Device Monitor
functionality present in Control Core Services v9.3 for workstations/servers with
I/A Series software v8.8 and Control Core Services v9.0-v9.2.
29
Also install QF1302638 on each Control Core Services workstation/server to update the Device
Monitor application. This Quick Fix is available from the GCS website, at https://pasupport.sch-
neider-electric.com.
30
6. V9.3 Installation Overview
This chapter contains an introduction to the Control Core Services v9.3 release and an
overview of Control Core Services v9.3 installation.
Control Core Services v9.3 Software Installation Guide (B0700SW) provides detailed instructions to
support installing Control Core Services v9.3 and preparing for process operation.
6.1 Pre-Installation and Migration Procedures

Control Core Services v9.3 is installed as either a Day 0 installation, which does not need any pre-
existing versions of I/A Series software to run, or as a Day 1 upgrade of an existing I/A Series soft-
ware v8.8 installation or Control Core Services v9.0-v9.3. It also supports a Release Update.
These terms are defined below:
♦ Day 0 installation - The base level software is loaded for release and the station is com-
mitted to set up its identity, configuration and system configuration information.
♦ Release Update - Only software which has changed between this release and the cur-
rent release on the station is loaded.
♦ Day 1 installation - Software included in the Release Update plus any changes to sys-
tem and or station configuration are committed as well.
Refer to “Software Installation Overview” and “Release Update of I/A Series Software v8.8 or
Control Core Services v9.0-9.1 to Control Core Services v9.3 Including Optional Day 1/Selected
Package Installation” in Control Core Services v9.3 Software Installation Guide (B0700SW) for the
list of pre-installation and migration procedures.
6.1.1 Backing Up the CSA Database

Back up the CSA files by using the CSA_Save utility as described in “Backing Up and Restoring
Compound Summary Access (CSA)” on page 154.
6.2 Workstation and Server Software Installation

The Control Core Services v9.3 is provided for Windows workstations and servers, and needs
either a Day 0 installation or Day 1 upgrade.
A Day 0 installation needs:
1. Restoration of the Control Core Services v9.3 compatible operating system image on
all new and existing Windows workstations and servers.
2. Installation of Control Core Services v9.3 software.
3. Preparation for the process operation.
A Day 1 installation needs:
1. Installation of the Control Core Services v9.3 software.
2. Preparation for the process operation.
31
B0700SV – Rev F 6. V9.3 Installation Overview
During the Control Core Services Day 0 installation, you can opt to install Control Core Services
with or without security enhancements. For security enhanced Control Core Services installa-
tions, the PDC has to be installed with the Control Core Services v9.3 operating system image
and Control Core Services software before any other workstation or server is upgraded.
Control Core Services v9.3 Software Installation Guide (B0700SW) provides detailed instructions to
support you in preparing your workstations and servers for upgrade, installing v9.3 operating sys-
tem images, installing Control Core Services v9.3, and preparing for process operation. Thor-
oughly review that document prior to beginning installation of Control Core Services v9.3.
6.3 Post-Installation and Migration Procedures

6.3.1 Restoring the CSA Database
If you took a backup of CSA, restore the CSA files using the CSA_Merge utility as described in
“Restoring CSA (CSA_Merge)” on page 156.
NOTE
If you perform a Day 1 operation in order to move the Compound Summary Access
(CSA) server package from one workstation with CCS v9.3 to another workstation
with CCS v9.3 and you have performed deployments to CNI stations involving
CNI hosted alarm destinations, the following special action is needed.
Move the C:\ProgramData\Invensys\IASeries\AccessListEdi-
tor\cs_devmon_CNI.cfg file from the old CSA workstation to the new CSA work-
station prior to initiating any subsequent deployments to the CNI stations.
Furthermore, you have to copy the following CNI configuration files to the new
CSA server workstation:
C:\ProgramData\Invensys\IASeries\AccessListEditor\NamespaceMap.xml
C:\ProgramData\Invensys\IASeries\AccessListEditor\ConnectionSettings\CNI-
Config.xml
6.3.2 Configuring Display Color Settings

The workstation and server platforms supported by I/A Series software v8.5-v8.8 or Control Core
Services v9.0 and later releases have to use the “Highest (32 bit)” color quality display property
value for the displays.
For H90/M90 and H91 servers, refer to the information in the “Quick Restore” chapter of the
server’s hardware and software specific instructions document.
For H92/M92 workstations, refer to the “Installing and Updating Drivers” chapter of the work-
station’s hardware and software specific instructions document.
6.3.3 Updating FCP270s, ZCP270s, FCP280s, and ATS Images

Perform an IMAGE UPDATE for Control Processor 270s (FCP270 and ZCP270), FCP280s,
and Address Translation Stations (ATSs) hosted by stations with Control Core Services v9.3. For
control processors, refer to the appropriate user’s guide. You can perform an image upgrade to the
Control Core Services v9.3 image of the FCP280, FCP270, or ZCP270 without initializing its
database.
32
6. V9.3 Installation Overview B0700SV – Rev F
For ATSs, refer to Address Translation Station User's Guide (B0700BP) for instructions.
When the update process is finished, verify that the station is at the correct image level. Refer to
Appendix B “EEPROM Revision Levels”, for the latest EEPROM and image revision levels for
Control Core Services v9.3.
For legacy control processors, refer to Appendix B “EEPROM Revision Levels” for the latest
image version numbers for these modules supported by Control Core Services v9.3.
6.3.4 Performing EEPROM Updates

Perform an EEPROM update of the FCMs and FBMs that are not at the revision level specified
for v9.3 software. Refer to Appendix B “EEPROM Revision Levels”, for details.
6.3.5 Backing Up Hard Disks

Symantec Backup Exec System Recovery software is included with Control Core Services. It is
recommended that you use the Symantec software package for your system backup and recovery
needs.
Refer to either of the following documents for instructions, depending on the version of
Symantec software installed:
♦ Symantec System Recovery 2013 Desktop, Server and Virtual Editions Guide for I/A eries
Systems (B0700EY)
♦ Symantec System Recovery 2011 Workstation Edition and Server Edition Guide for
I/A Series Workstations (B0700ES)
♦ Symantec Backup Exec System Recovery (2010 Workstation Edition and Server Edition
Guide for I/A Series Workstations) (B0700ED)
♦ Symantec Backup Exec System Recovery (Version 8.5 Workstation Edition and Server Edi-
tion Guide for I/A Series Workstations) (B0700EA)
6.3.6 Reconciling the Configuration

The last phase of the software installation process is the reconciliation phase. Reconciliation is
needed after every committed install (Day 0 or Day 1). The reconcile process is used to update the
software install status of each Control Core Services package on each Foxboro station in the sys-
tem configuration for the Foxboro Evo system. The reconcile media is created on the Foxboro Evo
system after installation and then imported into System Definition.
More information on the reconcile process can be found in the following locations:
♦ Refer to “Day 1 Operations (Standard or Security Enhanced Foxboro Evo Control
Core Services)” in Control Core Services v9.3 Software Installation Guide (B0700SW).
♦ Refer to “Reconciling the System Configuration” in System Definition: A Step-by-Step
Procedure (B0193WQ, Rev. N or later) for a complete description of reconciliation.
33
B0700SV – Rev F 6. V9.3 Installation Overview
34
7. V9.3 Operational
Recommendations
This chapter provides recommendations that you may want to consider relating to Control Core
Services v9.3.
7.1 Day 1 Installation of Control Core Services v9.3

When performing a Day 1 installation for Control Core Services v9.3, it is possible to get the sys-
tem into an incorrect state if a Day 1 update is started, committed configuration install files are
loaded, but then the installation is either canceled or you choose to back up and perform a Release
Update instead. This can affect various subsystems including the Access List Editor and The Mesh
Configurator. You will not have access to the correct set of committed configuration install files.
To correct the situation, perform another Day 1 installation on the affected system, completing
the installation until it has finished normally. Procedures are provided in the Control Core Services
v9.3 Software Installation Guide (B0700SW).
7.2 Installation of Foxboro Evo Control Software 6.0.x

or v6.1-v6.2 on Control Core Services v9.3
Before Foxboro Evo Control Software 6.0.x or v6.1-v6.2 can be installed on a station with Con-
trol Core Services v9.3 installed, you have to modify the SYSLVL file manually. Proceed as fol-
lows:
1. Backup your existing SYSLVL file.
2. On the station with Control Core Services v9.3 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.
35
B0700SV – Rev F 7. V9.3 Operational Recommendations
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.
Figure 7-2. SYSLVL File Contents - Default
6. Modify the entry “9.3.34” to “9.2” and save the file, as shown in Figure 7-3.
36
7. V9.3 Operational Recommendations B0700SV – Rev F
Figure 7-3. SYSLVL File Contents - Modified
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.34”
and save the file.
9. Install Foxboro Evo Control Software 6.0.x, or v6.1-v6.2 as described in the versions
of Foxboro Evo Control Software Installation Guide (B0750RA) and Foxboro Evo Con-
trol Software Deployment Guide (B0750BA) included with the software.
7.3 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 2008 R2, DL380 Gen9 server and later
♦ For Windows 7, Z440 workstation and later
Refer to the Hardware and Software Specific Instructions document included with your worksta-
tion or server for details about the multiple CPU core feature as used with your specific station.
7.3.1 Disabling the Microsoft Exchange Scan Add-In in

McAfee® VirusScan Enterprise (VSE)
When installing Control Core Services v9.1 or later on a workstation or server on which the mul-
tiple CPU core feature will be enabled, be aware that one additional procedure has to be per-
37
formed after the procedures listed in the “Multiple CPU Core Feature” chapter in the Hardware
and Software Specific Instructions included with your multicore-capable workstation or server.
After completing the “Installing McAfee Patch 4” procedure, you have to remove the McAfee®
VirusScan Enterprise (VSE) On Delivery Email Scanner components from the local VSE console.
Proceed as follows:
1. From the system toolbar, right-click the McAfee icon.
Figure 7-4. McAfee VirusScan Enterprise (VSE) System Icon
2. From the popup menu that appears, select Virus Scan Console…
Figure 7-5. McAfee VirusScan Enterprise (VSE) - Selecting VirusScan Console
3. In the Virus Scan Console window, right-click On-Delivery Email Scanner and
select Disable. When the On-Delivery Email Scanner’s status becomes Disabled,
exit the VirusScan Console by selecting Task -> Exit.
Figure 7-6. McAfee VirusScan Console - On-Delivery Email Scanner Disabled
Setup for a workstation or server with the multiple CPU core feature enabled is finished.
38
7.4 Control Core Services Security Enhancements

7.4.1 Using the Autologon Feature
The I/A Series software v8.5-v8.8 and Control Core Services v9.0 or later allows the use of
autologon as in previous versions of I/A Series software. It can be used for installations with and
without the security enhancements installed.
For installations with the security enhancements installed, refer to “Foxboro Evo Control Core
Services Startup Options” on page 96.
The autologon feature has not changed for workstations that do not have the security enhance-
ments installed.
7.4.2 Security Enhanced Foxboro Evo System Setup

As part of a security enhanced Control Core Services setup, each Control Core Services user
account has to belong to a pre-defined Active Directory organizational unit (OU). Refer to the
section titled “Creating Domain User Accounts” in Security Enhancements User's Guide for I/A
Series Workstations with Windows 7 or Windows Server 2008 Operating Systems (B0700ET) for
instructions on setting up user accounts on a security enhanced system.
7.4.3 Removal of the McAfee HIP Software

If you remove the McAfee HIP software from a station and then plan to re-install it, create the fol-
lowing registry key and DWORD value before re-installing the software:
♦ Key: \HKEY_LOCAL_MACHINE\Software\McAfee\HIP
♦ Add DWORD:FirewallPort and assign a decimal value of 10111
If this is not done, the HIP product interferes with the operation of File Replication
Services (FRS).
7.4.4 Non-Expiring Password for ePO Console Logins

The instructions in the Optional McAfee® Security Products Installation and Configuration Guide
for DVD K0174LX (B0700EZ) or Optional McAfee Security Products Installation and Configura-
tion Guide (B0700EX) documents instruct you to use a user account that does not have an expir-
ing password. If this requirement is not adhered to, and the password expires, you cannot log in to
the ePO console with a different password.
If you do use an account that has an expiring password, you can do the following to work around
this.
Log on to the ePO server using the an account having Domain Administrator privileges (such as,
IADomainAdmin). Once logged on, from Start > Administrative Tools, select Active
Directory Users and Computers. Select the account you are using for logging on to the ePO
console. Change the account so that its password does not expire. Log off the ePO server and log
back on using the modified ePO account.
39
7.4.5 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 7) and domain controller servers (running Windows
Server 2008 R2 Standard). If you need remote access to these stations and are willing to accept
any resulting security concern, you would need to turn on these services.
Be aware if you add the Remote Desktop Services role to a server post-installation, the addition of
that role results in a registry entry being made:
Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal
Server\TSAppSrv\TSMSI
Value: Enable (DWORD=1)
This registry entry is related to a feature of Remote Desktop Services on the Windows Server
2008 R2 Standard 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
the standard 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.
2. Start the Control Panel from the Start menu, click Administrative Tools, then
Services.
3. On stations with Windows Server 2008 R2 Standard, 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 7, 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.
40
7.4.6 Station Assessment Tool

The Station Assessment Tool reports differences between individual workstations or servers that
have differing Styles and Revisions associated with H92/M92/P92, H91/P91, or H90/M90/P90
designations. This is a normal situation due to inherent differences among the Dell, Magelis, and
HP hardware. The Station Assessment Tool is designed to indicate differences on the same work-
station or server over time so that you can track incremental changes that have occurred to the
workstations or servers.
For more information on the Station Assessment Tool, refer to Station Assessment Tool (SAT) User's
Guide (B0700DZ).
7.4.7 Time Zone and Foxboro Station Assessment Tool

If the time zone on a workstation is changed while the Station Assessment Tool (SAT) GUI is
open, the time zone reported in the SAT assessments and audits will not reflect that change even
though the system time reported will reflect the change in time zone. After changing the time
zone, the SAT GUI has to be closed and then reopened before performing any assessments or
audits in order to produce accurate assessment and audit reports.
7.4.8 Firewall Functionality

If you need firewall functionality, it is recommended that you install security enhanced Control
Core Services and use the firewall supplied with the McAfee Host Intrusion Prevention (HIP)
software.
The HIP software can be installed from the Schneider Electric McAfee Products Installation
DVD. When installed, the firewall is enabled by default with pre-configured settings, which can
be customized by a knowledgeable user. Refer to Optional McAfee® Security Products Installation
and Configuration Guide for DVD K0174LX (B0700EZ) or Optional McAfee Security Products
Installation and Configuration Guide (B0700EX) for details.
If you are not going to install the security enhanced Control Core Services, you may use the
Microsoft Windows firewall on network ports (NICs) that are NOT connected to The Mesh (as
the Foxboro Evo Control Network was previously known as), as in I/A Series software releases
prior to v8.5. Be certain that the Windows firewall is not enabled for the REDL Virtual Miniport
driver and the NICs connected to The Mesh.
7.4.9 Guidelines for Using BESR for Backing Up and Restoring

Domain Controllers
The Symantec Backup Exec System Recovery (BESR) product is used to backup and restore
workstations and servers. However, be aware that for domain controllers, restoring an old image
that has Active Directory installed on it is a last resort approach when you have more than one
domain controller. If you have a working domain controller and you need to restore another
domain controller, it is best to reinstall the second domain controller and let replication occur
with the good domain controller rather than restore the second domain controller from a backup
image.
In the case of servers that have Active Directory installed on them, i.e., domain controllers, follow
these guidelines if you are forced to restore them from BESR backups.
41
7.4.9.1 Making Backup Images of Domain Controllers

1. After installing a domain controller, change the tombstone lifetime value to suit your
backup practices. The default is 60 days. If you ever plan to restore an image older
than 60 days, change this value accordingly. The procedure for doing this is described
in Control Core Services v9.3 Software Installation Guide (B0700SW).
2. Wait to make the initial backup of domain controllers until they have been running
for 12 hours.
3. If you have secondary domain controllers, make certain the PDC and SDC are work-
ing together properly. For more information, refer to “Checking the Health of Active
Directory” on page 43.
4. Make entire backups of both the PDC and the SDC about the same time (separated
by minutes, not hours).
5. Backup the active drives (for example, C: and D:) at the same time.
6. Make certain that you select the Verify Recovery Point option in the BESR win-
dow when creating the backup image.
7.4.9.2 Restoring Only One Domain Controller

This procedure applies when there is only one domain controller being restored (for example, in
the case of a hardware unavailability), whether it is the only domain controller or there are multi-
ple domain controllers present:
1. It is recommended that the domain controller backup image not be older than 84
days (2 times the maximum machine account password age).
2. Shut down the domain controller and restore its BESR image.
3. After the domain controller is rebooted, verify it is working properly. For more infor-
mation, refer to “Checking the Health of Active Directory” on page 43.
7.4.9.3 Restoring Multiple Domain Controllers from Backup Images

If it is necessary to restore multiple domain controllers from backup images at the same time, such
as, in a testing environment, follow this procedure:
1. It is recommended that the domain controller backup images not be older than 84
days (2 times the maximum machine account password age). Optimally, the backup
images were created about the same time.
2. Shut down the domain controllers.
3. Boot up only the PDC and restore its BESR image. It is not necessary to disconnect
the PDC from the network.
4. Seize the Flexible Single Master Operation (FSMO) roles. The procedure for doing
this is described in the appendix Seize the Flexible Single Master Operation (FSMO)
roles. The procedure for doing this is described in the appendix “Secondary Domain
Controllers in a Foxboro Evo System” in Control Core Services v9.3 Software Installa-
tion Guide (B0700SW), in the context of moving these roles to another domain con-
troller, when the PDC is no longer available. In the context here, it is performed on a
PDC that is being restored from a BESR image.
42
5. Set the PDC as authoritative for SYSVOL. Refer to the “Authoritative FRS
restore” procedure described in the following Microsoft article:
http://support.microsoft.com/kb/290762.
6. Boot up the next domain controllers (SDC) and restore its BESR image.
7. After the domain controller is rebooted, verify it is working properly. For more infor-
mation, refer to “Checking the Health of Active Directory” on page 43.
8. Repeat steps 6 and 7 for each additional domain controller.
7.4.9.4 Checking the Health of Active Directory

The following are a few checks that can be used to assess the health of Active Directory.
1. Perform one of the following steps, depending on whether there is only one or multi-
ple domain controllers:
a. If there is only one domain controller, open a command prompt window and type
dcdiag to check for detected errors.
b. If there are multiple domain controllers, verify that replication is working. Open a
command prompts window, type repadmin /showreps, and verify that all the
operations succeeded.
2. Launch the Event Viewer (Start > Administrative Tools > Event Viewer).
a. Look in the Application log and verify there are no detected “userenv” errors.
b. Look in the File Replication Service log and verify that an Event “13516” message
is at the top of the log.
7.4.10 Removing and Adding Stations from/to a Domain

Occasionally, you may need to remove workstations or servers from the domain and then add
them back to the domain. For example, when a Windows station that was previously a member of
a domain is restored from a BESR backup, or if you need to rebuild a PDC from scratch, you may
need to remove the station from the domain and then add it back to the domain.
To remove a workstation from the domain and then re-attach it to the domain, perform the fol-
lowing steps:
NOTE
You have to be logged into an account that has Administrative privileges, for exam-
ple, the IAInstaller account, to perform this procedure.
1. On your desktop, right-click My Computer, click Advanced System Settings, and

select Properties. The System Properties dialog box appears.
43
2. On the System Properties dialog box, select the Computer Name tab and click
Change.
Figure 7-7. System Properties Window (Remove Workstation)
3. The Computer Name Changes window appears. Select the Workgroup radio button
and type in a name for the workgroup (for example, WORKGROUP). Click OK.
44
Type actual
Workgroup name
here.
Figure 7-8. Computer Name Changes Window (Remove Workstation)
4. Type in the user name and password of an account with permissions to remove work-
stations from the domain (for example, IADomainAdmin). Click OK.
5. Click OK when the following dialog box appears.
Figure 7-9. Computer Name Change - Remember Local Admin Password
6. Type in the user name and password of an account with permissions to add worksta-
tions to the domain (for example, IADomainAdmin). Click OK.
45
Figure 7-10. Log in IADomainAdmin
7. Click OK on the next dialog box.
Figure 7-11. Computer Name Changes - Welcome to Workgroup Dialog Box
The computer has now been removed from the domain.

Figure 7-12. Computer Name Changes - Restart Computer
46
(Clicking OK on this dialog box does not restart your computer automatically.)
9. After the workstation restarts, log on with the local administrator account credentials.
10. Right-click My Computer in Windows Explorer and select Properties. On the
System Properties dialog box, click Change.
Figure 7-13. System Properties Window (Rejoin Workstation)
11. The Computer Name Change window appears. Select the Domain radio button and
type in the name for the domain (for example, iaseries.local). Click Ok.
47
Figure 7-14. Computer Name Changes (Rejoin Workstation)
12. Type in the user name and password of an account with permissions to add worksta-
tions to or remove stations from the domain (for example, IADomainAdmin). Click
OK.
Figure 7-15. User Name and Password (Rejoin Workstation)
48
Figure 7-16. Computer Name Changes - Welcome to Domain Dialog Box
The computer has now been added to the domain.

Figure 7-17. Computer Name Changes - Restart Computer
(Clicking OK on this dialog box does not restart your computer automatically)
15. Click OK on the Computer Name Changes dialog box.
16. Click OK on the System Properties dialog box.
17. The System Settings Change dialog box appears prompting for a system reboot.
Figure 7-18. System Settings Change Dialog Box
Click Restart Later, as the startup account has to be selected before restarting the
computer.
49
18. At the restart, the system initiates the logon using the I/A Series Startup Account.
After the proper startup actions have been taken, the logon screen is presented. At this
time, any valid domain logon account may be used to log on to the workstation.
7.5 System Configuration

Windows 7 and Windows Server 2008 R2 Standard are new station types introduced in I/A Series
software v8.8. Monitor these stations with the System monitors running on I/A Series software
v8.8 or Control Core Services v9.0 or later systems. Host the network printer and USB printers
with workstations running on an I/A Series software v8.8 or Control Core Services v9.0 or later
system.
7.5.1 Blue Screen Resulting from COMM10 Ports Configured

with Printers
The Communication Processor 10 (COMM10) hosted by a workstation on the Foxboro Evo
Control Network can only be used as a FoxWatch® terminal on nodebus on which it resides.
Configure port 4 of the COMM10 as a VT100 terminal (TERM).
! CAUTION
DO NOT configure printers on COMM10 ports 1 through 3.
If you are rehosting a COMM10 from a Nodebus host, you must perform the following steps:
1. Remove every printer configured on COMM10 ports.
2. Configure the fourth COMM10 port as a VT100 terminal.
3. Add any printers you just removed to another Nodebus-hosted COMM10, or a
Nodebus workstation.
4. Day 1 Commit the system to update printer and Device Monitor configurations.
5. Make any adjustments to Group-Devices of databases targeting printers that are
unavailable or renamed.
Not removing the printers configured on the ports of COMM10 stations may result in blue
screens of workstations on the control network. For the workstation recovery, you need to do the
following:
♦ Remove the printers configured on the COMM10 ports using SysDef software (essen-
tially steps 1 through 5 above).
♦ Perform a Day 0 software installation on workstations on the control network with
the corrected Commit installation media.
7.6 User Accounts for Standard Installations

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, Fox.
50
7.6.1 ia User Account

For servers on which the Control Core Services are installed without security enhancements (that
is, a standard installation), a special “ia” user account is provided on server platforms for remotely
viewing process control displays. The default password for this account is remote. This account
does not provide access to the standard Windows Server 2008 R2 Standard desktop features; for
example, the Task Bar or Start menu. After logging on while using this account, the system’s
default behavior is to open a view-only instance of FoxView. When the user exits FoxView, the
user is logged off and remote connection is terminated automatically.
NOTE
As mentioned above, the system’s default behavior is to open a view-only instance of
FoxView. On stations with Windows Server 2008 R2 Standard, it is possible to
override the this behavior if the remote user switches to a FoxView environment;
this will remove the protections that enforce the “view-only” behavior. (This
assumes that the remote user knows the password to this environment).
7.6.2 Configuring a Remote User Account

It is possible to create additional remote user accounts. The following procedure describes how to
create a user account similar to the ia account on a station with standard Control Core Services:
1. Invoke Computer Management. Click the Start button, then click Control Panel
> Administrative Tools. Double-click Computer Management.
2. Select and expand Local Users and Groups in the left-hand pane.
3. Click Users.
4. Create a new account. From the Action menu, select New User.
51
Figure 7-19. New User Dialog Box
5. Fill in the Properties dialog box. Set the password settings to match your organiza-
tion’s requirements.
6. Click Create. (When editing an existing account, the Create button is replaced by
the OK button).
7. Right-click on the account in the right pane. Click Properties.
8. Click the Member Of tab. Using the Add button, add the groups as shown in
Figure 7-20.
52
Figure 7-20. ia Properties, Member Of Tab
The Exceed Users group is needed if this remote user needs to run applications that
need Exceed. For example, Integrated Control Configurator, SMDH, or Operator
Action Journal.
9. Click Apply.
10. Click the Environment tab on the ia Properties dialog box, and fill it as shown in
Figure 7-21.
53
Figure 7-21. ia Properties, Environment Tab
Enter this text in the Program file name field is as follows:

D:\usr\fox\system32\startp /b D:\usr\fox\customer\con-
fig\ia_logon.cmd
However, you can clone this command file and modify it to provide the behavior you
need. In that case, specify your custom command file instead.
11. Click Apply.
12. Click the Sessions tab on the Properties dialog box and fill it as shown in
Figure 7-22.
54
Figure 7-22. ia Properties, Sessions Tab
13. Click Apply.

14. Click OK.
15. Close the Computer Management window.
At this point, the Model H91/P91 and H90/P90 station is ready for connections from remote
users over LAN. (However, you also need to configure the additional instances of FoxView soft-
ware or Alarm Manager before they can actually log in remotely).
NOTE
The behavior of remote instances of FoxView and Alarm Manager is influenced by
the settings in the \usr\fox\wp\data\fv_cmds file. If you change those settings,
you need to reboot the server for those changes to take effect.
55
7.7 Software Installation

7.7.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 warnings in the
log. Make certain that you address every detected error and warning appropriately before continu-
ing 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 warnings, contact the Global Customer Support (GCS) for assistance. Refer
to the contact information on page xiii.
7.7.2 Migration from I/A Series Software v8.5 to Foxboro Evo

Control Core Services v9.0
When performing a system migration from I/A Series software v8.5 directly to Foxboro Evo Con-
trol Core Services v9.0 or later, you have to install QF1023535 on the PDC with I/A Series soft-
ware v8.5 and every AW in its domain before performing the system migration process to Control
Core Services v9.0 or later. Quick Fixes are available through our Global Customer Support at
https://pasupport.schneider-electric.com.
You can install the Quick Fix on AWs with I/A Series software v8.5 after the PDC's migration to
Control Core Services v9.0 or later if needed, as there is nothing that disallows the Quick Fix
from being installed at I/A Series software v8.5.
If you have already upgraded the system with I/A Series software v8.5 to I/A Series software v8.6
or v8.7 prior to migration to Control Core Services v9.0 or later, installing QF1023535 is not
necessary as it is already included and installed on systems with I/A Series software v8.6 and v8.7.
7.7.3 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.
56
♦ Installing Control Core Services Day 1 installation media.

The full procedure is provided in Control Core Services v9.3 Software Installation Guide
(B0700SW).
7.7.4 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.
7.8 Windows Workstations

7.8.1 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 eight 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 as well.
7.8.2 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-
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
Do not attempt to upgrade driver versions after installation of Control Core Ser-
vices as this may result in detected errors.
7.8.3 Viewing the Exceed Log File from the Desktop Taskbar
On Windows 7 and Windows Server 2008 stations running the Control Core Services, viewing
the Exceed log file needs an extra step compared to Windows XP and Windows Server 2003. Pro-
ceed as follows:
57
1. Hover the cursor over the Exceed icon in the taskbar.

2. Right-click on the Exceed box that pops up just above the icon. This displays the
menu that was previously displayed directly by right-clicking on the Exceed icon in
the taskbar on Windows XP and Windows Server 2003.
3. Click Tools to provide an option to view the log file.
7.8.4 IP Netmask Settings of Windows Workstations on the

Nodebus
Nodebus workstations have their IP netmask set to 255.255.254.0 for Windows NT workstations
and 255.255.224.0 for Windows XP workstations. The IP netmasks of these workstations need to
be changed to 255.255.0.0 for IP forwarding through the ATS to work.
Without changing the netmask, a Windows workstation will behave as if workstations on the
control network are on a different subnet, and will not be able to reach them via IP. This affects IP
communication, For example, pings, ftp, rlogin, rsh, and telnet. Solaris workstations have the cor-
rect netmask.
Changing the Netmask on a Nodebus Windows NT Workstation

Perform the following steps to change the netmask on a Nodebus workstation running the
Windows NT operating system:
1. From the Start menu, select Settings > Control Panel.
2. Open the Network control panel.
3. Select the Protocols tab.
4. With TCP/IP Protocol selected, click Properties.
5. From the Adapter pulldown, select the Foxboro network card.
(If you are not certain which card is correct, try them one by one until you find one
with an IP address of the form 151.128.xxx.xxx).
6. Change the Subnet Mask from 255.255.254.0 to 255.255.0.0.
7. Click OK to exit the Microsoft TCP/IP Properties dialog box.
8. Click Close to exit the Network control panel.
9. When asked if you want to restart your computer now, click No.
10. Reboot the station. Refer to “Shutting Down/Restarting the Station” on page 108.
Changing the Netmask on a Nodebus Windows XP Workstation

Perform the following steps to change the netmask on a Nodebus workstation running the
Windows XP operating system:
1. From the Start menu, select Settings > Control Panel.
2. Open the Network Connections control panel.
3. Right-click the I/A Series Local Area Connection and select Properties.
(If you are not certain which connection is correct, try them one by one until you find
one with the Foxboro Protocol checked).
4. Double-click Internet Protocol (TCP/IP) from the list of items.
5. Change the Subnet mask from 255.255.224.0 to 255.255.0.0.
58
6. Click OK to exit the Internet Protocol (TCP/IP) Properties dialog box.

7. Click OK to exit the Local Area Connection Properties dialog box.
8. Exit the Network Connections control panel.
7.8.5 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.
7.8.6 Screen Savers

s a general rule, it is not advisable to run screen savers on your Foxboro stations. However, in the
security enhanced 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 Enhancements User's Guide for I/A Series Workstations with Windows 7 or
Windows Server 2008 Operating Systems (B0700ET) document has information related to these
policy settings (search for “screen saver” in that document).
7.8.7 Security Feature in Windows 7 and Windows Server 2008

R2 Standard
Due to the security feature in Windows 7 and Windows Server 2008 R2 Standard, files created by
one user may not be accessible by another user in normal (un-elevated) operations. For example,
workfiles created by a SaveAll script (which runs every night and is scheduled via the AT com-
mand) 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 the un-elevated (non-administrative)
“Fox” 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 “Fox” 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.
59
7.9 Solaris 10 Stations

7.9.1 GNOME Session Manager Segmentation Fault
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.
7.10 System Monitor

7.10.1 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.
7.10.2 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.
7.11 Object Manager Software

7.11.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.
7.12 Displays
7.12.1 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
60
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.
7.13 Application Software

7.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 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 Con-
trol Core Services v9.0 and later (which was the “Plant Maintenance” group for I/A Series soft-
ware 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.
7.14 Alarm Management Subsystem

7.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.
7.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-
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
61
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.
7.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.
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).
62
7.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.
7.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.
7.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 Windows XP workstation running Message Manager software, a message
may appear stating that the Alarm Manager is unable to obtain new alarms because the Alarm
Server Task is unavailable, although the alarms do appear on the CAD.
7.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.
7.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:
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.
63
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.
7.15 Historian Software

This section presents observations and recommendations for Historian software users, and
describes the subtleties of AIM*Historian software and Historian software relative to the use of
the ATS module.
Refer to AIM*AT Suite AIM*Historian User's Guide (B0193YL) for details about this software.
7.15.1 Assumptions
It is assumed that timekeeping (system time domain) located on the control network side of the
Foxboro Evo node is in UTC, and the timekeeping on the Nodebus is in IATIME.
7.15.2 Historian Installation

AIM*Historian v3.4.1 is designed for installation on Control Core Services v9.0 or later. The pre-
vious version of AIM*Historian (v3.4) can be upgraded to v3.4.1 if it was installed on I/A Series
software v8.8 prior to upgrading to Control Core Services v9.0 or later. AIM*Historian v3.4 can-
not be installed directly on a station with Control Core Services v9.0 or later. If this has been
done, AIM*Historian v3.4 has to be uninstalled prior to installing v3.4.3.
7.15.3 Historian Configuration

There are three historian configuration attributes that are vital for proper collection and retrieval
of timestamps: IATIME (Control Core Services time), TZ (time zone), and DST (daylight savings
time).
IATIME IATIME is a historian instance attribute. It determines the format in
which the timestamps are stored in the historian. Setting IATIME to yes
(or 1) causes the timestamp to be stored in IATIME in the historian. Set-
ting IATIME to no (or 0) causes the timestamp to be stored in UTC for-
mat in the historian.
It is recommended that you configure this parameter to match the system
time domain on the station on which the historian resides.
♦ For AIM*Historian software on the I/A Series software v6.x/v7.x
side, configure this attribute as IATIME=yes.
♦ For AIM*Historian software on the control network, or for off-
platform historians, configure IATIME=no.
TZ and DST TZ and DST are collector attributes. They determine the amount of
adjustments made to the timestamps by the collectors and by the data
retrieval software when necessary. These attributes are configured the same
on Nodebus and the control network Historians.
♦ Configure TZ to the time zone where the Historian is actually
located. For example, in the Eastern U.S., configure TZ=
64
GMT_MINUS_5; in most of Western Europe, configure TZ=

GMT_PLUS_1.
(Be advised that on stations on the control network, match the TZ
attribute with the system time setting. On Nodebus stations, how-
ever, the system time zone is set to GMT and the TZ attribute will
not typically match that setting).
♦ Configure DST to the actual status of the Daylight Savings Time;
in the summer months, configure DST=yes; in the winter months,
set DST=no.
It is recommended that you configure the TZ and DST attributes the
same for the collector stations of each instance, including the shadow sta-
tions REALTIME_SERVER and MESSAGE_SERVER.
Historian Time Configuration Notes

♦ The TZ and DST attributes are only used by the Historian collector and only when a
time conversion is necessary for the timestamps. A time conversion is necessary when
the timekeeping format on the local station is different from the timekeeping format
configured in the Historian instance by the parameter IATIME. For example, if the
station is keeping time in IATIME, but the IATIME parameter in the Historian
instance is set to ‘no’ (or 0), then the collector has to convert the station time from
IATIME to UTC time. In order to make the proper conversion, the TZ and DST
time offsets have to be included in the calculation. This time conversion for the time-
stamps is done automatically by the Historian when data values are being written to
the Historian and also when values are being read from the Historian for a FoxView
trend, for example.
♦ It is needed that you configure the TZ and DST offsets in the collector because the
TZ and DST offset values are both set to zero on the standard Control Core Services
stations.
♦ No time conversion is necessary if the IATIME parameter matches the timekeeping
type of the local station.
Refer to AIM*Historian User’s Guide (B0193YL) for additional information on configuring the
TZ and DST attributes.
7.15.4 Historian Naming

While there is a statement in the AIM* documentation that it is permissible to have two
AIM*Historian instances with the same name on the same node. This is not recommended for a
production system, in particular, for a production system with a mixture of legacy and AIM*His-
torian instances.
It is not recommended to have two AIM*Historians with the same name on the same Foxboro
Evo system.
Two Historians with the same name cannot coexist on the same station. Two Historians with the
same name can coexist on two different stations on the same node and collect data without con-
cerns, but only one set of trend servers can be active at any particular point of time. Switching
from one set of trend servers to the other needs an operator intervention consisting of multiple
steps to be executed on both Historian host stations. In addition, it is not trivial for the operator
to find out which set of trend servers is currently active, so it would be difficult for him to know
65
from where the trend data is coming. For these reasons, it is strongly discouraged to have multiple
Historian instances with the same name.
7.15.5 Changing Points on a FoxView Trend Display to a New

Historian Name
Refer to FoxView Software (B0700FC) to find out what you need to do if the source of trend dis-
play data have to be changed from one Historian to another.
7.16 Control Configuration Software

7.16.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 compound.
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.
7.16.2 ECB Period for HART FBMs

Be aware that the fastest allowed ECB period for the HART FBMs is 100 milliseconds
(PERIOD = 0). However, it is recommended that you refer to the appropriate Sizing Guidelines
and Excel Workbook for your Control Processor to determine the optimal BPC for this ECB in
order to keep from overloading.
7.16.3 Station Must Not Be Shutdown or Rebooted While ICC is

Open
Do not attempt to shutdown or reboot a station while ICC is open. First, close ICC and then pro-
ceed with the shutdown or reboot operation.
7.17 Control Software

7.17.1 Updating Sequence Block Code after Migration to a New
Operating System or NutCracker Version
You may encounter suboptimal conditions if you are using sequence blocks and migrating from
workstations running the Solaris operating system to workstations running the Windows worksta-
tion or vice versa. You may also encounter similar conditions when migrating between different
versions of NutCracker software.
66
Prior to I/A Series software v8.2, preprocessor software behaved identically on both Windows and
Solaris platforms. Pre-v8.2 MKS NutCracker software was compatible with the Solaris C prepro-
cessor software.
However, I/A Series software v8.2-v8.8 and Control Core Services for the Windows operating sys-
tem was released with a newer version of MKS NutCracker. This version of MKS caused some
interoperability suboptimal conditions with Windows platforms running the older version of the
MKS NutCracker software, as well as with Solaris workstations running the native Solaris C pre-
processor software.
Table 7-1 to Table 7-3 give an overview of these conditions you may encounter when migrating
High Level Batch Language (HLBL) and Sequential Function Chart (SFC) files between plat-
forms and configurators, and general considerations for migrating sequence block code.
Table 7-1. General Migration Considerations
Foxboro Evo
Control
ICC on ICC on IACC on Editors on
Solaris Windows Windows Windows
Description Platform Platform Platform Platform
Precompiler supports reserved Yes Yes Yes Yes
words
Precompiler supports long No No No No
comments
Precompiler supports long IF No No Yes Yes
statements
Table 7-2. HLBL Migration Considerations
Foxboro Evo
Control
Precompiler is case sensitive Yes Yes No No
Precompiler replaces strings Yes No No No
included in single quotes
correctly
Precompiler correctly expands Yes No No No
#define statements
Precompiler correctly expands Yes No No No
#define statements with com-
ments
Precompiler needs that a No No Yes Yes
value is added to #define
statements
Precompiler supports “#if Yes Yes No No
defined” statements
Precompiler supports redefini- Yes Yes No No
tion of #define values
Precompiler supports condi- Yes Yes No No
tional inclusion
67
Table 7-2. HLBL Migration Considerations (Continued)
Foxboro Evo
Control
Precompiler supports a direc- Yes Yes No Yes
tory structure
Precompiler removes white No Yes Yes Yes
space
Precompiler exhibits text edi- N/A N/A Yes N/A
tor suboptimal conditions
Precompiler supports spaces N/A N/A No Yes
behind #endif macro
Precompiler support multi-line Yes Yes No No
macros separated by a backs-
lash ('\') character at the end
of the line.
Table 7-3. SFC Migration Considerations
Foxboro Evo
ICC on ICC on IACC on Control Editors
Solaris Windows Windows on Windows
Precompiler has subopti- No Yes Yes Yes
mal conditions with car-
riage return, line feed, and
tab characters
Precompiler has subopti- No No Yes Yes
mal conditions with single
quotes
For additional information on control configuration, sequence blocks, and their compilation,
refer to the following documents:
♦ High Level Batch Language (HLBL) User’s Guide (B0400DF)
♦ I/A Series Configuration Component (IACC) User's Guide (B0700FE)
♦ Sequence Block SFC Editor User's Guide (B0750AM)
♦ Sequence Block HLBL Editor User's Guide (B0750AL)
♦ Integrated Control Configurator (B0193AV)
♦ Sequential Function Chart/Structured Text Configurator and Display Manager for
Sequence Blocks (B0193UZ)
The following sections describe these concerns in more detail.
7.17.1.1 General Considerations

The following subsections describe general considerations when migrating sequence block code
between different configurators and operating systems:
68
Using Reserved Words

Before migrating from a Solaris to a Windows workstation, make certain that you have not rede-
fined any reserved words, such as AUTO, MANUAL, or FUNCTION. If you are using a case-
sensitive configurator and reserved words have been redefined, you can resolve the concern by
changing the case of the defined word (for example, auto, manual, or function). This will affect
the SENDMSG command.
For a list of reserved words, refer to the “Keywords” section in High Level Batch Language (HLBL)
User’s Guide (B0400DF).
Using Long Comments and If Statements

The compiler cannot find labels if comments are too long or if the text is too long within an IF
loop. To resolve this concern, enter a carriage return after approximately 60 characters. Addition-
ally, for a list of other sequence compiler limits, refer to “Sequence Compiler Limits” in High Level
Batch Language (HLBL) User’s Guide (B0400DF).
7.17.1.2 HLBL Code

The following subsections describe the concerns with HLBL code that may appear when migrat-
ing code between configurators and operating systems:
♦ “Case Sensitivity” on page 69.
♦ “Replacement of Strings Included in Single Quotes” on page 70.
♦ “Expansion of #define Statements” on page 71.
♦ “Value Added to #define Statements” on page 71.
♦ “Conditional Inclusion Support” on page 72.
♦ “Directory Structure” on page 73.
♦ “Text Editor Concerns” on page 76.
♦ “Space Behind #endif Macro” on page 77.
Case Sensitivity
ICC running on both Solaris and Windows platforms is case-sensitive, whereas the IACC and the
Foxboro Evo Control Editors (hereinafter referred to as Control Editors) applications (which both
run on Windows platforms) are not case-sensitive. You may have a concern when compiling code
depending on which control configuration tool you are using. For example, you may have case-
sensitivity suboptimal conditions if you are upgrading from ICC running on a Solaris platform to
the Control Editors running on a Windows platform, as shown in the following example.
The following code will not compile in the non-case-sensitive control configurators because the
uppercase BATCHTIME macro conflicts with the lower case batchtime variable:
#ifdef BATCHTIME
batchsec : RI0015; {Batch timer in seconds}
batchtime : SN0001; {Batch elapsed time string batch time changed from
batchtime to batchtime1}
lasttime : II0001; {Last time batch time was updated}
#endif
Alternatively, the following code will compile, because the batchtime variable has been changed
to batchtime1:
69
#ifdef BATCHTIME
batchtime1 : SN0001; {Batch elapsed time string batch time changed
form batchtime to batchtime1}
#endif
TIP
If you are upgrading from a non-case-sensitive configurator (ICC on Solaris or
Windows platforms) to a case-sensitive configurator (IACC or the Control Editors),
make certain your code does not contain tokens that differ only in case, such as an
uppercase macro name and a lowercase variable name.
Replacement of Strings Included in Single Quotes

For ICC running on Solaris platforms, the precompiler will replace strings included in single
quotes, as in device := 'CHARG_VLV'. However, this is not the case for ICC running on a Win-
dows platform or for IACC and the Control Editors. The precompilers for these applications will
not replace strings enclosed in single quotes. If you are upgrading from a Solaris platform to a
Windows platform, you will have a suboptimal condition if the code contains strings enclosed in
single quotes that are meant to be replaced by macros, as shown in the following example.
In the following code snippet, the precompiler will not substitute RX_101:XV101_1A wherever
CHARG_VLV appears, because the CHARG_VLV string is within single quotes. This condition occurs
for ICC running on a Windows platform, as well as IACC and the Control Editors.
#define OPEN TRUE /* existing macro */
#define CHARG_VLV RX_101:XV101_1A /* existing macro */
001 DRIVE(device := 'CHARG_VLV', option := 1, mode := OPEN);

002 :CHARG_VLV.MA := FALSE;
Alternatively, if the code was changed as follows, the precompiler will substitute
‘RX_101:XV101_1A’ wherever sCHARG_VLV appears, and RX_101:XV101_1A wherever
CHARG_VLV appears.
#define OPEN TRUE /* existing macro */
#define CHARG_VLV RX_101:XV101_1A /* existing macro */
#define sCHARG_VLV ‘RX_101:XV101_1A’ /* new macro */
001 DRIVE(device := sCHARG_VLV, option := 1, mode := OPEN);

002 :CHARG_VLV.MA := FALSE;
TIP
If you are upgrading from ICC running on the Solaris platform to ICC, IACC, or
the Control Editors running on a Windows platform, make certain that the code
does not contain strings enclosed in single quotes that are meant to be replaced by
macro text. Include the single quotes in the macro definition instead.
70
Expansion of #define Statements

Precompilers on Solaris platforms and Windows platforms expand #define macros in the code dif-
ferently. The Windows XP operating system takes everything after the macro name and blindly
substitutes it into the code, where the Solaris operating system will remove comments of the type
{} and will recognize that substitution not be made if the macro name is included in a string.
For example, consider the following code:
#define Desired ::UNIT.RI0001 {Any REAL from display}
H2O_SetPt := Desired + 5.0;
MESSAGE := “Enter Desired Water Amount to TK-301, ACK”;
The Windows XP operating system expands this code as follows:
H2O_SetPt := ::UNIT.RI0001 {Any REAL from display} + 5.0;
MESSAGE := “Enter ::UNIT.RI0001 {Any REAL from display} Water Amount
to TK-301, ACK”;
The comment included in the H2O_SetPt line is not standard coding practice, but the text will
compile and run on both Windows and Solaris platforms. However, the substitution that Win-
dows XP precompiler makes on the MESSAGE line is incorrect.
Expansion of #define Statements with Comments

If there are spaces between the #define declaration and a comment, suboptimal conditions may
occur.
For example, consider the following code:
...
#define RX_PRESS :PT101_1A /* Comment */
...
REPEAT
P1 := :RX_PRESS.PNT_1;
UNTIL FALSE;
...
The Windows XP operating system expands this code as follows:
P1 := ::PT101_1A.PNT_1;
TIP
If you are upgrading from an ICC on Solaris platforms to ICC, IACC, or the Con-
trol Editors on a Windows platform, make certain all the macros contained in
define statements are expanded properly in the Sequence code. If there are spaces
before comments, remove the spaces. For example, modify the code to read:
#define RX_PRESS :PT101_1A/* Comment */
Value Added to #define Statements

For precompilers associated with ICC on both Windows and Solaris platforms, define state-
ments do not need to have a value assigned:
# define MACRO
However, for IACC and the Control Editors, a value has to be added to the define statement in
order for the code to compile:
# define MACRO value
71
In the following example, the precompilers associated with IACC and the Control Editors do not
accept the macro without a value assigned to it, whereas the statements are valid for ICC on Win-
dows and Solaris platforms.
#include “opt_HLBL_Global_UnitExec.s”
#define BATCHTIME {no value is assigned to the macro BATCHTIME }
#include “opt_HLBL_Global_TimeCalc.s”
#ifdef BATCHTIME
batchelapsedtime : SN0001; {Batch elapsed time string}
#endif
In the following modified example, a value is assigned to the BATCHTIME macro, so the
code is accepted by the precompilers:
#include “opt_HLBL_Global_UnitExec.s”
#define BATCHTIME 1 {the value “1” is assigned to the macro BATCHTIME }
#include “opt_HLBL_Global_TimeCalc.s”
#ifdef BATCHTIME
batchelapsedtime : SN0001; {Batch elapsed time string}
#endif
TIP
If you are upgrading from a ICC on Solaris or Windows platforms to IACC or the
Control Editors on a Windows platform, make certain all the macros contained in
define statements are assigned a value.
Conditional Inclusion Support

The precompilers associated with ICC running on Solaris and Windows platforms provide condi-
tional inclusion support. However, you may need to make modifications if you are migrating
from ICC on Solaris or Windows platforms to IACC or the Control Editors on Windows plat-
forms, or vice versa.
Conditional inclusion commands like if, ifdef, or ifndef, allow parts of the source code to be
included or ignored during compilation. The condition can be tested based on the value of a con-
stant expression or on whether a macro name is defined. If the conditional inclusion command
tests for equality, the test has to contain only one equal sign (‘=’) if you are using IACC or the
Control Editors.
For example, the following code containing conditional “if ” statements does not compile on
IACC or the Control Editors:
#if NUM_OF_PUMPS == 2
VALID_SUM = 3;
VALID_PRD = 2;
#endif
72
#if NUM_OF_PUMPS == 3
VALID_SUM = 6;
VALID_PRD = 6;
#endif
In the following modified example, only one ‘=’ character is used in the equality test. This code
compiles on IACC and the Control Editors.
#if NUM_OF_PUMPS = 2
VALID_SUM = 3;
VALID_PRD = 2;
#endif
#if NUM_OF_PUMPS = 3
VALID_SUM = 6;
VALID_PRD = 6;
#endif
TIP
If you are using conditional inclusion statements and you are upgrading to IACC or
the Control Editors, make certain equality tests only use one equal sign.
Directory Structure
The ICC running on Solaris and Windows platforms and the Control Editors allow a directory
structure for individual include files, whereas IACC does not allow a directory structure.
For example, Figure 7-23 shows an example of a directory structure that could have been used
with ICC or the Control Editors, and Figure 7-24 shows the sequence code that references the
files in the directory structure. Specifically, the #include statements in Figure 7-24 are referencing
files that reside in the “D:\opt\HLBL\Global” and “D:\opt\HLBL\SBR” directories, such as
book_release.s and msg_disp.sbr.
73
Figure 7-23. Directory Structure Used with ICC or the Foxboro Evo Control Editors
Figure 7-24. Sequence Code Referencing Include Files Contained in a Directory Structure
74
However, the directory structure shown in Figure 7-23 is not supported when you are migrating
from ICC or the Control Editors to IACC. To work around this, you can use the “Text Objects”
names in IACC to mimic the original file structure.
Text objects are library objects that contain Structured Text (ST) code and can be inserted into
the sequence block code. To mimic the original file structure in IACC, perform the following
steps to create a text object and add code to it.
1. In the IACC Project Navigator, expand System > Libraries > Text Objects.
2. Right-click Text Objects and choose New Text Object from the pop-up menu.
3. A new object with a default name is added under the Text Objects branch. The
default name is highlighted, and you can change the name at this point.
4. Give the Text Object a new name using the convention <pathname>_<filename>.
For example, give the D:\opt\HLBL\SBR\msg_disp.sbr file the name
opt_HLBL_SBR_MsgDisp.sbr.
5. Add code to the Text Object:
a. Double-click the object to open the ST Code Editor.
b. Copy the text from the included file and paste it into the Text Object in IACC.
c. Update the filenames in throughout the sequence code. You could do this by per-
forming a find and replace operation to replace “/opt/HLBL/SBR/” with
“opt_HLBL_SBR_”, as shown in “Sequence Code Referencing IACC Text
Objects” on page 76 below.
d. Verify, compile, and save the code in the Text Object.
75
Figure 7-25. Sequence Code Referencing IACC Text Objects
TIP
If you are migrating to IACC, manually copy and paste the files into the IACC con-
figurator and use the “Text Objects” library name to mimic the old file structure.
Refer to “Creating and Editing Text Objects” in I/A Series Configuration Component
(IACC) User's Guide (B0700FE).
Text Editor Concerns

The Structured Text (ST) Code Editor is a text editor built into IACC for creating and editing
HLBL code for sequence blocks. The ST Code Editor in IACC does not allow you to edit the first
line in the sequence block. To work around this condition, you have to import the proper code
manually on a per-block basis, rather than compiling sequence blocks using the bulk HLBL block
compiler.
76
Figure 7-26. Sequence Code Referencing IACC Text Editor
TIP
If you are migrating to IACC, import the code manually on a per-block basis. Refer
to “Compiling the HLBL Code” in I/A Series Configuration Component (IACC) User's
Guide (B0700FE).
Space Behind #endif Macro

In IACC, spaces behind endif statements lead to detected compilation errors. This suboptimal
condition does not occur for ICC on Solaris and Windows platforms or the Control Editors.
Because there is a space after the endif statement, the code in the following example will not
compile in IACC:
IACC accepts the code in the following example:
77
TIP
If you are migrating to IACC, remove spaces after endif statements.
7.17.1.3 SFC Code

The following subsections describe the concerns with SFC code that may appear when migrating
code between configurators and operating systems:
♦ “Carriage Return, Line Feed, Tab” on page 78.
♦ “Single Quote Concerns” on page 78.
Carriage Return, Line Feed, Tab

If you attempt to migrate code from a Solaris platform (ICC) to a Windows platform (ICC,
IACC, or the Control Editors), the carriage return, line feed, and tab characters appear in the
migrated text as shown below:
Figure 7-27. Sequence Code Referencing Carriage Return, Line Feed, Tab
TIP
After migrating code from Solaris to Windows, replace the carriage return, line feed,
and tab characters that do not import correctly into SFC/ST Display Manager.
Refer to SFC V2.0 Release Notes (Windows XP and Windows Server 2003 Platforms)
(B0400QR) or SFC V 2.0 Release Notes (Solaris Platform) (B0400QS) for information
on migrating sequence blocks between Windows and Solaris platforms.
Single Quote Concerns

In IACC, the following SFC code will not compile because there is a single quote in the
comment.
(* SECURE OTHER REACTOR'S CHARGE BLOCK, BLEED, AND CONTROL VALVES *)
SECURE_CHRG_VLVS := TRUE;\
If a single quote appears in a comment, the detected error message in Figure 7-28 will appear.
78
Figure 7-28. Sequence Code Referencing Single Quote Concern
However, the following SFC code with the single quote removed will compile in IACC:
(* SECURE OTHER REACTORS CHARGE BLOCK, BLEED, AND CONTROL VALVES *)
SECURE_CHRG_VLVS := TRUE;\
Alternately, the Control Editors deal with this issue internally by removing any single quotes
embedded in comments before compilation. The source code is not changed and successfully
compiles, but the single quote characters have been removed from the compiled code.
TIP
After migrating code to IACC, make certain there are no single quotes embedded in
comments. To work around this suboptimal condition, you could either replace the
single quote with another character or remove the single quote character, for exam-
ple “can’t” would become “cant” or “cannot”.
If you are migrating code to the Control Editors, keep in mind that the compiled code
will not contain the single quote character if it was embedded in a comment.
7.17.2 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.
79
7.17.3 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.
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.
7.17.4 Migrating a Control Database to an FCP280, FCP270, or

ZCP270
You can migrate a control database from a CP60 to an FCP280, FCP270 or ZCP270 provided
that the database is configured correctly. Database validation logic in the FCP280, FCP270 or
ZCP270 has been improved since the CP60, and databases containing detected configuration
errors that are undetected by a CP60 will not load correctly into an FCP280, FCP270 or
ZCP270. Before performing the control database migration and loading the database for use with
an FCP280, FCP270 or ZCP270, you have to correct these detected configuration errors to
improve proper system performance.
80
First, check the periods and phases of the ECB200/ECB202 blocks and their associated DCI
blocks to make certain there are no phasing discrepancies. DCI block execution frequency cannot
be faster than its associated parent ECB200/ECB202 execution frequency. The period/phase of
the associated child ECB201 is irrelevant to the DCI block execution. DCI blocks have to be con-
figured to run on a multiple of both the ECB200/ECB202 phase and the phase of the compound
containing the DCI block. For example, an invalid configuration can include a DCI block config-
ured for 0.5 second execution, but the block’s parent ECB200/ECB202 is configured for 1 second
execution. This invalid detected configuration error goes undetected in the CP60, but will disal-
low the database from being loaded on an FCP280, FCP270 or ZCP270. Prior to I/A Series soft-
ware v8.0 the entire set of DCI blocks is as follows: BIN, BINR, BOUT, IIN, IOUT, PAKIN,
PAKOUT, PLSOUT, RIN, RINR, ROUT, STRIN, and STROUT.
Second, if you are migrating a control database from a Nodebus CP to an FCP280, FCP270 or
ZCP270, please note that databases containing the MVC (Multivariable Controller Block) and
MVL (Multivariable Loop Block) blocks will not load into an FCP280, FCP270 or ZCP270.
7.17.5 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.
7.17.6 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.
7.17.7 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.
81
! CAUTION
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.
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.
7.17.8 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.
7.17.9 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.
7.18 Control Processor (FCP280, FCP270 and

ZCP270)
7.18.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
82
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
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 risk that 100 Series FBMs will need to boot up by making cer-
tain that the 100 Series FBMs are mounted on a rack with a battery back-up or an Uninterrupt-
able 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.
7.18.2 Validating FCM100E and FCM100Et Settings (ZCP270

Only)
The validation for FCM100E and FCM100Et ECBs has been tightened with I/A Series software
v8.5-v8.8 or Control Core Services v9.0 and later to make certain that the correct files are down-
loaded during any FCM software updates. The software type and the hardware type in the FCM
ECB are separately validated, and each is needed to be set to 210. If either is incorrectly set during
creation of the FCM ECB, then a detected E28 - INVALID SOFTWARE/HARDWARE TYPE error
will result. This detected E28 error will also occur when loading the control database where the
incorrect values have been saved from less stringent systems.
If such a detected error occurs during a LoadAll, neither the FCM nor the FBMs below it is dis-
played in system management software. To recover, perform one of the following steps:
♦ Prior to saving the control database, correct the FCM ECB’s by setting the Hardware
Type and Software Type to 210, or
♦ After the LoadAll completes, re-enter the ECB with the corrected values in place.
With the corrected FCM ECB in place, the FBMs automatically re-attached.
7.18.3 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.
7.18.4 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.
83
♦ 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\'
7.18.5 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)
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.
84
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.
7.18.6 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).
7.19 Field Device Controller 280 (FDC280)

7.19.1 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.
85
7.20 Address Translation Station (ATS)

7.20.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.
7.20.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 Processors1 CP30, CP30 Style B, CP40, CP40 Style B, and CP60
These stations have to have the minimum firmware revisions listed in Table 7-4 in order to oper-
ate with the ATS:
Table 7-4. Minimum Versions for Nodebus Stations Running on

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

The Foxboro Evo Control Network (Continued)
Minimum Firmware
Station Type1 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)2
1.
These control processors have been withdrawn from sale. Comprehensive sup-
port services for these products are limited to the Lifecycle Support Policy.
2.
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.
7.20.3 Network Fault 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
87
nfd_debug_saved.LTRBUG.txt), overwriting any existing contents. Then the log file is emp-
tied.
Startup detected errors and warnings are logged to the Event Viewer in the Application log, source
“ATS Monitor” (for example, changing the LogDirectory to a non-existent location).
NOTE
If you used stabin_tool.exe to disable NFD mastership on an ATS (for example,
using QF1008334, QF1009129, or QF1011230), remember to restore the normal
behavior after removing the workstations with I/A Series software v7.x from the
node. This makes certain there is a still a candidate NFD Master available on the
node. To enable NFD mastership on an ATS, run ‘stabin_tool.exe -a -nonfd
0 STALTRBUG.BIN’ on the ATS boot host, then reboot both sides of the ATS
together. The station reboots twice: once as directed from 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.
7.21 Intrinsically Safe I/O Subsystem

7.21.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).
7.22 Fieldbus Modules (FBMs) and Field

Communication Modules (FCMs)
7.22.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.
7.22.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.
88
7.22.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.
7.22.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.
7.22.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.
89
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).
7.22.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.
7.22.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 7-29 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 7-29. 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 failed in SMDH,
the FCM icon will not show a warning status based on the missing partner module, and a system
alarm will not be generated based on the missing partner module.
The FCM defaults to a redundant configuration, in which Bit 2 of FCMCFG is set to 0. In the
redundant mode, a missing B FCM module is marked as failed, the FCM is shown in a warning
condition, and a system alarm is generated.
90
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 fail in a constant reboot cycle.
7.22.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.
7.22.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.
7.22.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.
7.22.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-
ber of raw counts per second, which is actually 10 times the desired value. This detected error has
91
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.
7.22.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 fail to zero in order to allow the opposite (non-failed) FBM to assume (or
continue) control without interference from the failed module.
7.22.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.
7.22.14 Field Device System Integrator (FDSI) Subsystem

7.22.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.
7.22.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.
7.22.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 detected W62 - UNRESOLVED CONNECTION error on the
Default Detail display.
92
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
detected W62 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.
7.22.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 B “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.
7.22.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.
7.22.16 FBM223 PROFIBUS Configurator

The FBM223 PROFIBUS Configurator only supports GSD Revision 3. Request a GSD file with
Revision 3 from the device vendor.
7.23 FOUNDATION fieldbus, PROFIBUS-DP, HART,

Modbus, DeviceNet, and FDSI
7.23.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.
93
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.
7.24 Tools and Utilities

7.24.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.
7.24.2 Run Utilities as Administrator

Invoke SOM, RSOM, SIPC, RSIPC and similar applications from a command prompt with
Administrator privileges.
To open a command prompt with Administrator privileges:
♦ Click Start and type cmd.exe in the Search box.
♦ Right-click cmd.exe under Programs and click Run as Administrator. The User
Account Control (UAC) prompt appears.
♦ If you are already logged on with an account with Administrator privileges, click Yes.
Otherwise,
♦ On the dialog box that appears, enter the user name and password for an account with
Administrator privileges.
♦ The command prompt opens with Administrator privileges and you can invoke the
desired utility.
NOTE
By default, the “Fox” account on standard installations and user accounts that are
member of the I/A Plant Administrators group on systems with security enhanced
Control Core Services have Administrator privileges.
7.25 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.
94
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
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.
7.26 Virus Scan Exclusions

Virus scan exclusions have been updated every iteration since I/A Series software v8.6. Once
applying the policy update to the ePO server, the updated exclusions are automatically propagated
to all secure ePO enabled AWs (v8.5 through Control Core Services v9.0 or later). If you are run-
ning a mixed system (v8.5 through Control Core Services v9.0 or later), you will need to manu-
ally update exclusion lists for standard workstations, so that the Windows workstations on the
Foxboro Evo Control Network have a consistent exclusion list.
You can download the updated virus scan exclusions from the Global Customer Support website
(https://pasupport.schneider-electric.com).
7.27 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.
95
7.28 Control Blocks and Parameters

7.28.1 Changing FSENAB for ECB200 (PROFIBUS-DP FBM223)
Changing the FSENAB (fail-safe enable) parameter from 0 to 1 on an ECB200 that is configured
for PROFIBUS-DP FBM223 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.
7.28.2 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.
7.29 Exceed Software

7.29.1 IP Address Displayed in the Exceed Icon
The new version of Exceed software (v14) that is installed with I/A Series software v8.8 or Con-
trol Core Services v9.0 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 corre-
sponds 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.
7.30 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.
7.30.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 > I/A Series 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.)
96
NOTE
Security settings may disallow access to the Control Panel applets. Security
enhanced Control Core Services uses Group Policy Settings to restrict access. Refer
to Security Enhancements User's Guide for I/A Series Workstations with Windows 7 or
Windows Server 2008 Operating Systems (B0700ET). Standard Control Core Ser-
vices security settings are described in “Restricted Desktop” on page 104.
2. A User Account Control (UAC) prompt appears.

A dialog box similar to the version shown in Figure 7-30 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.
Figure 7-30. User Account Control Prompt for Control Core Services Users
with Administrative Rights
A dialog box similar to the version shown in Figure 7-31 is displayed for users without adminis-
trative 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.
97
Figure 7-31. 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 7-32 and
Figure 7-33.
Figure 7-32. I/A Series Startup Options Dialog Box (Enhanced Security)
98
Figure 7-33. I/A Series Startup Options Dialog Box (Standard Security)
4. Select the appropriate option:

♦ 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 104. This option is not present on
security enhanced 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 104. This
option is not present on security enhanced 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.
99
♦ 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
Before selecting an Autologon option on security enhanced 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 on security enhanced Control Core Services, the
Autologon Configurator is invoked. Refer to “Autologon” on page 102.
The restricted desktop options take effect on next logon and are described in detail on page 104.
The other options take effect on station’s reboot.
The Autologon options are not available on a Domain Controller. When the control panel applet
is opened on a Primary or Secondary Domain Controller, these options are disabled. The
restricted desktop options are not available unless FoxView is installed. When the control panel is
opened on such a station, these options are disabled.
When options are disabled, an explanation is displayed near the bottom of the dialog box, as
shown in Figure 7-34 and Figure 7-35.
Figure 7-34. I/A Series Startup Options Dialog Box for Domain Controllers
100
Figure 7-35. 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
warning message is displayed near the bottom of the dialog box as shown in Figure 7-36. (This
warning overwrites any descriptions of why options are disabled). In this state, the OK button is
disabled. This condition may be the result of older software installers that fail to enable every
instance of current Control Core Services.
101
Figure 7-36. I/A Series Startup Options Dialog Box with Invalid Options (Enhanced Security)
To correct this condition, select one of the options in the dialog box. This enables the OK button.
Click OK.
NOTE
Do not change the startup options in the middle of a software installation unless
directed by the documentation.
7.30.2 Autologon
The Autologon feature automates the logon process by storing a user-specified account and pass-
word in the registry database. 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 with-
out requiring a user to provide appropriate credentials. Use this feature only in areas that are
secured by other means.
7.30.2.1 Autologon Configurator (Enhanced Security)

On security enhanced Control Core Services, after selecting an Autologon option from the con-
trol panel applet and clicking OK, you are prompted for the logon credentials to use. Enter the user
account, domain name, and the password (in both fields) as shown in Figure 7-37. Click OK.
102
Figure 7-37. 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).
NOTE
If you want to autologon to the local station (for example, if the control network is
not enabled), enter the station’s letterbug for the domain name.
7.30.2.2 Autologon Settings (Standard Security)

On standard Control Core Services, selecting an Autologon option from the control panel applet
uses the logon credentials of the standard Fox user account. To use different credentials, you need
to create a registry entry to specify the user account and password. The optional key to do this is
as follows:
HKLM\SOFTWARE\Invensys\IASeries\Autologon
This has to contain the following two values:
UserName REG_SZ string specifying user account name
PW REG_SZ string specifying account password
After adding, changing, or removing these values, open the I/A Series Startup Options control
panel applet, verify if the appropriate Autologon option is selected, and click OK. If this key is not
available, the Control Core Services use the logon credentials of the standard Fox user account.
To use the standard Fox user account with a different password, fill in the Autologon key with
UserName=“fox” and PW=“new password”.
103
NOTE
If difficulties arise with specific applications when you use a different account for
autologon, it is recommended that you delete these registry entries and use the stan-
dard Fox user account and password.
7.30.3 Restricted Desktop

The restricted desktop options provide a security option on standard Control Core Services to
limit user access on operator stations. When a user enables one of the Autologon, restricted
desktop access or Autologon, restricted desktop access and shutdown access
options, it results in 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 7-38. Start Menu in a Restricted Desktop
104
♦ 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 96.
7.30.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 7-39,
Figure 7-40, and Figure 7-41 are examples of this screen for users with different type of privileges.
Figure 7-39. Sample Welcome Screen for IA Plant Operators and for Restricted Desktop and
Shutdown Access
105
Figure 7-40. Sample Welcome Screen for Restricted Desktop Access
Figure 7-41. Sample Welcome Screen for Standard Fox User and IA Plant Admins
106
This screen provides access to the following commands, depending on the current user’s privi-
leges:
♦ Lock this computer - Disallows access to the station. The current user can unlock
the station by logging in. Refer to “Locking/Unlocking the Station” on page 107.
♦ Log off - Closes the current user’s programs without turning off the computer. Refer
to “Logging Off ” on page 107.
♦ Start Task Manager - Opens the Windows Task Manager. Refer to “Windows
Task Manager” on page 107.
♦ Shut down - Shuts down the station. Refer to “Shutting Down/Restarting the Sta-
tion” on page 108.
♦ Restart - Reboots the station. Refer to “Shutting Down/Restarting the Station” on
page 108.
7.30.5 Locking/Unlocking the Station

To lock or unlock the station, press Ctrl+Alt+Delete.
♦ While locking an unlocked station, the Welcome Screen appears.
Click Lock this computer.
♦ While unlocking a locked station, a prompt appears.
Enter the current user’s password and click OK.
7.30.6 Windows Task Manager

From the Task Manager, you can perform a number of system tasks, such as:
♦ Monitor the CPU
♦ Create new tasks and display statistics for currently running tasks or processes
♦ Start and close applications
7.31 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.
7.31.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 Log off.
♦ Click the Start button and select Log off from the power options submenu on the
lower-right, as shown in Figure 7-42.
107
Figure 7-42. Log Off from the Start Menu
Once the station is shut down, every user on that station is logged off by the operating system.
NOTE
When logging off, you may briefly notice detected error messages for processes that
cannot start properly. This does not indicate a real detected error. When the operat-
ing system terminates a needed process before signaling Control Core Services that
the logoff is in progress, the Control Core Services attempts to respawn the process,
resulting in the detected error messages. Once the operating system signals the Con-
trol Core Services of the logoff operation, the processes are allowed to terminate and
the detected error messages are removed.
7.31.2 Shutting Down/Restarting the Station

Users may shut down a station by performing one of the following options:
NOTE
Security settings may prevent access to the Shut down and Restart picks from the
Welcome Screen and Start menu. Security enhanced Control Core Services uses
Group Policy Settings to restrict access. Refer to Security Enhancements User's Guide
for I/A Series Workstations with Windows 7 or Windows Server 2008 Operating Systems
(B0700ET). Standard Control Core Services security settings are described in
“Restricted Desktop” on page 104.
♦ 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 7-43.
Figure 7-43. Restart and Shut Down Picks
108
♦ Click the Start button and select Shut down or Restart from the power options
menu on the lower-right.
♦ 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.
7.31.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
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
109
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
7.32 Migrating Existing Workstation or Server

with Windows XP or Windows Server 2003
Before migrating an existing workstation or server with Windows XP or Windows Server 2003 to
Control Core Services v9.3, you have to remove the SoftIO card from the workstation or server.
Leaving in the SoftIO card with Control Core Services v9.3 installed causes suboptimal condi-
tions for the GCIO serial driver (gcio_task). The SoftIO card is not supported on systems with
Control Core Services v9.3. This applies to both DELL and HP workstations or servers.
7.33 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 warning 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 chang-
ing time zones on Windows systems, it is possible for the AM/PM setting in the time to change.
110
8. V9.3 User Notes
This chapter contains user notes for the Control Core Services v9.3 release.
8.1 Windows Workstations

8.1.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.
8.1.2 “Local Area Connection” Not To Be Renamed in Network

Connections
In Control Panel -> Network Connections, which lists the available NICs, do not change the
name of any “Local Area Connection x” network connection. This can result in software installa-
tion issues or system instability.
8.1.3 Printer Monitor Warning 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.
8.1.4 Additional Security for Plant Operators and View Only

Users
In the appendix “Comparison of “Invensys Plant” GPOs” in Security Enhancements User's Guide
for I/A Series Workstations with Windows 7 or Windows Server 2008 Operating Systems (B0700ET),
the table “Group Policy Settings for I/A Series v8.8” (which also applies to the Control Core Ser-
vices v9.3) compares the group policy settings for the following Control Core Services/I/A Series
security groups:
♦ IA Plant Admins (the least restrictive policies)
111
B0700SV – Rev F 8. V9.3 User Notes
♦ 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 make them even more secure. These policy settings
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 B0700ET describes a generic procedure for
editing Group Policy Objects (GPOs), more specific 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 8-1.
Figure 8-1. Invensys Plant Operators/View Only Filtered v1.0 GPOs
112
8. V9.3 User Notes B0700SV – Rev F
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 8-2.
Figure 8-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.
113
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 8-3.
Figure 8-3. Editing GPO Settings
Optimally, the result appears as shown in Figure 8-4.
Figure 8-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.
8.1.5 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”.
114
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.
8.1.6 Inadvisable to Install USB Annunciator Keyboard Upgrade

Media (K0174LG) on Workstations/Servers with Control Core
Services
It is inadvisable to install the USB Annunciator Keyboard Upgrade Media (K0174LG) on any
workstations or servers with Control Core Services v9.0 or later. The USB-based annunciator key-
board drivers from this media are installed already as part of the Control Core Services v9.0 or
later installation, and installing these drivers from the K0174LG media will cause suboptimal
conditions in your station.
Be aware that if you try to install this K0174LG media on your workstation or server, a message
will appear: “This USB Upgrade only applies to version 8.8.0.”
8.1.7 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
115
The following messages appear in the System Manager as a result of the initial action request
when SMON has stopped responding.
Figure 8-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 8-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 8-7.
116
Figure 8-7. Clearing the f<LETTERBUG>+ Lock File
8.1.8 Administrator Password Not Set After Image Restoration

for HP DL380 Gen9 and Later Servers
Starting with the HP DL380 Gen9 server images for Windows Server 2008 R2, the Administra-
tor password is not set after the image is restored. It is vital to follow the procedures provided in
the Hardware and Software Specific Instructions manual for the specific model server being
installed and set the password for the Administrator account accordingly. This is especially vital if
the server is to be installed as a primary or secondary domain controller as the domain controller
promotion will fail if the password for the Administrator account fails to meet password complex-
ity requirements.
8.2 Applications
8.2.1 FoxDraw
8.2.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.
8.2.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-
117
log boxes are closed. It is recommended that you do not move these dialog boxes when they
appear.
8.2.2 Station Assessment Tool (SAT)

When running either of the following SAT 2.0 PowerShell cmdlets:
♦ Get-AllDomainPrinters
♦ Get-SystemAudit -t DOMAINPRINTERS
The current printer status (example, Idle, Printing, or others) is not currently reported by SAT.
The printer status reported in each of the SAT assessments and audits is “Offline”. These cmdlets
are discussed in Station Assessment Tool (SAT) User’s Guide (B0700DZ).
8.2.2.1 SAT Commands for Secure Foxboro Evo Systems

For secure systems, it is not advisable to execute the following SAT commands. This applies when
the user credentials under which the command is executed differ from the currently logged on
user of the remote station on which the assessment is being performed. Executing these com-
mands under these conditions can result in the remote station becoming unresponsive and needs
a reboot of the remote station to resolve the condition. For example, any assessment or audit
which results in SERVICES being queried or any general WMI query (such as the SAT Get-
WMICObject command or the general PowerShell Get-WmiObject command).
For example:
♦ Get-SystemAudit custom.xml -AssessmentOnly -Credential Admin1, where cus-
tom.xml contains an entry for SERVICES and Admin1 is not currently logged into
the remote workstations to be assessed.
♦ Get-SystemAudit custom.xml -t SERVICES, where the currently logged on user is
also not logged into the remote workstations to be assessed.
♦ Get-AllServices -Name NESRV1 -Credential Admin1, where Admin1 is not currently
logged into the remote workstation NESRV1.
♦ Get-AllServices -Name NESRV1, where the currently logged on user is also not
logged into the remote workstation NESRV1.
♦ Get-WmicObject -Class Win32_ComputerSystem -Name NESRV1 -Credential
Admin1, where Admin1 is not currently logged into the remote workstation
NESRV1.
♦ Get-WmicObject -Class Win32_ComputerSystem -Name NESRV1, where the cur-
rently logged on user is not currently logged into the remote workstation NESRV1.
It is possible to comment on the SERVICES entry from the audit XML files (such as custom.xml
and baseline.xml) and execute these assessments separately.
NOTE
This applies to both the SAT PowerShell Cmdlets and the SAT Graphical User
Interface (GUI).
118
8.3 Application Software

8.3.1 SOE and FoxHSDAI.exe Process
The FoxHSDAI.exe process is designed to run continuously. If the SOE instance is deleted,
FoxHSDAI.exe has to be stopped from the Windows Task Manager before a new instance is
created.
8.3.2 TDR Does Not Succeed in Printing Reports to Network

Printer
The TDR software application does not succeed in printing reports to network printers in
I/A Series software v8.8 or Control Core Services or v9.0 or later.
NOTE
You may get a detected error message reading 0x0000052e when you try to install a
network/shared printer with a workstation with Windows 7.
You can resolve this issue with one of the following workarounds:
1. Before you add the network printer, open a Command Prompt window, and type the
following:
start \\<servername>\<printername>
NOTE
In this command, <servername> represents the name of the print server and
<printername> represents the share name of the printer.
2. In the authentication window, enter the appropriate credentials.

Alternatively, you can store a trusted credential in the Credential Manager. To do this, perform
the following steps:
1. Click the Start button and click Control Panel. In the Control Panel, open the
Credential Manager.
2. Click Add a Windows credential.
3. In the dialog box, enter an appropriate print server name. Then, enter a user name
and password that are trusted on the print server.
4. Click OK.
8.3.3 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
119
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
Figure 8-8. Use Priority Alarm Printing Style
120
Figure 8-9. Use Original Alarm Printing Style
8.4 Device Monitor

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.3 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.
121
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).
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:
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.
8.5 I/A Series Configuration Component (IACC)

8.5.1 Using User-Defined Formulas
To use user-defined parameter in formulas, be certain to handle cases of null value. For example:
=IF(S(TLD_NAME_BASE)=="",LEFT(S(CNX_CSDINFO),4)&"T"&RIGHT(S(CNX_CSDINFO),
LENGTH(S(CNX_CSDINFO))-4),
LEFT(S(TLD_NAME_BASE),4)&"T"&RIGHT(S(TLD_NAME_BASE),
LENGTH(S(TLD_NAME_BASE))-4))
In the IACC System tab, define a new block type derived from the Foxboro defined blocks in
library, add a new parameter, add a new block type to template, and then use this new parameter
in the formula.
8.6 Control Processors

8.6.1 I/O Load (Fieldbus Scan Load) Increase Due to Failed 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
122
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.
8.6.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
Figure 8-10. 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.
123
8.7 Fieldbus Modules (FBMs) and Field

Communication Modules (FCMs)
8.7.1 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.
8.8 Time Synchronization

8.8.1 Incorrect Card Shown After Spectracom Time Card Driver
Installation
When installing Spectracom time card driver, the user has to select Spectracom TSAT PCI-FXA
Timing Board. However, the result of this installation shows that the driver was installed for
Spectracom TSAT PCI -HB1PPS Timing Board, which is an incorrect card name.
This is a condition specific to the Spectracom and no action is needed to solve this condition.
8.8.2 KSI Clock Daemon Application Runs on Startup

On a station with a GPS Timekeeper, a detected error message may appear indicating that System
Time could not be set:
Clock Daemon
Set System Time Failed, error: %d
If this message appears, proceed as follows:
1. Click Ignore to close the dialog box.
2. Remove the shortcut to the Clock Daemon application from the following directory:
C:\users\All Users\Microsoft\Windows\Start Menu\Programs\Startup\
8.9 Device Monitor

8.9.1 Device Monitor Master Active on Isolated Segments of The
Foxboro Evo Control Network
It is recommended that you install QF1302638 on all station that run the Device Monitor, to
upgrade the Device Monitor to a revision that disallows the following concern.
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, if one of the Master stations is not installed with
124
QF1302638, the Master station which takes over may not re-read the statuses of all 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:
2. Type the following command and press <Enter>: D:\usr\fox\cs\dm_recon
It is also possible to retrieve a list of the alarm destination statuses that Device Monitor
currently has:
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
A workstation should not be booted up 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 unavailability of alarms or control processor slowdown.
In addition, connecting a workstation to the control network which was booted up
offline will also cause a conflict with the Master Timekeeper which might result in a
time jump or other system instability.
8.10 Foxboro Evo Control Network

8.10.1 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 SSA chassis managed switches configured as
routers and implement VRRP for network redundancy.
Failover times for faults involving the unavailability of a single path between the routers of the
SSA chassis managed switches are typically one second. With active devices in the VRRP path,
failovers can take between 25 and 60 seconds.
The SSA chassis managed switches are discussed in The MESH Control Network Hardware Instruc-
tions for S-Series Switches (P0973KD/P0973KK/P0973LN) (B0700CE).
125
8.11 Control Network Interface

8.11.1 Initiating Reboot or Image Update Action on CNI using
System Manager v2.6
If you attempt to initiate a “Reboot” or “Image Update” equipment change action on a CNI via
System Manager v2.6, a detected “Cannot Initiate Action” error message may appear on the Mes-
sages tab in the System Manager. This detected error indicates that the CNI has been locked and
you are disallowed from performing this action.
To unlock the CNI, navigate to the directory “usr\fox\sp\locks” and delete the file fXXXXXX+,
where XXXXXX is the letterbug of the CNI.
This applies to System Manager v2.6 only.
8.11.2 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 failure 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 failure 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 failure of a CNI’s sin-
gle power supply is detected. It will exhibit the alternate behavior described above.
126
Repeat this procedure on the System Monitors hosting CNI stations.
8.11.3 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 station
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.
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.
8.11.4 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 8-11 below),
and a four second timeout per engineering units string on the display. Also, if the units contain
garbage character(s) from a previous display of the trend, the same timeout delay is experienced.
127
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.
Figure 8-11. Trend Pen Configurator in FoxView With Garbage String Displayed
8.11.5 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.
128
8.11.6 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.
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.
8.11.7 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.
129
130
9. Customer Cases Resolved in V9.3
This chapter describes the suboptimal conditions resolved in Control Core Services v9.3.
CAR Number Description

1123005 Had a problem with FBM46 where the AINR Block would not go to IOBAD /
OOS when the physical input is disconnected, as detailed below. - Input
removed, PRIMARY goes OOS in AINR while SECONDARY stays healthy
(holding last value), with the result PNT remains healthy. This happened for
channel # 1. - Tried above for Channel # 2 of FBM, same result. - Removed
backup FBM, SECONDARY goes OOS, with the result PNT also goes OOS. -
Installed the FBM Back, SECONDARY again goes healthy with value as 0.00
All above was done with physical field signal disconnected. FBM is Type 46
Hardware Revision is 0C Software Revision is 61.1 FBM Letterbug is 2060E1
while ZCP letterbug is 203C23 The system was recently upgraded from P79 /
Nodebus / CP30 to P90 / Mesh / ZCP270. Snapshots showing AINR block,
System Manager, Text Dump of CP are available.
1156704 Issue-1: While rebooting the one of the FCP270FT, Sysmonlog not logging
that CP's single status and after that CP boots sysmonlog not logging CP
redundant status. Customer expecting this information in sysmonlog as earlier
versions of IA. This information in sysmonlog is critical for them, since this
sysmonlog will be routed to Alarm Management System to analyze the daily
system alarms.
Issue-2: When single CP is rebooted, Equipment added online messages flood-

ing for all the child equipment of that CP in sysmonlog which is not required.
Customer does not want this message flood since it is not the case in earlier IA
versions.
1162100 Test configuration: while running the Message Manager non-redundant, an
alarm shower is triggered (a total of 8000 priority 3 alarms, ~400 generated
every 5 seconds) from a single ZCP270 running 830305. The Message Man-
ager is then stopped and restarted during the alarm shower resulting in lost
alarms (not delivered to the CAD). The alarms that are lost are not the alarms
that were generated prior to the Message Manager starting up. The lost alarms
appear to be occuring while during startup of the Message Manager. It appears
that the CP is loosing track of which alarms were transmitted as a result of the
CSU and which need to be transmitted as they are generated.
131
B0700SV – Rev F 9. Customer Cases Resolved in V9.3

1176885 No BAD IO with AINR even though bad alarm option set. CP0435 with
FBM246b (ECB83R SW49). The project has configured a new ECB83R for
the FBM246b and used the AINR to read the transmitter data. If the primary
FBM is pulled, the AINR shows bad io alarm for the AINR primary reading, if
the secondary FBM is pulled, a bad io alarm occurs for the secondary. If the
transmitter is pulled only one bad io alarm occurs for the primary meas, the
AINR then selects the secondary meas with no bad io alarm. In this configura-
tion it is impossible to get both primary and secondary meas values to get a bad
io when the field device is disconnected.
1179916 The server management process (/usr/fox/sysmgm/smat/servmgm.exe) that
monitors the server health details (power, diskspace etc) for Servers is installed
as part of the ASMDW7 package that can be assigned to a server AW in SysDef.
So if you decided that a server that has no human interface (OPC interface for
instance) and it does not need Foxview and System Manager Client/SMDH,
you also loose the server info in System Management! servmgm.exe should be
installed as part of IAMESH package in stead of ASMDW7.
1187068 There can be a delay in the execution of some sequences when one-shots are
configured between two different FCPs. For example an SFC transition can
occur which does not go to the next step for a certain time while all its condi-
tions are valid. It can last up to ~10 minutes and then resume itself without
operator action.
1188841 *Doug Cox problem pier to pier zcp270
After doing many checkpoints the site noticed that there were several Peer to
Peer points of a Boolean type which were not updating on the sink side but
there was no error indication. The site had seen this before and can correct the
issue by setting the point to 0 on the source side, checkpointing both sides and
then setting the point to 1 and checkpointing again. The case in point is two
ZCPs with version 870075 on a version 8.7 I/A non secure system. In some sit-
uations the source point doesn't exist in the OM lists of the source station, yet
the Sink side still has the point with an indication of Scanning.
1191638 VLV block in auto with AUTOPN, COUT, OPNLIM all true & DISABL &
CLSLIM false, no mismatch alm
AUTOPN to false
COUT to false
After 2 sec OPNLIM to false
After 2 sec DISABL to true
After 2 sec DISABL to false
MISMATCH alarm is initiated
After 6 sec CLSLIM to true
Why is mismatch alarm initiated when TOC is 1.2 (72 seconds) and the CLS-
LIM was true well within this time?
Why is DISABL influencing mismatch alarm detection?
When the same configuration and sequence of actions are done on a GDEV
block, MISMATCH wasn't initiated.
Is this the intended behaviour of VLV block?
132
9. Customer Cases Resolved in V9.3 B0700SV – Rev F

1193342 FBM227 showing spiked readings when connected to device.
Disconnected device, wired the TA connections together to set value at Zero
volts.
1194118 During the testing of QF-1106399 with redundant Message Managers run-
ning, an alarm shower of 30000 alarms was generated from 11 ZCP2070s.
During the shower, the ACTIVE Message Manager (1AW065) was stopped
forcing a failover to the PASSIVE MM (1AW066). When 1AW066 changed to
ACTIVE and alarms were being delivered, 1AW065 was restarted. After
1AW065 was passive, all of the 14 alarm destinations were missing the same
number of alarms.
1199182 Looking at the real outputs on the detailed display of and IND block the num-
bering goes from RO0009 to R00010 to RO0011.
Note: It's R, ZERO, ZERO, ZERO, ONE, ZERO where it should be R, O
(Ooh), ZERO, ZERO, ONE, ZERO.
Please correct the DD.
1207276 The AUTOCP<LBUG> process in the FCP ends up asking for a checkpoint
every 20 minutes because the request queue cur_cnt fills up to the maximum of
75. The condition can only be cleared by a reboot of the CP. These queues can
be viewed using rspic, cdt AUTOCP<LBUG>.
1212487 Normal behavior: Compiling ladder logic in ICC will create files in the
usrplc50 directory. These files are converted to .fdf (and .pdf ) files in the
usrplcfv directory. When opening a PLB block with foxselect, the .fdf files is
being called and the ladder logic will be shown in foxview.
Problem: When ladder logic is compiled in IDE, files will be created in the
usrplc directory. This file is not accessible by foxview. It was attempted to con-
vert this file to an .fdf file with the conversion tools but this was not possible.
This makes that the ladder logic is not viewable in FoxView.
1214102 After upgrading EEPROM revision of FBM218, from 2.41H to 2.46N
through quickfix QF1185258, following messages appeared in the System
Manager.
Every time a switch role is performed a comms failure is received.
133

1214953 Functionality of AINR block:
For the Boiler project, customer wants to use AINR blocks, but some strange
behaviour was found.
Configuration: AINR block with 2x AIN or RIN the inputs:

AIN1 --> MEAS_P of AINR
AIN2 --> MEAS_S of AINR
Scaling is done on AIN1/AIN2 (SCI=3), AINR (SCI=0)
When MEAS_P becomes BAD, AINR switches to MEAS_S as it should, but

the SELREQ remains on PRIMARY, this should also switch to SECONDARY
according to the documentation:
Select Request specifies which of the redundant input points is to be used

(0 = primary, 1 = secondary). The selection decision specified by SELREQ
is overridden if the specified point has Bad or Out-of-Service status. If
both points have Bad or Out-of-Service status, the primary point is used.
The value of SELREQ is changed by the internal block logic, until the
next set or reconfiguration, whenever the specified point is Bad or Out-of-
Service and the alternate point is not.
As the SELSEQ remains on PRIMARY, if the primary block should become

healthy (for example when input hardware is replaced in field), the AINR's out-
put would then immediately switch to MEAS_P which is not desired and could
cause process disturbance/bumps.
However, when scaling is done on AINR (AIN1/AIN2 SCI=0 and AINR SCI=
3), the SELREQ does switch to SECONDARY when MEAS_P becomes bad.
SELREQ should always switch to the healthy input when the selected input
becomes BAD or OOS, independent if SCI is done on AINR or connected
input-block?
134

1216807 Problem: On site a boothost at V8.7 with a CP at 880014 exists. The auto
checkpoint function is enabled. Everything is working. The boothost had to be
replaced with a new one. From that moment the auto checkpoint function is
not working anymore.
The issue was replicated/reproduced that Auto checkpoint stops for a given CP,
whenever you (have to) change the boot host, without rebooting the CP its
hosting. Changing the boot host in this case as well as for our Lab test means:
Replacing the actual station with an identical Station (Same P-code, same style
and same revision, same letter bug & both systems are installed with the same
commit Install disk and both hosting the same Software revisions/releases).
Changing the HW for a boot host typically will be required in cases that a
Faulted Workstation only can be repaired by a HW replacement or in cases that
customers upgrade their DCS I/A software to a newer release which often
requires newer Hardware (I/A 8.7, OS = XP or Server 2003 --> I/A 8.8, OS =
Win7 or Server 2008).
1218395 When a CP270 is configured to operate in Message Manager mode
(CFGOPT.B27 in its Station Block is set true), its apr_import task will broad-
cast each and every group name declared in any of the Compound GRxDVy
parameters and/or the Station Block's DVx parameters once every 80 seconds.
On larger systems, particularly those with one or mode nodes attached via ATS,
that results in a totally unnecessary flood of Foxboro Broadcats messages that
the system can perfectly do without.
Strongly suggest to disable the apr_import task in the CP opsys when
CFGOPT.B27 is true.
1219186 Few workstations are generating high multicast packets in the mesh network.
All packet has the information as below:

sglin Alarm restore to
It's observed that multicast packets generated is not always same number of
packets it's varies from time to time.
1221935 The histlnbc process maybe prevented from running (user will need to manu-
ally edit the /etc/hist*files if they add or remove historians on mesh network).
The following regsistry -
Hkey_Local_MachineSoftwareInvensysIASeriesLauncherHistorian Scanner.
This key should be saved (in case they want to add it back other wise it will
manually need to be created). (ME) should test in his lab - SOL2509 created to
address.
135

1228832 Intermittent horn issues were observed when configuring horns for Console
and Console2 in Foxpanels to play wave files through USB Speakers connected
to the station.
Console and Console2 horns were configured. When an alarm was generated
the horn would work once and then would not work again after it had been
silenced. After rebooting the workstation, the horn would sound again (Tone1
of console2) the first time an alarm was sent to the workstation. After the horn
was silenced, no further horn sounding was observed until reboot or log off.
1231457 It is observed that during FCP270 FT test everytime after the primary module
get rebooted sometimes system manager generating message Fault Tolerant
Exec SM_MSG -00046 Fault Tolerant Modules Now Married in smon log and
some time it does not.
IA 8.8 release notes says that Inaccurate SMON Messages During FCP270
Reboot related to equipment has been added on-line for all parent and child
ECBs associated with the FCP270 (which is incorrect and has not hap-
pened).These additional messages may be safely ignored.
Is it applicable for all additional smon logs during FCP270 Reboot?
EMEATAC :
ADDITIONAL INFO TO ORIGINAL CASE DESCRIPTION : When
rebooting the primary of a FT pair of FCP270 it appears that the message pat-
tern shown in System Monitor is not consistent for each time you perform a
reboot. Customer especially complaints about the fact that the ''Remarried''
message : ''Fault Tolerant Exec SM_MSG -00046 Fault Tolerant Modules Now
Married'' is not always shown.
136

1232201 Using the classic SMDH to look at the NodeBus Network, the info presented
on screen may be false. The attachment folder contains 16 screenshot slides that
visualize the problem.
01 shows the initial screen of our SMDH, the NETWORK selection is made.
02 shows our three redundant ATS'es. NODE01 is pre-selected by SMDH
03 shows result of NEXT LEVEL selection. The station named MORRIS is
manually selected.
04 shows first page of EQUIPMENT INFO for MORRIS
05 shows second page. Notice calculated MAC address ending on 24E
06 shows selection of double up arrow.
07 shows selection of right hand arrow to go to next page of nodebus stations
08 shows the pre-selected ABARTH station highlighted (be aware, no manual
selection made. The selection is automatically done by SMDH)
09 now the EQUIPMENT INFO is selected manually
10 shows first EQUIPMENT INFO page
11 shows the seconds page. Notice the repetition of the data. All is the same as
on slide 05 !!!! So SMDH shows you the MORRIS data under the ABARTH
name.
12 & 13 back up a level and select another station, TALBOT in this case.
14 manually selected ABARTH again
15 & 16 SMDH now shows the correct data.
So, the problem is that when you first select a station, then select the next page,
the system does NOT refresh the station data unless you manually select
another station first.
1239816 The redundant FBM233 fails to go on-line after reinserting in the slot. Scenario
Establish communication between I/A and Triconex system using redundant

FBM233 and TSAA protocol
Observe the healthy status of the FBMs and communication on the System
manager
Remove the Master FBM from the slot
Wait about 5 seconds and reinsert the FBM into the slot
The FBM does not go on-line, it is shown failed on the System manager. The
FBMs LED status
Red: On
Green: On
Tx/Rx: On
Master: Off
Tracker: Flashing
The test was repeated with about 50 blocks with the same result.
137

1241720 PIDA function with MODOPT = 8 (PIDtau) in a FCP270.
When PIDA function MODOPT is set to 8 and the DERIV parameter set to
0, it appears to still use the derivative action in the calculation. This is causing
large spikes in the OUT parameter of the function. All other MODOPT
option 1-7 in the PIDA function, switch the derivative action off if the DERIV
parameter is set to 0.
The PIDA function MODOPT = 8 in a CP40B processor appears to switch of
the derivative action off when the DERIV parameter = 0.
This problem was noticed when a CP40B processor was upgraded to a
FCP270.
1243546 The IAs system was recently upgraded:
-IAs 7.1 to FCS 6.0.1
-CP60 (6.5.2) to FCP280(900030)
After this upgrade, the customer has observed that the PIDA are not run as
before.
The oscillation of the output is important.
He need to change all INT parameters (divide by approximately 100).
The tuning parameters of these blocks are exactly the same between CP60 and
FCP280. (The comparison was performed through dbvu tool with option t on
CP60 and FCP280).
1244882 Unable to delete the CP270 dump file. If Windows Explorer is used to delete
the dump file, the following message is prompted:
This action can't be completed because the file is open in rls.exe
1245495 A problem with a slave configuration exists.
Configuration data requires :
4 off 1 BYTE Slave out/Master in modules at 1 by each
120 off 1 Word Slave out /Master in Modules at 2bytes each
(refer slave cfg.jpg)
Validates okay (refer validation ok.jpg)
Saves ok
But when I renter configurator to check configuration it gives error
If I set up for
4 off 1 BYTE Slave out/Master in modules at 1 by each
2 off 60 Word Slave out /Master in Modules at 2bytes each
No errors are returned. However customer has set up his side as per previous
configuration
1245941 FBM214 is communicating to a Rosemount 5300 and 5400 series transmitters.
When the customer checks the echo curve and make an adjustment and hit
apply. it causes a pactware error and it locks up. Task manager must be used to
stop it. After this the transmitter will need to be rebooted to re-establish the
pactware connection.
138

1248225 When a value is written from the DCS, the PLC changes the value before the
readback which generates a fluctuation between the IOUT and its Input
parameter.
This causes the value being written to in the PLC to also fluctuate for a certain
period of time before settling out. The problem occur when the register in a
PLC change from a HI to LO value at a faster rate. EX IF operator select and
arrow and they do several click up a then they go over the desired set point then
they click fast on the arrow down. The result of that scenario is 2 times on 3,
the IOUT get confused and start bouncing from the new value versus the last
value receive. IOUT write previous value in the PLC but the feedback receive a
new value in a meantime forcing the IOUT to write again. At some point it get
stabilize.
1249320 FF ECB201's reporting stale data error.
Report from site by our Brazil office is in the Car volume, Stale data error.pdf.
The site has 18,000 FF devices and are experienced configuring commissioning
the devices. They are having trouble with some devices/FBMs.
1250548 CP280: SUCPV1 crashed with a memory violation:
checkpoint files are already send to RB
Once loaded, CP goes into endless crash/dump/reboot cycle that lasts around 5
minutes per cycle.
The BB checkpoint on the other hand does not crash the CP but results in CP
not showing any data in FoxSelect and Station block shows CYAN points only.
On the real system here in house, adding any compound to the system running
on the BB checkpoint is enough to make it crash.
The FoxSelect of the in-house system shows one compound with a space in its
name while the name itself stems from a block description. See screen shot in
attachment folder.
While the CP was still in its crash/dump/reboot cycle on the SuikerUnie in-
house system, the CP eventually went to green LED state after having just fin-
ished a dump and then the module was pulled.
The module was taken to our lab, given a different letterbug (CP2801) and its
last dump (suikerunie1_DUMP1) was extracted. Then it was booted with the
DB checkpoint to see if the crash could be reproduced. It could, resulting in
suikerunie2_DUMP1.
Request dump investigation so root cause can be found and eliminated.
139

1251379 Issues have been observed when attempting to deploy an Endress & Hauser
Prowirl 200 MAO block. When the initial deployment occurs (with only 4
connections) the MAO block is scheduled and works fine.
When adding another connection, the deployment seems to fail. Although the
block seems to be partially deployed.
The message ""OperationFailed F2281A_SEG4:PWRL200_MAO <pipe> E41
- UNLINKED INPUT SECURED; CHECK OM LISTS"" shows up.
The only way to fully get the block functioning with the proper connections is
to UNDEPLOY and then DEPLOY.
1251588 CINR/COUTR issue
The following issues with CINR/COUTR blocks were found.
1- When parameter IVO in CINR (in simulation mode IOMOPT=0) block is

set to true the block does not react to it by inverting the output, instead it func-
tions as if IVO was false (see block 3KCP_D3:419ARSY1 in the attached save
all CP Q419UC)
2- Some COUTR (in simulation mode IOMOPT=0) block have their INITO
parameter always latched to true even though the conditions for the INITO
parameter to be true are unavailable (compare blocks
3DAS_D3:Q4173417_O1 with 3DAS_D3:Q4173417_O2 in the attached
save all CP Q417UC)
1251605 dbvu280 reports the C:B.P link, but omits any parameter extension.
Configured 2 CIN blocks, 1 CALCA blocks and 1 PAKIN block, where
CALCA block (CALCA1) BI01 is linked/connected to
<compound_block>.CIN1.CIN and BI02 linked to
<compound_block>.CIN1.CIN.~
and CIN block CIN2 IN linked/connected to
<compound_block>.PAKIN.PAKCIN.B16
Ran a dbvu280 -t -I D:usrfoxspfilesOS1C80 -O CP280MapOffsets.txt -D
D:usrfoxspfilesDB<cp_letterbug>.UC -F
Snapshots will be made available.
It looks like dbv280 is behaving like dbvu270; not showing extensions like .~,
Bxx, etc
1254808 FBM219 or any version IOM file does not honor TDR/SOE requests
140

1255313 These updates need to be evaluated for inclusion in FCP280:
CAR1191638
CAR1162100
CAR1207276
CAR1241720 - QF is called QF1241720)
CAR1156704
CAR1231457
This additional update will be ready subsequently:

CAR1135923
CAR1248225 (dup)
1256567 Continuing on case 1253026.
After the upgrade to CCS9.1, an attempt to reproduce the case of flashing Cyan
of DCI blocks when the CP reboots was made. The issue is not reoccurring.
The flashing Cyan of the BIN and BOUT blocks still occurs when disconnect-
ing the active field bus cable to the baseplate housing the FBM247.
The CP name is SAFC81
The FBM247 is SA8101.
The test was performed after 1:00 pm MMT on 26th January.
The Cyan flashing is not happening all the times.
Another issue, when the cable was disconnected, the failure message is appear-
ing immediately.
But when it is connected back, the recovery message takes 1:7.75 minutes to
come, an unacceptable amount of time.
141

1257492 Working in a project to use the I/A system to work as HMI for their GE Tur-
bines. They are using FBM233 with OPC Client FDSI driver to communicate
to an OPC Server developed by Matikon, ""MatrikonOPC Server for GE Tur-
bines"". In the past months, they have been testing this communication, found-
ing and solving a lot of issues, but they have a big problem with the behavior of
output DCI blocks (ROUT, IOUT).
Problem is that, in the first connection between FBM233 and the OPC server,
the ROUT and IIOUT blocks write a ""0"" in the OPC tags associated to these
blocks, independently of the values of the tags. Values are overwritten, which is
dangerous to the operation of the turbine.
That happens with ROUT and IOUT blocks that are not connected to any
COMPOUND:BLOCK.PARAMETER. They are used from FoxView dis-
plays.
First connection between FBM233 and OPC server can be done if FBM is
rebooted, or if the Matrikon OPC server is reinitiated and connected again with
FBM.
While OPC server is restarting, OPC tags are in bad quality. During this time,
the ROUT and IOUT blocks are reading a ""0"", and when OPC tags are yet
operative, with correct values, ROUT and IIOUT blocks write a ""0"" to these
tags, overwritten the operative values.
Another issue is related to what GE Mark VI defines as ""pushbutton"" vari-

ables. This is an integer variable and is configured using an IOUT block. I/A
write integer ""1"" in IIOUT block, and send this ""1"" to GE controller tag.
When GE controller read value ""1"" in this tag, automatically write integer
""0"" in this tag. IOUT block reads ""0"", and, without an explanation, it
sends ""1"" again to the tag. This is dangerous because that means GE Turbine
receive 2 or more commands and it doesn't respond well.
They have been testing all kind of block parameters, FDSI configurations and
even implementing a lot of filters in the MatrikonOPC Server for GE control-
ler, which is very flexible.
The project is arriving to the end and the intention is operating GE Turbines
through FoxView in all their Power Plants, but due to the criticality of the oper-
ation of the turbines, this problem must be solved.
142

1258598 FBM214 (EEPROM 2.47B) Letterbug: 561405
All input channel got freeze, no variation showing in any of input channel
FBM and all Child devices showing no error in SMDH
Problem noticed by plant operator as no variation observed in process variable
in DCS from last 2 days
Problem confirmed after looking trend history for last 2 days, which was not
varying
FBM replaced with new module, and problem got resolved (process variables
updating)
No error on SMDH and no information in smon_log, if such thing repeats, it
is very difficult to trace fault in system.
1258627 When using som.exe on Windows to identify ghost/orphaned OM lists on a
system, som = reports the OM list's associated PID as a 5-character entry. On
this system, Windows actual PID can and does exceed this over time. For exam-
ple, a Windows PID of 233532 is running but the associated PID reported in
som is 33532. This makes identification of ghost/orphaned lists very difficult.
1260630 Alarm Status Indicator of the first unacknowledged alarm in Current Alarm
Display blinks at a significant higher rate then the alarms in the remaining
rows.
1262842 On an IASPT 10 pressure transmitter (IDP10, IGP20, IAP20) Revision ""0x30
As Fieldbus Foundation informs all devices calibrated in a certain value must
shows uncertain quality when the Process Value is upper or lower than the cali-
bration.
But it does not happen for the IASPT10, for those model don't matter whether
the PV is upper or lower from than the calibration and the quality keeps as
Good Non-Cascade.
After a certain time measuring the PV out of calibrate value the LAS (FBM228
firmware 1.28 and EEPROM 6.20 or 6.19) lose the communication with trans-
ducer block, as a consequence the LAS lose communication with resource and
AI block either.
The card may have lost the communication because the device still during a
long time working in a wrong way (out of the calibration value and showing
quality as Good Non-Cascade).
1267615 Issue confirmed with the information below will tell you how to produce more
reasonable memory usage numbers for the sequence blocks. The latest spread-
sheet is missing the "10 bytes per HLBL line of code" in the memory estimator.
1) FCP270 Sizing Tool B0700AV-K

2) FCP280 Sizing Tool B0700FY-A
3) FCP280 Sizing Tool B0700FY-B
Seq Description 1) 2) 3)
Memory used with 1000 IND of 100 lines 3275 2890 2890
Memory used with 1000 IND of 1000 lines 12275 (overload) 11690 KB
11690 KB
143

1268903 An issue related to E+H transmitter LevelflexFMP5X. it is related to the chan-
nel number entry as per the DD file the channel number consist from 5 digit
and when trying to put this number on the AI block the download fails.
1269277 Usually the parameters from CALCA II01 and II02 .. are used. This parameter
in CALCA is declared as O01, O02 ...O16.
However, on FCP280 is not working, when the parameter O01 is used in the
steps, it does not work, from O02 to O16 it works very well, it never happened
on FCP270 or ZCP.
The function ""STH LO01"" does not work when dealing with negative num-
bers.
Further investigation into this issue has revealed that on CALC or CALCA
blocks running on a FCP280 the function I.e.: ""STH LO01"" does not work
if the stack holds a negative value and the result is always '0'. On the xCP270
this functionality works properly, or negative values are processed properly.
After more testing, this might be an application (miss-applied) issue.
1270563 Find the below issue observed in Reliance J3 FAT with FBM218,
1 If the Master FBM218 is taken offline from system manager, Tracker changes
to Master with some error logs in system manager
Again if this module is taken online from system manager, It will not come
online.
This issue is randomly observed and is arising only when the left module is
Master.
2.FBM218 (Channel 1) is set to give 12ma in the field (Output value).

If the Master FBM is removed, Tracker changes to Master but at the same time
for 2/3 seconds current drops to 10ma and again restores to 12ma.This issue is
observed when channel 1 child ECB is configured as NOFAIL. For 4-20 con-
figuration this issue is not observed. FBM218 using image 2.47B
FCP280 using image 900032
1273272 CP is missing CP270 upgrades for CAR1191638, 1195614, 1214953,
1251379, 1251588, 1257492, 1187068 and 1271427
1274071 For PIDA blocks and PID family blocks, as well as RATIO blocks, when the
INCOPT is set to 1, and SUPOPT is 2 or 4 (DDC mode), the LHI bit in the
SUPBCO parameter is set to True when the output is clamped at low; the LLO
bit is set to True when the output is clamped at high.
1275241 QF1253717 will remain vulnerable to being overwritten and is not resolved by
QF1259689. QF1253717 addresses a Network Time Protocol (NTP) security
vulnerability as noted in advisory 2015007abi. If QF1253717 is installed on a
workstation, it is possible that a Day 1 process could result in the NTP execut-
able being overwritten.
144

1276218 System:
1. H90 server installed with CCS 9.1/CS 6.0.
2. Server hosts FT FCP280s (CP Image 091001).
Observed Issue:
1. While attempting to deploy a single control block (IIN) from IDE to FT
FCP280 both primary and shadow CPs went offline. It was determined that
block had invalid tag name assigned to PNT_NO parameter (parameter
included spaces and special characters). The specific string configured in
PNT_NO parameter is as follows: BmsFdfStatus = BMS FD fan status number
(SIGNED 16-BIT INTEGER). NOTE: Block successfully passed validation
without warning prior to deployment.
2. Once CPs went offline they would sometimes recover, however twice
observed that CPs would not recover until power to CPs was manually cycled
off/on.
3. This entire exercise was repeated with same results observed.
4. Installed FCP280 Quick Fix QF1255313 (CP Image 091005) and repeated
exercise with same results observed, CPs rebooted.
5. With IIN block correctly configured with valid PNT_NO parameter the
block deployment was successful and CP remained online.
1276403 FBM228 iom128 v6.21
Following is the scenario where Control in Field failed for DVC6200 posi-
tioner(020302.cff ) & GE Positioner('010201.cff ).
1) Configure the FF DVC6200 or FF GE SVI Positioner as LAS on segment.

2) Configure simple close loop having AI->PIDFF->AO block(AI block any
transmitter, PIDFF & AO block of DVC6200 positioner)
3) Operate the loop in auto condition.
4) Remove the Master FBM, LAS will be transferred to BACK-UP
LAS(Tracker FBM).
5) Try to change the setpoint of PIDFF block, PIDFF block goes into CYAN,
and there is no way to recover it back, only option is redeploy the block in to
FCP.
So PIDFF block should not go to cyan while changing the setpoint on Master
FBM failure. And there is no consistency in occurrence of this behaviour.
145

1277390 Recently EEPROM 2.47B was applied to all type of HART FBMs.
The below set of messages were seen for both FBM215 as well as FBM218.
Below an example for a FBM215
56CP1E Process = 56E111 FC04 -39 65 malfunction retry count exceeded

56CP1E Process = 56E111 FC13 -39 66 malfunction cleared
56CP1E Process = 56E111 FCD9 -39 65 malfunction retry count exceeded
56CP1E Process = 56E111 FCFF -39 66 malfunction cleared
Many of them appear in smon_log.

Why the message is not specific to a channel.
If the troubleshooting suggestion is to check Field customer will ask - what
Field device?
Is this related to a common counter for all devices malfunction from all config-
ured channels?
What is the maximum count that is exceeded?
Why the messages appears one after another if the counter is cleared?
Is the counter so small that can be exceeded in few seconds?
Device Malfunction set by a specific Field Device will be propagated to the con-
trol scheme (since in this particular case, it is transferred from legacy 4-20 tech-
nology to HART) and it will switch the particular controller to manual.
As mitigation some alarms has been configured for critical loops.
With this new message the fear is, all the controllers connected will switch to
manual?
1277691 CP280 go to single with follow message:
015-06-30 15:57:42 1HFF1C Fault Tolerant Exec SM_MSG -00047 Fault
Tolerant Prim Module Now Single. ROM Addr 00006C2E04B8
2015-06-30 15:57:45 1HFF1C Process = Shadow Report RDHSS 000130 -
Other module broke off marriage
2015-06-30 16:05:34 1HFF1C Process = Marriage Task RDHSS 000130 -
Interlink detected
2015-06-30 16:05:49 1HFF1C Process = Marriage Task RDHSS 000130 -
Marriage requested
2015-06-30 16:05:50 1HFF1C Fault Tolerant Exec SM_MSG -00046 Fault
Tolerant Modules Now Married
2015-06-30 16:05:51 1HFF1C Process = Shadow Report RDHSS 000130 -
Reboot SS = 233 err-code 50 action 18 task 255
2015-06-30 16:16:20 1HFF1C Process = SysMgr Service SYSMGR -00001
Acknowledge
2015-06-30 16:16:20 1HFF1C Station SYSMON -00045 Equipment failure
acknowledged
LED red, Display empty.

After reboot with the reset button the cp boot an run fine up to now.
146

1280330 My colleague is on site doing a CP60 to FCP80 migration.
Find attached ecb block listing of the 2 FCP280.
C82MCP has 2 pairs of FBP11-R and C83MCP has 1 pair of FBP11-R
FBP11-R are online and seems working well in system manager. LEDs are
green.
All I/O modules are online but in red.
Although the whole data base is built for channel # 3, the majority of packets
still are sent out over channel # 1, clearly showing that the CP280 code isn't
quite fit to handle migrated Spectrum I/O hardware yet.
1282371 After testing the three QC, a problem was found with the upload and compare
IACC utility tool as it is still upload the unsigned integer value from the CP.
1287484 Fixes
- CAR1269277
- FCP280 FT has stopped allowing IPC connections from host workstation
- FCP280 FT (v090022) has stopped allowing IPC connections from host
workstation.
1287671 A change to the station block detail display is needed so that FoxView can allow
for the opening of the correct station block display when that station block
resides on an FDC280 module. Currently, if a station block resides on an
FDC280, FoxView will open up the station block display used for legacy mod-
ule types (CP60 and earlier). This is different than the display used by the
newer module types.
1292605 The dbvu or omget doesn't report the correct value for the HWTYPE parame-
ter of the FBM04.
Procedure to reproduce:
- Install one FBM04, hosted by FCP270 or FCP280.
- Put the FBM on-line
- Open a cmd window and change to the korn shell
- Change to the /opt/fox/bin/tools directory
- Type:
omget CPNAME_ECB:FBMNAME.HWTYPE
Where CPNAME is the CP letterbug & FBMNAME is the FBM letterbug

Example:
omget F28050_ECB:JGMD02.HWTYPE
F28050_ECB:JGMD02.HWTYPE (byte): -52
The result is -52 which is not correct,
147

1294270 FBM245 redundancy test failed at staging, followed the below procedure:
1) From system manager took offline Main module.
Result : Main module failed and Tracker module become master.
2) From System manager took online Tracker module
Result : Smon_log gives message Tracker module online, but system manger
showing Tracker module failed.(Tracker FBM Hardware also in failed condi-
tion)
In EVO 9.2 version IOM file for FBM 245 is 2.47B, from EVO 9.1 Quick fix
list was found in QF1258598, the IOM image for FBM245 2.47C was found,
so 2.47B & 2.47C image was tested but result is same.
IOM image 2.47C

1295391 A CAR was needed to be created to update the FCP280 with these CP270 fixes
1123005
1191638
1218395
1252882
1271427
1279169
1216807
1269277
1277691
1296526 2 items if you cancel CCS 9.2 installer on OffMesh server:
- InstallShield offers ""Show the Windows Installer Log"" (MSI installer).
This work for OnMesh, but for OffMes, you have this error popup:
Error 2732. Directory Manager not initialized
- Domain information (as illustrated with B0700SU_A fig 5-16) has now a
choice offered:
New Forest or Replica (while the first time it is only New Forest, and this is not
documented).
Additional item
- If you interrupt the setup, in the middle of a step, it will automatically go to
the next step, without retrying the step in progress (example at step 16 you can-
cel the setup, the next time, it will not offer you to configure new user accounts
so you have to reload the server).
148

1297349 Verified this in our lab on an AW with I/A 9.1(.576) hosting an FCP280 run-
ning image 091014
and confirm your findings regarding the wrong maximum numbers of source
inter-station IPC connections shown via rsom.
rsom -> conn is showing a maximum of 30 sink (om_server) connections, being

ok.
rsom -> sconn is showing maximum of 100 source (scanner) connections
instead of 200.
Field Control Processor 280 (FCP280) PSS document (PSS 31H-1FCP280)

mentioned that Maximum Number of IPC Connections for CP280 is 231; 200
connections for source points; 30 connections for sink points; 1 connection for
internal use only.
While checking in RSIPC,CONN & SCONN we found that Total Sink points
showing 30 no's & Source points showing 100 no's. If two Source channel used
then RSIPC showing 98 free channel available.
we have selected CP280 in RSIPC & RSOM utility.
1) Is this bug in RSOM tool?
or
2) CP280 Sink and Source hardware limitations & PSS having wrong entry?
1299136 This is a tracking CAR to provide a CAR number for a quick fix of the
FCP270/ZCP270. All of the items being fixed are FCP280 items, and not
available for use on a 270 QF
1301146 The dbvu270 utility with options -rs or -t doesn't know how to deal with block
type 52.
1302096 While working on Hot Case # 1300199 for Heineken and trying to investigate
PLB and Ladder behavior, we noticed that the "rsom" tool has lost its capability
to display the value for binary parameters.
Each and every binary parameter that is in "scanning" mode, displayed using
the "opvr" command, shows nothing but spaces in its "value" field.
This is regardless of its actual value i.e. both 1 (true) and 0 (false) are repre-
sented by spaces.
1302638 Vehicle for releasing the Device Monitor functionality to support CNI 1.1 that
is provided in CCS v9.3 for CCS versions 8.8-9.2.
149

1304921 On FCP280 the getpars utility doesn't report information for the ECBs.
Procedure to reproduce the problem
In the /opt/fox/bin/tools directory type:
Example 1
getpars -UCPNAME* -n -mCMPNM:%15s -mCP:%7s -mTYPE:%7s -mDE-
SCRP:%32s
Example 2
getpars -UCPNAME -mDESCRP:%32s -mLSCO1:%5.2f -mHSCO1:%5.2f
Where CPNAME is the letterbug of the FCP280.
Both examples should provide information about the ECBs

1305060 Release vehicle for CCS v9.3 Trailer which will include the latest CNI image
version.
1312252 When upgrade 091014 to 019015 for FCP280, we faced CLAC&CLACA trig-
ger the command randomly. It made the plant run in a high risk. There are
some modification for CALC&CALCA in version 091015. How to resolve it
and it will resolve after upgrade to 091016? site engineer reported: CP280 with
019015, Calc /Calca BO trigger unexpectedly, not matching BI input and
logic.
site CP280 now upgrade to 019016, not sure if the issue reoccur? issue occur on
CALCA blocks, there is no CALC block on site. Each time, a different CALCA
is discovered an unexpected output, not match to input and logic.
newly created a CLACA block in each CP for testing, no link for Bi01--Bi16,
OR all the input BI signals and then OUT BO01--BO08. BI &BO put into
history.
on June 22nd, 13:12:26, history data show a test CALCA block Bi01--Bi16 all
zero, but Bo01--Bo08 =1.
screen captured.
After CPs had been replaced and remained EPROM at 091001, unfortunately,
the issue is still caught. But when GPS is disconnected. So The Issue is now sus-
pected being caused by GPS.
This issue is only been observed in CALCA block, not sure for other type
blocks
1324071 Release vehicle for initial offering of the FDC280.
150
Appendix A. Files to Back
Up/Restore
This appendix details the standard Control Core Services files and directories to consider
backing up when migrating from I/A Series software v8.8 or earlier or Control Core Services
v9.0-9.2 to Control Core Services v9.3 on a hard drive of a Windows workstation for
restoration onto the Day 0 drive.
You can back up the user files, and files that support applications.
A.1 Saving Files

For workstations running the Windows operating system, files have to be saved to removable
media or some other medium, for example, a recordable CD in order for the files to be restored
after the installation.
A.2 Files to Back Up/Restore for Day 0 Migration

Files listed in the following subsections may be backed up from your pre-v8.8 Windows system
for later restoration.
A.2.1 CNI Files

On the CSA server workstation:
♦ C:\ProgramData\Invensys\IASeries\AccessListEditor\cs_devmon_CNI.cfg
♦ C:\ProgramData\Invensys\IASeries\AccessListEditor\NamespaceMap.xml
♦ C:\ProgramData\Invensys\IASeries\AccessListEditor\ConnectionSettings\CNIConfig.x
ml
On the CNI host workstations:
♦ C:\ProgramData\Invensys\IASeries\AccessListEditor\*.xml {For the entire set of
Access List configuration files}
A.2.2 Application Databases

Consider backing up the following application database files. These files reside on the D: drive of
a Windows workstation.
Files requiring changes need to be recustomized.
NOTE
Do not just replace Day 0 files with older files.
151
B0700SV – Rev F Appendix A. Files to Back Up/Restore
A.2.2.1 AIM*API
For detailed information on saving the AIM*Historian database, refer to AIM*Historian User's
Guide (B0193YL) and AIM*AT Installation Guide (B0193YM).
NOTE
Stop the processes that write to the database (Historian, AIM*Historian, or
FoxAMI™, for example).
Consider backing up the following application database files:

♦ \opt\aim\bin\an_init.tcp (server file)
♦ \opt\aim\bin\aimapi.cfg
♦ \opt\aim\bin\alias.cfg
A.2.2.2 Control Libraries

♦ \opt\fox\ciocfg\sequenlibrary
♦ \opt\fox\ciocfg\sequeninclude
♦ \opt\fox\ciocfg\plblibrary
A.2.3 Display-Related Files

Back up every customized display file. No display file conversion is necessary when migrating dis-
play files from a pre-V8.x Windows workstation. Display file conversion may be needed if you
have displays from a UNIX-based workstation that you would like to port to a V8.x Windows sys-
tem. Refer to the appendix titled, “Display Convert Utility” in FoxDraw™ Software (B0700FD)
for instructions on using the conversion utility.
Customized markers, fonts, faceplates, and so forth, developed using the FoxDraw package, are
stored in the directory /opt/customer/displib.
Consider backing up the following display-related files. These files reside on the D: drive of a
Windows workstation.
♦ \usr\fox\alarms\<logical_name>AAtab1
♦ \usr\fox\alarms\<logical_name>AApan1
♦ \usr\fox\alarms\commgrp.cfg
♦ \usr\fox\alarms\alarms.fmt
♦ \usr\fox\alarms\<logical_name>.apc (or <logical_name>.apccr)1
♦ \usr\fox\alarms\horn.cfg
♦ \usr\fox\wp\data\wp5?_cmds2
♦ \usr\fox\wp\data\wp5?_glbls.12
♦ \usr\fox\wp\data\wp5?_glbls.all2
♦ \usr\fox\wp\data\am_cmds2
1. Before restoration, make sure file names contain the correct workstation’s logical name.
2. Files requiring changes need to be recustomized. It is inadvisable to simply replace Day 0 files with
older files.
152
Appendix A. Files to Back Up/Restore B0700SV – Rev F
♦ \usr\fox\customer\hi\dmcfg2
♦ \usr\fox\customer\alarms\cfg2
♦ \usr\fox\customer\config2
♦ \opt\menus
♦ \opt\disp
♦ \usr\disp
♦ \opt\customer
♦ \opt\custom\Initial_Disp.*2
♦ \opt\fox\env\*.*2
♦ Customer Display Files.
A.2.4 System-Related Files

Consider backing up the following system-related files. These files reside on the D: drive of a
Windows workstation.
A.2.4.1 Application Files

♦ \etc\fox\opsys_usr.cfg3
A.2.4.2 Historian or AIM*Historian Files

♦ \opt\aim\inst
♦ \opt\aim\myfiles.
A.2.4.3 User Applications and Third-Party Package Files

The databases and configuration files for user applications and third-party packages have to be
backed up. Include Foxboro Industry or Application Group applications found in /etc/fox/rc.fox-
apps and /usr/fox/bin/user_apps.dat.
Following Control Core Services installation, these files can be restored and the applications and
third-party packages can be reloaded or installed from user- or vendor-supplied media.
NOTE
Reinstallation of third-party packages mandates that the original or a newer version
of the package media is available. Consult with the vendor to determine compatibil-
ity and rekeying requirements.
3. New (Day 0) versions of these files may need customization using data from your older files. It is
inadvisable to simply replace the Day 0 files with the older files.
153
A.3 Backing Up and Restoring Compound Summary

Access (CSA)
NOTE
Do not use other methods of backing up and restoring CSA database files, such as
archiving the data files from or to the /opt/fox/csa directory.
NOTE
In the following CSA procedures, keep in mind that the term “50 Series” applies to
workstations running the UNIX operating system, and the term “70 Series” applies
to workstations running the Windows operating system.
To perform the CSA operations below, you need to be in a VT100 session or Command prompt
window on the CSA host station.
♦ On 50 Series stations, use a WYSE terminal or start a VT100 session from the
SftMnt pull-down menu.
♦ On 70 Series stations, start up a Command Prompt window, and type the following
to get into a Shell mode:
D:
ncenv
sh
A.3.1 Backing Up CSA (CSA_Save)

On the CSA host station, perform CSA_Save to back up the CSA database files.
NOTE
The CSA_Save operation might fail for individual stations that have compounds
without blocks. When this occurs, remove the empty compound, using the Inte-
grated Control Configurator, and retry the CSA_Save operation.
1. Back up the CSA database files. Before performing this operation, consider the
following:
♦ An empty directory has to be available for the CSA_Save operation. The
(CSA_Save) operation might fail for stations for which a file already exists.
♦ For drive space requirements, assume that you need 15 KB of space per control
station. Use the df command to check available drive space in the /usr partition.
2. Type the following:
cd /usr/fox/csa
mkdir save
CSA_Save ./save
This saves the CSA files in the /usr/fox/csa/save directory. There is one text file for
each control station.
154
Appendix A. Files to Back Up/Restore B0700SV – Rev F
3. Verify the contents of the save file(s). Type the following:

cd /usr/fox/csa/save
ls -l
Verify that each control station has a text file in this directory.
4. Archive the files onto removable media. Type the following:
tar cvf /dev/fd0 /usr/fox/csa/save (50 Series diskette)
tar cvf a: /usr/fox/csa/save (70 Series diskette)
tar cvf f: \csa_save.tar /usr/fox/csa/save (70 series USB drive)
The drive letter “f:”, as shown in the above example may vary depending on the
other peripherals attached.
A.3.2 Relocating CSA

After modifying System Definition to move CSA to a new host, you have to perform the follow-
ing procedures:
1. Perform a CSA_Save operation on the original host. Refer to “Backing Up CSA
(CSA_Save)” on page 154 for more information.
NOTE
If you perform a Day 1 operation in order to move the Compound Summary Access
(CSA) server package from one workstation with CCS v9.3 to another workstation
with CCS v9.3 and you have performed deployments to CNI stations involving
CNI hosted alarm destinations, the following special action is required.
Move the C:\ProgramData\Invensys\IASeries\AccessListEdi-
tor\cs_devmon_CNI.cfg file from the old CSA workstation to the new CSA work-
station prior to initiating any subsequent deployments to the CNI stations.
Furthermore, copy the following CNI configuration files to the new CSA server
workstation:
C:\ProgramData\Invensys\IASeries\AccessListEditor\NamespaceMap.xml
C:\ProgramData\Invensys\IASeries\AccessListEditor\ConnectionSettings\CNICo
nfig.xml
2. Remove CSA from the original host.

To remove CSA from a pre-v8.8 workstation, type the following:
♦ cd /usr/fox/bin
♦ Use an editor such as vi or Wordpad to open the file fox_apps.dat.
♦ Delete the record “ACSA”
♦ Save the file and exit the editor
♦ Reboot the workstation
To remove CSA from a workstation with I/A Series software v8.8 or Control Core
Services v9.0 or later:
♦ Perform a Day 1 installation on the workstation using the committed configu-
ration files from updated System Definition.
155
3. Install CSA on the new host (as part of a Day 0 or Day 1 installation) using the com-
mitted configuration files from the updated System Definition.
4. Perform a CSA_Merge operation on the new host. Refer to “Restoring CSA
(CSA_Merge)” on page 156 for more information.
NOTE
The CSA Server does not start and CSA_Merge utility does not work on the new
host until CSA has been removed from the original host.
A.3.3 Restoring CSA (CSA_Merge)

On the CSA host station, perform CSA_Merge to restore the CSA database files.
1. Extract the CSA files produced by the CSA backup procedure. Insert the removable
media and type the following:
tar xvf /dev/fd0 (50 Series diskette)
tar xvf a: * (70 Series diskette)
tar xvf f:\csa_save.tar (70 Series USB drive)
The drive letter “f ”, as shown in the above example may vary depending on the
other peripherals attached.
2. Restore the CSA database. Type the following:
cd /usr/fox/csa
CSA_Merge ./save
3. You can remove the CSA text files at this time to recover drive space. Type:
rm -r /usr/fox/csa/save
156
Appendix B. 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
B.1 Image Revision Levels for Control Stations and

ATS with Control Core Services v9.3
Table B-1 lists the control station and ATS EEPROM revision levels that have changed for this
release.
Table B-1. Control Core Services V9.3 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
Field Control Pro- FCP280 N/A N/A N/A 090022 090022 091001 092012
cessor 280
Control Network CNI N/A N/A N/A N/A N/A 092065 093040
Interface
Field Device Con- FDC280 N/A N/A N/A N/A N/A N/A 090000
troller 280 9000
Z-Module Control ZCP270 860016 870001 880009 900004 900018 900035 920040
Processor 270
Field Control Pro- FCP270 860016 870001 880009 900004 900018 900035 920040
cessor 270
Address Transla- ATS 860016 870001 880009 900004 900018 900035 920030
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.
157
B0700SV – Rev F Appendix B. EEPROM Revision Levels
Table B-2 lists the legacy station software and EEPROM revision levels supported for this release
of the Control Core Services.
Table B-2. Control Core Services V9.3 Legacy Station EEPROM/Image

and Software Revision Levels
EEPROM
Station Image Software Revision I/A Series
Description1 Mnemonic Name Version Level Release
Allen-Bradley Integrator 30 AB30B OS1A3B2 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 OS1FDB3 6.5.6 3.32 7.1
Modbus Integrator 30 Style B MG30B OS1M3B4 6.1.10 3.32 6.5.6
Communication Processor 10 COMM10 OS1CS 6.5.1 2.20 7.1
1. These control processors have been withdrawn from sale. Comprehensive support services for these
products are limited to the Lifecycle Support Policy.
2. For the Allen-Bradley Integrator 30 Style B, the OS1A3B package includes two files: OS1A3B and
OS1A3B.186.
3. 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.
4. For the Modbus Integrator 30 Style B, the OS1M3B package includes two files: OS1M3B and
OS1M3B.186.
B.2 100 Series FBM Software and EEPROM Versions

Table B-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 the following table, dashes indicate that the revision is unchanged from the previ-
ous release. N/A indicates that the station or module is not available for that Control
Core Services or I/A Series software release.
158
Appendix B. EEPROM Revision Levels B0700SV – Rev F
Table B-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.3
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
159
Table B-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
160
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
161
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.
B.3 200 Series FBM Software and EEPROM Versions

Table B-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>
162
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 B-4 and Table B-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 B-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.3
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
163
Table B-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 or
later)
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)
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)
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)
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)
FBM220 (FOUNDATION IOM220 2.20 – – – – 2.20 2.20
fieldbus H1)
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
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
164
Software Version
V9.0-
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)
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)
Serial FDSI) (v9.0-
9.1)
1.35.1
(v9.2)
1.36.3
(v9.3)
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)
Ethernet FDSI) (v9.0-
9.1)
1.35.1
(v9.2)
1.36.3
(v9.3)
FBM234 (AEAM01) IOM234 1.25B – – – – 1.25B 1.25B
FBM235 (ASAM01) IOM235 1.25B – – – – 1.25B 1.25B
FBM236 (ASDM24, IOM236 1.25B – – – – 1.25B 1.25B
ASDM48)
FBM238 IOM78 N/A N/A N/A 1.40N 1.40N 1.40N 1.40N
(v9.0-
9.2)
1.41C
(v9.3+)
165
Software Version
V9.0-
(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)
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)
FBM247 IOM247 – – – – 2.42C 2.46J 2.46J
(v9.0)
2.47B
(v9.1-
v9.2)
2.50A
(v9.3)
FBM248 IOM248 – – – – – – 2.50A
(v9.3)
FBM250 (ISCM) IOM250 N/A 2.40 – – 2.40B 2.40B 2.50H
(v9.0-
9.1)
2.41C
(v9.2+)
Table B-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
166

(DIN Rail Mounted Form Factor) (Continued)

V9.0-
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
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 or
later)
FCM100E IOM210E 2.03 – 2.05 2.06 2.06 2.06 2.08
167


V9.0-
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)
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)
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)
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)
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)
FBM231 (Redundant Serial IOM231 0112 – 0113 – – 0114 0115
FDSI)
168


V9.0-
FBM232 (Simplex Ethernet IOM232 0112 – 0113 – – 0114 0115
FDSI)
FBM233 (Redundant Ether- IOM233 0112 – 0113 – – 0114 0115
net FDSI)
FBM234 (AEAM01) IOM234 1.25B – – – – – –
FBM235 (ASAM01) IOM235 1.25B – – – – – –
FBM236 (ASDM24, IOM236 1.25B – – – – – –
ASDM48)
(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)
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)
FBM247 IOM247 – – – – 2.42C 2.46J 2.46J
(v9.0)
2.47B
(v9.1-
v9.2)
2.50A
(v9.3)
FBM248 IOM248 – – – – – – 2.50A
(v9.3)
FBM250 (ISCM) IOM250 N/A 2.40 – – 2.40B 2.40B 2.50H
(v9.0-
9.1)
2.41C
(v9.2+)
169
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

b0700sv F PDF

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

b0700sv F PDF

Uploaded by

Copyright:

Available Formats

Foxboro Evo™

Process Automation System

Control Core Services v9.3

Copyright 2015-2018 Schneider Electric.

SOFTWARE LICENSE AND COPYRIGHT INFORMATION

2. Features of Control Core Services V9.3 Release................................................................. 9

3. V9.3 Upgrade Considerations.......................................................................................... 13

3.5.2 Control Core Services Interoperability and Compatibility ......................................... 18

4. V9.3 Hardware Requirements ......................................................................................... 23

5. V9.3 System Setup .......................................................................................................... 25

6. V9.3 Installation Overview.............................................................................................. 31

7. V9.3 Operational Recommendations............................................................................... 35

7.6.1 ia User Account ......................................................................................................... 51

7.17 Control Software ............................................................................................................. 66

7.24 Tools and Utilities ........................................................................................................... 94

8. V9.3 User Notes ............................................................................................................ 111

8.4.1 Device Monitor Master Active on Isolated Segments of

9. Customer Cases Resolved in V9.3 ................................................................................. 131

Appendix A. Files to Back Up/Restore............................................................................... 151

Appendix B. EEPROM Revision Levels............................................................................. 157

♦ Control Software v6.1 Release Notes (B0750SJ)

♦ FBM207/FBM207b/FBM207c – Channel-Isolated, Voltage Monitor/Contact Sense Input

1.1 Overview of the Control Core Services v9.3

1.2 Hardware Requirements

1.3 Domain Controllers

1.4 Operating System Image Installation

1.5 Control Core Services Security Enhancements

1.6 Control Core Services V9.3 Support for the

1.7 Site Upgrades

1.7.1 Migrating Files

1.7.2 Compound Summary Access (CSA)

1.8 Installation Overview

1.8.1 Installing the Foxboro Evo Control Core Services v9.3

3. When the installation is finished, click Finish.

1.8.2 Quick Fix 1287671 for Legacy Workstations and Servers

1.9 Migration Requirements

1.9.2 Migration of Domain Controller from I/A Series Software

1.10 Security Advisory for Adobe® Reader®

1.11 Foxboro Evo Product Rebranding

Table 1-1. Foxboro Evo Product Rebranding

Product Name for Foxboro Evo Process

2.1 Support for FBM248

2.2 Support for Field Device Controller 280

2.3 Additional Features for the Control Network

♦ Process Alarm messages sent via the APRINT mechanism. Acknowledgements

2.4 System Configuration Changes

2.4.1 Software Packages

Name Description Software

Table 2-2. Recommended Packages for On-Control Network Workstations

Station Operational Role Recommended Packages

If a package is not assigned, it will not be loaded onto the station.

3.1 Site Upgrade Plans

3.2 Control Software Support for Control Core

3.3 Supported Topologies and System Rules

3.4 System Configuration and Installation

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