b0700gq C

Foxboro Evo™
Process Automation System
Field Device Controller 280

(FDC280) User's Guide
*B0700GQ* *c*
B0700GQ
Rev C
December 17, 2018
Schneider Electric, Foxboro, Foxboro Evo, FoxView, and I/A Series are trademarks of Schneider Electric, its
subsidiaries, and affiliates.
All other brand names may be trademarks of their respective owners.
Copyright 2016 - 2018 Schneider Electric.

All rights reserved.
SOFTWARE LICENSE AND COPYRIGHT INFORMATION

Before using the Schneider Electric Systems USA, Inc. supplied software supported by this docu-
mentation, you should read and understand the following information concerning copyrighted
software.
1. The license provisions in the software license for your system govern your obligations
and usage rights to the software described in this documentation. If any portion of
those license provisions is violated, Schneider Electric Systems USA, Inc. will no lon-
ger provide you with support services and assumes no further responsibilities for your
system or its operation.
2. All software issued by Schneider Electric Systems USA, Inc. and copies of the software
that you are specifically permitted to make, are protected in accordance with Federal
copyright laws. It is illegal to make copies of any software media provided to you by
Schneider Electric Systems USA, Inc. for any purpose other than those purposes men-
tioned in the software license.
Contents
Figures.................................................................................................................................... ix
Tables.................................................................................................................................... xv
Preface................................................................................................................................. xvii
Who This Book Is For .......................................................................................................... xvii
What You Should Know ....................................................................................................... xvii
Revision Information ............................................................................................................ xvii
Reference Documents ............................................................................................................ xix
Glossary of Terms ................................................................................................................... xx
1. Introduction ...................................................................................................................... 1
Overview ................................................................................................................................... 1
Features ................................................................................................................................ 3
Functional and Environmental Constraints .......................................................................... 4
I/O Network Configuration ................................................................................................. 5
FDC280 .......................................................................................................................... 5
Ethernet Interfaces ........................................................................................................... 5
Serial Interfaces ................................................................................................................ 5
Summary of Communication Link Characteristics (Ethernet) ......................................... 5
Other Factors ....................................................................................................................... 6
Number of Devices and FDC280 Loading ...................................................................... 6
FDC280 Supported Protocol .................................................................................................... 6
FDC280 Functionality .............................................................................................................. 7
I/O Integration ..................................................................................................................... 7
Fault Tolerance Over the Foxboro Evo Control Network .................................................... 7
FDC280 Fault Tolerant Operation Over the Foxboro Evo Control Network ................. 7
Redundant vs. Fault Tolerant Systems Over the Foxboro Evo Control Network ............. 8
Self-Hosting and Non-Self-Hosting Modes .......................................................................... 8
Self-Hosting Feature ........................................................................................................ 9
Checkpoint Behavior in Self-Hosting FDC280 ............................................................... 9
Image Update ..................................................................................................................... 10
Major Image Update ..................................................................................................... 10
Minor Image Update ..................................................................................................... 10
FDC280 Identification ....................................................................................................... 10
Number of Self-Hosting or Auto-Checkpointing FDC280s Supported By a Boot Host ..... 11
FDC280 Network Configuration for the Foxboro Evo Control Network ............................... 11
Network Path Switching .................................................................................................... 13
FDC280 Ethernet Network Configurations for Supported Field Devices ............................... 13
i
B0700GQ – Rev C Contents
Simplex FDC280 to Ethernet Field Devices Configuration ................................................ 14

Fault-Tolerant FDC280 to Ethernet Field Devices over Separate Networks
Configuration ..................................................................................................................... 15
Fault-Tolerant FDC280 to Ethernet Field Devices over Common Networks
Configuration ..................................................................................................................... 17
Connecting to Single-Ported Field Devices .................................................................... 18
Connecting to Dual-Ported Field Devices ..................................................................... 18
Field Device-Level Redundancy ..................................................................................... 18
Fault-Tolerant FDC280s to Dual Ported and Single Ported Ethernet Field Devices over
Common Networks Configuration .................................................................................... 19
FDC280 Serial Network Configurations for Supported Field Devices .................................... 19
Simplex FDC280 to Serial Field Devices Configuration ..................................................... 20
Fault-Tolerant FDC280 to Serial Field Devices Configuration .......................................... 21
Time Synchronization ............................................................................................................. 23
Overview ............................................................................................................................ 23
Internal Source Time Synchronization .......................................................................... 23
External Source Time Synchronization .......................................................................... 23
FDC280 Sizing Constraints .................................................................................................... 24
2. Quick Start Guide ........................................................................................................... 25
3. Installing the Field Device Controller 280....................................................................... 29

Overview ................................................................................................................................. 29
System Definition .............................................................................................................. 29
Installing a Single or Primary FDC280 Module ...................................................................... 30
Maintaining EMC and CE Compliance For FDC280 Baseplates (European
Installations Only) .............................................................................................................. 36
Setting the Letterbug .......................................................................................................... 37
Manual Letterbug Assignment via LCD Display ............................................................ 37
Automatic Letterbug Assignment From Existing FDC280 ............................................ 39
Configuring the FDC280 Self-Hosting Option .................................................................. 39
Initializing the FDC280 with Self-Hosting Enabled ...................................................... 39
Disabling Self-Hosting .................................................................................................. 40
Verifying Self-Hosting Information Using Station Block Display .................................. 40
Auto-Checkpoint While Enabling/Disabling Self-Hosting ............................................ 41
Installing a Shadow FDC280 Module ..................................................................................... 42
Caution on Removing the FDC280 ........................................................................................ 43
Network Cabling for FDC280 Network Adapters ................................................................... 43
FDC280 Simplex Serial Termination Assembly Installation .................................................... 46
FDC280 Simplex Serial Termination Assembly Installation Instructions ........................... 47
FDC280 Simplex Serial Termination Assembly Cable Connections ................................... 47
RS-422 and RS-485 Cable Connections ............................................................................. 48
Connecting an RS-485 Device to the FDC280 Simplex Serial Termination Assembly ....... 50
RS-485 and RS-422 Cable Specifications ...................................................................... 52
Connecting an RS-422 Device to the FDC280 Simplex Serial TA ..................................... 52
ii
Contents B0700GQ – Rev C
TA Terminations For RS-422 or RS-485 ........................................................................... 54

RS-232 Cable Connections ................................................................................................ 56
Connecting an RS-232 Port to the TA ............................................................................... 57
RS-232 Cables ............................................................................................................... 57
FDC280 Simplex Serial TA RS-232 Switches .................................................................... 58
TA RS-232 Switch Settings ................................................................................................ 59
FDC280 Simplex Serial Termination Assembly RS-232 Switch Pinout .............................. 60
FDC280 Fault Tolerant Serial Termination Assembly Installation .......................................... 63
FDC280 Fault Tolerant Serial Termination Assemblies Installation ................................... 64
FDC280 Fault Tolerant Serial Termination Assembly Cable Connections ......................... 64
RS-422 and RS-485 Cable Connections ............................................................................. 65
Connecting an RS-485 Device to the FDC280 Fault Tolerant Serial TA ........................... 67
Connecting an RS-422 Device to the FDC280 Fault Tolerant Serial TA ........................... 70
TA Terminations For RS-422 or RS-485 ........................................................................... 73
RS-232 Cable Connections ................................................................................................ 77
Connecting an RS-232 Port to the TA ............................................................................... 78
Connecting a Single-Ported RS-232 Device to Fault Tolerant FDC280 ............................. 79
FDC280 Fault Tolerant Serial TA RS-232 Switches .......................................................... 79
TA RS-232 Switch Settings ................................................................................................ 80
FDC280 Fault Tolerant Serial Termination Assembly RS-232 Switch Pinout .................... 81
Boot-Up Sequence .................................................................................................................. 84
Case 1 – Rebooting a Commissioned FDC280 .................................................................. 85
Case 2 – Connecting an FDC280 with the Same Letterbug ............................................... 85
Case 3 – Connecting an FDC280 with a New Letterbug ................................................... 86
Case 4 – Connecting a Shadow Module with Same Software Image ................................... 86
Case 5 – Connecting a Shadow Module with Different Software Image ............................. 88
Case 6 – Powering Up FDC280 Baseplate with Fault Tolerant FDC280s With
Different Software Images .................................................................................................. 89
Case 7 – Powering Up FDC280 Baseplate with Fault Tolerant FDC280s with
Same Software Image ......................................................................................................... 89
Decommissioning an FDC280 Module .................................................................................. 89
4. Configuration Information.............................................................................................. 91
Overview ................................................................................................................................. 91
System Configuration ............................................................................................................. 91
System Configuration Procedure ........................................................................................ 92
Control/BPC Overrun Detection ....................................................................................... 92
Control Configuration ............................................................................................................ 92
Available Foxboro Evo System Control Blocks ................................................................... 96
Ethernet Primary ECB ....................................................................................................... 96
Serial Primary ECBs ........................................................................................................... 97
5. Control Block Configuration Information for I/O Functions.......................................... 99

ECBs and DCI Blocks Used with the FDC280’s Modbus Driver ........................................... 99
Configuration Procedures ....................................................................................................... 99
iii
Install FDC280 Drivers ...................................................................................................... 99

Import Driver Definition File .......................................................................................... 101
Configure FDC280 .......................................................................................................... 102
Configure FDC280’s Drivers ........................................................................................... 106
Creating and Editing the FDC280 ECB for Ethernet and Serial Drivers (ECB200) .... 109
Custom Parameters for Modbus ECB200 .................................................................... 110
Configure FDC280’s Field Device Objects ...................................................................... 111
Configuring Device ECB (ECB201) ................................................................................ 115
Configuring the Device Options Parameter ................................................................. 118
Configuring DCI Blocks .................................................................................................. 120
Distributed Control Interface (DCI Blocks) .......................................................................... 121
DCI Block Point Number Parameters .............................................................................. 121
Fail-safe Actions ............................................................................................................... 122
DCI Block Processing ...................................................................................................... 123
Key DCI Block Functions ................................................................................................ 124
Periodic/Change-Driven Execution ............................................................................. 124
Auto/Manual Mode Operation .................................................................................... 124
Simulation Mode ......................................................................................................... 124
Signal Conditioning and Linear Scaling ....................................................................... 124
Input Limiting ............................................................................................................. 124
Confirmed Outputs ..................................................................................................... 125
Output Clamping ........................................................................................................ 125
Output Initialization ................................................................................................... 125
Cascade Initialization ................................................................................................... 125
Redundant Input Selection .......................................................................................... 126
DCI Parameter Status Bits ........................................................................................... 126
6. Configuring FDC280 Using ICC and CCS FDC280 Configurator .............................. 127
Using ICC and ICC Driver Task Utility to Configure FDC280 ........................................... 127
Installing FDC280 Ethernet/Serial Port Drivers ............................................................... 128
Overview for Modbus TCP Client Driver Installation ................................................. 129
Overview for Modbus Serial Master Driver Installation ............................................... 129
Configuring Parameters in Station Block for FDC280 in ICC ......................................... 131
Configuring Ethernet Port ECB (ENET_PORT1) in ICC .............................................. 131
Configuring FDC280 Serial Port ECBs (SERIAL_PORT1-4) ......................................... 132
Configuring FDC280 Driver ECBs in ICC ...................................................................... 133
Configuring FDC280’s Field Devices in ICC ................................................................... 136
Configuring the Device Options Parameter ................................................................. 140
Commit Configuration Changes ...................................................................................... 142
Using ICC Driver Task .................................................................................................... 143
Recovery From Detected Error State Adding a Second ECB200 As a Child to An FDC280
Serial Port ............................................................................................................................. 147
CCS FDC280 Configurator .................................................................................................. 150
Installation of CCS FDC280 Configurator ...................................................................... 151
CCS FDC280 Configurator Layout ................................................................................. 153
Opening an FDC280 in CCS FDC280 Configurator ...................................................... 154
Configuring IP Addresses in CCS FDC280 Configurator ................................................ 156
iv
Configuring Device Options in CCS FDC280 Configurator ........................................... 157

Configuring Groups in a Device ....................................................................................... 157
Adding a New Group .................................................................................................. 158
Deleting/Undeleting a Group ...................................................................................... 158
Archiving a Configuration in CCS FDC280 Configurator ............................................... 159
Loading an Archived Configuration in CCS FDC280 Configurator ................................ 159
Loaded Configuration of the Same Letterbug .............................................................. 159
Loaded Configuration of a Different Letterbug ........................................................... 160
Letterbug of the Loaded Configuration is Not Hosted By the Workstation ................. 161
Deploying a Configuration .......................................................................................... 162
Modifying a Configuration Offline .................................................................................. 164
Troubleshooting the CCS FDC280 Configurator ............................................................ 166
7. Principles of Operation ................................................................................................. 169

Fault-Tolerant FDC280 Operation ....................................................................................... 169
Fault Tolerant FDC280 Operation With Devices On Multiple Ports .............................. 170
Fault Tolerant FDC280 Operation With Single Ported Devices ...................................... 170
Communication Through Primary FDC280 With Periodic Testing From Shadow
FDC280 ...................................................................................................................... 170
Confirming Shadow Connectivity To Device When Primary Connection Fails .......... 171
Support of Fault Tolerant FDC280 to Single-Ported Serial Device Configuration ........... 172
Single-Ported Device Interface Diagram ...................................................................... 172
Single Port Configuration ............................................................................................ 174
Multiple Driver Instance Support ......................................................................................... 174
Serial Ports Loopback Test .................................................................................................... 175
8. FDC280 Security Guidelines......................................................................................... 177

Overview of FDC280 Security Guidelines ............................................................................ 177
General Security Considerations ........................................................................................... 180
Operating Environment ................................................................................................... 180
Basic Security Functions ........................................................................................................ 180
Data Format ..................................................................................................................... 180
Active Directory ............................................................................................................... 180
Environments ................................................................................................................... 180
Ethernet Switch Access ................................................................................................ 182
9. System Management ..................................................................................................... 183

Overview ............................................................................................................................... 183
Operating Status ................................................................................................................... 183
System Manager Displays for the FDC280 ........................................................................... 184
10. Process Operator Displays........................................................................................... 187

Block Detail Displays ............................................................................................................ 187
FDC280 Station Block Detail Display ............................................................................. 188
v
FDC280 Station Compound Block Detail Display .......................................................... 190

FDC280 Ethernet Port Primary ECB Detail Display ....................................................... 191
FDC280 Serial Port Primary ECB Detail Display ............................................................ 192
FDC280 Driver ECB200 Detail Display .......................................................................... 194
ECB200 (FDC280 for Ethernet) Primary Data ........................................................... 196
FDC280 Field Device ECB201 Detail Display ................................................................ 196
ECB201 (Field Device) Primary Data ......................................................................... 199
11. Maintenance and Control Software Equipment Information ...................................... 201

Overview ............................................................................................................................... 201
System Management Displays ............................................................................................... 201
FDC280 Equipment Status and Information Display ........................................................... 202
FDC280 Equipment Change Actions ............................................................................... 206
FDC280 Ethernet Port Equipment Status and Information Display ..................................... 207
FDC280 Ethernet Port Equipment Change Actions ........................................................ 210
FDC280 Driver for Ethernet and Serial (ECB200) Equipment Status and Information
Display .................................................................................................................................. 211
FDC280 Driver Equipment Change Actions ................................................................... 214
FDC280 Serial Port Equipment Status and Information Display .......................................... 215
FDC280 Serial Port Equipment Change Actions ............................................................. 218
Device Equipment Status and Information Display (Field Device - ECB201) ....................... 219
Device Equipment Change Actions .................................................................................. 220
Service and Support .............................................................................................................. 221
12. Troubleshooting FDC280 Hardware .......................................................................... 223

Overview ............................................................................................................................... 223
FDC280 LCD, LED Indicators, and Reset Button ............................................................... 223
Liquid Crystal Display (LCD) .......................................................................................... 224
Start-up Diagnostic Display ......................................................................................... 225
Default Operational Display ........................................................................................ 225
Detected Error Displays ............................................................................................... 226
LED Indicators ................................................................................................................ 226
Operational Status LED Indicators .................................................................................. 227
Types of Resets ................................................................................................................. 228
FDC280 Troubleshooting ..................................................................................................... 228
Using the Operational Status LEDs .................................................................................. 229
Red off, Green off ........................................................................................................ 229
Red on, Green off ........................................................................................................ 230
Red on, Green on ........................................................................................................ 231
Cycling Red, Red/Green .............................................................................................. 231
Red off, Green on ........................................................................................................ 232
Fault Tolerant FDC280 Troubleshooting Addenda ......................................................... 232
Replacing an FDC280 Which is Not Working ............................................................ 233
Available Detected Memory Error Messages ..................................................................... 233
vi
Exceeding Allowable Object Manager (OM) Updates/Second .......................................... 234

E43 Detected Error Generated During FDC280 Deployment ......................................... 234
FDC280 Switchover Changes IDLE Time ....................................................................... 234
FDC280’s OM Scanner ........................................................................................................ 236
Memory Dumps ................................................................................................................... 236
FDC280 Diagnostics ............................................................................................................ 239
Start-Up Diagnostics ........................................................................................................ 239
Detected Error Recovery Local Diagnostics ...................................................................... 239
Detected Error Recovery Cooperative Diagnostics ............................................................ 239
FDC280 Diagnostics ........................................................................................................ 240
Network Adapter LED Indicators ......................................................................................... 240
13. Troubleshooting FDC280 Ports.................................................................................. 243

FDC280 Ethernet I/O Port in Offline State .......................................................................... 243
Ethernet and Serial Port Counters and Device Diagnostic Blocks ......................................... 243
Resetting Port Counters ................................................................................................... 243
Serial Port Parameters .................................................................................................. 244
Other Diagnostic Information .......................................................................................... 245
Reset Counters ................................................................................................................. 246
Response Timeout Counter .............................................................................................. 247
Worst Response Time ...................................................................................................... 247
Good Messages Sent ......................................................................................................... 248
Good Messages Received .................................................................................................. 248
Modbus Device Exception Responses ............................................................................... 248
Modbus Gateway Exception Responses (Ethernet Only) .................................................. 249
Last Detected Error Message ............................................................................................ 249
Over Scan Time High ...................................................................................................... 250
Number of Over Scans ..................................................................................................... 250
Configured Options ......................................................................................................... 251
Group Scan Time ............................................................................................................. 251
OverScan Condition ............................................................................................................. 252
Appendix A. Major Image Update and Minor Image Update ............................................ 253
Introduction .......................................................................................................................... 253
Overview .......................................................................................................................... 253
Image Update Terms and Concepts ................................................................................. 254
Determining Whether a Major or Minor Image Update Is Needed ....................................... 259
Determining Whether to Use Manual or Auto Mode for Image Update ............................... 260
Process Control Considerations ............................................................................................. 261
Minor Image Update for Married Stations ....................................................................... 261
Major Image Update or Minor Image Update for Unmarried Stations ............................. 261
General Block Processing Considerations .................................................................... 261
Additional Process Control Considerations Due to New FDC280 Image ......................... 263
Performing an FDC280 Image Update ................................................................................. 263
vii
Updating a Non-Fault-Tolerant FDC280 ........................................................................ 265

Major Image Update for Non-Fault-Tolerant FDC280 ............................................... 265
Updating a Fault-Tolerant FDC280 ................................................................................ 266
Minor Image Update for Married Stations .................................................................. 266
Minor Image Update For Unmarried Stations ............................................................. 268
Major Image Update for a Fault-Tolerant FDC280 ..................................................... 269
If Image Update Attempted With Same Image ................................................................. 272
Appendix B. Improving Performance of the CCS FDC280 Configurator on Stations with

Enterprise Edition Control Core Services v9.3 or Later ..................................................... 275
Appendix C. Upgrading / Usage with FDC280 Released 090009000 Image..................... 281

Notice for Configurations with Single-Ported Serial Devices ................................................. 281
Appendix D. FDC280 Debug Driver and FDC280 I/O Diagnostic Tool ......................... 283
Configuring the FDC280 Debug Driver via Control Software .............................................. 285
Configuring the FDC280 Debug Driver via ICC .................................................................. 293
FDC280 I/O Diagnostic Tool Installation ............................................................................ 299
Using the FDC280 I/O Diagnostic Tool .............................................................................. 303
Appendix E. Interfacing Fault-Tolerant FDC280 to M580 PLC HSBY............................ 313

Overview of Interfacing Fault-Tolerant FDC280 to M580 PLC HSBY ................................ 314
Redundant IO Network for Communications Between Systems ........................................... 314
Hot Standby M580 ............................................................................................................... 314
Appendix F. FDC280 System Monitor Log (smon_log) Messages..................................... 317
Index .................................................................................................................................. 321
viii
Figures
1-1. Simplex and Fault-Tolerant FDC280s in Baseplate ....................................................... 2
1-2. Fault-Tolerant FDC280s and Network Adapters in FDC280 Baseplate ........................ 2
1-3. Multiple FDC280s in The Foxboro Evo Control Network (Simplified) ..................... 12
1-4. Simplex (Single) FDC280 to Ethernet Field Devices Configuration ............................ 14
1-5. Fault-Tolerant FDC280s to Ethernet Field Devices in Separate Networks
Configuration ............................................................................................................. 15
1-6. Fault-Tolerant FDC280s to Ethernet Field Devices in Common Network
Configuration ............................................................................................................. 17
1-7. Fault-Tolerant FDC280s Interfacing to Single Ported and Dual Ported Ethernet
Devices ........................................................................................................................ 19
1-8. FDC280 Simplex in Typical Serial Network Configurations ....................................... 20
1-9. Fault-Tolerant FDC280 to Dual-Ported Serial Devices in Typical Network
Configurations ............................................................................................................ 21
1-10. Fault-Tolerant FDC280 to Single-Ported Serial Devices in Typical Configurations .... 22
3-1. FDC280 Module Installation (Typical) ...................................................................... 30
3-2. Example Network Adapters (Fiber) in FDC280 Baseplate (Do Not Connect Their
Cables At This Time) .................................................................................................. 34
3-3. Ferrite Core, Typical ................................................................................................... 36
3-4. Ferrite Cores Installed On FDC280 Baseplate Input Power Cables ............................. 37
3-5. FDC280 Faceplate Buttons and Liquid Crystal Display (LCD) .................................. 38
3-6. Initializing a Self-Hosting FDC280 ............................................................................ 40
3-7. Self-Hosting Status via Station Block Display ............................................................. 41
3-8. Recommended Fiber Adapter Module Switch Connections ........................................ 44
3-9. Fiber and Copper Adapter’s Network Ports ................................................................. 45
3-10. FDC280 Baseplate and Network Adapters Connected
(Fiber Adapters Shown - Example Rendering Only) .................................................... 46
3-11. RH926GH Termination Assembly ............................................................................. 47
3-12. FDC280 Simplex Serial Termination Assembly .......................................................... 48
3-13. FDC280 Simplex Serial Termination Assembly Labels for RS-422 and RS-485 .......... 49
3-14. RS-485 (2-wire) Non-redundant Device Connection .................................................. 50
3-15. RS-485 (2-wire) TA Cable Connections, FDC280 Located Mid Bus .......................... 51
3-16. RS-485 (2-wire) TA Cable Connections, FDC280 Located at Bus End Point ............. 52
3-17. RS-422 Non-redundant Connection ........................................................................... 53
3-18. RS-422 TA Cable Connections ................................................................................... 54
3-19. RS-485 (2-wire) Termination Resistor ........................................................................ 55
3-20. RS-422 Termination Resistor ...................................................................................... 55
3-21. Compression Screw TA RS-422 and RS-485 Termination Switches ........................... 56
3-22. Ring-Lug TA RS-422 and RS-485 Termination Switches ........................................... 56
3-23. RS-232 FDC280 Direct Cabling Configuration, Example .......................................... 57
3-24. RH970WX/WY/XC/XD RS-232 Cables .................................................................... 58
3-25. FDC280 Simplex Serial TA RS-232 Switches ............................................................. 59
3-26. RS-232 TA Switches ................................................................................................... 61
3-27. RS-232 Switches, Null Modem - Standard Handshake ............................................... 62
3-28. RS-232 Switches, Null Modem - No Handshake ........................................................ 62
ix
B0700GQ – Rev C Figures
3-29. RS-232 Switches, Modem Connection (Typical) ........................................................ 63

3-30. FDC280 Fault Tolerant Serial Port Termination Assemblies ...................................... 64
3-31. FDC280 Fault Tolerant Serial Termination Assembly (One Shown) .......................... 65
3-32. FDC280 Fault Tolerant Serial Termination Assembly Label (One Shown) for
RS-422 and RS-485 .................................................................................................... 66
3-33. RS-485 (2-wire) Fault Tolerant FDC280 to Dual-Ported Devices Connection ........... 67
3-34. RS-485 (2-wire) Fault Tolerant FDC280 to Single-Ported Devices Connection ......... 68
3-35. RS-485 (2-wire) TA Cable Connections (One Shown), FDC280 Located Mid Bus .... 69
3-36. RS-485 (2-wire) TA Cable Connections (One Shown),
FDC280 Located at Bus End Point ............................................................................. 70
3-37. RS-422 (4-Wire) Fault Tolerant FDC280 to Dual-Ported Device Connections .......... 71
3-38. RS-422 (4-Wire) Fault Tolerant FDC280 to Single-Ported Device Connections ........ 71
3-39. RS-422 TA Cable Connections (One Channel Shown) ............................................... 72
3-40. RS-485 (2-wire) Termination Resistor for Fault-Tolerant FDC280 to
Dual-Ported Device .................................................................................................... 73
3-41. RS-485 (2-wire) Termination Resistor for Fault-Tolerant FDC280 to
Single-Ported Device ................................................................................................... 74
3-42. RS-422 Termination Resistors for Fault-Tolerant FDC280 Connected to
Dual-Ported Device .................................................................................................... 75
3-43. RS-422 Termination Resistors for Fault-Tolerant FDC280 Connected to
Single-Ported Device ................................................................................................... 76
3-44. Compression Screw TA RS-422 and RS-485 Termination Switches ........................... 77
3-45. Ring-Lug TA RS-422 and RS-485 Termination Switches ........................................... 77
3-46. RS-232 FDC280 Redundant Cabling Configuration, Example .................................. 78
3-47. RS-232 FDC280 Redundant Cabling Configuration, Example .................................. 79
3-48. FDC280 Fault Tolerant Serial TA RS-232 Switches ................................................... 80
3-49. RS-232 TA Switches ................................................................................................... 82
3-50. RS-232 Switches, Null Modem - Standard Handshake ............................................... 83
3-51. RS-232 Switches, Null Modem - No Handshake ........................................................ 83
3-52. RS-232 Switches, Modem Connection (Typical) ........................................................ 84
4-1. Receive Message Did Not Succeed for Object V071FD_S2 ........................................ 94
5-1. FDC280 Modbus TCP Driver - Installation Summary ............................................. 100
5-2. FDC280 Modbus Serial Driver - Installation Summary ............................................ 100
5-3. Import FDC Driver Dialog Box ................................................................................ 101
5-4. Station Block - RDALGO Parameter - FDC280 Control Processors ......................... 103
5-5. ENET_PORT1 Tab, Configuration Subtab for an ECB Compound - FDC280
Control Processors .................................................................................................... 104
5-6. SERIAL_PORT1 Tab, Configuration Subtab for an ECB Compound - FDC280
Control Processors .................................................................................................... 105
5-7. Create New Driver from the FDC280’s Ethernet Port .............................................. 106
5-8. Bulk Create New FDC280 Driver ............................................................................ 107
5-9. Control Editors for the FDC280 Driver ................................................................... 108
5-10. ECB Tab for an ECB Compound - [FDC280].ECB200 Driver Subtab .................... 108
5-11. Create New Field Device Object Individually ........................................................... 111
5-12. Bulk Create New Field Device Objects ..................................................................... 112
5-13. Control Editors for the Field Device Object .............................................................. 113
5-14. Hardware Editor - Groups Tab ................................................................................. 113
6-1. ECBs of FDC280’s Ethernet Port and Four Serial Ports in ICC ............................... 128
x
Figures B0700GQ – Rev C
6-2. FDC280 Modbus TCP Driver Installation ............................................................... 129

6-3. FDC280 Modbus Serial Driver Installation .............................................................. 130
6-4. Setting the Value of RDALGO in STATION Block in ICC ..................................... 131
6-5. Parameters of Ethernet Port ECB in ICC .................................................................. 132
6-6. Parameters of Serial Port ECB in ICC ....................................................................... 133
6-7. Ethernet Port Driver Configuration Data in ICC ...................................................... 134
6-8. Serial Port Driver Configuration Data in ICC .......................................................... 135
6-9. Ethernet Device Configuration Data in ICC ............................................................. 139
6-10. Serial Device Configuration Data in ICC .................................................................. 139
6-11. Example of Using iccdrvr.tsk.exe ............................................................................... 143
6-12. System Message - Insufficient FBM Memory/Connections ....................................... 148
6-13. System Message - E16 - Compound or Block Not Found ......................................... 149
6-14. System Message - ECB Configuration File Not Identified ......................................... 150
6-15. Invocation of CCS FDC280 Configurator in FoxView ............................................. 151
6-16. Startup View of CCS FDC280 Configurator ............................................................ 152
6-17. System Message When Starting an Additional CCS FDC280 Configurator Instance 152
6-18. Active CCS FDC280 Configurator Instance in the Taskbar ...................................... 152
6-19. CCS FDC280 Configurator Layout .......................................................................... 153
6-20. List of FDC280s Hosted by the Workstation ............................................................ 154
6-21. Example of an Unreachable FDC280 ........................................................................ 155
6-22. Configuration Activity Flow Diagram for CCS FDC280 Configurator ..................... 156
6-23. IP Address Configuration Data for Fault-Tolerant FDC280 ..................................... 156
6-24. Device Options in Options Field in Device Configuration Panel .............................. 157
6-25. Group Command Buttons and Group Counter ........................................................ 158
6-26. Configuration File and FDC280 is Out Of Sync ...................................................... 160
6-27. System Message Notification of Archiving Before Closing ........................................ 161
6-28. Configuration Belongs to an FDC That Is Not Hosted By the Workstation ............. 161
6-29. Only Selected Items Are Deployed in CCS FDC280 Configurator ........................... 162
6-30. Access the “Go Off-Line…” Command in System Manager ..................................... 163
6-31. Filename Saved in Parameter FILEID in ICC ........................................................... 164
6-32. Location of Fields in a Configuration File ................................................................. 165
7-1. RS-232 Single-Ported Device Connections ............................................................... 173
7-2. RS-485/422 Single-Ported Device Connections ........................................................ 173
8-1. System Trust Boundary ............................................................................................. 178
8-2. User Profiles in Active Directory Users and Computers ............................................ 181
10-1. FDC280 Station Block Detail Display ...................................................................... 188
10-2. FDC280 Compound Block Detail Display ............................................................... 190
10-3. FDC280 Ethernet Port Primary ECB Detail Display ................................................ 191
10-4. FDC280 Serial Port Primary ECB Detail Display - Part 1 ........................................ 192
10-5. FDC280 Serial Port Primary ECB Detail Display - Part 2 ........................................ 193
10-6. ECB200 (FDC280 Driver) Block Detail Display - First Page ................................... 194
10-7. ECB200 (FDC280 Driver) Block Detail Display - Second Page ............................... 194
10-8. ECB200 (FDC280 Driver) Block Detail Display - Third Page ................................. 195
10-9. ECB201 (Field Device) Block Detail Display - First Page ......................................... 196
10-10. ECB201 (Field Device) Block Detail Display - Second Page ..................................... 197
10-11. ECB201 (Field Device) Block Detail Display - Third Page ....................................... 197
11-1. FDC280 System Manager Display ............................................................................ 202
11-2. FDC280 Equipment Change Actions ....................................................................... 206
xi
11-3. Fault-Tolerant FDC280’s Ethernet Port Equipment Information

Display – Typical ...................................................................................................... 207
11-4. Non-Fault-Tolerant FDC280’s Ethernet Port Equipment Information
Display – Typical ...................................................................................................... 207
11-5. FDC280 Ethernet Port Equipment Change Actions ................................................. 210
11-6. FDC280 Driver for Ethernet (ECB200) Equipment Information
Display – Typical ...................................................................................................... 211
11-7. FDC280 Driver for Serial (ECB200) Equipment Information Display – Typical ..... 212
11-8. FDC280 Driver Equipment Change Actions ............................................................ 214
11-9. Fault-Tolerant FDC280’s Serial Port Equipment Information Display – Typical ..... 215
11-10. Non-Fault-Tolerant FDC280’s Serial Port Equipment Information
Display – Typical ...................................................................................................... 215
11-11. FDC280 Serial Port Equipment Change Actions ...................................................... 218
11-12. Device Equipment Information Display (ECB201) / FDC280 Field Device
(FDC_Device) – Typical ........................................................................................... 219
11-13. Device Equipment Change Display ........................................................................... 221
12-1. FDC280 LED Indicators and Reset Button .............................................................. 224
12-2. FDC280 Core 1 and Core 2 Idle Metrics in FoxView ............................................... 235
12-3. Copper and Fiber Adapter LED Indicators ............................................................... 240
A-1. Image Update Overview ............................................................................................ 254
A-2. Image Revision and Image Revision Mismatch Fields in System Manager ................. 258
A-3. Determining Whether a Major or Minor Image Update Is Needed ........................... 259
A-4. System Manager Equipment Change Display ............................................................ 264
A-5. Minor Image Update Dialog Box .............................................................................. 267
A-6. Major Image Update Dialog Box .............................................................................. 270
B-1. Accessing Group Policy Management Application .................................................... 276
B-2. Group Policy Management - Accessing Group Policy Objects .................................. 277
B-3. Group Policy Management - Accessing Invensys IA Computers v2.0 - Edit... ........... 277
B-4. Group Policy Management - Accessing Public Key Policies ....................................... 278
B-5. Group Policy Management - Accessing Certificate Path Validation Settings ............. 278
B-6. Certificate Path Validation Settings Properties - Network Retrieval Tab ................... 279
B-7. Certificate Path Validation Settings Properties - Default Retrieval Timeout Settings . 279
D-1. FDC280 Debug Driver and FDC280 I/O Diagnostic Tool ...................................... 284
D-2. FDC280 Debug Driver - New Driver... Menu Item ................................................. 285
D-3. FDC280 Debug Driver - Bulk Create Dialog ............................................................ 286
D-4. FDC280 Debug Driver - Diagnostic Driver in Network view ................................... 287
D-5. FDC280 Debug Driver - Related ECB… Menu Item ............................................... 288
D-6. FDC280 Debug Driver - Driver Editor .................................................................... 289
D-7. FDC280 Debug Driver - Deploy Menu Item ........................................................... 290
D-8. Select Objects for Deployment (Step 1 of 4) Dialog Box ........................................... 291
D-9. System Manager - Put the Driver You Configured On-Line ...................................... 292
D-10. ICC - Select Vol ........................................................................................................ 293
D-11. ICC - Select Edit Station ........................................................................................... 294
D-12. ICC - Select FDC280 Module .................................................................................. 295
D-13. ICC - View Blocks/ECBs in this Compound ............................................................ 296
D-14. ICC - Insert New Block/ECB ................................................................................... 297
D-15. ICC - Configuring the Log Driver (LOGDRV) ........................................................ 298
D-16. System Manager - Put the Driver You Configured On-Line ...................................... 299
xii
Figures B0700GQ – Rev C
D-17. Invoke FDC280 I/O Diagnostic Tool Installer ......................................................... 299

D-18. FDC280 I/O Diagnostic Tool Setup - License Terms and Conditions ...................... 300
D-19. FDC280 I/O Diagnostic Tool Setup - Install Compatible Version of
Microsoft .NET Framework ...................................................................................... 300
D-20. FDC280 I/O Diagnostic Tool Setup - End-User License Agreement ........................ 301
D-21. FDC280 I/O Diagnostic Tool Setup - Welcome to the Tool Setup Wizard .............. 302
D-22. FDC280 I/O Diagnostic Tool Setup - Destination Folder ........................................ 303
D-23. Starting the FDC280 I/O Diagnostic Tool ............................................................... 303
D-24. FDC280 I/O Diagnostic Tool - Options .................................................................. 304
D-25. FDC280 I/O Diagnostic Tool - Configuration Options Dialog Box ......................... 305
D-26. FDC280 I/O Diagnostic Tool - Start Log ................................................................. 305
D-27. FDC280 I/O Diagnostic Tool - Connect Button ...................................................... 306
D-28. FDC280 I/O Diagnostic Tool - Runtime Data ......................................................... 307
D-29. FDC280 I/O Diagnostic Tool - Missed Messages ..................................................... 307
D-30. FDC280 I/O Diagnostic Tool - Packet Info Tab ...................................................... 308
D-31. FDC280 I/O Diagnostic Tool - Chop Log ............................................................... 309
D-32. FDC280 I/O Diagnostic Tool - Pause Display Button .............................................. 310
D-33. FDC280 I/O Diagnostic Tool - Clear All Button ..................................................... 310
D-34. FDC280 I/O Diagnostic Tool - Open Log ............................................................... 311
D-35. FDC280 I/O Diagnostic Tool - Re-Display Log Data .............................................. 311
D-36. FDC280 I/O Diagnostic Tool - Two Instances Listening to the Appropriate
Ports on the Primary and Secondary FDC280 Modules ............................................ 312
E-1. Interfacing FDC280 FT to M580 PLC HSBY with No Single Point Capable Of
Taking Down the System .......................................................................................... 313
xiii
xiv
Tables
1-1. Supported FDC280 Serial Port Termination Assemblies ............................................... 5
1-2. Communication Link Characteristics ............................................................................ 5
1-3. Communication Link Characteristics for Serial I/O ...................................................... 6
3-1. Baseplate and Mounting Positions for FDC280 Modules ........................................... 32
3-2. Termination Cables (Type 5) for the FDC280 Serial Termination Assemblies ............ 47
3-3. RS-485 and RS-422 Cable Specifications .................................................................... 52
3-4. RS-232 Communication Cables .................................................................................. 58
3-5. Serial Port Adapter Pin Connections ........................................................................... 59
3-6. Termination Cables (Type 5) for FDC280 Fault Tolerant Serial Installations ............. 64
3-7. RS-232 Communication Cables, Single Ported Device to Two TAs (Fault Tolerant
FDC280) .................................................................................................................... 78
3-8. Serial Port Adapter Pin Connections ........................................................................... 80
4-1. New STATION Parameters for FDC280 ................................................................... 96
5-1. ECB200 Key Parameters/Values for FDC280 ........................................................... 109
5-2. ECB201 Key Parameters for Devices ......................................................................... 115
5-3. DCI Block Point Number Parameters Requiring a Data Identifier ............................ 121
5-4. DCI Parameter Status ............................................................................................... 126
6-1. ECB201 Key Parameters for Devices for ICC Configuration .................................... 136
6-2. Figure 6-19 - CCS FDC280 Configurator Layout Legend ........................................ 153
6-3. Figure 6-26 Configuration File and FDC280 is Out Of Sync Legend ....................... 160
6-4. Figure 6-32 - Location of Fields in a Configuration File Legend ............................... 165
6-5. Troubleshooting the CCS FDC280 Configurator ..................................................... 166
9-1. Equipment Information Display for FDC280 Field Device Statuses After Parent
Driver Is Turned Online ........................................................................................... 184
10-1. FDC280 Station Block Detail Display Field Descriptions ......................................... 188
10-2. FDC280 Compound Block Detail Display Field Descriptions .................................. 190
10-3. FDC280 Ethernet Port Primary ECB Detail Display Field Descriptions ................... 191
10-4. FDC280 Serial Port Primary ECB Detail Display Field Descriptions ........................ 193
10-5. FDC280 Driver ECB200 Detail Display Field Descriptions ..................................... 195
10-6. FDC280 Field Device ECB201 Detail Display Field Descriptions ............................ 198
11-1. FDC280 Equipment Status and Information Display Fields ..................................... 203
11-3. FDC280 Ethernet Port Equipment Status and Information Display Fields ............... 208
11-5. FDC280 Driver for Ethernet or Serial (ECB200) Equipment Status and Information
Display Fields ............................................................................................................ 212
11-6. FDC280 Driver (ECB200) Equipment Change Actions ........................................... 214
11-7. FDC280 Serial Port Equipment Status and Information Display Fields .................... 215
11-8. FDC280 Serial Port Equipment Change Actions ...................................................... 218
11-9. Device Equipment Information Display Fields (Field Devices - ECB201) ................ 219
11-10. Device ECB201 Equipment Change Actions ............................................................ 221
12-1. FDC280 LED Indicators and Reset Button .............................................................. 226
12-2. FDC280 Operational Status LEDs ........................................................................... 227
12-3. Network Adapter LED Indicators ............................................................................. 241
xv
B0700GQ – Rev C Tables
13-1. Counters Display for Ethernet Port Counters For FDC280 ...................................... 244
13-2. Counters Display for Serial Port Counters For FDC280 ........................................... 244
13-3. Ethernet/Serial Device Diagnostic Blocks .................................................................. 245
A-1. Image Update Terms and Concepts .......................................................................... 254
A-2. Example Major and Minor Update Scenarios ............................................................ 259
A-3. Determine Whether to Use Manual or Auto Mode for Image Update ...................... 260
E-1. Figure E-1 - Interfacing FDC280 FT to M580 PLC HSBY Legend .......................... 314
F-1. FDC280 Detected Configuration smon_log Errors ................................................... 317
F-2. FDC280 Runtime smon_log Messages ..................................................................... 319
xvi
Preface
This document describes how to configure and install the Field Device Controller 280 (FDC280)
in a Foxboro Evo™ Process Automation System with the Foxboro Evo Control Network (herein-
after referred to as the control network). It also describes how the FDC280 functions in the con-
trol network. Finally, it describes how to troubleshoot system problems.
Who This Book Is For

This book is written for process control engineers and process operators, instrument and mainte-
nance engineers, and other qualified and authorized personnel involved in installing, configuring
and maintaining the FDC280 for operation in the control network.
What You Should Know

Prior to using this book, you should be generally familiar with the Foxboro Evo system, with the
Control Core Services software, and with Standard and Compact 200 Series Subsystem User’s Guide
(B0400FA). Detailed information relating to the various Foxboro Evo Control Core Services soft-
ware and Foxboro Evo system hardware elements is found in the reference documents listed
below.
Revision Information
For this revision of this document (B0700GQ, Rev. C), these changes were made:
Global
♦ Updated the document to implement new corporate and product branding.
♦ Rewrote all safety messages.
♦ Updated terminology to meet safety standards.
Chapter 1 “Introduction”
♦ Updated Figure 1-2 and Figure 1-3.
♦ Added serial port support to “Overview” on page 1 and “I/O Integration” on page 7.
♦ Added “Serial Interfaces” on page 5 and Table 1-3.
♦ Added “FDC280 Serial Network Configurations for Supported Field Devices” on
page 19.
Chapter 2 “Quick Start Guide”
♦ Moved steps from the Quick Start Example in FDC280 Modbus Master Drivers (Serial
and TCP/IP) (B0700GT) into this chapter.
Chapter 3 “Installing the Field Device Controller 280”
♦ Added “Caution on Removing the FDC280” on page 43, “FDC280 Simplex Serial
Termination Assembly Installation” on page 46, and “FDC280 Fault Tolerant Serial
Termination Assembly Installation” on page 63.
xvii
B0700GQ – Rev C Preface
Chapter 4 “Configuration Information”

♦ Updated the definition of TDVCNT in Table 4-1.
♦ Added serial port information and a note about undeploying blocks to “Control Con-
figuration” on page 92.
♦ Added “Control/BPC Overrun Detection” on page 92.
♦ Added “Ethernet Primary ECB” on page 96 and “Serial Primary ECBs” on page 97.
Chapter 5 “Control Block Configuration Information for I/O Functions”
♦ Moved this chapter from FDC280 Modbus Master Drivers (Serial and TCP/IP)
(B0700GT) into this book.
♦ Added “Options Applicable to Serial Ports Only” on page 120.
Chapter 6 “Configuring FDC280 Using ICC and CCS FDC280 Configurator”
♦ Added this chapter.
Chapter 7 “Principles of Operation”
♦ Added “Fault Tolerant FDC280 Operation With Devices On Multiple Ports” on
page 170, “Fault Tolerant FDC280 Operation With Single Ported Devices” on
page 170, “Multiple Driver Instance Support” on page 174, and “Serial Ports Loop-
back Test” on page 175.
Chapter 10 “Process Operator Displays”
♦ Added “FDC280 Serial Port Primary ECB Detail Display” on page 192.
Chapter 11 “Maintenance and Control Software Equipment Information”
Chapter 13 “Troubleshooting FDC280 Ports”
♦ Added this chapter.
Appendix A “Major Image Update and Minor Image Update”
♦ Updated “Minor Image Update for Married Stations” on page 266.
Appendix B “Improving Performance of the CCS FDC280 Configurator on Stations with
Enterprise Edition Control Core Services v9.3 or Later”
♦ Added this appendix.
Appendix C “Upgrading / Usage with FDC280 Released 090009000 Image”
Appendix D “FDC280 Debug Driver and FDC280 I/O Diagnostic Tool”
Appendix E “Interfacing Fault-Tolerant FDC280 to M580 PLC HSBY”
xviii
Preface B0700GQ – Rev C
Reference Documents
The following documents provide additional and related information.
For information about using the FDC280 with the protocols and field devices it supports:
♦ FDC280 Modbus Master Drivers (Serial and TCP/IP) (B0700GT)
For information about defining control blocks and compounds, refer to:
♦Integrated Control Block Descriptions (B0193AX)
♦ Integrated Control Software Concepts for CP270, FCP280, and FDC280 (B0700AG)
For information about configuring and managing the FDC280, refer to:
♦ Field Device Controller 280 (FDC280) Sizing Guidelines and Excel Workbook
(B0700GS)
♦ System Definition: A Step-by-Step Procedure (B0193WQ)
♦ System Manager (B0750AP)
♦ Block Configurator User's Guide (B0750AH)
♦ Hardware Configuration User’s Guide (B0750BB)
♦ Process Operations and Displays (B0700BN)
♦ Security Guidelines For ISASecure™ Certified Products (B0700GH)
For information about mounting and powering the FDC280 baseplate, refer to:
♦ Standard and Compact 200 Series Subsystem User’s Guide (B0400FA).
For information about system power and earthing (grounding), refer to:
♦ Power, Earthing (Grounding), EMC and CE Compliance (B0700AU)
For information about the Foxboro Evo Control Network, refer to:
♦ The Foxboro Evo Control Network Architecture Guide (B0700AZ)
For information about virtual machines used to host the FDC280, refer to:
♦ Virtualization User’s Guide (B0700VM)
For information about software security for the FDC280 and its host, refer to:
♦ Security Implementation User's Guide for I/A Series and Foxboro Evo Workstations (Win-
dows 10 or Windows Server 2016 Operating Systems) (B0700HG)
For information about the RemoteWatch Server installation and network security, refer to:
♦ RemoteWatch Server C20 Style B Software V5.0 Installation Guide (B0860BX)
♦ RemoteWatch Server V5.1.3 Upgrade Guide (B0860BR)
♦ RemoteWatch V5.1.3 Release Notes (B0860RS)
♦ RemoteWatch V5.1.3 User's Guide (B0860CR)
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.
xix
Glossary of Terms
The following terminology, used throughout this user’s guide, relates to the FDC280 and associ-
ated equipment.
Name Meaning
ARP Address Resolution Protocol - used by the Internet Protocol (IP)
[RFC826], specifically IPv4, to map IP network addresses to the hard-
ware addresses used by a data link protocol
BPC Block Processing Cycle
Checkpoint File The Control Database, that resides on the host workstation, which is
downloaded to the FDC280.
Commissioned A commissioned control processor is a control processor for which all
the steps required to place the device into service have been performed.
This includes:
♦ Connecting to the baseplate and power
♦ Setting the letterbug
♦ Connecting to the Foxboro Evo Control Network
♦ Receiving and storing the IP address, MAC address, and control
database from its host workstation in the CP's Serial SPI flash
memory
Once these steps have been completed the CP becomes operational.
Copper Adapter Network adapter module, installed on the FDC280’s baseplate to
maintain upstream communications with the control network via a
1000Base-T CAT5 copper Ethernet cable with RJ-45 connectors
DHCP Dynamic Host Configuration Protocol is a client/server protocol that
automatically provides an Internet Protocol (IP) host with its IP address
and other related configuration information such as the subnet mask
and default gateway.
DIN DIN is a non-governmental organization established to promote the
development of standardization and related activities in Germany.
DMZ Demilitarized zone - a physical or logical sub-network that separates an
internal local area network (LAN) from other untrusted networks, usu-
ally the Internet.
ECB Equipment Control Block
EDSA Embedded Device Security Assurance certification (IEC62443)
EEPROM Electrically erasable programmable read-only memory
Fault Tolerant (FT) A station that is running with two FDC280 controllers.
FBM Foxboro Evo system Fieldbus Module (Compact or Standard)
FCP270 Field Control Processor 270
FCP280 Field Control Processor 280
FDC280 Field Device Controller 280
FDC driver Field Device Controller Driver - the name of the driver’s object in the
Foxboro Evo Control Software
xx
Preface B0700GQ – Rev C
Name Meaning
FDSI Foreign Device Systems Integrator
Fiber Adapter Network adapter module, installed on the FDC280’s baseplate to main-
tain upstream communications with the control network via a 100
Mbps fiber optic cable with LC to MT-RJ connectors
Foxboro Evo Control Core software environment, formerly known as “I/A Series (Intelligent
Core Services Automation Series) software”. A workstation which runs this software is
known as a “Foxboro Evo Control Core Services workstation”.
Foxboro Evo Control Formerly known as “FCS Configuration Tools”, “InFusion™ Engineer-
Editors ing Environment”, or “IEE”, these are the Control Software engineering
and configuration tools built on the ArchestrA® Integrated Develop-
ment Environment (IDE).
Foxboro Evo Control Formerly known as “Foxboro Control Software (FCS)” and “InFusion”,
Software a suite of software built on the ArchestrA Integrated Development Envi-
ronment (IDE) to operate with the Foxboro Evo Control Core Services
software.
Foxboro Evo Process An overall term used to refer to a system which may include either, or
Automation System both, Foxboro Evo Control Software and Foxboro Evo Control Core
Services software.
GMT Greenwich Mean Time (GMT) is an international time standard
GPS Global positioning system
ICMP Internet Control Message Protocol
ICS Industrial Control System
LC Connector for fiber optic cable connection to the Fiber Adapter
LED Light-emitting diode
Letterbug Alphanumeric string that the user defines to identify a station in a Fox-
boro Evo system.
Major Image Update Refer to Appendix A “Major Image Update and Minor Image Update”.
Married FT Station Two healthy FDC280 controllers operating as one station.
MMF Multimode fiber cable
Minor Image Update Refer to Appendix A “Major Image Update and Minor Image Update”.
MTK Master Timekeeper
MT-RJ Connector for fiber optic cable connection to Ethernet switches
NTP Network Time Protocol - a networking protocol for clock synchroniza-
tion between computer systems over packet-switched, variable-latency
data networks.
OLUG Online Upgrade, which refers to a legacy method of updating a control
processor's software, which is not supported by the FDC280.
Remarry When a newly booted FDC280 module marries with an FDC280 run-
ning in Single Primary mode.
ROM Read only memory
RWS RemoteWatch Service
xxi
Name Meaning
Rx Receive (communications)
Single Primary An FDC280 module that is running as a single module.
SOE Sequence of Events
Station The virtual controller which runs as one or two CP modules. For exam-
ple, the station may exist on both fault-tolerant modules, but the station
itself is considered a single entity.
STK Slave Timekeeper
SysDEF System Definition
System Configurator Application for configuration of the overall Foxboro Evo system – the
availability and relationships between the hardware – SysDef, and the
Foxboro Evo Control Editors.
TDR/TDA Transient Data Recorder/ Transient Data Analyzer
The Control Editors Refer to “Foxboro Evo Control Editors” above.
The Control Network The Foxboro Evo Control Network
Tx Transmit (communications)
UTC Universal Coordinated Time
Additional terms that pertain to the Image Update features for the FDC280 are provided in
“Image Update Terms and Concepts” on page 254.
xxii
1. Introduction
This chapter describes the main features, fault-tolerant operation, network configuration, and
time synchronization of the Field Device Controller 280 (FDC280).
Overview
The Field Device Controller 280 (FDC280) is an optionally fault-tolerant controller module
whose primary purpose is for device integration, including interfacing field devices, accessing data
in those devices for display, historization, and performing control tasks.
It provides communication connectivity to remote field devices which support these protocols:
♦ Modbus TCP protocol - only supports connection to field devices, gateways, or
bridges that support the Modbus TCP protocol (specifications are in PSS 31H-
2FDC280). Physically connects to those over 10/100 Mbps/ 1 Gbps copper Ethernet
via customer supplied switches.
♦ Modbus RTU Protocol: supports serial devices that support Modbus RTU or ASCII
on RS-232, RS-422, or RS-485 networks
The FDC280 is certified ISASecure® EDSA Level 1, and requires a host workstation with Fox-
boro Evo Control Core Services software v9.3 or later, and Foxboro Evo Control Software v6.2 or
later. It provides the standard capabilities of a Foxboro Evo control processor, such as regulatory,
logic, timing, and sequential control internally, and performs data acquisition (via connected
devices) and alarm detection/notification.
It has a liquid crystal display (LCD) on its faceplate, which displays information such as the letter-
bug, role (Primary/Shadow/Single), part number, hardware revision information, manufacturing
date, and OS version. System engineers can set the FDC280’s letterbug using the arrow and
<Select> keys on the faceplate. A set of light-emitting diodes (LEDs) provide a visual indication of
the communication activity of all of the control network and the Ethernet and serial channels for
field device communications.
The FDC280 can be installed as simplex (single) or fault-tolerant, as shown in Figure 1-1. If
installed as simplex, the FDC280 must be installed in the left slot in the FDC280 baseplate.
Also be aware that the baseplate’s left and right Ethernet ports and serial ports correspond to the
FDC280s installed in the left and right baseplate slots, as shown in Figure 1-2.
1
B0700GQ – Rev C 1. Introduction
Simplex FDC280
Must Be Installed in the Left Baseplate Slot Fault-Tolerant FDC280
Figure 1-1. Simplex and Fault-Tolerant FDC280s in Baseplate
Figure 1-2 shows the LCD and LEDs on a fault-tolerant FDC280 in an FDC280 baseplate (P/N
RH101KF).
Network Adapters Time Strobe To Ethernet I/O

Liquid Crystal Display (LCD) Switches and
(Fiber Adapters Shown) Connectors (A/B)
Field Devices
To The
Foxboro Evo
Control
Network
Ethernet I/O Port

for Right
FDC280*
Ethernet I/O Port
for Left
FDC280*
Power Serial I/O Port

for Right
Ground Select Button FDC280**
Left FDC280
Up-Arrow Button Right FDC280 Serial I/O Port
for Left
Down-Arrow Button FDC280**
* These Ethernet ports enable communications via the customer-supplied dedicated network to the field
devices.
** These Serial ports enable communications via the customer-supplied dedicated network to the field
devices.
Figure 1-2. Fault-Tolerant FDC280s and Network Adapters in FDC280 Baseplate
The LEDs on the faceplate of the FDC280 are explained in “FDC280 LCD, LED Indicators, and
Reset Button” on page 223.
2
1. Introduction B0700GQ – Rev C
The FDC280 baseplate includes connectors for:

♦ Up to two FDC280s
♦ Two copper or fiber network adapters, which connect the FDC280s to the control
network via either copper or fiber 100Mb Ethernet connections, shown in Figure 1-2.
♦ Primary/secondary power from a supported Foxboro power supply
♦ Two CAT5 RJ-45 connectors for Time Strobe connectors - these allow time strobe
cables to connect directly to the baseplate without the need for Time Strobe Adapters.
♦ Two 10/100 Mbps/1 Gbps copper Ethernet RJ-45 connectors for Ethernet connectors
(to field devices either directly or via customer-supplied Ethernet switches) - use
CAT5e or CAT6 cabling with these connectors
♦ Two 37-pin D-type connectors, each of which supports four serial ports (to field
devices via supported termination assemblies) - Use the Compact Type 5 cable
(RH100HV) to connect the FDC280’s baseplate to the termination assemblies.
Unlike the FCP280, the FDC280 does not support the PIO bus and cannot connect to any of the
standard 100 or 200 Series Fieldbus Modules (FBMs). It is designed primarily for field device
integration for Ethernet and Serial protocols.
If upgrading from an FDSI installation, consult with our Global Customer Support at
https://pasupport.schneider-electric.com to optimize your new configuration.
Features
The FDC280 provides the following standard control processor features:
♦ Supports up to 256 field devices and up to 8000 blocks. (For sizing guidelines, includ-
ing examples of valid block count combinations, refer to Field Device Controller 280
(FDC280) Sizing Guidelines and Excel Workbook (B0700GS).)
♦ Can scan I/O points up to 10 times per second as supported by the foreign device.
♦ Field Device Integration support for Modbus TCP, 10/100 Mbps/1 Gbps on the field
device side.
♦ Field Device Integration support for Modbus RTU Serial in RS-232 /RS-422/RS-485
modes up to 115.2 Kbaud rate on the field device side.
♦ A direct 100 Mbps Ethernet fiber or copper connection to the control network for
high speed data communication. Copper cabling is low-cost. Fiber optic cabling is
immune to electromagnetic interference over its length.
♦ A fault tolerant option that delivers improved availability and safety using unique,
dual controller comparison on all outgoing messages over the Foxboro Evo Control
Network, as well as to support redundant operations for monitoring/controlling con-
nected field devices.
♦ Communications with the Foxboro Evo Control Network managed by redundant
Fiber or Copper Adapters mounted on the FDC280 baseplate.
♦ The transceiver in the FDC280 can run RS-485 loaded with up to 256 equivalent
nodes. It has an input resistance of 125 kΩ. This impedance is defined as having one
unit load (UL).
♦ Optional self-hosting mode allows the FDC280 to start up and run, executing its con-
figured control scheme using the checkpoint file stored in flash memory. This allows
3
the FDC280 to boot itself with a valid control database even if its host workstation is
not present.
♦ Minor image update replaces the executable image of a running, fault-tolerant
FDC280 controller with minimal impact to a controlled process.
♦ Optimizes rack space compared to the FCP/FDSI solution
♦ Alarm Queue size supports up to 20,000 messages.
♦ Optional external time synchronization, supported by a global positioning system
available via pulse output from an MTK Spectracom card to the FDC280’s baseplate
♦ Liquid Crystal Display (LCD) and buttons on FDC280 faceplate allow letterbug set-
ting and reading the letterbug, module roles, and real-time statuses.
♦ Improved controller performance. In ideal conditions, the FDC280 can execute
16,000 blocks per second. Refer to Field Device Controller 280 (FDC280) Sizing
Guidelines and Excel Workbook (B0700GS) for information on loading.
♦ Control block processing isolation from device scanners is provided by isolating each
activity to an independent processor core within the FDC280’s CPU - one core for
the FDC280’s control software and Foxboro Evo Control Network communications
software (Core 1), and one core for communicating with the connected field devices
(Core 2). With a fault-tolerant pair of FDC280s, the Core 2 full communication with
the field devices is performed by the Primary FDC280, with the Shadow FDC280
doing minimal communication to maintain connection with the devices. A dedicated,
memory-based communication channel is provided to allow the Core 1 access to
Device configuration and the data managed by Core 2.
♦ For enhanced reliability during maintenance operations, a recessed reset button,
located at the front of the module, allows you to manually reset the module without
removing it from the baseplate.
♦ Flash memory will work for the lifetime of the FDC280.
I/O communications support the following data streams:
♦ Real-time I/O
♦ I/O maintenance activity, such as alarm messages and SMON log messages
NOTE
The FDC280 does not support Sequence of Events (SOE), or TDA/TDR.
When planning for the installation and operation of the FDC280 and the customer-supplied
dedicated network to the field devices, you must consider the following factors:
♦ The FDC280 functional and environmental constraints
♦ The network configuration.
Functional and Environmental Constraints

Refer to the following documents for functional and environmental specifications relating to the
FDC280:
♦ Field Device Controller 280 (FDC280) (PSS 31H-2FDC280)
Foxboro Evo Control Core Services v9.3 (or higher) is required for FDC280 operation.
4
Consider the following when designing an Ethernet network configuration for your particular
application:
♦ Network Configuration – Type of module
♦ Other Factors – Distance, length, number of devices - Refer to The Foxboro Evo Con-
trol Network Architecture Guide (B0700AZ).
These factors are addressed in the following subsections.
I/O Network Configuration

FDC280
The FDC280 is used in the network configurations shown in Figure 1-4 through Figure 1-10.
The FDC280 baseplate has a pair of RJ-45 connectors for copper I/O Ethernet 10Base-T and
100/1000Base-TX connectivity. The FDC280 installed in the left FDC280 slot in the FDC280
baseplate communicates through the left Ethernet I/O port (see Figure 1-2), and the FDC280 in
the right FDC280 slot communicates through the right Ethernet I/O port.
Ethernet Interfaces
The FDC280 baseplate has a pair of Ethernet 10/100 Mbps/ 1 Gbps TCP/IP connections to the
customer-supplied dedicated network (to the field devices).
The IP Address and netmask have to be set (configurable). The FDC280 does not support
DHCP in the current release.
Serial Interfaces
The FDC280 provides four serial ports for connecting to the Serial devices via termination assem-
blies. Use the Compact Type 5 cable (RH100HV) to connect the FDC280’s baseplate to the ter-
mination assemblies.
Table 1-1 provides the part numbers of the termination assemblies supported as part of the
FDC280’s serial interfaces.
Table 1-1. Supported FDC280 Serial Port Termination Assemblies
Termination Assembly Part Number

Serial Termination Assembly with Compression RH926GH
Screws
Serial Termination Assembly with Ring-Lugs P0926PA
Summary of Communication Link Characteristics (Ethernet)

Table 1-2 summarizes the communication link characteristics for the Ethernet interface.
Table 1-2. Communication Link Characteristics
Specification Ethernet
Mode of Operation TCP/IP; UDP
5
Table 1-2. Communication Link Characteristics (Continued)
Specification Ethernet
Supported Data Rates 10/100Mbps / 1 Gbps (or
auto-negotiate)
The communication speed (data rate) is configurable via the ESPEED parameter in the Primary
ECB.
Table 1-3 summarizes the communication link characteristics for Serial interfaces.
Table 1-3. Communication Link Characteristics for Serial I/O
Serial Mode Baud Rate

RS-232, RS-484, RS-422 300, 600, 1200, 2400, 4800,
(Single and dual modes for each type) 9600, 19200, 38400, 57600,
115200
Other Factors
You should consider the following factors when designing a configuration for your application:
♦ The number of devices allowed per FDC280
♦ Ethernet and serial cables, and their allowable length.
Number of Devices and FDC280 Loading

The FDC280 supports a total number of 256 devices s across all the five ports (one Ethernet and
four serial ports). These can be 256 Ethernet devices, or 128 Ethernet devices and 128 serial
devices, with maximum of 32 devices on each serial port in RS-485 mode.
If you configures more than 32 devices under a single serial port, any devices over the 32-device
limit will be marked as “unresolved” with error code “W95 EXCEEDED MAXIMUM
DEVICES”.
You should consider the FDC280 loading when determining the number of devices on the net-
work. The actual number of devices supported is a function of the scan times, device latencies,
and number of devices. As a result, the sizing tool discussed in the following manual should be
used to determine the actual number of devices supported:
♦ Field Device Controller 280 (FDC280) Sizing Guidelines and Excel® Workbook
(B0700GS)
FDC280 Supported Protocol

The configurations in which an optionally fault-tolerant FDC280 is used vary depending on the
protocol(s) of the field devices currently controlled by the FDC280.
Refer to the following manuals for the configurations available when the FDC280 is used with
each type of protocol:
♦ FDC280 Modbus Master Drivers (Serial and TCP/IP) (B0700GT)
6
FDC280 Functionality
This section discusses the functionality of the FDC280.
I/O Integration
The FDC280 provides communication connectivity to remote field devices which support the
Modbus TCP/RTU protocol over Ethernet II and IEEE standard 802.3 (supporting TCP/IP and
Modbus RTU in Serial RS232/422/485 modes). It provides a number of I/O integration tasks
such as interfacing field devices, accessing data in those devices for display, historization, and per-
forming control functions. It physically connects to field devices over 10/100Mbps/1Gbps copper
Ethernet via customer-supplied switches. It supports interfacing to single and dual port devices
from a fault-tolerant FDC280, and interfacing to Ethernet bridges. As well, both dual ported and
simplex serial devices are allowed for the FDC280 serial ports.
A pair of FDC280s support redundant communications over the customer-supplied copper
10/100 Mbps/1 Gbps Ethernet network.
Fault Tolerance Over the Foxboro Evo Control Network

Fault tolerant operation over the Foxboro Evo Control Network is unique with Foxboro control
processors and uses patented technology. Fault-tolerance is superior to redundancy because outgo-
ing messages from the fault tolerant controller must be identical in both modules for a message to
transmit successfully.
NOTE
FDC280s perform redundant operation over the customer-configured copper
10 Mbps/100 Mbps/1Gbps Ethernet network for field device communications.
The following sections describe how fault-tolerance is implemented using the FDC280 and the
difference between redundancy and fault-tolerance over the control network from an applications
standpoint.
FDC280 Fault Tolerant Operation Over the Foxboro Evo Control Network
The fault-tolerant version of the FDC280 consists of two modules operating in parallel (primary
and shadow), with redundant connections to the control network. (The customer-configured net-
work can use either single or redundant connections to the field devices). The two control proces-
sor modules, married together as a fault tolerant pair, provide continuous operation of the unit in
the event of a single hardware failure occurring within one module of the pair. When the primary
and shadow modules boot up, they join together in a process which is referred to as “marriage.”
Both modules receive and process information simultaneously, and faults are detected by the
modules themselves. One of the significant methods of fault detection is comparison of
communication messages at the module’s external interface. Upon detection of a fault, the
communication message is aborted, and self-diagnostics are run by both modules to determine
which module is not working. The module which is working properly then assumes control with-
out affecting normal system operations. An aborted control network communication message is
then sent by the non-defective module via the retry mechanisms of the communications protocol.
An aborted communication message is retried on the next BPC. For more information, see
“FDC280 Diagnostics” on page 239.
7
Redundant vs. Fault Tolerant Systems Over the Foxboro Evo Control
Network
In “redundant” systems, the goal of improved availability through redundancy has been achieved
using a second, or “backup” controller. Redundant systems that use a secondary controller may
have the following shortcomings:
♦ Problems with the primary controller are not detected or are only detected after a
number of potentially bad messages have been transmitted to the field.
♦
Secondary controllers may not use the latest “good” data when they take over from the
primary controller. Configuring the secondary controller incorrectly can result in
substantial system downtime.
♦ Secondary controllers may have health problems that are hard to determine after they
have been idle for a long period of time.
To remove these shortcomings from your systems, the FDC280 uses a patented method of fault-
tolerance for communications over the control network.
Self-Hosting and Non-Self-Hosting Modes

An FDC280 requires the latest control database be downloaded to its local memory when it boots
up. This database is provided in a checkpoint file, which the controller acquires based on whether
it is in the non-self-hosting mode (the default mode) or the self-hosting mode.
When the FDC280 boots up in the traditional non-self-hosting mode, it requests the checkpoint
file from its host workstation. When the controller is using the self-hosting mode of operation,
the checkpoint file is stored locally in the FDC280’s flash memory. Thus, the FDC280 can boot
up in environments where a host workstation is not present. An FDC280 cannot be configured to
run in self-hosting mode until after the station boots up the first time in non-self hosting mode1.
Non-self-hosting mode is the default for a newly commissioned FDC280. If an FDC280 boots
up without a valid checkpoint file in flash, it will load the checkpoint file from the host worksta-
tion. When the database download is complete, the FDC280 issues a checkpoint command auto-
matically, during which the checkpoint file is written to flash.
The self-hosting feature provides a mechanism for an FDC280 to start up and execute its config-
ured control scheme in the absence of a host workstation. A host workstation is only required
when you change the control configuration or the controller image.
The FDC280 requires a host workstation with Control Core Services software v9.3 or later.
FDC280s running in self-hosting mode, after they have been booted up, do not require a link to
the Foxboro Evo Control Network to fully support the self-hosting functionality. (The initial
boot-up process does not require a communications path to host workstations.)
There are certain limitations on the self-hosting mode of an FDC280 controller.
♦ When you enable self-hosting in an FDC280, the smallest time interval allowed for
the auto-checkpoint option is two (2) hours.
♦ If the user attempts to set an auto-checkpoint time of less than two hours, the
FDC280 will force the time to two hours and send a message to the SMON log iden-
tifying the change.
1. If
you install an FDC280 off the shelf that has a valid checkpoint file in flash, the module will load
this file. Any FDC280 that is taken out of service has to be decommissioned (see “Decommissioning
an FDC280 Module” on page 89) so the checkpoint file in its flash memory has been invalidated.
8
For more information, refer to “Configuring the FDC280 Self-Hosting Option” on page 39.
Self-Hosting Feature
All the control blocks and other information that the FDC280 needs to control its field devices
(depending on the protocol) is either written in the flash of the FDC280 or is included in the
checkpoint file. This means that if an FDC280 needs to reboot and go online after a power cycle,
it will be able to do so without the presence of a boot host workstation.
Checkpoint Behavior in Self-Hosting FDC280

When a fault tolerant FDC280 is running in self-hosting mode, the primary module helps ensure
that its shadow module has a matching version of the checkpoint file in flash before allowing the
shadow module to marry with the primary module. To be sure that the files match, the FDC280s
maintain these behaviors:
♦ When a fault tolerant pair of FDC280s are running in self hosting mode and a check-
point command is issued, the fault tolerant station sends the checkpoint file to the
host workstation. When the process of sending the checkpoint file to the host is com-
plete, the FDC280 requests that checkpoint file from the host and copies the file to
flash in both the primary and shadow module.
♦ When a fault tolerant pair of FDC280s with a newly assigned letterbug are booted up,
the modules will marry and load the checkpoint file from the host workstation. If self-
hosting is enabled (i.e. the CFGOPT parameter in the checkpoint file has self-hosting
enabled), the FDC280 station will automatically issue a checkpoint command at the
completion of the checkpoint download. As part of the checkpoint process for self-
hosting, the checkpoint file is written to both the primary and shadow modules’ flash
memory.
♦ When a new FDC280 module is booted up with the intention of marrying with an
FDC280 that is running in Single Primary mode, and the station is configured for
self-hosting mode, the Single Primary module first downloads its checkpoint file to
the shadow module before the shadow module is allowed to marry the Single Primary
module.
If the Single Primary module is downloading the checkpoint file from flash memory
or writing the checkpoint file from the host to flash, the marriage will be held off until
all operations to the Single Primary flash have completed. Normally, a marriage takes
a maximum of 10 seconds to occur when self-hosting is not enabled. However, in this
case the marriage may be held off longer than 10 seconds.
♦ If one module of a fault tolerant pair is not successful in writing a checkpoint file to
flash and the other module succeeds, the module that is not able to write to flash will
invalidate the checkpoint file in flash and go offline. The module that successfully
wrote to flash transitions to Single Primary and sends a message to the SMON log
indicating why the other module went offline.
♦ If both modules of a fault tolerant pair are not successful in writing the checkpoint file
to flash memory, both modules will invalidate the checkpoint file in flash and send a
diagnostic message to the SMON log. The station continues to run fault tolerant and
will attempt to load a new checkpoint file on the next checkpoint command or from
their host when they are rebooted.
9
♦ If a non-fault tolerant module is not successful in writing a checkpoint file to flash

successfully, the module invalidates the checkpoint file in flash and sends a diagnostic
message to the SMON log. The station continues to run as Single Primary and will
load a new checkpoint file on the next checkpoint command or from its host when it
is rebooted.
Image Update
The FDC280's image is stored in flash memory, and has two methods of being updated: Major
Image Update and a Minor Image Update. A Major Update typically provides new feature and a
Minor Update which typically provides new drivers. A non-fault tolerant/simplex FDC280 can
only have a Major Image Update.
A Major Image Update has a major impact on the system process, as described in Appendix A
“Major Image Update and Minor Image Update”. Details for each type of update are provided in
this appendix.
Major Image Update

The Major Image Update, which typically provides new features and corrects undesirable behav-
ior, can only be used to install a new software image when the plant is NOT running normally
(i.e. shut down) as significant disruptions to I/O communications and control behavior occur. It
updates the image in a single (non fault-tolerant) FDC280, and can also be used to update a fault-
tolerant pair.
Minor Image Update

For a fault tolerant FDC280 only, a Minor Image Update, which typically provides new drivers
and corrects undesirable behavior, replaces the executable image (operating system) of a running
FDC280 with a newer image without having to shut down the equipment being controlled by the
FDC280. This feature allows you to take advantage of many product enhancements while only
pausing control for less than 0.5 seconds with I/O scanning failover within 2.5 seconds plus scan
time. This has the same process effect as a failover operation to the Shadow FDC280.
Only one active Field Device Control Network (FDCN) network interface is required for an
Image Update to occur. As shown in Figure 1-2 on page 2, each FDC280 baseplate has two fiber
or copper adapters, but only one is required to have connectivity for a Minor Image Update.
If a release supports Minor Image Update, it can be used to add new protocol drivers or updated
versions of previously-released protocol drivers in a running FDC280.
Be advised that updated versions of previously released protocol drivers can be added using a
Minor Image Update to communicate with new devices.
If you need to update a driver already communicating with existing devices, even if the release
supports Minor Image Update actions, there will be disruption to the control of the devices using
the driver, where as devices connected to the other drivers will not be impacted.
Also note that the driver ECB for the existing device needs to be reconfigured to use the driver ID
of the updated driver.
FDC280 Identification
Baseplate-mounted modules provide identification to the system software of the identity of all
mounted modules by means of a unique, 6-character string called a “letterbug”. For FDC280s,
10
the letterbug identification is a soft letterbug which can be configured using the buttons on the
front of the FDC280 as described in “Setting the Letterbug” on page 37.
Number of Self-Hosting or Auto-Checkpointing FDC280s

Supported By a Boot Host
If the auto-checkpointing option is enabled for the FDC280, along with the self-hosting option,
the FDC280 loading requirements are based partially on the CP idle time and the CP database
size. The resulting maximum total time from checkpoint start to the display of an “installed into
flash memory” message in the system monitor log (SMON log) is fifteen minutes per FDC280.
With an auto-checkpoint rate of two hours (15 minutes x 8 = two hours), this results in a maxi-
mum of eight FDC280s that should be hosted by a single boot host when both the functions are
enabled.
If you slow the auto-checkpoint rate or run small databases, you can host more FDC280s on a
single boot host. Even if the self-hosting option is disabled, the auto-checkpoint timing is roughly
the same. The recommended maximum number of FDC280s that can be hosted also remains
unchanged.
FDC280 Network Configuration for the Foxboro Evo

Control Network
The control network uses redundant communication paths to enhance control reliability.
Figure 1-3 below shows a simplified FDC280 network configuration using redundant Ethernet
fiber switches, 100Mbps fiber cables, and fault tolerant FDC280s. Multiple FDC280s can share
the same redundant switch.
11
The Foxboro Evo Control Network

Ethernet Fiber Switch Ethernet Fiber Switch
FAST ETHERNET WORKGROUP SWITCH FAST ETHERNET WORKGROUP SWITCH
RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
PWR PWR
RESET
CPU CPU
RESET
COM COM
1 Gbps Ethernet
Fiber Optic Cables
FAST ETHERNET WORKGROUP SWITCH FAST ETHERNET WORKGROUP SWITCH
RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
PWR PWR
RESET
CPU RESET
CPU
COM COM
100 Mbps Ethernet

Fiber Optic Cables
Tx & Rx (Redundant)
FDC280 Baseplate FDC280 Baseplate

To To
Ethernet I/O Ethernet I/O
Switches Switches
To Devices To Devices
Fiber adapters TA TA Fiber adapters TA TA

“A” and “B” “A” and “B”
To Serial I/O Field Devices To Serial I/O Field Devices
Note: For additional sizing information, refer to The Foxboro Evo System Planning and Sizing
(B0700AX).
Figure 1-3. Multiple FDC280s in The Foxboro Evo Control Network (Simplified)
The FDC280 uses 100 Mbps Ethernet fiber or copper connections to communicate with Foxboro
stations connected to Ethernet switches in the control network. For information about general
guidelines and specific requirements for designing the control network above the FDC280 level,
including site planning and network installation guidelines, see The Foxboro Evo Control Network
Architecture Guide (B0700AZ).
The FDC280 may operate with similar, off-the-shelf equipment, but Schneider Electric is not
responsible for any system not functioning as described in this user guide if such equipment is
used.
For controls, indicators, and maintenance of the Ethernet switches, refer to the appropriate ven-
dor’s literature, and to the switch-specific documents listed in The Foxboro Evo Control Network
Architecture Guide (B0700AZ).
For instructions on installing and cabling the FDC280 in the non-fault tolerant and fault tolerant
configurations, see Chapter 3 “Installing the Field Device Controller 280”.
12
Network Path Switching

The control network provides redundant communication paths. The control network architecture
and the software in the FDC280 allow it to switch paths when a communications path fails or
when replacing modules.
Each FDC280 has two station MAC addresses and two IP addresses, which are not embedded in
hardware. When you replace the controller, the new controller acquires its station MAC and IP
addresses from the system configuration file based on its assigned letterbug. Software on the
FDC280 then selects the network path that is used to transmit outbound communication.
FDC280 Ethernet Network Configurations for

Supported Field Devices
The FDC280 supports connections to the field devices either directly or via Ethernet communi-
cations to connect to standard Ethernet network components, such as switches and hubs. This
provides the flexibility for the FDC280 to support communications over a variety of network
configurations, including either non-redundant or redundant networks (described below).
When in redundant mode, the FDC280 has two interdependent Ethernet I/O interfaces that the
redundant pair coordinates. These two interfaces have separate and independently-assigned IP
addresses.
Via a customer-supplied dedicated network, the FDC280 can connect directly to field devices
with Ethernet I/O, or to field devices with serial I/O via a protocol-specific gateway which per-
forms the Ethernet-to-serial Modbus TCP I/O protocol conversion and communications:
♦ To enable connection to serial Modbus slave devices, use an Ethernet to Serial Gate-
way (e.g., Schneider-Electric's EGX100).
♦ To enable connection to serial Modbus Plus devices, use a Modbus Plus Ethernet
Bridge.
These configurations are discussed in the following sections.
13
Simplex FDC280 to Ethernet Field Devices Configuration

A simplex, non-fault-tolerant FDC280 connects to Ethernet field devices as shown in Figure 1-4.
FDC280
Ethernet Connection
Serial Connection
Customer-Supplied Dedicated Ethernet Network(1)
Protocol
Field Device Specific
Gateway
Field Device
Field Device
(1) It is recommended to use managed switches for maintenance Field Device

and troubleshooting. Network is optional.
Figure 1-4. Simplex (Single) FDC280 to Ethernet Field Devices Configuration
This configuration does not support a redundant connection to the field device’s Ethernet I/O
network from the FDC280.
14
Fault-Tolerant FDC280 to Ethernet Field Devices over Separate

Networks Configuration
Fault-tolerant FDC280s can connect to Ethernet field devices over separate networks as shown in
Figure 1-5.
FDC280
Left (left/top) Ethernet Connection
Right (right/bottom) Ethernet Connection
Left Serial Connection
Right Serial Connection
192.168.0.1 192.168.0.1 (2)
Customer-Supplied Customer-Supplied
Dedicated Ethernet Dedicated Ethernet
Network (1) Network (1)
192.168.0.2
Field Device
192.168.0.2
192.168.0.3
Field Device
192.168.0.3
192.168.0.4 192.168.0.4
Protocol Protocol
Specific Specific
Gateway Gateway
Field Device
Field Device
Figure 1-5. Fault-Tolerant FDC280s to Ethernet Field Devices in Separate Networks Configuration
NOTE
(1) in Figure 1-5 - When connecting to field devices via a network, it is recom-
mended to use managed switches for maintenance and troubleshooting. The net-
work is optional.
15
Each FDC280 module in a fault-tolerant pair may have the same IP address or may have unique
IP addresses when configured for redundant I/O networks. The FDC280 also supports field
devices with redundant ports on redundant networks where each port may have the same or a
unique IP address.
Some field devices that support redundancy use separate Ethernet I/O networks to isolate the traf-
fic between their primary and secondary Ethernet ports. The separation may be accomplished by
using different subnets, VLANS, or even separate physical networks.
In most cases, separate physical networks are used to help prevent network issues (such as network
storms) on one side from impacting the other side. On occasion, separate physical networks are
required by a specific field device; for example, when the device has identical IP/MAC addresses
on both of its ports that keep both ports from being active in the same network.
Be aware that separate networks do not allow for redundant FDC280s to connect to single-ported
field devices.
16
Fault-Tolerant FDC280 to Ethernet Field Devices over Common

Networks Configuration
Fault-tolerant FDC280s can connect to Ethernet field devices over a common network as shown
in Figure 1-6. In cases where field devices do not need separate I/O networks, a common I/O net-
work can be used. A common network allows for a fault-tolerant FDC280 to connect to single-
ported field devices.
Left FDC280 Right FDC280

Left FDC280 Ethernet Connection
Right FDC280 Ethernet Connection
192.168.0.1 192.168.0.11
Customer-Supplied Dedicated Ethernet Network
192.168.0.2 192.168.0.5
Field Device Field Device
192.168.0.12
192.168.0.3 192.168.0.6
192.168.0.13
192.168.0.4 192.168.0.14 192.168.0.7

Protocol Protocol Protocol
Specific Specific Specific
Gateway Gateway Gateway
Serial Connection Serial Connection
Figure 1-6. Fault-Tolerant FDC280s to Ethernet Field Devices in Common Network Configuration
17
NOTE
1. As shown in Figure 1-6, use subnet 192.168.0.x with subnet mask
255.255.255.0.
2. Either the Left or Right FDC280 can be configured to communicate with any
field device via the customer-supplied dedicated Ethernet network.
Be advised that in Figure 1-6, the FDC280 baseplate Ethernet port connections identified as
192.168.0.1 and 192.168.0.11 are dependent on the settings of the DVNAME parameter in
the Device ECB, either or both of the ports of a dual ported device or, in the case of the single
ported devices, both 192.168.0.1 and 192.168.0.11 can communicate with the single port (field
devices 192.168.0.5, 192.168.0.6 and 192.168.0.7).
Also be aware that a common network does not allow for field devices that have identical
IP/MAC addresses on their redundant ports.
Connecting to Single-Ported Field Devices

In the case of single-ported field devices, both the Primary and Shadow FDC280 modules always
communicate independently with each device.
If the single-ported device can handle multiple simultaneous connections, both the Primary and
Shadow FDC280 modules establish separate connections to the device. The Primary FDC280
performs the normal scan/write while the Shadow FDC280 only has minimal periodic communi-
cations to verify connectivity and keep the connection alive.
If the single-ported device cannot handle multiple simultaneous connections, the behavior is sim-
ilar to the previous description, with the exception that the Shadow FDC280 only performs an
ICMP Ping to verify connectivity.
Connecting to Dual-Ported Field Devices

For dual-ported devices in a common network configuration, the behavior should be the same as
when in a separate network configuration. As shown in Figure 1-6, the Left FDC280 only com-
municates to the left port of each of the devices, and the Right FDC280 only communicates to
the right port of each of the devices.
The FDC280 supports a set of algorithms for handling redundancy switchover for any errors
detected in redundant configurations. Each supported protocol has different options defined by
the RDALGO parameter of the FDC280 station block. For the Modbus TCP driver, refer to the
section “Configure FDC280” and the description of configuration of the RDALGO parameter of
the FDC280 object in FDC280 Modbus Master Drivers (Serial and TCP/IP) (B0700GT).
Field Device-Level Redundancy

Some devices support device-level redundancy. One example of device-level redundancy is the SE
M580 HSBY, described in Appendix E “Interfacing Fault-Tolerant FDC280 to M580 PLC
HSBY”. In case the primary module stops working, the secondary module takes over the pri-
mary's IP address (and announces via Address Resolution Protocol (ARP)) as it assumes control. It
effectively appears as a single ported module to the FDC280.
With this type of device, the FDC280 reacts quickly to the ARP announcement so that it estab-
lishes a new connection to the newly active device module.
18
Fault-Tolerant FDC280s to Dual Ported and Single Ported

Ethernet Field Devices over Common Networks Configuration
Without the link shown in blue in Figure 1-7, the configuration provides for redundant with no
single point causing disruption of the process.
With this link, the configuration provides redundancy with coverage for some multiple point fail-
ures. However, that configuration will require switches with spanning tree protocol enabled.
Left FDC280 Right FDC280 Left FDC280 Ethernet Connection
Right FDC280 Ethernet Connection
192.168.1.1 192.168.1.11
Switch 1 Switch 2
192.168.1.3 Dual Ported 192.168.1.4

Field Device
Switch 3
192.168.1.5
Single Ported
Field Device
Figure 1-7. Fault-Tolerant FDC280s Interfacing to Single Ported and Dual Ported Ethernet Devices
FDC280 Serial Network Configurations for Supported

Field Devices
The FDC280 has four serial ports - each port can be individually configured for RS-232, RS-422,
or RS-485. In non-redundant configurations, a simplex FDC280 is used for interfacing single
ported field devices. In redundant configurations, the fault tolerant FDC280s (Left/Right) can
both interface dual ported field devices. The FDC280 can support up to four direct connect field
19
devices (RS-232 or RS-422) or up to 128 RS-485 field devices distributed over its four ports. On
a port configured for RS-485 protocol, the maximum number of devices supported is 32.
Simplex FDC280 to Serial Field Devices Configuration

A simplex, non-fault-tolerant FDC280 connects to Serial field devices via supported termination
assemblies as shown in Figure 1-8.
Control
FDC280 Network
Simplex
Termination TA
Assembly 1 2 3 4
Four Ports
See below for typical connections.
TA TA
1 2 3 4 1 2 3 4
Modem/ Modem/
Device Field Field
Device
Devices Devices
Field Field
Modem/ Modem/ Devices Devices
Device Device
RS-232/RS-422 RS-485 multidrop

Direct connection. without modems or converters.
Single ported devices. Single ported devices.
NOTE: Each FDC280 port (1 through 4) can be individually configured for RS-232, RS-422, or RS-485
communication standards.
Figure 1-8. FDC280 Simplex in Typical Serial Network Configurations
20
Fault-Tolerant FDC280 to Serial Field Devices Configuration

Fault-tolerant FDC280s can connect to Serial field devices via supported termination assemblies
as shown in Figure 1-9 and Figure 1-10.
Control
FDC280 FDC280 Network
Left Right
Termination TA TA
Assembly 1 2 3 4 1 2 3 4
Four Ports
See below for typical connections.
TA TA
1 2 3 4 1 2 3 4
RS-485 multidrop
Slave without modems or converters.
Devices Dual-ported devices.
Slave
Devices
TA TA
1 2 3 4 1 2 3 4
Modem/
Modem/ Device
Device
Modem/
Device
RS-232/RS-422
Modem/ Dual-ported devices only.
Device
NOTE: Each FDC280 port (1 through 4) can be individually configured for RS-232, RS-422, or RS-485
communication standards.
Figure 1-9. Fault-Tolerant FDC280 to Dual-Ported Serial Devices in Typical Network Configurations
21
FDC280
RS-232 Configuration
Termination Assembly (Left) Termination Assembly (Right)
RS-232 Ports RS-232 Ports

RS-485/422 Ports RS-485/422 Ports
P1 P2 P3 P4 P1 P2 P3 P4
RS-232 Y-Cable
Single-Ported
RS-232 Device
RS-485 2-Wire Configuration


P1 P2 P3 P4 P1 P2 P3 P4
Single-Ported Single-Ported
RS-485 Device RS-485 Device
RS-422 4-Wire Configuration


P1 P2 P3 P4 P1 P2 P3 P4
Single-Ported
RS-422 Device
Figure 1-10. Fault-Tolerant FDC280 to Single-Ported Serial Devices in Typical Configurations
22
Be advised that for the RS-485 2-Wire Configuration in Figure 1-10, for a single-ported device
interfacing on RS-485, the termination assembly’s termination resistors should be enabled on the
termination assembly that is at the end of the bus. Only one termination assembly should have
the termination turned on.
Time Synchronization
The Foxboro Evo system supports time synchronization using either an optional, externally main-
tained source of Universal Coordinated Time (UTC) from GPS satellites or an internal source
using proprietary software.
The FDC280 timestamps data when it is scanned by the FDC driver, so time resolution of I/O
data time stamping depends on the scan rate (which is configurable). Time synchronization
within a Foxboro Evo system synchronizes controllers to provide accurate timestamps for event
and data reporting throughout the system. Time stamping is used for many streams of informa-
tion, such as alarm messages.
For complete information on time synchronization, refer to Time Synchronization User’s Guide
(B0700AQ).
Overview
A Master Timekeeper (MTK), residing in a workstation or server, maintains the time source and
distributes the system time to all other stations in the control network. A Slave Timekeeper (STK)
receives time information from the MTK and keeps itself synchronized with the MTK, and thus
with all other stations in the control network. An STK resides in each control processor.
The MTK determines the time for synchronizing all slave stations by using the station’s real-time
clock (internal time source), the optional GPS receiver and time strobe generator (external time
source), or an external NTP time synchronization source delivered via a second network.
Time strobe cables can be connected directly to RJ-45 ports in the FDC280 baseplate - see
Figure 1-2.
Universal Time Code (UTC) is the international time standard.
Internal Source Time Synchronization

For internal source time synchronization (standard), the MTK station uses time from the internal
clock in the host station. The MTK distributes time as UTC to all stations in the control net-
work. This time is displayed as local time.
At run-time, the time can be entered or changed using the System Management Set Date and
Time display or time can continue to run on its internal clock.
For procedures on how to set the date and time using System Manager, refer to “Date and Time
Tools” in System Manager (B0750AP).
External Source Time Synchronization

For external source time synchronization (optional), the MTK station uses either an externally
maintained source of UTC from GPS satellites, or an external NTP time synchronization source
delivered via a second network. Equipment to support the former option includes a GPS receiver
and time strobe generator.
23
The MTK uses a hardware connection to the controllers to increase the synchronization accuracy
by providing a time strobe pulse, which is sent continuously by the MTK at a precise time
interval. The controllers have built-in hardware to receive the sync pulses generated by the MTK.
FDC280 Sizing Constraints

The FDC280 has several aspects that consume its capacity, including BPC setting, the number
and type(s) of blocks, block memory usage, and so forth. Since the FDC280’s capacity is con-
sumed based on the configuration of these aspects, it is strongly recommended to review the siz-
ing guidelines described in Field Device Controller 280 (FDC280) Sizing Guidelines and Excel
Workbook (B0700GS).
In general, the following apply to FDC280:
♦ The maximum number of blocks that can be configured for use with the FDC280 (or
fault tolerant FDC280 pair) is 8262, including all types: control blocks, ECBs, com-
pounds, data blocks, and so forth. Refer to Field Device Controller 280 (FDC280)
Sizing Guidelines and Excel Workbook (B0700GS) for examples of valid block count
combinations.
The maximum number of blocks used in a given configuration depends on scan
periods and block type selection. This maximum can also be limited by FDC280
memory.
♦ The number of I/O points/blocks which the FDC280 can support (8000 for Modbus
TCP) can vary depending on the protocol(s) of the field devices for which the
FDC280 is set up to control. Refer to the manual for each supported protocol. The
possible scan rates depend on a number of factors.
♦ Other factors need to be considered, such as the number of IPC Connections, alarms,
the size of the Object Manager (OM) database, number of peer-to-peer connections,
etc. Refer to “OS Configurable Parameters” in The MESH Control Network System
Planning and Sizing (B0700AX).
24
2. Quick Start Guide
This chapter provides a sequence for installing and configuring the Field Device Controller
280.
This chapter outlines a typical summary procedure for installing and configuring the Field Device
Controller 280 (FDC280) hardware and software in a Foxboro Evo system. The summary proce-
dure provides references to sections in this guide or other manuals where you will find the details
of each procedure.
This procedure assumes that you are familiar with Foxboro Evo system concepts and the FDC280
hardware and software. Appropriate documents and chapters within this document are referenced
as part of each step.
For more comprehensive information on installing and configuring the FDC280 hardware and
software, refer to the subsequent chapters of this document.
1. Plan your system.
♦ Plan all hardware:
♦ The FDC280’s location and enclosure (see K-Series Enclosures Site Planning
and Installation User’s Guide (B0700GN) or Enclosures and Mounting Struc-
tures - Site Planning and Installation User's Guide (B0700AS))
Refer to Standard 200 Series Baseplates (PSS 31H-2SBASPLT) for the
FDC280 baseplate’s dimensions when planning installation in a Schneider
Electric enclosure.
♦ Which protocol(s) the FDC280 will use to control its field devices, and the
number of I/O points
♦ What network infrastructure you will use - switches, cabling, etc.
♦ The type of network adapter used to connect the FDC280 baseplate to the
control network
♦ Which workstation will host the FDC280
♦ The location and cabling for all field devices to be connected to the FDC280
♦ Plan all software:
♦ Which control blocks to use, loops, strategies, etc.
♦ Letterbugs for all equipment
♦ Network addresses, etc.
♦ To plan your system loading and other run-time factors, refer to the following siz-
ing guidelines:
♦ Field Device Controller 280 (FDC280) Sizing Guidelines and Excel Workbook
(B0700GS).
♦ The Foxboro Evo System Planning and Sizing (B0700AX).
25
B0700GQ – Rev C 2. Quick Start Guide
2. Define the FDC280s in a system configurator.

If you haven’t already, install the Foxboro Evo software by referring to the Control Core
Services Software Installation Guide document included with your version of the soft-
ware, and to the Foxboro Evo Control Software Installation Guide (B0750RA).
An FDC280 with image software versions later than 0900010000 is supported by
Control Software v7.1.1 or later.
With Control Core Services v9.3-9.4, install Maintenance Pack MP47481162. This
Maintenance Pack, as well as its installation instructions (provided in its release notes),
is available for download from the Global Customer Support at https://pasupport.sch-
neider-electric.com.Refer to “System Definition” on page 29. During system configura-
tion, you must define whether the FDC280s will be installed fault tolerant or non-
fault tolerant.
For additional system configuration instructions, refer to the “System Development”
and “Security” manuals listed under “Foxboro Evo Control Software and Foxboro Evo
system software Specific Documentation” in Foxboro Evo Process Automation System
Deployment Guide (B0750BA). Refer to the section “Controllers” in Hardware Config-
uration User’s Guide (B0750BB) to define the FDC280.
3. Install the field devices for the FDC280.
Refer to the manual included with these field devices.
4. Install the FDC280s and their network adapters in the FDC280 baseplate.
Install the FDC280’s baseplate, if not already installed. Refer to Standard and Compact
200 Series Subsystem User’s Guide (B0400FA).
Refer to “Installing a Single or Primary FDC280 Module” on page 30. If installing a
second FDC280 (for fault tolerance), refer to “Installing a Shadow FDC280 Module”
on page 42.
5. Connect power to the FDC280 baseplate.
Refer to “Power Supply Mounting and Installation” in Standard and Compact 200
Series Subsystem User’s Guide (B0400FA).
6. Set the letterbug of the FDC280.
Refer to “Manual Letterbug Assignment via LCD Display” on page 37.
7. Connect the network adapters’ cabling to the FDCN Ethernet switches.
Foxboro offers a variety of Ethernet switches that allow you to connect devices to the
FDC280. For information on these Ethernet switches refer to The Foxboro Evo Con-
trol Network Ethernet Equipment (PSS 31H-7NWEQUIP). The switches can be set up
in a number of topologies with a variety of fiber optic cabling, as described in The
Foxboro Evo Control Network Architecture Guide (B0700AZ).
Refer to “Network Cabling for FDC280 Network Adapters” on page 43.
8. Connect the Ethernet cabling from the field device Ethernet switches to the field
devices.
Connect the FDC280 baseplate to the customer-supplied dedicated network as
described in “Network Cabling for FDC280 Network Adapters” on page 43.
9. Optionally connect the time strobe cables to the appropriate RJ-45 connectors on
the FDC280 baseplate.
26
2. Quick Start Guide B0700GQ – Rev C
The RJ-45 ports for the FDC280 baseplate are shown in Figure 1-2 on page 2.
10. Commission the FDC280.
a. Once you have connected the baseplate to the control network, the FDC280
communicates with its host station.
b. Update the FDC280’s operating system by performing an Image Update opera-
tion. Refer to the document for the appropriate management application:
♦ FoxView - FoxView™ Software v10.4 (B0700FC, Rev. B or later)
♦ System Manager - see System Manager (B0750AP)
Also refer to the warning and notice on page 31.
c. Deploy the FDC280’s control database (containing the FDC280’s ECBs and DCI
blocks) either:
♦ Via the Control Software as described in the Control Database Deployment
User's Guide (B0750AJ).
♦ Via ICC as described in Chapter 6 “Configuring FDC280 Using ICC and
CCS FDC280 Configurator”.
11. Install the FDC Driver on the Control Software client workstation or on the work-
station running Control Core Services that hosts the FDC280.
Refer to “Install FDC280 Drivers” on page 99.
12. Plan and install the field devices.
13. Connect the field devices to the I/O Ethernet switches.
Connect the field devices directly to the customer-supplied I/O Ethernet switches as
described in Chapter 3 “Installing the Field Device Controller 280”.
14. Import the FDC280 Modbus driver and configure the FDC280, its Primary ECB
(for the Ethernet port), its ECB200 (for its driver), and its field device ECBs
(ECB201s) and their I/O points (DCI blocks).
Use the Foxboro Evo Control Editors to create all these objects. Refer to “Configura-
tion Procedures” on page 99 for these instructions.
You may perform this step with either:
♦ The Control Software or,
♦ If your FDC280 has an image version higher than 0900010000, with ICC and
the CCS FDC280 Configurator. For ICC configuration instructions, refer to
Chapter 6 “Configuring FDC280 Using ICC and CCS FDC280 Configurator”.
When configuring each field device with the Control Software (discussed in “Equip-
ment Control Blocks” in the Block Configurator User's Guide (B0750AH)):
♦ For a simple configuration with the same scan rate for all the points in a device,
configure the ECB201’s parameters only.
Otherwise, use the Groups tab in the Device Editor (discussed in “Configuration
Procedures” on page 99). Groups configuration is optional.
♦ In both these cases, configure the device options in the DVOPTS parameter of the
ECB201, regardless of the parameter length.
Configure the block processing Period/Phase as discussed in “DCI Block Processing”
on page 123.
27
B0700GQ – Rev C 2. Quick Start Guide
15. Create and edit DCI blocks for all device I/O points to be processed.
See “DCI Block Point Number Parameters” on page 121, and “Configuring DCI
Blocks” on page 120
When performing this step with the Control Software. connect these other blocks to
the device as discussed in “Other Field I/O Connection Methods” in Block Configura-
tor User's Guide (B0750AH).
16. Deploy the changes to the FDC280.
♦ The Control Software (refer to Control Database Deployment User's Guide
(B0750AJ)) or,
Also, place FDC280 online via System Manager (as described in System Manager
(B0750AP)) if you have not already done so.
17. Enable communications with each field device via System Manager.
See “FDC280 Equipment Change Actions in FDC280 Modbus Master Drivers (Serial
and TCP/IP) (B0700GT) and System Manager (B0750AP).
18. Verify Device I/O Data using the Block Detail Displays.
a. Access your preferred detail display application for details on the blocks, such as
the Foxboro Evo Control HMI or FoxView. Refer to Control HMI Application
User's Guide (B0750AR) or FoxView Software (B0700FC) for instructions.
b. Access the block detail display for each DCI block created, and confirm its data.
19. Checkpoint the Database. For details, refer to System Manager (B0750AP).
20. Monitor the FDC280’s operation.
Refer to the appropriate manual:
♦ System Manager - see System Manager (B0750AP)
♦ Control HMI - Control HMI Application User's Guide (B0750AQ)
♦ FoxView - FoxView™ Software v10.4 (B0700FC, Rev. B or later)
21. When needed, decommission the FDC280.
Refer to “Decommissioning an FDC280 Module” on page 89.
28
3. Installing the Field Device
Controller 280
This chapter provides installation and cabling information for the Field Device Controller 280
(FDC280).
Overview
The FDC280 is available in two configurations, non-fault tolerant and fault tolerant.
Communication between the two modules in the fault tolerant configuration takes place via wir-
ing in the baseplate in which the modules are installed.
The FDC280 must be installed in the FDC280 baseplate (P/N RH101KF), which must be
mounted horizontally for cooling purposes. For complete information on this baseplate, includ-
ing how to mount it and provide power, refer to Standard and Compact 200 Series Subsystem User’s
Guide (B0400FA).
The FDC280’s baseplate is designed for installation in Foxboro Evo system equipment enclosures.
For general information on installing equipment into these enclosures, refer to K-Series Enclosures
Site Planning and Installation User’s Guide (B0700GN) or Enclosures and Mounting Structures - Site
Planning and Installation User's Guide (B0700AS). Refer to Standard 200 Series Baseplates
(PSS 31H-2SBASPLT) for the FDC280 baseplate’s dimensions when planning installation in a
Schneider Electric enclosure.
For installation of the FDC280 in accordance with ISASecure™ certification requirements, cer-
tain facility and system configuration requirements must be complied with. Refer to Security
Guidelines For ISASecure™ Certified Products (B0700GH) for instructions on installing the
FDC280 so that ISASecure™ requirements are met.
System Definition
System Definition identifies the Foxboro Evo system components, system software required by
each component, the system component letterbugs, and other system characteristics for correctly
loading system software and identifying the system software objects. The letterbug is an
alphanumeric string that the user defines to identify a station in a Foxboro Evo system.
System Definition is initially performed prior to installation of the system equipment, and it is
updated with any hardware/software system changes. Reports produced by System Definition
(SysDef ) software define the system network and provide information that can be used in con-
junction with equipment installation.
♦ For a step-by-step procedure for defining a Foxboro Evo system configuration using
the System Definition (SysDef ) software, refer to System Definition: A Step-By-Step
Procedure (B0193WQ).
♦ To use the Control Editors to define the system, refer to the “System Development”
and “Security” manuals listed under “Foxboro Evo Control Software and Foxboro Evo
system software Specific Documentation” in Foxboro Evo Process Automation System
29
B0700GQ – Rev C 3. Installing the Field Device Controller 280
Deployment Guide (B0750BA). Refer to the section “Controllers” in Hardware Config-

uration User’s Guide (B0750BB) to define the FDC280.
Installing a Single or Primary FDC280 Module

Figure 3-1 shows how to install a single (non-fault tolerant) or primary (fault tolerant) FDC280
module on its FDC280 baseplate (RH101KF) with a pair of either fiber adapters (RH924WA) or
copper adapters (RH924UQ).
FDC280, 2-Position Self-Retaining

DIN Rail Mounted Baseplate (RH101KF) Hex Screw
(1 of 2)
FDC280 Module
(RH101FQ)
Adapter Adapter FDC280 FDC280

Slot A Slot B Position 1 Position 2
“FDC280 1” “FDC280 2”
For all Ethernet and serial cabling coming from the

Each FDC280 baseplate requires two network
FDC280 baseplate, it is recommended that you
adapters - either two fiber adapters or copper
label this cabling depending on whether it will
adapters.
support communications from the Left or Right
FDC280s. Fiber Adapter Copper Adapter
Self-Retaining (RH924WA) (RH924UQ)
Hex Screw
(1 of 2)
* Network adapters are installed with their

tops facing the left side of the baseplate.
Figure 3-1. FDC280 Module Installation (Typical)
30
3. Installing the Field Device Controller 280 B0700GQ – Rev C
WARNING
POTENTIAL DEATH OR SERIOUS INJURY
For safety reasons, always consider the possible impact on plant

operations before removing a non-fault tolerant FDC280 module from
a baseplate in an active control system.
Failure to follow these instructions can result in death or serious

injury.
NOTICE
POTENTIAL DATA LOSS AND EQUIPMENT DAMAGE
Physically removing an FDC280 from a fault tolerant pair means that

your plant will have to assume the responsibilities and potential
conditions with running control in simplex/non-fault tolerant mode.
Failure to follow these instructions can result in data loss and/or

equipment damage.
To perform this procedure, you require a hex driver tool (part number X0179AZ).
Be aware of the following when working with FDC280 modules in self-hosting mode:
1. When replacing a module in a fault tolerant pair and the other module remains run-
ning as Single Primary, plug in the new module and it will receive the image and
checkpoint file from the Primary module prior to marrying. However, when replacing
a module and the station is currently powered down, boot up the module that was not
replaced first and then marry in the replacement module. This helps ensure that the
new module assumes the same letterbug and is given the proper checkpoint file during
its marriage.
2. When FDC280 modules are installed for the first time (that is, two fault tolerant
modules are installed together, or one non-fault tolerant module is installed, where
none of these modules have generated or received the checkpoint file for their control
scheme) and these modules are meant to run in self-hosting mode, they must be
booted initially in non-self-hosting mode (as set by default). This helps ensure that the
modules download the most recent checkpoint file from the host workstation. To help
ensure these modules boot-up in the default mode, change the letterbug to a non-exis-
tent letterbug and then back to desired letterbug. This helps ensure the FDC280 will
load the checkpoint file from the host workstation.
The FDC280 can only be plugged into a baseplate connector in an FDC280 baseplate. Table 3-1
details the baseplate for mounting FDC280 modules in their designated slots.
31
Table 3-1. Baseplate and Mounting Positions for FDC280 Modules
Fault Tolerant
DIN Rail Baseplate FDC280 Baseplate Single FDC280
Baseplate Size Position Part Number Positions Baseplate Position
2 Position Vertical or RH101KF 1 and 2 1 (2 position
Horizontal1 remains empty)
1.
The FDC280 baseplate must be installed on a horizontal DIN rail only.
To install a single (non-fault tolerant) or primary (fault tolerant) FDC280 on a modular

baseplate:
1. Install the horizontally- or vertically-mounted FDC280 baseplate to the DIN rail,
connect the dc power cable, and optionally connect the time strobe cable to the base-
plate as described in “Equipment Installation” in Standard and Compact 200 Series
Subsystem User’s Guide (B0400FA). Be aware that, if the FDC280 is to meet Marine
certification requirements, it must be installed on a horizontal DIN rail only.
To optionally connect to an external time strobe generator via RJ-45 connectors
labelled on the baseplate, refer to “Module Fieldbus and Time Strobe Splitters/Termi-
nators” in B0400FA.
NOTICE
POTENTIAL EQUIPMENT DAMAGE
Observe the signal and power cable separation and segregation

guidelines in Standard and Compact 200 Series Subsystem User’s
Guide (B0400FA)
Failure to follow these instructions can result in equipment

damage.
2. Install the FDC280 module (RH101FQ) as follows:

a. Press the FDC280 into position 1 (“FDC280 1”) in the designated modular base-
plate, as shown in Figure 3-1. With the FDC280, the embedded software in
FDC280 does not know if it is running in simplex (single) mode or fault-tolerant
mode. If the FDC280 is configured as in simplex mode, FDC280 needs to be
plugged in the left slot in the FDC280 baseplate.
The FDC280 can only be plugged into a baseplate connector that specifically
supports the FDC280. These baseplate slots are labeled “FDC280 1” and
“FDC280 2” (see Figure 3-1).
b. Tighten the two self-retaining hex screws on the module using a hex driver tool
(part number X0179AZ).
32
NOTICE
1. When using the hex driver tool (X0179AZ) or other 5/32 hex driver
tool, make sure that it does not generate more than 12 inch pounds of
torque (1.356N-m), or you might strip the threaded inserts out of the
baseplate.
2. The FDC280 module must be screwed in place for proper
operation. It is inadvisable to expect the signal connectors alone to
hold the module in place.

damage.
3. Install the two network adapters (fiber adapters (RH924WA) or copper adapters
(RH924UQ)) onto the FDC280 baseplate as follows. They must be installed in the
orientation shown in Figure 1-2 on page 2.
a. Press the network adapter into its appropriate position in the designated modular
baseplate, as shown in Figure 3-1, either Position “A” or Position “B”.
b. Tighten the two self-retaining hex screws on the module using a hex driver tool
(part number X0179AZ).
NOTICE
When using the hex driver tool (X0179AZ) or other 5/32 hex driver
torque (1.356 N-m), or you might strip the threaded inserts out of the
baseplate.

damage.
c. Repeat for the second network adapter.
33
Figure 3-2. Example Network Adapters (Fiber) in FDC280 Baseplate (Do Not Connect Their Cables
At This Time)
4. If you are installing the FDC280 in a European installation, perform the procedure in
“Maintaining EMC and CE Compliance For FDC280 Baseplates (European Installa-
tions Only)” on page 36.
5. When all modules are installed, connect power to the baseplate as shown in Figure 1-2
on page 2 and as described in “Baseplate Power Supply Cabling” in Standard and
Compact 200 Series Subsystem User’s Guide (B0400FA).
The FDC280 follows one of the following boot-up sequences:
♦ “Case 2 – Connecting an FDC280 with the Same Letterbug” on page 85
♦ “Case 3 – Connecting an FDC280 with a New Letterbug” on page 86
6. Assign the FDC280 letterbug as described in “Setting the Letterbug” on page 37.
34
NOTICE
Make sure you assign the correct FDC280 letterbug before connecting
the Ethernet fiber optic cables to the FDC280. This avoids potential
process control safety issues if a letterbug has previously been
assigned to the module. Label space is provided on the front of the
module to record the letterbug.
Also, when replacing a non-fault tolerant FDC280 set to self-hosting
mode, change the letterbug to a non-configured letterbug and then to
its hosted letterbug. This helps ensure the correct letterbug is
configured and there is no valid checkpoint file in flash. Without
following this order, the letterbug configured for that module may not
match the letterbug expected by the host.

damage.
7. Once the first FDC280 has booted up as a Single Primary module, you can install a
second FDC280 module in this baseplate as described in “Installing a Shadow
FDC280 Module” on page 42.
8. Connect the network adapter modules to Ethernet switches in the control network as
described in “Network Cabling for FDC280 Network Adapters” on page 43.
9. Connect the copper communication cables from the FDC280 baseplate to the appro-
priate switch in the customer-supplied dedicated network that connects to the field
devices, or directly to the field device itself.
NOTE
For cabling connections from the FDC280 baseplate to the customer-supplied ded-
icated network, it is recommended that you use shielded CAT5e or CAT6 twisted
pair cable because it has the advantage of providing protection for external interfer-
ence.
10. If replacing an existing non-fault tolerant module, update the new FDC280 hardware
to the correct software image using the “Image Update” action, if required. (This
action can either upgrade or downgrade an FDC280’s software image depending on
the revision of that software image.) In System Manager (B0750AP), refer to “Image
Update” under section “Equipment Change Actions”.
I the FDC280 will run in non-self-hosting mode, the installation procedure is finished.
Otherwise, proceed to “Configuring the FDC280 Self-Hosting Option” on page 39.
35
Maintaining EMC and CE Compliance For FDC280 Baseplates

(European Installations Only)
When installing FDC280 modules and their respective baseplates in European installations, you
must add the hardware discussed in this section to maintain EMC and CE compliance. The
requirements in this section have to be applied in addition to the power and grounding require-
ments prescribed in Standard and Compact 200 Series Subsystem User’s Guide (B0400FA).
It is better attenuate system interference presence detected at the source before they find their way
to multiple high frequency “sneak” paths. Once the EMI noise is in the system, it can easily
migrate through the ground system as common mode EMI noise.
There are seven basic steps to the philosophy and mitigation of interference that are discussed in
this document:
♦ Provide proper enclosure and rack-room grounding
♦ Attenuate the source(s) of interference
♦ Capture and return interference to its source
♦ Shield remaining interference away from sensitive equipment
♦ Apply recommended power wiring practices
♦ Apply shielded cable/conduit to minimize radiated emissions and EMI noise pickup
♦ Utilize proper separation and segregation of power, communications, and signal
cabling in system enclosure and at the customer site
Installation and interconnection information is detailed in this appendix only to the extent neces-
sary to configure the equipment mechanically and electrically so that the EMI emissions and
immunity levels fall within parameters that are consistent with the requirements of the European
Community EMC Directive. In addition, the following installation of clamp-on common mode
ferrite cores, which are an effective way to reduce conducted interference, has to be installed on
all FDC280 baseplate input power cables to make the EMI emissions and immunity levels fall
within the parameters of the EMC directives.
These common mode ferrites (Foxboro part number BF162YH) has to be installed on all DC
input power cables attached to the FDC280 baseplates as close as possible to the actual baseplate
power connector.
Figure 3-3 illustrates a typical clamp-on common mode ferrite core installed on a cable.
Figure 3-4 shows a typical FDC280 and baseplate with the clamp-on common mode ferrites
installed.
Figure 3-3. Ferrite Core, Typical
36
Figure 3-4. Ferrite Cores Installed On FDC280 Baseplate Input Power Cables
Setting the Letterbug

The letterbug may be assigned via the methods described below:
♦ “Manual Letterbug Assignment via LCD Display”
♦ (For fault tolerant FDC280s only) “Automatic Letterbug Assignment From Existing
FDC280”
An FDC280 must have a unique letterbug in your system.
Manual Letterbug Assignment via LCD Display

The FDC280’s letterbug can be assigned manually using the buttons on the faceplate of the
FDC280, shown in Figure 3-5. When changing the letterbug manually, you must follow the fol-
lowing requirements:
♦ Check that the FDC280 is not connected to the control network, or the letterbug
assignment process will not work. The FDC280 does not respond to button presses
unless it is disconnected from the control network.
♦ For an FDC280 pair, the modules must be in single mode for their letterbugs to be
changed (i.e. only one module must be present in either of the FDC280 baseplate’s
slots). The Select button on the FDC280 will not respond when the primary and
shadow modules are married.
♦ Do not press any buttons in an order other than that described in the following proce-
dure, or the letterbug assignment process will be aborted.
37
Liquid Crystal Display (LCD)
Select Button
Up-Arrow Button
Down-Arrow Button
Figure 3-5. FDC280 Faceplate Buttons and Liquid Crystal Display (LCD)
To assign a letterbug to an FDC280, proceed as follows:

1. Holding down the Select and down-arrow together the LCD displays the follow-
ing:
CHANGE
Y LETTERBUG? N
2. The “?” flashes on and off for 30 seconds.
Use the Select button to move the cursor to the “Y” or the down-arrow to move to
the “N”.
If the cursor is over the “Y” then press Select again and the cursor moves to the first
character of the letterbug.
If the cursor is over the “N” then the process will be aborted. The process is also
aborted if no button is pressed within 30 seconds.
3. Set the letterbug. The LCD displays a temporary letterbug, and the first character
(usually “F”) flashes. The arrow buttons will iterate this character through the alpha-
numeric character set - pressing the up-arrow button changes an “F” to “G” and the
down-arrow changes an “F” to “E”. The set of one-digit numbers (0-9) can be
selected after iterating through the alphabet; pressing the up-arrow button changes
“Z” to “0” (zero), iterates through the numbers, and then changes “9” to “A”.
Set the character to the appropriate letter/number, and then press the Select button to
move to the next character.
Continue setting characters until the letterbug has been completed.
The process is aborted if you wait more than 30 seconds without pressing any
buttons during this stage of the process.
38
4. While setting the letterbug, the display shows:

{letterbug you are setting}
Y ACCEPT CHG? N
5. After pressing Select for the last character, the “?” flashes on and off for 30 seconds.
Use the Select button to move the cursor to the “Y” or the down-arrow to move to
the “N”.
If the cursor is over the “Y”, and then you press Select again, the FDC280 will
accept the new letterbug and reboot.
If the cursor is over the “N”, the process will be aborted. The process is also aborted if
no button is pressed within 30 seconds.
The letterbug is set. When the installation procedures for the FDC280(s) in their baseplates are
complete, the FDC280s can be connected to the control network.
Automatic Letterbug Assignment From Existing FDC280

When a new FDC280 module is plugged in to marry with a running FDC280 module, the letter-
bug is assigned automatically to the new module. The FDC280 reboots automatically after the
letterbug has been (automatically) assigned.
Configuring the FDC280 Self-Hosting Option

Modify the CFGOPT parameter of the FDC280’s Station block to enable or disable self-hosting.
To enable self-hosting in an FDC280, use control configurator software to set the self-hosting bit
(Bit 8) of the CFGOPT parameter in the Station block (CFGOPT=0x01XX) and issue a Check-
point command. Refer to Integrated Control Block Descriptions (B0193AX) for additional informa-
tion on the CFGOPT Station block parameter.
For additional details on the operation of an FDC280 with self-hosting enabled, refer to:
♦ “Checkpoint Behavior in Self-Hosting FDC280” on page 9
♦ “Initializing the FDC280 with Self-Hosting Enabled” below
Initializing the FDC280 with Self-Hosting Enabled

Be aware that the FDC280’s database cannot be initialized with self-hosting enabled. If you try to
initialize the database on an FDC280 that is configured for self-hosting, you will get the message
shown below. If the FDC280 is operating in self-hosting mode, you must first disable self-hosting
and perform a checkpoint before initializing the FDC280.
39
Figure 3-6. Initializing a Self-Hosting FDC280
Disabling Self-Hosting
To disable self-hosting in an FDC280, use control configurator software to reset the self-hosting
bit (Bit 8) of the CFGOPT parameter in the Station block (CFGOPT=0x00XX). Refer to
Integrated Control Block Descriptions (B0193AX) for additional information on the CFGOPT Sta-
tion block parameter.
The SMON log indicates the outcome of the Checkpoint command. For example, the SMON
log will contain the following line:
2007-11-03 10:03:20 FP0101 Process = Self Hosting RDHSS 000131 - Self Host-
ing Disabled
When an FDC280 has self-hosting enabled (CFGOPT=0x01XX) and auto-checkpoint is set for
two hours but configured for one hour (CKPOPT=1 and AUTCKP=2), and self-hosting is then
disabled by resetting CFGOPT to 0x00XX without altering the CKPOPT or AUTCKP values
and a checkpoint is performed, the auto-checkpoint frequency continues to be two hours (instead
of the originally configured one hour).
To complete a checkpoint frequency faster than two hours, refer to “Auto-Checkpoint While
Enabling/Disabling Self-Hosting” on page 41.
Verifying Self-Hosting Information Using Station Block Display

The status of the FDC280’s self-hosting mode is also indicated in the processor’s Station block
display. Proceed as follows:
1. Open FoxSelect.
2. Select the FDC280’s letterbug.
40
3. Open the Station block for the FDC280. Refresh if necessary.

The status of self-hosting is shown under Options, as illustrated in Figure 3-7.
See NOTE below.
If self-hosting is disabled, the following is shown:
Figure 3-7. Self-Hosting Status via Station Block Display
Figure 3-7 shows the “MEMORY SELF PRESERVATION” bit as enabled (CFGOPT.B22).
However, in the FDC280, the memory self-preservation bit is not used. You can ignore any mes-
sages about memory self-preservation for the FDC280. This feature was used only for the
FCP270.
Auto-Checkpoint While Enabling/Disabling Self-Hosting

When you enable self-hosting in an FDC280, the smallest time interval allowed for the auto-
checkpoint option is two (2) hours.
If you attempt to set this to a smaller interval, the FDC280 will override this command. The fol-
lowing message may appear in the SMON log:
2008-01-24 14:56:27 FP0101 Process = Checkpoint CIO_DB 000015 - Auto Check-
point Override to 2 Hours
If this occurs, you should do one of the following with your appropriate control configurator to
help ensure that the configurator’s work file reflects the actual AUTCKP value in the FDC280:
♦ Modify AUTCKP to reflect two hours and issue a Checkpoint command.
41
♦ Upload any “Runtime Changes” so any differences between the Galaxy configuration
database and the FDC280 are resolved. This will force the FDC280 to upload its cur-
rent parameter values to the work file on the workstation.
If either of these steps is not performed when you disable self hosting, the auto-checkpoint inter-
val will remain at two hours but the value of AUTCKP in the work file will remain unchanged. To
verify the time interval set for auto-checkpoint, view the Station Block Display for the current
FDC280 value.
Installing a Shadow FDC280 Module

All FDC280 modules are shipped from the factory with the latest software image (operating
system) stored in flash memory. If the software image of the shadow and primary modules
differ, the shadow module copies the software image from the primary module and writes it to
flash memory before marrying the primary.
To perform this procedure, you require a hex driver tool (Foxboro part number X0179AZ) or
other 5/32 hex driver tool.
If self-hosting is enabled and the checkpoint file of the shadow and primary modules differ, the
shadow module copies the checkpoint file from the primary module and writes it to flash mem-
ory before marrying the primary.
If the letterbug of the shadow module differs from the primary module, the shadow copies the
primary’s letterbug to flash memory before marrying the primary.
Also, if the shadow module is to be run in self-hosting mode, refer to the first note on page 31.
To install a shadow (fault tolerant) FDC280 module on a modular baseplate:
1. Press the FDC280 module (RH101FQ) into position 2 (“FDC280 2”) in the
designated modular baseplate, as shown in Figure 3-1 on page 30.
2. Tighten the two self-retaining hex screws on the module using a hex driver tool
(Foxboro part number X0179AZ).
NOTICE
1.When using the hex driver tool (Foxboro part number X0179AZ) or
other 5/32 hex driver tool, make sure that it does not generate more
than 12 inch pounds of torque (1.356 N-m), or you might strip the
threaded inserts out of the baseplate.
operation. It is inadvisable to expect the signal connectors alone to
hold the module in place.

damage.
42
3. If you are installing the FDC280 in a European installation, perform the procedure in
“Maintaining EMC and CE Compliance For FDC280 Baseplates (European Installa-
tions Only)” on page 36.
4. Verify that the shadow module boots up and marries the primary module as described
in one of the following boot-up sequences:
♦ “Case 4 – Connecting a Shadow Module with Same Software Image” on page 86
♦ “Case 5 – Connecting a Shadow Module with Different Software Image” on
page 88
5. Verify that the shadow module is married to the primary module by viewing the LCD
messages shown. Refer to the “Controller (Control Processor) Messages” table in
Control Core Service V9.x System Error Messages (B0700AF) for the list of applicable
“marriage”-related messages.
For more information, in System Manager (B0750AP), “Equipment Information”
under section “Station Information for Control Processors, CNIs, and ATSs”.
6. Using the Equipment Information display for the FDC280 in the System Manager,
confirm the following (see Chapter 9 “System Management”):
♦ The shadow module is married (Married Shad) to the primary module (Married
Prim):
PRIMARY MODE: Married Prim
SHADOW MODE: Married Shad
The installation procedure is finished.
Caution on Removing the FDC280
CAUTION
POTENTIAL INJURY
When used in environments with an ambient temperature greater than

25 degrees C (77 degrees F), be advised that when handling the
FDC280 modules, the modules may become too hot to touch.
Failure to follow these instructions can result in injury.
Network Cabling for FDC280 Network Adapters

To design your implementation of the control network, including site planning and network
installation guidelines, refer to The Foxboro Evo System Planning and Sizing (B0700AX) and The
Foxboro Evo Control Network Architecture Guide (B0700AZ).
It is recommended that you purchase fiber optic or copper cable for your configuration of the
control network which meets the requirements listed in The Foxboro Evo Control Network Archi-
tecture Guide (B0700AZ) and the “Site Planning” chapter of the Foxboro documents for the
switches from which you will build your network.
43
If you are planning to build your implementation of the control network with copper cabling
(and the copper adapter), be aware that for the FDC280, the maximum copper cabling connec-
tion is 100 m (328 ft).
NOTICE
When installing fiber optic cable, do not exceed the maximum bend
radius of 5 cm (2 in).

damage.
Each fiber/copper adapter connects to one switch, as shown in Figure 3-8. Switches in the control
network should be redundant, so one adapter should connect to switch “A” and the other should
connect to switch “B”. The cables should connect to the same port number on both switch “A”
and “B” - that is, if one adapter connects to port 1 on switch “A”, the other adapter should con-
nect to port 1 on switch “B”.
SWITCH GROUP A
Note: Fiber adapters shown.

SWITCH GROUP B
Same port #
on each switch.
Figure 3-8. Recommended Fiber Adapter Module Switch Connections
To avoid cabling issues, it is recommended that:

♦ All cables are labeled.
♦ Use only the appropriate cable lengths.
♦ Use different cable colors fir different networks when possible.
To connect a single (non-fault tolerant) FDC280 module to Ethernet switches in the control net-
work, proceed as follows:
1. Remove any rubber port dust covers from the fiber or copper adapter module’s net-
work ports, as shown in Figure 3-9. Retain the dust covers for use on any unused
ports.
44
Fiber Adapter (RH924WA) Copper Adapter (RH924UQ)
Fiber Network Ports Copper Network Port
NOTE: As shown here, rubber dust covers have already been removed from the ports.
Figure 3-9. Fiber and Copper Adapter’s Network Ports
2. Connect the appropriate cabling from the adapter’s network port(s) to its associated
switch on the control network. (Repeat for its pair adapter as well.)
a. For the fiber adapter, connect the fiber adapters to one Ethernet Fiber switch
(switch 1) in the control network using 100 Mbps fiber optic cable with LC to
MT-RJ connectors. For each cable, attach one LC to each of the fiber adapters.
Connect the fiber adapters to another Ethernet Fiber switch (switch 2) in the con-
trol network using another 100 Mbps fiber optic cable with LC to MT-RJ con-
nectors. Purchase and install fiber optic cable which meets the requirements listed
in The Foxboro Evo Control Network Architecture Guide (B0700AZ) and the “Site
Planning” chapter of the documents shipped with the Foxboro switches you are
using.
See Figure 3-10 below for an example of cable connections to fiber adapters.
b. For the copper adapter, connect the copper adapter in position “A” to one Ether-
net Fiber switch (switch 1) in the control network using a 100Base-T or
1000Base-T CAT5 copper Ethernet cable with RJ-45 connectors. Purchase and
install copper cable which meets the requirements listed in The Foxboro Evo Con-
trol Network Architecture Guide (B0700AZ) and the “Site Planning” chapter of the
documents shipped with the Foxboro switches you are using.
NOTE
The copper adapter cannot be used with the C-Series switches
(P0973BL/P0973HA), C5-Series switches (P0973KJ), and S-Series switches
(P0973KD/P0973KK). These switches are described in The MESH Control Net-
work Hardware Instructions for C-Series Switches (P0973KJ/HA/BL) and B-Series
Switches (P0973LK) (B0700CJ) and The MESH Control Network Hardware Instruc-
tions for S-Series Switches (P0973KD/P0973KK) (B0700CE).
45
Connect the copper adapter in position “B” to another Ethernet Fiber switch
(switch 2) in the control network using a 100Base-T or 1000Base-T CAT5 copper
Ethernet cable with RJ-45 connectors.
Fiber Adapters Shown
Power Cable
Note: The above figure is an example rendering only. The information shown in the LCDs is not
representative of information shown in the field.
Figure 3-10. FDC280 Baseplate and Network Adapters Connected

(Fiber Adapters Shown - Example Rendering Only)
FDC280 Simplex Serial Termination Assembly

Installation
A typical simplex serial termination assembly (RH926GH) installation is shown in Figure 3-11.
The termination assembly (TA) connects to the FDC280’s baseplate by means of a termination
cable.
NOTE
For all Ethernet and serial cabling coming from the FDC280 baseplate, it is recom-
mended that you label this cabling depending on whether it will support communi-
cations from the Left or Right FDC280s.
46
Termination Cable
Switches
Termination
Assembly
RS-232 Cable To Field Device

Figure 3-11. RH926GH Termination Assembly
The part numbers for the supported termination assemblies are listed in Table 1-1. Use the Com-
pact Type 5 cables in Table 3-2 to connect the FDC280’s baseplate to the termination assemblies.
Table 3-2 lists the available lengths and part numbers for a Type 5 communication cable for the
FDC280 serial termination assemblies.
Table 3-2. Termination Cables (Type 5) for the FDC280 Serial Termination Assemblies
Cable Part Number Length

RH100HV 1.0m (3.2 ft)
RH100HW 1.5m (4.9 ft)
RH100HX 2.0m (6.6 ft)
RH100HY 3.0m (9.8 ft)
RH100HZ 5.0m (16.4 ft)
FDC280 Simplex Serial Termination Assembly Installation

Instructions
Install the supported FDC280 serial termination assemblies as per the general installation instruc-
tions in Standard and Compact 200 Series Subsystem User’s Guide (B0400FA).
The following subsection describes how to make the device cable connections to the TA.
FDC280 Simplex Serial Termination Assembly Cable

Connections
The (TA) provides physical connection of the devices to the FDC280’s serial ports (see
Figure 3-12). TA, P0926GH, has compression screws and TA, P0926PA has ring-lugs for making
field wire connections to/from the field devices. The termination assemblies provide for:
♦ Connecting up to four RS-422 and/or RS-485 cables via screw compression or ring-
lug terminals
47
♦ Selecting termination resistor for RS-422

♦ Selecting termination resistor for RS-485 when the FDC280 is located at end of
the bus
♦ Connecting up to four RS-232 devices via DB-25 cable connectors.
♦ Selecting and switching clear-to-send, request-to-send, and other RS-232 signals
♦ Connecting an earthing point for RS-232/RS-422/RS-485 cable shields.
In an RS-485 configuration, the FDC280 can be located anywhere on the bus. If the FDC280 is
located at the end of a bus, terminators on the TA are switch selectable (terminating resistors for
the prevention of signal reflection). In an RS-422 configuration, switch selectable terminations on
the TA are available for both the transmit and/or receive cables.
Cable Termination Switches Switches for RS-232 Switches for RS-232

(Type 5) for RS-422 and RS-485 Communication Signals Communication Signals
(under cover) (under cover) (under cover)
Compression Screw DB-25

Connections for Connectors
RS-422 and RS-485 for RS-232
For Ring-Lug Connections,
see Figure 3-11
Figure 3-12. FDC280 Simplex Serial Termination Assembly
RS-422 and RS-485 Cable Connections

Any of the four serial ports of an FDC280 can be configured as RS-232, RS-422, or RS-485. The
FDC280 ports are non-redundant to support single-ported field devices. The communication
standard for each port depends on the configuration of the FDC280 ports and the field device.
RS-485, two-wire, uses a twisted pair cable with one shield. It is bidirectional (transmit and
receive are on the same pair) (see Figure 3-14 on page 50). Each RS-485 cable has a single pair
(Rx/Tx+ and Rx/Tx-).
48
RS-422 uses a four-wire shielded cable. It has a transmit pair (TxD+/TxD-), a receive pair
(RxD+/RxD-) and one shield (see Figure 3-17 on page 53).
The RS-422 and RS-485 cable connections are shown on the label of the FDC280 TA (see
Figure 3-13). Whether a port is using RS-232, RS-422 and/or RS-485 depends on the configura-
tion of the particular port and the field device. The termination assembly has four separate termi-
nals, R+, T+, R-, and T-.
Cable shields are connected to the SG terminal for each port. SG is signal ground and Sh is frame
ground. SG is the odd numbered (1, 3, 5 and 7) terminals on the TA. Sh is the even (2, 4, 6 and
8) numbered terminals on the TA.
All RS-232 communication switches for a configured RS-422 or RS-485 port should be in the
OPEN position.
Compression Screw Ring-Lug

Termination Assembly Termination Assembly
Figure 3-13. FDC280 Simplex Serial Termination Assembly Labels for RS-422 and RS-485
RS-485 cabling configurations require consideration of where the master is located on the bus.
The FDC280 can be located at the end of the bus, or it can be located at a point other than the
end of the bus. When the FDC280 is located at the end of the RS-485 bus, connected and com-
municating to 2-wire RS-485 field devices, the terminator switches should be closed. Otherwise,
the terminator switches should be open.
RS-422 configurations require device terminations at one end of the receive and transmit cables.
The terminator switches should be closed, if the field device does not have terminating resistors
on the transmit and receive cable. Otherwise, the terminator switches should be open.
49
Connecting an RS-485 Device to the FDC280 Simplex Serial

Termination Assembly
In a non-redundant system, one twisted-pair cable from/to the single ported device is connected
to compression connections on the TA. When the FDC280 is at a point along the length of the
bus (but not at either end), one twisted-pair cable from/to the next device is connected to the TA
to continue the bus to the next device. Refer to Figure 3-14. If connected to 2-wire RS-485
devices, external wiring from/to the device connects to the T+ and T- terminals. When the
FDC280 is at an end point of the bus, you should close only one terminator switch (TX switch in
the CLOSE position) for each port. For cable specifications, refer to “RS-485 and RS-422 Cable
Specifications” on page 52.
RS-485 configurations require device terminations at both ends of the bus. It is not required to
terminate all other devices on the bus.
Termination
Assembly
R+ Device
RxD/TxD-P
T+ Rx/Tx+
To/From R-
Next Device Shield grounded at
T- Rx/Tx- one end of twisted
RxD/TxD-N
pair
Figure 3-14. RS-485 (2-wire) Non-redundant Device Connection
To connect an RS-485 (2-wire) channel to the TA:

1. Route the RS-485 cable(s) through the Foxboro Evo enclosure to the TA.
2. Use strain relief wire ties on the cable(s).
3. To make the device cable connections at the FDC280 TA when the FDC280 is at a
point along the length of the bus (but not at either end point), proceed as follows:
a. Connect the receive and transmit (RxD/TxD-P) wire to T+ (Port 1, 2, 3, or 4)
and the receive and transmit (RxD/TxD-N) wire to T- (Port 1, 2, 3, or 4) com-
pression screw or ring-lug terminals as shown in Figure 3-15.
b. Connect the next device’s receive and transmit (RxD/TxD-P) wire to T+ (Port 1,
2, 3, or 4) and the receive and transmit (RxD/TxD-N) wire to T- (Port 1, 2, 3, or
4) compression screw or ring-lug terminals as shown in Figure 3-15.
c. Connect the cable shield to the SG terminal of the TA. The cable shield must be
grounded at only one end of the cable, not both. SG is the odd numbered (1, 3, 5
and 7) terminals on the TA. Sh is the even (2, 4, 6 and 8) numbered terminals on
the TA.
d. Set all RS-422/RS-485 bus termination switches for the channel to the open posi-
tion (see Figure 3-21 on page 56).
e. Set all RS-232 communication switches for a configured RS-422 or RS-485 port
to be in the OPEN position (see Figure 3-25 on page 59).
50
FBM224/230/231, Serial
Input/Output 01 02 03 04
4
Cabling C
O
Port 1 M
M
U
C02 = RxD/TxD-P N
I
B02 = RxD/TxD-N C
A
A01 = Shield T
I
Port 2 O
N
C04 = RxD/TxD-P For local termination of
cable shield, jumper SG to Sh
B04 = RxD/TxD-N R+ T+ R+ T+ R+ T+ R+ T+
A03 = Shield R- T- R- T- R- T- R- T-
SG Sh SG Sh SG Sh SG Sh
Port 3 Signal 01 02 03 04 05 06 07 08
C06 = RxD/TxD-P Connection C

B06 = RxD/TxD-N Points:
A05 = Shield C=+ B
B=-
Port 4 A = Shield A
C08 = RxD/TxD-P
B08 = RxD/TxD-N
A07 = Shield To/From To/From
Devices Devices
RxD/TxD-P RxD/TxD-P
RxD/TxD-N RxD/TxD-N
Note: Cable connections shown are for Port 1. Port 2, 3, and 4 connections
are made in a similar manner.
Figure 3-15. RS-485 (2-wire) TA Cable Connections, FDC280 Located Mid Bus
4. If the FDC280 is located at either end point of the RS-485 bus,

a. Connect the transmit/receive (RxD/TxD-P) wire to T+ (Port 1, 2, 3, or 4) and the
receive/transmit (RxD/TxD-N) wire to T- (Port 1, 2, 3, or 4) compression screw
or ring-lug terminal as shown in Figure 3-16.
b. Connect the cable shield to the SG terminal of the TA. The cable shield must be
grounded at only one end of the cable, not both. SG is the odd numbered (1, 3, 5
and 7) terminals on the TA. Sh is the even (2, 4, 6 and 8) numbered terminals on
the TA.
c. Set all RS-232 communication switches for a configured RS-422 or RS-485 port
d. Terminate the bus as described in “TA Terminations For RS-422 or RS-485” on
page 54.
51
01 02 03 04
4
C
Input/Output O
M
Cabling M
U
Port 1 N
I
C02 = RxD/TxD-P C
A
B02 = RxD/TxD-N T
I
O
A01 = Shield N
For local termination of
Port 2 cable shield, jumper SG to Sh
R+ T+ R+ T+ R+ T+ R+ T+
C04 = RxD/TxD-P R- T- R- T- R- T- R- T-
B04 = RxD/TxD-N SG Sh SG Sh SG Sh SG Sh
Signal 01 02 03 04 05 06 07 08
A03 = Shield
Connection
C
Port 3 Points:
C06 = RxD/TxD-P C=+ B
B06 = RxD/TxD-N B=-
A05 = Shield A = Shield A
Port 4
C08 = RxD/TxD-P To/From
B08 = RxD/TxD-N Devices
A07 = Shield
RxD/TxD-P
RxD/TxD-N
Note: Cable connections shown are for Port 1. Ports 2, 3, and 4 connections are made in a similar manner.
Figure 3-16. RS-485 (2-wire) TA Cable Connections, FDC280 Located at Bus End Point
RS-485 and RS-422 Cable Specifications

Cable specifications for the RS-485 and RS-422 communication interface standard are based on
the use of Type A cable (shielded twisted-pair) parameters listed in Table 3-3.
Table 3-3. RS-485 and RS-422 Cable Specifications
Impedance 135 to 165 ohms, at a frequency of 3 to 20 MHz

Capacitance 15-20 pf/ft
Loop resistance 110 ohms/km
Wire gauge 0.64 mm (22 AWG)
Conductor area > 0.33 mm2
The Type A cable (described here) is available with various protection characteristics: buried cable,
cable with PE sheath, and so on. Refer to the cable manufacturer’s specifications for details.
Connecting an RS-422 Device to the FDC280 Simplex Serial TA

In a non-redundant RS-422 system, one cable, consisting of a pair of transmit wires, a pair of
receive wires and one shield, can be connected to the compression or ring-lug connections on the
TA. See Figure 3-17. RS-422 configurations require device terminations at one end of the receive
and transmit cables. The terminator switches should be closed, if the field device does not have
terminating resistors on the transmit and receive cable. Otherwise, the terminator switches should
be open.
52
RS-422 configurations require device terminations at one end of the transmit and receive bus.
Termination Device
Assembly
T+ Rx+
T- Rx- Shield grounded at

one end of cable
R+ Tx+
R- Tx-
Figure 3-17. RS-422 Non-redundant Connection
To connect an RS-422 channel to the TA:

3. To make the device cable connections at the FDC280 TA for RS-422, proceed as fol-
lows:
a. Connect the receive cable (RxD-P and RxD-N) to T+ and T- (Port 1, 2, 3, or 4)
compression screw or ring-lug terminal as shown in Figure 3-18.
b. Connect the receive cable shield to the SG (Port 1, 2, 3, or 4) compression screw
or ring-lug terminal as shown in Figure 3-18. SG is the odd numbered (1, 3, 5
and 7) terminals on the TA.
c. Connect the transmit cable (TxD-P and TxD-N) to R+ and R- (Port 1, 2, 3, or 4)
d. Connect the transmit cable shield to the SG (Port 1, 2, 3, or 4) compression screw
f. Terminate the bus as described in “TA Terminations For RS-422 or RS-485” on
page 54.
53
Rx (Input) Cabling TX (Output) Cabling

Port 1 01 02 03 04 Port 1
C01 = RxD-P 4
C
C02 = TxD-P
B01 = RxD-N O
M
B02 = TxD-N
A01 = Shield M
U
A01 = Shield
N
Port 2 I Port 2
C
C03 = RxD-P A
T
C04 = TxD-P
B03 = RxD-N I
O
B04 = TxD-N
A03= Shield For local termination of
N A03 = Shield
Port 3 R+ T+ R+ T+ R+ T+ R+ T+ Port 3
C05 = RxD-P
R- T- R- T- R- T- R- T-
SG Sh SG Sh SG Sh SG Sh C06 = TxD-P
B05 = RxD-N Signal 01 02 03 04 05 06 07 08 B06 = TxD-N
A05= Shield Connection A05= Shield
C
Points:
Port 4 Port 4
C=+ B
C07 = RxD-P C08 = TxD-P
B=-
B07 = RxD-N B08 = TxD-N
A = Shield A
A07 = Shield A07 = Shield
To From
Device Device
RxD-P TxD-P
RxD-N TxD-N
Note: Cable connections shown are for Port 1. Port 2, 3, and 4 connections are made in a similar manner.
Figure 3-18. RS-422 TA Cable Connections
TA Terminations For RS-422 or RS-485

Eight termination resistors for an RS-422 or RS-485 bus are available on the TA to terminate the
field device or RS-485 bus. Each of the four FDC280 serial ports has a transmit and a receive
resistor that is placed across the bus/field device when the switch is switched to the CLOSE posi-
tion.
RS-485 configurations require device terminations at both ends of the bus. All other devices on
the bus segment have to not be terminated. When the FDC280 is located at either end of the bus,
it must be terminated. Figure 3-19 shows the terminating scheme for RS-485. For RS-485, the
twisted-pair cable can be terminated on the TA (Tx switch in the CLOSE position).
Figure 3-20 shows the terminating scheme for RS-422. For RS-422, both the transmit and receive
cables can be terminated on the TA (Tx and Rx switch in the CLOSE position).
♦ RS-485 configurations require device terminations at both ends of the bus. All other
devices on the bus segment have to not be terminated.
♦ RS-422 configurations require device terminations at one end of the receive and trans-
mit cables.
54
Termination Device
Assembly
R+
R-
RxD/TxD-P
Rx/Tx+
110 T+
ohms
Rx/Tx-
T- RxD/TxD-N
Shield grounded at
one end of cable
Figure 3-19. RS-485 (2-wire) Termination Resistor
Termination Device
Assembly
Rx+
T+
Rx-
T-
Tx+
110 R+
ohms
Tx-
R-
Shield grounded at
one end of cable
Figure 3-20. RS-422 Termination Resistor
To make RS-422 terminations or RS-485 bus terminations with the FDC280 located at the end
point of the bus, proceed as follows:
1. Remove the plastic housing next to the compression screws on the TA by squeezing
the plastic housing on both sides and lifting the housing.
2. Press the required termination switch on the TA to the CLOSE position (termination)
(refer to Figure 3-21 for compression screw TAs and to Figure 3-22 for ring-lug TAs)
for each cable requiring termination. This provides line termination by inserting ter-
mination resistors across the line.
3. Set unused PORTn Tx and Rx switches to the OPEN position.
4. Terminate Ports 1, 2, 3 and/or 4 (if used) in the same manner (see Figure 3-21).
55
PORT PORT PORT PORT

01 02 03 04
| | | |
Tx|Rx Tx|Rx Tx|Rx Tx|Rx
CLOSE
OPEN
PORT PORT PORT PORT

01 02 03 04
| | | |
Tx|Rx Tx|Rx TX|Rx Tx|Rx 01 08 01 08 01 08 01 08
CLOSE CLOSE CLOSE CLOSE CLOSE
C C C C
OPEN OPEN OPEN OPEN OPEN
CLOSE CLOSE CLOSE CLOSE
B B B B
OPEN OPEN OPEN OPEN
A A A A
OPEN OPEN OPEN OPEN
01 02 03 04 05 06 07 08
CABLE TYPE 5 C RS-232 RS-232
B
FBM IDENTIFICATION PORT PORT PORT PORT
01 02 03 04
A
Figure 3-21. Compression Screw TA RS-422 and RS-485 Termination Switches

PORT
Tx|Rx
04
|
PORT
Tx|Rx
03
|
PORT
Tx|Rx
02
|
PORT PORT PORT PORT

04
01 08 01 08 01 08 01 08
|

C C C C
03
|
OPEN OPEN OPEN OPEN

PORT
Tx|Rx
B B B B
02
|
01
OPEN OPEN OPEN OPEN

|

01
|
A A A A
CLOSE
OPEN
OPEN OPEN OPEN OPEN
01 02 03 04 05 06 07 08
CLOSE
OPEN
CABLE TYPE 5
B RS-232 RS-232
PORT PORT PORT PORT

FBM IDENTIFICATION
A 01 02 03 04
Figure 3-22. Ring-Lug TA RS-422 and RS-485 Termination Switches
5. Replace the plastic housing covering the termination resistors.
RS-232 Cable Connections

RS-232 devices cannot be more than 15 m (50 ft) cable length from the FDC280, per EIA stan-
dards. RS-232 uses the DB-25 connectors on the TA.
56
Each serial port of an FDC280 supports a non-redundant single ported device.
Connecting an RS-232 Port to the TA

In a non-redundant system, one input/output cable to/from the device per each FDC280 serial
port is made to the RS-232 DB-25 connectors on the TA.
Figure 3-23 shows an example of RS-232 non-redundant port and direct cabling for a single
ported device. Cabling requirements for third-party devices must be provided by the third party.
For cable standard RS-232, refer to “RS-232 Cables” on page 57.
Connects to one of the

TA RS-232 DB-25 Modem
Connectors
Modem
Network Configuration
Device
Connects to one of the

TA RS-232 DB-25 Device
Connectors
Direct Configuration
Figure 3-23. RS-232 FDC280 Direct Cabling Configuration, Example
To connect a single ported device to the TA for RS-232 communication:

1. Turn off device equipment power.
2. Determine the device to be connected and connect the appropriate cable to the
device.
3. Connect the signal cable shield at the device end (modem, programmable controller,
device, and so on) to a suitable earthing point on the device.
6. Remove the dust cover from the DB-25 connector on the TA for the port(s) (PORT
01, 02, 03, and/or 04) that is configured for RS-232 communications.
7. Connect the DB-25 connector from the device to PORT 01, 02, 03, and/or 04 female
connector.
8. Set the RS-232 switches on the TA. Refer to “TA RS-232 Switch Settings” on
page 59.
RS-232 Cables
Table 3-4 lists the cables and Figure 3-24 shows the pinouts for the standard RS-232 cables avail-
able from Foxboro.
57
Table 3-4. RS-232 Communication Cables
Cable
Option Length Cable Part No.
RS-232 VT100 20 ft RH970XD (supersedes P0970XD)
40 ft RH970WY (supersedes P0970WY)
RS-232 Modem 20 ft RH970XC (supersedes P0970XC)
40 ft RH970WX (supersedes P0970WX)
DCE (Local) 20 ft RH970XD (supersedes P0970XD)
40 ft RH970WY (supersedes P0970WY)
1
25 14
13
10"
13 1
25 14
Pinouts for RS-232 Cables

WIRE TABLE WY/WX WY/WX
WIRE WIRE A.W.G. WIRE
FROM TO
PAIR NO. SIZE COLOR
1 28 WHT/BLK N/C N/C
1
2 28 WHT/BRN N/C N/C
3 28 WHT/RED P1-2 P2-2
2
4 28 WHT/ORN P1-7 P2-7
5 28 WHT/YEL P1-3 P2-3
3
6 28 WHT/GRN P1-7 P2-7
7 28 WHT/BLU P1-4 P2-4
4
8 28 WHT/VIO P1-7 P2-7
9 28 WHT/GRY P1-5 P2-5
5
10 28 WHT/BLK/BRN P1-7 P2-7
6
11 28 WHT/BLK/RED P1-6 P2-6
12 28 WHT/BLK/ORN P1-7 P2-7
13 28 WHT/BLK/YEL NC/P1-15 NC/P2-15
7
14 28 WHT/BLK/GRN NC/P1-7 NC/P2-15
15 28 WHT/BLK/BLU P1-8 P2-8
8 WHT/BLK/VIO P1-7
16 28 P2-7
17 28 WHT/BLK/GRY N/C N/C
9 WHT/BRN/RED N/C
18 28 N/C
19 28 WHT/BRN/ORN P1-17 P2-17
10 WHT/BRN/YEL P1-7
20 28 P2-7
21 28 WHT/BRN/GRN P1-20 P2-20
11 WHT/BRN/BLU P1-7
22 28 P2-7
23 28 WHT/BRN/VIO P1-22 P2-22
12
24 28 WHT/BRN/GRY P1-7 P2-7
25 28 WHT/RED/ORN P1-24 P2-24
13 WHT/RED/YEL P1-7
26 28 P2-7
SHLD - - SHLD SHLD LUG
Figure 3-24. RH970WX/WY/XC/XD RS-232 Cables
FDC280 Simplex Serial TA RS-232 Switches

The RS-232 switches located on the TA consist of 24 switches for each port that you must config-
ure before communication between the FDC280 and its devices can begin. The switch settings
depend on the device and the cable between the switches and the device.
Figure 3-25 shows the 24 switches in four groups (PORT 01 to PORT 04). Each port has 3
switch banks with a total of 24 individual switches per port. Each switch bank A, B, and C has 8
58
switches labeled 01 to 08. The designator CLOSE indicates that the switch is closed, when the
switch is in the pressed down position.
01 08 01 08 01 08 01 08
C C C C
OPEN OPEN OPEN OPEN
B B B B
OPEN OPEN OPEN OPEN
A A A A
OPEN OPEN OPEN OPEN
PORT PORT PORT PORT

01 02 03 04
| | | |
Tx|Rx Tx|Rx Tx|Rx Tx|Rx 01 08 01 08 01 08 01 08
C C C C
B B B B
OPEN OPEN OPEN OPEN
A A A A
OPEN OPEN OPEN OPEN
01 02 03 04 05 06 07 08
B
FBM IDENTIFICATION
PORT PORT PORT PORT
01 02 03 04
A
Figure 3-25. FDC280 Simplex Serial TA RS-232 Switches
TA RS-232 Switch Settings

The TA has 24 individual switches per port that are set open or closed depending on the device,
and the type of cable. The switch settings for each of the four ports are identical. However, the
user-configured port usage (RS-422 or RS-485 versus RS-232) for each port and the cable con-
nected to the port, determines the required switch settings for each port. Figure 3-25 shows the
switches and the communication signal that is routed for each switch closure. Any switch not
closed for a given configuration is set to open (OPEN position).
Use a serial port adapter DB-9 female connector to DB-25 female connector for devices that
require a DB-9 connector. Table 3-5 correlates the DB-25 to DB-9 pin connections
Table 3-5. Serial Port Adapter Pin Connections
Female DB-9 Female DB-25

Pin Pin
1 8
2 3
3 2
4 20
5 7
59
Table 3-5. Serial Port Adapter Pin Connections (Continued)

Pin Pin
6 6
7 4
8 5
9 22
FDC280 Simplex Serial Termination Assembly RS-232 Switch

Pinout
Figure 3-26 shows the Clear (CTS) and Request-to-Send (RTS), Data Carrier Detected (DCD),
Transmit (TXD) and Receive Data (RXD) switches from the output of the DB-25 cable to the
field device. Using this figure, you can select different RS-232 switch settings for various cable
configurations. Figure 3-26 shows the switch settings for only Port 1. The switch settings for each
of the four ports, switch numbers, and pinouts are identical for each port.
Figure 3-27 shows the switch settings (only Port 1) for a standard handshake connection.
Figure 3-28 shows the switch settings (only Port 1) for a no-handshake connection. Figure 3-29
shows the switch settings (only Port 1) for a modem connection. Switch settings for Ports 2, 3,
and 4 are the same. The figures are examples and show general switch settings. Refer to the ven-
dors document to understand the communication requirements for a particular device and then
set the switches accordingly.
60
C-06
A-05
RTS 5 12 CTS
5
A-07
A-06
A-06 7 10 GND
7
6 11
CTS
A-08
B-01 8 9
1 16 RTS
4
B-06
B-02 6 11
B-04
2 15 DCD/RXD+ 4 13 DTR
20
B-03 B-07
B-05 7 10
3 14 11
5 12 DCD
8
A-01
TXD 1 16 TXD B-08
2 C-01 8 9
DTR 1 16 DSR
A-02 6
2 15 RXD
3 C-02
2 15 C-03
A-03 3 14 GND
RXD C-05 7
3 14 5 12
C-04
A-04 4 13
4 13 13
NOTES:
1. Numbers in circles are DB-25 connector pin numbers.
2. Pin numbers for switches are the same for each port.
3. Switch numbers for each port are shown in the following table:
Port 1 Port 2 Port 3 Port 4

C C C C
B B B B
A A A A
4. See Table 3-5 for Port Adapter DB-25 to DB-9 pin connections.
5. Switches C-07 and C-08 are not used and can be in any position (CLOSED or OPEN).
Figure 3-26. RS-232 TA Switches
61
TA RS-232 Switch Assembly

TA
Cable DB-25
TXD TXD 2
A-02
RXD RXD 3
A-04
RTS RTS 4
A-05 D
CTS 5 E
B-02 CTS
V
6 I
DTR DSR
C-01 C
E
GND 7
GND
DCD B-08 DCD 8
B-04 20
Closed switches. DTR
Only Port 1 switches shown.
Figure 3-27. RS-232 Switches, Null Modem - Standard Handshake
TA TA RS-232 Switch Assembly

DB-25
Cable
TXD A-02 TXD 2
RXD RXD 3
A-04
RTS RTS 4
A-06 A-08 D
CTS CTS 5 E
V
DSR 6 I
GND
B-08 C
DCD 7 E
GND
C-05 8
DCD
DTR
B-06
DTR 20
Closed switches.
No handshaking or carrier detect
Figure 3-28. RS-232 Switches, Null Modem - No Handshake
NOTE
Partial handshakes can be provided by combinations of the configurations shown in
Figure 3-27 and Figure 3-28. Refer to device documentation for specific device
requirements.
62

TA
Cable DB-25
2
TXD A-01 TXD
3
RXD A-03 RXD
RTS 4
B-01 RTS
D
CTS 5 E
B-03 CTS
V
6 I
DSR DSR C
E
GND GND 7
DCD 8
B-05 DCD
DTR C-02 20
DTR
Closed switches.
Figure 3-29. RS-232 Switches, Modem Connection (Typical)
FDC280 Fault Tolerant Serial Termination Assembly

Installation
A typical FDC280 fault tolerant serial termination assembly installation is shown in Figure 3-30.
The termination assemblies (TAs) connect to the baseplate by means of termination cables. The
FDC280 fault tolerant serial installation is identical to the FDC280 simplex serial installation,
except that there are two modules, two termination assemblies, two termination cables, and two
cables to the redundant field device. The FDC280 fault tolerant serial termination cables and ter-
mination assemblies are identical to the FDC280 simplex serial termination cable and TA.
NOTE
For all Ethernet and serial cabling coming from the FDC280 baseplate, it is recom-
mended that you label this cabling depending on whether it will support communi-
cations from the Left or Right FDC280s.
63
Type 5
Termination
Cables(2)
Termination
Assemblies (2)
RS-232 Cables To Field Devices

Figure 3-30. FDC280 Fault Tolerant Serial Port Termination Assemblies
The part numbers for the associated termination assemblies are listed in Table 1-1. Use the Com-
pact Type 5 cables in Table 3-6 to connect the FDC280’s baseplate to each termination assembly.
Table 3-6 lists the available lengths and part numbers for Type 5 communication cables for the
FDC280.
Table 3-6. Termination Cables (Type 5) for FDC280 Fault Tolerant Serial Installations
Cable Part Number Length

RH100HV 1.0m (3.2 ft)
RH100HW 1.5m (4.9 ft)
RH100HX 2.0m (6.6 ft)
RH100HY 3.0m (9.8 ft)
RH100HZ 5.0m (16.4 ft)
FDC280 Fault Tolerant Serial Termination Assemblies Installation

Install the two FDC280 fault tolerant serial termination assemblies per the installation instruc-
tions in Standard and Compact 200 Series Subsystem User’s Guide (B0400FA).
The following subsection describes how to make the device cable connections to the termination
assemblies.
FDC280 Fault Tolerant Serial Termination Assembly Cable

Connections
Each of the termination assemblies provide physical connection for each port of a dual ported
device to the FDC280 serial ports (see Figure 3-31). TA, P0926GH, has compression screws and
TA, P0926PA has ring-lugs for making field wire connections to/from the field devices. Each of
the two TAs provide for:
♦ Connecting up to four RS-422 and/or RS-485 cables via screw compression or ring-
lug terminals
64
♦ Selecting termination resistor for RS-422

♦ Selecting termination resistor for RS-485 when the FDC280 is located at end of
the bus
♦ Connecting up to four RS-232 devices via DB-25 cable connectors.
♦ Selecting and switching clear-to-send, request-to-send, and other RS-232 signals
♦ Connecting an earthing point for RS-232/RS-422/RS-485 cable shields.
In an RS-485 configuration, the FDC280 can be located anywhere on the bus. If the FDC280 is
located at the end of a bus, terminators on the TA are switch selectable (terminating resistors for
the prevention of signal reflection). In an RS-422 configuration, switch selectable terminations on
the TA are available for both the transmit and/or receive cables.
Cable Termination Switches Switches for RS-232 Switches for RS-232

(Type 5) for RS-422 and RS-485 Communication Signals Communication Signals
(under cover) (under cover) (under cover)
Compression Screw DB-25

Connection for Connectors
RS-422 and RS-485 for RS-232
For Ring-Lug Connection,
See Figure 3-37.
Figure 3-31. FDC280 Fault Tolerant Serial Termination Assembly (One Shown)
RS-422 and RS-485 Cable Connections

Each of the four redundant serial ports of the FDC280 can be RS-232, RS-422 or RS-485. The
FDC280 serial ports are redundant to support dual ported devices. The communication standard
for each redundant port depends on the configuration of the FDC280 serial ports and the field
device.
RS-485, two-wire, uses a twisted pair cable with one shield. It is bidirectional (transmit and
receive are on the same pair) (see Figure 3-33 on page 67). Each RS-485 cable has a single pair
(Rx/Tx+ and Rx/Tx-).
65
RS-422 uses a four-wire shielded cable. It has a transmit pair (TxD+/TxD-), a receive pair
(RxD+/RxD-) and one shield (see Figure 3-37 on page 71).
The RS-422 and RS-485 cable connections are shown on the label of each or the FDC280 fault
tolerant serial TAs (see Figure 3-31). As indicated on the label for each TA, an FDC280 has four
separate serial communication ports. Whether a port is using RS-232, RS-422 and/or RS-485
depends on the configuration of the particular port and the field device. Each termination assem-
bly has four separate terminals, R+, T+, R-, and T-.
Cable shields are connected to the SG terminal for each port. SG is signal ground and Sh is frame
ground. SG is the odd numbered (1, 3, 5 and 7) terminals on the TA. Sh is the even (2, 4, 6 and
8) numbered terminals on the TA.
All RS-232 communication switches for a configured RS-422 or RS-485 port should be in the
OPEN position.
Compression Screw Termination Ring-Lug Termination

Label and Connections Label and Connections
Figure 3-32. FDC280 Fault Tolerant Serial Termination Assembly Label (One Shown) for RS-422 and
RS-485
RS-485 cabling configurations require consideration of where the master is located on the bus.
The FDC280 can be located at the end of the bus, or it can be located at a point other than the
end of the bus. When the FDC280 is located at the end of the RS-485 bus, connected and com-
municating to 2-wire RS-485 field devices, the terminator switches should be closed. Otherwise,
the terminator switches should be open.
The terminator switches should be closed, if the field device does not have terminating resistors
on the transmit and receive cable. Otherwise, the terminator switches should be open.
66
Connecting an RS-485 Device to the FDC280 Fault Tolerant

Serial TA
In a redundant system, one twisted-pair cable from/to each port of the dual ported device is con-
nected to compression connections on each TA. When the FDC280 is at a point along the length
of the bus (but not at either end), one twisted-pair cable from/to the next device is connected to
the TA to continue the bus to the next device. Refer to Figure 3-33. If connected to 2-wire RS-
485 devices, external wiring from/to the device connects to the T+ and T- terminals. When the
FDC280 is at an end point of the bus, you should close only one terminator switch (TX switch in
the CLOSE position) for each redundant port. For cable specifications, refer to “RS-485 and RS-
422 Cable Specifications” on page 52.
the bus have to not be terminated.
Termination
Assembly
(Left) Device
R+
(Port 1)
RxD/TxD-P
T+ Rx/Tx+
To/From R-
(Port 1) T- Rx/Tx-
RxD/TxD-N one end of twisted
pair
Termination
Assembly
(Right) Device
R+
(Port 2)
RxD/TxD-P
T+ Rx/Tx+
To/From R-
(Port 2) T- Rx/Tx-
RxD/TxD-N one end of twisted
pair
Figure 3-33. RS-485 (2-wire) Fault Tolerant FDC280 to Dual-Ported Devices Connection
67
Termination
Assembly
(Left) Device
R+
RxD/TxD-P
T+ Rx/Tx+
To/From R-
T- Rx/Tx- one end of twisted
RxD/TxD-N
pair
Termination
This is a single-ported device
Assembly with only one RS-485 Port.
(Right)
R+
RxD/TxD-P
T+
R-
T-
RxD/TxD-N
Figure 3-34. RS-485 (2-wire) Fault Tolerant FDC280 to Single-Ported Devices Connection
To connect an RS-485 (2-wire) channel to the TA:

3. To make the device cable connections at the FDC280 fault tolerant serial TA when
the FDC280 is at a point along the length of the bus (but not at either end point),
proceed as follows:
a. Connect the receive and transmit (RxD/TxD-P) wire to T+ (Port 1, 2, 3, or 4)
and the receive and transmit (RxD/TxD-N) wire to T- (Port 1, 2, 3, or 4) com-
pression screw or ring-lug terminals as shown in Figure 3-35.
b. Connect the next device’s receive and transmit (RxD/TxD-P) wire to T+ (Port 1,
2, 3, or 4) and the receive and transmit (RxD/TxD-N) wire to T- (Port 1, 2, 3, or
4) compression screw or ring-lug terminals as shown in Figure 3-35.
c. Connect the cable shield to the SG terminal of the TA. The cable shield must be
grounded at only one end of the cable, not both. Sh is the even (2, 4, 6 and 8)
numbered terminals on the TA.
d. Set all RS-422/RS-485 bus termination switches for the channel to the open posi-
tion (see Figure 3-44 and Figure 3-45 on page 77).
68
Input/Output
Cabling
Port 1 FBM224/230/231, Serial
01 02 03 04
4
C02 = RxD/TxD-P C
B02 = RxD/TxD-N O
M
A01 = Shield M
U
N
Port 2 I
C
C04 = RxD/TxD-P A
T
B04 = RxD/TxD-N I
O
A03 = Shield N
Port 3 R+ T+ R+ T+ R+ T+ R+ T+
B06 = RxD/TxD-N Signal 01 02 03 04 05 06 07 08
A05 = Shield Connection C
Port 4 Points:
B08 = RxD/TxD-N B=-
To/From To/From
Devices Devices
RxD/TxD-P RxD/TxD-P
RxD/TxD-N RxD/TxD-N
Figure 3-35. RS-485 (2-wire) TA Cable Connections (One Shown), FDC280 Located Mid Bus
4. If the FDC280 is located at either end point of the RS-485 bus,

a. Connect the transmit/receive (RxD/TxD-P) wire to T+ (Port 1, 2, 3, or 4) and the
receive/transmit (RxD/TxD-N) wire to T- (Port 1, 2, 3, or 4) compression screw
b. Connect the cable shield to the SG terminal of the TA. The cable shield must be
grounded at only one end of the cable, not both. Sh is the even (2, 4, 6 and 8)
numbered terminals on the TA.
c. Set all RS-232 communication switches for a configured RS-422 or RS-485 port
d. Terminate the bus as described in “TA Terminations For RS-422 or RS-485” on
page 73.
5. Repeat Steps 1 through 4 for the redundant channel to the redundant device.
69
01 02 03 04
4
C
Input/Output O
M
Cabling M
U
Port 1 N
I
C
C02 = RxD/TxD-P A
T
B02 = RxD/TxD-N I
O
A01 = Shield N
Port 2 cable shield, jumper SG to Sh
R+ T+ R+ T+ R+ T+ R+ T+
B04 = RxD/TxD-N Signal 01 02 03 04 05 06 07 08
A03 = Shield Connection
C
Port 3 Points:
B06 = RxD/TxD-N B=-
Port 4
To/From
C08 = RxD/TxD-P
B08 = RxD/TxD-N Devices
A07 = Shield
RxD/TxD-P
RxD/TxD-N
Note: Cable connections shown are for Port 1. Ports 2, 3, and 4 connections are made in a similar manner.
Figure 3-36. RS-485 (2-wire) TA Cable Connections (One Shown),
FDC280 Located at Bus End Point
Connecting an RS-422 Device to the FDC280 Fault Tolerant

Serial TA
In a redundant RS-422 system, two cables, each consisting of a pair of transmit wires, a pair of
receive wires and one shield, can be connected to the compression or ring-lug connections on each
TA of the redundant channel. See Figure 3-37. RS-422 configurations require device terminations
at one end of the receive and transmit cables. The terminator switches should be closed, if the
field device does not have terminating resistors on the transmit and receive cable. Otherwise, the
terminator switches should be open.
RS-422 configurations require device terminations at one end of the transmit and receive bus.
Also refer to Figure 1-10 on page 22.
70
Dual-Ported Device
Termination Device
Assembly (Port 1)
(Left) T+ Rx+

one end of cable
R+ Tx+
R- Tx-
Termination Device
Assembly (Port 2)
(Right) T+ Rx+

one end of cable
R+ Tx+
R- Tx-
Figure 3-37. RS-422 (4-Wire) Fault Tolerant FDC280 to Dual-Ported Device Connections
Single-Ported Device
Termination Device
Assembly (Port 1)
(Left) T+ Rx+

one end of cable
R+ Tx+
R- Tx-
Termination
Assembly
(Right) T+
T-
R+
R-
Figure 3-38. RS-422 (4-Wire) Fault Tolerant FDC280 to Single-Ported Device Connections
71
To connect an RS-422 channel to the TA:

3. To make the device cable connections at the FDC280 fault tolerant serial TA for
RS-422, proceed as follows:
a. Connect the receive cable (RxD-P and RxD-N) to T+ and T- (Port 1, 2, 3, or 4)
b. Connect the receive cable shield to the SG (Port 1, 2, 3, or 4) compression screw
c. Connect the transmit cable (TxD-P and TxD-N) to R+ and R- (Port 1, 2, 3, or 4)
d. Connect the transmit cable shield to the SG (Port 1, 2, 3, or 4) compression screw
terminal as shown in Figure 3-39.
f. Terminate the bus as described in “TA Terminations For RS-422 or RS-485” on
page 73.
g. Repeat Steps 1 through 3 for the redundant channel to the redundant device.
Rx (Input) Cabling TX (Output) Cabling

Port 1 01 02 03 04 Port 1
C01 = RxD-P 4
C
C02 = TxD-P
B01 = RxD-N O
M
B02 = TxD-N
A01 = Shield M
U
A01 = Shield
N
Port 2 I Port 2
C
C03 = RxD-P A
T
C04 = TxD-P
B03 = RxD-N I
O
B04 = TxD-N
A03= Shield For local termination of
N A03 = Shield
Port 3 R+ T+ R+ T+ R+ T+ R+ T+ Port 3
C05 = RxD-P
R- T- R- T- R- T- R- T-
SG Sh SG Sh SG Sh SG Sh C06 = TxD-P
B05 = RxD-N Signal 01 02 03 04 05 06 07 08 B06 = TxD-N
A05= Shield Connection A05= Shield
C
Points:
Port 4 Port 4
C=+ B
C07 = RxD-P C08 = TxD-P
B=-
B07 = RxD-N B08 = TxD-N
A = Shield A
A07 = Shield A07 = Shield
To From
Device Device
RxD-P TxD-P
RxD-N TxD-N
Figure 3-39. RS-422 TA Cable Connections (One Channel Shown)
72
TA Terminations For RS-422 or RS-485

Eight termination resistors for an RS-422 or RS-485 bus are available on the TA to terminate the
field device or RS-485 bus. Each of the four FDC280 serial ports has a transmit and a receive
resistor that is placed across the bus/field device when the switch is switched to the CLOSE posi-
tion.
the bus segment have to not be terminated. When the FDC280 is located at either end of the bus,
it must be terminated. Figure 3-40 shows the terminating scheme for RS-485. For RS-485, the
twisted-pair cable can be terminated on the TA (Tx switch in the CLOSE position).
Figure 3-42 shows the terminating scheme for RS-422. For RS-422, both the transmit and receive
cables can be terminated on the TA (Tx and Rx switch in the CLOSE position).
♦ RS-485 configurations require device terminations at both ends of the bus. All other
devices on the bus segment have to not be terminated.
♦ RS-422 configurations require device terminations at one end of the receive and trans-
mit cables.
Dual-Ported Device
Termination Device
Assembly (Port 1)
(Left)
End of bus R+
should be closed
R-
RxD/TxD-P
Rx/Tx+
110 T+
ohms
Rx/Tx-
T- RxD/TxD-N
Shield grounded at
one end of cable
Termination Device
Assembly (Port 2)
(Right)
End of bus R+
should be closed
R-
RxD/TxD-P
Rx/Tx+
110 T+
ohms
Rx/Tx-
T- RxD/TxD-N
Shield grounded at
one end of cable
Figure 3-40. RS-485 (2-wire) Termination Resistor for Fault-Tolerant FDC280 to Dual-Ported Device
73
Termination Device
Assembly (Port 1)
(Left)
R+
Should stay open
R-
RxD/TxD-P
Rx/Tx+
110 T+
ohms
Rx/Tx-
T- RxD/TxD-N
Shield grounded at
one end of cable
Termination
Assembly
(Right)
End of bus R+
should be closed
R-
RxD/TxD-P
110 T+
ohms
T- RxD/TxD-N
Figure 3-41. RS-485 (2-wire) Termination Resistor for Fault-Tolerant FDC280 to Single-Ported
Device
74
Dual-Ported Device
Termination Device
Assembly (Port 1)
(Left) Rx+
T+
Should be closed
Rx-
T-
Tx+
110 R+
ohms
Tx-
R-
Shield grounded at
one end of cable
Termination Device
Assembly (Port 2)
(Right) Rx+
T+
Should be closed
Rx-
T-
Tx+
110 R+
ohms
Tx-
R-
Shield grounded at
one end of cable
Figure 3-42. RS-422 Termination Resistors for Fault-Tolerant FDC280 Connected to Dual-Ported
Device
75
Termination Device
Assembly (Port 1)
(Left) Rx+
T+
Rx-
T-
Tx+
110 R+
ohms
Tx-
R-
Shield grounded at
one end of cable
Termination
Assembly
(Right)
T+
Should be closed
T-
110 R+
ohms
R-
Figure 3-43. RS-422 Termination Resistors for Fault-Tolerant FDC280 Connected to Single-Ported
Device
To make bus terminations with the FDC280 located at the end point of the bus, proceed as
follows:
1. Remove the plastic housing next to the compression screws on the TA by squeezing
the plastic housing on both sides and lifting the housing.
2. Press the required termination switch on the TA to the CLOSE position (termination)
(refer to Figure 3-44 for compression screw TAs and Figure 3-45 for ring-lug TAs) for
each cable requiring termination. This provides line termination by inserting termina-
tion resistors across the line.
3. Set unused PORTn Tx and Rx switches to the OPEN position.
4. Terminate Ports 1, 2, 3 and/or 4 (if used) in the same manner (see Figure 3-44 or
Figure 3-45).
76
PORT PORT PORT PORT

01 02 03 04
| | | |
CLOSE
OPEN
PORT PORT PORT PORT

01 02 03 04
| | | |
Tx|Rx Tx|Rx TX|Rx Tx|Rx 01 08 01 08 01 08 01 08
C C C C
B B B B
OPEN OPEN OPEN OPEN
A A A A
OPEN OPEN OPEN OPEN
01 02 03 04 05 06 07 08
B
FBM IDENTIFICATION PORT PORT PORT PORT
01 02 03 04
A
Figure 3-44. Compression Screw TA RS-422 and RS-485 Termination Switches

PORT
Tx|Rx
04
|
PORT
Tx|Rx
03
|
PORT
Tx|Rx
02
|
PORT PORT PORT PORT

04
01 08 01 08 01 08 01 08
|

C C C C
03
|
OPEN OPEN OPEN OPEN

PORT
Tx|Rx
B B B B
02
|
01
OPEN OPEN OPEN OPEN

|

01
|
A A A A
CLOSE
OPEN
OPEN OPEN OPEN OPEN
01 02 03 04 05 06 07 08
CLOSE
OPEN
CABLE TYPE 5
B RS-232 RS-232
PORT PORT PORT PORT

FBM IDENTIFICATION
A 01 02 03 04
Figure 3-45. Ring-Lug TA RS-422 and RS-485 Termination Switches
5. Replace the plastic housing covering the termination resistors.
RS-232 Cable Connections

Each of the redundant four serial ports of the FDC280 can be RS-232, RS-422 or RS-485. Each
redundant port of an FDC280 supports dual ported devices depending on the configuration of
the FDC280 ports and the devices.
77
RS-232 devices cannot be more than 15 m (50 ft) cable length from the FDC280, per EIA stan-
dards. RS-232 uses the DB-25 connectors on the TA.
Connecting an RS-232 Port to the TA

In a redundant system, two input/output cables to/from the device per each FDC280 serial port is
made to the RS-232 DB-25 connectors on the TA.
The following figures (Figure 3-46 and Figure 3-47), show examples of RS-232 cabling for dual
ported devices. Each DB-25 cable from/to the device connects to the Port 01 (02, 03, or 04) of
one TA of the FDC280 pair and the other cable connects to same port (01, 02, 03, or 04) of the
other TA of the other FDC280 pair. Cabling requirements for third-party devices must be pro-
vided by the third party.
Connecting a dual ported device to the TA for RS-232 communication is the same as connecting
a single ported device to the TA as described above, except that the connections are made for each
port of the dual ported device. See Figure 1-10 on page 22. For standard RS-232 cables, refer to
“RS-232 Cables” on page 57. Also for single-ported RS-232 devices, use the Y-cables listed in
Table 3-7.
Table 3-7. RS-232 Communication Cables, Single Ported Device to Two TAs (Fault Tolerant FDC280)
Option Length Cable Part Number

RS-232 Y-Cable 6m (20 ft) RH100MM
12m (40 ft) RH100MP
Modem
Connects to one of four
RS-232 DB-25 Modem
Connectors on one TA
Device
Connects to same
RS-232 DB-25 Modem
Connector on redundant TA
Modem
Both ports of the device must have the same address

Figure 3-46. RS-232 FDC280 Redundant Cabling Configuration, Example
78
Connects to one of four

RS-232 DB-25
Connectors on one TA
Device
Connects to same
RS-232 DB-25
Connector on redundant TA
Both ports of the device must have the same address
Figure 3-47. RS-232 FDC280 Redundant Cabling Configuration, Example
To connect a dual ported device to the TA for RS-232 communication:

1. Turn off device equipment power.
2. Determine the device to be connected and connect the appropriate cable to the
device.
3. Connect the signal cable shield at the device end (modem, programmable controller,
device, and so on) to a suitable earthing point on the device.
6. Remove the dust cover from the DB-25 connector on the TA for the port(s) (PORT
01, 02, 03, and/or 04) that is configured for RS-232 communications.
7. Connect the DB-25 connector from the device to PORT 01, 02, 03, and/or 04 female
connector.
8. Set the RS-232 switches on the TA. Refer to “TA RS-232 Switch Settings” on
page 80.
9. Repeat steps 1 through 9 for the redundant, or dual port, of the device.
Connecting a Single-Ported RS-232 Device to Fault Tolerant

FDC280
As shown in Figure 1-10 on page 22, use the Y-cable to connect the device to the two termination
assemblies. Use the Y-cables listed in Table 3-7 “RS-232 Communication Cables, Single Ported
Device to Two TAs (Fault Tolerant FDC280)” on page 78.
FDC280 Fault Tolerant Serial TA RS-232 Switches

The RS-232 switches located on each TA consist of 24 switches for each port that you must con-
figure before communication between the FDC280 and its devices can begin. The switch settings
depend on the device and the cable between the switches and the device.
Figure 3-48 shows the 24 switches in four groups (PORT 01 to PORT 04). Each port has 3
switch banks with a total of 24 individual switches per port. Each switch bank A, B, and C has 8
switches labeled 01 to 08. The designator CLOSE indicates that the switch is closed, when the
switch is in the pressed down position.
79
01 08 01 08 01 08 01 08
C C C C
OPEN OPEN OPEN OPEN
B B B B
OPEN OPEN OPEN OPEN
A A A A
OPEN OPEN OPEN OPEN
PORT PORT PORT PORT

01 02 03 04
| | | |
Tx|Rx Tx|Rx Tx|Rx Tx|Rx 01 08 01 08 01 08 01 08
C C C C
B B B B
OPEN OPEN OPEN OPEN
A A A A
OPEN OPEN OPEN OPEN
01 02 03 04 05 06 07 08
B
FBM IDENTIFICATION
PORT PORT PORT PORT
01 02 03 04
A
Figure 3-48. FDC280 Fault Tolerant Serial TA RS-232 Switches
TA RS-232 Switch Settings

Each TA has 24 individual switches per port that are set open or closed depending on the device,
and the type of cable. The switch settings for each of the four ports are identical. However, the
user-configured port usage (RS-422 or RS-485 versus RS-232) for each port and the cable con-
nected to the port, determines the required switch settings for each port. Figure 3-49 shows the
switches and the communication signal that is routed for each switch closure. Any switch not
closed for a given configuration is set to open (OPEN position).
Use a serial port adapter DB-9 female connector to DB-25 female connector for devices that
require a DB-9 connector. Table 3-8 correlates the DB-25 to DB-9 pin connections
Table 3-8. Serial Port Adapter Pin Connections

Pin Pin
1 8
2 3
3 2
4 20
5 7
6 6
80
Table 3-8. Serial Port Adapter Pin Connections (Continued)

Pin Pin
7 4
8 5
9 22
FDC280 Fault Tolerant Serial Termination Assembly RS-232

Switch Pinout
Figure 3-49 shows the Clear (CTS) and Request-to-Send (RTS), Data Carrier Detected (DCD),
Transmit (TXD) and Receive Data (RXD) switches from the output of the DB-25 cable to the
field device. Using this figure, you can select different RS-232 switch settings for various cable
configurations. Figure 3-49 shows the switch settings for only Port 1. The switch settings for each
of the four ports, switch numbers, and pinouts are identical for each port.
Figure 3-50 shows the switch settings (only Port 1) for a standard handshake connection.
Figure 3-51 shows the switch settings (only Port 1) for a no-handshake connection. Figure 3-52
shows the switch settings (only Port 1) for a modem connection. Switch settings for Ports 2, 3,
and 4 are the same. The figures are examples and show general switch settings. You should refer to
the vendors document to understand the communication requirements for a particular device and
then set the switches accordingly.
Partial handshakes can be provided by combinations of the configurations shown in Figure 3-50
and Figure 3-51. Refer to device documentation for specific device requirements.
81
C-06
A-05
RTS 5 12 CTS
5
A-07
A-06
A-06 7 10 GND
7
6 11
CTS
A-08
B-01 8 9
1 16 RTS
4
B-06
B-02 6 11
B-04
2 15 DCD/RXD+ 4 13 DTR
20
B-03 B-07
B-05 7 10
3 14 11
5 12 DCD
8
A-01
TXD 1 16 TXD B-08
2 C-01 8 9
DTR 1 16 DSR
A-02 6
2 15 RXD
3 C-02
2 15 C-03
A-03 3 14 GND
RXD C-05 7
3 14 5 12
C-04
A-04 4 13
4 13 13
NOTES:
1. Numbers in circles are DB-25 connector pin numbers.
2. Pin numbers for switches are the same for each port.
3. Switch numbers for each port are shown in the following table:
Port 1 Port 2 Port 3 Port 4

C C C C
B B B B
A A A A
4. See Table 3-5 for Port Adapter DB-25 to DB-9 pin connections.
5. Switches C-07 and C-08 are not used and can be in any position (CLOSED or OPEN).
Figure 3-49. RS-232 TA Switches
82

TA
Cable DB-25
TXD TXD 2
A-02
RXD RXD 3
A-04
RTS RTS 4
A-05 D
CTS 5 E
B-02 CTS
V
6 I
DTR DSR
C-01 C
E
GND 7
GND
DCD B-08 DCD 8
B-04 20
DTR
Closed switches.
Figure 3-50. RS-232 Switches, Null Modem - Standard Handshake
TA TA RS-232 Switch Assembly

DB-25
Cable
TXD A-02 TXD 2
RXD RXD 3
A-04
RTS RTS 4
A-06 A-08 D
CTS CTS 5 E
V
DSR 6 I
GND
B-08 C
DCD 7 E
GND
C-05 8
DCD
DTR
B-06
DTR 20
Closed switches.
No handshaking or carrier detect
Figure 3-51. RS-232 Switches, Null Modem - No Handshake
83
TA
Cable DB-25
2
TXD A-01 TXD
3
RXD A-03 RXD
RTS 4
B-01 RTS
D
CTS 5 E
B-03 CTS
V
6 I
DSR DSR C
E
GND GND 7
DCD 8
B-05 DCD
DTR C-02 20
DTR
Closed switches.
Figure 3-52. RS-232 Switches, Modem Connection (Typical)
Boot-Up Sequence
The boot up sequence for the FDC280 has the following typical cases:
♦ Case 1: Rebooting a commissioned FDC280 module.
♦ Case 2: Connecting a non-self-hosting module with the same letterbug to the base-
plate with the Ethernet network cables connected.
♦ Case 3: Connecting a non-self-hosting module with a new letterbug to the baseplate
with the Ethernet network cables connected.
♦ Case 4: Connecting a shadow module with the same software image to the baseplate,
after the primary module has booted up, loaded the checkpoint file, and initialized
on-control.
♦ Case 5: Connecting a shadow module with a different software image to the baseplate,
after the primary module has booted up, loaded the checkpoint file, and initialized
on-control.
♦ Case 6: Powering up an FDC280 baseplate with different software images in the Left
and Right FDC280 in a fault tolerant pair.
♦ Case 7: Powering up an FDC280 baseplate with fault-tolerant FDC280s with the
same software image
The boot up sequence for each of the above cases are described in the following sections.
For procedures to assign the letterbug to an FDC280, refer to “Setting the Letterbug” on page 37.
For FDC280s in self-hosting mode, a 14 second delay occurs before the module attempts to
download its checkpoint file from flash memory.
84
Case 1 – Rebooting a Commissioned FDC280

When a Reboot command is issued to a commissioned FDC280 running non-fault tolerant, the
operational sequence is as follows:
1. The FDC280 lights the red Operational Status LED while running the start-up
diagnostics. The LCD is solid white (blank).
2. If the start-up diagnostics test results are OK, the FDC280 lights the red and green
Operational Status LEDs and performs other internal tests. While the red and green
LEDs are on, the LCD shows “<CP letterbug> UNKNOWN” on line 1, with “Marriage
Wait” soon added on line 2.
3. If the internal test results are OK, the FDC280 lights the green Operational Status
LED and turns off the red LED, and the LCD shows “<CP letterbug> Single”1 on
line 1. The LCD begins a rotating display of 4 different lines of information - see
“Typical Messages During Normal Operation” in B0700AF. If any of the startup tests
are not successful, the LCD shows a detected error message (refer to “Error Messages
Following Start-up Diagnostics” in Control Core Service V9.x System Error Messages
(B0700AF)) and the LEDs are left as red on and green off.
4. In non-self-hosting mode, the FDC280 loads the checkpoint file (control database)
from the host server.
In self-hosting mode, the FDC280 either loads the checkpoint file (control database)
from the host server and performs a checkpoint operation if it does not have the
checkpoint file in flash memory, or it loads the checkpoint file from its internal flash
memory if the file is present.
5. The FDC280 initializes on-control as defined by the control database.
Case 2 – Connecting an FDC280 with the Same Letterbug

When connecting to the baseplate a non-self-hosting FDC280 module with the same letterbug as
the removed module, with the control network cables connected, the operational sequence is the
same as for Case 1.
The FDC280 reboots, loads the checkpoint file from the host, and initializes on-control as
described in Steps 1 through 5 in Case 1.
1. Forbrevity, steps within this case are referenced by the descriptions of the subsequent cases. If the
rebooted FDC280 is running as fault tolerant, “Primary” or “Shadow” is displayed on the LCD
instead of “Single”.
85
NOTICE
Make sure you assign the correct FDC280 letterbug before connecting
the Ethernet fiber optic cables to the FDC280. This avoids potential
process control safety issues if a letterbug has previously been
assigned to the module. Label space is provided on the front of the
module to record the letterbug.
Also, when replacing a non-fault tolerant FDC280 set to self-hosting
mode, change the letterbug to a non-configured letterbug and then to
its hosted letterbug. This helps ensure the correct letterbug is
configured and there is no valid checkpoint file in flash.
Without following this order, the letterbug is configured for that module
may not match the letterbug expected by the host.

damage.
Case 3 – Connecting an FDC280 with a New Letterbug

A “new letterbug” is a letterbug for a station which has not been commissioned to date.
If the letterbug of an FDC280 is changed, the checkpoint file in flash memory is invalidated. The
next time the FDC280 reboots, it will load the checkpoint file from the host workstation.
When installing a non self-hosting FDC280 on its baseplate with a new letterbug and the control
network cables connected, the operational start-up sequence is as follows:
1. The FDC280 boots up as described in Steps 1 through 3 in Case 1.
2. The FDC280 loads the network addresses from the host server.
3. The FDC280 reboots, loads the checkpoint file from the host, and initializes on-con-
trol as described in Steps 1 through 5 in Case 1.
Case 4 – Connecting a Shadow Module with Same Software

Image
When connecting a shadow FDC280 module with the same software image as the primary mod-
ule to the baseplate – after the primary FDC280 module has booted up, loaded the checkpoint
file, and initialized on-control – the operational sequence is as follows:
1. The shadow module boots up as described in Steps 1 through 3 in Case 1.
2. If the FDC280 is in self-hosting mode and the checkpoint file in flash of the shadow
module differs from the checkpoint file in flash of the primary module or the shadow
module lacks a checkpoint file, the shadow module turns on the red Operational Sta-
tus LED while the green LED remains on.
3. If the FDC280 is in self-hosting mode, the primary module sends its checkpoint file
to the shadow module which writes it into its own flash memory.
86
If the checkpoint operation succeeds, messages similar to the following examples are
sent to the SMON log:
2008-01-21 13:53:11 FP0101 Process = Flash Loader RDHSS 000131 -
Shadow Checkpoint update Needed
Shadow Checkpoint File Sent
These messages are sent by the primary module and only indicate that the primary has
sent the checkpoint file to the shadow module. The shadow module still has to write
the checkpoint file to its flash, which could take more than a minute.
If the checkpoint operation is not successful, messages similar to these examples are
sent to the SMON log by the primary module:
Shadow Checkpoint Incomplete - Reboot Shadow
Then, one of two scenarios will occur:
♦ The shadow module will reboot automatically to reinitiate the marriage process.
♦ The shadow module will remain in the red/green LED state and not reboot. In
this scenario, you must reboot the Shadow module manually to restart the mar-
riage process.
4. If the FDC280 is in self-hosting mode, the shadow module boots up again as
5. If the letterbug of the shadow module differs from the primary module, the shadow
copies the primary’s letterbug to flash memory and reboots.
6. The shadow module marries the primary module, as indicated by the single, simulta-
neous quick flashing of the red Operational Status LED on both modules, then the
modules run fault tolerant.
The marriage should occur within 10 seconds, except for the following conditions
when the station is in self-hosting mode:
♦ If the primary module (in Single Primary mode) is downloading the checkpoint
file from flash memory, the marriage will be held off until the download is com-
plete. The shadow module's LEDs will remain green while it waits for the mar-
riage to occur.
♦ If the primary module (in Single Primary mode) is performing a checkpoint,
which includes a write to its flash, the marriage will be held off until the check-
point operation is complete. The shadow module's LEDs will remain green while
it waits for the marriage to occur.
The primary module LCD shows “<CP letterbug> Primary” and the shadow module
LCD shows “<CP letterbug> Shadow”.
87
Case 5 – Connecting a Shadow Module with Different Software

Image
When connecting a shadow FDC280 module with a different software image than the primary
module to the baseplate – after the primary module has booted up, loaded the checkpoint file,
and initialized on-control – the operational sequence is as follows:
1. The shadow module boots up as described in Steps 1 through 3 in Case 1.
2. Since the shadow module’s software image differs from the primary module, the
shadow FDC280 lights the red Operational Status LED while the green LED remains
on.
3. The primary module sends its software image to the shadow which writes it into its
own flash memory. The shadow module LCD shows on line 1: “BURN PRI IMAGE”,
and on line 2: “GET PRI IMAGE”.
4. The shadow module boots up again as described in Steps 1 through 3 in Case 1.
5. If the FDC280 is in self-hosting mode, and the checkpoint file in flash of the shadow
module differs from the checkpoint file in flash of the primary module or the shadow
module lacks a checkpoint file, the shadow FDC280 lights the red Operational Status
LED while the green LED remains on.
6. If the FDC280 is in self-hosting mode, the shadow module copies the checkpoint file
from the primary module and writes it to flash memory.
If the checkpoint operation succeeds, messages similar to the following examples are
sent to the SMON log:
These messages are sent by the primary module and only indicate that the primary has
sent the checkpoint file to the shadow module. The shadow module still has to write
the checkpoint file to its flash, which could take more than a minute.
If the checkpoint operation is not successful, messages similar to these examples are
sent to the SMON log by the primary module:
Shadow Checkpoint Incomplete - Reboot Shadow
Then, one of two scenarios will occur:
♦ The shadow module will reboot automatically to reinitiate the marriage process.
♦ The shadow module will remain in the red/green LED state and not reboot. In
this scenario, you must reboot the shadow module manually to restart the mar-
riage process.
7. If the FDC280 is in self-hosting mode, the shadow module boots up again as
8. If the letterbug of the shadow module differs from the primary module, the shadow
copies the primary’s letterbug to flash memory.
88
9. The shadow module marries the primary module, as indicated by the single, simulta-
neous quick flashing of the red Operational Status LED on both modules. Then the
modules run fault tolerant. The primary module’s LCD shows “<CP letterbug> Pri-
mary” and the shadow module’s LCD shows “<CP letterbug> Shadow”.
The marriage should occur within 10 seconds, except for the following conditions
when the station is in self-hosting mode:
♦ If the primary module (in Single Primary mode) is downloading the checkpoint
file from flash memory, the marriage will be held off until the download is
complete. The shadow module's LEDs will remain green while it waits for the
marriage to occur.
♦ If the primary module (in Single Primary mode) is performing a checkpoint,
which includes a write to its flash, the marriage will be held off until the check-
point operation is complete. The shadow module's LEDs will remain green while
it waits for the marriage to occur.
Since the shadow module assumes the software image and letterbug of the primary FDC280, the
boot up sequence can be used to identify the shadow FDC280 if its letterbug and ID are both
unknown. When the shadow FDC280 is married, its letterbug is now known and its Manufactur-
ing ID can be viewed from the Equipment Information display in System Management, where
the ID is the last six characters of the SHAD ROM ADDRESS.
Case 6 – Powering Up FDC280 Baseplate with Fault Tolerant

FDC280s With Different Software Images
When powering up an FDC280 baseplate with a fault-tolerant FDC280 pair with different soft-
ware images, the image in the Right FDC280 (the module installed on the right FDC280 slot in
the baseplate) takes precedence. As the Left module boots up, it updates to the image of the Right
FDC280 automatically.
Case 7 – Powering Up FDC280 Baseplate with Fault Tolerant

FDC280s with Same Software Image
When two partners in a fault-tolerant pair are rebooted and the software image in each is the
same, the FDC280 with the lowest ROM MAC address will reboot. The FDC280 with the high-
est ROM MAC address becomes single/simplex. Then the other FDC280 marries it and both run
in a fault-tolerant mode normally
Decommissioning an FDC280 Module

You can decommission an FDC280 module that you no longer plan to use. For example, you
want to remove the FDC280 from the system and place it into storage.
Proceed as follows:
1. Plug the module into the system without connecting to the control network.
2. Wait for the LCD Display to display the following:
<LETTERBUG> Single
FDC280 - NO LINK
89
3. Using the buttons on the LCD display, set the station letterbug to any value, as
described in “Manual Letterbug Assignment via LCD Display” on page 37. Setting it
to the same letterbug is acceptable.
4. With the network adapters still disconnected from the control network, wait for the
module to reboot to accept the new letterbug.
5. Wait for the LCD display to display the following:
<LETTERBUG> Single
FDC280 - NO LINK
6. Remove the FDC280 from the baseplate.
By following this procedure, if you use this FDC280 in another application, you help ensure that
the module will not load a stale checkpoint file from its flash memory, if the module was running
with self hosting enabled before it was removed.
90
4. Configuration Information
This chapter provides system configuration information (System Definition) and control
configuration information.
Overview
In general “configuration” refers to the act of specifying the Foxboro Evo system, including the
types of hardware and software modules that comprise the system and the control blocks that will
be used in the control scheme:
♦ System configuration is the configuration of the overall Foxboro Evo system – the
availability and relationships between the hardware. System configurators include Sys-
Def, and the Control Editors.
♦ Control configuration is the definition of the Process itself, or specifically, the Process
Control Database – control loops, blocks, etc. Control configurators include the Con-
trol Editors.
NOTE
The FDC280 cannot be configured with the IACC control configurator.
Prior to performing configuration procedures, you are encouraged to develop I/O signal lists. You
should develop loop control schemes and loop drawings to document the control scheme. From
the signal lists and loop drawings, you can determine the type and quantity of equipment required
for your control scheme.
System Configuration
Your system configurator application is used to identify the Foxboro Evo system components, sys-
tem software required by each component, the system component letterbugs, and other system
characteristics for correctly loading system software and identifying the system software objects.
System definition with your system configurator produces Commit media, which is required for
software installation and, therefore, must be completed before software installation. It is initially
performed prior to installation of the system equipment, and it is updated with any hard-
ware/software system changes. Reports produced by the system configurator define the network of
the system and provide information that can be used in conjunction with equipment installation.
In the future, if changes are made to the initial hardware layout, the system definition database
must be updated to reflect these changes.
Using a system configurator, you define the type and quantity of FDC280s, associated field
devices, their letterbugs, and the software (for example, digital input, sequence logic, and so forth)
for the FDC280s. Letterbugs are unique, 6-character strings that identify equipment, such as
FDC280s, to the Control Core Services, using the rules described in “FDC280 Identification” on
page 10. The letterbug is set via one of the methods described in “Setting the Letterbug” on
page 37.
91
B0700GQ – Rev C 4. Configuration Information
During System Configuration, you must choose whether to configure fault tolerant or non-fault
tolerant FDC280s.
NOTE
If an FDC280 is configured to be fault-tolerant but is running as a single module,
all of the FDC280’s devices will go into a warning state to indicate that they have
lost one of their connections.
System Configuration Procedure

To perform system definition, configure the Foxboro Evo system as described in the correspond-
ing document provided with your system configurator (SysDef or the Control Editors).
♦ For the Control Editors, refer to Block Configurator User's Guide (B0750AH) and
Hardware Configuration User's Guide (B0750BB).
♦ For SysDef, refer to System Definition: A Step By Step Procedure (B0193WQ).
After you have completed system definition, install the system software. Refer to the appropriate
Hardware and Software Specific Instructions for your workstation or server.
Control/BPC Overrun Detection

In order to accommodate all customer configurations the control station can be overloaded with
too many control blocks, I/O processing and OM scanner loads, and a BPC rate that is too fast.
We provide sizing guidelines to predict approximate loading. We provide overrun indications to
provide notification that a station is loaded beyond capacity.
♦ BPC overruns cause control gaps with control cycles not occurring as scheduled. The
cycle always completes but the next control cycle does not start as scheduled resulting
in a gap to the next scheduled start and a loss of a control cycle.
♦ OM Overruns cause OM connected points to not update at the selected OM scan
rate with the possibility of missing value transitions that would normally be seen if a
scan could be complete as scheduled. All points in the scanner database are processed
in order, but this scan will take multiple passes of the OM scan rate to complete with
the OM Overruns counter increasing.
Both of these overruns may cause concerning effects and may be monitored and alarmed by
appropriate control logic connected to the station block parameters.
To check your system on startup, you can check if overruns occur:
1. Feed the station block control overrun counter to a block.
2. Set a high limit on the number of overruns your system is allowed to have.
3. Configure a process alarm to detect that condition.
Control Configuration
When you have defined and installed the FDC280, you are ready to configure your control sys-
tem and download/deploy the control strategies to the FDC280. Control configuration comprises
designing your control strategy loop diagrams and configuring the compounds and control blocks
for these loops. The FDC280 control database consists of configuration data for the compounds
92
4. Configuration Information B0700GQ – Rev C
and associated control blocks, including Equipment Control Blocks (ECBs) required for the
FDC280.
You may perform this control configuration with either:
♦ If your FDC280 has an image version higher than 0900010000, with ICC and the
CCS FDC280 Configurator. For ICC configuration instructions, refer to Chapter 6
“Configuring FDC280 Using ICC and CCS FDC280 Configurator”.
FDC280 with software version 0900010000 or later is supported by Control Software
v7.1.1 or later. With Control Core Services v9.3-9.4, install Maintenance Pack
MP47481162. This Maintenance Pack, as well as its installation instructions (pro-
vided in its release notes), is available for download from the Global Customer Sup-
port at https://pasupport.schneider-electric.com.
NOTE
Undeploying DCI function blocks can be time consuming as it takes approximately
two seconds to delete each DCI Block from the FDC280. To avoid long undeploy-
ment times, it is recommended that the corresponding devices (ECB201s) are unde-
ployed first, followed by a second undeployment action to delete the DCI Blocks
from the FDC280.
As a compound/block editor, the Foxboro control configurators provide compound and block
building templates (in a general sense) along with a full range of editing functions.
In general, you create a compound in which to locate control blocks for a specific control strategy,
for example, the blocks required to control the outlet temperature of a heat exchanger. Then, you
create the blocks required for implementing the control strategy. Refer to Integrated Control Soft-
ware Concepts for CP270, FCP280, and FDC280 (B0700AG) for details and the Block Configura-
tor User's Guide (B0750AH).
When deploying and then undeploying more than 350 blocks in a single compound, Control
Software timeouts can occur, depending on the block type. To avoid timeouts with this undeploy-
ment operation of the whole compound, undeploy individual blocks in the compound until the
number of blocks in the compound reaches 350 and then undeploy the compound.
Undeploying a compound with more than 350 blocks from the Control Software results in a
timeout detected error as shown in Figure 4-1.
This condition occurs because the undeployment of blocks operation takes about 2.2 seconds for
each block to be deleted and the Control Software configurator uses a timeout which works for a
compound with 350 or fewer blocks.
If you see the message shown in Figure 4-1 with the undeployment of a compound with more
than 350 blocks, wait for more than 2.2 seconds times the number of blocks in the compound for
the FDC280 to compete the undeployment operation before performing any further configura-
tion changes or deploying/undeploying with the FDC280.
To confirm that the FDC280 has completed the undeployment operation, verify if you can
checkpoint the controller from System Manager. When, the checkpoint operation succeeds, use
these steps to synchronize the deployment status in the Control Software and FDC280:
1. Select Synchronize DBs for the controller.
2. Select the first choice Update Galaxy with controller deploy status.
93
Figure 4-1. Receive Message Did Not Succeed for Object V071FD_S2
The ECBs provide the software interface between the I/O control blocks and the FDC280. Actual
control of the process is performed by compounds, consisting of control blocks, which you con-
figure. For each FDC280, you create an ECB200 block as its main driver.
As well, the FDC280 has ECBs for handling FDC280 communications, called the Primary ECBs
(or ECB11s). These are created automatically by the system configurator. The FDC280 supports
up to five of these, described below:
♦ ENET_PORT1 - this Primary ECB handles all communications through the
FDC280 baseplate’s Ethernet port(s)
♦ SERIAL_PORT1, SERIAL_PORT2, SERIAL_PORT3, and SERIAL_PORT4 -
these Primary ECBs handle all communications through the FDC280 baseplate’s
serial ports
Be mindful that each of the FDC280’s non-Primary ECBs must be assigned to this Primary ECB.
For the FDC280’s Ethernet Primary ECB, you must set:
♦ (New parameter) ESPEED to the Ethernet speed to be used for this port - set to your
speed:
♦ 0 = Auto (default)
♦ 1 = 10Mbps half [duplex]
♦ 2 = 10Mbps full [duplex]
♦ 5 = 1Gbps full [duplex]
Verify that when setting the ESPEED value for an FDC280, the corresponding switch
port (to which the FDC280’s baseplate is physically connected) is also configured
with the same setting. If the FDC280 is set to use Auto-Negotiate, the switch port
must also be set to Auto-Negotiate. If the FDC280 is set to 10Mbs/Full, the switch
port must also be configured to 10Mbs/Full (not Auto Negotiate).
This also applies for circumstances in which the FDC280 has a direct connection to a
field device.
♦ (New parameters) FDATA1-4 to the IP addresses (and additional configuration data)
needed to connect to the customer-supplied switches. These are described in detail
later in this chapter.
For each of the Serial Primary ECBs, you must set
♦ SMODE; Serial communication mode; configurable, non-settable; range = 0-6;
default=0; 0=disabled, 1=RS-232 (Dual), 2=RS-422 (Dual), 3=RS-485 (Dual), 4=RS-
232 (Single), 5=RS-422 (Single), 6=RS-485 (Single)
94
♦ SBAUD; Serial communication baud rate; configurable, non-settable; range = 0-9;

default=6; 0=300, 1=600, 2=1200, 3=2400, 4=4800, 5=9600, 6=19200, 7=38400,
8=57600, 9=115200
♦ PARITY; Serial communication parity; configurable, non-settable; range = 0-2;
default=2; 0=None, 1=Odd, 2=Even
♦ STBITS; Serial communication stop bits; configurable, non-settable; range = 0-2;
default=0; 0=1 bit, 1=1.5 bits, 2=2 bits
♦ DTBITS; Serial communication data bits; configurable, non-settable; range = 5-8;
default=8
For the FDC280’s Station block, you must set the Redundancy Algorithm (RDALGO). The
FDC280 supports two methods of determining to which of the redundant FDC280s to give con-
trol in the event of a failover:
♦ “ALG=0” - This method only automatically performs a failover if the Shadow
FDC280 has good connectivity to all devices that the Primary FDC280 has marked as
running without issues, and the Shadow FDC280 has good connectivity to one or
more devices that the Primary FDC280 has marked as failed. If there are connection
problems detected in both Primary and Shadow FDC280s for differing sets of devices,
this redundancy algorithm does not initiate a failover. This is the default method used.
♦ “ALG=1” - This method performs a failover when the Shadow FDC280 has more
good connected devices than the Primary FDC280. It gives control to the FDC280
with the higher count of “good” connected devices. This algorithm is best used when
all devices have equal importance to you.
NOTICE
POTENTIAL DATA LOSS
I/O Core redundancy failover logic is temporarily suspended during

configuration and operational changes. If the Primary module of a
fault-tolerant FDC280 pair loses communication to one or more
devices while there are ongoing configuration or operational changes,
a failover event will not occur even if the Shadow module has good
connection to the same device(s). This may cause data loss.
Redundancy failover logic will resume after the instantiation of the
configuration and operation changes is completed, plus an additional
four seconds.
Examples of configuration changes are DCI block
deployment/undeployment operations.
Examples of operation changes are the Driver Online/Offline and
Device Enable/Disable actions.
Failure to follow these instructions can result in data loss.
For the FDC280’s ECB200 block, you may set the custom parameters for each FDC280 driver, if
applicable. For the Modbus driver, these custom parameters are discussed in “Custom Parameters
for Modbus ECB200” on page 110.
95
NOTE
An FDC280 device driver instance (ECB200) only supports a PHASE value of 1.
You must set these parameters with the Control Editors in order to maintain proper communica-
tions between the FDC280 and their field devices.
For Control Core Services v9.3, the STATION block’s display was updated to provide additional
information about the FDC280’s Core 2 - information including CPU utilization, available free
memory, SW version, total number of device connections, and Primary and Shadow number of
device connections (see Table 4-1 below - parameters which you will not configure are shown
with gray backgrounds).
Table 4-1. New STATION Parameters for FDC280
Parameter Description
IDLET2 The percentage of time that the FDC280’s Core 2 is idle
TOTM2 Total Memory indicates the number of free memory bytes available in Core 2
VERSN2 Version number of Core 2’s control software
FDLOAD Percent of BPC for Core 1 processing of foreign device data
PDVCNT Number of primary device connections
SDVCNT Number of shadow device connections
TDVCNT Total number of configured devices under all drivers that are placed online
RDALGO Redundancy algorithm - described above
For a typical application of control blocks with the FDC280 and detailed control configuration
procedures for the Modbus driver, refer to FDC280 Modbus Master Drivers (Serial and TCP/IP)
(B0700GT).
For control configuration details, refer to Block Configurator User's Guide (B0750AH) and Hard-
ware Configuration User's Guide (B0750BB).
Available Foxboro Evo System Control Blocks

The Control Core Services offer a wide range of control blocks, providing solutions for a broad
spectrum of process control applications. For details on the selection and usage of control blocks,
refer to Integrated Control Block Descriptions (B0193AX).
NOTE
The FDC280 does not support non-DCI ECBs or the ECB202.
Ethernet Primary ECB

If your configuration has Ethernet I/O devices interfaced to the I/O Ethernet port, set the
BADALM parameter in your Primary ECB to “2” to generate a system alarm for any loss of
power from either one of the redundant power connections on the FDC280 baseplate. Be advised
that if you inhibit alarming on the Ethernet port via System Manager, the system alarm will not
be generated. Also if the port is turned offline, that itself will generate a system alarm. So, for sys-
96
tem alarm generation triggered by the loss of one of the redundant power connections, the Pri-
mary ECB’s BADALM parameter needs to be configured, the port needs to be turned online, and
the alarm on this port has to not be inhibited.
Refer to the “Primary ECB (ECBP or ECB11)” chapter in Integrated Control Block Descriptions,
Volume 2 (B0193AX) for the BADALM parameter configuration for Primary ECBs.
Serial Primary ECBs

If your configuration has serial I/O devices only interfaced to one of the serial ports, set the
BADALM parameter in your Primary ECB to “2” to generate a system alarm for any loss of
power from either one of the redundant power connections on the FDC280 baseplate. Be advised
that if you inhibit alarming on the serial port via System Manager, the system alarm will not be
generated. Also if the port is turned offline, that itself will generate a system alarm. So, for system
alarm generation triggered by the loss of one of the redundant power connections, the Primary
ECB’s BADALM parameter needs to be configured, the port needs to be turned online, and the
alarm on this port has to not be inhibited.
If your configuration has devices interfaced to more than one port on the FDC280, to generate a
system alarm for the loss of power from one of the redundant power connections on the FDC280
baseplate, you need to configure the BADALM parameter for one of the associated Primary
ECBs.
Refer to the “Primary ECB (ECBP or ECB11)” chapter in Integrated Control Block Descriptions,
Volume 2 (B0193AX) for the BADALM parameter configuration for Primary ECBs.
97
98
5. Control Block Configuration
Information for I/O Functions
This chapter provides information necessary for configuring the control blocks associated with
the FDC280 I/O functions.
ECBs and DCI Blocks Used with the FDC280’s

Modbus Driver
The FDC280’s Modus driver input/output (reading/writing data from/to the devices) control
block configuration involves configuring the associated equipment control blocks (ECBs) and
Distributed Control Interface (DCI) blocks. The “ECBs and DCI Blocks Used with the FDC280
Modbus Driver” table in FDC280 Modbus Master Drivers (Serial and TCP/IP) (B0700GT) lists
the ECBs and DCI blocks used with the FDC280 and the Modbus driver. For descriptions of the
ECBs and DCI blocks used with the FDC280, refer to Integrated Control Block Descriptions
(B0193AX).
This chapter provides information regarding control block configuration. For specific informa-
tion on the ECB and DCI block parameter settings, refer to Integrated Control Block Descriptions
(B0193AX).
Configuration Procedures
You may perform this control configuration process with either:
♦ The Control Software, as described below or,
♦ If your FDC280 has an image version higher than 0900010000, with ICC and the
CCS FDC280 Configurator. For ICC configuration instructions, refer to “Install
FDC280 Drivers” on page 99 and Chapter 6 “Configuring FDC280 Using ICC and
CCS FDC280 Configurator”.
This set of procedures provided in this section guides you through the control configuration pro-
cess for the FDC280 using the Control Editors.
Install FDC280 Drivers

Install the FDC280 Modbus TCP Client driver Rev 1.0 file from the Foxboro Evo FDC280
Modbus TCP Client Driver V1.0 CD-ROM (K0177AH-A) onto the Control Software client
workstation.
As well, install the Modbus RTU Driver media for FDC280 Rev 1.0 file from the Modbus Serial
RTU and ASCII Driver media for FDC280 (K0177CV) onto the Control Software client work-
station.
Proceed as follows:
1. Insert the CD-ROM into the host workstation’s media drive.
2. Using Windows/File Explorer, navigate to the root directory of the CD-ROM.
99
B0700GQ – Rev C 5. Control Block Configuration Information for I/O Functions
3. Double-click on the ModbusTcpClientV1 MSI installer package.

4. Follow the prompts which appear to complete installation of the FDC Driver file.
The driver file is installed on the workstation. Figure 5-1 and Figure 5-2 show the driver media
about to be installed on a Control Software Client workstation.
Figure 5-1. FDC280 Modbus TCP Driver - Installation Summary
Figure 5-2. FDC280 Modbus Serial Driver - Installation Summary
Your Galaxy database must import this file as described in the procedure below.
100
5. Control Block Configuration Information for I/O Functions B0700GQ – Rev C
Import Driver Definition File

Import the FDC Driver file (DriverDefinition.xml) into the Galaxy database. This file was
installed on the Control Software client workstation as described in the previous section.
You only need to load this file once.
It is possible to proceed with the control configuration without importing the FDC Driver file,
but some of the validation features, such as the Device or DCI block’s configuration validation,
Points filtering, and Data Type lookup will not be available. Also, you will not be able to deploy
the Driver instance until the FDC Driver file is imported.
Proceed as follows:
1. In the Control Editors, select Galaxy -> Import -> FDC Driver. The Import FDC
Driver dialog box appears.
2. Click the “...” button adjacent to the text field at the top of the dialog box.
Figure 5-3. Import FDC Driver Dialog Box
3. Browse to the location into which the FDC Driver file was installed on the Control
Software client workstation. While this location depends on where the ArchestrA
application was installed, in most circumstances, this file will be located in the follow-
ing folder:
D:\Program Files\Archestra\Framework\Bin\Invensys\FDC Drivers\[Driver name and
version]
The [Driver name and version] folder name is:
D:\Program Files\Archestra\Framework\Bin\Invensys\FDC Drivers\Modbus TCP
Client 1.0
4. After selecting the FDC Driver file, click Validate.
If the Control Editors cannot find the FDC Driver file, a detected error message is
shown. Repeat Step 2.
101
If the Control Editors find that the FDC Driver file already exists on the Galaxy data-
base, a notification appears. The Import button appears if you want to override this
existing FDC Driver file with the FDC Driver file you selected in the previous step.
5. Click Import. The Import FDC Driver dialog box closes. A dialog box appears which
informs you whether or not the import operation succeeded.
Configure FDC280
Next, configure the FDC280 object itself. The FDC280 uses software package (image) OS3I80.
Proceed as follows:
1. Create FDC280 individually or via Bulk Data.
To create the FDC280 individually, refer to “Creating Controllers on the Foxboro Evo
Control Network” in the Hardware Configuration User's Guide (B0750BB).
To Bulk Create FDC280s, refer to Bulk Data Editor User's Guide (B0750AF).
To configure the FDC280, refer to “Configuring Controllers - Hardware” and “Con-
figuring Controllers - Software” in B0750BB.
2. Configure the STATION block for the FDC280 and type the name of the desired
Redundancy Algorithm (RDALGO - “ALG=0” or “ALG=1”) to set your preferred
method of failover for the FDC280. The FDC280 supports two methods of deter-
mining to which of the redundant FDC280s to give control in the event of a failover:
♦ “ALG=0” - This method only automatically performs a failover if the Shadow
FDC280 has good connectivity to all devices that the Primary FDC280 has
marked as running without issues, and the Shadow FDC280 has good connectiv-
ity to one or more devices that the Primary FDC280 has marked as failed. If there
are connection problems detected for both Primary and Shadow FDC280s for dif-
fering set of devices, this redundancy algorithm does not initiate a failover.
If RDALGO is not configured (i.e., left blank), “ALG=0” is used by default.
♦ “ALG=1” - This method performs a failover when the Shadow FDC280 has more
good connected devices than the Primary FDC280. It gives control to the
FDC280 with the higher count of “good” connected devices. This algorithm is
best used when all devices have equal importance to you.
Refer to “Editing Station Compounds” in the Block Configurator User's Guide
(B0750AH) for details on setting the other STATION block’s parameters.
102
Figure 5-4. Station Block - RDALGO Parameter - FDC280 Control Processors
103
3. Configure the Primary ECB for the Ethernet port (ENET_PORT1) as shown in
Figure 5-5.
Figure 5-5. ENET_PORT1 Tab, Configuration Subtab for an ECB Compound - FDC280 Control Pro-
cessors
NOTE
Regarding the addresses shown in Figure 5-5, for security considerations, Schneider
Electric recommends using only non-routable/private subnets:
10.0.0.0 - 10.255.255.255, 172.16.0.0 - 172.31.255.255, 192.168.0.0 -
192.168.255.255
Set the:
♦ Bad Alarm field (which sets the BADALM parameter in the Primary ECB - refer
to Integrated Control Block Descriptions (B0193AX) for details)
♦ Speed drop-down box, which sets the ESPEED parameter (0 - Auto is the
default). It is important that the speed/duplex setting matches exactly that of the
network port connected at the other end of the network cable; presumably an
Ethernet switch port. (E.g., Auto (negotiate) on the FDC280 port matches with
Auto (negotiate) on the switch port, 100Mbit/Full duplex on FDC280 port
matches with 100Mbit/Full duplex on the switch port, and so on.) Most
hub/switches use “Auto-Negotiate” as their default setting.
♦ Fields in the Left and Right tables. Enter the network configuration (IP address,
subnet mask, and default gateway) for the left-most field device Ethernet port on
104
the FDC280 baseplate in the Left table, and enter the network configuration for
the right-most field device Ethernet port on the same baseplate in the Right table.
The following IP addresses are NOT allowed:
♦ 0.0.0.0
♦ 127.*.*.* (loopback addresses)
♦ 224-239.*.*.* (multi cast addresses)
♦255.255.255.255 (broadcast address)
The default gateway address must be in the same subnet as the configured IP
address.
If the FDC280 is configured non-fault tolerant, only the Left address tables are
displayed for configuration.
This is discussed further in “Editing ECB Compounds and ECBs” in the Block
Configurator User's Guide (B0750AH).
4. Configure the Primary ECB for each of the four Serial ports as shown in Figure 5-6.
Figure 5-6. SERIAL_PORT1 Tab, Configuration Subtab for an ECB Compound - FDC280 Control
Processors
NOTE
To make any configuration changes to a Primary ECB, the corresponding port must
be set to offline mode.
105
Configure FDC280’s Drivers

The Modbus driver in the FDC280 supports up to 256 field devices and up to 8000 I/O points.
The maximum number of blocks that can be configured for use with the FDC280 (or fault toler-
ant FDC280 pair) is 8262, including all types: control blocks, ECBs, compounds, data blocks,
and so forth. Refer to Field Device Controller 280 (FDC280) Sizing Guidelines and Excel Workbook
(B0700GS) for examples of valid block count combinations.
Proceed as follows to configure the driver:
1. Individually create or Bulk Create the FDC280’s driver from the FDC280’s Ethernet
port in the Control Editors.
Drivers can be created either directly from the Ethernet port, or created individually
and then assigned to an FDC280 station.
To create the FDC280’s driver individually, refer to “Creating Controllers on the Fox-
boro Evo Control Network” in the Hardware Configuration User's Guide (B0750BB).
Right-click the Ethernet Port object and select New Driver.... A Bulk Create dialog
box opens. Select the appropriate driver type for this port and click OK.
Figure 5-7. Create New Driver from the FDC280’s Ethernet Port
106
To Bulk Create the FDC280’s driver, refer to Bulk Data Editor User's Guide
(B0750AF).
Figure 5-8. Bulk Create New FDC280 Driver
To assign undeployed drivers to an FDC280 station, perform one of the following:

♦ Drag and drop each undeployed driver onto an FDC280’s Ethernet port object in
the Control Editors. (Deployed drivers cannot be dragged and dropped.)
♦ Right-click the driver and select Assign To. In the Assign To dialog box that
appears, select the appropriate selection in the Scope drop-down menu.
♦ The empty selection lists all FDC280 station instances in the Galaxy database.
♦ The All Equipment Units selection lists all FDC280 station instances assigned
to an Equipment Unit.
♦ The port selection lists the available Ethernet ports for the selected stations.
When the driver is dropped on an Ethernet port object, the PARENT parameter
(viewed at the Parent ECB parameter) of the driver is set to the port's ENET_PORT1
parameter.
This also creates an ECB200 for this driver, through which you can configure the
driver.
2. You can configure the description of the FDC280 driver, and view all the driver prop-
erties, using the Control Editors. Double-click the FDC280 driver to open this
Editor.
107
Figure 5-9. Control Editors for the FDC280 Driver
In the General tab, you can type a new description in the Description: field if desired.
3. Configure the ECB200 associated with this driver as described in “Creating and Edit-
ing the FDC280 ECB for Ethernet and Serial Drivers (ECB200)” on page 109. An
example is shown in Figure 5-10.
Figure 5-10. ECB Tab for an ECB Compound - [FDC280].ECB200 Driver Subtab
Under the Driver tab, “Custom Parameters” section, set the FDC280 related configu-
ration parameters as well. This information will be stored in the CPARM1-6 parame-
ters in the ECB200. For the Modbus driver, these custom parameters are discussed in
“Custom Parameters for Modbus ECB200” on page 110.
108
Be aware that if you change these custom parameters, you must take the driver offline
and then put it online again in order to apply the change.
Creating and Editing the FDC280 ECB for Ethernet and Serial Drivers
(ECB200)
ECB200 is the equipment control block for the FDC280’s driver. This driver supports both
Ethernet and serial communications. Refer to Integrated Control Block Descriptions (B0193AX) for
the ECB200 parameter definitions.
NOTE
To make any configuration changes to a driver ECB200, it must be set to offline
mode.
To create and edit an ECB200:

1. Access the Control Editors. For detailed instructions, refer to “Equipment Control
Blocks” and “FDC Driver and Device ECB Configuration with FDC280 Control
Processors” in the Block Configurator User's Guide (B0750AH).
2. Select a compound or insert a new compound.
3. Add an ECB200.
4. Select the ECB200 block, then select and edit the desired block parameters.
Table 5-1 lists the key ECB200 parameters for the FDC280. They are available in the
subtabs indicated below under the “ECBs” tab in the editor. Refer to Integrated Con-
trol Block Descriptions (B0193AX) for the ECB200 parameter definitions.
Table 5-1. ECB200 Key Parameters/Values for FDC280
Editor Subtab Parameter/ Value Description

General Block Type ECB200
Block Description Description
Block Sample Time Block execution time
(PERIOD)
Block Phase Number Rate at which to scan the ECB at a specific Block Pro-
cessing Cycle (BPC) within the time determined by
the PERIOD
Execution Zone1 The block's execution zone. (CONT1, CONT2,
SEQ, DATA, ECB)
Port1 Type of port (Ethernet or Serial)
109
Table 5-1. ECB200 Key Parameters/Values for FDC280 (Continued)
Editor Subtab Parameter/ Value Description

FBM Device Identifier 6-character ID of the FDC280
Hardware Type The Hardware Type should be:
1 for the FDC280’s Ethernet functionality
2 for the FDC280’s Serial functionality
(Automatically filled in for the Control Software -
must be manually typed in for ICC)
Software Type The Software Type should be 200, for the FDC280’s
Ethernet functionality. (Automatically filled in)
Parent ECB Block name of parent Primary ECB (ENET_PORT1,
or SERIAL_PORT1-4) (Automatically filled in)
Driver Custom Parameter1 and Custom parameter for the driver. See the next section.
Custom Parameter2
Custom Parameter3 Not used with the Modbus driver.
- through -
Custom Parameter6
Driver Driver and version:
-1 for Diagnostic Driver
1 for Modbus/TCP 1.0
2 for Modbus Serial
3 for Modbus/TCP 1.1
(Automatically filled in based on the selection of the
Driver as shown in Figure 5-10)
1. Not an ECB200 parameter.
Custom Parameters for Modbus ECB200

The ECB200 has a set of custom parameters (CPARM1-6) which allow you to customize the
behavior of the FDC280 driver. For the Modbus driver, you can only set CPARM1 - do not set
the others.
The FDC280 Modbus TCP and Serial RTU drivers support the following optional custom
parameter for CPARM1 (settable at Custom Parameter1)
The FDC280 TCP driver supports:
♦ “TSTAMP” - If this custom parameter is specified, then for all field devices, their
points are timestamped in the FDC280 when they are read from the field devices.
(TSTAMP can be specified at the device level.)
If “TSTAMP” is not specified, any value and status changes for an I/O point are time
stamped when the corresponding DCI block is processed.
Timestamping is explained in “Timestamping” in FDC280 Modbus Master Drivers
(Serial and TCP/IP) (B0700GT).
The FDC280 Serial Modbus RTU driver supports the selection of TSTAMP and RTU or ASCII
for the protocol in CPARM1. If the TSTAMP option is selected, the timestamping behavior is
the same as described above for the TCP driver. If the parameter is left blank, RTU is used by
default. The FDC280 Serial Modbus RTU driver supports port handover delay in CPARM2.
110
This is set in the Control Software in the Block Configurator, under the Driver tab for the
ECB200. This parameter can be up to, but not exceed, 64 characters. Refer to “Equipment Con-
trol Blocks” in the Block Configurator User's Guide (B0750AH) for instructions on setting these
parameters.
These custom parameters are different than those custom parameters used with the field devices,
shown in Figure 5-14 on page 113.
Configure FDC280’s Field Device Objects

Finally, configure the objects which represent the field devices in the Control Editors.
Proceed as follows to configure each field device:
1. Create and configure the FDC280’s field devices (FDC_Devices) individually from
the FDC280’s driver, or via Bulk Data.
To create the field device objects individually, refer to “Devices” in the Hardware Con-
figuration User's Guide (B0750BB).
For example, right-click any FDC280 driver instance, and select New-> Device.... A
Bulk Create dialog box appears. Select the appropriate field device type and click OK.
Figure 5-11. Create New Field Device Object Individually
111
To Bulk Create the field device objects, refer to Bulk Data Editor User's Guide
(B0750AF).
Figure 5-12. Bulk Create New Field Device Objects
To assign undeployed field device objects to an FDC280’s driver, perform one of the
following:
♦ Drag and drop each undeployed field device object onto an FDC280’s driver in
the Control Editors. (Deployed objects cannot be dragged and dropped.)
♦ Right-click the field device object and select Assign To. In the Assign To dialog
box that appears, select the appropriate selection in the Scope drop-down menu.
♦ The empty selection lists all FDC280 driver instances in the Galaxy database.
♦ The All FDC280 Stations selection lists all driver instances assigned to a
FDC280 station.
♦ The specific FDC280 station selection lists all drivers assigned to that station.
An ECB201 is created for the field device, through which you can configure the field
device.
2. To rename the device, right-click on field device object and select Rename Con-
tained Name.
3. You can configure the description of the field device object, and view all the object
properties, using the Control Editors. Double-click the field device object driver to
open this Editor.
112
Figure 5-13. Control Editors for the Field Device Object
In the General tab, you can type a new description in the Description: field if desired.
If you click the link adjacent to the “Related ECB201” field, a list of the ECB201
parameters will appear. This list is described in “Configuring Device ECB (ECB201)”
on page 115.
4. Optionally, in the currently open editor, click the Groups tab. Configure the table
shown in this tab.
Figure 5-14. Hardware Editor - Groups Tab
The maximum number of Groups is limited to 2000 for all devices configured for the
FDC280 Modbus. This is the limit for the total number of groups for all the config-
ured device ECBs in FDC280.
If a device is deployed with a group configuration that causes the total number of
groups to exceed the maximum of 2000, the Device ECB201 detail display will show
W96- “Exceeded maximum groups”. Once a device is in this state, it must be unde-
113
ployed and then redeployed with a fixed configuration that does not exceed the max
group limit.
a. Set the Group Name, Scan Rate, and Phase parameters. Group Name must be
unique, and not exceed 128 characters. Figure 5-14 is an example usage with
Modbus driver.
♦ Group Name - Any unique alphanumeric name for the group. For Modbus
Function Code 23, you must prefix the name with “FC23_” (note the under-
score at the end of prefix as shown in Figure 5-14).
♦ Scan Rate - The group's scan rate in milliseconds. (Any value less than 100
results in using the default scan rate: 500 milliseconds. The Scan Rate used
has a resolution of 100 milliseconds. The value configured is truncated to the
closest 100 millisecond units. For example, if you configure 451 milliseconds,
the driver uses 400 milliseconds for the Group scan rate.)
♦ Phase - The group's phase can be specified by appending “/n” to the scan rate
where “n” is the phase. The default phase value is zero.
The allowable phase values depend on the configured scan rate (period). The
minimum phase value is “0”, and the maximum phase value is:
Max Phase = (Scan Rate in milliseconds/ 100) - 1
For example, if the Scan Rate is 1000, the Max Phase is 9, the number of
phases are 10 (0 through 9); if the scan rate is 5000, the Max Phase is 49 and
the number of phases are 50 (0 through 49).
If the specified phase value is greater than the Max Phase, the default phase of
“0” will be considered for that group.
Configure the custom parameters specific to your FDC280’s driver, if any.
The following are definitions for the Custom Parameters associated with the
FDC280 Modbus/TCP driver.
To configure Custom Memory Maps (refer to the section “Custom Memory Map”
in FDC280 Modbus Master Drivers (Serial and TCP/IP) (B0700GT)):
♦ Custom Parameter 1 – Configure the starting address for the group.
♦ Custom Parameter 2 – Configure the ending address for the group.
To configure Cyclic Group Write/Read (Function Code 23) group:
♦ Custom Parameter 1 – Configure the start to end address range of the Input
Registers. The address range must be separated by a hyphen (-).
♦ Custom Parameter 2 – Configure the start to end address range of the Output
Registers. The address range must be separated by a hyphen (-).
♦ Custom Parameter 3 – Configure optional Wait Count:
WC=n, where n is integer value with a range of 1-99.
You can copy and paste one or more rows in the same field device, or from one
field device to another.
These driver custom parameters differ from the custom parameters in the ECB200,
which are described later in this document.
When you have completed defining all the groups, remember to click anywhere on
the blank line. Otherwise, the last defined line will not be saved.
114
If related ECB201 is deployed and checked out, the Control Editors check-in opera-
tion is not successful with appropriate message (as the ECB could not be marked
“dirty”).
5. Configure the ECB201 for the device. Refer to the next section.
6. Set up the device’s I/O connections. Refer to “I/O Connections” in the Block Configu-
rator User's Guide (B0750AH) and “Making Field Connections” in Strategy Editor
User's Guide (B0750AN).
7. Configure your other compounds, strategies, and DCI blocks as discussed in the Block
Configurator User's Guide (B0750AH). Connect these other blocks to the device as
discussed in “Other Field I/O Connection Methods” in B0750AH.
8. Deploy the control configuration as discussed in Control Database Deployment User's
Guide (B0750AJ) and System Manager (B0750AP).
Configuring Device ECB (ECB201)

For each device associated with the FDC280, a child ECB201 must be configured and connected
to the (parent) ECB200. ECB201 can reside in the same compound as the ECB200 or it can
reside in any other user-configured compound.
You create and edit the device ECBs (ECB201s) in a manner similar to that used for the ECB200.
Table 5-2 lists the key ECB201 parameters for field devices. Refer to Integrated Control Block
Descriptions (B0193AX) for the ECB201 parameter definitions.
1. Access the Control Editors. For detailed instructions, refer to “Equipment Control
Blocks” in the Block Configurator User's Guide (B0750AH).
2. Select the ECB201 block, then select and edit all block parameters. Refer to Inte-
grated Control Block Descriptions (B0193AX) for the ECB201 parameter definitions.
Table 5-2. ECB201 Key Parameters for Devices
Editor Subtab Parameter Description

General NAME Contains the name used by the FDC280 to access this ECB.
General Block Description
Description
Block Sample The block’s execution time base, 1 = 0.5 second. This is the scan
Time period at which the Control Processor scans DCI blocks. The
(PERIOD) scan rate of the device is independent of this scan period.
Block Phase Block phase number
Number
115
Table 5-2. ECB201 Key Parameters for Devices (Continued)

FBM Device Identi- A unique 6-character ID. This is the device identifier shown in
fier the System Manager.
Device Name This field contains the IP address of the device and optionally
the node address.
FDC280 x.x.x.x
Single Mo Example: 192.168.1.25
de
OR
x.x.x.x/n
Example: 192.168.1.25/2
n(For Modbus serial devices when connected
FDC280 serial ports)
Where x.x.x.x is the Modbus Device's IP

address, and n is the Modbus Device Address1.
The Modbus Address is optional, and it is usually

unnecessary for most device types. The Modbus
Device Address can either be specified here, or in
the DVOPTS parameter. For certain configura-
tions such as interfacing Modbus Plus (serial
devices) through a bridge, the Bridge IP address
and the serial device address, which is the device
address, are used. The later is also referred to as
Node number.
When communicating to Modbus Plus devices

through the Modbus Plus to Ethernet Bridge
(MEB), the IP address of the MEB and the Mod-
bus Plus device address must be specified.
116
Table 5-2. ECB201 Key Parameters for Devices (Continued)

FBM Device Name FDC280 x.x.x.x;y.y.y.y
(Cont.) Fault-Tol- Example: 192.168.1.25;192.168.1.26
erant OR
x.x.x.x/l;y.y.y.y/r
Example: 192.168.1.25/1;192.168.1.26/2
FDC280 serial ports, where n can range from 1 to
254)
Where x.x.x.x is the Modbus Device's left IP

address (the port connected to the fault-tolerant
Left FDC280 module), l is the left Modbus
Device Address y.y.y.y is the Modbus Device's
right IP address (the port connected to the fault-
tolerant Right FDC280 module), and r is the
right Modbus Device Address.
The Modbus Addresses are optional, and they are

usually unnecessary for most device types.
The Modbus Device Addresses can either be speci-

fied here, or in the DVOPTS parameter.
NOTE
The maximum number of charac-
ters allowed in the DVNAME
parameter is 32. If the length of
the DVNAME parameter exceeds
32, specify the Modbus Device
Addresses in the
DVOPTS parameter using the
“+LN=xx” and “+RN=xx”
options.

through MEB, the IP address of the MEB and the
Modbus Plus device address must be specified.
Device The name of the protocol plus any required options. Refer to
Options “Configuring the Device Options Parameter” on page 118.
1. “Device address” in this document is the same as “Unit Identifier” in the Modbus Messaging On
TCP/IP Implementation Guide V1.0b document, part of the documentation set in the Preface of
FDC280 Modbus Master Drivers (Serial and TCP/IP) (B0700GT). The default device address is
255. Some devices ignore the device address.
117
Configuring the Device Options Parameter

The Device Options (DVOPTS) parameter can be set to any of the following desired options.
These options can be appended in any order or combination (unless explicitly stated otherwise).
♦ +@scan rate – Scan rate value in tenths of a second. For example, for a 2 second
scan rate applied to all query messages for this device, DVPOPTS = +@20. The default
scan rate is 500 ms (1/2 second).
♦ +H configures the driver to use Modbus function code 8 as a heartbeat. Without this
option, the driver uses the default heartbeat method described in “Device Fail Opera-
tion and Heartbeat” listed in FDC280 Modbus Master Drivers (Serial and TCP/IP)
(B0700GT).
+H=address configures the driver to use the specified Modbus address for its
heartbeat.
If you enter +H, function code 8 message is used for the heartbeat. If you enter
+H=address, the reading of the point at the address is used for the heartbeat.
♦ +DUPS enables the Modbus driver to allow multiple DCI blocks to be configured for
the same address (i.e. duplicate addresses allowed).
♦ +TSTAMP is used for enabling the timestamp option for this device. Timestamping is
explained in “Timestamping” in FDC280 Modbus Master Drivers (Serial and TCP/IP)
(B0700GT).
♦ +TO=n – (Where O is the letter “O”) Applies a response timeout value, specified by n,
to this device. The timeout value is in tenths of a second. The default timeout value is
500 ms (1/2 second). If TO=0, the default value is used. Vendor device product
documentation may suggest a proper response time for the device. The FDC280
response timeout period should be set to this time.
+TO=Mn (where O is the letter “O”) configures a response timeout value to be used
instead of the default value, where “n” (1 - 999) is equal to the timeout value in milli-
seconds. (The entered value is rounded up internally to nearest 10ms.) Default time
out value (500ms) will be used if “n” value is not in the specified range or not config-
ured. This option is used to achieve sub-100ms durations. Vendor device product
documentation may suggest a proper response time for the device.
♦ +LN=xxx – Specific for the FDC280 Simplex or, for an FDC280 pair, the module
installed in the left slot in the FDC280 baseplate; applies the Modbus device address
for the single FDC280 or the Left FDC280, where xxx can be a 1 to 3 digit address
(1 to 254). If you do not specify a device address, a default device address of 255 is
used. (This option is not available for Modbus serial devices, i.e. HWTYPE=2.)
♦ +RN=xxx – For an FDC280 pair, the module installed in the right slot in the FDC280
baseplate; applies the Modbus device address for the Right FDC280, where xxx can
be a 1 to 3 digit address (1 to 254). If you do not specify a device address, a default
device address of 255 is used. (This option is not available for Modbus serial devices,
i.e. HWTYPE=2.)
♦ +RT=n configures the number of retries to attempt when a response timeout occurs,
where “n” (0-9) is equal to the number of retries. Default retries (2) will be considered
if “n” value is not in the specified range or not configured.
♦ +SC or +MC specifies the Modbus function code for writing to coils when the device
does not support both single and multiple write function codes. “+SC” specifies that
118
the device supports only function code 05 (Force Single coil) for writing to coils.
“+MC” specifies that the device supports only function code 15 (Force multiple coils)
for writing to coils. “+SC” and “+MC” are mutually exclusive options. If both options
are specified (“+SC+MC” or “+MC+SC”) at the same location (in the DVOPTS
parameter of ECB201), the device will be marked as Invalid.
♦ +SR or +MR specifies the Modbus function code for writing to registers when the
device does not support both single and multiple-write function codes. “+SR” speci-
fies that the device supports only function code 06 (Force Single register) for writing
to registers. “+MR” specifies that the device supports only function code 16 (Force
multiple registers) for writing to registers. “+SR” and “+MR” are mutually exclusive
options. If both options are specified (“+SR+MR” or “+MR+SR”) at the same
location (in DVOPTS parameter of ECB201), the device will be marked as Invalid, if
the Groups are not used at ECB201. And also a message “Invalid options +SR+MR
specified for device” will be displayed in smon_log.
♦ +TP configures the Shadow FDC280 to use Internet Control Message Protocol
(ICMP) ping as an alternative heartbeat mechanism to verify device connectivity. To
enable this option, at least one point or heartbeat needs to be configured for the corre-
sponding device.
♦ +BPIV, or Bypass Input validation. By default the driver validates all fields of a Mod-
bus response message from a connected device as per the Modbus Protocol
specifications listed in “Modbus Protocol Documents” in FDC280 Modbus Master
Drivers (Serial and TCP/IP) (B0700GT).
Any response message that does not conform to the protocol completely is discarded.
This feature addresses security considerations from the device interface’s point of view.
If you need to connect to a device that does not fully comply with the Modbus Proto-
col, you can bypass the input validation feature by using this +BPIV, option.
This parameter can take multiple concatenated settings. The delimiter between each
setting is a single space. All the possible options can be concatenated. There is no max-
imum number of characters for this parameter.
For Modbus Plus devices through MEB:
1. An ECB201 block should be created for each Modbus Plus device under an MEB.
The IP address of the MEB should be specified in the DVNAME parameter and the
Modbus Plus device node address should be specified using the “/m” notation in the
DVNAME parameter or the “+LN=” (Simplex, non-fault-tolerant FDC280) or
“+LN=” and “+RN=” (Fault-tolerant FDC280) options in DVOPTS parameter of the
ECB201 block.
2. The options are independently configurable for each Modbus Plus device.
3. The MEB uses the specified Modbus Device Address for routing messages to the
appropriate end device. Each end device must have a corresponding route configured
in the MEB’s routing table. Please refer to the MEB's user's guide (Schneider Elec-
tric's Document Model no. 31005104) for instructions on configuring the routing
table.
4. Both the Left and Right FDC280s communicate to the same MEB, therefore the LN
and RN values must be identical.
119
When including options in your DVOPTS parameter that require a configured value
(such as +@rate or +TO=n), if you do not enter a value for the option (such as
“+@+TO=”), then the default value for that option is used.
The following is an example setting of the Device Options parameter:
Device Options = +@10+H+TO=20+LN=5+RN=123
This syntax indicates that there is a one second scan rate for queries; the Function Code 8 heart-
beat option is applied; the Response Timeout setting is two seconds; the Left FDC280 is con-
nected to device address 5; and the Right FDC280 is connected to device address 123.
Options Applicable to Serial Ports Only

♦ +ECTDLY option:
The Modbus master driver supports the introduction of a configurable delay between
the RTS assertion and the first byte of data transmission. The driver also introduces a
time delay between the last byte of data transmission and RTS De-Assert, to interface
with the slow radio link devices in RS-232 Serial communication.
The option (+ECTDLY) has to be configured in the CPARM1 parameter of ECB200.
Early Assertion and Delayed Negation (+ECTDLY=y): Configure the ECTDLY option
to enable the early assertion and delayed negation of the RTS signal, where y is one
hundredth of a second. If you do not specify the value for the option, the default value
is 0 (zero) and the maximum value is 6000. If the value of y is greater than 6000, the
driver will be marked NOTREADY and a diagnostic message “Max Supported
value for ECTDLY option is 6000” will be displayed in smon_log.
For example: if +ECTDLY=20, the driver introduces a 200 millisecond early assertion
and delayed negation of the RTS signal during the transmission of the data packet in
RS-232 communication.
The +ECTDLY option is supported only for RS-232 (Single and dual port modes). If
configured in other modes, the driver will be marked NOTREADY and a diagnostic
message “ECTDLY option is supported only for RS-232 Modes” will be dis-
played in smon_log.
♦ +RD option:
This Modbus driver can support a response delay when transmitting messages to the
device. This configuration is necessary for some devices that cannot handle fast
requests.
The option (+RD) has to be configured in the CPARM1 parameter of ECB200.
Response Delay (+RD=n): Enables a response delay between messages sent to the
device, where n indicates the time in milliseconds. The default value is 0 (zero).
Configuring DCI Blocks

In a control strategy, the DCI control blocks interface the Foxboro Evo system to the field devices.
The DCI blocks used with devices used with the Modbus driver are listed in the “ECBs and DCI
Blocks Used with the FDC280 Modbus Driver” table in FDC280 Modbus Master Drivers (Serial
and TCP/IP) (B0700GT).
For detailed information on block creation, refer to Block Configurator User's Guide (B0750AH).
For parameter definitions, refer to Integrated Control Block Descriptions (B0193AX).
120
As part of the editing operations performed on the newly created DCI blocks, certain parameters
(PNT_NO, R11_PT and others) must contain a point address to specify the particular point to
be accessed regarding the input or output data handled by the DCI block.
For details regarding the parameters to be configured, refer to “Distributed Control Interface
(DCI Blocks)” on page 121 and “Configuring DCI Blocks for Points” in FDC280 Modbus Master
In conjunction with creating and editing DCI blocks, you must configure the various blocks and
compounds required for the desired control scheme. Refer to the following documents to perform
these operations:
♦ Standard and Compact 200 Series Subsystem User’s Guide (B0400FA)
♦ Integrated Control Software Concepts for CP270, FCP280, and FDC280
(B0700AG)
♦ Integrated Control Block Descriptions (B0193AX)
To create and edit a DCI block in an existing compound, add the block to a Strategy as described
in Block Configurator User's Guide (B0750AH) and Strategy Editor User's Guide (B0750AN).
The engineering units configured for the block detail display must match the units configured in
the device.
To verify operation of the DCI blocks and the device data using the block detail displays:
1. Access the Foxboro Evo Control HMI, FoxView, or the FoxSelect compound/block
overview utility. Refer to Control HMI Application User's Guide (B0750AQ) or Process
Operations and Displays (B0700BN) for details.
2. Access the block detail display for each DCI block created, and confirm its data.
Distributed Control Interface (DCI Blocks)

DCI Block Point Number Parameters
DCI block point number parameters specified in Table 5-3 must be encoded (configured) by con-
necting to or entering a data identifier using the Control Editors. This identifier enables the
FDC280 to identify specific data coming from or going to the input/output stream.
Table 5-3. DCI Block Point Number Parameters Requiring a Data Identifier
Parameter(s)
DCI Block to be Coded
BIN (Binary Input) PNT_NO
BINR (Redundant Binary Input) BI1_PT, BI2_PT, BI3_PT [BI3_PT optional;
needed if ARBOPT =1 (TMR)]
121
Table 5-3. DCI Block Point Number Parameters Requiring a Data Identifier (Continued)
Parameter(s)
DCI Block to be Coded
BOUT (Binary Output) and PLSOUT (Pulse PNT_NO, INI_PT (INI_PT optional; needed
Output) if external initialization request. INI_PT must
contain a valid Boolean device address if it is to
be used, or an empty (null string) or spaces if it
is to be not used; anything else causes the DCI
block to fail cyan with “W65 error (invalid
point address)” in the corresponding block
detail display.)
IIN (Integer Input) PNT_NO
IINR (Redundant Integer Input) II1_PT, II2_PT, II3_PT [II3_PT optional;
IOUT (Integer Output) PNT_NO, INI_PT (INI_PT optional; needed
if external initialization request)
PAKIN (Packed Binary Inputs) PKINGP
PAKINR (Redundant Packed Binary Inputs) PK1_PT, PK2_PT, PK3_PT [PK3_PT
optional; needed if ARBOPT =1 (TMR)]
PAKOUT (Packed Boolean Outputs) PKCOGP
RIN (Real Input) PNT_NO
RINR (Redundant Real Input) RI1_PT, RI2_PT, RI3_PT [RI3_PT optional;
ROUT (Real Output) PNT_NO, INI_PT (INI_PT optional; needed
if external initialization request)
STRIN (String Input)1 PNT_NO, device specific
1. STRIN is supported only for configuring diagnostic blocks, not for field data.
For detailed examples of setting the PNT_NO parameter, refer to “Configuring DCI Blocks for
Points” in FDC280 Modbus Master Drivers (Serial and TCP/IP) (B0700GT).
Fail-safe Actions
The FDC280 Modbus driver supports fail-safe functionality, with the ability to write fail-safe val-
ues to output points under certain conditions. Refer to Integrated Control Block Descriptions
(B0193AX) for details on configuring fail-safe options through the FSOPTN parameter in each
DCI block (with the exception of the PAKOUT block, as fail-safe functionality is not supported
with PAKOUT block).
The Modbus driver supports only the “Fail-safe upon CP request” options. Those options are:
♦ Fail-safe if bad measurement
♦ Fail-safe if the set fail-safe (SETFS) parameter is set
In addition, when the compound containing the DCI block is turned off, or when the DCI block
is deleted and any of the FSOPTN parameter options are configured, FDC280 writes the fail-safe
value (FSOUT) configured in the DCI block to the device.
122
NOTE
If an output needs to have a fail-safe value before the corresponding DCI block or
the compound containing the block is deleted, you must write the fail-safe value
manually from the Foxboro Evo Control HMI or FoxView™ software.
DCI Block Processing

The following is an overview of DCI block processing (and data read/write) operations.
NOTE
Scheduling of block processing depends on the Period/Phase of the ECB or control
block. For proper operation, you must synchronize the associated ECB and control
block processing, if required, by configuring these parameters appropriately. It is
recommended that you use the default ECB values and modify only the block Peri-
ods and Phase.
The FDC280 processes the ECBs and DCI blocks as an integral part of its compound processing
each Basic Processing Cycle (BPC). The order of processing is the same as the order of the com-
pounds, ECBs, and blocks configured in the control database.
Processing of the ECBs and control blocks is performed in the following sequence:
1. Scheduling of a control block depends on its Period and Phase parameter settings. It is
the user’s responsibility to synchronize (if required) the associated ECB and control
block processing by configuring these parameters appropriately.
2. ECBs scheduled to be processed are executed to read fresh inputs:
When a parent or child ECB is processed, its list of DCI blocks is examined. For each
DCI input or output block ready to be run in that BPC, its DCI connection requests
are added to a read list for that ECB. When the read list is complete, data is collected
from Core 2 to populate the DCI Connection records. Core 2 manages the input data
asynchronously and independently of Core 1, according to the configured I/O scan
time. All read list data is moved into the DCI connection records in the DCI blocks as
data is retrieved.
3. Control blocks scheduled to be processed are executed:
When all ECBs have been processed, the control blocks are processed. When the DCI
blocks are processed, all DCI connection data is processed. (Refer to “Key DCI Block
Functions” on page 124 for a description of the common functions performed in the
DCI blocks.) During this processing, the DCI blocks set write request flags in the
DCI connection records for any outputs that need to be written to the field devices.
4. ECBs scheduled to be processed, and containing fresh outputs to be written, are
executed:
When all control blocks have been processed, the ECBs are processed once again to
drive the field outputs (in the control output blocks) that have been changed in that
BPC. When a DCI parent or child ECB is processed, its list of blocks is examined
once again. For each DCI connection record with a pending write request flag, a write
list is generated.
When the write list is complete, data is moved to a Core 2 output buffer and immedi-
ately (within 100 milliseconds) written to the corresponding device(s). (If necessary,
123
multiple messages are used to write all data requested by the DCI blocks for that
BPC.)
Key DCI Block Functions

Some key DCI block functions that can be selected by parameter settings are described in the fol-
lowing paragraphs. For more specific information on these functions, refer to the DCI block
descriptions (BIN, BINR, BOUT, RIN, RINR, ROUT, IIN, IINR, IOUT, PAKIN, PAKINR,
PAKOUT, STRIN, and STROUT) in Integrated Control Block Descriptions (B0193AX).
Periodic/Change-Driven Execution
All DCI blocks are executed periodically according to their Period/Phase parameter configuration.
The BOUT, ROUT, and PAKOUT blocks normally set write requests to Core 2 of the FDC280
only when their desired output value changes. If the secondary loop timer (SECTIM) is config-
ured nonzero in the BOUT or ROUT blocks (SECTIM does not apply to PAKOUT blocks),
write requests are also set in BOUT and ROUT blocks if the timer expires between output
changes.
Auto/Manual Mode Operation

All DCI blocks except PAKIN and PAKINR support the Auto/Manual mode of operation. This
allows the operator to substitute the inputs in the BIN/BINR, RIN/RINR, and IIN/IINR blocks,
and to drive the ROUT, IOUT, and PAKOUT outputs directly. Separate inputs can be used to
drive the outputs of the BOUT block when the block is in Manual mode (Set for the BOUT
block).
Simulation Mode
In the RIN/RINR, BIN/BINR, IIN/IINR, PAKIN/PAKINR blocks, the input is provided by a
separate, configurable input parameter. In the ROUT, IOUT, BOUT, and PAKOUT blocks, con-
firmation of the output value change is simulated automatically. The simulation mode may be
used in conjunction with the Auto/Manual mode. The two features may co-exist in any DCI
block.
Signal Conditioning and Linear Scaling

Signal conditioning and linear scaling of analog inputs/outputs can be configured in the
RIN/RINR and ROUT blocks. The SCI and SCO parameters can be used to specify any of the
standard signal conditioning algorithms supported by I/A Series control processor except thermo-
couple and RTD conversions. For a description of the SCI conditioning algorithms, refer to the
appendix associated with the RIN/RINR block, in Integrated Control Block Descriptions
(B0193AX). For a description of the SCO conditioning algorithms, refer to the ROUT block in
Integrated Control Block Descriptions (B0193AX).
Input Limiting
The input values of the RIN (RINR) block are constrained by the engineering range
(HSCI1/LSCI1) configured in the block. If the input value is out-of-range, it is clamped to the
high/low range value, and the corresponding Limited High/Limited Low (LHI/LLO) status bit is
set in the value record.
124
Confirmed Outputs
The outputs of the BOUT, ROUT, IOUT, and PAKOUT blocks are confirmed by a readback of
the actual value read from the field.
When an output is changed by Core 1 in one of these blocks, it is stored into a request location
that is part of the output value record in the DCI block. (In Control Core Services terminology,
this type of output is referred to as a “Shadow” output and is reflected in the Shadow status bit
(Bit 12) in the value record).
The actual output value of the DCI block will not be updated until confirmation of the requested
change is received during the next processing cycle of the DCI block. The request value is written
by Core 2 to the field device. If the field device allows the output value to be read by the
FDC280, the FDC280 uses the latest value from the field device as the DCI readback value. Oth-
erwise, after the write operation is performed, the FDC280 uses the request value as the DCI
readback value. On the next DCI block cycle, the block output value will be updated in Core 1
with the readback value from the field, thus completing the confirmation of the change. The
request value sent to the field device is also available as a separate parameter in the BOUT, ROUT,
and IOUT blocks and can be used to aid in diagnostic testing
Output Clamping
The output value of the ROUT block is constrained by the limit values (HOLIM/LOLIM) con-
figured in the block. The limit values are constrained by the engineering range (HSCO1/LSCO1)
configured in the block. If the output value exceeds its limiting constraints, it is clamped to the
high/low value, and the corresponding Limited High/Limited Low (LHI/LLO) status bit is set in
the value record.
Output Initialization
The output value of a BOUT, ROUT, IOUT, or PAKOUT block initializes to the value read back
from the field.
However, the initial output value is retained unchanged when modifying the configuration of a
block. (These are the conditions under which it is not desirable to change the current output
value).
Additionally, if an output block is configured Write-Only (refer to “Write-Only Points” in
FDC280 Modbus Master Drivers (Serial and TCP/IP) (B0700GT), the output value of the block
initializes to the block input.
Cascade Initialization
Upstream logic in a cascade is initialized by a BOUT, ROUT, or IOUT block in each of the fol-
lowing cases:
♦ When the DCI block initializes
♦ When the DCI block mode changes from Manual to Auto mode
♦ When the readback value transitions from Bad and/or Out-of-Service status to Good
status
♦ When the Initialization Input (INI_PT), if used, is cleared.
125
Redundant Input Selection

In the RINR, BINR, IINR, and PAKINR blocks, arbitration voting logic is used to select one of
the redundant input values. In the RINR block, an arbitration tolerance limit (ARBLIM) is used
to determine whether the analog inputs agree. In the BINR block, the discrete inputs must have
the same Boolean value in order to agree.
If any two inputs agree and are healthy, the first of the two inputs is selected. If none of the
healthy inputs agrees, or if none of the inputs is healthy, the selection is made according to a pre-
configured selection option (SELOPT) in the block.
DCI Parameter Status Bits

Table 5-4 shows the DCI parameter status (for example, the value record status for MEAS in a
RIN block). The bit numbers in Table 5-4 represent the bit numbers in the parameter status
word, not the block status bit of the DCI or other control blocks. User-written software applica-
tions can access any of the 16 bits of the value record status word. Refer to Integrated Control Soft-
ware Concepts for CP270, FCP280, and FDC280 (B0700AG).
Table 5-4. DCI Parameter Status
DCI Parameter Status1 Meaning

Out-of-Service (OOS) The Out-of-Service (OOS) bit is set when:
(Bit 11) ♦ a point is initialized
♦ the parent device (device connection) is not operational
♦ the point (data connection) is not operational
♦ the parent device is disabled
Bad Value (BAD) The Bad Value of a DCI connection is set when:
(Bit 8) ♦ an invalid floating point is detected
♦ a device becomes unavailable (no communication with the
device)
♦ the initial read back of a point configured with Write-Only
option.
Error (ERR) The Uncertain (ERR) bit is set when driver timestamping option
(Bit 15) (TSTAMP) is enabled but FDC280 has not yet synchronized its
clock.
Limited High (LHI) Not supported
(Bit 13)
Limited Low (LLO) Not supported
(Bit 14)
Fail-Safe (FS) Fail-safe has been asserted.
(Bit 4)
1. Standard Foxboro Evo status bits (used with all blocks)
126
6. Configuring FDC280 Using ICC
and CCS FDC280 Configurator
This chapter describes how to configure the FDC280 using the Integrated Control Configurator
(ICC) and CCS FDC280 Configurator.
Using ICC and ICC Driver Task Utility to Configure

FDC280
The Integrated Control Configurator (ICC) and ICC Driver Task utility can be used to configure
the Ethernet and serial ports of an FDC280, as an alternative to the Control Editors (which was
discussed in Chapter 5 “Control Block Configuration Information for I/O Functions”). ICC and
the ICC Driver Task are installed in Foxboro Evo workstations as part of the Control Core Service
installation. They can be used to configure any FDC280 stations hosted by the workstation on
which they are installed. Host assignments for FDC280s are determined at the time of system
configuration via System Definition utility, which is discussed in System Definition: A Step-By-Step
Procedure (B0193WQ), while the Control Core Services installation application saves this host-
FDC280 association in the host workstation.
For details on the usage of ICC, refer to Integrated Control Configurator (B0193AV).
The FDC280’s Ethernet port (ENET_PORT1) and four serial ports (SERIAL_PORTx) are pre-
sented as an ECB under the Primary ECB of an FDC280 in ICC, as shown in Figure 6-1.
127
B0700GQ – Rev C 6. Configuring FDC280 Using ICC and CCS FDC280
Figure 6-1. ECBs of FDC280’s Ethernet Port and Four Serial Ports in ICC
You can configure:

♦ One or more drivers under the Ethernet port
♦ One driver under each Serial port.
This appendix details how to configure parameters that are configurable in ICC and the ICC
Driver Task. However, for certain configurations, you have to use the CCS FDC280 Configura-
tor, discussed in “CCS FDC280 Configurator” on page 150. The CCS FDC280 Configurator is
used for these tasks:
1. Ethernet port data; for example, IP addresses of a simplex or fault-tolerant FDC280
2. ECB201 Device Option parameter exceeding 32 characters in length for devices con-
nected to a Serial or Ethernet port
3. Points in a device mapped to multiple groups.
The parameter values used in this appendix are examples for illustrative purposes only. The values
to use for each parameter are described in detail in previous sections of this document or in
FDC280 Modbus Master Drivers (Serial and TCP/IP) (B0700GT).
Installing FDC280 Ethernet/Serial Port Drivers

The FDC280’s Ethernet and serial port drivers have to be installed before configuration via ICC
or the ICC Driver Task can succeed. If you have not installed them already, install them as
described in this section.
Each of the FDC280 drivers have their own installers that will register themselves.
128
6. Configuring FDC280 Using ICC and CCS FDC280 Configurator B0700GQ – Rev C
To install these drivers:

1. Insert the CD-ROM (containing Modbus TCP Client 1.1 driver (K0177AH) or
Modbus Serial Master 1.0 driver (K0177CV)) in the host workstation's media drive,
or mount the installation media to a network location accessible by the host worksta-
tion.
2. Navigate to the root directory of the CD-ROM or installation media using Win-
dows/File Explorer.
3. Double-click the installer package.
4. Follow the on-screen instructions to install the FDC Driver files.
Overview for Modbus TCP Client Driver Installation

Install the Modbus TCP Client driver file on the workstation running Control Core Services v9.3
or later that hosts the FDC280 using the Modbus TCP Client Driver media for FDC280
(K0177AH).
The media installs the supported files for the FDC280 Modbus TCP Client 1.1 and Modbus
TCP Client 1.0 to configure in ICC.
Figure 6-2 shows the results of a successful installation of the media.
Figure 6-2. FDC280 Modbus TCP Driver Installation
Overview for Modbus Serial Master Driver Installation

Install the Modbus Serial Master driver on the workstation running Control Core Services v9.3 or
later that hosts the FDC280 using the Modbus Serial RTU and ASCII Driver media for FDC280
(K0177CV).
129
The media installs the supported files for FDC280 Modbus Serial Master to configure in ICC.
Figure 6-3 shows the results of a successful installation of the media.
Figure 6-3. FDC280 Modbus Serial Driver Installation
130
Configuring Parameters in Station Block for FDC280 in ICC

You have to set the value of Redundancy Algorithm parameter (RDALGO) in the STATION
block as described in “Configure FDC280” on page 102. It can be set to “ALG=0” or “ALG=1”.
Figure 6-4 displays an example of setting the value of RDALGO to “ALG=1”.
Figure 6-4. Setting the Value of RDALGO in STATION Block in ICC
Configuring Ethernet Port ECB (ENET_PORT1) in ICC

The Ethernet port ECB (ENET_PORT1) contains configuration data for all Ethernet communi-
cations between the FDC280 and the field devices. Some of the parameters are configured using
ICC and others using CCS FDC280 Configurator (described in “CCS FDC280 Configurator”
on page 150). This ECB can be accessed in ICC as following.
1. Select the Compound <FDC280_letterbug>_ECB (for example FDC411_ECB) on
the initial screen of the FDC280.
2. In the Compound Functions menu, select View Blocks/ECBs in this com-
pound.
3. Select ENET_PORT1 in the left panel.
4. In the Block/ECB Functions menu, select Edit All Block/ECB Parameters.
Figure 6-5 below shows its configurable parameters in ICC. The parameter must be configured.
131
Figure 6-5. Parameters of Ethernet Port ECB in ICC
The valid values of ESPEED are:

♦ 0 = Auto (default)
♦ 5 = 1Gbps full [duplex]
Confirm that when setting the ESPEED value for an FDC280, the corresponding
switch port (to which the FDC280’s baseplate is physically connected) is also config-
ured with the same setting. If the FDC280 is set to use Auto-Negotiate, the switch
port must also be set to Auto-Negotiate. If the FDC280 is set to 10Mbs/Full, the
switch port must also be configured to 10Mbs/Full (not Auto Negotiate). This also
applies for circumstances in which the FDC280 has a direct connection to a field
device.
Additional configuration data, such as IP addresses, are configured via CCS FDC280 Configura-
tor, which is detailed in “CCS FDC280 Configurator” on page 150.
Configuring FDC280 Serial Port ECBs (SERIAL_PORT1-4)

The FDC280’s serial port ECBs (SERIAL_PORT1-4) contain configuration data for all serial
communications with the field devices. This ECB can be accessed in ICC as follows:
132
1. In the initial screen of the FDC280, select compound <FDC280_letterbug>_ECB (for

example FDC411_ECB).
2. In the Compound Functions menu, select View Blocks/ECBs in this com-
pound.
3. In the left panel, select the appropriate serial port ECB (SERIAL_PORT1-4).
4. In the Block/ECB Functions menu, select Edit All Block/ECB Parameters.
Figure 6-6 illustrates the configurable parameters in ICC. The configured parameters and their
values are underlined.
Figure 6-6. Parameters of Serial Port ECB in ICC
Key fields to consider updating are:

♦ SMODE - valid range is 0-6 (0 indicates disabled mode).
♦ SBAUD - valid range is 0-9.
♦ PARITY - valid range is 0-2.
♦ STBITS - valid range is 0-2.
♦ DTBITS - valid range is 5-8.
Configuring FDC280 Driver ECBs in ICC

You have to create and configure the FDC280 Driver ECBs manually, as they are not created by
default with the Ethernet port ECB and the serial port ECBs in the FDC280. Before you can
configure the drivers in ICC, install the FDC280 driver media as described in “Install FDC280
Drivers” on page 99. A Debug driver that can be used to diagnose communication issues with a
133
device is also available, and can be configured without having to install it separately from any
driver media.
NOTE
To make any configuration changes to a Primary ECB, the corresponding port must
be set to offline mode.
1. Select a compound or the Primary ECB (<Letterbug>_ECB) from the compound list
view in which you want your drivers to be configured.
Configuring drivers and devices under a compound has an advantage when moving
them from one FDC to another. If driver and device ECBs are under the Primary
ECB, the driver and device ECBs will not be loaded in when the LoadAll is done on
the SaveAll of another CP that is already in the Foxboro DCS network. If driver and
device ECBs are under a compound, they will be loaded in. You will only have to
change the parent names to reflect the ports with the new Primary ECB.
2. In the compound view, select Insert New Block/ECB.
Figure 6-7 displays an example of data provided to the driver ECB for an Ethernet
driver. The changed fields are boxed in red.
Figure 6-7. Ethernet Port Driver Configuration Data in ICC
♦ The Type must be ECB200.

♦ The HWTYPE must be 1.
♦ The SWTYPE must be 200.
♦ The PARENT must be ENET_PORT1.
134
♦ The DRVRID is the driver ID of the port. They are assigned as follows:
-1 = Diagnostic Driver
1 = Modbus/TCP 1.0
2 = Modbus Serial
3 = Modbus/TCP 1.1
Because this driver ECB is under a compound, the reference of PRIMARY_ECB is
included in the PARENT parameter. The DEV_ID can be the same or different from
the name of this ECB.
3. For an ECB of a Serial driver, the configuration data are similar except three fields
HWTYPE, PARENT, and DRVRID.
♦ The HWTYPE must be 2.
♦ The PARENT is SERIAL_PORT1-4.
Figure 6-8. Serial Port Driver Configuration Data in ICC
The ECB200 has a set of custom parameters (CPARM1-6) which allow you to customize the
behavior of the FDC280 driver. For the Modbus driver, you can only set CPARM1 - do not set
the others.
The FDC280 Modbus TCP and Serial RTU drivers support the following optional custom
parameter for CPARM1 (settable at Custom Parameter1)
The FDC280 TCP driver supports:
♦ “TSTAMP” - If this custom parameter is specified, then for all field devices, their
points are timestamped in the FDC280 when they are read from the field devices.
(TSTAMP can be specified at the device level.)
If “TSTAMP” is not specified, any value and status changes for an I/O point are time
135
stamped when the corresponding DCI block is processed.

Timestamping is explained in “Timestamping” in FDC280 Modbus Master Drivers
(Serial and TCP/IP) (B0700GT).
The FDC280 Serial Modbus RTU driver supports the selection of TSTAMP and RTU or ASCII
for the protocol. If the TSTAMP option is selected, the timestamping behavior is the same as
described above for the TCP driver. If the parameter is left blank, RTU is used by default.
Be aware that if you change these custom parameters in a driver which is running online, you
must take the driver offline and then put it online again in order to apply the change.
These custom parameters are different than those custom parameters used with the field devices,
shown in Figure 5-14 on page 113.
NOTE
To make any configuration changes to a driver ECB200, it must be set to offline
mode.
Configuring FDC280’s Field Devices in ICC

In the ICC hierarchy, the FDC280’s field devices are configured “children” of the FDC280 driv-
ers. Create new devices by selecting the Insert New Block/ECB command in the Compound
View. The devices’ parameters are configured as follows.
♦ TYPE = ECB201.
♦ The DEV_ID can be different from the ECB name.
♦ SWTYPE = 200
♦ For Ethernet devices:
♦ HWTYPE=1
♦ PARENT = Ethernet Driver
♦ DVNAME=IP Address/<Node Number>. See Figure 6-9 for an example.
♦ For Serial devices:
♦ HWTYPE = 2
♦ PARENT = Serial port driver
♦ DVNAME = Modbus address
♦ PORTNO = Serial port number to access the device. See Figure 6-10 for an exam-
ple.
♦ DVOPTS is specific to each device. Be advised that if the device options require more
than 32 characters, use the CCS FDC280 Configurator, discussed in “CCS FDC280
Configurator” on page 150.
Table 6-1 lists the key ECB201 parameters for field devices for configuration in ICC. Refer to
Integrated Control Block Descriptions (B0193AX) for the ECB201 parameter definitions.
Table 6-1. ECB201 Key Parameters for Devices for ICC Configuration

General NAME Contains the name used by the FDC280 to access this ECB.
136
Table 6-1. ECB201 Key Parameters for Devices for ICC Configuration (Continued)

General Block Description
Description
Block Sample The block’s execution time base, 1 = 0.5 second. This is the scan
Time period at which the Control Processor scans DCI blocks. The
(PERIOD) scan rate of the device is independent of this scan period.
Block Phase Block phase number
Number
FBM Device Identi- A unique 6-character ID. This is the device identifier shown in
fier the System Manager.
Device Name This field contains the IP address of the device and optionally
the node address.
FDC280 x.x.x.x
Single Mo Example: 192.168.1.25
de
OR
x.x.x.x/n
Example: 192.168.1.25/1
Where x.x.x.x is the Modbus Device's IP

address, and n is the Modbus Device Address1.
The Modbus Address is optional, and it is usually

unnecessary for most device types. The Modbus
Device Address can either be specified here, or in
the DVOPTS parameter. For certain configura-
tions such as interfacing Modbus Plus (serial
devices) through a bridge, the Bridge IP address
and the serial device address, which is the device
address, are used. The later is also referred to as
Node number.

through the Modbus Plus to Ethernet Bridge
(MEB), the IP address of the MEB and the Mod-
bus Plus device address must be specified.
137
Table 6-1. ECB201 Key Parameters for Devices for ICC Configuration (Continued)

FBM Device Name FDC280 x.x.x.x;y.y.y.y
(Cont.) Fault-Tol- Example: 192.168.1.25;192.168.1.26
erant OR
x.x.x.x/l;y.y.y.y/r
Example: 192.168.1.25/1;192.168.1.26/2
Where x.x.x.x is the Modbus Device's left IP

address, l is the left Modbus Device Address
y.y.y.y is the Modbus Device's right IP address,
and r is the right Modbus Device Address.
The Modbus Addresses are optional, and they are

usually unnecessary for most device types.
The Modbus Device Addresses can either be speci-

fied here, or in the DVOPTS parameter.
NOTE
The maximum number of charac-
ters allowed in the DVNAME
parameter is 32. If the length of
the DVNAME parameter exceeds
32, specify the Modbus Device
Addresses in the
DVOPTS parameter using the
“+LN=xx” and “+RN=xx”
options.

through MEB, the IP address of the MEB and the
Modbus Plus device address must be specified.
Device The name of the protocol plus any required options. Refer to
Options “Configuring the Device Options Parameter” on page 140.
1.
“Device address” in this document is the same as “Unit Identifier” in the Modbus Messaging On
TCP/IP Implementation Guide V1.0b document, part of the documentation set in the Preface of
FDC280 Modbus Master Drivers (Serial and TCP/IP) (B0700GT). The default device address is
255. Some devices ignore the device address.
To access points in a device as multiple sets each with a different scan rate or for custom memory
mapped devices, you have to use the Groups functionality described in “CCS FDC280 Configu-
rator” on page 150.
138
Figure 6-9. Ethernet Device Configuration Data in ICC
Figure 6-10. Serial Device Configuration Data in ICC
139
Configuring the Device Options Parameter

The Device Options (DVOPTS) parameter can be set to any of the following desired options.
These options can be appended in any order or combination (unless explicitly stated otherwise).
♦ +@scan rate – Scan rate value in tenths of a second. For example, for a 2 second
scan rate applied to all query messages for this device, DVPOPTS = +@20. The default
scan rate is 500 ms (1/2 second).
♦ +H configures the driver to use Modbus function code 8 as a heartbeat. Without this
option, the driver uses the default heartbeat method described in “Device Fail Opera-
tion and Heartbeat” listed in FDC280 Modbus Master Drivers (Serial and TCP/IP)
(B0700GT).
+H=address configures the driver to use the specified Modbus address for its
heartbeat.
If you enter +H, function code 8 message is used for the heartbeat. If you enter
+H=address, the reading of the point at the address is used for the heartbeat.
♦ +DUPS enables the Modbus driver to allow multiple DCI blocks to be configured for
the same address (i.e. duplicate addresses allowed).
♦ +TSTAMP is used for enabling the timestamp option for this device. Timestamping is
explained in “Timestamping” in FDC280 Modbus Master Drivers (Serial and TCP/IP)
(B0700GT).
♦ +TO=n – (Where O is the letter “O”) Applies a response timeout value, specified by n,
to this device. The timeout value is in tenths of a second. The default timeout value is
500 ms (1/2 second). If TO=0, the default value is used. Vendor device product
documentation may suggest a proper response time for the device. The FDC280
response timeout period should be set to this time.
+TO=Mn (where O is the letter “O”) configures a response timeout value to be used
instead of the default value, where “n” (1 - 999) is equal to the timeout value in milli-
seconds. (The entered value is rounded up internally to nearest 10ms.) Default time
out value (500ms) will be used if “n” value is not in the specified range or not config-
ured. This option is used to achieve sub-100ms durations. Vendor device product
documentation may suggest a proper response time for the device.
♦ +LN=xxx – Specific for the FDC280 Simplex or, for an FDC280 pair, the module
installed in the left slot in the FDC280 baseplate; applies the Modbus device address
for the single FDC280 or the Left FDC280, where xxx can be a 1 to 3 digit address
(1 to 254). If you do not specify a device address, a default device address of 255 is
used. (This option is not available for Modbus serial devices, i.e. HWTYPE=2.)
♦ +RN=xxx – For an FDC280 pair, the module installed in the right slot in the FDC280
baseplate; applies the Modbus device address for the Right FDC280, where xxx can
be a 1 to 3 digit address (1 to 254). If you do not specify a device address, a default
device address of 255 is used.
♦ +RT=n configures the number of retries to attempt when a response timeout occurs,
where “n” (0-9) is equal to the number of retries. Default retries (2) will be considered
if “n” value is not in the specified range or not configured. (This option is not avail-
able for Modbus serial devices i.e. HWTYPE=2.)
♦ +SC or +MC specifies the Modbus function code for writing to coils when the device
does not support both single and multiple write function codes. “+SC” specifies that
140
the device supports only function code 05 (Force Single coil) for writing to coils.
“+MC” specifies that the device supports only function code 15 (Force multiple coils)
for writing to coils. “+SC” and “+MC” are mutually exclusive options. If both options
are specified (“+SC+MC” or “+MC+SC”) at the same location (in the DVOPTS
parameter of ECB201), the device will be marked as Invalid.
♦ +SR or +MR specifies the Modbus function code for writing to registers when the
device does not support both single and multiple-write function codes. “+SR” speci-
fies that the device supports only function code 06 (Force Single register) for writing
to registers. “+MR” specifies that the device supports only function code 16 (Force
multiple registers) for writing to registers. “+SR” and “+MR” are mutually exclusive
options. If both options are specified (“+SR+MR” or “+MR+SR”) at the same
location (in DVOPTS parameter of ECB201), the device will be marked as Invalid, if
the Groups are not used at ECB201. And also a message “Invalid options +SR+MR
specified for device” will be displayed in smon_log.
♦ +TP configures the Shadow FDC280 to use Internet Control Message Protocol
(ICMP) ping as an alternative heartbeat mechanism to verify device connectivity. To
enable this option, at least one point or heartbeat needs to be configured for the corre-
sponding device.
♦ +BPIV, or Bypass Input validation. By default the driver validates all fields of a Mod-
bus response message from a connected device as per the Modbus Protocol
specifications listed in “Modbus Protocol Documents” in FDC280 Modbus Master
Any response message that does not conform to the protocol completely is discarded.
This feature addresses security considerations from the device interface’s point of view.
If you need to connect to a device that does not fully comply with the Modbus Proto-
col, you can bypass the input validation feature by using this +BPIV, option.
This parameter can take multiple concatenated settings. The delimiter between each
setting is a single space. All the possible options can be concatenated. There is no max-
imum number of characters for this parameter.
For Modbus Plus devices through MEB:
1. An ECB201 block should be created for each Modbus Plus device under an MEB.
The IP address of the MEB should be specified in the DVNAME parameter and the
Modbus Plus device node address should be specified using the “/m” notation in the
DVNAME parameter or the “+LN=” (Simplex, non-fault-tolerant FDC280) or
“+LN=” and “+RN=” (Fault-tolerant FDC280) options in DVOPTS parameter of the
ECB201 block.
2. The options are independently configurable for each Modbus Plus device.
3. The MEB uses the specified Modbus Device Address for routing messages to the
appropriate end device. Each end device must have a corresponding route configured
in the MEB’s routing table. Please refer to the MEB's user's guide (Schneider Elec-
tric's Document Model no. 31005104) for instructions on configuring the routing
table.
4. Both the Left and Right FDC280s communicate to the same MEB, therefore the LN
and RN values must be identical.
141
When including options in your DVOPTS parameter that require a configured value
(such as +@rate or +TO=n), if you do not enter a value for the option (such as
"+@+TO="), then the default value for that option is used.
The following is an example setting of the Device Options parameter:
Device Options = +@10+H+TO=20+LN=5+RN=123
This syntax indicates that there is a one second scan rate for queries; the Function Code 8 heart-
beat option is applied; the Response Timeout setting is two seconds; the Left FDC280 is con-
nected to device address 5; and the Right FDC280 is connected to device address 123.
Options Applicable to Serial Ports Only

♦ +ECTDLY option:
The Modbus master driver supports the introduction of a configurable delay between
the RTS assertion and the first byte of data transmission. The driver also introduces a
time delay between the last byte of data transmission and RTS De-Assert, to interface
with the slow radio link devices in RS-232 Serial communication.
The option (+ECTDLY) has to be configured in the CPARM1 parameter of ECB200.
Early Assertion and Delayed Negation (+ECTDLY=y): Configure the ECTDLY option
to enable the early assertion and delayed negation of the RTS signal, where y is one
hundredth of a second. If you do not specify the value for the option, the default value
is 0 (zero) and the maximum value is 6000. If the value of y is greater than 6000, the
driver will be marked NOTREADY and a diagnostic message “Max Supported
value for ECTDLY option is 6000” will be displayed in smon_log.
For example: if +ECTDLY=20, the driver introduces a 200 millisecond early assertion
and delayed negation of the RTS signal during the transmission of the data packet in
RS-232 communication.
The +ECTDLY option is supported only for RS-232 (Single and dual port modes). If
configured in other modes, the driver will be marked NOTREADY and a diagnostic
message “ECTDLY option is supported only for RS-232 Modes” will be dis-
played in smon_log.
♦ +RD option:
This Modbus driver can support a response delay when transmitting messages to the
device. This configuration is necessary for some devices that cannot handle fast
requests.
The option (+RD) has to be configured in the CPARM1 parameter of ECB200.
Response Delay (+RD=n): Enables a response delay between messages sent to the
device, where n indicates the time in milliseconds. The default value is 0 (zero).
Commit Configuration Changes

Commit changes or new configurations to the FDC280 with command NEW or CHECKPOINT
from the ICC menu bar. The command NEW performs the CHECKPOINT operation before closing
the FDC280 configuration.
142
Using ICC Driver Task

Instead of using ICC to configure control parameters of an FDC280, you can use the ICC Driver
Task. Whereas ICC provides an interactive mechanism, ICC Driver Task provides a scripting
mechanism. First create an input file that follows instructions provided in I/A Series Integrated
Control Configurator Application Programing Interface (B0193NE). Once an input file is created, it
can be used with command iccdrvr.tsk.exe at a command prompt to configure the FDC280.
An example of using this command is:
iccdrvr.tsk.exe -i FDC409_icc_cfg.txt -o iccresult.txt -d iccdata.txt
where FDC409_icc_cfg.txt is the input file.
The content of this input file is provided later in this section as an example. The command
iccdrvr.tsk.exe -h can provide a brief instruction how to use the utility. Figure 6-11 depicts
an example execution of the command.
Figure 6-11. Example of Using iccdrvr.tsk.exe
The content of the input file FDC_icc_cfg.txt is printed here as an example.

# This file is an input file to iccdrv.tsk.exe.
# Lines starting with a number sign '#' are comments which will be ignored
# by iccdrv.tsk.exe.
#
# Refer to document "I/A Series Integrated Control Configurator Application
# Programming Interface" (B0193NE) for usage.
# Open an ICC session with the CP. Its letterbug is FDC409.
143
OPEN FDC409 ALL TESTDATABASE
# Modify parameter RDALGO of STATION block

MODIFY FDC409_STA:STATION
RDALGO = ALG=1
END
# Set the value of ESPEED of Ethernet Port ECB to, for example 2,
# which is 10Mbps full duplex.
MODIFY FDC409_ECB:ENET_PORT1
ESPEED = 2
END
# Set the parameters of SERIAL_PORT1

MODIFY FDC409_ECB:SERIAL_PORT1
SMODE = 1
SBAUD = 6
PARITY = 2
STBITS = 0
DTBITS = 8
END
# Set the parameters of SERIAL_PORT2

SMODE = 1
SBAUD = 6
PARITY = 2
STBITS = 0
DTBITS = 8
END
# Set the parameters of SERIAL_PORT3. Only setting SMODE. Others are kept
as default.
SMODE = 1
END
# Set the parameters of SERIAL_PORT4. Only setting SMODE. Others are kept
as default.
SMODE = 1
END
# Add a compound DRVRS_DEVS to hold driver and device ECBs.

ADD DRVRS_DEVS
TYPE = COMPND
144
DESCRP = Compound for Drivers and Devices

ON = 1
END
# Add an Ethernet driver.

ADD DRVRS_DEVS:EDRV01
TYPE = ECB200
DEV_ID = EDRV01
HWTYPE = 1
SWTYPE = 200
PORTEX = 1
PARENT = FDC409_ECB:ENET_PORT1
DRVRID = 1
END
# Add a Serial driver on Serial Port 1.

ADD DRVRS_DEVS:SDRV01
TYPE = ECB200
DEV_ID = SDRV01
HWTYPE = 2
SWTYPE = 200
PORTEX = 1
PARENT = FDC409_ECB:SERIAL_PORT1
DRVRID = 2
END

TYPE = ECB200
DEV_ID = SDRV02
HWTYPE = 2
SWTYPE = 200
PORTEX = 1
DRVRID = 2
END

TYPE = ECB200
DEV_ID = SDRV03
HWTYPE = 2
SWTYPE = 200
PORTEX = 1
145
DRVRID = 2
END

TYPE = ECB200
DEV_ID = SDRV04
HWTYPE = 2
SWTYPE = 200
PORTEX = 1
DRVRID = 2
END
#Add an Ethernet device with DVOPTS empty.

ADD DRVRS_DEVS:EDV102
TYPE = ECB201
DEV_ID = EDV102
HWTYPE = 1
SWTYPE = 200
PARENT = EDRV01
DVNAME = 192.168.100.31/1
DVOPTS =
END
# Add a Serial device under Port 1 driver with DVOPTS.

# DEV_ID is different from the ECB name.
ADD DRVRS_DEVS:S1DV01
TYPE = ECB201
DEV_ID = SDV101
HWTYPE = 2
SWTYPE = 200
PARENT = SDRV01
DVNAME = 1
DVOPTS = +@10+TO=5+H=30001+DUPS+RT=3
END

TYPE = ECB201
DEV_ID = SDV201
HWTYPE = 2
SWTYPE = 200
PARENT = SDRV02
146
DVNAME = 1
END

TYPE = ECB201
DEV_ID = SDV301
HWTYPE = 2
SWTYPE = 200
PARENT = SDRV03
DVNAME = 1
END

TYPE = ECB201
DEV_ID = SDV401
HWTYPE = 2
SWTYPE = 200
PARENT = SDRV04
DVNAME = 1
END
CLOSE
EXIT
Recovery From Detected Error State Adding a Second

ECB200 As a Child to An FDC280 Serial Port
Each FDC280 serial port can support only one driver represented by ECB200. If you inadver-
tently added another driver ECB200, use the steps described in this section to recover from the
resulting state.
If an attempt is made to add a second ECB200 (FDC280 Driver) as a child to an FDC280 Serial
Port (SERIAL_PORT1, 2, 3, or 4), a system message will be generated in ICC, as shown in
Figure 6-12. The block has not been created in the FDC280 when this occurs but the entry is still
in the work file at this point.
147
Figure 6-12. System Message - Insufficient FBM Memory/Connections
If you click Continue, ICC returns to the list of parameters for the same block.
If you click Cancel, ICC returns to the lists of blocks in the currently selected compound.
If you click Done, the message shown in Figure 6-13 will be displayed indicating that the block
does not exist. Click Continue.
148
Figure 6-13. System Message - E16 - Compound or Block Not Found
To resolve this, it is necessary to delete the block. A serial port on an FDC280 module can have
only one driver attached. Select the block and select Delete. A system message will be generated,
shown in Figure 6-14, which can be ignored. The block is now removed from the work file.
149
Figure 6-14. System Message - ECB Configuration File Not Identified
CCS FDC280 Configurator

The CCS FDC280 Configurator is a Windows GUI application which performs additional
FDC280 configuration tasks outside of those performed by ICC or the ICC Driver Task, for data
that cannot be configured via ICC or the ICC Driver Task. If you are planning to configure the
FDC280 and its field devices with ICC, perform the procedures in “Using ICC and ICC Driver
Task Utility to Configure FDC280” on page 127 to configure standard data for the ports, drivers
and devices, and then return to this appendix to complete the configuration.
The CCS FDC280 Configurator configures additional data, such as:
1. One or two IP addresses of the Ethernet port. At least one address is needed for an
FDC280 to communicate with Ethernet field devices.
2. Device options that exceed 32 characters in length.
3. Points in a device mapped to multiple groups.
This configurator is used only after basic configuration of the Ethernet port, serial ports, drivers,
and devices have already been done on the FDC280 via ICC or the ICC Driver Task. The config-
urator accesses the list of drivers and devices configured using ICC when first opened to allow the
user to configure groups and device options for the only the pre-configured devices in ICC.
150
In addition, the CCS FDC280 Configurator provides other capabilities such as:
1. Deploying the configured data from the configurator to the target FDC280.
2. Allowing users to archive a configuration for later modification and deployment or for
using it as a template for another FDC280.
3. Allowing users to edit the configuration data of an FDC280 which is not hosted by
the configurator workstation. The configuration data can be archived to a file and
brought over to the host station for deployment.
4. Display a list of drivers which are installed in host machine and their details.
Values used in this appendix might not reflect all possible values of any field. For full specifica-
tions of each field, refer to Chapter 5 “Control Block Configuration Information for I/O Func-
tions” and FDC280 Modbus Master Drivers (Serial and TCP/IP) (B0700GT).
NOTE
For running the CCS FDC280 Configurator on stations with Enterprise Edition
Control Core Services v9.3-9.4, add new Group policies to the PDC on the net-
work as described in Appendix B “Improving Performance of the CCS FDC280
Configurator on Stations with Enterprise Edition Control Core Services v9.3 or
Later”.
Installation of CCS FDC280 Configurator

The CCS FDC280 Configurator is installed as part of Maintenance Pack MP47481162 on a CP-
host workstation. (MP47481162 is available from the GCS website.) Once installed, the configu-
rator can be invoked from FoxView, under the Config menu with an entry named FDC_Cfg.
Refer to Figure 6-15.
Figure 6-15. Invocation of CCS FDC280 Configurator in FoxView
Invoke the CCS FDC280 Configurator by selecting this FDC_Cfg entry. Figure 6-16 displays a
startup view of the configurator.
151
Figure 6-16. Startup View of CCS FDC280 Configurator
Only one instance of the CCS FDC280 Configurator can run at any time. Subsequent startups
from the FoxView will open a dialog box (Figure 6-17) indicating an instance of the CCS
FDC280 Configurator is already running.
Figure 6-17. System Message When Starting an Additional CCS FDC280 Configurator Instance
Select OK, then locate the active instance in the Taskbar (Figure 6-18). Click it to bring it to the
front.
Figure 6-18. Active CCS FDC280 Configurator Instance in the Taskbar
152
CCS FDC280 Configurator Layout

Figure 6-19 provides an overview of the layout of the CCS FDC280 Configurator. Each area is
described in detail in subsequent sections.
(A)
(B)
(C)
(E)
(D) (F) (G) (H) (I)
Figure 6-19. CCS FDC280 Configurator Layout
Table 6-2. Figure 6-19 - CCS FDC280 Configurator Layout Legend
Item Description
(A) Configured FDC280 or Drop-Down FDC280 List
(B) Configuration Data
(C) Activity Log
(D) List of installed drivers
(E) Tree view of ports, drivers, and devices
(F) Deploy changes to the FDC280
(G) Load up an archived configuration
(H) Save the configuration
(I) Exit the CCS FDC280 Configurator
153
Blue texts and pen icon indicates changes have not been deployed to the FDC280.
Blue texts and red 'x' icon indicates an input error. In the example above, the subnet mask has
five fields instead of four.
Opening an FDC280 in CCS FDC280 Configurator

To configure an FDC280 in the CCS FDC280 Configurator, select the FDC280 from the drop-
down list. Figure 6-20 shows an example of an FDC280 list. Only FDC280s hosted by the work-
station are shown.
Figure 6-20. List of FDC280s Hosted by the Workstation
Once an FDC280 is selected, the configurator will communicate with the FDC280 to confirm it
is online and to retrieve the latest configuration. If the FDC280 is accessed by another utility,
such as ICC or the ICC Driver Task, the retrieval will not succeed. A system message will report
this condition in the Messages panel. Also, if the configurator cannot find the selected FDC280,
it will not display the configuration. Figure 6-21 displays an example of an FDC280 that cannot
be reached by the configurator.
154
Figure 6-21. Example of an Unreachable FDC280
The configuration data of an FDC280 can be already committed (that is, deployed) into the
FDC280. This data can be modified in the configurator and archived to an XML file for further
modification and deployment later. When you load the XML file into the configurator, if any dif-
ferences are found, the configuration checks and flags the changed drivers or devices with a
change indicator - blue text and a pen icon. You can deploy these differences to the hosted
FDC280(s). For more information, refer to “Deploying a Configuration” on page 162.
Figure 6-22 describes the flow of configuration activities of an FDC280. Unless noted directly,
these activities are performed in the CCS FDC280 Configurator.
155
Figure 6-22. Configuration Activity Flow Diagram for CCS FDC280 Configurator
Configuring IP Addresses in CCS FDC280 Configurator

IP address data can be configured by selecting IP Address in the configurator’s tree view. If your
FDC280 is fault- tolerant, the left IP address data and right IP address data are shown in Ethernet
Port Configuration panel. Type in the IP addresses, the subnet masks, and the Default Gateway’s
IP addresses for the two sides. Figure 6-23 provides an example of IP address data. Note the fields
are changed into edit mode when changed.
Figure 6-23. IP Address Configuration Data for Fault-Tolerant FDC280
156
If your FDC280 is simplex (single), only one set of IP address, subnet mask, and gateway data is
shown in the Ethernet Port Configuration section of the configurator.
Configuring Device Options in CCS FDC280 Configurator

A device’s options are presented in the Options field in the Device Configuration panel. This field
allows you to provide device options that are longer than 32 characters, which is not allowed in
ICC. (Options with 32 characters or less are also accepted by this field.) Figure 6-24 shows an
example of an Options field with 42 characters for device DEE101.
Figure 6-24. Device Options in Options Field in Device Configuration Panel
Once an Options field with more than 32 characters is deployed, it will be shown in ICC and Sys-
tem Manager in the form of first 29 characters, followed by three dots (…). For example:
MODBUS+@10+TO=5+H+DUPS+LN=201...
Configuring Groups in a Device

The CCS FDC280 Configurator provides three command buttons to add groups, delete groups
and undelete groups. Figure 6-25 depicts the three buttons within the Device Configuration
panel of a device, and the total number of groups. It is the total of all devices (see the blue circled
text).
157
Figure 6-25. Group Command Buttons and Group Counter
Each row under the three buttons represent a group. The Action field in each row provides the
status of each group:
♦ The empty field indicates the group has been deployed to the FDC280.
♦ The pen icon indicates the group has been deployed to the FDC280 and one or more
of the fields have been modified but have not been deployed.
♦ The plus sign (+) indicates the group has been added and has not been deployed.
♦ The “x” sign indicates the group will be deleted/removed from the device on the next
deployment.
Adding a New Group

Add a new group to a device by selecting the Add Group button. A new row is added to the bot-
tom of existing rows, and the plus (+) sign is shown in the Action field. The plus (+) will disappear
once a deployment is carried out successfully. A change in each field will turn its text into edit
mode (blue font along with edit pen).
Deleting/Undeleting a Group
Delete a group by selecting a group (i.e. a row), and then selecting the Delete Selected
Group(s) button.
♦ If the group is newly added and has not been deployed, the group will be deleted from
the configuration.
♦ If the group has been deployed already, an “x” will be added to the Action field. The
group will be deleted from the configuration once a deployment is carried out success-
fully. You can undelete this group via the Undeleted Selected Group(s) button.
The operation will remove the “x” sign from the row. The next deployment will not
remove the group from the device and from the configuration.
158
The CCS FDC280 Configurator allows users to delete/undelete multiple groups with one click.
To select a range of groups, for example from group 1 to group 4, first select group 1, and then
press the <Shift> key (on the keyboard) while selecting group 4. You can select an additional
group by pressing the <Ctrl> key (on the keyboard) while selecting an additional group.
Archiving a Configuration in CCS FDC280 Configurator

The CCS FDC280 Configurator allows users to archive a configuration to a file by selecting the
Archive… button, and then selecting the folder and providing a filename. You are responsible for
recording the folder location and the filename of the archived configuration. Configuration
archives are stored in XML format.
Be advised that archiving a configuration does not deploy the configuration to the FDC280. It
only saves the configuration data (old and new) to the specified file.
Loading an Archived Configuration in CCS FDC280 Configurator

Users can load an archived configuration into the configurator by selecting the Load… button.
The configurator will ask for the location (i.e. the folder) and the filename. Users are responsible
for the location and the filename of an archived configuration. The configurator will validate the
contents of the loaded file including the XML syntax. The configurator will abandon the load as
soon as a detected error is found. It will not attempt to salvage any part of the file. A message in
the Messages panel will reflect the non-completed load.
The loaded configuration will be checked against the active configuration. The possible scenarios
that can happen are:
1. The loaded configuration belongs to the same letterbug as the active configuration.
2. The loaded configuration does not belong to the letterbug of the active configuration
but belongs to a letterbug of an FDC280 hosted by the configurator workstation.
3. The loaded configuration does not belong to the letterbug of the active configuration
and also not belong to a letterbug of any FDC280 hosted by the configurator work-
station.
These subsections describe the behavior of the CCS FDC280 Configurator in each scenario.
Loaded Configuration of the Same Letterbug

Once the CCS FDC280 Configurator detects the loaded configuration belongs to the same letter-
bug of the active configuration, it will compare data in the loaded configuration with the data in
the active configuration. Any difference will be indicated with blue text and pen icon at the device
level and at the field level. The value in the fields will be the value from the loaded configuration.
In case of different items in the tree view, such as drivers or devices configured in the FDC280,
not appearing in the configuration file and vice versa, the configurator will include them both
with indicators. Drivers or devices that are in the configuration file but not in the FDC280 are
not selectable for deployment. Drivers or devices that are in the FDC280 but not in the configu-
ration file are indicated with an “x” icon. You still are able to deploy these devices. Figure 6-26
provides an example of this scenario.
159
(A)
(B)
Figure 6-26. Configuration File and FDC280 is Out Of Sync
Table 6-3. Figure 6-26 Configuration File and FDC280 is Out Of Sync Legend
Item Description
(A) These devices are in the configuration file, but not in the FDC280. They
are not selectable for deployment.
(B) Devices with the “x” icon are in the FDC280 but not in the configuration
file. You are still able to deploy these devices.
Loaded Configuration of a Different Letterbug

Once the CCS FDC280 Configurator detects the loaded configuration belongs to another letter-
bug, it will attempt to close the active configuration. If the active configuration has not been saved
after changes, it will notify the user with a dialog box. (Figure 6-27). You will have a chance to
archive/save the configuration.
160
Figure 6-27. System Message Notification of Archiving Before Closing
After the configurator closes the active configuration, it will attempt to connect and load the con-
figuration from the new FDC280 first and then treat the loaded configuration as it belongs to the
same active configuration.
Letterbug of the Loaded Configuration is Not Hosted By the Workstation

The CCS FDC280 Configurator allows you to modify an archived configuration of an FDC280
that is not hosted by the configurator workstation. Once the configurator detects such configura-
tion in loading, it will attempt to close the active configuration first if there is an active configura-
tion. The operation is described in detail in “Loaded Configuration of a Different Letterbug” on
page 160.
After closing the active configuration, the configurator will load in the requested configuration.
Figure 6-28 displays an example of the configuration. Notice that the Deploy button is disabled
because the configurator is not able to deploy this configuration.
Figure 6-28. Configuration Belongs to an FDC That Is Not Hosted By the Workstation
161
Deploying a Configuration
Commit changes to the FDC280 by selecting items from the tree view (IP Address or devices)
then selecting the Deploy button. Only selected items are deployed. In Figure 6-29, only changes
in IP Address, devices DEE101, DEE103, and DE0101 will be deployed. Changes in devices
DE0201 and DE0301 will not be deployed.
Figure 6-29. Only Selected Items Are Deployed in CCS FDC280 Configurator
Once the Deploy button is selected, the CCS FDC280 Configurator attempts to connect to the
FDC280 (FDC410 in Figure 6-29) to download the changed configuration. Therefore, for the
deployment to be successful, the FDC280 has to be online and not being used by ICC or ICC
Driver Task. If the IP Address data is deployed (as in Figure 6-29), confirm the Ethernet port is
offline. The deployment on the IP Address will not succeed if the Ethernet port is online, and a
system message in the Messages panel will relay this condition. As well the IP Address will still
remain in edit mode. You can turn the Ethernet port offline via System Manager. Access the Go
Off-line… command on the FDC280 as shown in Figure 6-30.
This also applies to devices. In order to deploy a device successfully, the communications state of
the deployed device must be disabled.
162
Figure 6-30. Access the “Go Off-Line…” Command in System Manager
For a deployed device with options longer than 32 characters and/or with one or more groups, a
file will be created to hold the data. The filename will be saved in parameter FILEID of the
device. The format of the filename is <Letterbug>_<Driver's DEV_ID>_<Device's
DEV_ID>.XML. Figure 6-31 provides an example of a filename in parameter FILEID. Notice
that the value of DVOPTS ends with three dots (…) to indicate the value is longer than 32 char-
acters.
163
Figure 6-31. Filename Saved in Parameter FILEID in ICC
Once a deployment completes successfully, all deployed items will turn into normal text. For
those items which do not complete successfully, a deployment will stay in the edit mode.
It is highly recommended that you always archive the latest configuration.
Modifying a Configuration Offline

There are two mechanisms you can use to configure additional data offline. The target FDC280
only needs to be online at the time of deployment.
♦ First, load an archived configuration into the CCS FDC280 Configurator, change val-
ues and save the configuration back to the file. For detailed instructions, refer to
“Letterbug of the Loaded Configuration is Not Hosted By the Workstation” on
page 161.
♦ As well, you can modify the contents of a saved configuration directly. It is highly rec-
ommended that an XML editor is used to help ensure the syntax remains correct.
♦ This mechanism allows you to change all configuration data, including the letter-
bug associated with the file. The names of port drivers and devices must match
the names of the port drivers and devices of the letterbug determined during con-
trol configuration.
164
♦ The modification can be performed in any station. When the file is ready for
deployment, you must copy it onto the host station, load it into the Configurator,
and deploy to the FDC280. For detailed instructions, refer to “Loaded Configura-
tion of the Same Letterbug” on page 159.
Figure 6-32 describes each field in the configuration file. The file is displayed with long lines are
wrapped to the next line.
Figure 6-32. Location of Fields in a Configuration File
Table 6-4. Figure 6-32 - Location of Fields in a Configuration File Legend
Item Description
(A) Letterbug
(B) IP Address Data
165
Table 6-4. Figure 6-32 - Location of Fields in a Configuration File Legend (Continued)
Item Description
(C) Driver with more than one device
(D) Device with one or more groups
(E) Device with no group
(F) Reminder that letterbug, port names, DriverIDs, DeviceIDs, and Block Names must
match those in ICC
Use the file FDC280Configuration.Sample.xml under directory C:\ProgramData\Schneider

Electric\CCS FDC280 Configurator\ as a template. The file is installed during the
installation of the CCS FDC280 Configurator.
Troubleshooting the CCS FDC280 Configurator

The status of every activity is logged in the Messages panel. Check this log after every activity. The
log is brief but descriptive, even in the case of an operation not succeeding. If possible, the log
provides hints for users to fix in case of an operation not succeeding.
This section elaborates cases in additional detail beyond that shown in the Messages panel. Also
check the smon_log for information that conditions that did not succeed - for example, the
“Invalid Gateway Configured in ECBP” message.
Table 6-5. Troubleshooting the CCS FDC280 Configurator
Activity log or Symptom Diagnostic and/or Solution

Communication to FDC failed. Caused by one of the following reasons:
<letterbug> ♦ The FDC280 is not online.
♦ The configurator is unable to communicate with
the FDC280. It could be due to network corrup-
tion.
♦ The configurator is unable to retrieve data from the
FDC280. It could be ICC or the ICC Driver Task
is accessing the FDC280.
In this case, the message “Get FDC failed. Database
locked.” should be in the next line.
(Alternatively) Devices are not properly configured. For example, the
Communication to FDC failed. value of the parameter PARENT of a driver is spelled
<letterbug> “ENET_PORT” instead of “ENET_PORT1” (with the
- OR - letter “1” at the end) and there is at least one device
Get controller failed. Device: <device under this driver.
name> doesn’t have a driver,
Device file downloaded failed for Confirm the IP Address data has been provided to the
<Letterbug>/<Driver>/<Device> FDC280. If the address has not been provided, deploy it
at least at the same time as deploying the device.
166
Table 6-5. Troubleshooting the CCS FDC280 Configurator
Activity log or Symptom Diagnostic and/or Solution

Device configuration doesn't exist for In the rare case of this condition occurring, apply one of
FDC280: <Letterbug>/driver's these workarounds.
<DEV_ID>, device's DEV_ID. 1. Load the archived configuration of the FDC280, and
then deploy.
2. Re-enter the configuration data of the device(s), and
then deploy.
Error: <something> is invalid… Starting with “Error” and a colon “:” is an XML related
detected error. For example, “Error: The element
‘Device’ has invalid child element ‘Group’.” is shown in
the Messages panel if there are more than 2000 groups in
the loaded XML configuration file.
167
168
7. Principles of Operation
This chapter describes the fault-tolerant FDC280 operation.
Fault-Tolerant FDC280 Operation

During every BPC, the value and status of all the I/O points are copied from the Primary
FDC280 to the Shadow FDC280 so that when a role switch occurs, the point value and status is
preserved. When a role switch takes place, the Shadow FDC280 is in position to take over as the
new Primary because it already has all the required configuration information including current
input/output data values and it is communicating with the same Modbus devices.
On every BPC, the connections status of all the devices on the Shadow FDC280 is monitored by
the Primary FDC280 and the device status reported to the System Manager is updated. A device
with “good” connection status with both the modules is marked “good”. If connection status is
“good” from the Primary FDC280 and “failed”/bad from the Shadow FDC280, the device status
is set to yellow condition and an alarm is raised. If the device connection is “failed”/bad from both
the FDC280s, the device is marked “Failed” (red) and an alarm is raised. Also if the device is
unavailable from the Primary FDC280, available from the Shadow FDC280, and failover is not
permitted by the failover logic, the device is marked “Failed” (red) and a detected alarm is raised.
For an example of device status changing to “Failed”, refer to section “Device Unavailability
Operation and Heartbeat” in FDC280 Modbus Master Drivers (Serial and TCP/IP) (B0700GT).
The Primary FDC280 constantly runs a redundancy algorithm to check if a failover to the
Shadow module is required in case of loss of link to the I/O Ethernet network or loss of connec-
tion to one or more devices.
If the loss of a link to the customer-supplied Ethernet I/O network is detected via the Primary
FDC280, the redundancy algorithm running on the Primary FDC280 triggers an automatic role
switch, with the Primary FDC280 rebooting to become a Shadow module and Shadow FDC280
switching to the role of Primary module.
If the Primary FDC280 loses connection to one or more devices, depending on how the Redun-
dancy Algorithm (RDALGO) is configured, Core 1 receives a request for a role switch to com-
plete the failover. Refer to Figure 5-4 on page 103 for details on how to configure the
Redundancy Algorithm.
When the Redundancy Algorithm is set to default (ALG =0, the “match and more” algorithm),
the role switch operation is requested if the Shadow FDC280 has good connection status to all
the devices for which the Primary FDC280 has good connection status and also to additional
devices for which the Primary FDC280 does not have good connections status. When the algo-
rithm is set to 1 (ALG=1, the “more and better” algorithm), the role switch operation is requested
if the Shadow FDC280 has more number of devices with “good” connection statuses.
If an automatic role switch does not occur because both the Primary and Shadow FDC280s have
lost some device connections, you can force a manual role switch using the System Manager by
selecting to reboot the Primary module.
If a dual-ported device is unable to communicate on its port connected to the Primary FDC280
and an automatic role switch cannot occur due to one or more unavailable devices on the Shadow
169
B0700GQ – Rev C 7. Principles of Operation
FDC280, the device is marked “Failed” and the device's icon on the equipment displays in the
System Manager is changed to red, as the FDC280 will not be able to acquire any inputs from
this device. Since an automatic role switch only occurs if the partner module is able to reach all
the enabled devices, you could disable communication to the detected “Failed” devices to force
the automatic role switch functionality with the FDC280s communicating to “good” devices
only. This may be used to achieve the automatic role switch functionality while fixing or replacing
the “Failed” devices.
The FDC280s also have their Primary and Shadow LEDs to indicate their role status. The Equip-
ment Information pages in the System Manager indicate Primary and Shadow connection status
for each device. If the ECBs display as yellow, you can use these displays to determine which side
of the connection has stopped working. For example, if the device ECB is yellow and the ECB201
display shows the status “Left active, Right failed”, it implies that the FDC280 is acquiring data
from the device through the Ethernet I/O network connected to the left Ethernet I/O port on the
baseplate, and that the left FDC280 is the Primary module.
If the device ECB is shown as red and the ECB201 display shows the status “Left active, Right
failed”, this implies that the FDC280 is acquiring data from the device through the left Ethernet
I/O port on the baseplate, and that the right FDC280 is the Primary module. This occurs if the
Redundancy Algorithm on the Primary FDC280 determines that failover must not be affected.
Fault Tolerant FDC280 Operation With Devices On Multiple

Ports
When multiple ports have been configured for an FDC280, the FDC280 redundancy algorithm
takes a short-cut decision during a failover condition based on port status.
The rules for short-cut decision are:
1. All in-use ports of the Primary FDC280 should be in the detected “Failed” state and
the Shadow FDC280 should have at least one in-use port that is in the good state with
at least one connected device.
An “in-use port” is defined to be a port that has been configured with devices and the
port is enabled.
2. If above condition is satisfied, the Shadow FDC280 is considered to have better
device connectivity and a role swap between the two FDC280s will occur.
If the above criteria are not satisfied, the FDC280 role swap mechanism works based
on Good/Fail device counting. It applies the MATCH AND MORE or MORE IS
BETTER algorithm according to the FDC280 STATION block configuration. These
algorithms are discussed in “Fault-Tolerant FDC280 Operation” on page 169.
Fault Tolerant FDC280 Operation With Single Ported Devices

The redundancy logic is same as for dual-ported devices. The MATCH AND MORE and
MORE IS BETTER redundancy algorithms are applicable. For the serial single ported devices,
any one of the FDC280 modules can interface them at a time.
Communication Through Primary FDC280 With Periodic Testing From

Shadow FDC280
Communication with single-ported ECB201 devices configured under Serial ECBP
(SERIAL_PORT(n)), configured in single-ported mode (SERIAL_PORT(n) ECBP’s SMODE
170
7. Principles of Operation B0700GQ – Rev C
parameter should be 4, 5, or 6), is predominately through the Primary FDC280. During this
time, the Shadow FDC280 disables its communication on the corresponding port to help prevent
interference with the Primary FDC280's communication as both modules share a single physical
communication line.
To check the ECB201 device connectivity status for the Shadow FDC280 module for redundancy
functionality, the Primary FDC280 relinquishes the control of the ECBP Serial port, called as a
“port handover”, on a periodic basis so that the Shadow FDC280 module can test its connectivity
to the ECB201 device. This period is called a “port handover period, which is a configurable
parameter through custom parameters of ECB200 Driver block.
The exchange of control (from Primary to Shadow and then back to Primary) is a slow process
that can take as much as 1-2 seconds (due to the current Primary/Shadow information exchange
mechanism that only happens once a BPC). During this time, device scans or writes will be on
hold.
Configuration of Port Handover Time

Enter +PH=xx option to CPARM2 custom parameter of ECB200 driver block to modify port
handover time. This value is in seconds.
Example: CPARM2=PH=15
In absence of the +PH option in the CPARM2 custom parameter, the FDC280 uses the default
value, i.e. 10 seconds. The minimum value can be configured is 20 times of FDC280 STATION
BPC, i.e. 20*BPC. For example, if BPC = 500milliseconds, then the minimum PH value is 10.
If the user enters less than this value, the ECB200 driver will be marked to the
DCI_NOT_READY state and the FDC280 reports SMON message by stating “Min supported
value for PH option is 20 times of BPC”.
The port handover time will be set to the value which is greatest among these three values:
1. 20 times the station BPC
2. The configured port handover value in CPARM2 in the ECB200 driver block
3. Three times the maximum device scan rate under the serial port.
Logic to Set Device Status in Shadow FDC280 Module

When the Shadow FDC280 gets control of the serial port, it will test its connectivity to its devices
by sending a single heartbeat message to one of the devices under the port that the Primary
FDC280 currently reports is having good connectivity.
Shadow FDC280 will consider device(s) on the port to be equal to the Primary FDC280 when
the Shadow’s test is successful. If Shadow test does not succeed, the Shadow FDC280’s device(s)
on the port will be considered to have no connectivity; that means all these devices are considered
in the detected failed state for the Shadow FDC280.
The Shadow FDC280 will report the results of the connectivity test to the Primary FDC280 and
relinquish control of the port. The Primary module will then take back control of the port and
resume normal communications to the device(s).
Confirming Shadow Connectivity To Device When Primary Connection

Fails
If the Primary FDC280 loses all connectivity to a port (i.e., all devices configured for that port are
in the detected failed state), the Primary FDC280 will immediately relinquish control of the port
171
and request the Shadow FDC280 to test its device connectivity to determine if the detected fail-
ure is only on its side. When the Shadow FDC280 gets control of the port, it will send a heartbeat
test message to each of the configured devices on that port. When the tests are complete, the
Shadow FDC280 reports the results of the tests to the Primary FDC280 and relinquishes control
of the port.
If the test results indicate that the Shadow FDC280 has devices with good device connectivity, the
redundancy algorithm will consider the Shadow FDC280's better device connectivity on this
port. The redundancy role swap will then occur based on the user's configured redundancy algo-
rithm's rules.
If the test results indicate that the Shadow FDC280 also does not have any device connectivity,
the Primary and Shadow FDC280s will take turns controlling the port to “hunt” for connectivity
to be re-established.
The exchange of control (from Primary FDC280 to Shadow FDC280 and then back to Primary)
is a slow process that can take as much as 1-2 seconds (due to the current Primary/Shadow infor-
mation exchange mechanism that only happens once a BPC). Therefore, due to the loss of the
Primary FDC280’s serial link, the redundancy role swap will be delayed until confirming the
Shadow FDC280’s connectivity to device.
Support of Fault Tolerant FDC280 to Single-Ported Serial Device

Configuration
The Modbus serial driver allows the redundant FDC280 pair to communicate with a single-
ported Modbus slave device. To facilitate this, the FDC280 driver will:
1. Turn ON the serial port connections for the FDC280 module operating as the
Primary module, while the FDC280 module operating as the Shadow will have its
serial port connections turned OFF. This is to help ensure a single point-to-point con-
nection between the Modbus slave device and the FDC280, operating as Primary.
2. Send the Modbus read and write commands via the FDC280 running as Primary
module.
3. Perform a role-switch whenever communications become unavailable on the FDC280
running as Primary and a communication success is detected on the FDC280 running
as Shadow. In this situation, the FDC280 running as Primary will transition to
Shadow (and the Shadow will transition Primary). When this occurs, the former
Shadow module (the new Primary) will begin sending Modbus read and write com-
mands.
Single-Ported Device Interface Diagram

Figure 7-1 shows a connection diagram for interface between a fault-tolerant FDC280 and single
ported device.
172
Figure 7-1. RS-232 Single-Ported Device Connections
Figure 7-2. RS-485/422 Single-Ported Device Connections
The left and right FDC280 modules will connect their serial port to the same serial bus. For each
protocol type:
♦ RS-232 - use a straight through splitter (“Y”) cable.
♦ RS-485 - both modules will be added daisy-chained to RS-485 bus.
♦ RS-422 - daisy-chain the device's Tx lines to both FDC280 Rx terminals, and daisy-
chain the device's Rx lines to both FDC280 Tx terminals.
173
All devices under any FDC280 serial port ECBP must be either single-ported or dual-ported. It is
not recommended to mix single-ported and dual-ported devices on the same FDC280 serial port.
Single Port Configuration

The serial port can be configured to communicate single-ported devices using the SMODE
parameter of SERIAL_PORTx ECBP, where x is the port number (SMODE):
SMODE Mode of Communication

4 RS-232 Single ported
Example: SERIAL_PORT1:SMODE=4
After modifying SERIAL_PORT1 ECBP, you have to perform offline and online cycles on the
serial port ECBP to apply the changes.
The configured mode of communication (single or dual) for the serial port will be displayed in
the System Manager at the ‘Device Port Serial Mode’ parameter of ECBP equipment status of the
ECBP.
For example: Device Port Serial Mode: RS232 Single
When the FDC280 is started, all the serial port’s transceivers will be disabled. Only after the port
ECBP has been configured and enabled, the Primary FDC280 module transceiver will be
enabled.
The Shadow module serial port transceiver will be enabled only after port handover from the Pri-
mary module. This is to help ensure that if you install a Y-cable before configuration, the Primary
and Shadow modules are not overdriving the device communication line.
The Shadow module will ignore any received messages and will not send any transmissions on
port when it is configured in single ported mode.
Multiple Driver Instance Support

The FDC280 supports 32 simultaneous driver instances. Each driver instance is represented by an
ECB200 block (with its driver type specified in DRVRID parameter).
♦ For the Modbus TCP driver, set DRVRID=1.
♦ For the Modbus Serial Driver, set DRVRID=2.
Driver Instances can be of same or different driver types.
Some driver types may have their own restrictions on the maximum number of driver instances.
The sum of instances on the Ethernet and four Serial ports of the FDC280 baseplate is 32 driver
instances. Each serial port is restricted to having no more than one driver instance, and the Ether-
net port can have up to 32 driver instances.
Driver instances act independently of each other. For instance, driver operations (such as
Enable/Disable) of one driver instance will not impact other driver instances. An example usage of
the driver instance of an Ethernet driver is with grouping devices using a Modus TCP driver
instance for each group of devices.
174
Serial Ports Loopback Test

The FDC280 performs all Serial ports loopback diagnostic tests to identify internal hardware
issues. Serial loopback diagnostics will be performed at the following times.
♦ FDC280 Start-up on all serial ports.
♦ If the serial port’s ECBP is in Offline state, Not configured state, or Invalid Port Con-
figuration, the FDC280 runs a loopback test on that port periodically for every 10
minutes.
♦ Whenever communications become unavailable for all the devices, which are all
enabled, on a serial port ECBP.
If the serial ports’ loopback test during FDC280 startup is passed, a system message “Serial
Port Loopback Test PASS” for that port will be logged to SMON.
If any serial port’s loopback test does not succeed, that FDC280 module will be turned to offline
mode by displaying “Remote Serial <n> Diagnosis Failure” on the LCD display and a
system message will be logged to SMON as “Serial Port Loopback Test FAIL. Error
Code = <x>”, where ‘<n>’ is serial port number and ‘<x>’ is loopback test error code.
If any serial port ECBP is configured as “single-ported”, the port loopback test will not run for
that port in the Shadow FDC280 module. This causes a collision/disturbance of the Primary
FDC280’s communications to the device. During the startup of the Shadow FDC280, a loopback
test will also not be performed.
A loopback test will run for serial port (which is configured for single-ported serial devices) in the
Shadow FDC280 when the port is in handover to the Shadow FDC280.
175
176
8. FDC280 Security Guidelines
This chapter provides an overview of security guidelines for installing and operating the
FDC280 in the Foxboro Evo system in a manner consistent with the ISASecure® certification
for ISASecure Level 1 Devices.
The purpose of the ISASecure program is stated in the ISASecure Compliance Institute charter docu-
ment:1
“The ISA Security Compliance Institute manages the ISASecure® program which recognizes and pro-
motes cyber-secure products and practices for industrial automation suppliers and operational sites.
The ISASecure® designation is earned by industrial control suppliers for products that demonstrate
adherence to ISCI cyber security specifications derived from open, consensus industry standards. ISASe-
cure® certifications evaluate product/system cyber security characteristics, laboratory test products/sys-
tems and, assess supplier's adherence to cyber security lifecycle development best practices.”
Overview of FDC280 Security Guidelines

In order to operate the FDC280 in a manner consistent with the ISASecure specifications, it is
necessary to establish and maintain a trust boundary is as defined in Figure 8-1. The trust bound-
ary is maintained by physical plant security as well as by the other system characteristics of inter-
nal and external equipment as described below. In an ISASecure Embedded Device Security
Assurance (EDSA) compliant Foxboro Evo system, there are only two types of connections cross-
ing the system trust boundary:
♦ GPS signal from a satellite to the GPS antenna of the Foxboro Evo system
♦ An external connection allowing for RemoteWatch connectivity through a Remote-
Watch Services (RWS) Server.
Additional information about these two types of connections is available in the section “General
Security Considerations” in Security Guidelines for ISASecure Certified Products (B0700GH).
1. ISASecurity Compliance Institute. (2013). ISASecure® IACS Certification Programs. [White

paper]. Retrieved from http://isasecure.org/en-US/Documents/Articles-and-Technical-Papers/ISASecure-
IACS-CyberSecurity-Certification-August
177
B0700GQ – Rev C 8. FDC280 Security Guidelines
Figure 8-1 illustrates scope of the trust boundary for an ISASecure EDSA compliant system.
Corporate Ethernet
Network
Internet
Firewall
The Physical and Electronic Security Perimeter (trust boundary) for an ISASecure EDSA compliant
system with RWS support is this green shaded area (RWS is a standard option).
DMZ
Firewall
Plant Ethernet
GPS
Network
Antenna
RWS
Server
Firewall
Security
Enhanced electrical wiring
Workstation(s)
FECN Field Bus
Process under control

Embedded
Module(s)
Controller(s)
(analog/digital)
Valves, etc.
Serial RS-232, ...
Terminal(s) FDC280
External
Server(s) Embedded
Device(s)
Controller(s)
Valves, etc.
External
Device
Configuration
Servers Integration Ethernet Network
Note: To simplify this diagram, optional redundant FECN network hardware, connections, Embedded Controllers
and Field Bus Modules are not shown. The FDC280 supports dual Integration Ethernet Network connections.
Figure 8-1. System Trust Boundary
The portion of the above diagram shaded green represents the trust boundary for the system,
which is within the physical and electronic security perimeter of the system. The trust boundary
includes the RWS Server and Plant Ethernet Network when this optional component is present,
as shown in this diagram. You may not have an RWS Server but if you do, it is supported in this
way.
These items are required to achieve and maintain the secure trust boundary:
♦ Physical Plant Requirements
The system security perimeter is meant to mitigate the threat of outside attack by
restricting physical and electronic access to the system. Physical security of the plant
control area is the responsibility of plant management.
The plant control area consists of the control room, controller, and I/O locations
among other areas. Examples of physical security can include guarded gates to the site,
security cameras, fences, locks, badges, biometric devices, and similar or related equip-
ment. To maintain a security perimeter, the following requirements must be met:
a. Only authorized personnel are permitted within the security perimeter.
b. No wireless communication signals may be transmitted across the security perim-
eter.
c. Only a GPS signal is permitted to be received across the security perimeter.
178
8. FDC280 Security Guidelines B0700GQ – Rev C
d. The only network connection crossing the security perimeter uses a secure (SSL-
based) Virtual Private Network (VPN) to connect a RemoteWatch Services
(RWS) Server with the GCS Center. Additionally, no inbound traffic is allowed to
establish remote services on this network.
The system security perimeter is designed to mitigate the threat of outside attack by:
a. Restricting physical access to the system, so only authorized personnel are permit-
ted within the security perimeter.
b. Restricting electronic access to the system, by defining the types of signals and
connections that are permitted to cross the security perimeter and using access
controls and information classifications, so only authorized personnel have access
to data.
♦ Workstation and Server on the Foxboro Evo Control Network Requirements
The security enhanced Control Core Services v9.3 or later must be installed to meet
EDSA certification requirements. This version uses Microsoft® Active Directory for
user access management and control.
For instructions about configuration for secure operation, refer to the Control Core
Services vX.X Software Installation Guide, included in the Foxboro Evo Electronic Doc-
umentation media kit (K0174MA) that is provided with the Control Core Services
software shipped with your workstation or server.
For instructions on how to install the Control Software on platforms with the security
enhanced Control Core Services software, refer to the Foxboro Evo™ Control Software
Installation Guide (B0750RA).
♦ Plant Ethernet Network Equipment Requirements
For any equipment connected to the Plant Ethernet Network, it is the responsibility
of Plant Management to help ensure that this equipment maintains the appropriate
level of Confidentiality, Integrity, and Availability according to the function of that
equipment. Any equipment connected to the Plant Ethernet Network must meet the
requirements stated above to maintain the security perimeter.
♦ Integration Ethernet Network Requirements
The Integration Ethernet Network must meet the requirements of the security perim-
eter described above. Any equipment connected to this network is assumed to be
approved for use and to be configured to operate on this network, and is considered
an authorized device.
♦ FDC280 Requirements
The Image Version for the FDC280 must be version specified in Control Core Services
v9.3 Release Notes (B0700SV, Rev. B or later) or in a later version of these Control Core
Services vX.X Release Notes to meet ISASecure Level 1 for Devices certification require-
ments.
♦ Foxboro Evo Control Network Ethernet Switch Requirements
It is the responsibility of the user to help prevent connection of any non-Control Core
Services device to ports of the Ethernet switches in the control network. It is also the
responsibility of the user to help prevent a wireless access point to be connected to the
control network. Refer to Switch Configurator Application Software Guide for the Fox-
179
boro Evo Control Network (B0700CA), for information on controlling access to the
internet switches.
Only Extreme Networks Ethernet switches may be used in an EDSA-compliant Fox-
boro Evo system.
♦ NTP Exclusion
Under no circumstances configure an EDSA Level 1 compliant Foxboro Evo system
to use NTP as a Master Timekeeper source (i.e. sync to an off-Control Network time
source using “NTP mode”) since a connection to support this configuration will cross
the trust boundary.
General Security Considerations

Adherence to the security guidelines is required to help ensure use of the product complies with
ISASecure certification.
Operating Environment
The operating environment for the system must comply with environmental requirements of the
FDC280 product specification, Field Device Controller 280 (FDC280) (PSS 31H-2FDC280), and
must also include physical plant security sufficient to limit access to the trust boundary area so
that only authorized persons are able to enter it. It is further required that persons authorized to
work within the trust boundary be instructed in maintaining the security of the trust boundary.
(For example, persons working within the trust boundary shall not allow unauthorized persons to
enter or enable a data link to a device outside of the trust boundary.)
Basic Security Functions

Basic security functions are described below.
Data Format
The FDC280 uses COMEX, a proprietary protocol for which information is not publicly avail-
able, for transmission of data.
Active Directory
A Foxboro Evo system with the security enhancements installed employs the use of Microsoft
Active Directory for several reasons:
♦ Makes it possible to manage computer user accounts and group policies from a central
location.
♦ Provides authentication services.
♦ Is a time-tested stable technology.
Environments
The FoxView application groups users according to the tasks they perform and grants access to
system menus and features according to the needs and assumed competencies of the particular
group to which a user belongs. The collection of programs, utilities, displays and functionality
grouped according to the needs of users of a particular type constitutes an environment. Each
180
8. FDC280 Security Guidelines B0700GQ – Rev C
environment displays its own menu commands in the left panel. An environment also includes an
access password for security, as well as protection levels to disable menu options that are not avail-
able to the environment.
This security is supplemented by a group policy in Active Directory named Schneider Electric
FoxView Environments. This group policy controls access to FoxView environments based on the
logged on user account and the security groups of which the user is a member. Refer to Security
Implementation User's Guide for I/A Series and Foxboro Evo Workstations (Windows 10 or Windows
Server 2016 Operating Systems) (B0700HG) or Security Implementation User's Guide for I/A Series
and Foxboro Evo Workstations with Windows 7 or Windows Server 2008 Operating Systems
(B0700ET), for instructions on configuring FoxView environments.
Similarly, users of Foxboro Evo Control Software (the Control Software) allocate system privileges
according to user groups on the primary domain controller. Unlike FoxView, no additional login
is required once the user has logged in to the Windows operating system. Refer to Foxboro Evo™
Control Software Installation Guide (B0750RA), Security Implementation User's Guide for I/A Series
and Foxboro Evo Workstations (Windows 10 or Windows Server 2016 Operating Systems)
(B0700HG), and Security Implementation User's Guide for I/A Series and Foxboro Evo Workstations
with Windows 7 or Windows Server 2008 Operating Systems (B0700ET) for instructions on creat-
ing user accounts for the Control Software. Figure 8-2 shows user group and user profiles in
Active Directory as would be viewed when configuring user accounts.
Figure 8-2. User Profiles in Active Directory Users and Computers
181
Ethernet Switch Access

Physical port access to switches should be secured at all times. It is the responsibility of the plant
management to control physical connectivity to the switch ports and to help ensure that unused
ethernet switch ports are disabled in the switch configuration. Command Line Interface (CLI)
access is required to be secured at all times through both physical control and disabling via pass-
word-protected administrative function. Refer to Switch Configurator Application Software Guide
for the Foxboro Evo Control Network (B0700CA) for information on secure configuration of ether-
net switches.
182
9. System Management
This chapter provides general system management information for the Field Device Controller
280. It also provides references to the manuals that describe the tools you use to perform in-
depth system management tasks.
Overview
The general Foxboro Evo system management philosophy applies to the Field Device Controller
280 in the Foxboro Evo system. Through the System Manager and System Management Displays,
you can receive status information on the FDC280 and send change requests to the FDC280.
Monitoring the FDC280 is not supported in the System Management Display Handler
(SMDH).
System management for the FDC280 is supported on the following system management tools:
♦ System Manager v2.9 or later (supported on Control Core Services software v9.3 or
later) - discussed in System Manager (B0750AP)
♦ FoxView™ - discussed in FoxView Software V10.4 (B0700FC, Rev. B or later) and
Process Operations and Displays (B0700BN)
For monitoring an FDC280 with software version later than 0900010000, install MP47481162
on the workstation hosting the FDC280, System Monitor client station, and System Manager
Server v2.12 station. However, for an FDC280 with a software version 0900010000 or earlier, the
Maintenance Pack and System Manager v2.12 or later are not needed.
MP47481162 can be installed only on stations running Control Core Services v9.3-v9.4. You can
acquire MP47481162 from the GCS website:
https://pasupport.schneider-electric.com
System Manager v2.12 can be installed on stations running I/A Series software v8.8 or Control
Core Services software v9.0-v9.2.with QF1304733 and MP47481190 for monitoring the other
types of CP, including FDC280 with Ethernet and serial port support.
The security of this system is maintained via the standard Foxboro control processor software and
the customer-engineered user interface to the control block database. All access to the I/O data is
through the control blocks. The end user has no direct access to any of the I/O functions or the
data in the FDC280s.
Operating Status
The operating status of the FDC280 is reported by the Foxboro Evo system using on-screen and
printed messages. Refer to the following documents for information on the reporting of equip-
ment operating status and detected errors:
♦ System Manager (B0750AP)
♦ Control Core Service V9.x System Error Messages (B0700AF)
♦ Process Operations and Displays (B0700BN).
183
B0700GQ – Rev C 9. System Management
System Manager Displays for the FDC280

The System Manager allows you to access:
♦ Equipment information
♦ Configuration information
♦ Equipment change actions.
These displays reflect the system’s current operating status and provide a valuable maintenance aid
by allowing you to observe the current operating status of the various system elements and
intervene in system operations.
For information on using the System Manager, refer to the following sections in System Manager
(B0750AP):
♦ Identifying FDC280s and their devices in System Manager - see “Identification for
Field Device Controller 280 (FDC280)” under section “Identification of Control Sta-
tions, Control Network Interfaces (CNIs), ATSs, and LIs”
♦ Equipment Information Display for FDC280 - see “Equipment Information” under
section “Station Information for Control Processors, CNIs, and ATSs”
♦ Configuration Information Display for FDC280 - see “Equipment Status” under
section “Station Information for Control Processors, CNIs, and ATSs”
♦ Equipment Information Display for FDC280 Drivers - see “Driver Information for
FDC280 Drivers”
♦ Equipment Information Display for FDC280 Device - When a field device is
deployed as part of configuring the FDC280, the fields “Equipment Status” and
“Device Status” have the following initial values:
♦ Equipment Status: Disabled, Out of Service
♦ Device Status: DCI Not Ready, Device Disabled
When the parent driver is turned online at a later time, the status of the above fields
transitions to the state shown in Table 9-1 under various conditions.
Table 9-1. Equipment Information Display for FDC280 Field Device Statuses After Parent Driver Is
Turned Online
Equipment Status
Device State Out Of Service Device communication disabled
Not Ready Device communication enabled and parent driver or port
turned offline or configuration is not valid
Failed Device communication failed/became unavailable
On Scan Device communication is good
Communica- Enabled or disabled
tion
184
9. System Management B0700GQ – Rev C
Table 9-1. Equipment Information Display for FDC280 Field Device Statuses After Parent Driver Is
Turned Online (Continued)
Device Status
DCI Not ready Invalid group configuration or invalid device option when
length of device option is more than 32 characters.
Unresolved Invalid configuration (configuration error other than above
Connection scenario)
DCI Ready Device Configuration is good
Device Disabled Device communications disabled
Port Disabled Device communication is enabled and port is offline.
♦ Viewing Field Devices for FDC280 - see “Connected FBMs or Field Devices”
♦ Counters Information for FDC280 - see “Control Station, CNI, ATS, and LI Coun-
ters” and “Diagnostic Counters - For FCP280, FDC280, and CNI”
♦ Equipment Change Actions for FDC280 - see “Control Station or CNI Actions”
under section “Equipment Change Actions”
♦ Equipment Change Actions for FDC280 Driver - see “Device or FDC280
Driver/Device Actions”
♦ Controlling I/O Communications via FDC280 Drivers - see “Enabling and Dis-
abling Communications for Multiple Devices (FBM222, FBM228, FBM247, and
FBM248) and FDC280 Drivers”
♦ Reboot Station Procedure - see “Reboot” under section “Equipment Change Actions”
♦ Checkpoint - see “Checkpointing” under section “Equipment Change Actions”
♦ Image Update Procedure for FDC280 - see “Major and Minor Image Update” under
section “Equipment Change Actions”
♦ Primary ECBs’ information and management procedures - see section “Primary
ECB (Primary FBM) Information”
♦ Equipment Change Actions for FDC280’s Primary ECBs - see “Primary ECB
Actions” under section “Equipment Change Actions”
185
B0700GQ – Rev C 9. System Management
186
10. Process Operator Displays
This chapter provides references for information on the process operator displays used with the
Foxboro Evo system (and thus with the FDC280).
The Foxboro Evo system provides the types of Block Detail displays shown in this chapter for per-
formance of process control operations:
For information on how these displays are used, refer to Control HMI Application User's Guide
(B0750AQ) and System Manager (B0750AP).
Block Detail Displays

The following Equipment Control Blocks (ECB200 and ECB201) relate to the FDC280 and its
associated field devices as follows:
♦ ECB200 represents the FDC280 Ethernet driver communications to the field devices
♦ ECB201 represents each field device attached to the FDC280.
The block detail displays for these ECBs are described in the following subsections. To access the
block detail displays, use the appropriate application select the appropriate compound and then
select the ECB200 or ECB201, view the Information Pane as described in Control HMI Applica-
tion User's Guide (B0750AQ).
When modifying an ECB201 configuration with changes that are related to DCI connections (for
example, when changing a device address), you are advised not to wait for the Control Editors to
report any detected error(s) associated with that change. Rather, you should monitor the ECB201
block detailed display while modifying the ECB201 configuration. This helps ensure that all pos-
sible detected errors are detected (and resolved) before commencement of process control opera-
tions.
187
B0700GQ – Rev C 10. Process Operator Displays
FDC280 Station Block Detail Display

Figure 10-1 shows an example of the FDC280 Station block detail display in the Control HMI.
Figure 10-1. FDC280 Station Block Detail Display
Table 10-1 provides descriptions of the fields shown in this detail display.
Table 10-1. FDC280 Station Block Detail Display Field Descriptions
Field Description
TIME Station internal clock time
INACTIVE or Toggles the status between ACTIVE and INACTIVE. Selecting the box
ACTIVE enables or disables station performance data collection and station load-
ing updates.
STABPC Station Basic Processing Cycle represents the station’s BPC in seconds
MAXMEM Maximum Memory provides an indication of memory fragmentation in
the CP and shows the largest continuous area of memory available to
applications. It is detailed in Integrated Control Block Descriptions
(B0193AX).
VERSNO Software Version Number is the number of the installed Foxboro Evo
software
TOTMEM Total Memory indicates the number of bytes of dynamic free memory
available for the control database. The station updates this value a mini-
mum of every thirty seconds.
188
10. Process Operator Displays B0700GQ – Rev C
Table 10-1. FDC280 Station Block Detail Display Field Descriptions (Continued)
Field Description
VERSN2 Software Version Number 2 indicates the version number of FDC280’s
Core 2 control software.
TOTM2 Total Memory 2 indicates the number of free memory bytes available in
an FDC280’s Core 2 for the driver configuration and operation.
PEER TO PEER
STATUS
TOTAL The current number of peer-to-peer control block input connections
configured in the control database. It is detailed in Integrated Control
Block Descriptions (B0193AX).
DSCNTD The current number of peer-to-peer connections that have been discon-
nected due to a loss of peer-to-peer communications with the source sta-
tion. It is detailed in Integrated Control Block Descriptions (B0193AX).
DELETED The current number of peer-to-peer connections whose source blocks or
compounds have been deleted. It is detailed in Integrated Control Block
Descriptions (B0193AX).
NOTFND The current number of peer-to-peer connections that have never been
located on the system. It is detailed in Integrated Control Block Descrip-
tions (B0193AX).
AUTCKP Automatic Checkpoint specifies the period of automatic checkpoints in
increments of 30 minutes. It is detailed in Integrated Control Block
The FDC280 Station block detail display shows the OM 200 msec FAST-SCAN UPDATES
option. However, this option remains grey colored or unchecked because it does not apply to the
FDC280.
More details on the actions available from this detail display, such as the faceplate navigation but-
tons, are available in the section “Faceplate Overlays” in Control HMI Application User's Guide
(B0750AQ).
189
FDC280 Station Compound Block Detail Display

Figure 10-2 shows an example of the FDC280 Station Compound block detail display in the
Control HMI.
Figure 10-2. FDC280 Compound Block Detail Display
Table 10-2. FDC280 Compound Block Detail Display Field Descriptions
Field Description
ON or Indicates if the compound is ON or OFF.
OFF
CINHIB Compound Inhibit specifies the priority levels of alarm inhibit within
the compound, detailed in Integrated Control Block Descriptions
(B0193AX).
INITON Initialize On/Off specifies the state the compound assumes on initializa-
tion, detailed in Integrated Control Block Descriptions (B0193AX).
UNACK Indicates whether or not you want to propagate alarm acknowledge
actions to all blocks in a compound.
ALMLEV Alarm Level specifies the highest priority of all active alarms within the
compound.
SSTATE Sequential State represents the collective operational state of all sequen-
tial control blocks in the compound, detailed in Integrated Control Block
190
More details on the actions available from this detail display, such as the faceplate navigation but-
tons, are available in the section “Faceplate Overlays” in Control HMI Application User's Guide
(B0750AQ).
FDC280 Ethernet Port Primary ECB Detail Display

Figure 10-3 shows an example of the Primary ECB detail display for the FDC280 Ethernet port
in the Control HMI.
Figure 10-3. FDC280 Ethernet Port Primary ECB Detail Display
Table 10-3. FDC280 Ethernet Port Primary ECB Detail Display Field Descriptions
Field Description
Device Identifier Device identifier for this Ethernet port.
ECB Status:
ECB ON or The Primary ECB’s compound is either ON or OFF.
ECB OFF
DEV READY or The FDC280 is either ready or not ready to exchange data with the
DEV NOT READY attached devices.
ON SCAN or The Primary ECB is either in on-scan or off-scan mode.
OFF SCAN
DEV FAIL Some portion of the FDC280’s hardware has become unavailable.
DEV SHUTDWN The FDC280 is not operating.
191
Table 10-3. FDC280 Ethernet Port Primary ECB Detail Display Field Descriptions (Continued)
Field Description
COMM FAIL There is a problem with communications to/from the FDC280.
UNDEF The Primary ECB has an unresolved configuration problem.
OPSTAT The current value of the Module Operational Status parameter, detailed
in Integrated Control Block Descriptions (B0193AX).
More details on the actions available from this detail display are available in the section
“Faceplate Overlays” in Control HMI Application User's Guide (B0750AQ).
FDC280 Serial Port Primary ECB Detail Display

Figure 10-4 and Figure 10-5 show examples of the Primary ECB detail display for the FDC280
Serial port in the Control HMI.
Figure 10-4. FDC280 Serial Port Primary ECB Detail Display - Part 1
192
Figure 10-5. FDC280 Serial Port Primary ECB Detail Display - Part 2
Table 10-4. FDC280 Serial Port Primary ECB Detail Display Field Descriptions
Field Description
Device Identifier Device identifier for this Serial port.
ECB Status:
ECB ON or The Primary ECB’s compound is either ON or OFF.
ECB OFF
DEV READY or The FDC280 is either ready or not ready to exchange data with the
DEV NOT READY attached devices.
ON SCAN or The Primary ECB is either in on-scan or off-scan mode.
OFF SCAN
DEV FAIL Some portion of the FDC280’s hardware has become unavailable.
COMM FAIL There is a problem with communications to/from the FDC280.
UNDEF The Primary ECB has an unresolved configuration problem.
193
FDC280 Driver ECB200 Detail Display

Figure 10-6 through Figure 10-8 show examples of the FDC280 Driver (ECB200) detail display
in the Control HMI.
Figure 10-6. ECB200 (FDC280 Driver) Block Detail Display - First Page
Figure 10-7. ECB200 (FDC280 Driver) Block Detail Display - Second Page
194
Figure 10-8. ECB200 (FDC280 Driver) Block Detail Display - Third Page
Table 10-5. FDC280 Driver ECB200 Detail Display Field Descriptions
Field Description
Software Type Software type. For the ECB200, this is 200.
Hardware Type Hardware type. For the FDC280, this is 1.
Device Identifier Device identifier for this block.
ECB STATUS:
ECB ON or The ECB200 is either ON or OFF.
ECB OFF
DEV READY or The ECB is either ready or not ready for operation.
DEV NOT READY
ON SCAN or The ECB has been placed on/off control block processing scan.
OFF SCAN
UNDEF The ECB200 has a detected issue caused by an unresolved configuration
condition.
COMM FAIL Communication failure detected due to Core 2 not providing updates for
driver.
DRV STATUS: The driver configuration is ready/not ready for operation.
DCI READY or
NOT READY
ON LINE or The FDC280 is online or offline.
OFF LINE
195
Table 10-5. FDC280 Driver ECB200 Detail Display Field Descriptions (Continued)
Field Description
ECB200 (FDC280 for Ethernet) Primary Data

The ECB200 primary data consists of ECB200 parameters, which are described in Integrated
Control Block Descriptions (B0193AX).
FDC280 Field Device ECB201 Detail Display

Figure 10-9 through Figure 10-11 shows an example of the field device (ECB201) detail display
in the Control HMI.
Figure 10-9. ECB201 (Field Device) Block Detail Display - First Page
196
Figure 10-10. ECB201 (Field Device) Block Detail Display - Second Page
Figure 10-11. ECB201 (Field Device) Block Detail Display - Third Page
When a device is deployed as part of configuring the FDC280, the fields ECBSTA and DEVSTS
in the ECB201 detail display have following initial values:
♦ ECBSTA: ECB OFF, DVC Ready, Off Scan
♦ DEVSTS: Not Ready, DVC Disabled
197
When the parent driver is turned online at a later time, the ECBSTA and DEVSTS fields transi-
tions to the states shown in Table 10-6 under various conditions.
Table 10-6. FDC280 Field Device ECB201 Detail Display Field Descriptions
Field Description
Device Identifier Device identifier for this block.
Software Type Software Type.
Hardware Type Hardware Type.
ECB STATUS:
ECB ON or The ECB201 is either ON or OFF, depending on the action from the
ECB OFF System Manager setting device communication to be enabled or
disabled.
NOT READY or The FDC280 is either ready or not ready to exchange data with the
READY attached devices.
UNDEF The ECB201 has an unresolved configuration problem. For details, refer
to the smon_log messages and detected error messages on the default
display (field ACHNGE).
ON SCAN or The ECB has been placed on/off control block processing scan. The sta-
OFF SCAN tus goes to “ON SCAN” when both the parent port and parent driver are
online.
DVC FAIL Device ECB is reporting a detected failure.
COMM FAIL Communication failure detected due to Core 2 not providing updates for
device.
DVC STATUS:
DCI READY or The field device configuration is ready/not ready for operation. “NOT
NOT READY READY” indicates an invalid group configuration or an invalid device
option when the length of device options exceeds 32 characters. For
details, refer to the smon_log messages.
DEV DISABLD or Device communication is enabled or disabled.
DEV ENABLD
DEV FAILED “DEV FAILED” is set either when there is no physical connection to
device or there is a connection but communications are not successful.
UNRESOLVED Shown when there is an unresolved connection to the field device. This
indicates configuration issues. For details, refer to the smon_log messages
and detected error messages on the default display (field ACHNGE).
198
ECB201 (Field Device) Primary Data

The ECB201 primary data consists of ECB201 parameters, which are described in Integrated
Control Block Descriptions (B0193AX).
199
200
11. Maintenance and Control
Software Equipment Information
This chapter provides maintenance information for the FDC280 when used with field devices
over Ethernet or serial with Modbus drivers.
NOTE
In general, maintenance consists of the actions taken to make the system opera-
tional and keep it functional. Maintenance actions include reviewing the system
logs, HMI displays, LCD display messages and LED indicators.
DANGER
HAZARD OF ELECTRIC SHOCK, EXPLOSION, OR ARC FLASH
To prevent explosion, install and remove cables, wiring, modules and

other replaceable components only when the area is known to be
nonhazardous.
Failure to follow these instructions will result in death or serious

injury.
Overview
The general Foxboro Evo system management philosophy applies to the FDC280 incorporated
into the Foxboro Evo system. Through the System Management Displays, you can receive status
information on the FDC280, as well as send change requests to the FDC280.
System management for the FDC280 is supported on the following system and display manage-
ment packages:
♦ System Manager - discussed in System Manager (B0750AP)
♦ FoxView - discussed in Process Operations and Displays (B0700BN)
♦ Foxboro Evo Control HMI - discussed in Control HMI Application User's Guide
(B0750AQ).
System Management Displays

Operators will view data regarding their control equipment using display applications such as the
System Manager.
The System Manager allows you to access equipment information and status for a Foxboro Evo
system, including the FDC280 and their field devices. This display reflects the system’s current
201
B0700GQ – Rev C 11. Maintenance and Control Software Equipment Information
operating status and provide a valuable maintenance aid by allowing you to observe the current
operating status of the various system elements and intervene in system operations. For informa-
tion on navigating through the System Manager screens, see System Manager (B0750AP).
For information on viewing the FDC280 and device runtime information in the Control HMI,
refer to Control HMI Application User's Guide (B0750AQ).
With regard to the FDC280 and associated devices, the System Manager provides the following
displays:
♦ A device level display (I/O Display), which shows the associated field devices for the
selected FDC280
♦ Detailed equipment information and equipment change actions for each FDC280,
FDC280 driver, Ethernet port, serial port, and the associated field devices.
For detailed information on the I/O device display, refer to System Manager (B0750AP).
FDC280 Equipment Status and Information Display

Table 11-1 describes the available Equipment Information fields provided for FDC280 in the
order that they appear on the System Manager display pages.
Figure 11-1. FDC280 System Manager Display
202
11. Maintenance and Control Software Equipment Information B0700GQ – Rev C
Table 11-1. FDC280 Equipment Status and Information Display Fields
Field Description
Name User-supplied FDC280 name.
Type For the FDC280, set to “Field Device Controller 280”.
SMON Name of the System Monitor application to which the FDC280 is con-
nected
Boot Host Name of the host workstation for this FDC280
SMON Host Name of the workstation that hosts the System Monitor application to
which the FDC280 is connected
Self-Hosting Enabled/Not Enabled - Indicates whether or not self-hosting is enabled
for this FDC280
IP Address The IP address for this FDC280 on the Foxboro Evo Control Network
Fault Tolerant Yes/No - Indicates whether or not fault tolerant operation is enabled for
this FDC280
Switch Connections The number of connections to switches on the control network.
Fault Tolerant State Primary/Shadow/No Information - Primary or Shadow for fault-toler-
ant FDC280s, or No Information for non-fault-tolerant FDC280s
Run Mode On-line or Off-line (default) is displayed. Set the Run Mode using the
GO ON-LINE and GO OFF-LINE options from the right-click menu of
the FDC280 in the System Manager.
Alarm Enabled State Indicates whether alarming is Enabled or Inhibited for the FDC280.
♦ To inhibit alarming, right-click the FDC280 name in the Naviga-
tion pane and choose Inhibit Alarming from the context menu.
♦ To enable alarming, right-click the FDC280 name in the Naviga-
tion pane and choose Enable Alarming from the context menu.
Failed State Failed/Not Failed. This field changes to Failed if a serious hardware
condition is detected (including a possible communications cable
break) causes the FDC280 to become unavailable.
Failed Devices Attached Yes/No. Indicates if any of the field devices connected to the FDC280
have become unavailable.
Failed Acknowledged Acknowledged (default) or Not Acknowledged is displayed. If the
State Failed State value changes from Not Failed to Failed, the Failed
Acknowledged State value changes to Not Acknowledged to indicate
this transition, and remains until the FDC280 unavailability is
acknowledged by the user.
Failed Devices Acknowl- Acknowledged (default) or Not Acknowledged is displayed. If any of
edged the devices attached to the FDC280 stop working and become unac-
knowledged, Not Acknowledged is displayed.
Image Update State Indicates whether or not the FDC280 is having its image (OS) updated
at the present time.
Diagnostics State Active/Not Active. Indicates whether or not the FDC280 is running
self-diagnostics.
203
Table 11-1. FDC280 Equipment Status and Information Display Fields (Continued)
Field Description
Download State Indicates whether or not the FDC280 is rebooting.
Reporting State Indicates whether the station is reporting its status to its system moni-
tor; values can be:
♦ Reporting All
♦ No Reporting
♦ No Counters
♦ No Information
Master Timekeeper The Timekeeper’s time source may be a GPS signal provided by a sta-
Reporting tion on the Foxboro Evo Control Network or a source located off of the
control network.
NTP is enabled when the Master Timekeeper needs to be synchronized
to a time source located on a station which is located off of the control
network.
Refer to System Manager (B0750AP) for additional details.
Station Address A six-octet media access control (MAC) address assigned during system
definition and used by the networking protocol in the Foxboro stations
Cable State Status of cable connections between the workstation and the switch:
♦ Both Cables Okay
♦ Fault
♦ No Information
Primary Mode If the FDC280 is married to another fault-tolerant FDC280, indicates
its status:
♦ Single Primary when the FDC280 is a non-redundant station and
it is on-line.
♦ Married Primary for the primary module in a redundant pair that
is operating normally
♦ Image Updating when the primary module software image is
being updated
♦ Off Line
♦ Downloading when the control database is being downloaded to
the primary module
♦ Failed
♦ No Information
Primary ROM Address A six-octet MAC address of the Primary FDC280 assigned during man-
ufacturing. The last six characters of this address are the module hard-
ware ID which is stamped on a label on the module’s outer cover.
Primary Hardware Part Part number for a non-fault-tolerant FDC280 or for the Primary mod-
Number ule in a fault-tolerant pair
Primary Hardware Revi- Revision level of the hardware for a non-fault-tolerant FDC280 or of
sion the Primary module hardware in a fault-tolerant pair
Primary Hardware Date Manufacturing date of the hardware for a non-fault-tolerant FDC280
or of the Primary module hardware in a fault-tolerant pair
204
Table 11-1. FDC280 Equipment Status and Information Display Fields (Continued)
Field Description
Primary Image Revision Revision number for the operating software image in a non-fault-toler-
ant FDC280 or in the Primary module hardware in a fault-tolerant pair
Primary Remote Image Revision number for the image running of the FDC280’s Core 2.
Revision
Shadow parameters are only shown for fault-tolerant FDC280s.
Shadow Mode ♦ Married Shadow for the shadow module in a redundant pair that
is operating normally
♦ Image Updating when the software for a shadow station in a
redundant pair is being updated
♦ Downloading when the control database is being downloaded to
the shadow station
♦ Diags Active when the station is performing Offline Diagnostics
♦ Off Line
♦ Failed
♦ No Information
Shadow ROM Address A six-octet MAC address of the Shadow CP/CNI/ATS assigned during
manufacturing. The last six characters of this address are the module
hardware ID which is stamped on a label on the module’s outer cover.
Shadow Hardware Part Part number for the Shadow module.
Number
Shadow Hardware Revi- Revision level of the Shadow module hardware.
sion
Shadow Hardware Date Manufacturing date of the Shadow module hardware.
Shadow Image Revision Revision number for the operating software image in the Shadow mod-
ule hardware.
205
FDC280 Equipment Change Actions

The equipment change actions for the FDC280 are shown in Figure 11-2. Table 11-2 describes
the available text fields in the order that they appear in the System Manager.
Figure 11-2. FDC280 Equipment Change Actions
Table 11-2. FDC280 Ethernet Port Equipment Change Actions
Action Description
Acknowledge Station Acknowledges any alarms currently occurring for the FDC280.
Inhibit Alarming Inhibits FDC280 alarms from propagating upward in the Foxboro Evo
system.
Enable Alarming Enables FDC280 alarms to propagate upward in the Foxboro Evo sys-
tem.
Disable All Reports Disables all internal reporting of all status information from the
FDC280.
Enable All Reports Enabling all reports permits the internal reporting of all status informa-
tion for the FDC280 and any attached field devices, as well as reporting
of system and peripheral counters to the System Monitor. When report-
ing is enabled, all displays are updated with the current status of the
FDC280 and its field devices, and any equipment unavailability can be
acknowledged.
Checkpoint Refer to “Checkpointing” in System Manager (B0750AP).
Major Image Update/ Refer to the appendix “Major Image Update and Minor Image Update”
Minor Image Update in Field Device Controller 280 (FDC280) User's Guide (B0700GQ).
The checkpoint file in flash is invalidated forcing the checkpoint file to
be loaded from the host workstation. Only after the appropriate Image
Update operation is complete will the checkpoint file be copied to flash.
Be aware that the Major Image Update will have a major effect on your
system process.
Reboot Reboot the FDC280.
206
Table 11-2. FDC280 Ethernet Port Equipment Change Actions (Continued)
Action Description
Disable Download Disables downloads from the host workstation to the FDC280. Helps
prevent rebooting or updating the FDC280 image.
Enable Download Enables downloads from the host workstation to the FDC280. In order
to reboot an FDC280 or to update the FDC280 image, you must enable
downloading.
Offline Diagnostics Sets FDC280 into the off-line diagnostics state, which puts it off-line
FDC280 Ethernet Port Equipment Status and

Information Display
Typical Equipment Status and Information display pages for the FDC280’s Ethernet port are
shown in Figure 11-3 and Figure 11-4. Table 11-3 describes the available text fields in the order
that they appear in the System Manager.
Figure 11-3. Fault-Tolerant FDC280’s Ethernet Port Equipment Information Display – Typical
Figure 11-4. Non-Fault-Tolerant FDC280’s Ethernet Port Equipment Information Display – Typical
207
Table 11-3. FDC280 Ethernet Port Equipment Status and Information Display Fields
Field Description
Name Name of the FDC280 Ethernet port.
Type For the FDC280 Ethernet port, displays “Ethernet port”
Alarm Enabled State Indicates whether alarming is Enabled or Inhibited for the FDC280
field devices over the “A” or “B” buses.
♦ To inhibit alarming, right-click the FDC280 Ethernet port in the
Navigation pane and choose Inhibit Left Port (A) Alarming or
Inhibit Right Port (B) Alarming from the context menu.
♦ To enable alarming, right-click the FDC280 Ethernet port in the
Navigation pane and choose Enable Left Port (A) Alarming or
Enable Right Port (B) Alarming from the context menu.
Failed Acknowledged Acknowledged or Not Acknowledged. The field changes to Not
State Acknowledged when Failed State changes from Not Failed to Failed.
♦ Right-click the peripheral name in the Navigation pane and
choose Acknowledge Device from the context menu to acknowl-
edge the unavailable peripheral.
Devices Attached Yes/No. Indicates if any field devices are communicating with the
FDC280 via this FDC280 Ethernet port.
FDC Power 1 Status of the FDC280’s primary power cable is either OK or Failed
Failed Devices Attached Yes, if a field device attached to the FDC280 Ethernet port is reported
as unavailable; otherwise, No. To determine which field devices are
unavailable, click the Connections tab to list the type, current status,
run mode and unavailability mode of each field device.
FDC Power 2 Status of the FDC280’s secondary power cable is either OK or Failed
Failed Devices Yes or No. This field is initially set to Yes. If a field device stops work-
Acknowledged ing, the field is set to No until the system alarm from the field device is
acknowledged.
Right-click the field device in the Navigation pane and choose
Acknowledge Device from the context menu to acknowledge the
unavailable device.
The following fields appear for fault-tolerant FDC280’s only.
Primary Position Left/Right. Indicates which of the two fault-tolerant FDC280s is cur-
rently the Primary module (the one installed in the left or right position
in the FDC280 baseplate).
Device Port Configura- Valid or Not Valid. Indicates the validity of the port.
tion
Left Device Port Link Indicates the status of the Left FDC280 Ethernet port, which runs
Status communications from the FDC280 installed in the left position in the
FDC280 baseplate.
208
Table 11-3. FDC280 Ethernet Port Equipment Status and Information Display Fields (Continued)
Field Description
Right Device Port Link Indicates the status of the Right FDC280 Ethernet port, which runs
Status communications from the FDC280 installed in the right position in
Left Device Port Link Indicates the speed over which the Left FDC280 Ethernet port is com-
Speed municating to the switches on the I/O customer-supplied dedicated
network. This Ethernet port runs communications from the FDC280
installed in the left position in the FDC280 baseplate.
Right Device Port Link Indicates the speed over which the Right FDC280 Ethernet port is
Speed communicating to the switches on the I/O customer-supplied dedi-
cated network. This Ethernet port runs communications from the
FDC280 installed in the right position in the FDC280 baseplate.
Left Device Port IP The IP address of the Left FDC280 Ethernet port on the I/O cus-
Address tomer-supplied dedicated network. This Ethernet port runs communi-
cations from the FDC280 installed in the left position in the FDC280
baseplate.
Right Device Port IP The IP address of the Right FDC280 Ethernet port on the I/O cus-
Address tomer-supplied dedicated network. This Ethernet port runs communi-
cations from the FDC280 installed in the right position in the
FDC280 baseplate.
The following fields appear for non-fault-tolerant FDC280’s only.
Module Position Left/Right. Indicates the position in which the FDC280 is installed in
Device Port Link Speed Indicates the speed over which this FDC280 Ethernet port is commu-
nicating to the switches on the I/O customer-supplied network.
tion
Device Port IP Address The IP address of the FDC280 Ethernet port on the I/O customer-sup-
plied dedicated network.
Device Port Link Status Indicates the status of the FDC280 Ethernet port.
209
FDC280 Ethernet Port Equipment Change Actions

The equipment change actions for the FDC280 Ethernet port are shown in Figure 11-5.
Table 11-4 describes the available text fields in the order that they appear in the System Manager.
Figure 11-5. FDC280 Ethernet Port Equipment Change Actions
Table 11-4. FDC280 Ethernet Port Equipment Change Actions
Action Description
Inhibit Device Alarming Inhibits device alarms from the FDC280 Ethernet port
Enable Device Alarming Enables device alarms from the FDC280 Ethernet port
Go On-line Connects the field devices to the FDC280, thus enabling communica-
tion.
This also returns the related ECB200 and ECB201s back to an earlier
state before going on-line when device communication is restored.
Go Off-line Disconnects the field devices from the FDC280, thus disabling commu-
nication.
This also puts ECB200 and related ECB201s into Out of Service (OOS)
state with no communication to the field devices, and the FDC280’s
Ethernet port is completely shut off for incoming packets as well.
Inhibit Left Port (A) For fault-tolerant FDC280s, inhibit Ethernet port link alarms for the
Alarms FDC280 installed on the left-most slot on the FDC280 baseplate
Enable Left Port (A) For fault-tolerant FDC280s, enable Ethernet port link alarms for the
Alarms FDC280 installed on the left-most slot on the FDC280 baseplate
Inhibit Right Port (B) For fault-tolerant FDC280s, inhibit Ethernet port link alarms for the
Alarms FDC280 installed on the right-most slot on the FDC280 baseplate
Enable Right Port (B) For fault-tolerant FDC280s, enable Ethernet port link alarms for the
Alarms FDC280 installed on the right-most slot on the FDC280 baseplate
210
FDC280 Driver for Ethernet and Serial (ECB200)

Equipment Status and Information Display
Typical Equipment Status and Information display pages for the FDC280 driver’s Ethernet or
serial Equipment Control Block (ECB200) are shown in Figure 11-6 and Figure 11-7. Table 11-5
describes the available text fields in the order that they appear in the System Manager.
Figure 11-6. FDC280 Driver for Ethernet (ECB200) Equipment Information Display – Typical
211
Figure 11-7. FDC280 Driver for Serial (ECB200) Equipment Information Display – Typical
Table 11-5. FDC280 Driver for Ethernet or Serial (ECB200) Equipment Status and Information
Display Fields
Field Description
Name Name of the ECB200.
Type For the FDC280 driver, displays “Protocol Driver”
the FDC280 driver in the System Manager.
field devices.
♦ To inhibit alarming, right-click the FDC280 driver in the Naviga-
tion pane and choose Inhibit Device Alarming from the context
menu.
♦ To enable alarming, right-click the FDC280 driver in the Naviga-
tion pane and choose Enable Device Alarming from the context
menu.
Device State Failed/Not Failed. This field changes to Failed if a detected hardware
fault (including a possible communications cable break) causes the
FDC280 to become unavailable.
212
Table 11-5. FDC280 Driver for Ethernet or Serial (ECB200) Equipment Status and Information
Display Fields (Continued)
Field Description
FDC280 via this FDC280 driver.
Failed Devices Attached Yes, if a field device attached to the FDC280 is reported as unavailable;
otherwise, No. To determine which field devices are unavailable, click
the Connections tab to list the type, current status, run mode and
unavailability mode of each field device.
Warning Conditions Yes/No. Indicates if any detected warning condition exists on the
Exist FDC280.
Acknowledged ing, the field is set to No until the system alarm from the field device is
acknowledged.
unavailable device.
Driver Mismatch Yes/No. Yes indicates the image revision for Primary and Shadow
FDC280s is different.
Compound Name Compound name containing the FDC280 driver’s ECB200.
Block Name Name of the ECB200.
Hardware Type For the FDC280 driver, this is set to “1”.
Port Ethernet/Serial. Type of port for the FDC280 driver.
Software Type ECB type. For the ECB200, this is set to “200”.
Driver Type of FDC280 driver.
Driver Status Current status for the FDC280 driver.
213
FDC280 Driver Equipment Change Actions

The equipment change actions for the FDC280 driver are shown in Figure 11-2. Table 11-6
describes the available text fields in the order that they appear in the System Manager.
Figure 11-8. FDC280 Driver Equipment Change Actions
Table 11-6. FDC280 Driver (ECB200) Equipment Change Actions
Action Description
Inhibit Device Alarming Inhibits device alarms from the FDC280 driver
Enable Device Alarming Enables device alarms from the FDC280 driver
Go On-line Connects the field devices to the FDC280 driver, thus enabling commu-
nication.
Go on-line after going off-line reestablishes device communications, but
it will take longer to complete the connect than selecting Go On-line
from the Ethernet port.
Go Off-line Disconnects the field devices from the FDC280 driver, thus disabling
communication.
state with no communication to the field devices.
Enable/Disable Com- Enable or disable communications to/from the field devices to which this
munication driver is attached
Enable/Disable Multi- Submenu of “Enable/Disable Communication”. Enable or disable com-
ple Devices munications to/from the field devices to which this driver is attached
214
FDC280 Serial Port Equipment Status and

Information Display
Typical Equipment Status and Information display pages for the FDC280’s serial port are shown
in Figure 11-9 and Figure 11-10. Table 11-7 describes the available text fields in the order that
they appear in the System Manager.
Figure 11-9. Fault-Tolerant FDC280’s Serial Port Equipment Information Display – Typical
Figure 11-10. Non-Fault-Tolerant FDC280’s Serial Port Equipment Information Display – Typical
Table 11-7. FDC280 Serial Port Equipment Status and Information Display Fields
Field Description
Name Name of the FDC280 serial port.
Type For the FDC280 serial port, displays “Serial port”
215
Table 11-7. FDC280 Serial Port Equipment Status and Information Display Fields (Continued)
Field Description
field devices over the “A” or “B” buses.
♦ To inhibit alarming, right-click the FDC280 Ethernet port in the
Navigation pane and choose Inhibit Left Port (A) Alarming or
Inhibit Right Port (B) Alarming from the context menu.
♦ To enable alarming, right-click the FDC280 Ethernet port in the
Navigation pane and choose Enable Left Port (A) Alarming or
Enable Right Port (B) Alarming from the context menu.
FDC280 via this FDC280 Ethernet port.
FDC Power 1 Status of the FDC280’s primary power cable is either OK or Failed
Failed Devices Attached Yes, if a field device attached to the FDC280 serial port is reported as
unavailable; otherwise, No. To determine which field devices are
unavailable, click the Connections tab to list the type, current status,
run mode and unavailability mode of each field device.
FDC Power 2 Status of the FDC280’s secondary power cable is either OK or Failed
Acknowledged ing, the field is set to “No” until the system alarm from the field device
is acknowledged.
unavailable device.
The following fields appear for fault-tolerant FDC280’s only.
Primary Position Left/Right. Indicates which of the two fault-tolerant FDC280s is cur-
rently the Primary module (the one installed in the left or right position
in the FDC280 baseplate).
Left Device Port Link Connected or Disconnected. Indicates the status of the Left FDC280
Status serial port, which runs communications from the FDC280 installed in
the left position in the FDC280 baseplate.
Right Device Port Link Connected or Disconnected. Indicates the status of the Right FDC280
Status serial port, which runs communications from the FDC280 installed in
the right position in the FDC280 baseplate.
The following fields appear for non-fault-tolerant FDC280s only.
Module Position Left/Right. Indicates the position in which the FDC280 is installed in
216
Table 11-7. FDC280 Serial Port Equipment Status and Information Display Fields (Continued)
Field Description
The remaining fields appear for both non-fault-tolerant and fault-tolerant FDC280s.
tion
Device Port Serial Mode Indicates the current mode:
Disable
RS232_Auto
RS422 Dual
RS485 Dual
RS232 Single
RS422 Single
RS485 Single
Device Port Stop Bits Indicates the serial port stop bit:
1 bit
1.5 bit
2 Bit
Unknown
Device Port Baud Rate Indicates the serial baud rate for communications:
300
600
1200
2400
4800
9600
19200
38400
57600
115200
Device Port Data Bits Indicates the bit rate for serial port communications:
5 Bit
6 Bit
7 Bit
8 Bit
Unknown
Device Port Parity Indicates the serial port parity:
Odd
Even
Unknown
217
FDC280 Serial Port Equipment Change Actions

The equipment change actions for the FDC280 Ethernet port are shown in Figure 11-11.
Table 11-8 describes the available text fields in the order that they appear in the System Manager.
Figure 11-11. FDC280 Serial Port Equipment Change Actions
Table 11-8. FDC280 Serial Port Equipment Change Actions
Action Description
Acknowledge Device Acknowledges alarms deriving from the serial port
Inhibit Device Alarming Inhibits device alarms from the FDC280 serial port
Enable Device Alarming Enables device alarms from the FDC280 serial port
Go On-line Connects the field devices to the FDC280, thus enabling communica-
tion.
Go Off-line Disconnects the field devices from the FDC280, thus disabling commu-
nication.
state with no communication to the field devices, and the FDC280’s
Ethernet port is completely shut off for incoming packets as well.
218
Device Equipment Status and Information Display

(Field Device - ECB201)
Typical equipment status and information display pages for FDC280 field devices are shown in
Figure 11-12. The display (ECB201) is similar for each device connected to the FDC280’s Ether-
net port. Table 11-9 describes the available text fields in the order that they appear in the System
Manager.
Figure 11-12. Device Equipment Information Display (ECB201) / FDC280 Field Device (FDC_Device)
– Typical
Table 11-9. Device Equipment Information Display Fields (Field Devices - ECB201)
Field Description
Name The identifier assigned to this field device during system hardware def-
inition
Type Type of hardware specified when the identifier was defined. For the
ECB201, displays “Field Device”
Communications Indicates the state (Enabled or Disabled) of communications to/from a
field device.
219
Table 11-9. Device Equipment Information Display Fields (Field Devices - ECB201) (Continued)
Field Description
Alarm Enabled State Indicates whether alarming is Enabled or Inhibited for the field device.
♦ To inhibit alarming, right-click the field device name in the Navi-
gation pane and choose Inhibit Device Alarming from the con-
text menu.
♦ To enable alarming, right-click the field device name in the Navi-
gation pane and choose Enable Device Alarming from the con-
text menu.
When alarming is inhibited for a device, the system monitor still
updates its status, but alarm messages are not displayed in System Man-
ager, and are not logged to the printer or the historian.
Device State Failed or Not Failed (default) is displayed. This field changes to Failed
if a detected device hardware fault (including a possible communica-
tions cable break) causes the device to become unavailable.
Warning Conditions Yes/No. Indicates if any warning condition is detected on the field
Exist device.
Failed Acknowledged Acknowledged (default) or Not Acknowledged is displayed. If the
State Device State value changes from Not Failed to Failed, the Failed
Acknowledged State value changes to Not Acknowledged to indicate
this transition, and remains until the device unavailability is acknowl-
edged by you.
Compound Name Compound name containing the ECB201.
Block Name The ECB201 name.
Hardware Type For the field device, this is set to “1”.
Device Name Device Name of the device configured in associated ECB201 (typically
IP address of device)
Software Type ECB type. For the ECB201, this is set to “201”.
Device Protocol Type of protocol used to communicate with this field device (Modbus
TCP or Serial for Modbus devices)
Port Ethernet/Serial. Type of FDC280 port used to communicate with this
field device.
Device Options Current options set for the field device.
Device Status Device status messages (may have multiple lines)
Device Diagnostic Sta- Device Diagnostic status messages
tus
Device Equipment Change Actions

The equipment change actions for the field device are shown in Figure 11-13. The actions is sim-
ilar for each field device connected to the FDC280’s Ethernet port. The actions that are active for
this field device are described in Table 11-10.
220
Figure 11-13. Device Equipment Change Display
Table 11-10. Device ECB201 Equipment Change Actions
Action Description
Inhibit Device Alarming Inhibits device alarms from the field device ECB
Enable Device Alarming Enables device alarms from the field device ECB
Disable Communications Disables communications between the field devices and the
field device ECB
Enable Communications Enables communications between the field devices and the
field device ECB
Service and Support

If you need assistance, please contact Global Customer Support via https://pasupport.schneider-elec-
tric.com.
221
222
12. Troubleshooting FDC280
Hardware
This chapter describes possible suboptimal FDC280 situations and provides diagnostic routines
that allow you to locate and resolve these conditions quickly.
Overview
In most cases, problems occur because the controller is misconfigured or there are detected prob-
lems in the network connections. In the event of suboptimal hardware behavior, the Foxboro Evo
system maintenance approach is oriented toward module replacement. Any module can be
replaced without affecting the operation of any other module, including the other module of a
fault tolerant pair.
The Station Block displays provide information to help you evaluate FDC280 performance. For
more information, refer to Integrated Control Block Descriptions (B0193AX), System Manager
(B0750AP), and Process Operations and Displays (B0700BN).
NOTE
If you have a field device connected to the fault-tolerant FDC280 and the device is
power-cycled, a failover operation may occur if the device connects to the Shadow
FDC280 first and takes a much longer time to connect to the Primary FDC280.
FDC280 LCD, LED Indicators, and Reset Button

The liquid crystal display (LCD) and light-emitting diodes (LEDs) on the front of the FDC280
module (Figure 12-1) provide visual indication of the module’s operational status and
transmit/receive communications activity. The recessed Reset button enables you to restart the
FDC280.
The control network path LEDs indicate which FDC280 is primary; these LEDs are only active
on the primary module.
The LCD and LEDs are described in separate sections below.
223
B0700GQ – Rev C 12. Troubleshooting FDC280 Hardware
First line (letterbug)

and role Liquid Crystal Display
Second line (status info) (LCD)
Operational Status LEDs

Reset Button (Recessed) Green (Top)/ Red (Bottom)
Future
Future Ethernet Status

for Field Devices
NOTE: Text shown in the LCD above may not be typical for an FDC280. Typically, Line 1 would include
“Single”, “Primary”, or “Shadow” depending on the FDC280’s role, after the CP’s letterbug. Line 2
would show messages (listed below) such as “Ethernet OK” to indicate that the Ethernet
connection status is good.
Figure 12-1. FDC280 LED Indicators and Reset Button
Liquid Crystal Display (LCD)

The FDC280 has a liquid crystal display (LCD) on its faceplate, which displays operational sta-
tus, configuration, revision, and identification information on two lines as shown in Figure 12-1:
♦ The first line typically displays the FDC280’s letterbug and role (“Single”, “Primary”,
or “Shadow”).
♦ The second line typically displays the FDC280’s part number, operating system ver-
sion, hardware revision and manufacturing date, and Ethernet status, as described in
“Typical Messages During Normal Operation” in Control Core Service V9.x System
Error Messages (B0700AF, Rev. C or later).
Operators can set the FDC280’s letterbug using the arrow and Select keys as described in “Man-
ual Letterbug Assignment via LCD Display” on page 37.
Pushing and holding in any of the three buttons under the LCD (Select, Up or Down) illuminates
the backlight behind the LCD to full brilliance. When released, the backlight remains on at half-
brilliance for one second. At power up, the backlight is on for about three seconds.
224
12. Troubleshooting FDC280 Hardware B0700GQ – Rev C
Start-up Diagnostic Display

During start-up diagnostics, the LCD indicates if the boot process did not succeed. If this condi-
tion is detected, an error code identifying detected condition is displayed on the second line of
LCD, such as:
DDR3 Memory Configuration FAILED!
Invalid Images, can't boot!
Default Operational Display

During normal operation, the LCD shows the letterbug, operational state of the module, and
left/right position in the baseplate. Normal statuses on Line 1 are:
<CP letterbug> <Status> <L/R>
Where:
<CP letterbug> is the FDC280 letterbug
<Status> is the FDC280’s operational status of Single, Primary, or Shadow
<L/R> is the Left/Right position of the FDC280 in the baseplate: L for left position,
or R for right position.
For example, a single FDC280 with letterbug “FP0101” in the left position of the baseplate dur-
ing normal operation would show “FP0101 Single L” on the first line.
The second line shows the following sets of messages:
Part No <part #>
Where <part #> is the FDC280 part number - e.g., “Part No RH101FQ”
Ver <ver>
<ver> is the FDC280 image version - e.g., “0903001001”
Rev <FPGA Rev><Hardware Rev> Date <Manufacture Date>
Where:
<FPGA Rev> is a single letter indicating the CPU FPGA revision value.
<Hardware Rev> is a single letter indicating the hardware revision value.
<Manufacture Date> is the 2-digit year, followed by the 2-digit week within the
year in which the module was manufactured.
For example:
Rev CA Date 1652
Where C is the FPGA revision, A is the hardware revision, and the module was
manufactured in year 16 (2016), the 52nd week.
Ethernet OK - or
Ethernet A BAD - or
Ethernet B BAD - or
Ethernet A/B BAD
These indicate the Foxboro Evo Control Network Ethernet connections status for the
FDC280.
This second line takes 20 seconds to cycle through all four different second lines, displaying each
piece of information for five seconds.
225
For a list of messages shown during normal operation, refer to “FCP280, FDC280, and CNI
LCD Messages” in Control Core Service V9.x System Error Messages (B0700AF).
Detected Error Displays

When the FDC280 is not operational due to becoming unavailable, the LCD shows the condi-
tion information as follows. Line 1 reads:
<CP letterbug> Subsys ID <ID> Error = <error>
Where:
<CP letterbug> is the FDC280 letterbug
<ID> is the numeric ID for the reporting subsystem
<error> is the numeric code for the detected error condition
Line 2 reads:
<Error message text>
Where:
<Error message text> is descriptive text corresponding to the detected error con-
dition.
The information shown in each of these lines may be up to 32 characters long. As the LCD dis-
play can only show 16 characters per line, text over 16 characters will scroll to the left to display
the full line.
For a list of detected error messages shown on the LCD, refer to “Error Messages Following
FCP280/FDC280 Failure or CNI Runtime Errors” in Control Core Service V9.x System Error Mes-
sages (B0700AF).
LED Indicators
Light-emitting diodes (LEDs) on the front of the FDC280 (see Figure 12-1) provide visual
indication of the:
♦ FDC280 operational status
♦ Transmit (Tx)/receive (Rx) communications activity of the Ethernet, serial (not used),
and EtherNet/IP (not used) channels.
Table 12-1 describes these LEDs and controls.
Table 12-1. FDC280 LED Indicators and Reset Button
Item Description
Operational Status LEDs (top two) Green and red LEDs indicate the health of the FDC280.
See “Using the Operational Status LEDs” on page 229.
Reset Button Resets the FDC280 when pressed. (It is recessed on the
faceplate.) The FDC280’s database is reloaded from the
boot host workstation or from the primary module, or
from flash memory if self-hosted. Refer to “Types of
Resets” on page 228.
226
Table 12-1. FDC280 LED Indicators and Reset Button (Continued)
Item Description
Ch1-4 Tx/Rx Yellow/Green bi-color LED indicates when the primary
FDC280 is transmitting or receiving data on the serial bus
as described below. These LEDs are active only on the pri-
mary FDC280.
ENet Green color LED that indicates activity on the Ethernet
connection to the field devices
Mod and Net For future use.
The Channel Tx/Rx and ENet LEDs indicate transmit/receive communication status over the
corresponding channels as follows:
♦ (Channel Tx/Rx only) Flashing YELLOW indicates transmit data is present.
♦ (Channel Tx/Rx only) Flashing GREEN indicates receive data is present.
♦ (ENet only) Flashing GREEN indicates activity on the Ethernet connection to the
field devices
♦ NOT FLASHING indicates that:
♦ There is no data being received or transmitted. Check configuration to make sure
that Channel, Driver and Devices have been enabled.
♦ The Ethernet or serial cabling is disconnected, broken, or otherwise compro-
mised. Check the cabling between the FDC280 baseplates and the field device
cable connections. For more information, refer to the manual which describes
FDC280 communications for the appropriate protocol.
If none of the above issues caused the bus to be inactive and you know that data
must be being transferred, you must replace the module.
To identify any issues with the connections to the control network (ETHERNET), check the sta-
tus messages displayed on the second line of the LCD, listed in “FCP280, FDC280, and CNI
LCD Messages” in Control Core Service V9.x System Error Messages (B0700AF).
Operational Status LED Indicators

The Operational Status LEDs (red and green) on the front of the FDC280 indicate the module’s
operational status (see Figure 12-1). Table 12-2 describes the operational conditions indicated by
these LEDs.
Table 12-2. FDC280 Operational Status LEDs
Red
(Bottom) Green (Top)
LED LED Status
OFF ON Module is online and functional. (This is the normal run state.)
OFF OFF No power, or an error is detected in which the green and red LED is
not turned on.
227
Table 12-2. FDC280 Operational Status LEDs (Continued)
Red
(Bottom) Green (Top)
LED LED Status
ON ON Start-up, or an error is detected in which the green LED is not
turned off. On power-up, both LEDs are on. The red LED is on for
about three seconds. The green LED remains on until a hardware
error is detected.
ON OFF Module is in detected failed state, or it is running start-up diagnos-
tics during boot up.
Types of Resets
The FDC280 supports two types of reset operations:
♦ Warm - Only issued under manual button control. Pressing the recessed Reset button
(see Figure 12-1) for under two seconds invokes a Warm reset, which restarts the sys-
tem software but does not perform a hardware reset of the peripherals. As part of the
software initialization, all the Ethernet PHYS1 (the physical layer of the OSI model
and the control network communications) are still issued with a soft reset.
The Warm reset should be used if a module has rebooted or gone offline (red/green)
in order to recover the detected error code stored in the CPU memory area.
♦ Cold - Always issued when the FDC280 is powered on or after holding the recessed
Reset button for greater than two seconds. A Cold reset resets everything in the system
as if a power cycle had been invoked. It is indicated by rapid flashing of the display
backlight.
FDC280 Troubleshooting
This troubleshooting information is provided as a service guide for some of the most commonly
encountered system problems. Problems that surface in many cases are faults associated with com-
munication paths (cables, connectors, internal data and power buses, and so forth).
NOTICE
Do not attempt to repair modules in the field. Replacing modules is

acceptable.

damage.
1. APHY connects a link layer device (often called MAC as an abbreviation for media access control)
to a physical medium such as an optical fiber or copper cable.
228
To reboot the FDC280, use the System Manager when possible. You can also press the recessed
reset button in the field but this should not be your first choice.
If you have a field device connected to the fault-tolerant FDC280 and the device is power-cycled,
a failover operation may occur if the device connects to the Shadow FDC280 first and takes a
much longer time to connect to the Primary FDC280.
Using the Operational Status LEDs

The Operational Status LEDs (red and green) on the front of the FDC280 (see Figure 12-1) indi-
cate the module’s operational status.
Red off, Green off

When the red and green LEDs are off, this typically indicates loss of dc power. Perform the
following checks. (These checks need not be followed in order.)
1. Verify that the power cable is firmly connected to the baseplate and power supply.
2. If other module(s) in the modular baseplate are operating correctly, then:
a. Cycle power to the unavailable FDC280 module (off then on) by unscrewing the
two self-retaining hex screws on the module using a hex driver tool (X0179AZ),
pulling the module from the baseplate, then pushing the module back on the
baseplate and tightening the two self-retaining hex screws on the module using a
hex driver tool, as described in “Replacing an FDC280 Which is Not Working”
on page 233.
NOTICE
baseplate.
operation. It is inadvisable to depend on the signal connectors to hold
the module in place.

damage.
b. Replace the FDC280 module which is not working with a known good module to
test that slot in the baseplate (see “Replacing an FDC280 Which is Not Working”
on page 233).
c. Remove the FDC280 module and check the connector for bent pins. For module
removal procedures, see “Replacing an FDC280 Which is Not Working” on
page 233).
229
3. Verify that the operational status LEDs on the front of the Foxboro power supply
(FPS400-24, FPS240-24, or FPS120-24) are in the normal state (green LED is on,
and red LED is off ).
4. Use a multimeter to verify that the dc voltage at the output connector is within the
range 21.6 to 25.2 V dc. For connector pin assignments, refer to Standard and Com-
pact 200 Series Subsystem User’s Guide (B0400FA).
5. If all modules on the baseplate are not working and the Foxboro power supply is oper-
ating normally, remove the power cable from the power supply and baseplate, and use
a multimeter to verify continuity of the cable conductors, or replace the cable. For
more information, refer to Standard and Compact 200 Series Subsystem User’s Guide
(B0400FA).
If none of the above checks resolve the suboptimal condition, you must replace the module.
Red on, Green off

When the red LED is on and the green LED is off, this indicates that the module was unable to
pass the online diagnostics. This usually indicates a detected hardware error of some kind. Hard-
ware issues detected are typically internal to the FDC280 module, but you can try these tests to
correct the problem:
1. Reboot the FDC280 module using either the module Reset button (see Figure 12-1)
or the System Manager (refer to System Manager (B0750AP)). In System Manager
(B0750AP), refer to “Reboot” under section “Equipment Change Actions”.
2. Cycle power to the unavailable FDC280 module off then on as follows:
a. Unscrew the two self-retaining hex screws on the module using a hex driver tool
(X0179AZ). See “Replacing an FDC280 Which is Not Working” on page 233.
NOTICE
baseplate.

damage.
b. Pull the module from the baseplate and push the module back on the baseplate.
c. Secure the two self-retaining hex screws on the module.
3. If the module is part of a fault tolerant pair, replace it and verify that the new module
marries successfully.
230
NOTICE
POTENTIAL DATA LOSS
If the unavailable FDC280 module is part of a fault tolerant module

pair, disconnecting the time strobe cable from the baseplate causes
the primary FDC280 module on control not to receive the time strobes
it requires for time synchronization.
4. Check for insufficient voltage, as shown in Steps 1 through 4 in the previous section.
Red on, Green on

On power-up, the default condition of both LEDs is on. Once the FDC280 module is running,
software turns off the red LED. If this state persists, an error is detected in the processor. Please be
patient with this state – if the module is updating its software, it may stay in the red-green state
for as long as five minutes.
1. Verify that the module is properly configured using System Manager.
2. Check the cabling to the network adapter. If married, the module can persist in the
red-green state when the cables are improperly connected, for example, by swapping
the control network A and B cables on a fiber adapter.
If these steps do not work to bring the green LED on and the red LED off, you must replace the
module.
Cycling Red, Red/Green

The FDC280 passes its main processor diagnostics, and then it tries to load software into the
Input/Output controller. For whatever reason, this load is either not working or the cooperative
diagnostics between the two processors reach a bad conclusion.
1. If the module is married to its fault tolerant partner, make sure that the customer-sup-
plied dedicated network cabling is properly connected to the baseplate.
2. Cycle power to the FDC280 module off, then on, as follows:
a. Unscrew the two self-retaining hex screws on the module using a hex driver tool
(X0179AZ). See “Replacing an FDC280 Which is Not Working” on page 233.
231
NOTICE
torque (1.356N-m), or you might strip the threaded inserts out of the
baseplate.

damage.
b. Pull the module from the baseplate and push the module back on the baseplate.
c. Fix the two self-retaining hex screws on the module.
If these steps do not bring the green LED on and the red LED off, you must replace the module.
Red off, Green on

When the red LED is off and the green LED is on, this indicates that the module is online and
functional. This is the normal operating state.
Fault Tolerant FDC280 Troubleshooting Addenda

The FDC280 uses software synchronization to keep the two modules executing exactly the same
software, using exactly the same data. If the software is not synchronized, synchronization is
restored when the primary module transmits its database to the shadow module in a sequence
commonly referred to as a “hot remarry.” The hot remarry is essentially the same as the initial sta-
tion marriage.
A hot remarry operation should take no more than 0.5 seconds. To minimize the impact on a
process, no more than five hot remarry operations may occur within a one minute period.
If more than five hot remarry operations occur within a one minute period, the Primary FDC280
switches to Single mode and the fault tolerant control processor marriage is broken, which puts
the Shadow FDC280 in the offline state. The message “Exceeded Escalation Threshold” is
printed on the system printer or at the System Monitor message display. You may then use the
System Manager to reboot (restart) the shadow FDC280.
If no “hot remarry” operations have occurred for a period of seven days, a hot remarry is forced to
diagnose any latent hardware issues (such as a shadow transmitter which is not working or to
allow a test to force detected ECC errors to exercise error detection logic) which are not detected
in normal operation.
If either FDC280 in a fault tolerant pair becomes unavailable, the unavailable module’s red oper-
ational LED turns on. If this occurs, proceed with these checks. (These checks need not be fol-
lowed in order.)
232
1. Make sure that the FDC280’s Ethernet network fiber cables are correctly connected to
the network adapters.
2. Check for detected error messages at the system printer or at the System Monitor mes-
sage display.
3. Replace the FDC280 if all else does not succeed, as described in the next subsection.
Replacing an FDC280 Which is Not Working

To replace a module which is not working in an FDC280 fault tolerant pair, proceed as follows:
1. Loosen the FDC280 base mounting screws completely using a 5/32 hex driver tool
(P/N X0179AZ).
NOTICE
baseplate.

damage.
2. Using both hands, pull on the FDC280 to remove it from the baseplate.
3. Install the new FDC280 using the appropriate procedure. See “Installing a Shadow
FDC280 Module” on page 42.
After the new FDC280 (shadow) is installed, it automatically boots up, acquires its letterbug,
image, and control database from the primary module, and marries the primary module.
Available Detected Memory Error Messages

The FDC280 enforces a memory protection scheme during block installation. The total database
size must not exceed 22 MBytes, and the FDC280 requires a minimum of approximately 2 MB
of free memory. This is always enforced during the block installation operations. This results in an
FDC280 with the maximum amount of memory devoted to blocks displaying approximately
2 MB of memory available. This protective feature is in effect for all FDC280 installations.
233
NOTE
However, be aware that previous versions of I/A Series software (v8.8 or earlier)
were not designed for this 2 MB minimum. SMON notifications in Control Core
Services and I/A Series software are set to trigger messages when the FDC280’s free
memory threshold is at 400 KB, 200 KB, and 100 KB. Since the FDC280’s free
memory minimum is 2 MB, be aware that these trigger messages will not activate
for the FDC280.
For a list of memory detected error messages shown on the LCD, refer to “FCP280, FDC280,
and CNI LCD Messages” in Control Core Service V9.x System Error Messages (B0700AF).
Exceeding Allowable Object Manager (OM) Updates/Second

With the support of maximum of 28,000 points in OM Scanner table, it is possible that the OM
Scanner would not be able to scan through all points at the end of its cycle due to lacking of
resource for the cycle. In such case, the OM Scanner stops scanning for the cycle, increments the
counter “OM Update Missed Due to Lack of Resource” under the Application Layer and the OM
Scanner Overrun. The OM Scanner continues from the next un-scanned point in the next cycle
until finishing the last point in the table. Once it finishes the last point, the OM Scanner will stop
scanning for the cycle and start from the beginning in the next cycle.
Updates might be skipped due to the OM Scanner’s resource limitation, but the latest update
would not be missed. If it is skipped in the current cycle, it will be picked up in the next cycle. To
resolve this, reduce the load on OM Scanner or on the FDC280. For details on how to do this,
refer to The Foxboro Evo System Planning and Sizing (B0700AX) and FDC280 Sizing Guidelines
and Excel® Workbook (B0700GS).
E43 Detected Error Generated During FDC280 Deployment

During the control database deployment to the FDC280, this error is detected if any of these
three conditions is satisfied:
E43 "E43 - MAXIMUM NUMBER OF BLOCKS REACHED"
♦ The maximum number of total supported blocks (8262) is exceeded.
♦ The maximum number of supported driver instances (currently 1) is exceeded.
♦ The maximum number of supported devices is exceeded.
The FCP280’s deployment process also can detect this error but only if the first condition is satis-
fied and the number of blocks is exactly 8000 (not 8262). The FDC280 deployment differs in
that any of the above three conditions cause this detected error to be generated.
FDC280 Switchover Changes IDLE Time

The FDC280 has two idle metrics for its CPU cores:
♦ For Core 1 - CORE 1 IDLE TIME (IDLETM parameter in Station Block)
♦ For Core 2 - IDLE TIME (IDLET2 parameter in Station Block)
These are shown separately in HMI station displays such as FoxView.
234
Figure 12-2. FDC280 Core 1 and Core 2 Idle Metrics in FoxView
When rebooting or enforcing a switchover from the FDC280 running as Primary to the FDC280
running as Shadow (e.g. when the Shadow becomes the Primary), there is a temporary, noticeable
but slight change in the CORE 1 IDLE TIME for Core 1, and similarly, a temporary but signifi-
cant change in the IDLE TIME for Core 2. In fact, the Core 2 IDLE TIME will show up to 90+
percent initially and then decrease quickly to the actual value. Typically within 10–20 seconds,
the actual correct value will be displayed.
When FDC280s are running in a fault tolerant configuration, the Primary FDC280 performs the
majority of the actual work (e.g. 8000 points configured to be read from multiple devices – the
Primary FDC280 is issuing 8000 reads in a short amount of time and the Shadow FDC280 is
issuing as few reads as possible to maintain a working knowledge of the health of its connections
to the devices).
As the Shadow FDC280 runs significantly fewer operations, it is expected to have a significantly
higher idle time than the Primary FDC280. Fault tolerant FDC280s can only report one IDLE
TIME, so the pair only reports the IDLE TIME time of the Primary FDC280 (the one doing the
most work).
235
However, when the Shadow FDC280 becomes the Primary (when the original Primary is no lon-
ger available) the current IDLE TIME (the high IDLE TIME as it was as Shadow) can be per-
ceived for a short amount of time. Then it quickly advances to the actual value.
Due to differences in processing when in a married fault-tolerant state versus single/simplex oper-
ation, the FDLOAD parameter may show lower load when the FDC280 is single/simplex.
FDLOAD may also vary to a lower value when significant maintenance activities (such as check-
point, Image Update, or upload actions) occur due to more rapid processing of I/O events in a
controller that would otherwise experience more idle time.
FDC280’s OM Scanner
When the FDC280’s Object Manager (OM) Scanner database is full at the time the FDC280 is
rebooted, it is possible that not all list points managed by the FDC280 will reconnect.
The OM Scanner database consists of 1400 rows of 20 points each for a total of 28,000 total scan
points. This problem is associated with the number of rows used in the OM Scanner by OM lists
and is not dependent on the total number of points. The problem only occurs if the number of
free rows in the OM scanner is one or zero.
For example, assume that applications on the Foxboro Evo Control Network, such as FoxView
displays, Control HMI displays, Historian connections, peer to peer connections, and so forth,
result in 1399 or 1400 rows of the FDC280’s OM Scanner database being filled. Each of these
points is connected and scanning. Then the FDC280 is rebooted. Normally it would be expected
that all these points are automatically reconnected by the FDC280 after the reboot. However,
when the OM Scanner is at this capacity, all points might not reconnect. This occurs because,
potentially, one list that previously had all its points scanning could now have as many as 46
points not scanning. Alternatively, two or more lists could have a total of 46 points not scanning.
The chances of this problem occurring are very low as it is unlikely that the OM Scanner will ever
be filled to capacity during normal operation.
You can recognize and avoid this potential problem by viewing the contents of the FDC280 OM
Scanner by using the “rsom” workstation tool found in D:\opt\fox\bin\tools. Refer to Software
Utilities (B0193JB) for details on using “rsom”. Use the “scan” command in the tool to view the
scanner database table. It indicates the count of free scanner rows in the top right corner of the
display.
If the number of free rows is 1 or 0, it is recommended that you reduce the load of the OM scan-
ner by closing at least one of the lists. This can be done by closing a display or reducing the num-
ber of Historian or peer to peer connections.
Memory Dumps
There are three kinds of memory dumps. If the FDC280 module detects a software error while
running (such as Watch Dog Timer (WDT) time-out or a memory violation), it saves a memory
image of the FDC280 so that a thorough analysis of why it has stopped working can be per-
formed. The unavailable FDC280 also compresses and writes the entire data space into flash
memory for later analysis. The FDC280 will reboot immediately after writing the memory dump
into the flash memory (elapsed time up to 240 seconds). Upon reboot, the FDC280 sends a mes-
sage to the detected error log indicating that it experienced a memory violation or WDT time-
out.
236
The second kind of memory dump is when a “Forced” dump is initiated, whereby the current
contents of memory are compressed and saved into flash. Forced dump analysis IS NOT useful to
analyze hardware unavailability conditions of FDC280s with RED only or RED/GREEN opera-
tional LEDs. Forced dumps erase any previous memory violation information stored in flash, so
should only be initiated at the express request of Foxboro development personnel.
As well, for debugging purposes for Schneider Electric, the FDC280 has the capability to dump
its memory contents to flash memory when in the offline state - that is, when the module has its
RED/GREEN LEDs lit and a message scrolling across the LCD screen identifying why it is
offline. When the FDC280 is in this state, simultaneously select the Select and Up Arrow but-
tons to initiate the dump function. To extract the dump from flash memory, use one of these
methods:
1. The FDC280 is replaced by another FDC280 and its dump information extracted
offline.
2. The FDC280 can be uploaded online while still running all normal control
functions.
WARNING
For safety reasons, always consider the possible impact on plant

operations before placing the Primary FDC280 module offline or
rebooting it after the shadow module stopped working.

injury.
NOTICE
POTENTIAL DATA LOSS AND EQUIPMENT DAMAGE
Physically removing an FDC280 from a fault tolerant pair means that

your plant will have to assume the responsibilities and potential
conditions with running control in simplex/non-fault tolerant mode.
Failure to follow these instructions can result in data loss and/or

equipment damage.
a. If the FDC280 was married at the time of the violation, only the information
from the Primary FDC280 can be uploaded (the shadow FDC280 will be placed
offline during the dump upload). If the violation was in the shadow module, it
must become the primary to upload the memory dump. To make the Shadow
FDC280 become Primary, use the System Manager to reboot the Primary
FDC280.
237
b. To initiate the dump upload from the command line prompt, execute the
iaboot_upld <letterbug> command from directory opt/fox/bin/tools.
The FDC280 sends its entire flash memory contents to a 53 MB file in directory
d:/usr/fox/sp/files with the name <letterbug>_dump<X> where <X> is a sequen-
tial number with the current dump having the greatest number.
The entire upload process takes approximately three minutes and its status is
indicated by messages at the system printer or at the System Monitor message dis-
play.
Syntax
iaboot_upld <letterbug> <action>
where:
♦ <letterbug> = six-character letterbug of the FDC280
♦ <action> = U to upload existing dump image from single/primary module.
This is the command that should always be used to extract memory violation
information.
♦ <action> = F to create a new dump image and restart single/shadow module
NOTICE
POTENTIAL DATA LOSS
The “F” option forces a dump of the current module state and WILL
ERASE any information from a previous memory violation. ONLY USE
the “F” option when directed by Foxboro Development personnel.
After successful launch of the program, it issues a double-check message as

follows.
If action = F:
“Create a new dump image and restart single/shadow module - enter Y/N:”
If action = U:
“Set controller to run single and upload existing dump image - enter Y/N:”
If Y (or y) is entered, a final message is issued
“Create new dump image initiated.”
or
“Upload dump initiated”
c. If the original fault is detected while the FDC280s were married, you can now
restart the offline FDC280, which remarries its partner. To restart the module, in
System Manager (B0750AP), refer to “Reboot” under section “Equipment Change
Actions”.
238
NOTE
Non-fault tolerant FDC280 can transmit their memory dump at any time.
For a list of messages shown on the LCD, refer to the messages under “Runtime Diagnostic Han-
dler Subsystem Messages” in Control Core Service V9.x System Error Messages (B0700AF).
FDC280 Diagnostics
The FDC280 diagnostic routines are broken down into these areas:
♦ Start-up
♦ Detected Error Recovery Local
♦ Detected Error Recovery Cooperative
There are no user scheduled diagnostics required for the FDC280.
Start-Up Diagnostics
Start-up diagnostics run every time the FDC280 module is powered up or restarted. Start-up
diagnostics test the basic core functionality of the module prior to running control or attempting
marriage. They consist of boot flash checksum, code flash checksum, main and I/O shared mem-
ory tests, interrupt controller tests, and other low level functionality. The start-up diagnostics
complete in approximately five seconds. An unavailability condition detected is indicated by the
Operational Status LEDs (red LED remains on and green LED remains off ).
Detected Error Recovery Local Diagnostics

Detected error recovery local diagnostics run during the FDC280’s initial installation and subse-
quently whenever a fault is detected by the run-time mechanisms (output miscompare, sync time-
out, and so forth). These diagnostics attempt to detect any faults that can be isolated to a particu-
lar controller. Examples are Ethernet port loopback tests, state sequencer tests, interrupt controller
tests, shared memory tests, and I/O interface tests. An unavailability condition detected is indi-
cated by the Operational Status LEDs (red LED is on and green LED is off ) and by messages at
the system printer and/or at the System Monitor message display.
Detected Error Recovery Cooperative Diagnostics

Detected error recovery cooperative diagnostics run when a fault is detected by the run-time
mechanisms (output miscompare, sync time-out, and so forth). These diagnostics tests work
cooperatively to detect any faults that inhibit normal fault tolerant operations.
If a particular FDC280 has become unavailable, that FDC280 is sent to the failed state. An exam-
ple of this type of suboptimal condition is a detected compare logic operation that did not suc-
ceed. In this case, FDC280s A and B perform cooperative loopback tests with comparison logic
enabled; FDC280 B passes all tests and FDC280 A stops working due to a miscompare.
If a fault is detected in the mechanisms but it cannot be isolated to a particular FDC280, the
shadow FDC280 is sent to the offline state. An example of this is when an inter-link exchange is
not successful.
If no fault is detected then a PASSED indication is returned which results in a Hot-Remarry
where all variable data from the primary FDC280 are copied into the shadow FDC280.
239
A module becoming unavailable is indicated by the Operational Status LEDs (red LED is on and
green LED is off ) and by messages at the system printer and/or at the System Monitor message
display.
FDC280 Diagnostics
The FDC280 operates in the same way as the FCP280 when selecting Offline Diagnostics
from System Manager (at the station level). This System Manager action puts the selected module
(Primary/Shadow) in an offline state with both the Red/Green LEDs turned on. When in this
state, the offline module can be rebooted using System Manager by selecting the Shadow module.
No other operations are performed in this state.
Network Adapter LED Indicators

Light-emitting diodes (LEDs) on the front of the copper adapter and fiber adapter modules
(Figure 12-3) provide visual indication of the module’s operational status and transmit/receive
communications activity of the control network A and B links, as well as communications to the
FDC280s in the baseplate. Table 12-3 describes these LEDs.
The control network path Tx LEDs indicate which controller is primary as well as the network
path it is using; these LEDs are only active on the primary module.
Operational Status LEDs
Ethernet Switch Communication

Activity Indicators
Figure 12-3. Copper and Fiber Adapter LED Indicators
240
Table 12-3. Network Adapter LED Indicators
LED Description
Operational Status (top) Yellow LED indicates the health of the external power supply to
the network adapter.
OFF indicates both 24 V dc sources are OK.
YELLOW ON indicates one of the two 24 V dc sources is missing,
has detected errors, or the fuse for one source is blown.
Operational Status (bottom) Red and green bi-color LED indicates the health of the internal
power supply for the network adapter.
GREEN ON indicates the internal 3.3 V supply is running
normally (power OK).
RED ON indicates the internal 3.3 V supply is not OK.
Switch Yellow link/activity LED for The Mesh control network connec-
tion (network switch 100 Mbit Ethernet connection), copper or
fiber. YELLOW ON indicates the link is running normally.
Blinking indicates data transfer activity, transfer (TX) or receive
(RX).
1 Yellow link/activity LED for 100 Mbit Ethernet communications
between the network adapter and the FDC280 in slot 1 on the
baseplate. Blinking indicates data transfer activity.
Not blinking indicates that no data is being transferred - it may
indicate that the cabling for that port is disconnected, broken, or
otherwise compromised. If you suspect an issue, check the cable to
the network adapter or Ethernet switch for that port.
2 Yellow link/activity LED for 100 Mbit Ethernet communications
between the network adapter and the FDC280 in slot 2 on the
baseplate. Blinking indicates data transfer activity.
Not blinking indicates that no data is being transferred - it may
indicate that the cabling for that port is disconnected, broken, or
otherwise compromised. If you suspect an issue, check the cable to
the network adapter or Ethernet switch for that port.
241
242
13. Troubleshooting FDC280 Ports
This chapter provides troubleshooting information for the FDC280 when used with any
supported Ethernet or serial field devices.
If you have a field device connected to the fault-tolerant FDC280 and the device is power-cycled,
a failover operation may occur if the device connects to the Shadow FDC280 first and takes a
much longer time to connect to the Primary FDC280.
FDC280 Ethernet I/O Port in Offline State

If the default Gateway address is not in the same subnet as the FDC280’s Ethernet I/O port, the
System Manager equipment status shows the “Device Port Configuration” field with a value of
“Invalid”. As well, the System Monitor log (smon_log) shows the following message: “Invalid
Gateway Configured in ECBP”.
To resolve this issue, verify that your default Gateway address is in the same subnet as the
FDC280’s Ethernet I/O port.
Ethernet and Serial Port Counters and Device

Diagnostic Blocks
The current Ethernet/serial port counters and diagnostic blocks for each Ethernet/serial device
interface may be monitored The block definitions are shown in Table 13-3.
The Ethernet port counters and the counters for serial ports 1-4 are available in the System
Manager.
Also refer to Appendix D “FDC280 Debug Driver and FDC280 I/O Diagnostic Tool” for details
about the diagnostic tool.
Resetting Port Counters

The System Manager allows for resetting counters as a set or individually. Resetting a counter will
reset both the Primary and Shadow FDC280s’ value for that counter. The FDC280’s Ethernet
Counters cannot be reset individually. Resetting any one of the Ethernet counters will reset them
all.
243
B0700GQ – Rev C 13. Troubleshooting FDC280 Ports
Table 13-1. Counters Display for Ethernet Port Counters For FDC280
Counter Behavior Default Description

Ethernet Device Port This counter increments on 0 Bad FDC280, Bad device, Inter-
Error Packets [For each bad Ethernet packet mittent Cable, Bad Switch,
FDC280 Only] received on the device port Switch or device power unavail-
of the FDC280. It incre- ability detected, DOS attack.
ments when the driver
detects CRC, Framing and
size errors.
Ethernet Device This counter increments on 0 Normal behavior is to increment
Received Packets each received Ethernet at least twice per scan cycle and
[For FDC280 Only] packet on the device port. this is a normal indication of suc-
cessful device communications.
Ethernet Device Port This counter increments on 0 This counter increments on each
Transmitted Packets each transmitted Ethernet transmitted Ethernet packet on
[For FDC280 Only] packet on the device port. the device port.
Serial Port Parameters

The port parameters for each of the Serial Ports 1 through 4 are available in the System Manager
This list of diagnostic counters are now presented in the System Manager as part of FDC280
serial port ECBP.
♦ Transmitted messages count
♦ Transmit message detected error count
♦ Received messages count
♦ Parity detected error (received) count
♦ Framing detected error (received) count
♦ Checksum detected error (received) count
Separate sets of counters are maintained for the left and right FDC280 modules. However, only
the counters from the Primary FDC280 will be displayed.
For fault tolerant FDC280s, serial port counter data for each module is preserved as long as there
is at least one module running to remember the data.
Table 13-2. Counters Display for Serial Port Counters For FDC280
Counter Description Default Cause of Behavior

Serial Device Port Count of messages received 0 A detected checksum error can
Checksum Error from the device that were be caused by device with incom-
(received) counter considered unsuccessful due patible protocol or interference
[For FDC280 Only] to a detected checksum in the serial line.
error.
244
13. Troubleshooting FDC280 Ports B0700GQ – Rev C
Table 13-2. Counters Display for Serial Port Counters For FDC280 (Continued)
Counter Description Default Cause of Behavior

Serial Device Port Count of messages received 0 A detected framing error can be
Framing Error from device that were con- caused by incorrect configura-
(received) counter sidered unsuccessful due to a tion or interference in the serial
[For FDC280 Only] detected framing error. line.
Normal behavior is to increment
at least twice per scan cycle and
this is a normal indication of
successful device communica-
tions.
Serial Device Port Count of messages received 0 A detected parity error can be
Parity Error from device that were con- caused by incorrect configura-
(received) counter sidered unsuccessful due to a tion or interference in the serial
[For FDC280 Only] detected parity error. line.
Serial Device Port Count of messages received 0 This counter increments on each
Received Message from devices. received Serial Port packet on
Error counter the device port.
[For FDC280 Only] Depending on the protocol,
messages are delineated by a 3-
character break in transmission
or by distinct start/stop patterns.
Serial Device Port Count of detected port 0 A detected transmission error
Transmitted Message transmission errors. can occur if serial port/line is not
Error Counter in the proper mode when
[For FDC280 Only] attempting to transmit.
Serial Device Port Count of messages transmit- 0 This counter increments on each
Transmitted Message ted to devices. transmitted Serial port packet on
Counter the device port.
[For FDC280 Only]
Other Diagnostic Information

The other diagnostic information for each device on the Ethernet/serial ports can be obtained by
configuring DCI blocks as shown in Table 13-3.
Table 13-3. Ethernet/Serial Device Diagnostic Blocks
Parameter Value Description

NAME * Block name of the point
Block * Block type, varies depending on the counter
Type
IOM_ID * Provides a complete path to the parent ECB201.
245
Table 13-3. Ethernet/Serial Device Diagnostic Blocks (Continued)
Parameter Value Description

PNT_NO * $x_RESET_CNTRS See “Reset Counters” on
page 246.
$x_RESP_TIMEOUTS See “Response Timeout Counter”
on page 247 below.
$x_WORST_RESP_TIME See “Worst Response Time” on
page 247.
$x_MSGS_SENT See “Good Messages Sent” on
page 248.
$x_MSGS_RCVD See “Good Messages Received” on
page 248.
$x_MISC1_ERRS See “Modbus Device Exception
Responses” on page 248.
$x_MISC2_ERRS See “Modbus Gateway Exception
Responses (Ethernet Only)” on
page 249.
$x_LAST_ERR_MSG See “Last Detected Error Mes-
sage” on page 249.
$x_OVERSCAN_TIME_HIGH See “Over Scan Time High” on
page 250.
$x_OVERSCANS See “Number of Over Scans” on
page 250.
$CONFIG_OPTIONS See “Configured Options” on
page 251.
#_SCANTIME See “Group Scan Time” on
page 251.
Where x = “L” or “R”
Prefix '$L' corresponds to the counter value on the FDC280 installed in
the left FDC280 slot of the baseplate, while '$R' corresponds to the coun-
ter value on the FDC280 installed in the right FDC280 slot of the base-
plate.
Reset Counters
When the value is toggled, this resets all counters for the device on the corresponding FDC280.
Block definition is as follows:
Block Type BOUT Defines the block as a discrete output block
IOM_ID * Provides a complete path to the parent ECB201 device
block
246
PNT_NO * FDC280 Single: $L_RESET_CNTRS

FDC280 Fault-Tolerant: $L_RESET_CNTRS
$R_RESET_CNTRS
Prefix ‘$L’ corresponds to counter value on the
FDC280 installed in the left baseplate slot,
while the prefix ‘$R’ corresponds to counter
value on the FDC280 installed in the right
baseplate slot.
Response Timeout Counter

The number of response timeouts (query sent, but no reply received) on a specific device may be
monitored. Block definition is as follows:
Block Type IIN Defines the block as an integer input block
block
PNT_NO * FDC280 Single: $L_RESP_TIMEOUTS
FDC280 Fault-Tolerant: $L_RESP_TIMEOUTS
$R_RESP_TIMEOUTS
Prefix ‘$L’ corresponds to timeouts on the
while the prefix ‘$R’ corresponds to timeouts
on the FDC280 installed in the right baseplate
slot.
Worst Response Time

This counter contains the highest device response time (in milliseconds) since the FDC280 was
turned online or counter reset. Use this counter to check if the timeout configured for the device
is correct or if the device is not responding within the time expected. Before taking this counter
value, perform the reset counter operation, which resets the previous values and displays the cur-
rent worst response time value, once. Block definition is as follows:
block
PNT_NO * FDC280 Single: $L_WORST_RESP_TIME
FDC280 Fault-Tolerant: $L_WORST_RESP_TIME
$R_WORST_RESP_TIME
while ‘$R’ corresponds to counter value on the
FDC280 installed in the right baseplate slot.
247
Good Messages Sent

The number of good messages sent to a specific device may be monitored. Block definition is as
follows:
block
PNT_NO * FDC280 Single: $L_MSGS_SENT
FDC280 Fault-Tolerant: $L_MSGS_SENT
$R_MSGS_SENT
Good Messages Received

The number of good messages received from a specific device may be monitored. Block definition
is as follows:
block
PNT_NO * FDC280 Single: $L_MSGS_RCVD
FDC280 Fault-Tolerant: $L_MSGS_RCVD
$R_MSGS_RCVD
Modbus Device Exception Responses

The number of Modbus exception responses (0x01-0x08) coming directly from the device. Block
definition is as follows:
block
248
PNT_NO * FDC280 Single: $L_MISC1_ERRS

FDC280 Fault-Tolerant: $L_MISC1_ERRS
$R_MISC1_ERRS
baseplate slot.
Modbus Gateway Exception Responses (Ethernet Only)

The number of Modbus exception responses (0x0A-0x0B) coming from the gateway. Block defi-
nition is as follows:
block
PNT_NO * FDC280 Single: $L_MISC2_ERRS
FDC280 Fault-Tolerant: $L_MISC2_ERRS
$R_MISC2_ERRS
baseplate slot.
NOTE
The Gateway Exception responses are only used with the Modbus TCP/IP driver.
Last Detected Error Message

The exception code and short text description of the last Modbus exception received for a device.
Block Type STRIN Defines the block as a string input block
block
PNT_NO * FDC280 Single: $L_LAST_ERR_MSG
FDC280 Fault-Tolerant: $L_LAST_ERR_MSG
$R_LAST_ERR_MSG
baseplate slot.
249
The following is a list of possible values:

♦ 01 (Illegal Function)
♦ 02 (Illegal Data Address)
♦ 03 (Illegal Data Value)
♦ 04 (Slave Device Failure)
♦ 05 (Acknowledge)
♦ 06 (Slave Device Busy)
♦ 07 (Negative Acknowledge)
♦ 08 (Memory Parity Error)
♦ 0A (Gateway Path Unavailable)
♦ 0B (Gateway Target Device Failed to Respond)
When the counters are reset, this block will display the text “(none)”.
Over Scan Time High

The Over Scan time high diagnostic IIN block will contain the highest Over Scan time (in milli-
seconds) since the FDC280 was turned online or counter reset. The Over Scan time is the time
difference between two successive read commands from a group less the configured scan rate
interval. For example, if the time difference between two successive read commands is 1.2 seconds
and the configured scan rate is 1 second, the counter will display 200 (1.2 seconds -1 second). It
always displays the highest over scan time from all the groups within the device.
Block Type IIN Defines the block as a integer input block
block
PNT_NO * FDC280 Single: $L_OVERSCAN_TIME_HIGH
FDC280 Fault-Tolerant:
$L_OVERSCAN_TIME_HIGH
$R_OVERSCAN_TIME_HIGH
baseplate slot.
Number of Over Scans

The Number of Over Scans diagnostic IIN block will contain the count of Scan Overruns for all
the groups of the concerned device. The counter gets incremented by 1 for each scan overrun. A
scan overrun occurs when the time difference between two successive read commands of a
particular group is not within the configured scan rate interval.
250
Block Type IIN Defines the block as a integer input block

block
PNT_NO * FDC280 Single: $L_OVERSCANS
FDC280 Fault-Tolerant: $L_OVERSCANS
$R_OVERSCANS
baseplate slot.
Configured Options
The Configured Options diagnostic STRIN block will contain the list of options that are in effect
for a particular device. The list of options in effect will be helpful when you have options
configured in multiple locations. Also, if you have configured the same option with different
values in more than one place, this diagnostic block will show which value is actually being used
by the driver.
Block Type STRIN Defines the block as a string input block
block
PNT_NO * FDC280 Single/Fault-Tolerant: $CONFIG_OPTIONS
The string in the diagnostic block displays the device options (DVOPTS) parameter of the
ECB201 block as configured using the Foxboro Evo Control Editors.
Group Scan Time

The Group Scan time diagnostic IIN block will contain the time difference in milliseconds from
the command send time to the reply received time for a particular group. This counter requires
that the device is configured with a device configuration file.
The block definition is as follows:
NAME * Name of the point
TYPE IIN Defines the block as a integer input block
block
PNT_NO * #_SCANTIME
Replace “#” with the Group Name from the device
configuration file.
251
OverScan Condition
When overscans are occurring (without creating the diagnostic block), the Modbus driver notifies
the user that the overscan condition is set when the time difference between two successive read
commands of a particular group is not within the configured scan interval. In this condition, the
device will be marked to a “Failed” state and an message “Overscan Condition - Marking
Device to Warning State” will be displayed in smon_log and the device ECB201’s Equip-
ment Info shows “I/O Overscan” in the device diagnostic status.
252
Appendix A. Major Image Update
and Minor Image Update
This appendix describes the Major and Minor Image Update functions of the FDC280.
Introduction
Overview
This appendix provides a basic overview of the Image Update process, to assist you in determining
how to perform the Major and Minor Image Update operations and the options for the FDC280
in your process control system, as well as informing you of the implications of these operations.
This feature replaces the online upgrade (OLUG) feature provided by the FCP280.
The Major Image Update and Minor Image Update features (see Figure A-1) allow you to update
the software image (operating system) and FDC Driver on the FDC280:
♦ The Major Image Update can only be used to install a new software image when the
plant is NOT running normally (i.e. shut down) as significant disruptions to I/O
communications and control behavior occur. The Major Image Update is for install-
ing changes that cannot be installed with a Minor Image Update, typically new
features.
For non-fault-tolerant FDC280s, only the Major Image Update is supported.
♦ The Minor Image Update can be performed at any time as the only process effect is a
normal failover after the new image is installed in the Shadow module. This update
allows minor changes to be installed with minimal process effects.
When performing a Minor Image Update, ECB201 devices will go into a detected
“System Warning” condition while the update is in progress.
The Major Image Update and Minor Image Update functions are identical for FDC280s in self-
hosting and non-self-hosting modes.
Major and Minor Image Updates for fault-tolerant FDC280s allow you to choose the Image
Update completion mode as either “Manual” or “Auto”. Refer to the “Manual Completion Mode”
and “Auto Completion Mode” descriptions in Table A-1 below for details.
Refer to Figure A-1 for a high-level overview of the Image Update operations for an FDC280.
253
B0700GQ – Rev C Appendix A. Major Image Update and Minor Image Update
System Manager -
provides the following FDC280 update operations:
Simplex (Single) FDC280:

Major Image Update
Fault-Tolerant FDC280:
Major Image Update
Minor Image Update
The Foxboro Evo Control Network
Image Update instructions are delivered to the FDC280

via The Foxboro Evo Control Network.
Fault-Tolerant
FDC280 Pair
with Fiber Adapters
Note that the Image Update operations presented by System Manager depend on how the FDC280 is
configured, not on how it is currently running. So right-clicking in System Manager on an FDC280
configured as fault-tolerant, but currently running with just a single module, will see both Major Image
Update and Minor Image Update presented.
NOTE: Depending on the type of Image Update operation, and other factors, the process itself may
or may not be interrupted by this operation.
Figure A-1. Image Update Overview
Image Update Terms and Concepts

Table A-1 defines the terms and concepts used with the Image Update features.
Table A-1. Image Update Terms and Concepts
Term or Acronym Description

FDC280 Image Update A process for updating the software image and/or FDC
Driver on an FDC280.
Can be either a Major Image Update or Minor Image
Update.
The Major Image Update and Minor Image Update func-
tions are identical for FDC280s in self-hosting and non-self-
hosting modes.
See the “Major Image Update” and “Minor Image Update”
descriptions below for more details.
254
Appendix A. Major Image Update and Minor Image Update B0700GQ – Rev C
Table A-1. Image Update Terms and Concepts (Continued)

Major Image Update Applies to single and fault-tolerant FDC280s.
An Image Update during which the FDC280 is taken offline
and updated with the new image. This will cause an inter-
ruption to plant processing, and should only be performed
during downtime. It typically provides new features. It uses a
“cold start”.
A Major Image Update has the exact same effect as a reboot
from checkpoint operation. Block state is not preserved dur-
ing this update.
Refer to “Process Control Considerations” on page 261 for
more detail.
Minor Image Update Only applies to fault-tolerant FDC280 modules.
The FDC280 only needs to be configured fault-tolerant to
allow Minor Image Update request, but must be married for
the request to actually perform a Minor Image Update (refer
to “Minor Image Update for Married Stations” on page 266):
♦ This is an Image Update during which each FDC280 in
a fault-tolerant pair is taken offline separately and
updated with the new image. It typically resolves
detected errors and has the same effect on the process as
a failover.
Refer to “Minor Image Update For Unmarried Stations” on
page 268 for actions taken when a Minor Image Update is
requested for unmarried stations.
Image Update Completion Mode Only applies to fault-tolerant FDC280s.
The choice of how the Image Update is to be completed,
either user-controlled (“Manual”) or automatically (“Auto”).
Refer to the “Manual Completion Mode” and “Auto Com-
pletion Mode” descriptions below for more details.
255

Manual Completion Mode Only applies to fault-tolerant FDC280s.
Requires user intervention before the Image Update process
can be completed.
For a Major Image Update, “Manual” mode allows the oper-
ator to control the operational flow of the new image and
decide to go forward with the new image or “Backout” to the
previous image. Refer to the “Backout” facility description
below for more details.
For a Minor Image Update, with “Manual” mode, the Image
Update process completes on the Shadow FDC280 automat-
ically, and the operator must reboot the Primary FDC280 to
complete the overall update. Refer to the example SMON
messages below informing you of the need for a reboot to
complete the update, including indication of a detected
Warning condition, and to Figure A-2 on page 258 which
shows indications in System Manager (including the Image
Revision Mismatch field having a value of “Yes” and a
detected Warning icon adjacent to the FDC280 object on
the left-hand side).
UPDATE RDHSS 000131 - Reboot Primary when
directed
o o o
SYSMON -00133 Warning Error Condition Exists
SYSMON -00268 Primary & Shadow image version
mismatch
o o o
UPDATE RDHSS 000131 - Shadow Ready for Take-
over
UPDATE RDHSS 000131 - Reboot Primary to com-
plete installation
Refer to “Determining Whether to Use Manual or Auto
Mode for Image Update” on page 260 for more details.
Auto Completion Mode Only applies to fault-tolerant FDC280s.
For a Major Image Update, “Auto” mode enables the update
to complete automatically with the end result of both
FDC280s running fault-tolerant with the new image.
For a Minor Image Update, “Auto” mode enables the Image
Update process to complete automatically by rebooting the
FDC280 running the older image and performing a failover
to the FDC280 running the new image, with the end result
of both FDC280s running fault-tolerant with the new
image.
Refer to “Determining Whether to Use Manual or Auto
Mode for Image Update” on page 260 for more details.
256

“Backout” facility During a Major Image Update with the “Manual” comple-
tion mode selected, you can choose to “back out” the new
image and revert to the old image. Refer to the description of
“Manual Completion Mode” (in this table) above for details.
The following example SMON messages inform you of your
choice:
Update RDHSS 000131 - IMG Loaded - reboot
Shadow to accept new image
Update RDHSS 000131 - or reboot Primary to go
back to old image
OLUG Online Upgrade, which refers to a legacy method of updat-
ing a control processor's software, which is not supported by
the FDC280.
FDC280 Image Revision In the System Manager, the following format is applicable to,
for a non-fault-tolerant FDC280, the “Primary Core 1
Image Revision” field and, for a fault-tolerant FDC280, the
“Primary Core 1 Image Revision” and “Shadow Core 1
Image Revision” fields:
MMmmXXXyyy
Where:
♦ MM = Major product version (corresponds with Con-
trol Core Services Major Product Version)
♦ mm = Minor product version (new feature or breaking
change; consult the release notes shipped with your ver-
sion of Control Core Services)
♦ XXX = Major FDC280 image revision
♦ yyy = Minor FDC280 image revision (aka “build num-
ber”)
For example, for image revision “0903001002”:
♦ “0903” indicates major/minor system revision 9.3
♦ “001” is the major FDC280 image revision
♦ “002” is the minor FDC280 image revision
Refer to Figure A-2 on page 258 for the System Manager dis-
play of the FDC280 image revision field.
Primary Core 2 Image Revision This field shows Core 2 common component version for the
Primary FDC280. It is in the format xxxxxx.
See Figure A-2 on page 258.
The Core 2 image has two components: the common com-
ponent and the protocol driver. The driver component ver-
sion is displayed in the ECB200 in the Driver field.
257

Shadow Core 2 Image Revision This field shows Core 2 common component version for the
Shadow FDC280. It is in the format xxxxxx.
See Figure A-2 on page 258.
The Core 2 image has two components: the common com-
ponent and the protocol driver. The driver component ver-
sion is displayed in the ECB200 in the Driver field.
Image Revision Mismatch To assist in determining if a Manual Minor Image Update is
completed for fault-tolerant FDC280s, the Equipment
Information section in the System Manager for the FDC280
contains the “Image Revision Mismatch” field. If this field is
set to “Yes”, this indicates the image revisions for Primary
and Shadow FDC280s differ, and you need to complete the
Manual Minor Image Update by rebooting the Primary
FDC280, allowing the Shadow FDC280 with the new image
to take over.
Refer to Figure A-2 below.
Figure A-2. Image Revision and Image Revision Mismatch Fields in System Manager
258
Determining Whether a Major or Minor Image

Update Is Needed
Figure A-3 and Table A-2 assist in helping you to determine whether a Major or Minor Image
Update is required to update the image of your FDC280s.
Refer to the “FDC280 Image Revision” in the

“Image Update Terms and Concepts” table
above for the format of the revision.
Do the first seven digits

No
of the new Revision match
the first seven digits of the
previous Revision?
If all ten digits of the new and old revisions match

and an Image Update is attempted, refer to the
Yes section “If Image Update Attempted WIth Same
Image” in this Appendix below.
Simplex FDC280 is Simplex Fault-Tolerant

or Fault-Tolerant?
Must use a Major Image Update. Must use a Minor Image Update.
Figure A-3. Determining Whether a Major or Minor Image Update Is Needed
Table A-2. Example Major and Minor Update Scenarios
Note: Digits which differ between revisions are in bold red.

If the previous And the new Revision Then the following is
Revision is: is: And the FDC280 is: needed:
0903001002 0903001002 n/a None1
0903001002 0903001003 Single Major Image Update
0903001002 0903001003 Fault-tolerant Minor Image Update
0903001002 0903002001 Fault-tolerant Major Image Update
259
1. If any Image Update is attempted when the previous and new revisions match, it will be ignored
once the update sees that the previous and new revisions match. Refer to “If Image Update
Attempted With Same Image” on page 272 for further details.
Determining Whether to Use Manual or Auto Mode

for Image Update
Table A-3 assists you in determining whether to perform your Image Update feature using either
Manual or Auto mode.
Table A-3. Determine Whether to Use Manual or Auto Mode for Image Update
Module
Configuration Image Update Type Use Mode Reason for Choosing This Mode
Single n/a n/a for simplex Does not apply to simplex FDC280s
FDC280s
Fault Tolerant Major Image Update Manual You want to verify the operation of the
new image before deciding to either:
♦ Go forward and complete the
Image Update to the new image or
♦ Back out the new image and revert
to the old image.
Auto You do not need to verify the operation
of the new image before it gets loaded
into the Shadow FDC280 of the fault-
tolerant pair; that is, you prefer to allow
the Image Update to automatically
complete.
Fault Tolerant Minor Image Update Manual Although you cannot verify the opera-
tion of the new image before the update
completes (as you can for a Manual
Major Image Update), you can control
when the update completes and the
new image takes over control. This can
be useful if you have a very short time
window in which to complete the
Image Update, and need the new image
to be written into the Shadow FDC280
while the Primary FDC280 is still con-
trolling the process.
Auto You do not need to control when the
update completes and the new image
takes over control; that is, you prefer to
allow the Image Update to automati-
cally complete.
260
Process Control Considerations

Minor Image Update for Married Stations
A Minor Image Update for married stations has the same effect as a fault-tolerant failover, mean-
ing control is paused for up to 500 milliseconds. Additionally, I/O updates are paused for up to
two seconds.
Major Image Update or Minor Image Update for Unmarried

Stations
WARNING
Do not under any circumstance use the Major Image Update option or
Minor Image Update option for an unmarried FDC280 to update an
image in a running plant, as this could result in the loss of control of
your process and I/O operations for a considerable period of time.

injury.
A Major Image Update or a Minor Image Update for an unmarried FDC280 has the same control
effect as a full reboot of the Single Primary module or, if fault-tolerant, of the two FDC280s in
the fault-tolerant pair. Control may be unavailable for several minutes.
The remainder of this subsection explains various process control considerations relevant to
resuming control of the process following a Major Image Update or a Minor Image Update for an
unmarried FDC280.
General Block Processing Considerations

As the FDC280 that previously had the Shadow role assumes control (i.e. becomes the Primary),
the data values in the Shadow database file being used do not reflect the current process/plant
conditions. It reflects the process as it existed some number of seconds ago. The checkpoint data is
considered “stale”. This may have significant implications for a given process/plant.
As control is being assumed with the new FDC280 image, all the blocks in that FDC280 are ini-
tialized, with no exceptions. While many of the blocks used by the FDC280 can, with proper
configuration, initialize without introducing a process “bump”, others cannot.
As control is being assumed, the I/O values are not available and any control strategies tied to I/O
state view the values as in OOS or BAD states.
Stale Data
The impact of stale data is a function of a given control processor block type and its application.
For example, the impact of rolling back in time for a Sequence block is likely to affect the exe-
cuted sequence and the point in time when the sequence was interrupted.
261
The influence of stale data may or may not have an impact on the Arithmetic block family with
the majority of the dependence on the application of the given block. For this block family,
remember that the blocks’ stack is nulled upon block initialization.
The impact of stale data with respect to continuous control (e.g., PIDA) should be indistinguish-
able with the provision that care is taken that control loop initialization is treated properly.
Compound and Block Initialization

Compounds initialize according to the state configured in the INITON parameter.
Continuous control blocks initialize according to the states configured in the INITMA and
INITLR parameters. Typically the blocks are set to initialize in Auto. They use the last I/O values
read before the Image Update command but then will see a transition to the BAD/OOS state.
Block initialization has a large effect on Sequence blocks. Sequence blocks will re-initialize during
a Major Image Update or a Minor Image Update for an unmarried FDC280 operation.
The antithesis of this is a PIDA block acting as the primary to a ROUT block secondary. With
appropriate configuration, a control loop can survive an update with the control effect being that
the process I/O becomes unavailable between seconds to a couple minutes.
DCI blocks initialize according to the states configured in INITMA. The DCI output blocks ini-
tialize using the failsafe values, whereas the continuous output blocks initialize using the BAD or
OOS status until I/O communications are re-established.
Sequence control blocks initialize according to the states configured in the RSTMA and RSTACT
parameters. This clears internal variable values and restarts sequence code execution at the first
statement.
Peer-to-Peer Block Initialization

For a Major Image Update or a Minor Image Update for an unmarried FDC280, all blocks ini-
tialize in the updated FDC280 and peer-to-peer Object Manager connections are re-established.
During a Major Image Update of an FDC280 or a Minor Image Update for an unmarried
FDC280, the re-establishment of connections also affects the station at the other end of the
FDC280:
♦ System management displays (such as FoxView or Control HMI) showing data from
the updating FDC280 temporarily show live data values in cyan color (out-of-ser-
vice), then return to normal.
♦ Applications such as the Historian experience a temporary loss of data.
♦ Peer-to-peer connections with other control processors should be evaluated for the
impact that the temporary loss of communications with the updating FDC280 may
have on the remote process.
♦ Peer-to-peer connections may be restored with the I/O values still in the OOS/BAD
state until communications with I/O devices are restored.
Also refer to “FDC280’s OM Scanner” on page 236.
Prior to updating stations with peer-to-peer cascade loops, you should open the loops by switch-
ing the secondary blocks to the Local mode. After the update has been completed for both control
stations (in case of a fault-tolerant pair), you should close the cascade loops by switching the sec-
ondary blocks back to the Remote mode.
262
Reconnecting all peer-to-peers between the FDC280s can take a long period of time depending
on scan time and other factors. Therefore, special failsafe or shutdown logic configurations that
use these connections might need to be bypassed or disconnected until this process is finalized.
After the completion of a Major Image Update or a Minor Image Update for an unmarried
FDC280, if the FDC280 has peer-to-peer connections, the variable “Points Not Found” on the
station page <COMPOUND>_STA:STATION may not indicate the correct total of points
not found. The variable “Points Not Found” is updated during initialization and may be updated
again within approximately 60 seconds. Some points may resolve after the initial update is made,
causing a “Points Not Found” reading that is higher than the actual. This reading is corrected
with the second update.
Additional Process Control Considerations Due to New FDC280

Image
During the Image Update procedure, a transition from running with the existing FDC280 image
to the new FDC280 image occurs. Therefore, it is recommended that you review the following
documentation, as appropriate, for the new software image to determine if there are software
changes that may impact control operation:
♦ Control Core Services Release Notes and Installation Procedures (supplied with new
Control Core Services software)
♦ Quick Fix Installation Notes.
Performing an FDC280 Image Update

For all FDC280 Image Update operations described in this section, it is assumed that you have
updated the FDC280 host workstation's d:\usr\fox\sp\files\OS3I80 file with the new operating
system image.
The FDC280 offers two options for updating the FDC280’s image or the FDC280 driver:
♦ Major Image Update
♦ Minor Image Update
For a non-fault-tolerant FDC280, the Minor Image Update feature is not supported
and is not shown.
These options are accessed via a right mouse click on the FDC280 icon in the System Manager.
This opens the menu showed in Figure A-4, which shows the two image update options.
263
Figure A-4. System Manager Equipment Change Display
These options are detailed in subsequent sections.
NOTICE
Only designated personnel who are aware of the effects of making

equipment changes should initiate equipment change actions.

damage.
For a Major Image Update, refer to “Process Control Considerations” on page 261 for a descrip-
tion of the effects on process control that these procedures have.
WARNING
POTENTIAL DEATH OF SERIOUS INJURY
If performing a Major Image Update, when a step in this section asks

you to reboot a Primary or Shadow module, you have to use System
Manager to perform this action. Rebooting a module via a hardware
reset, with either a warm or cold start, can have adverse affects,
including the loss of control of your process and/or moving to an
unintended image revision.

injury.
264
NOTICE
POTENTIAL DATA LOSS
If performing a Minor Image Update, when a step in this section asks

you to reboot a Primary or Shadow module, you have to use System
Manager to perform this action. Rebooting a module via a hardware
reset, with either a warm or cold start, can have adverse affects,
including an additional period of being “off control” and moving to an
unintended image revision.
If you attempt an Image Update before a prior reboot or Major Image Update is completely fin-
ished (that is, when a “DATABASE DOWNLOAD COMPLETE” SMON message is logged),
you will see the following SMON message logged, and the Image Update request will be ignored:
“Station not yet ready for image operations”.
Updating a Non-Fault-Tolerant FDC280

The following section describes the System Manager procedures you must perform to update the
image in a non-fault-tolerant FDC280, and the sequence of system events required for the
update.
Major Image Update for Non-Fault-Tolerant FDC280
WARNING
Do not under any circumstance use the Major Image Update option to
update an image in a running plant, as this could result in the loss of
control of your process and I/O operations for a considerable period of
time.
Refer to “Process Control Considerations” on page 261 for additional

information.

injury.
In the System Manager, the Major Image Update command updates the image (operating sys-
tem software) in the flash memory of the selected FDC280 with a new image, and/or the
FDC280 driver. The update request downloads the image file (OS3I80) from its host, and writes
it to the FDC280's flash memory. Immediately after it completes, the FDC280 will reboot from
it.
To perform a Major Image Update for a non-fault-tolerant FDC280, proceed as follows:
265
1. Select the icon for the FDC280 in the Navigation Pane, described in System Manager
(B0750AP).
2. Right-click the FDC280 and click Checkpoint.... This helps ensure that all
changes to the FDC280 are recorded in the host server.
Alternatively you can select the FDC280, select the Actions menu from the top
menu bar, hover the mouse over Equipment Change when it appears, and click
Checkpoint.... (You can invoke the actions in the following steps using this alter-
nate method as well.)
3. Verify that the download is currently enabled. If it is not, right-click the FDC280 and
click Enable Download.
To confirm that download is currently enabled, verify that the Equipment Change
submenu lists Disable Download as one of its picks.
4. Right-click the FDC280 and click Major Image Update.
5. The Major Image Update confirmation dialog box appears. Click OK to confirm the
update.
6. The FDC280 downloads the image from the host, and messages are sent to the Sys-
tem Monitor log (smon_log) and printer to indicate progress.
7. After the image is downloaded from the host and written to its flash memory, the
module reboots from the newly installed OS file.
8. The image update is complete. The total elapsed time for the update process is several
minutes. Depending on the mix of protocol devices (such as Modbus) connected to
the FDC280, the time for the recovery of the FDC280 and all of its connected field
devices varies between less than a minute to several minutes.
9. To verify the new image revision levels, use the Equipment Information display in the
System Manager to view the updated image version in the “Primary Core 1 Image
Revision” and “Primary Core 2 Image Revision” fields.
Updating a Fault-Tolerant FDC280

Refer to “Determining Whether a Major or Minor Image Update Is Needed” on page 259 to
determine which image update operation is required, based on the current and new revisions.
Then refer to the appropriate section below.
Minor Image Update for Married Stations

This section describes the System Manager procedures to perform a Minor Image Update of a
fault-tolerant FDC280 whose modules are currently married, and the sequence of system events
required for the update.
A Minor Image Update for a married fault-tolerant FDC280 has the same effect as a fault-tolerant
failover, meaning control is paused for up to 500 milliseconds. Additionally, I/O updates are
paused for up to two seconds.
Refer to “Determining Whether to Use Manual or Auto Mode for Image Update” on page 260 to
determine whether to choose “Auto” or “Manual” mode.
To perform a Minor Image Update for a married fault-tolerant FDC280, proceed as follows:
(B0750AP).
266
2. Right-click the FDC280 and click Checkpoint. This helps ensure that all changes to
the station are recorded in the host server.
3. Verify that the download is enabled. If it is not, right-click the FDC280 and click
Enable Download.
To enable the download, verify that when you right-click the FDC280, that Disable
Download is one of its picks.
4. Right-click the FDC280 and click Minor Image Update.
5. The Minor Image Update dialog box appears. Select the desired start option (Manual
or Auto), and click OK. (These are discussed in “Determining Whether to Use Manual
or Auto Mode for Image Update” on page 260.)
Figure A-5. Minor Image Update Dialog Box
The Minor Image Update performs the following:

♦ The Shadow FDC280 is placed offline, updated to its new image, and rebooted.
♦ If comparison of the current and new FDC280 revisions indicate that a Major Image
Update is needed; that is, any of the first seven digits of the version string differ, the
Minor Image Update is aborted and the following messages are sent to the SMON
log.
Update Rejected Image Versions not compatible with Minor Update
Update Rejected A Major update must be Performed to switch to
this image
Update Rejected Restoring Married operation running the existing
image
The station reverts to the image in the Primary module, fault-tolerant operation
resumes, and the update process stops ! .
♦ The Primary FDC280 switches to Single mode (instead of Fault-Tolerant).
♦ The new image is written to the Shadow FDC280. The Shadow FDC280 reboots and
performs verification that the version indicates a Minor Image Update. If it is not a
Minor Image Update, it is rejected and a message is sent to the System Manager that
267
the update could not be performed. (If rejected, the modules will return to married
operation running the old image.)
♦ If verified successfully, the Primary FDC280 and Shadow FDC280 marry normally.
♦ The FDC280 running the new image performs initialization for its Core 2 CPU.
When the initialization is complete, a message is sent indicating “Shadow ready for
takeover”.
♦ The Primary FDC280 and Shadow FDC280 then operate in the same manner as any
other marriage scenario with the Shadow FDC280 going through an “education” pro-
cess where it configures and reforms all connections to the I/O while the Primary
FDC280 maintains control.
♦ The System Manager log displays a message that the FDC280 modules are ready for
image activation. (Also an indication in the Device Driver ECB of a Minor Image
Update in progress is displayed in the same log.)
♦ If the “Auto” mode is selected, the image update completes automatically by rebooting
the module running the older image and performing a failover to the module running
the new image.
As soon as the update of the module running the older image is complete (up to five
minutes), the module running the new image reboots. System Manager expects the
module running the new image to be running online, so when it goes offline, System
Manager treats this as an error detected in the Primary module and a Shadow module
failover. This causes System Manager to detect a suboptimal condition; however, it
correctly shows the module running the older image as running Single Primary mode.
When the module finishes the update and marries, all these detected errors are cleared
and resolved.
♦ If the “Manual” mode is selected, the operator may now initiate a switch to the new
image with a standard “Reboot Primary” command from the System Manager.
Rebooting the Primary FDC280 results in the Shadow FDC280 assuming control
with the new Minor image behavior. The module with the old image reboots, copies
the new Minor version of software, and then marries normally.
The Primary FDC280 reboots in the same manner as it would for a failover, while the Shadow
FDC280 takes over from the current control state.
The total process should complete in less than two minutes after the remarriage operation.
There is NO difference in process effects from a Minor Image Update to a “normal” failover
sequence (where the Shadow module becomes the Primary due to operator command or detected
errors in the hardware).
A Minor Image Update can be reversed by simply re-installing the previous image and performing
another Minor Image Update.
Minor Image Update For Unmarried Stations

Typically, an FDC280 module configured for fault-tolerant operation would have a pair of mar-
ried modules running at the time of a Minor Image Update. If for whatever reason, the FDC280
does not have a pair of married modules running, a Minor Image Update can still be requested.
However, it will have the effect of a Major Image Update.
268
WARNING
Do not under any circumstance use the Minor Image Update option,
for a fault-tolerant FDC280 without a pair of married modules to
time.

information.

injury.
Refer to “Minor Image Update for Married Stations” on page 266 for steps to initiate the request.
The update progresses to completion automatically.
Major Image Update for a Fault-Tolerant FDC280
WARNING
Do not under any circumstance use the Major Image Update option to
time.

information.

injury.
This section describes the System Management procedures to perform a Major Image Update of a
fault-tolerant FDC280 station, and the sequence of system events required for the update.
Refer to “Determining Whether to Use Manual or Auto Mode for Image Update” on page 260 to
decide whether to choose “Auto” or “Manual” mode.
To perform a Major Image Update for a fault-tolerant FDC280, proceed as follows:
(B0750AP).
2. Right-click the FDC280 and click Checkpoint.... This helps ensure that all
changes to the station are recorded in the host server.
269
3. Verify that download is enabled. If it is not, right-click the FDC280 and click Enable
Download.
To enable the download, verify that the Equipment Change submenu lists Disable
Download as one of its picks.
4. Right-click the FDC280 and click Major Image Update.
5. The Major Image Update dialog box appears. Select the desired start option (Manual
or Auto), and click OK. (These are discussed in “Determining Whether to Use Manual
or Auto Mode for Image Update” on page 260.)
Figure A-6. Major Image Update Dialog Box
6. If the comparison of the current and new FDC280 revisions indicate that a Minor
Image Update is needed; that is, all of the first seven digits of the version string are the
same, the Major Image Update is aborted and the following messages are sent to the
SMON log
Update Rejected Images are compatible with a Minor Update option
Update Rejected For minimal process effects perform Minor Update
image
The station reverts to the original image, fault-tolerant operation resumes, and the
update process stops ! .
7. If the “Manual” option is selected, the Major Image Update options are presented in
the SMON log (smon_log) as the backout option.
Update RDHSS 000131 - IMG Loaded - reboot Shadow to accept new
image
Update RDHSS 000131 - or reboot Primary to go back to old image
If the “Auto” option is selected, the update process completes with both modules run-
ning the new image by rebooting the module with the older image and updating it to
the new software revision.
Select Reboot... as shown in Figure A-4 and choose the desired module to reboot:
270
♦ Primary to revert back to the old image.

♦ Shadow to accept the new image.
The update process runs to completion with no further operator intervention.
If the “Auto” option is selected, the update process completes with both modules run-
ning the new image by automatically rebooting the module with the older image and
updating it to the new software revision.
For reference, the sequence of system events for a Major Image Update with operator intervention
and backout options follows:
1. The host is updated with the appropriate operating system image (OS3I80 for
FDC280).
2. In System Manager, the operator selects Major Image Update.
3. The Major Image Update dialog box appears. Select Manual to choose operator inter-
vention, and click OK.
4. When the command is received, the Primary FDC280 downloads the OS image from
its host.
5. The Primary FDC280 places the Shadow FDC280 offline.
6. The Shadow FDC280 is updated to its new image and reboots.
7. When the Primary FDC280 detects that the Shadow FDC280 has rebooted, their
images are compared to determine if a Minor Image Update (see “Determining
Whether a Major or Minor Image Update Is Needed” on page 259) is all that is
needed.
8. If a Major Image Update is not needed, the update is rejected and the following mes-
sages saying that a Minor Image Update may be performed instead are sent to the
SMON log.
Update Rejected Images are compatible with a Minor Update option
Update Rejected For minimal process effects perform Minor Update
image
(The Shadow FDC280 reboots and marries the Primary normally, running the old
image.) !
9. If a Major Image Update is required, it performs a checkpoint operation to the
FDC280’s Flash memory with no pause in its control functions.
10. When the checkpoint operation is complete, the FDC280’s control operations pause
for approximately 300 milliseconds while the Primary FDC280 copies the checkpoint
file to Core 1 of the Shadow FDC280.
11. Control continues on the Primary FDC280 while Core 1 of the Shadow FDC280
installs the database that it received. This may take from 0.5 to 15 (or more) seconds.
12. The Shadow FDC280 assumes control and performs a start-up operation with the
checkpoint information it received. This takes two Block Processing Cycles (BPCs)
before the control outputs are applied to the field.
13. The I/O connectivity to the Modbus devices is lost after the Shadow FDC280
assumes control until the Shadow FDC280 reforms the connections to the I/O. This
271
may take from a few seconds to several minutes depending on the number of I/O
devices.
14. At this point, the operator can evaluate the process, and perform one of the following
steps manually:
♦ If the operator is satisfied with the behavior of the FDC280 running the new
image, they must reboot the Shadow FDC280 using System Management dis-
plays. This will complete the update process by implementing the new image in
the module pair and returning them to fault-tolerant operation.
♦ If the operator does not want to continue running with the new software image,
they must reboot the Primary FDC280 using System Management displays.
This invokes the back out process, which is basically a “reverse Major Image
Update” operation; when the Shadow FDC280 comes back online from the
reboot, a checkpoint operation is performed by the Primary FDC280 and sent to
the Shadow FDC280. The Shadow FDC280 installs the checkpoint file and then
assumes control.
The end result is that the FDC280s resume fault-tolerant operation running the
old software image.
Be aware that when choosing this option, the image in the host workstation needs
to be reverted to this older version as well, for consistency.
15. The update is complete. The total elapsed time for the Major Image Update process is
several minutes, plus the decision time to commit to the new image. Control offline
time is approximately a few seconds to a few minutes for the FDC280 (with an addi-
tional few seconds to a few minutes to go back to the old image, if you are unsatisfied
with new image). Peer-to-peer communication maximum downtime is approximately
30 seconds (depending on the number of OM connections).
If Image Update Attempted With Same Image

If you attempt an Image Update with the same image revision, the Image Update will copy that
“new” image in, see that it is the same as the “old” image, and ignore it.
Refer to the messages below for an example sequence of SMON messages for such an Image
Update of a fault-tolerant station. The example is for a Manual Major Image Update of fault-tol-
erant FDC280, but the messages would be similar for other fault-tolerant Image Updates (only
the “SysMgr” message would be different).
2016-09-01 09:20:04 FDC903 Fault Tolerant Exec SM_MSG -00046 Fault Toler-
ant Modules Now Married
2016-09-01 09:20:04 FDC903 Process = Flash Loader RDHSS 000131 - Image
update ignored due to duplicated image loaded
2016-09-01 09:19:32 FDC903 Process = Flash Loader RDHSS 000131 - Load 50
pct
2016-09-01 09:19:17 FDC903 Process = Flash Loader RDHSS 000131 - FLASH
Update Started
2016-09-01 09:19:16 FDC903 Station SYSMON -00048 Equipment updating EEPROM
2016-09-01 09:19:16 FDC903 Process = SysMgr Service SYSMGR -00126 Manual
Major Image Update
272
Refer to the messages below for an example sequence of SMON messages for such an Image
Update of a simplex (single) station.
2016-09-08 17:31:12 T73PFD Equip = DRV001/DEV001 SYSMON -00051 Equipment
has been added on-line
2016-09-08 17:31:12 T73PFD Equip = DRV001 SYSMON -00051 Equipment has been
added on-line
2016-09-08 17:31:12 T73PFD Equip = ENETP1 SYSMON -00051 Equipment has been
added on-line
2016-09-08 17:31:12 T73PFD Station SYSMON -00041 Equipment on-line
2016-09-08 17:30:50 T73PFD Station SYSMON -00043 Equipment failed
2016-09-08 17:30:50 T73PFD Fault Tolerant Exec SM_MSG -00040 Write to
EEPROM failed. ROM Addr = 000000000000
2016-09-08 17:30:50 T73PFD Process = Flash Loader RDHSS 000131 - Image
update ignored due to duplicated image loaded
2016-09-08 17:30:17 T73PFD Process = Flash Loader RDHSS 000131 - Load 50
pct
2016-09-08 17:30:02 T73PFD Process = Flash Loader RDHSS 000131 - FLASH
Update Started
2016-09-08 17:30:02 T73PFD Station SYSMON -00048 Equipment updating EEPROM
2016-09-08 17:30:01 T73PFD Process = SysMgr Service SYSMGR -00127 Auto
Major Image Update
NOTE
Be aware that the “Write to EEPROM failed. ROM Addr = 000000000000”
SMON message reflects implementation needed so the System Monitor can allow
an internal retry after correcting the temporary duplicate image issue.
273
274
Appendix B. Improving
Performance of the CCS FDC280
Configurator on Stations with
Enterprise Edition Control Core
Services v9.3 or Later
This appendix describes how to add new Group policies to the PDC on the network to improve
performance of the CCS FDC280 Configurator on stations with Enterprise Edition Control
Core Services v9.3-9.4.
For running the CCS FDC280 Configurator on stations with Enterprise Edition Control Core
Services v9.3-9.4, add new Group policies to the PDC on the network as described in this
appendix.
1. Log on to the PDC using domain administrator credentials (such as
iadomainadmin).
2. Click the Start button, and then select Windows Administrative Tools ->
Group Policy Management.
275
B0700GQ – Rev C Appendix B. Improving Performance of the CCS FDC280
Figure B-1. Accessing Group Policy Management Application
The Group Policy Management console opens.

3. In the left pane of the console, expand the tree nodes:
Forest: <domain name> -> Domains -> <domain name> -> Group Policy
Objects
276
Appendix B. Improving Performance of the CCS FDC280 Configurator on Stations with Enterprise Edition Control Core
Figure B-2. Group Policy Management - Accessing Group Policy Objects
4. Right-click on the GPO titled “Invensys IA Computers v2.0” and in the menu that
appears, click Edit.
Figure B-3. Group Policy Management - Accessing Invensys IA Computers v2.0 - Edit...
The Group Policy Management Editor opens.

5. In the left tree pane of the Editor, expand the nodes:
Computer Configuration -> Policies -> Windows Settings -> Security
Settings
Then select the node Public Key Policies.
277
Figure B-4. Group Policy Management - Accessing Public Key Policies
6. In the right pane, the setting Certificate Path Validation Settings appears.
Double-click it to edit it.
Figure B-5. Group Policy Management - Accessing Certificate Path Validation Settings
278
Appendix B. Improving Performance of the CCS FDC280 Configurator on Stations with Enterprise Edition Control Core
7. In the Certificate Path Validation Settings Properties dialog box that opens, click the
Network Retrieval tab.
Figure B-6. Certificate Path Validation Settings Properties - Network Retrieval Tab
8. Change the values of the following settings to 1:

a. In the “Default URL retrieval timeout (in seconds):” field, change the value to
“1”.
b. In the “Default path validation cumulative retrieval timeout (in seconds):” field,
change the value to “1”.
Figure B-7. Certificate Path Validation Settings Properties - Default Retrieval Timeout Settings
9. Click OK to close the dialog box.

10. Close the Group Policy Management Editor dialog box.
11. On the clients running CCS FDC280 Configurator, perform the following steps
a. Log on to the client using an administrator credentials (such as IAInstaller)
b. Open a command prompt (cmd.exe) in Administrator mode.
c. Run the command: gpupdate /force
d. Wait for the command to complete.
In most cases, performance of the CCS FDC280 Configurator is improved.
279
280
Appendix C. Upgrading / Usage
with FDC280 Released 090009000
Image
This appendix describes how to add a partner FDC280 with the previously-released
090009000 image.
Notice for Configurations with Single-Ported Serial

Devices
NOTICE
POTENTIAL DATA LOSS
Single-ported Serial communications can be temporarily compromised

when plugging in a partner FDC280 that has the previously-released
090009000 image. To avoid disruption of the single-ported Serial
communications, perform the following procedure:
1. Unplug the termination assembly cable from the FDC280’s

baseplate (that corresponds to the side of the partner FDC280 module
to be plugged in).
2. Plug in new partner FDC280 that has the 0900009000 image.
3. After the new Shadow FDC280 completes updating and is married,

then re-plug its termination assembly cable.
To avoid having to do this, it is recommended that you update your

entire inventory of FDC280 modules to image version 0900010000, or
later.
281
B0700GQ – Rev C Appendix C. Upgrading / Usage with FDC280 Released 090009000 Image
282
Appendix D. FDC280 Debug Driver
and FDC280 I/O Diagnostic Tool
This appendix describes how to configure the FDC280 debug driver and FDC280 I/O
Diagnostic Tool.
The FDC280 debug driver and FDC280 I/O Diagnostic Tool are software components that assist
in diagnosing any suboptimal conditions in communications between the FDC280 and any of
the connected devices. While earlier methods of diagnosis relied to capturing information via
hardware interrupts, these software components no longer use these methods. The FDC280
debug driver captures all inter-FDC280-device communications and relays this information over
a Local Access Network (LAN). The FDC280 I/O Diagnostic Tool presents this information to
the user in a proprietary GUI. No third-party hardware is required for this communication diag-
nosis.
Only one instance of the debug driver can be deployed at a given time.
283
B0700GQ – Rev C Appendix D. FDC280 Debug Driver and FDC280 I/O Diagnostic Tool
Figure D-1. FDC280 Debug Driver and FDC280 I/O Diagnostic Tool
First, you have to configure the FDC280 debug driver either via the Control Software or ICC.
284
Appendix D. FDC280 Debug Driver and FDC280 I/O Diagnostic Tool B0700GQ – Rev C
Configuring the FDC280 Debug Driver via Control

Software
Proceed as follows:
1. Start the Control Software. In the Network view, select the Ethernet Port under which
you want to create a driver. Right-click the Ethernet Port, and select New Driver….
Figure D-2. FDC280 Debug Driver - New Driver... Menu Item
285
2. In the Bulk Create dialog box, select the Diagnostic Driver option checkbox and click
OK.
Figure D-3. FDC280 Debug Driver - Bulk Create Dialog
286
The driver will be created and shown in the Network view.
Figure D-4. FDC280 Debug Driver - Diagnostic Driver in Network view
287
3. Right-click the driver and select Open Related ECB....
Figure D-5. FDC280 Debug Driver - Related ECB… Menu Item
288
4. Configure the driver’s ECB200, and save the configuration.
Figure D-6. FDC280 Debug Driver - Driver Editor
Set CPARM1, CPARM2, and CPARM3 next. CPARM1 and CPARM2 represent
where the information from each FDC280 will be sent for capture. CPARM1 is the
left module, and CPARM2 is the right module. Configure the IP address of the sta-
tion running the FDC280 I/O Diagnostic Tool, and the port on which the tool will
be receiving the diagnostics data. For example (CPARM1 192.168.100.90:7001)
would configure the left FDC280 module to send its data to the station at IP
192.168.100.90 on the port 7001. The port number for the two modules has to be
different. For example
(CPARM2 192.168.100.90:7002) - this setting allows data from both modules to be
captured using multiple instances of the tool. Finally, configure CPARM3 to contain
the name of the device from which you wish to capture information, as well as the rate
(in seconds) of which the device diagnostic counter information updates have to be
sent. For example, (CPARM3 S1001:10) would configure the Log Driver to capture
Device S1001’s data and send its diagnostic information updates every 10 seconds. By
default, the Log Driver runs for 10 minutes so as to not cause any overhead for
extended periods of time. However, this can be changed by editing CPARM3, such as
(CPARM3 S1001:10+LTO=100). This configures the same options as before, but the
289
Log Time Out time is set to 100 minutes instead of 10. If you want the Log Driver to
run forever, configure the LTO to be 0. The remaining Definitions may be left as
default configurations.
5. Rick-click the station’s ECB Compound and select Deploy….
Figure D-7. FDC280 Debug Driver - Deploy Menu Item
290
6. In the Select Objects for Deployment (Step 1 of 4) dialog box, click driver’s ECB200
block, click Finish>> to deploy the ECB200 block to the FDC280 station.
Figure D-8. Select Objects for Deployment (Step 1 of 4) Dialog Box
291
7. Open the System Manager. Select the driver you just configured and right-click on it.
Select Go On-Line….
Figure D-9. System Manager - Put the Driver You Configured On-Line
Now proceed to “FDC280 I/O Diagnostic Tool Installation” on page 299.
292
Configuring the FDC280 Debug Driver via ICC

Proceed as follows:
1. Invoke ICC and click Vol.
Figure D-10. ICC - Select Vol
293
2. Click Edit Station.
Figure D-11. ICC - Select Edit Station
294
3. Select the FDC280 whose communications you want to diagnose.
Figure D-12. ICC - Select FDC280 Module
295
4. On the left side of ICC, select the compound that contains your currently configured
drivers. Then click View Blocks/ECBs in this Compound.
Figure D-13. ICC - View Blocks/ECBs in this Compound
296
5. Select any Ethernet or serial driver, or the Log Driver (LOGDRV) on the left column
and click Insert New Block/ECB.
Figure D-14. ICC - Insert New Block/ECB
When configuring the Log Driver (LOGDRV) for use with the FDC280 I/O Diag-
nostic Tool, you have to set certain parameters that are needed for the tool to func-
tion.
a. While configuring the driver (type ECB200), confirm that the DRVRID parame-
ter is set to -1.
b. Set HWTYPE to 1, and SWTYPE to 200.
c. Configure the parent ECB to be the FDC280’s Ethernet port (regardless of which
device you want to capture).
d. Set CPARM1, CPARM2, and CPARM3 next. CPARM1 and CPARM2 represent
where the information from each FDC280 will be sent for capture. CPARM1 is
the left module, and CPARM2 is the right module. Configure the IP address of
the station running the FDC280 I/O Diagnostic Tool, and the port on which the
tool will be receiving the diagnostics data. For example (CPARM1
192.168.100.90:7001) would configure the left FDC280 module to send its
data to the station at IP 192.168.100.90 on the port 7001. The port number for
the two modules has to be different. For example
297
(CPARM2 192.168.100.90:7002) - this setting allows data from both modules

to be captured using multiple instances of the tool. Finally, configure CPARM3 to
contain the name of the device from which you wish to capture information, as
well as the rate (in seconds) of which the diagnostic information updates have to
be sent. For example, (CPARM3 S1001:10) would configure the Log Driver to
capture Device S1001’s data and send its diagnostic information updates every 10
seconds. By default, the Log Driver runs for 10 minutes so as to not cause any
overhead for extended periods of time. However, this can be changed by editing
CPARM3, such as (CPARM3 S1001:10+LTO=100). This configures the same
options as before, but the Log Time Out time is set to 100 minutes instead of 10.
If you want the Log Driver to run forever, configure the LTO to be 0. The
remaining Definitions may be left as default configurations.
Figure D-15. ICC - Configuring the Log Driver (LOGDRV)
6. After the parameters for the driver are configured, click Done on the bottom of ICC.
298
7. Open the System Manager. Select the driver you just configured and right-click on it.
Select Go On-Line….
Figure D-16. System Manager - Put the Driver You Configured On-Line
Now proceed to “FDC280 I/O Diagnostic Tool Installation” on page 299.
FDC280 I/O Diagnostic Tool Installation

Now that the driver is up and running, install the FDC280 I/O Diagnostic Tool. This tool is pro-
vided at the Global Customer Support website at this URL:
https://pasupport.schneider-electric.com/content/prodinfo/fdc280/fdc280_frame.asp
1. Navigate to the location at which you downloaded the FDC280 I/O Diagnostic Tool
installation package.
2. Launch the installer.
Figure D-17. Invoke FDC280 I/O Diagnostic Tool Installer
299
3. In the installer, read through the license terms and conditions. Check the I agree to
the license terms and conditions checkbox, and then click Install.
Figure D-18. FDC280 I/O Diagnostic Tool Setup - License Terms and Conditions
4. The installer checks if you have a compatible version of Microsoft .NET Framework
installed to run the tool. If this is not installed, the installer runs the offline installer of
.NET Framework. This process may take up to fifteen (15) minutes to complete.
Figure D-19. FDC280 I/O Diagnostic Tool Setup - Install Compatible Version of Microsoft .NET
Framework
300
5. After the installer finishes checking or installing the .NET Framework, it displays the
End-User License Agreement. Confirm that the I accept the terms in the
License Agreement checkbox is checked. Then click Next.
Figure D-20. FDC280 I/O Diagnostic Tool Setup - End-User License Agreement
301
6. The Welcome to the FDC280 Device Communication Diagnostics Tool Setup

Wizard appears. Click Next.
Figure D-21. FDC280 I/O Diagnostic Tool Setup - Welcome to the Tool Setup Wizard
302
7. Select where the FDC280 I/O Diagnostic Tool should be installed, or accept the
default location. Click Next to install the tool and finish the installation process.
Figure D-22. FDC280 I/O Diagnostic Tool Setup - Destination Folder
Using the FDC280 I/O Diagnostic Tool

Once you have configured the Log Driver on the FDC280 and installed the FDC280 I/O Diag-
nostic Tool, you are ready to use the tool.
1. From the Start menu, invoke the FDC280 I/O Diagnostic Tool.
Figure D-23. Starting the FDC280 I/O Diagnostic Tool
303
2. From the File drop-down menu, select Options…. This opens the Configuration
Options menu.
Figure D-24. FDC280 I/O Diagnostic Tool - Options
3. From the Configuration Options dialog box, in the UDP Port Number field, type the
number of the port on which you will be listening for diagnostic information. (You
configured this port during the Log Driver configuration.)
In the Number of Rows to Display field, type the maximum number of rows you
want displayed in the view at once.
To change from chunk logs to circular logging, check the Circular Logging?
checkbox. Chunk logs split and create a new log every time the maximum file size is
hit. Circular logging retains the entirety of the log on one file, which will loop around
itself, deleting the oldest entries and only keeping the newest that fit within the file
size.
304
Figure D-25. FDC280 I/O Diagnostic Tool - Configuration Options Dialog Box
4. After configuring these settings, if you want to log all the data received on the tool, it
is recommended that you start logging. From the File drop-down menu, select Start
Log to begin logging data with the selected settings. You are prompted to provide a
save location for the log and to provide a name for the log. After that, logging
commences.
Figure D-26. FDC280 I/O Diagnostic Tool - Start Log
305
5. At this point, all required components are configure. To begin capturing data sent
from the log driver, click the Connect button.
Figure D-27. FDC280 I/O Diagnostic Tool - Connect Button
The device that was configured in the Log Driver will be recorded and data regarding its commu-
nications with the FDC280 is captured in the tool. Each message sent to this device from the
FDC280 and all messages received on the device will be visible on the main display (Figure D-28)
as they are generated. As well, the tool receives periodic updates (as configured in the log driver)
on the Diagnostic Information of the FDC280. This information is visible in the bottom right of
the display and includes helpful data for diagnosing problems within the FDC280.
306
Figure D-28. FDC280 I/O Diagnostic Tool - Runtime Data
If your connection happens to drop or a communication packet becomes unavailable, the tool will
notify you with a message listing how many messages became unavailable. (This is highlighted in
Figure D-29.)
Figure D-29. FDC280 I/O Diagnostic Tool - Missed Messages
307
If you want to further examine a message, or view the information in a different format, select any
message in the display, and the Packet Info tab on the bottom left hand corner of the tool will
provide additional data.
Figure D-30. FDC280 I/O Diagnostic Tool - Packet Info Tab
308
If you want to work with the data you have been logging while still acquiring more data, from the
File menu, click Chop Log to save the current data as is and start a new log with the incoming
information. Now you can view the file in Excel or any other spreadsheet application.
Figure D-31. FDC280 I/O Diagnostic Tool - Chop Log
If the incoming information is hard to keep track of, or you would prefer to view some of the pre-
viously visible data, click the Pause Display button in the upper right corner of the tool to stop
displaying the captured information but continue writing it all to the log. Any information
received during this period will only be viewable by opening the log.
If you need a clean slate and want to wipe the display clean, click the Clear All button to
remove all data from the display. Any data saved to the log will be unaffected.
309
Figure D-32. FDC280 I/O Diagnostic Tool - Pause Display Button
Figure D-33. FDC280 I/O Diagnostic Tool - Clear All Button
310
After exiting the tool and saving a log file, you can open it later if you do not currently have a con-
nection up. From the File menu, click Open Log.
Figure D-34. FDC280 I/O Diagnostic Tool - Open Log
After selecting the file you want to open, the log data is loaded into the tool and displayed in the
same manner as when it was originally captured.
Figure D-35. FDC280 I/O Diagnostic Tool - Re-Display Log Data
311
In order to capture information from both the primary and secondary FDC280s, open a second
instance of the tool and configure the options to listen on both the ports configured in the log
driver.
Figure D-36. FDC280 I/O Diagnostic Tool - Two Instances Listening to the Appropriate Ports on the
Primary and Secondary FDC280 Modules
312
Appendix E. Interfacing Fault-
Tolerant FDC280 to M580 PLC
HSBY
This appendix describes how to interface a fault-tolerant FDC280 to a M580 PLC HSBY. It
provides details about the interface and additional recommendations to be considered when
designing the interface.
The hot standby M580 PLC HSBY to the fault-tolerant FDC280 interface in Figure E-1 is
designed to provide a redundant Modbus TCP communication interface between the two sys-
tems.
(A)
(B)
(C)
(D)
Figure E-1. Interfacing FDC280 FT to M580 PLC HSBY with No Single Point Capable Of Taking Down
the System
313
B0700GQ – Rev C Appendix E. Interfacing Fault-Tolerant FDC280 to M580 PLC HSBY
Table E-1. Figure E-1 - Interfacing FDC280 FT to M580 PLC HSBY Legend
Item Description
(A) Typical Hot Standby M580 system with Ethernet commutation cards:
♦ 2*CPS3500: Power Supply
♦ 2*BME XBP 0400: 4 SLOTS ETHERNET BACKPLANE for the HSBY M580
♦ 2* BME H58 2040: M580 HSBY CPU
♦ 2*BME NOC 0301.3: Ethernet Communication Module
(B) IO network redundant switches for Modbus TCP communication between the fault-tol-
erant FDC280 Ethernet port and the hot standby M580 Ethernet communication cards
(C) Fault Tolerant FDC280
(D) To the Foxboro Evo control network
Overview of Interfacing Fault-Tolerant FDC280 to

M580 PLC HSBY
During normal operation the Primary FDC280 communicates directly with the Primary M580.
The Shadow FDC280 always maintains a link with the Primary M580 using heartbeat messages.
The Shadow FDC280 is always ready to take over the communication with the Primary M580 if
the Primary FDC280 experiences a loss of communication. If the Shadow FDC280 cannot com-
municate with the Primary M580, a system message is reported in the System Manager.
Redundant IO Network for Communications Between

Systems
The two interconnected switches provide a redundant communication path between the two sys-
tems so that any of the fault-tolerant FDC280 modules can communicate with any of the hot
standby M580 units. The active communication link will be always between the Primary
FDC280 and the Primary M580.
Hot Standby M580

The hot standby M580 system must be equipped with Ethernet communication cards. BME
NOC 0301.3 is used in this typical interface example. The NOC card must be assigned two IP
addresses during the configuration, one for the M580 Primary NOC and the other for the M580
Secondary NOC. When the Primary and Secondary M580 swap roles, the NOC card IP
addresses will be also swapped, which means the M580 Primary NOC card will always have the
same IP address regardless which of the two M580 units is the Primary. Hence, the fault-tolerant
FDC280 must be configured to only communicate with the M580 Primary NOC IP address.
♦ Attempting to communicate with the Secondary M580 from the Foxboro DCS may
succeed. However, no write operations can be performed through the Secondary
M580. Only the M580 Primary NOC IP address must be used when configuring the
device in the Foxboro DCS.
314
Appendix E. Interfacing Fault-Tolerant FDC280 to M580 PLC HSBY B0700GQ – Rev C
♦ The hot standby M580 system is not designed to swap roles by default if a loss of
communication link is detected on the M580 Primary NOC card. Hence, if a full
redundancy is desired, the hot standby M580 system has to be configured to swap
roles in case of a communication link loss is detected on the M580 Primary NOC
card.
♦ The Foxboro DCS will not report a system message by default if a loss of communica-
tion link is detected on the M580 Secondary NOC card. If an alarm is required to be
reported in the Foxboro DCS system, the hot standby M580 system and the Foxboro
DCS system must be configured to generate an alarm in case of a communication link
loss is detected on the M580 Secondary NOC card. The Primary M580 can forward
the alarm to the Foxboro DCS system using DCI blocks.
315
B0700GQ – Rev C Appendix E. Interfacing Fault-Tolerant FDC280 to M580 PLC HSBY
316
Appendix F. FDC280 System
Monitor Log (smon_log) Messages
This appendix provides common smon_log messages which may be issued as part of FDC280
operation.
Table F-1. FDC280 Detected Configuration smon_log Errors
smon_log Message Text Description

IP Address not Configured for Left Port in ENETP1 has been enabled without any IP address con-
ECBP
figured for the Left port. This message can also appear
when FDC280 has been rebooted after initialization.
Invalid IP Addr Configured in ECBP IP address (configured in ENETP1) is invalid. See page
17 for list of invalid IP addresses.
Invalid Subnet Mask Configured in ECBP Subnet mask (configured in ENETP1) is not a valid
subnet mask.
Invalid IP address/Subnet mask combination The configured IP address and Subnet mask combina-
configured
tion is invalid.
Invalid Gateway/Subnet mask combination The configured Default Gateway address and Subnet
configured
mask combination is invalid.
Invalid Gateway Configured in ECBP The configured Default Gateway address is not valid.
OS Error in setting IP address configured in The configured IP address/Subnet mask/Default Gate-
FDATA
way has passed initial validation, but the operating sys-
tem has returned a detected error when trying to set the
configuration.
Invalid ESPEED configured in ECBP The configured Speed/Duplex value is not a valid value.
OS Error in setting Speed/Duplex The configured Speed/Duplex has passed initial valida-
tion, but the operating system has returned a detected
error when trying to set the configuration.
Invalid Driver ID configured for ECB200 ECB200 has been configured with an invalid Driver
ID.
Invalid Timestamp option configured in Cus- An invalid value has been found in ECB200 Custom
tom Parameter 1
Parameter 1. For Modbus TCP/IP driver, only the
Timestamp (TSTAMP) option is valid.
Invalid options configured in DVOPTS param- Invalid/unknown options were detected in Device
eter
Options (DVOPTS) parameter. Refer to page 29 for a
list of valid device options.
Scanrate configured in DVOPTS is not a valid The Scan rate option (“+@n”) has been incorrectly con-
number
figured.
Timeout configured in DVOPTS is not a valid The Timeout option (“+TO=n”) has been incorrectly
number
configured.
317
B0700GQ – Rev C Appendix F. FDC280 System Monitor Log (smon_log) Messages
Table F-1. FDC280 Detected Configuration smon_log Errors (Continued)

Retry Count configured in DVOPTS is not in The Retry Count option (“+RT=n”) has been incor-
range (0-9)
rectly configured.
Invalid Heartbeat Point Addr configured in The Heartbeat address (“+H=address”) has been incor-
DVOPTS
rectly configured.
Invalid option +SC+MC configured at DVO- The +SC and +MC options are mutually exclusive, and
PTS parameter
they cannot both be configured at the same time.
Invalid option +SR+MR configured at DVO- The +SR and +MR options are mutually exclusive, and
PTS parameter
they cannot both be configured at the same time.
Invalid Group Scanphase Configured The configured device group’s scan/phase value is
invalid.
Invalid Group Scanrate Configured The configured device group’s scan rate value is invalid.
Invalid Group Start Addr configured The configured device group’s starting address (Custom
Parameter 1) is invalid.
Invalid Group End Addr Configured The configured device group’s end address (Custom
Parameter 2) is invalid.
Invalid Group configured with different start The configured device group’s start and end addresses
and end Addr Type
are invalid due to being in different type ranges.
Invalid group configured with Addr Range The configured device group’s address range overlaps
overlapped
with that of another group.
WC option Configured for group is not a valid The configured device group’s Wait Cycle (“+WC=n”)
number
has an invalid value.
Invalid Group range exceeds max size The configured device FC23 group’s read/write address
range exceeds the maximum size.
Custom parameter 1 not specified for group The configured device group expects Custom Parameter
1 to be configured, but its configuration was not pro-
vided.
vided.
vided.
Groups/Points configuration parsing error While parsing the device group’s configuration, an
unexpected error has been detected.
Exceeding maximum number of groups The current FDC280 configuration is attempting to
allowed 2000
employ more than the allowed maximum of 2000
groups.
Invalid options configured in Custom Parame- An invalid option has been found in ECB200 Custom
ter 1
Parameter 1.
ter 2
Parameter 2.
318
Appendix F. FDC280 System Monitor Log (smon_log) Messages B0700GQ – Rev C
Table F-1. FDC280 Detected Configuration smon_log Errors (Continued)

Min supported value for PH option is 20 times For Single Ported Devices, the PH configured in
of BPC
ECB200 Custom Parameter 2 has been found to be less
than 20 times of BPC.
If BPC is 0.5 then the PH should be >=10
ter 3
Parameter 3.
ter 4
Parameter 4.
ter 5
Parameter 5.
ter 6
Parameter 6.
Table F-2. FDC280 Runtime smon_log Messages

Suppressing duplicate messages for next 10 Due to excessive number of messages being generated,
minutes
all duplicate messages will be suppressed for the next 10
minutes.
Device Integration Shadow Education Com- Device Integration Shadow Education has completed.
pleted
Shadow FDC280 module is now ready in case of
failover.
Device Integration Shadow Education timeout Device Integration Shadow Education has not com-
pleted within 15 minutes.
Error in Performing Fail Over Operation Device Integration failover request has become unavail-
able due to an unexpected error that has been detected.
Shadow Promotion due to better LINK Device Integration redundancy logic promotes Shadow
due to it having better link than Primary.
Shadow Promotion due to better connections Device Integration redundancy logic promotes Shadow
due to it having better device connections than Primary.
Reboot due to Interrupted Shadow education Device Integration Shadow Education had not yet com-
pleted when module became Single/Primary. Therefore,
a reboot occurred to get module back to a known state.
Education Timeout - Dump Available Device Integration Shadow Education was unable to
Reboot due to Device Integration Education
complete. Therefore, the shadow module produced a
Timeout
dump file and rebooted.
319
B0700GQ – Rev C Appendix F. FDC280 System Monitor Log (smon_log) Messages
320
Index
A Detected error recovery cooperative diagnostics
Active Directory 180 239
Addresses Detected error recovery local diagnostics 239
IP 13 Device data verification 28
MAC 13 Diagnostics
Auto/manual mode (control block) 124 detected error recovery cooperative diagnostics
239
B detected error recovery local diagnostics 239
Baseplates for FDC280 mounting 29 start-up 239
Basic Security Functions 180
Block Detail Displays 28 E
Block point number 121 ECB200 109
Block processing, DCI 123 ECB201 115
Block, defining 93 Environmental constraints 4
Boot-up sequence 84 Environments 180
commissioned FDC280 85 Equipment Change display 220
FDC280 module with a new letterbug 86 FBM230/232 206, 214
FDC280 module with the same letterbug 85 Equipment Information display
shadow module with the same letterbug and FBM231/233 202, 207, 211, 215
software image 86 Ethernet Switch Access 182
shadow module with the same letterbug but Ethernet Switch Requirements 179
different software image 88 External timing 23
Extracting memory dump information 237
C
Cable connections,RS-232 56, 77 F
Cable connections,RS-422 48, 65 Fault-tolerant operation 7
Cable connections,RS-485 hot remarry 232
RS-485 cable connections 48, 65 FDC280
Cable length 52 fault-tolerant operation 7
Cables, installing 45 installing 30
Cascade initialization 125 installing cables 45
Configuration information 99 installing secondary module 42
Configuring DCI blocks 120 installing single or primary module 32
Connections 48, 65 LED indicators 223, 240
Control block, defining 93 letterbug installation 34
Control Configuration 92 network configuration 11
copper adapter witch restrictions 45 overview 1
replacing an unavailable module 233
D
reset button 223
Data Format 180
sizing constraints 24
Data stream types 4
DCI block functions 124 FDC280 Requirements 179
DCI block processing 123 Field Device Controller 280, overview 1
DCI blocks
G
configuring 120
General Security Considerations 180
Defining blocks 93
Group displays 187
321
Index B0700GQ – Rev C
H R
Hot remarry 232 RDALGO 95, 102, 131
Redundancy Algorithm 95, 102, 131
I Redundant input selection 126
Input limiting 124 Reference documents xix
Installing Replacing an unavailable FDC280 module 233
cables 45 Reset button 223
FDC280 30 Reset button, location and operation 4
secondary FDC280 module 42 Revision information xvii
single or primary FDC280 module 32 RS-232 cable connections 56, 77
Internal timing 23 RS-232 communication switches
IP addresses 13 RS-422 or RS-485 configured port 49, 66
RS-232 switch pinout 60, 81
L RS-232 switch settings
LED diagnostic indicators 223, 226, 240 TA RS-232 switch settings 80
Letterbug installation 34 RS232 switch settings
Linear scaling 124 TA RS-232 switch settings 59
RS-232 switch settings, TA 59, 80
M RS-422 cable connections 48, 65
MAC addresses 13 RS-422 or RS-485 configured port
Maintenance 201 RS-232 communication switches 49, 66
Major Image Update procedure RS-422 or RS-485 port
non-fault-tolerant FDC280 station 265 RS-232 communication switches 49, 66
Master TimeKeeper 23
Memory dumps 236 S
extracting 237 self-hosting 8
enabling or disabling 39
N installation 31
Network configuration, FDC280 11 order of powering on 31
Network path switching 13 with fault-tolerance 9
NTP Exclusion 180 Signal conditioning 124
Simulation mode 124
O Slave TimeKeeper 23
Operating Environment 180 Software installation 92
Operational Status LEDs, troubleshooting 227, Start-up diagnostics 239
229 Switch pinout RS-232 60, 81
Output clamping 125 Switching network paths 13
Output confirmation 125 System Definition 91
Output initialization 125 System Management displays 201
FDC280 184
P System Manager displays 202
Parameter status bits, DCI 126 System Trust Boundary 178
Peer-to-peer connections
points not found 263 T
Periodic/change-driven execution 124 TA 47, 64
Physical Plant Requirements 178 TA RS-232 switch settings 59, 80
Point number 121 Termination assembly 47, 64
Process operator displays 187 Termination cable
part numbers and lengths 47, 64
Q Terminators 48, 65
Quick-start example 25
322
Index B0700GQ – Rev C
Terminators, bus 49, 50, 52, 53, 54, 66, 67, 70, 73
Time synchronization 23
Timing
external 23
internal 23
Troubleshooting
fault-tolerant FDC280 becoming unavailable 232
hot remarry 232
memory dumps 236
Operational Status LEDs 227, 229
323
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

b0700gq C

Uploaded by

Copyright:

Available Formats

b0700gq C

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

b0700gq C

Uploaded by

Copyright:

Available Formats

Foxboro Evo™

Process Automation System

Field Device Controller 280

Copyright 2016 - 2018 Schneider Electric.

SOFTWARE LICENSE AND COPYRIGHT INFORMATION

Simplex FDC280 to Ethernet Field Devices Configuration ................................................ 14

2. Quick Start Guide ........................................................................................................... 25

3. Installing the Field Device Controller 280....................................................................... 29

TA Terminations For RS-422 or RS-485 ........................................................................... 54

5. Control Block Configuration Information for I/O Functions.......................................... 99

Install FDC280 Drivers ...................................................................................................... 99

Configuring Device Options in CCS FDC280 Configurator ........................................... 157

7. Principles of Operation ................................................................................................. 169

8. FDC280 Security Guidelines......................................................................................... 177

9. System Management ..................................................................................................... 183

10. Process Operator Displays........................................................................................... 187

FDC280 Station Compound Block Detail Display .......................................................... 190

11. Maintenance and Control Software Equipment Information ...................................... 201

12. Troubleshooting FDC280 Hardware .......................................................................... 223

Exceeding Allowable Object Manager (OM) Updates/Second .......................................... 234

13. Troubleshooting FDC280 Ports.................................................................................. 243

Updating a Non-Fault-Tolerant FDC280 ........................................................................ 265

Appendix B. Improving Performance of the CCS FDC280 Configurator on Stations with

Appendix C. Upgrading / Usage with FDC280 Released 090009000 Image..................... 281

Appendix E. Interfacing Fault-Tolerant FDC280 to M580 PLC HSBY............................ 313

Appendix F. FDC280 System Monitor Log (smon_log) Messages..................................... 317

Index .................................................................................................................................. 321

3-29. RS-232 Switches, Modem Connection (Typical) ........................................................ 63

6-2. FDC280 Modbus TCP Driver Installation ............................................................... 129

11-3. Fault-Tolerant FDC280’s Ethernet Port Equipment Information

D-17. Invoke FDC280 I/O Diagnostic Tool Installer ......................................................... 299

Who This Book Is For

What You Should Know

Chapter 4 “Configuration Information”

Figure 1-1. Simplex and Fault-Tolerant FDC280s in Baseplate

Network Adapters Time Strobe To Ethernet I/O

Ethernet I/O Port

Power Serial I/O Port

The FDC280 baseplate includes connectors for:

Functional and Environmental Constraints

I/O Network Configuration

Table 1-1. Supported FDC280 Serial Port Termination Assemblies

Termination Assembly Part Number

Summary of Communication Link Characteristics (Ethernet)

Table 1-2. Communication Link Characteristics

Table 1-2. Communication Link Characteristics (Continued)

Table 1-3. Communication Link Characteristics for Serial I/O

Serial Mode Baud Rate

Number of Devices and FDC280 Loading

FDC280 Supported Protocol

Fault Tolerance Over the Foxboro Evo Control Network

Self-Hosting and Non-Self-Hosting Modes

Checkpoint Behavior in Self-Hosting FDC280

♦ If a non-fault tolerant module is not successful in writing a checkpoint file to flash

Major Image Update

Minor Image Update

Number of Self-Hosting or Auto-Checkpointing FDC280s

FDC280 Network Configuration for the Foxboro Evo

The Foxboro Evo Control Network