b0193jc U

I/A Series® System
System Management
Displays
B0193JC
Rev U
August 30, 2012
Invensys, Foxboro, d/p Cell, FIO, Fox, FoxCom, FoxView, I/A Series, INTERSPEC, the Invensys logo, Micro-
I/A, SINGLE STATION MICRO, SPEC 200, SPECTRUM, TankExpert, and UFM are trademarks of
Invensys plc, its subsidiaries, and affiliates.
All other brand names may be trademarks of their respective owners.
Copyright 1992-2012 Invensys Systems, Inc.

All rights reserved
SOFTWARE LICENSE AND COPYRIGHT INFORMATION

Before using the Invensys Systems, Inc. supplied software supported by this documentation, 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, Invensys Systems, Inc. will no longer provide you
with support services and assumes no further responsibilities for your system or its
operation.
2. All software issued by Invensys Systems, 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
Invensys Systems, Inc. for any purpose other than those purposes mentioned in the
software license.
Contents
Figures.................................................................................................................................... xi
Tables.................................................................................................................................... xv
Preface................................................................................................................................. xvii
Revision Information ............................................................................................................ xvii
Reference Documents .......................................................................................................... xviii
1. System Management Overview.......................................................................................... 1

Nodebus Interconnection Configurations ................................................................................. 1
Accessing System Management ................................................................................................. 2
System Management Subsystem Software ................................................................................. 2
System Monitor Subsystem .................................................................................................. 2
Station Manager Subsystem .................................................................................................. 3
Software Manager Subsystem ............................................................................................... 3
Server Manager Subsystem ................................................................................................... 3
Printer Monitor Subsystem .................................................................................................. 3
System Management Display Handler Subsystem ................................................................ 4
Network Fault Detection Subsystem .................................................................................... 4
Nodebus Cable Faults ...................................................................................................... 5
Carrierband LAN Cable Faults ........................................................................................ 5
PIO Bus Cable Faults ...................................................................................................... 5
System Event Messages ............................................................................................................. 5
2. Introduction to the User Interface ..................................................................................... 9

Accessing System Management Displays ................................................................................... 9
Hierarchy of System Management Displays ............................................................................ 11
Viewing the Initial Display ................................................................................................. 12
Understanding System Management Display Hierarchy ..................................................... 13
Understanding System Management Display Graphics ........................................................... 14
Navigating through the Displays and the Display Hierarchy .............................................. 15
Moving Through the Current Display ........................................................................... 15
Accessing the Bus Display .............................................................................................. 15
Accessing Devices on the Next Level ............................................................................. 15
Returning to Previous System Management Display ...................................................... 16
System Management Display Top Menu Bar Actions ........................................................ 16
Identifying Stations and Peripherals ................................................................................... 17
Graphical Representations of Stations and Attached Peripherals .................................... 17
Letterbugs as Indicators ................................................................................................. 18
iii
B0193JC – Rev U Contents
System Management Display Security ..................................................................................... 19

Operator Notification of System Equipment Faults ....................................................... 20
Understanding System Health Color-Coding .......................................................................... 21
Understanding Network Health Coding ................................................................................. 23
Color-Coding for all Network Health Displays and Stations .............................................. 24
Communication Health Color-Coding for the Address
Translation Station or Carrierband LAN Display ............................................................... 24
Communication Health Color-Coding for the Nodebus Display ....................................... 25
Communication Health Color-Coding for the PIO Network and Bus Display .................. 26
Overview of System Management Display Windows ............................................................... 27
Address Translation Station (ATS) Network Display Overview .......................................... 28
Related Information ...................................................................................................... 28
Carrierband LAN Display Overview .................................................................................. 29
Configuration Information Display Overview .................................................................... 30
Equipment Change Display Overview ................................................................................ 31
Equipment Information Display Overview ......................................................................... 33
Information about PIO Bus (Fieldbus) Selection ........................................................... 33
Inhibited Information Display Overview ............................................................................ 35
Alarm Inhibit States for Healthy Equipment ................................................................. 35
Intelligent Devices Display Overview ................................................................................. 36
Multiple Bus Display Overview .......................................................................................... 36
Nodebus Display Overview ................................................................................................ 37
Single-Node Systems ..................................................................................................... 37
Multi-Node Systems ...................................................................................................... 37
Understanding the Nodebus Display ............................................................................. 37
Off-Line Diagnostic Display Overview ............................................................................... 38
On-Line Diagnostics Display Overview .............................................................................. 39
Performance Options Display Overview ............................................................................. 40
Peripheral Counters Display Overview ............................................................................... 41
Peripheral Names and Types Display Overview .................................................................. 43
PIO Network and PIO Subnetwork Overview ................................................................... 44
Set Date and Time Display Overview ................................................................................. 45
iv
Contents B0193JC – Rev U
Station Display Overview ................................................................................................... 46

Switch Domain Display Overview ...................................................................................... 46
Switch Ports Display Overview ........................................................................................... 47
Switched Network Overview .............................................................................................. 49
System Alarm Display Overview ......................................................................................... 49
System Management Counter Categories Display Overview ............................................... 50
System Management Counters Displays Overview ............................................................. 50
System Monitor Displays ........................................................................................................ 51
3. Controlling Date, Time and Time Zone ......................................................................... 53

Setting Time from SMDH ...................................................................................................... 53
Procedure for Setting the Date and Time from SMDH ...................................................... 54
Setting Time Zone on The MESH Workstations .................................................................... 55
Setting Time Zone on The MESH Windows Workstations ............................................... 55
Setting Time Zone on The MESH Solaris Workstations .................................................... 56
Nodebus Daylight Saving Time (DST) Adjustments ............................................................... 56
Introduction ....................................................................................................................... 56
DST Procedures ................................................................................................................. 58
DST Examples ................................................................................................................... 61
DST Example 1 ............................................................................................................. 61
DST Example 2 ............................................................................................................. 62
DST Example 3 ............................................................................................................. 62
DST Example 4 ............................................................................................................. 62
4. Responding to Alarms ..................................................................................................... 63

Acknowledging Alarms Collectively for a Domain .................................................................. 63
Identifying Alarms .................................................................................................................. 63
Acknowledging Alarms ............................................................................................................ 65
Responding to Network Alarms .............................................................................................. 66
Inhibiting Alarms .................................................................................................................... 66
5. Monitoring the System.................................................................................................... 67

Viewing Equipment with Inhibited Alarming ......................................................................... 68
Overview of the Inhibited Information ............................................................................... 68
Viewing Equipment with Inhibited Alarming .................................................................... 68
Viewing Configuration Information ....................................................................................... 69
v
Overview of the Configuration Information ....................................................................... 69

Accessing the Configuration Information ........................................................................... 69
Accessing from a Network Display ................................................................................ 70
Accessing from a System Health Display ....................................................................... 70
Configuration Information ................................................................................................. 71
Configuration Information Display Actions .................................................................. 72
Equipment Information Display ............................................................................................. 72
Overview of the Equipment Information Display ............................................................... 72
Information About PIO Network (Fieldbus) Selection .................................................. 72
Accessing Equipment Information Displays ....................................................................... 72
Accessing from a System Health Display ....................................................................... 72
Accessing from a Network Health Display ..................................................................... 72
Accessing for NEXT LEVEL Intelligent Field Devices ................................................... 73
Equipment Information Display Actions ............................................................................ 73
Equipment Information Displays for Stations, Peripherals, FCMs and Switches ..................... 73
Equipment Information Display for Station/Switch ........................................................... 73
Equipment Information Display for Network Printer ........................................................ 81
Equipment Information Display for USB Printer ............................................................... 86
Equipment Information Display for Primary ECB (FBM0) ............................................... 89
Equipment Information for Fieldbus Module (FBM) ......................................................... 96
Equipment Information for Fieldbus Communications Modules (FCMs) ........................ 105
6. Monitoring Performance ............................................................................................... 115

Overview of Monitoring Performance ................................................................................... 115
Accessing the Performance Options Display .......................................................................... 115
Viewing System Management Counters ................................................................................ 116
Monitoring Changes in Performance ................................................................................ 117
System Management Counter Displays ................................................................................. 118
Resolution of Exceeded Counter Threshold Conditions ................................................... 118
MAC Sublayer ................................................................................................................. 119
Network Layer ................................................................................................................. 122
Transport Layer ................................................................................................................ 123
Application Layer ............................................................................................................. 126
Loading Parameters Display ............................................................................................. 129
Viewing Peripheral Device Counters ..................................................................................... 130
Accessing Peripheral Counters .......................................................................................... 130
Monitoring Changes in Performance ................................................................................ 131
Peripheral Names and Types Display ............................................................................... 131
7. Equipment Changes and Diagnostics ............................................................................ 139

Performing Equipment Changes ........................................................................................... 139
Accessing Equipment Change .......................................................................................... 139
Accessing from a System Health Display ..................................................................... 139
Accessing from a Network Health Display ................................................................... 139
Accessing from an Equipment Information Display ..................................................... 140
vi
Station Changes .................................................................................................................... 140

Checkpoint Command ..................................................................................................... 142
Saving Control Processor Changes ............................................................................... 142
Checkpointing Information for ICC Databases ........................................................... 143
Inhibit or Enable Station Alarming Actions ...................................................................... 144
Overview of Station Alarming ..................................................................................... 144
Procedures for Station Alarming .................................................................................. 144
Reboot Action .................................................................................................................. 144
Overview of Reboot Action ......................................................................................... 144
Reloading the Station Image ........................................................................................ 145
EEPROM Update Action ................................................................................................. 145
Overview of the EEPROM Update Action for Stations ............................................... 145
Updating EEPROM Firmware with New EEPROM Firmware ................................... 146
Fault Tolerant EEPROM Update ................................................................................ 147
Image Update ................................................................................................................... 147
Enable or Disable Download Actions ............................................................................... 147
Enable or Disable Uploads Actions ................................................................................... 148
Overview of the Enable Upload and Disable Upload Actions ...................................... 148
Enable or Disable All Reports Actions .............................................................................. 149
On-Line Image Update .................................................................................................... 149
Peripheral Changes ................................................................................................................ 150
Go On-Line or Go Off-Line ............................................................................................ 151
Understanding Peripheral Response to On-Line and Off-Line Actions ........................ 151
Procedures for Putting a Peripheral On-Line or Off-Line ............................................ 152
General Download for All FBM Images ........................................................................... 152
Overview of the General Download ............................................................................. 152
Downloading all FBM Images ..................................................................................... 153
Download ........................................................................................................................ 153
Overview of the Download Selected FBM Image ........................................................ 153
Procedure for Downloading a Selected FBM Image ..................................................... 153
EEPROM Update ............................................................................................................ 154
Overview of the EEPROM Update for Peripherals ...................................................... 154
Updating Peripheral Firmware with Updated EEPROM Software .............................. 154
PIO Bus Switching, Enabling and Disabling .................................................................... 155
Overview of the PIO Bus Switching Actions ................................................................ 155
Overview of Periodic PIO Bus Switching Mode .......................................................... 156
Periodic PIO Bus Switching Information for Specific Peripherals ................................ 156
BUS A: ENABLE SWITCHING and BUS B: ENABLE SWITCHING Modes ......... 157
BUS A: DISABLE SWITCHING and BUS B: DISABLE SWITCHING Modes ....... 157
Using the PIO Bus Switching Options ........................................................................ 157
Errors with the PIO Bus Switching Modes .................................................................. 158
FCM100Et, FCM100E, FCP270 and ZCP270 Module Fieldbus Switching Actions ....... 158
Overview of FCM100Et, FCM100E, FCP270, or ZCP270 Module Fieldbus
Switching Mode .......................................................................................................... 159
Using the FCM100Et, FCM100E, FCP270, or ZCP270 Module Fieldbus
Switching Options ....................................................................................................... 160
Inhibit Device Alarming or Enable Device Alarming ........................................................ 161
Reset Attention Bit ........................................................................................................... 162
vii
Switch Roles for Redundant Equipment ........................................................................... 162

Switch Changes ..................................................................................................................... 162
Inhibit or Enable Switch Alarming ................................................................................... 163
Disable or Enabling Reports ............................................................................................. 163
Running On-Line Network Diagnostics ............................................................................... 163
Overview of the On-Line Diagnostics .............................................................................. 163
Testing Nodebus Station Cables ....................................................................................... 163
Overview of the Nodebus Cable Test .......................................................................... 164
Procedure for Running the Nodebus Cable Test ......................................................... 164
Changing the Nodebus Cable Test Initiator ................................................................ 165
Carrierband LAN Cable Testing ...................................................................................... 166
On-Line Cable Tests ................................................................................................... 166
Performing Off-Line Diagnostics .......................................................................................... 166
Overview of the Off-Line Diagnostic Display ................................................................... 166
Accessing the Off-Line Diagnostic Display ....................................................................... 167
Running Off-Line Diagnostic Tests ................................................................................. 167
Running the Off-Line Diagnostic Tests ....................................................................... 167
Viewing the Results of the Off-Line Diagnostic Test ................................................... 168
After Running Off-Line Diagnostic Tests .................................................................... 169
Types of Off-Line Diagnostic Tests ............................................................................. 170
8. Calibrating Equipment.................................................................................................. 175

Overview of the Calibrate Actions Display ....................................................................... 175
Accessing the Calibrate Actions Display ........................................................................... 176
Calibrate Transmitters to Zero ......................................................................................... 176
Calibrate Transmitters to Zero Flow ................................................................................ 176
Calibrate Transmitters to Zero Total ................................................................................ 176
Calibrate Pressure to Zero on the P1 Transmitter ............................................................. 177
Correct Measurement Errors in Distance Between Sensors ............................................... 178
Correct Measurement Errors in Height of Sensors ............................................................ 178
Appendix A. Device-Specific Equipment Information ....................................................... 179

Equipment Information for A-B Redundant Gateway ECB .................................................. 180
Equipment Information Fields for Allen-Bradley PLC
Devices (ECB63, ECB64, ECB65) ................................................................................... 182
Equipment Information for the A-B Station ..................................................................... 184
Equipment Information for the A-B Station PLC5 Series ................................................. 189
Equipment Information for the A-B Station Rack ............................................................ 191
Equipment Information Fields for AW70 with Bristol Babcock RTUs ECB96 ..................... 193
I/O Driver Counters ........................................................................................................ 193
Equipment Information Fields for AW70 for Bristol Babcock RTUs ECB97 Devices ...... 199
Equipment Information Fields for Device-Oriented ECB Devices ........................................ 204
Equipment Information for Device Integrator Peripherals .................................................... 206
viii
Gateway Peripherals Equipment Information Fields .............................................................. 208

GE Controllers (ECB66, ECB67, ECB68) Equipment Information Fields ........................... 212
INI10, INI15 or SPECTRUM Interface Processor
Peripheral Equipment Information Fields ............................................................................. 214
Intelligent Field Devices Equipment Information Fields ....................................................... 215
820 and 860 Series Transmitter, Magnetic Flowmeter,
Vortex Intelligent Transmitter and Temperature Transmitter .......................................... 216
CORINT Mass Flowmeter ............................................................................................... 227
931D Gas Chromatograph ............................................................................................... 232
Hydrostatic Interface Unit (HIU) .................................................................................... 236
INTERSPEC Integrator Translator Equipment Information ................................................ 247
INTERSPEC Integrator 30 Peripherals Equipment Information .......................................... 249
AIM (Analog Input Module) and CCM (Controlled Communication Module) .............. 249
UIO (Universal Input/Output) and UFM (Universal Field Module) ............................... 253
I/O Gate Peripherals Equipment Information ....................................................................... 256
Micro-I/A AB-IO Peripherals Equipment Information ......................................................... 259
Micro-I/A AB-PIO Peripherals Equipment Information .................................................. 260
Micro-I/A AB-RIO Peripherals Equipment Information .................................................. 262
Micro-I/A GE-IO Peripherals Equipment Information .................................................... 263
Micro-I/A GE-PIO Peripherals Equipment Information .................................................. 264
Micro-I/A Station Equipment Information ...................................................................... 266
Modicon Devices (ECB60/61/62) Equipment Information .................................................. 269
Port ECB Devices Equipment Information ........................................................................... 271
Redundant FBM46 Equipment Information ......................................................................... 273
760 Micro Controller Devices Equipment Information ........................................................ 277
Workstation Processor Peripherals Equipment Information .................................................. 278
Appendix B. System Messages ........................................................................................... 283

Network Fault Detection Message ........................................................................................ 285
Standard Coded/Printed Messages ........................................................................................ 285
Appendix C. Device-Specific Peripheral Counter Background Information ...................... 287

Allen-Bradley, Modicon, or Instrument Gateway ............................................................. 287
Allen-Bradley PLC Devices .............................................................................................. 287
Allen-Bradley Redundant Gateway ................................................................................... 288
Allen-Bradley Station PLC ............................................................................................... 288
Device Integrator .............................................................................................................. 289
GE FANUC Programmable Controller Devices ............................................................... 290
INI10 Peripheral, INI15 Peripheral, and SIP ................................................................... 290
INTERSPEC Integrator Translator/INTERSPEC Integrator 30 ...................................... 290
I/O Gate ECB98 Devices ................................................................................................. 290
I/O Gate ECB99 and ECB100 Devices ............................................................................ 291
Micro-I/A Station Devices ................................................................................................ 292
ix
Modicon Programmable Controllers Devices ................................................................... 292

Primary FBM/FBM Device .............................................................................................. 292
Printer and Terminal Devices ........................................................................................... 293
Index .................................................................................................................................. 295
x
Figures
2-1. Accessing System Management from FoxView ............................................................ 10
2-2. Accessing System Manager from Display Manager ...................................................... 11
2-3. System Monitor Domains Display (Typical) ............................................................... 12
2-4. System Monitors Display (Typical) ............................................................................. 12
2-5. System Monitor Domain Display (Typical) ................................................................ 13
2-6. System Management Display Hierarchy ...................................................................... 14
2-7. ATS Network Display ................................................................................................. 29
2-8. Carrierband LAN Network Display for Multi-Node System (Typical) ........................ 30
2-9. Configuration Information Display ............................................................................. 31
2-10. Equipment Change Display for Stations ..................................................................... 32
2-11. Equipment Change Display for Peripherals ................................................................. 33
2-12. Equipment Information for a Station (Page 1 of 2) ..................................................... 34
2-13. Equipment Information for a Primary Fieldbus Module (Page 1 of 2) ........................ 34
2-14. Inhibited Alarming Information .................................................................................. 35
2-15. Intelligent Devices Display .......................................................................................... 36
2-16. Nodebus Display ......................................................................................................... 38
2-17. Off-Line Diagnostic Display ....................................................................................... 39
2-18. Carrierband LAN On-Line Diagnostics Display .......................................................... 40
2-19. Performance Options Display ..................................................................................... 41
2-20. Example of Peripheral Counters Display for an FBM .................................................. 42
2-21. Example of Peripheral Counters Display (Page 1 of 2) for a Switch ............................. 42
2-22. Example of Peripheral Names and Types Display for FBMs ........................................ 43
2-23. Example of Peripheral Names and Types Display for Switches .................................... 44
2-24. PIO Network Display ................................................................................................. 45
2-25. Station Display for AP50 ............................................................................................ 46
2-26. Switch Domain Display .............................................................................................. 47
2-27. Switch Ports Display ................................................................................................... 48
2-28. Switched Network Display .......................................................................................... 49
2-29. System Alarm List ....................................................................................................... 50
3-1. Set Date and Time Display ......................................................................................... 54
3-2. Time Zone Display ..................................................................................................... 56
3-3. System Monitor Domain with Daylight Savings Time Button .................................... 58
3-4. Current DST Time Mode ........................................................................................... 59
3-5. Current DST TIme Modes ......................................................................................... 60
3-6. DST Mode Auto ......................................................................................................... 61
4-1. System Monitor Domains Display Hierarchy .............................................................. 64
4-2. System Alarm List Display .......................................................................................... 65
5-1. Displays and Path for Monitoring the System ............................................................. 67
5-2. ATS or LI Nodebus Dialog ......................................................................................... 68
5-3. Inhibited Information Display .................................................................................... 69
5-4. Configuration Information Display for Carrierband LAN ........................................... 70
5-5. Configuration Information Display for Ethernet Switches .......................................... 71
5-6. Equipment Information Display for Station ................................................................ 77
5-7. Equipment Information Display for Station (Continued) ........................................... 77
xi
B0193JC – Rev U Figures
5-8. Equipment Information Display for Network Printer ................................................. 82

5-9. Equipment Change Display for Network Printer ........................................................ 83
5-10. Equipment Information Display for UDB Printer ...................................................... 86
5-11. Equipment Information Display for Primary ECB (FBM0) ........................................ 90
5-11. Equipment Information Display for Primary ECB (FBM0) (Continued) .................... 90
5-12. Equipment Information Display for FCM100Et (Page 1) ......................................... 106
5-15. Equipment Information Display for FCM100E (Page 1) .......................................... 108
6-1. Performance Options Display ................................................................................... 116
6-2. System Management Counter Categories Display ..................................................... 117
6-3. MAC Sublayer Counters Display .............................................................................. 119
6-4. Network Layer Display (Available for LI Stations Only) ........................................... 122
6-5. Transport Layer Counters Display ............................................................................ 123
6-6. Application Layer Counters Display .......................................................................... 126
6-7. Loading Parameters Display ...................................................................................... 129
6-8. Peripheral Names and Types Display (Communication Processor) ........................... 132
6-9. Peripheral Names and Types Display (Control Processor) ......................................... 132
6-10. Peripheral Names and Types Display (Ethernet Switches) ......................................... 133
6-11. Peripheral Counters, Page 1 (Ethernet Switch Ports) ................................................. 133
6-12. Peripheral Counters, Page 2 (Ethernet Switch Ports) ................................................. 134
6-13. Peripheral Counters (Printer/Terminal Counters) ..................................................... 135
6-14. Peripheral Counters (FBM) ....................................................................................... 136
7-1. Equipment Change Display for Stations, Typical ...................................................... 141
7-2. Equipment Change Display for FCP270 or ZCP270 Stations .................................. 141
7-3. Equipment Change Display for Address Translation Station ..................................... 142
7-4. FCP270FT/ZCP270FT Image Upgrade ................................................................... 150
7-5. Equipment Change, PIO Bus Switching ................................................................... 155
7-6. FCP270, FCM100Et, FCM100E and ZCP270 Module Fieldbus Selection .............. 159
7-7. Redundant FCM100E Bus Selection Warning Message ............................................ 160
7-8. Simplex FCM100Et Bus Selection Warning Message ................................................ 161
7-9. Simplex FCM100E Warning Message ....................................................................... 161
7-10. On-Line Diagnostics for Nodebus ............................................................................ 164
7-11. Off-Line Diagnostics Displaying Test Results ........................................................... 169
8-1. Calibration Actions Display (Typical) ....................................................................... 175
8-2. Equipment Information for Allen-Bradley Redundant Gateway ................................ 180
8-3. FBM Channel Status Byte ......................................................................................... 218
8-4. XMTR Status Number 1, Status Byte 2, Bit Positions .............................................. 219
8-5. XMTR Status Number 2, Status Byte 3 Description ................................................. 222
8-6. General Status 1 Low for HIU .................................................................................. 242
8-7. General Status 1 High for HIU ................................................................................. 242
8-8. General Status 2 Low for HIU .................................................................................. 243
8-9. Alarm Status 1 Low HIU .......................................................................................... 243
8-12. Alarm Status 2 High HIU ......................................................................................... 245
xii
Figures B0193JC – Rev U
8-13. Input Status Low HIU .............................................................................................. 246

8-14. Input Status High HIU ............................................................................................. 246
xiii
B0193JC – Rev U Figures
xiv
Tables
1-1. Event Messages Priorities .............................................................................................. 6
2-1. Initial System Health Displays .................................................................................... 11
2-2. Status Indicators .......................................................................................................... 18
2-3. Sys Bar Fault Notification ........................................................................................... 20
2-4. System Health Color Coding ...................................................................................... 22
2-5. Color-Coding for all Network Health Displays and Stations ....................................... 24
2-6. Communication Health Color-Coding for ATS or Carrierband LAN Display ............ 24
2-7. Red Cable Graphic Letter Codes for ATS or Carrierband LAN Display ...................... 25
2-8. Communication Health Color-Coding for the Nodebus Display ................................ 25
2-9. Red Cable Graphic Letter Codes for Nodebus Display ................................................ 26
2-10. Communication Health Color-Coding for the PIO Network and Bus Display ........... 26
2-11. Last Bad Channel Access State Color-Coding for the PIO Network and Bus Display . 27
2-12. Switch Status Indicators .............................................................................................. 48
2-13. Port Status Indicators .................................................................................................. 48
5-1. Equipment Configuration Information ....................................................................... 71
5-2. Station Types .............................................................................................................. 74
5-3. Explanations of the Bits (Set to 1) Related to the Primary Command Status
(I/A Series FBM01 to FBM99) ................................................................................. 102
5-4. Primary Command Status Field Values (DIN Rail Mounted FBMs) ........................ 103
5-5. Bit Positions Set to 1 ................................................................................................. 103
5-6. Explanations of the Bits (Set to 1) Related to the FBM Status ................................... 104
5-7. Expansion Units for FBMs ........................................................................................ 105
6-1. MAC Sublayer Counters Display .............................................................................. 120
6-2. Network Layer Display ............................................................................................. 122
6-3. Transport Layer Counters ......................................................................................... 124
6-4. Application Layer Counters ....................................................................................... 127
6-5. Loading Parameters ................................................................................................... 130
6-6. Peripheral Counters, Ethernet Ports .......................................................................... 134
6-7. Peripheral Counters For SCSI (Printers, Floppy, Disk, Terminals) Devices .............. 136
7-1. Communication Processor 10 and 760/761 Gateway Diagnostic Tests ..................... 170
7-2. Communication Processor 15/30, INIs, and Gateways Diagnostic Tests ................... 170
7-3. Control Processors Diagnostic Tests .......................................................................... 171
7-4. Application Processor 20 Diagnostic Tests ................................................................ 171
7-5. Workstation Processor 30 Diagnostic Tests ............................................................... 172
7-6. SPECTRUM Slave Gateway Diagnostic Tests .......................................................... 172
7-7. Tank Processor 10 Diagnostic Tests .......................................................................... 172
7-8. Carrierband LAN Interface Diagnostic Tests ............................................................. 173
7-9. INTERSPEC Integrator (IS30) Diagnostic Tests ...................................................... 173
8-1. Magflow Status Conditions ....................................................................................... 218
8-2. FBM Channel Status Byte Bit Descriptions .............................................................. 218
8-3. Activities or Events Associated with the Setting of Each Bit or Bits ........................... 220
8-4. Transmitter Type Number ........................................................................................ 220
8-5. 820 Series Transmitter Type Number ....................................................................... 220
8-6. Transmitter Bit Settings ............................................................................................ 222
xv
B0193JC – Rev U Tables
8-7. Magflow Transmitter Error/Status Code ................................................................... 223

8-8. Transmitter Status Bits 10 to 23 ............................................................................... 224
8-9. Bit Settings for the FBM Status Conditions .............................................................. 228
8-10. Hexadecimal Bit Settings .......................................................................................... 228
8-11. Hexadecimal Values for FBM Software Errors .......................................................... 229
8-12. Explanations of the Bits (Set to 1) Relating to the FBM Status ................................. 231
8-13. Bit Settings for the FBM Status Conditions .............................................................. 234
8-14. Explanations of the Bits (Set to 1) Relating to the Primary Command Status ............ 239
8-15. Fan/Power Monitor States ........................................................................................ 275
8-16. FBM46 Diagnostic Status 3 Errors ............................................................................ 275
B-1. System Management Event Messages for SMDH ...................................................... 283
B-2. Network Fault Detection Messages ........................................................................... 285
B-3. Standard Coded and Printed Messages ...................................................................... 285
xvi
Preface
This document describes the use of System Management displays for monitoring the health of the
network, the system, and stations on the network including peripherals and local communica-
tions equipment. It applies to The MESH control network, 50 Series systems, and 70 Series sys-
tems.
This document describes how to:
 Set the system date and time
 Access performance counters for analysis
 Calibrate intelligent devices
 Invoke equipment change actions for stations and peripherals
 Run cable and station diagnostics.
This document should be read by all those who are responsible for monitoring system equipment
and performing maintenance tasks on the equipment.
You should use this document in conjunction with other subsystem documents which include
System Management messages, preventive maintenance information, and corrective actions for
specific equipment.
Revision Information
For this revision of the document (B0193JC-U), the following changes were made:
Chapter 1 “System Management Overview”
 Updated the introduction on page 1 with regards to the three configurations in which
I/A Series workstations can interconnect with the Nodebus.
 Updated the maximum number of stations supported by the System Monitor in “Sys-
tem Monitor Subsystem” on page 2.
 Added “Server Manager Subsystem” on page 3 and “Printer Monitor Subsystem” on
page 3.
 Updated “Network Fault Detection Subsystem” on page 4.
Chapter 2 “Introduction to the User Interface”
 Updated Figure 2-7 “ATS Network Display” on page 29.
Chapter 5 “Monitoring the System”
 Added Workstation (Windows 7) and Workstation (Windows Server 2008) and Net-
work Printer to the table in “TYPE” on page 74.
 Updated “STATION NAME” on page 74 for Windows 7 and Windows Server 2008
stations.
 Added “Equipment Information Display for Network Printer” on page 81 and
“Equipment Information Display for USB Printer” on page 86.
 Removed Table 5-3 “FBM Types” and Table 5-4 “Types of Application Software and
Related FBM Hardware” on page 98 and replaced both with a reference to the appen-
xvii
B0193JC – Rev U Preface
dix “FBM - ECB Cross Reference” in Control Processor 270 (CP270) Integrated
Control Software Concepts (B0700AG).
Appendix B “System Messages”
 Added a note.
Reference Documents
For more information on relevant topics, refer to the following I/A Series documents:
 Field Control Processor (FCP270) User’s Guide (B0700AR)
 Z-Module Control Processor 270 (ZCP270) User’s Guide (B0700AN)
 Field Device System Integrators (FBM230/231/232/233) User’s Guide (B0700AH)
 FOUNDATION™ fieldbus User’s Guide for the Redundant FBM228 Interface
(B0700BA)
 Time Synchronization User’s Guide (B0700AQ)
 The MESH Control Network Architecture Guide (B0700AZ)
 Address Translation Station User's Guide (B0700BP)
 On-Line Upgrade (B0193RE)
 Control Processor 270 (CP270) On-Line IMAGE Upgrade (B0700BY)
 Device Integrator 15 and Device Integrator 30 User’s Guide (B0193RH)
 DIN Rail Mounted FBM Subsystem User’s Guide (B0400FA)
 Intrinsically Safe I/O Subsystem User’s Guide (B0700DP)
 Fieldbus Cluster I/O User’s Guide (B0193RB)
 FOUNDATION™ fieldbus H1 Communication Interface Modules (FBM220/FBM221)
User’s Guide (B0400FD)
 HART™ Communication Interface Modules User’s Guide (B0400FF)
 Instrument Gateway and 760/761 Series SINGLE STATION MICRO™ Controllers
Configurator (B0193RK)
 Integrators for Allen-Bradley™ Controllers (B0193RG)
 Integrators for Modbus and Modbus Plus Devices (B0193RL)
 Measurement Integration (B0193RA)
 Modbus Communication Interface Module (FBM224) User’s Guide (B0400FK)
 PROFIBUS-DP™ Communication Interface Module (FBM223) User’s Guide
(B0400FE)
 SPEC 200™ Control Integrator User’s Guide (B0193RD)
 SPECTRUM™ Migration Integrator User’s Guide (B0193RC)
 System Manager (B0750AP)
 I/A Series Configuration Component (IACC) User’s Guide (B0400BP)
 Integrated Control Configurator (B0193AV)
 System Definition: A Step-by-Step Procedure (B0193WQ)
 V8.x System Error Messages (B0700AF).
xviii
Preface B0193JC – Rev U
Most documents are available on the I/A Series Electronic Documentation DVD (K0173WT)
provided by the Foxboro business unit of Invensys Operations Management. The latest revisions
may also be available through Invensys Global Customer Support at
http://support.ips.invensys.com.
xix
B0193JC – Rev U Preface
xx
1. System Management Overview
This chapter gives a general overview of system management, including the system monitor,
station manager, software manager, and system management display handler, and also network
fault detection, subsystem software and system event messages.
System Management is a distributed software system that allows you to monitor the health and
performance of all components of a configured system, and to intervene in network operations
when necessary.
The System Management software runs in workstation processors (WPs), application processors
(APs), application workstations (AWs), and personal workstations (PWs).
The major subsystems that comprise the System Management software are as follows:
 System Monitor (SMON).
 Station Manager
 Software Manager
 System Management Display Handler (SMDH)
 Network Fault Detection (NFD)
 Server Manager
 Printer Monitor
Nodebus Interconnection Configurations

There are three configurations in which these subsystems, run on I/A Series workstations, can
interconnect with the Nodebus:
1. Workstations and stations on nodes use the Carrierband LAN Interface or the Fiber
Optic LAN (CLI) to connect to stations on other nodes – this has no network com-
ponent in The Mesh control network.
2. (Extender mode) Workstations and stations communicate with stations on The Mesh
control network and on other nodes using The Mesh as a backbone and the ATS to
connect to the Nodebus(es).
3. (LI mode) Workstations and stations use Address Translation Stations (ATS) to con-
nect Nodebus(es) to The Mesh control network, with an ATS as a ‘bridging node’ to a
Carrierband LAN Interface or Fiber Optic LAN (CLI) network with Nodebus(es).
Together, these subsystems provide the capability to:
 View hierarchical system displays that indicate the health of the system equipment.
The system equipment includes each station (I/A Series® module) and peripherals
(printers, terminals, Fieldbus Modules, intelligent field devices, gateways and gateway
devices, and so forth) within every System Monitor domain.
 (For the third configuration above only) View the Network View that indicates the
health of network communications, and the status of the Address Translation Station
(ATS) which handles communication between the Carrierband/fiber optic LAN and
The Mesh control network. The network communication hardware includes the Car-
1
B0193JC – Rev U 1. System Management Overview
rierband LAN cables and/or fiber optic LAN cables, Nodebus cables, Fieldbuses (PIO
buses), station transmitters, and station receivers.
 View The Mesh control network hierarchical displays that indicate the health of net-
work communications. The network communication hardware includes the Ethernet
switches, fiber optic cables, Fieldbuses (PIO buses), stations connected to the Ethernet
switches, and FBMs connected to the stations.
 Analyze network performance in terms of each station and peripheral by monitoring
communication counters.
 Initially set the network date/time on systems without a Global Positioning System
(GPS). For a system with GPS, date/time is automatically set by GPS time, not from
SMDH. Various system activities require the use of the date and time stamp.
 View station configuration information regarding node location, System Monitor,
host workstation, and so forth.
 For each station and peripheral, view equipment information regarding current status
in terms of hardware, software, run mode, failure mode, error status, and so forth.
 Perform equipment change options, such as CHECKPOINT, REBOOT, EEPROM
UPDATE, IMAGE UPDATE, DOWNLOAD/UPLOAD DATABASE, and so forth,
for stations and peripherals.
 Perform on-line cable tests (LAN and Nodebus) for stations; perform off-line station
diagnostic tests. These tests are useful to field service or maintenance personnel in
identifying and correcting equipment problems.
 Allow alarm inhibit functions for equipment, Ethernet switches, Address Translation
Station, LAN, Nodebus, Ethernet, PIO bus and indicate such on displays.
Accessing System Management

To access System Management in FoxView™ display manager:
 Click the SYSTEM button.
To access System Management in Display Manager:
 From the SYS menu, choose SYS_MGMT.
Appearance of the top menu bar on displays in this document vary. However, content reflects
what is actually displayed on the screen.
System Management Subsystem Software

The following describes the major subsystems comprising the System Management software.
System Monitor Subsystem

The System Monitor (SMON) subsystem monitors the health of the stations configured in its
domain. The SMON supplies status information retrieved from each station in its domain to the
operator via the appropriate displays in the SMDH subsystem.
The SMON maintains accurate information concerning the health, current status, and perfor-
mance of each station and its peripherals.
2
1. System Management Overview B0193JC – Rev U
The SMON routes standard error messages and system management alarm messages to the desig-
nated workstation processors (and/or workstations), logging devices (printers and system termi-
nals), and Historian. In addition, it responds to operator actions and reports those actions to the
SMDH software.
You define the System Monitor domain during the site planning and system definition phases.
[Refer to System Definition: A Step-By-Step Procedure (B0193WQ).] The System Monitor domain
represents all stations managed and monitored by that one SMON. A single SMON subsystem
resides in a selected application processors (AP), application workstations (AW) or personal work-
station (PW). Each network can contain a maximum of 64 stations per System Monitor domain,
and for I/A Series software v8.6 or later, each System Monitor domain can contain a maximum of
128 stations.
Station Manager Subsystem

The Station Manager subsystem resides in each station and does the following:
 Maintains communication with the System Monitor (SMON) software
 Maintains a database consisting of equipment information in order to process requests
for changes to equipment statuses as well as report any status information to the Sys-
tem Monitor subsystem
 Provides services such as rebooting stations, initiating diagnostics, updating
EEPROM information, and switching buses.
Software Manager Subsystem

The Software Manager subsystem is located in each workstation and file server and does the
following:
 Downloads station images, control databases, and FBM software
 Performs EEPROM/IMAGE updates
 Uploads station images under certain conditions
 Checkpoints control databases.
Server Manager Subsystem

The Server Manger subsystem is available in I/A Series software v8.6 and later versions. The
Server Manager monitors the critical components in Microsoft® Windows-based servers and
resides in Windows-based servers only.
The Server Manager utilizes SNMP protocol to communicate with the Microsoft SNMP service
to obtain the health statuses of the server components, including the statuses of the power sup-
plies, cooling systems, memory devices, as well as metrics such as temperature, voltages, intrusion
statuses and available disk space.
The Server Manager communicates with the System Monitor to send change statuses as well as
reporting any status information to the System Monitor.
Printer Monitor Subsystem

The Printer Monitor subsystem is responsible for monitoring the health and status of network
printers that are configured as alarm printers. The network printer is treated as a station with a
unique letterbug and is assigned to the domain of the System Monitor.
3
The Printer Monitor uses SNMP protocol to communicate with the network printer to obtain
the overall status and alerts currently active in the printer.
The Printer Monitor maintains the last-received status of the network printer locally and provides
this information to external interfaces on a change-driven basis or on-demand.
NOTE
For I/A Series software v8.8 or later, network printers are supported.
System Management Display Handler Subsystem

The System Management Display Handler (SMDH) is one of the five subsystems in the System
Management software system. You can use the SMDH subsystem to monitor the health and per-
formance of all components of your configured system and, when necessary, to intervene in net-
work operations.
The SMDH subsystem comprises displays containing actions you can use to monitor the health
of the network, the system, and all stations on the network, including peripherals and local com-
munications equipment. The displays also contain actions for acknowledging alarms, testing
cables, downloading databases, and more.
There are two types of SMDH displays:
 System Health Displays that contain information about the health of the system
 Network Displays that contain information about the health of network
communications.
From either the system health displays or the network health displays, you can access displays pro-
viding equipment change actions, equipment information, configuration information, and diag-
nostic testing.
Network Fault Detection Subsystem

The Network Fault Detection (NFD) subsystem runs in a workstation, file server, LAN interface
or Address Translation Station (ATS). It is responsible for diagnosing and reporting cable faults
for the Carrierband LAN (802.4), fiber optic LAN and the Nodebus (802.3). It reports PIO bus
cable faults detected by CPs. These errors are reported by NFD to System Monitor (SYSMON),
System Management Display Handler (SMDH) and the NFD printer selected during System
Definition.
There is a designated Test Initiator for the Carrierband LAN and a designated NFD Test Initiator
for each node. The order of precedence for the Test Initiator on a node is:
1. ATS
2. Workstation/Server with I/A Series software v7.x or later
3. Carrierband LAN
4. Application Processor or Workstation/Server with I/A Series software v6.x
Operators can manually override the current Test Initiator and NFD can be disabled on an ATS
starting at V8.4.2 or QF 1012403 and on a CLI V6.5.3 or QF1005591. (Later versions of
I/A Series software have these Quick Fixes installed already.)
4
Nodebus Cable Faults

On the Nodebus a cable test occurs under three conditions
 Station requested
 Operator requested
 Change of the Test Initiator
The Nodebus Test Initiator forwards the results of cable tests to SMON, SMDH and the NFD
printer.
Carrierband LAN Cable Faults

The NFD service in the CLI reports any Carrierband LAN cable faults to its System Monitor
which, for a CLI, will be typically on a node.
Each LAN module keeps track of heartbeats from cable A and B for each other LAN module.
When heartbeats are missed, a LAN module forwards that information to the Carrierband LAN
Test Initiator. The Carrierband LAN Test Initiator determines what the fault is based on all the
LAN modules reports as well as its own. This information is forwarded to SMON, SMDH and
the NFD printer.
Operator initiated cable tests on the Carrierband LAN cause the Test Initiator to tell all LAN
modules to turn on both transmitters and receivers for both cables, collect heartbeats and report
the results back to the Test Initiator. The Test Initiator reports those results to SMON, SMDH
and the NFD printer.
PIO Bus Cable Faults

PIO Bus cable faults are detected and reported by the CP hosting the PIO bus. The CP forwards
PIO Bus errors to its SMON. SMON forwards PIO bus errors to the Nodebus Test Initiator. The
Test Initiator reports those results to SMON and SMDH. NFD uses a multicast to all SMONs
and Display Manager message lines to report these errors causing all SYS keys to flash red and all
message lines to display the error.
Only workstations designated during System Monitor configuration can do the following:
 Perform on-line diagnostics, including testing cables and selecting new Nodebus
master
 Set or reset the system time
 Reset counters
 Access diagnostic tests.
NOTE
Only designated personnel should perform equipment status acknowledgment,
counter reset, equipment changes, and on-line and off-line diagnostics.
System Event Messages

The System Management subsystems generate network operation, equipment health, and equip-
ment status event messages.
5
Messages may be a general response to an operator’s request, or may contain an “error” response
reflecting status change, completion messages, operator’s results, station limitations, communica-
tion malfunctions, or other problems associated with the station or communication path.
Printed messages include the following information:
 date/time stamp
 valid time (or *, if invalid)
 priority level
 System Monitor name
 station letterbug
 subsystem software ID,
 error code
 an ASCII text string description of the event.
NOTE
Refer to V8.x System Error Messages (B0700AF) for a complete list of system error
messages.
Operator Notification of System Events

During System Monitor software configuration, you determine whether you want these event
messages sent to the message lines of workstation processors and/or personal workstations, a con-
figured historian, or configured printers.
Event messages are classified as Priority Level One, Two, or Three. Priority level determines how
the system notifies you of event messages.
Table 1-1 lists the three priorities and the various system event messages associated with them.
Table 1-1. Event Messages Priorities
Level Related System Event Messages

Priority One Equipment failure
Error protocol
Unexpected fault-tolerant state change for fault-tolerant module
Priority Two Device forced off-line
Equipment being monitored or is operational
Load is complete
Standard error messages
Priority Three Cable fault (cable, transmitter, receiver or PIO access fault)
The system sends Priority One and Priority Three event messages to the following:
 Message lines (located above the title bar in displays) of workstation processor (WP)
and/or personal workstation (PW) designated to report system management faults.
The ability to view messages sent to a station depends upon security access defined for
that station.
6
 Configured Historian.
 High-priority message printers.
The system sends Priority Two event messages to the following:
 Configured Historian
 Low-priority message printer.
7
8
2. Introduction to the User
Interface
This chapter discusses user interfaces, including the hierarchy of system management displays,
system management display graphics, security, system health color-coding, and system and
network health color-coding. It also provides overviews of 22 displays, and additional sources
for specifics.
This chapter provides an introduction to the user interface for System Management including:
 “Hierarchy of System Management Displays” on page 11
 “Understanding System Management Display Graphics” on page 14
 “System Management Display Security” on page 19
 “Understanding System Health Color-Coding” on page 21
 “Understanding Network Health Coding” on page 23
 “Overview of System Management Display Windows” on page 27
 “System Monitor Displays” on page 51.
Accessing System Management Displays

System Management Displays are accessed from FoxView or the Display Manager.
To access System Management on Windows based systems or Solaris based systems with
FoxView:
 Clicking the SYSTEM button on the Alarm bar (see Figure 2-1).
The initial System Management Display, System Monitors, appears. From this display you can
select a monitor and navigate through the Domain Display(s).
9
B0193JC – Rev U 2. Introduction to the User Interface
1. Click
2. Initial System
Management
Display
Figure 2-1. Accessing System Management from FoxView
For Solaris based workstations with Display Manager, click System to open System Management
(see Figure 2-2).
10
2. Introduction to the User Interface B0193JC – Rev U
Click
Figure 2-2. Accessing System Manager from Display Manager
Hierarchy of System Management Displays

Depending on the size of your configuration, one of the following initial system health displays
appears when you access SMDH:
Table 2-1. Initial System Health Displays
Initial Display Size of System Description

System Monitor Small systems configured Lists all stations within the domain of a single
Domain with only one system monitor System Monitor. This display can be accessed
(Figure 2-5) from a display with multiple System Monitors.
System Monitor Medium size systems configu- Lists all System Monitors and all the stations
Domains rations with several monitors within each System Monitor domain.
(Figure 2-3) and stations
System Moni- Larger system configurations Lists only System Monitors. To view the
tors (Figure 2-4) with a large number of system domain for a System Monitor, select the Sys-
monitors and stations tem Monitor.
You have access to all SMDH system health displays through these initial health displays. Select-
ing an entry (System Monitor name) from the System Monitors Display list brings up the System
Monitor Domain Display. However, if the system has only one System Monitor, the System Mon-
itor Domain Display is the initial display. This display lists all of the stations configured for that
single System Monitor.
11
Viewing the Initial Display
Figure 2-3. System Monitor Domains Display (Typical)
Figure 2-4. System Monitors Display (Typical)
12
Figure 2-5. System Monitor Domain Display (Typical)
Understanding System Management Display Hierarchy

From the initial system health display, other displays in the hierarchy can be accessed via selectable
listed options or selectable soft keys. Figure 2-6 shows the display hierarchy. The text between dis-
plays indicates a “soft” key. For simplicity, neither the NEXT LEVEL soft key, nor other display
option selections are shown in the figure.
For more information on the NETWORK selections, see “Monitoring the System” on page 67.
13
System Management
System System
System
Monitor Monitor
Monitors
Domain Domains
INH DISP TIME NETWORK SW NETWRK PERF OFF-LINE

SAL
CONFIG
Inhibited ATS?
No Yes Performance
Information Options Off-line
Diagnostics
CB LAN?
Set Date System Yes No ATS Switched
and Time Alarm Network
Network System Diagnostic
Management Results
Carrierband Nodebus SW Counter
LAN Domains Categories
Peripheral
Name/Types
System
Management
PIO Station Counter
Multiple Bus Station Network Peripheral
Displays
Counters
Ports Station
Bus
Equipment Equipment Configuration On-line Intelligent

Change Information Information Diagnostics Devices
CALIB
(from Peripheral
Change only)
Calibrate Equipment Equipment
Actions Change Information
Figure 2-6. System Management Display Hierarchy
Understanding System Management Display Graphics

This section contains the following information:
 “Navigating through the Displays and the Display Hierarchy” on page 15
 “System Management Display Top Menu Bar Actions” on page 16
 “Identifying Stations and Peripherals” on page 17.
14
Navigating through the Displays and the Display Hierarchy

As shown in Figure 2-6, the initial display provides access to additional displays that:
 Display information about the system as a whole such as the System Alarm List and
the Inhibited Information displays. These displays are accessible from the initial sys-
tem display by clicking a single soft key.
 Information about the network bus and individual displays. To view information
about individual devices requires that you navigate the bus display and, for some
devices, go down an additional level.
Soft keys appear at the bottom of the SMDH displays. You use the soft keys for paging through
multiple-page displays, accessing other displays, and performing display-specific actions.
Moving Through the Current Display

Vertical Pages
If the display that you are currently viewing has more than one page, use the arrowhead-shaped
page up and page down keys.
Horizontal Pages
If the display you currently view has a series of multiple horizontal pages, use the left-arrow and
right-arrow soft keys to move left or right in the series. Use the BEGIN and END soft keys to
move to the beginning and end of the series.
Accessing the Bus Display

You can access the Bus Display from the System Monitor Domain Display or System Monitor
Domains Display for a specific application workstation (AW).
To access the Bus Display:
1. From the System Monitor Domain Display or System Monitor Domains Display,
select the AW station and click CONFIG. The Multiple Bus Display for the AW
appears, showing peripherals connected to the workstation.
2. From the Multiple Bus Display, select the desired primary device (FBM, GE™,
Allen-Bradley or Modicon™) and click NEXT LEVEL. The Bus Display for that device
appears.
Accessing Devices on the Next Level

If the selected device connects to a Fieldbus or the selected controller connects to a bus, you can
select the device graphical representation and click NEXT LEVEL to access the Intelligent Devices
Display.
15
C54CP3 Indicates
Attached
IT3239 FBM 0
Devices
FBM 39
C54CP3
CP30 FT
Indicates Attached Devices
For example,
 For Allen-Bradley, GE, or Modicon, you can select the controller graphic and click
NEXT LEVEL to access the I/O display for the associated controller.
 For FBP10, you can select the device graphic and click NEXT LEVEL soft key to access
its I/O display.
NOTE
Only printers configured as alarm printers appear in this display.
Returning to Previous System Management Display

The HOME menu bar selection returns you to the initial display. The Return (double up-arrow-
heads) soft key shows the previous display in the hierarchy.
System Management Display Top Menu Bar Actions

The top menu bar on each System Management Display has the following standard selections:
HELP, CLOSE, HOME, DOMAIN, CLR MSG, and ACK CBL.
Selecting the appropriate field initiates the following actions:
 HELP is not supported.
 CLOSE exits System Management and returns to the previous environment.
 HOME returns the initial system health display to the screen. All System Monitors
are again requested to supply information regarding the stations in their domain.
 DOMAIN returns the most recently accessed System Monitor Domain Display to the
screen. DOMAIN is unselectable if a System Monitor Domain Display has not been
previously accessed.
 CLR MSG clears the message line located above the top menu bar. After reading the
message, you may clear the message from the message line using CLR MSG. If not
cleared, the current message is automatically cleared prior to the next message being
displayed.
 ACK CBL acknowledges all of the unacknowledged communication faults associated
with cables, transmitters, receivers, and PIO buses (Fieldbuses). Communication
faults are indicated on the Network Displays and result in the SYS field flashing until
acknowledged.
16
ACK CBL is only selectable if the workstation has been designated to perform secured
actions during System Monitor software configuration and the System Monitor is cur-
rently active.
 TIME allows you to select new values for the month, day, year, hour, minute, and sec-
ond for systems without a connected GPS. For systems with GPS, TIME is inhibited.
Identifying Stations and Peripherals

System display titles, which indicate the hierarchy within the System Monitor domain, can
include:
 System Monitor domain name
 Letterbug of a station within the System Monitor domain
 Letterbug of a peripheral attached to the station or the parent peripheral.
Station within
System Monitor the System
Display Name Domain Name Monitor Domain
Peripheral in
Indicates an Unacknowledged the Related
Equipment Fault Failure Station
Network display titles, which indicate the logical network hierarchy associated with each Address
Translation Station or Carrierband LAN interface on the network and the stations related to the
node, can include:
 Letterbug of the Carrierband LAN Interface connecting the Nodebus to the
Carrierband LAN or the fiber optic LAN
 Letterbug of the Address Translation Station connecting The Mesh control network to
the Carrierband LAN or the fiber optic LAN
 Letterbug of a station within the node
Network display titles, which indicate the logical network hierarchy associated with each Ethernet
switch on the network and the stations related to the domain, can include:
 Letterbug of the Ethernet switch
 Letterbug of a station within the domain.
Graphical Representations of Stations and Attached Peripherals

STATION, NETWORK and SWITCH NETWORK health displays show color-coded graphical
representations of the stations and attached peripherals.
17
511LI1* V11LI1 S11LI1* R11LI1
LAN FT LAN LAN FT LAN FT
Carrierband LAN Interface

SW001A
SW16P
FCP101 FCP201 FCP301 WPXP70
F270 FT F270 FT FCP270 WP70
The MESH Control Network
ATS002
ATS
ANST01 AWST02 CP6001 CP6002
AW70NC AW70NC CP60 CP60
Address Translation Station

The devices appear as individual box graphics, and each box contains a color-coded letterbug, the
type of device represented, and the device connection to the associated communication cable.
Letterbugs as Indicators
Letterbugs are six-character software names assigned to each System Monitor, station within the
domain, and peripheral attached to a station. Some peripherals, such as printers and system termi-
nals, have four-character letterbugs.
Letterbugs appear in the display titles and in the graphical representations of devices shown in dis-
plays, and are used to identify attached devices and the status of the devices.
Table 2-2. Status Indicators
Status Indicators Description

Any Color Blinking There is an unacknowledged health status change. When you acknowl-
Letterbug with an edge the health status, the letterbug returns to solid state (not blinking)
Asterisk and without an asterisk.
18
Table 2-2. Status Indicators (Continued)
Status Indicators Description

Left Angle Bracket (<) The represented station monitors, stations, or devices have inhibited
equipment.
Cyan Letterbug The represented device is off-line, not ready, and/or out-of-service.
Gray Letterbug The status of the represented station is unknown. There is no status
response from the System Monitor.
Red Letterbug (or red The represented equipment failed. (Blinking and with an asterisk indi-
filled box) cates unacknowledged, failed equipment.)
White Letterbug (or This is the normal (healthy) state for the represented System Monitor,
white filled box) station, or peripheral.
White Letterbug with The represented station or its peripheral returned to normal state with-
an Asterisk out acknowledgment of its faulted state.
Yellow Letterbug (or There are failed device(s) attached to the represented System Monitor,
yellow filled box) station, or peripheral, or this is a warning condition for some stations
or devices. A fault-tolerant or redundant station is not operational on
one side (running without backup). A non-fatal warning condition
(warning bit) at an FBP card. An I/O point associated with a device
failed.
System Management Display Security

During System Monitor software configuration, WPs, AWs, and/or PWs are designated to receive
notification of equipment and network faults and perform secured actions on stations within that
System Monitor’s domain and the network.
The configuration parameters for each System Monitor provide for the following workstation
designations:
 Both system and network equipment security access and fault notification for a maxi-
mum of six workstations per System Monitor
 System equipment fault notification only for another set of six workstations.
Each designated workstation provides the following:
 The SYS button reflecting the overall state of the network and the System Monitor
domain(s) configured to send events to the workstation.
 Access to the following secured actions via selectable top menu bar fields and soft
keys:
 Acknowledge station and peripheral faults using the ACK ALL and ACK menu
bar fields.
19
NOTE
With regard to the ACK ALL and ACK alarm acknowledgment soft keys, a worksta-
tion can be in either of two modes: open or secured. In the open mode, ACK ALL
and ACK are selectable from any workstation. In the secured mode these selections
can be made only from designated system workstations. The desired operating
mode is selected for a particular workstation during System Monitor software con-
figuration. The open mode is the default.
 Acknowledge network communication hardware faults using the ACK CBL menu
bar field.
 Access off-line diagnostics for stations in the System Monitor’s domain using the
OFF-LINE soft key.
 Access on-line diagnostics cable testing for stations on the network using the ON-
LINE DIAG soft key.
 Access Equipment Change options for stations and peripherals using the EQUIP
CHG soft key.
 Access counter performance reset options using the RESET ONE and RESET
ALL soft keys.
 Access to the TIME soft key for setting the network time.
Operator Notification of System Equipment Faults

System equipment failures are indicated in the following ways:
NOTE
On the Solaris based workstation, when the Display Manager window is closed
(iconized), the icon can be configured to indicate the current state of the ALARM
(A) and SYS (S) fields as follows:
DM: A# S#
where # indicates the blink state
1 = blinking normal color (green)
2 = solid red
3 = blinking red
Table 2-3. Sys Bar Fault Notification
Sys Bar Current State of Equipment

Solid Normal All system/network equipment is healthy.
Color (Green)
Blinking Normal All system/network equipment is healthy; one or more previous failures are
Color (Green) still unacknowledged. One-half of a fault-tolerant module has failed.
Solid Red One or more pieces of system/network equipment have failed; failures have
been acknowledged.
Blinking Red One or more pieces of system/network equipment have failed; failures have
not been acknowledged.
20
 The system health displays indicate the hardware fault with color-coded System Mon-
itor names and station letterbugs, and graphics.
 If configured, a logging device (printer/system terminal) and/or Historian receives
equipment fault messages.
NOTE
After you acknowledge a horn configured to sound when the System bar changes
from solid state (red or green) to blinking (red or green), you must also acknowledge
the related hardware (system and network) faults. Otherwise, the horn does not
sound for the next system fault.
Understanding System Health Color-Coding

Each System Monitor, station (I/A Series module) within the domain, and peripheral attached to
a station is represented by a logical name or a six-character alphanumeric letterbug ID. Some
peripherals such as printers and system terminals have four-character names. The System Monitor
logical names and device letterbugs are color-coded to indicate the health of each device.
In order for System Management Display Handler (SMDH) to display health status, each System
Monitor must provide the health information received from the stations in its domain. If the Sys-
tem Monitor name appears in gray text, SMDH could not establish communication with the Sys-
tem Monitor or communication with the System Monitor was lost. If communication is lost, the
last known state of each station is displayed. See Table 2-4 for a list of colors and the correspond-
ing health conditions.
A blinking letterbug with an asterisk indicates an unacknowledged health status change. Acknowl-
edgment of the health status removes both the blinking and the asterisk. It is possible for a station
to have a blinking white letterbug and asterisk if the faulted state was not acknowledged before
the station or its peripheral returned to normal.
NOTE
Operator-initiated actions on stations or peripherals, such as reboot, off-line diag-
nostics, go off-line, and so forth, do not result in a blinking letterbug and an
asterisk.
21
Table 2-4. System Health Color Coding
Equipment Logical Name Color Description of Status

System Monitor: White Normal state; healthy System Monitor Domain.
(Software) Yellow 1. Failed device attached to station within
domain; warning condition for IS30 device.
2. Fault-tolerant station non-operational on one side.
3. Warning bit at an FBP card.
4. Bad I/O point associated with a device.
Red Off-line or failed station within domain.
Gray Noncommunicative state; unknown health for System
Monitor Domain.
Equipment Letterbug Color Description of Status
Station (Ethernet White Normal state; healthy station.
switch, worksta- Yellow 1. Failed device attached to station; warning
tion, control pro- condition for device attached to an
cessor, Address integrator-type station (for example, CCM, UIO).
Translation Sta- 2. Bad I/O point associated with a device.
tion and so 3. Fault-tolerant or redundant station
forth): non-operational one side.
4. Warning bit at an FBP card.
Red Off-line or failed.
Peripheral: White Normal state; healthy device.
Printer, Terminal Cyan Off-line, not ready, out-of-service.
Red Failed.
Peripheral: White Normal state; healthy device.
FBM/CORINT/ Red Off-line or failed device.
HIU Analog Digital Converter Failure (AIM, CCM).
AIM, CCM,
UIO, UFM™
PLCs
22
Table 2-4. System Health Color Coding (Continued)
Peripheral: Yellow 1. Failed device attached to FBM18, FBM39,

FBM/CORINT/ FBM43, FBM44, or FBM46.
AIM, CCM, 2. Bad I/O point associated with a device.
UIO, UFM 3. For AIM, CCM, UIO, UFM, warning
PLC™ conditions:
FBCs – Attention Bit Set (UIO, UFM)
FBP10 – Battery Backup Failure (CCM, AIM)
FBP11 (UCM) – Control Panel Set Local (UIO)
FBP12 (FIO™) – DP10 Status Alarm (CCM, AIM)
FBP13 (UFM) – Port 1 or 2 Flunk (CCM)
FBP14 (UIO) – SPEC 200 Power Supply Failure (AIM,
SBMs CCM, UIO, UFM)
– System Flunk (CCM,UIO,UFM)
– System Power Fault (AIM, CCM)
4. For FBP10 Warning Condition set:
a. Letterbug/Slot conflict
b. I/O Bus failure
c. Power supply failure
b. Fan/Power Monitor problem
c. Primary power failure
d. Secondary power failure
e. Primary ac is low
f. Backup ac is low
g. Over-temperature indicator
b. Fan/Power Monitor problem
c. Group over-temperature indicator
a. Power fail
b. Nest power fail
a. Panel key in local position
b. Outputs flunked
c. Power failure
9. For SBM Warning Condition set: device has a
non-fatal error condition.
FBM/CORINT Cyan Off-line, not ready, out-of-service.
IFD, PLCs
Understanding Network Health Coding

Network health displays use color-coding and letter codes to indicate communication hardware
health. The graphics and colors indicate communication hardware health, as well as the active
PIO bus (Fieldbus) and its present mode setting.
23
For example, the SGL letter code above a station graphic identifies a station that has devices
attached to the single cable (that is, ThinNet).
Color-coding information by network display:
 All network health displays and all stations
 Carrierband LAN or Address Translation Station Display
 Nodebus Display
 PIO Bus Display
 Multiple Bus Display
 Bus Display.
Color-Coding for all Network Health Displays and Stations

These colors apply to the graphical representations and letterbugs in network health displays.
Table 2-5. Color-Coding for all Network Health Displays and Stations
Color and Object Status

White Outline Normal state; healthy network communications.
Red Outline  Communication fault(s) with station/device (LI, ATS, station or
FBM).
 Communication fault on the Nodebus cable.
 Communication fault with station or FBM at next level (indicates
communication fault path).
Gray Letterbug Station status is unknown; there is no status response from the System
Monitor. To receive update information for this status type, recall the asso-
ciated network health display.
White Letterbug Normal state; healthy station. (Not applicable to communication hardware
health.)
Yellow Letterbug There are failed device(s) attached to the station. A fault-tolerant or redun-
dant station is non-operational on one side. (Not applicable to communi-
cation hardware health.)
Red Letterbug The station is off-line or failed. (Not applicable to communication hard-
ware health.)
Communication Health Color-Coding for the Address

Translation Station or Carrierband LAN Display
These letter codes appear above the upper-left corner of the station graphic.
Table 2-6. Communication Health Color-Coding for ATS or Carrierband LAN Display
LI Station Red Codes Status

LI Transmitter A TA Failed Transmitter A in the primary module on
the LAN side of the LI
24
Table 2-6. Communication Health Color-Coding for ATS or Carrierband LAN Display (Continued)
LI Station Red Codes Status

LI Transmitter B TB Failed Transmitter B in the primary module on
the LAN side of the LI
LI Receiver A RA Failed Receiver A in the primary module on the
LAN side of the LI
LI Receiver B RB Failed Receiver B in the primary module on the
LAN side of the LI
Drop Cable A DA Failed Drop Cable A
Drop Cable B DB Failed Drop Cable B
Inhibit Station Cable A IA Inhibit LI Station transmitter/receiver cable
alarms for Carrierband A
Inhibit Station Cable B IB Inhibit LI Station transmitter/receiver cable
alarms for Carrierband B
Inhibit Station Cables A and B IAB Inhibit LI Station transmitter/receiver cable
alarms for Carrierband A and B
These letter codes are located on the red cable graphic.
Table 2-7. Red Cable Graphic Letter Codes for ATS or Carrierband LAN Display
LAN Cables/Drop Cables Red Codes Status

Cable A BAD CBL A Failed Cable A
Cable B BAD CBL B Failed Cable B
Cables A and B BAD CBL A and B Failed Cable A and Cable B
Inhibit Cable A INH CBL A Inhibit cable alarms for Carrierband LAN A
Inhibit Cable B INH CBL B Inhibit cable alarms for Carrierband LAN B
Inhibit Cables A and B INH CBL A and B Inhibit cable alarms for Carrierband
LANs A and B
Communication Health Color-Coding for the Nodebus Display

These letter codes appear above the upper-left corner of the station graphic.
Table 2-8. Communication Health Color-Coding for the Nodebus Display
Stations Red Codes Status

Transmitter on Nodebus Cable A TA Failed station transmitter on Nodebus Cable A
Transmitter on Nodebus Cable B TB Failed station transmitter on Nodebus Cable B
Receiver on Nodebus Cable A RA Failed station receiver on Nodebus Cable A
Receiver on Nodebus Cable B RB Failed station receiver on Nodebus Cable B
Inhibit Station Cable A IA Inhibit station transmitter/receiver cable alarms
for Nodebus A
25
Table 2-8. Communication Health Color-Coding for the Nodebus Display (Continued)
Stations Red Codes Status

Inhibit Station Cable B IB Inhibit station transmitter/receiver cable alarms
for Nodebus B
Inhibit Station Cables A and B IAB Inhibit station transmitter/receiver cable alarms
for Nodebus A and B
These letter codes appear in red on the cable graphic.
Table 2-9. Red Cable Graphic Letter Codes for Nodebus Display
Nodebus Cables Red Codes Status

Cable A BAD CBL A Failed Cable A
Cable B BAD CBL B Failed Cable B
Cable A and B BAD CBL A and B Failed Cables A and B
Inhibit Cable A INH CBL A Inhibit cable alarms for Nodebus A
Inhibit Cable B INH CBL B Inhibit cable alarms for Nodebus B
Inhibit Cables A and B INH CBL A and B Inhibit cable alarms for Nodebus A and B
Communication Health Color-Coding for the PIO Network and

Bus Display
These letter codes appear on the bus and indicate the current Fieldbus and its mode.
Table 2-10. Communication Health Color-Coding for the PIO Network and Bus Display
Fieldbus Black Codes Status

Fieldbus A A PERIODIC Bus A currently in use with periodic switching and bus
switching enabled
Fieldbus B B PERIODIC Bus B currently in use with periodic switching and bus
switching enabled
Fieldbus A A ENABLE Bus A running with bus switching enabled, periodic
switching disabled
Fieldbus A A DISABLE Bus A running with bus switching disabled, periodic
switching disabled
Fieldbus B B ENABLE Bus B running with bus switching enabled, periodic
switching disabled
Fieldbus B B DISABLE Bus B running with bus switching disabled, periodic
switching disabled
These letter codes appear above the peripheral and indicate the last bad channel access state for
the peripheral.
26
Table 2-11. Last Bad Channel Access State Color-Coding for the PIO Network and Bus Display
Peripheral Color/Code Status

Peripheral Channel Red “A” Last A Bus access was bad
Peripheral Channel Red “B” Last B Bus access was bad
Peripheral Channel Red “AB” Last A and B Bus accesses were bad
Inhibit Peripheral Channel A Black “IA” Inhibit PIO Bus A cable fault errors
Inhibit Peripheral Channel B Black “IB” Inhibit PIO Bus B cable fault errors
Inhibit Peripheral Black “IAB” Inhibit PIO Bus A and B cable fault errors
Channels A and B
Overview of System Management Display Windows

This section contains an alphabetical list of all the displays in System Management. The descrip-
tion of each display includes cross references to procedures and other information associated with
that display. The displays are:
 “Address Translation Station (ATS) Network Display Overview” on page 28
 “Carrierband LAN Display Overview” on page 29
 “Configuration Information Display Overview” on page 30
 “Equipment Change Display Overview” on page 31
 “Equipment Information Display Overview” on page 33
 “Inhibited Information Display Overview” on page 35
 “Intelligent Devices Display Overview” on page 36
 “Multiple Bus Display Overview” on page 36
 “Nodebus Display Overview” on page 37
 “Off-Line Diagnostic Display Overview” on page 38
 “On-Line Diagnostics Display Overview” on page 39
 “Performance Options Display Overview” on page 40
 “Peripheral Counters Display Overview” on page 41
 “Peripheral Names and Types Display Overview” on page 43
 “PIO Network and PIO Subnetwork Overview” on page 44
 “Set Date and Time Display Overview” on page 45
 “Station Display Overview” on page 46
 “Switch Domain Display Overview” on page 46
 “Switch Ports Display Overview” on page 47
 “Switched Network Overview” on page 49
 “System Alarm Display Overview” on page 49
 “System Management Counter Categories Display Overview” on page 50
 “System Management Counters Displays Overview” on page 50.
27
Address Translation Station (ATS) Network Display Overview

The Address Translation Station (ATS) Network Display (Figure 2-7) is the highest level network
display for a multi-node system using ATS modules. This display lists all of the ATS modules con-
figured in the system. This display is available only for systems that have ATS modules. I/A Series
systems that are pre-8.0C software release show the ATSs of nodes that don’t have LIs (see “Carri-
erband LAN Display Overview” on page 29).
Any red letter codes in this display indicate hardware faults.
NOTE
For more information on the Address Translation Station, refer to Address Transla-
tion Station User's Guide (B0700BP).
From this display, you can access other displays related to the selected ATS module.
Related Information
 “Responding to Alarms” on page 63
 “Viewing Configuration Information” on page 69
 “Equipment Information Display” on page 72
 “Performing Equipment Changes” on page 139.
28
Figure 2-7. ATS Network Display
Carrierband LAN Display Overview

The Carrierband LAN Display (Figure 2-8) is the highest level network display for a multi-node
system using Carrierband LAN Interface (LI) stations. This display shows a graphical representa-
tion of all the LI stations logically attached to the Carrierband LAN or fiber optic LAN. The first
LI station on the LAN is always preselected in this display.
The order of LIs shown in this display does not indicate the order of physical connections on the
bus.
Any red letter codes in this display indicate network communication hardware faults. When there
is no special text, all cables, transmitters, and receivers shown in the stations of the display are
operational.
From this display, you can access other displays related to the selected LI station.
Related Information
29
 “Performing Equipment Changes” on page 139

 “Running On-Line Network Diagnostics” on page 163.
NOTE
You cannot access the Equipment Change Display for a station that has an
unknown status, as indicated by letter codes.
Figure 2-8. Carrierband LAN Network Display for Multi-Node System (Typical)
Configuration Information Display Overview

The Configuration Information Display (Figure 2-9) contains system domain and network con-
figuration information for selected stations. You can use the information shown in this display
when verifying conditions from system health displays or network health displays, before you per-
form any actions, and when diagnosing system problems.
For example,
 Through system health displays, you can access the name of the Nodebus on which
the currently selected station resides.
 Before rebooting a station, you can verify the name of its boot host AP and then use
the various system displays to verify the health status of the AP.
Related Information
30
 “Configuration Information” on page 71.
Figure 2-9. Configuration Information Display
Equipment Change Display Overview

You can use the Equipment Change Display (Figure 2-10 and Figure 2-11) to perform equipment
status operations on selected stations or peripheral devices. Only workstations designated (during
System Monitor configuration) to perform secured actions on selected devices can access the
Equipment Change Display.
The Equipment Change Display for the Primary FBM indicates the operator-initiated selection
for the PIO bus (Fieldbus).
The list of change actions available from the Equipment Change Display differ between stations
and peripherals.
! CAUTION
Only designated personnel, aware of the effects of making equipment changes,
should initiate equipment changes.
Related Information
 Chapter 8 “Calibrating Equipment”.
31
NOTE
You can access the Calibrate Actions Display only for intelligent devices, or for
Hydrostatic Tank Gauge Interface Units (HIUs).
Figure 2-10. Equipment Change Display for Stations
32
Figure 2-11. Equipment Change Display for Peripherals
Equipment Information Display Overview

The Equipment Information Display (Figure 2-12 and Figure 2-13) contains information for
selected stations or peripherals, including configuration information, current health status, equip-
ment change action status information, and hardware and software information.
When the key is available, there is a faulted device that this workstation is configured to acknowl-
edge. Use the ACK key to acknowledge the health status of that device.
Information about PIO Bus (Fieldbus) Selection

The Equipment Information Display for a selected FBM indicates the last cable access status for
both Cable A and Cable B. The Equipment Information Display for the Primary FBM (also IIT)
indicates the active bus, the switch mode (as enabled or disabled), if periodic switching is cur-
rently enabled, and if the operator selection for the PIO bus (Fieldbus) is periodic switching.
Related Information
 “Equipment Information Display” on page 72.
33
Figure 2-12. Equipment Information for a Station (Page 1 of 2)
Figure 2-13. Equipment Information for a Primary Fieldbus Module (Page 1 of 2)
34
Inhibited Information Display Overview

This display (Figure 2-14) lists all equipment on the network for which alarming is inhibited.
This equipment includes all cables (Address Translation Station, Carrierband LAN, Nodebus, and
Fieldbus), station transmitters/receivers, (Address Translation Station, Carrierband LAN and
Nodebus), stations, and devices. Manually refresh this display to view the most current list of
inhibited equipment.
You use the alarming inhibit capabilities to permit or prohibit alarming for selected equipment.
By inhibiting alarming, you filter alarm conditions for the defined equipment such that the Sys-
tem Monitor continues to indicate overall system and network health even while equipment is
failed or off-line.
The system does not send alarm messages to the printer or Historian for equipment with alarming
inhibited.
Alarm Inhibit States for Healthy Equipment

You can inhibit alarms for healthy equipment. For the equipment on which you inhibit alarms,
you need to re-enable alarming manually when necessary.
Related Information
 “Viewing Equipment with Inhibited Alarming” on page 68.
Figure 2-14. Inhibited Alarming Information
35
Intelligent Devices Display Overview

The Intelligent Devices Display (Figure 2-15) lists the color-coded letterbugs of each intelligent
device attached to an FBM18, FBM39, FBM43, FBM44, or FBM46.
Related Information
 Chapter 8 “Calibrating Equipment”.
Figure 2-15. Intelligent Devices Display
Multiple Bus Display Overview

The Multiple Bus Network Display shows a graphical representation of the hardware configura-
tion of a station and its peripheral attachments. The secondary device graphic appears different
when there are attached devices. This display shows either physical (PIO device) or logical
(Allen-Bradley, GE, or Modicon device) letterbugs for the related stations or peripherals.
NOTE
Only black/white alarm printers show up in this display; color InkJet™ printers do
not appear in this display.
Related Information
36

Nodebus Display Overview

The Nodebus Display (Figure 2-16) shows different information depending upon the type of
system.
Single-Node Systems
For single-node systems, this display shows a graphical representation of all the stations connected
to the Nodebus. If this is a single node system, this is the top network display (that is, there is no
Carrierband Display or ATS Display).When you first access this display, the first station on the
Nodebus is always preselected.
Multi-Node Systems
If the domain has an ATS and an LI in the domain and the ATSs have been selected, you can
access the Nodebus Display via the ATS Network Display. If the domain has an ATS and an LI,
the Nodebus Display shows:
 The ATS module that connects the selected Nodebus to The MESH, and all the sta-
tions attached to that Nodebus. The title bar indicates the ATS module to which the
Nodebus is attached. (When you first access this display, the ATS module on the
Nodebus is always preselected.)
If the domain has an LI but no ATS and the LI Nodebus has been selected, the Carrierband LAN
display appears. The Carrierband LAN display shows:
 The LI station that connects the selected Nodebus to the LAN, and all the stations
attached to that Nodebus. The title bar indicates the LI station to which the Nodebus
is attached. (When you first access this display, the LI station on the Nodebus is
always preselected.)
If there is an ATS but no LI, in the domain, you can access the Nodebus Display via the ATS Net-
work Display. If the domain has an ATS and no LIs, the Nodebus Display shows:
 The ATS module and all the stations attached to that Nodebus. The title bar indicates
the ATS module to which the Nodebus is attached. (When you first access this dis-
play, the ATS module on the Nodebus is always preselected.)
Understanding the Nodebus Display

Any red station outlines, red cables, or red letter codes indicate network communication hardware
faults. When there is no special text, all cables, transmitters, and receivers shown in the stations of
the display are operational.
An SGL letter code appears above station graphics for stations with devices attached via a single
cable (that is, ThinNet).
From this display, you can access other displays related to the selected station.
37
Related Information
Figure 2-16. Nodebus Display
Off-Line Diagnostic Display Overview

The Off-Line Diagnostic Display (Figure 2-17) contains diagnostic tests for a selected station.
You can use off-line diagnostic tests to verify the proper operation of the station components.
Off-line diagnostic tests are station specific; when the Off-Line Diagnostic Display appears for a
selected station, the display shows only those tests available for that station.
You can run off-line diagnostics locally (across the Nodebus) and remotely (across the Carrier-
band LAN or fiber optic LAN via an Address Translation Station). Personal workstations and
Solaris based stations do not support off-line diagnostics.
You use the EXEC ONCE, EXEC ALL, and EXEC LOOP soft keys to run the off-line diagnostic
tests.
Related Information
 “Performing Off-Line Diagnostics” on page 166.
38
Figure 2-17. Off-Line Diagnostic Display
On-Line Diagnostics Display Overview

The On-Line Diagnostics Display (Figure 2-18) contains on-line diagnostic tests specific to a
selected network display.
The on-line diagnostic tests available differ based on network type, and include the following:
 Cable testing
 Enabling or inhibiting alarms
 Viewing the current Nodebus master
 Selecting a station as the Nodebus master
 Selecting the default Nodebus master.
For example, if you access this display from the Carrierband LAN or Nodebus Displays, you can
run Nodebus or tokenbus tests; if you access this display from a PIOM-type display (for an
FBM0), you can inhibit PIO cable alarms.
You can use the On-Line Diagnostics Display to test Carrierband LAN cables and the Nodebus
cables on-line.
Related Information
Figure 2-18 is an example of Carrierband LAN diagnostics; for Nodebus diagnostics example see
“Running On-Line Network Diagnostics” on page 163.
39
Figure 2-18. Carrierband LAN On-Line Diagnostics Display
Performance Options Display Overview

The Performance Options Display (Figure 2-19) contains access to the system management per-
formance displays. The performance displays contain information about system and peripheral
counters for selected stations.
Related Information
 “Accessing the Performance Options Display” on page 115.
40
Figure 2-19. Performance Options Display
Peripheral Counters Display Overview

The Peripheral Counters Display (Figure 2-20 and Figure 2-21) shows current information for
each peripheral counter. The types of counters associated with a peripheral vary according to the
peripheral group. For example, the types of counters associated with a printer or terminal differ
from the types of counters associated with FBMs.
Related Information
 “Viewing Peripheral Device Counters” on page 130.
NOTE
To reset counters, you must be using a workstation configured to have access to
secured actions.
41
Figure 2-20. Example of Peripheral Counters Display for an FBM
Figure 2-21. Example of Peripheral Counters Display (Page 1 of 2) for a Switch
42
Peripheral Names and Types Display Overview

The Peripheral Names and Types Display (Figure 2-22 and Figure 2-23) shows the letterbug and
type of each peripheral attached to a selected station. The letterbugs and types are color-coded in
the Peripheral Names and Types Display to indicate the health status of the related peripheral.
From this display, you can access the Peripheral Counters Display containing current information
about a selected peripheral counter, including the communication performance of any peripheral
attached to the selected station.
Related Information
 “Peripheral Names and Types Display” on page 131.
Figure 2-22. Example of Peripheral Names and Types Display for FBMs
43
Figure 2-23. Example of Peripheral Names and Types Display for Switches
PIO Network and PIO Subnetwork Overview

The PIO Network Display (Figure 2-24) shows the logical attachment of the FBMs, HIUs, dis-
play stations, or integrators to a Fieldbus associated with a CP, TP, DP, or the gateway station sup-
porting a PIO bus. This display indicates the last FBM access failure (A, B, AB) for each FBM,
the active bus, and the current bus mode.
Letter codes in the display indicate channel access faults for the active PIO bus (Fieldbus), the
current Fieldbus operation mode, and any FBM/peripheral failures.
From this display, you can access other displays related to the selected station or peripheral.
Related Information
44
NETWORK
Figure 2-24. PIO Network Display
Set Date and Time Display Overview

The Set Date and Time display contains controls for setting the date and time for the entire net-
work as well as the local station. Normally, you use this display only during initial start-up
procedures.
During System Management configuration, you define the date format as either
US (MM-DD-YY), ISO (YY-MM-DD), European or UR (DD-MM-YY). You cannot change
this format in the Set Date and Time display.
! CAUTION
Resetting the time can affect other activities on the network, such as Historian col-
lection, trending, reporting, and the CP10 CALC block TIM parameter. Only
authorized personnel should set the time or date.
To keep all stations on the node synchronized, you must make time and date changes through the
Set Date and Time display instead of through the system Adjust Time/Date function.
Time can not be set if the timekeeper is externally sourced using a Global Positioning System
(GPS). Access to the Set Date and Time display is not allowed by disabling the TIME soft key.
Time is automatically synchronized to the GPS system.
Related Information
 “Controlling Date, Time and Time Zone” on page 53.
45
Station Display Overview

The Station Display (Figure 2-25) contains graphical representations of the hardware and periph-
eral configuration for a selected station. You use this display to view the station configuration and,
if necessary, access other displays.
This display indicates fault-tolerant stations with the label FT. The letterbug and device type of
each station or peripheral shown in this display are color-coded to indicate hardware health.
Related Information
 “Identifying Alarms” on page 63
 “Acknowledging Alarms” on page 65
 “Inhibiting Alarms” on page 66
Figure 2-25. Station Display for AP50
Switch Domain Display Overview

When you select a switch from the Switched Network display, the Switch Domain display
(Figure 2-26) appears. This display shows all I/A Series stations (excluding other switches)
attached to the selected switch and the selected switch itself.
46
When you select the parent switch or station icon, the following options are available:
 EQUIP CHG
 EQUIP INFO
 NEXT LEVEL
 CONFIG INFO
Related Information
Figure 2-26. Switch Domain Display
Switch Ports Display Overview

The Switch Ports display (Figure 2-27) shows each port of an Ethernet switch. A typical Switch
Ports Display for a 16-port switch is shown in Figure 2-27. The Switch Ports Display, displays a
maximum of 32-ports on one screen. Paging is enabled so that more than 32-ports can be shown
on the display.
Switch status is displayed as shown in Table 2-12. Port status is displayed as shown in Table 2-13.
47
Table 2-12. Switch Status Indicators
Status Indicator Switch Status Condition

Fill White Healthy Switch is functioning normally.
Fill Red Failed Switch is failed.
Fill Yellow Warning Switch warning or a port is failed.
UNACK Symbol Unacknowledged Switch failure or port failure is unacknowledged.
Table 2-13. Port Status Indicators
Status Indicator Switch Status Condition

Fill White Healthy Port is functioning normally.
Fill Red Failed The actual Port state is failed.
Fill Cyan Off-line The Port is off-line.
UNACK Symbol Unacknowledged Port failure is unacknowledged.
Related Information
Figure 2-27. Switch Ports Display
48
Switched Network Overview

The Switched Network display (Figure 2-28) appears when you select the SW NETWORK soft
key in the initial system health display. This display shows all the configured Ethernet switches in
the system.
Related Information
Figure 2-28. Switched Network Display
System Alarm Display Overview

The System Alarm Display (Figure 2-29) lists station failures, and devices and cables that are in
system alarm condition. This display does not show any failed equipment for which alarming is
inhibited.
To view the most current alarm information, you must manually refresh this display.
You can also view unacknowledged equipment with unacknowledged alarms in the System Alarm
Display.
Related Information
 “Inhibiting Alarms” on page 66.
49
Figure 2-29. System Alarm List
System Management Counter Categories Display Overview

The System Management Counter Categories Display contains access to the System Management
Counter Displays for station-specific counter information.
System Management counters provide information relating to the communication performance
of the station, and of the station within the network. These cumulative counters represent com-
munication events.
Examples of communication events include the number of successful transmissions, the number
of retries, and the number of messages dropped.
Related Information
 “Monitoring Performance” on page 115.
System Management Counters Displays Overview

The System Management Counters Displays contain communication performance information
for selected stations. These displays identify how the station is performing within the network and
within the different layers of the network communication software protocol.
System counters are cumulative counters representing communication events that occur on the
network. These counters track communication events such as transmission errors, starts, retries,
and stops.
These displays show information specific to the following network communications layers:
 “MAC Sublayer” on page 119
 “Network Layer” on page 122
 “Transport Layer” on page 123
 “Application Layer” on page 126.
50
In addition, you can view station loading parameters. These parameters provide static counter
information related to communications sizing.
Related Information
 “Monitoring Performance” on page 115.
System Monitor Displays

Depending on the configuration of your system, one of the following displays appears as the ini-
tial or home display:
 System Monitor Domain Display
 System Monitor Domains Display
 System Monitors Display.
These displays are shown in “Viewing the Initial Display” on page 12.
The top menu bar on the initial displays has the following selections, which initiate the following
actions:
 ACK ALL, located on the System Monitor Domains Display and the System Monitor
Domain Display, acknowledges unacknowledged equipment failures (either failed or
returned-to-normal). System equipment faults are indicated on the system health dis-
plays and result in the SYS field changing to red as well as the field flashing until all
faults are acknowledged.
On the System Monitor Domains Display, ACK ALL acknowledges all the unac-
knowledged equipment within the System Monitor Domain(s) for which the worksta-
tion is responsible. On the System Monitor Domain Display, ACK ALL acknowledges
only that single System Monitor’s equipment faults.
ACK ALL is selectable if the workstation has been designated to perform secured
actions. (See “System Management Display Security” on page 19.)
 ACK, located on the Equipment Information Display, acknowledges the failure of the
selected device (station or peripheral). ACK is selectable only if the currently selected
device needs to be acknowledged and the workstation is designated to perform
secured actions. (See “System Management Display Security” on page 19.)
Related Information
 “Inhibiting Alarms” on page 66
 “Viewing Equipment with Inhibited Alarming” on page 68
 “Controlling Date, Time and Time Zone” on page 53
 “Inhibit or Enable Station Alarming Actions” on page 144.
51
52
3. Controlling Date, Time and Time
Zone
This chapter describes how to set and control the date, time and time modes for networks and
local stations.
The date, time and time zone within an I/A Series system can be set or changed as follows
 On The MESH network with an external Global Positioning System (GPS), the time
and date is set and controlled automatically by the I/A Series system. The user, how-
ever must set the time zone settings using the Windows Time Applet on Windows
workstations or by editing the /etc/TIMEZONE file on Solaris workstations.
 On The MESH network with no external GPS, the time and date is set via SMDH.
The user, however, must set the time zone settings using the Windows Time Applet
on Windows workstations or editing the /etc/TIMEZONE file on Solaris
workstations.
 On a Nodebus network the time and date is set via SMDH and the time zone settings
are set using the Window’s Time Applet. The time zone is set to Greenwich Mean
Time (GMT) Casablanca, Monrovia.
 On a mixed network system (The MESH and Nodebus) time and date is set and con-
trolled by The MESH system. Window’s Time Applet setting for time zone setting for
each network still apply.
Nodebus Daylight Savings Time (DST) adjustment is only supported if an Address Translation
Station (ATS) is installed in the system.
Setting Time from SMDH

The Set Date and Time Display contains controls for setting the date and time for the entire
Nodebus and The MESH network as well as the local station. Normally, you use this Display only
during initial startup procedures. Time and date can not be set if the timekeeper is externally
sourced using a Global Positioning System (GPS). Access to the Set Date and Time Display is not
allowed by disabling the TIME soft key. Time is automatically synchronized to the GPS system.
! CAUTION
Resetting the time can affect other activities on the network, such as Historian col-
lection, trending, reporting, and the CP10 CALC block TIM parameter. Only
authorized personnel should set the time or date.
To keep all stations on the node synchronized, you must make time and date
changes through the Set Date and Time Display instead of through the system
Adjust Time/Date function. You can use the Set Date and Time Display to set the
date and time for the entire network, as well as for the local station.
53
B0193JC – Rev U 3. Controlling Date, Time and Time Zone
During System Management configuration, you define the date format as either
US (MM-DD-YY), ISO (YY-MM-DD), European or UR (DD-MM-YY). You cannot change
this format in the Set Date and Time Display (Figure 3-1).
Figure 3-1. Set Date and Time Display
Procedure for Setting the Date and Time from SMDH

In a networked workstation configured to perform secured actions, you can access the Set Date
and Time Display from any initial health display, such as:
 System Monitor Domains Display
 System Monitors Display
 System Monitor Domain Display.
To set time from an initial health display:
1. Click TIME.
NOTE
Date and time can not be set if the timekeeper is externally sourced using a Global
Positioning System (GPS). Access to the Set Date and Time Display is not allowed
by disabling the TIME soft key.
2. From the Set Date and Time Display, select new values for the month, day, year, hour,
minute, and second as follows:
54
3. Controlling Date, Time and Time Zone B0193JC – Rev U
 Click the large arrows to increase or decrease the date and time numbers by five.
 Click the small arrows to increase or decrease the date and time numbers by one.
3. Click RETURN – SET to accept the network date and time you select. To cancel your
date and time selection, click RETURN – CANCEL.
Setting Time Zone on The MESH Workstations

Setting Time Zone on The MESH Windows Workstations
The time zone for each Windows-based workstation on The MESH is set using the Windows
Date/Time applet. The Windows Date/Time applet contains three tabs. The Date & Time tab
allows you to change the current time and date but should not be used. The Time Zone tab allows
you to set a time zone. The Internet Time tab triggers time synchronization but should not be
used.
If you select the Internet Time tab always exit via the Cancel button. Exiting via the OK button
(as opposed to the Cancel button) automatically starts the Windows Time service when you
reboot the workstation. The Windows Time service should always be set to Disabled; otherwise,
the workstation’s time settings may fluctuate unpredictably.
! CAUTION
Do not exit the Internet Time tab by clicking the OK button. Use the Cancel button
or simply close the applet.
To set the time zone for each MESH workstation:

1. Double click the displayed time on the windows task bar.
The Date and Time Properties display appears.
2. Click the Time Zone tab on the Date and Time Properties display.
3. The Time Zone display appears (see Figure 3-2).
55
Figure 3-2. Time Zone Display
4. Select the Time Zone from the drop down menu.

5. If desired, select Automatically adjust clock for daylight saving
changes.
6. Click OK.
Setting Time Zone on The MESH Solaris Workstations

The time zone for each Solaris-based workstation on The MESH is set by editing the
/etc/TIMEZONE file, which sets the TZ variable. Refer to Sun Microsystems documentation or
the “man” pages for information on “timezone”.
Nodebus Daylight Saving Time (DST) Adjustments

Introduction
I/A Series system release (V8.1 and later) supports the use of Address Translation Stations (ATS)
that connect The MESH control network to Nodebus networks. DST control is only supported if
an ATS is installed in the system. The Master Timekeeper (MTK) resides on The MESH and pro-
vides time updates to all stations on The MESH and Nodebus Networks. DST time adjustments
(Standard Time to Daylight Savings Time and vice versa) are automatically sent to all stations on
The MESH. Optional DST time adjustments are provided that allow an operator to determine
when DST time adjustments are sent to Nodebus stations. The operator can choose to have DST
time adjustments sent automatically or manually based on operator selections. These options
ensure backwards compatibility for I/A Series system releases with Nodebus Networks where the
operator decided when to manually change time via SMDH for DST adjustments. This feature
56
provides protection for applications (for example, Batch) where changing time backwards (from
Daylight Savings Time to Standard Time) could cause problems.
The following two attributes control sending DST time adjustments to Nodebus stations:
 DST Mode (MANUAL / AUTO)
 Nodebus Time Mode (STANDARD / DAYLIGHT)
MANUAL DST Mode that requires operator manual intervention for Nodebus sta-
tions to change from Standard Time to Daylight Savings Time and vice
versa. Time changes from Standard Time to Daylight Savings Time in the
spring and reverts back to Standard Time in the fall.
AUTO DST Mode that will cause Nodebus stations to automatically track time of
The MESH stations when they change from Standard Time to Daylight
Savings Time and vice versa.
STANDARD Standard Time: time in any of 24 time zones, usually the mean solar time
at the central meridian of each zone. In the continental USA, there are
four standard time zones: Eastern, Central, Mountain, and Pacific.
DAYLIGHT Daylight Savings Time: time during which clocks are set one hour or more
ahead of Standard Time to provide more daylight at the end of the work-
ing day during spring, summer, and early fall.
If DST Mode is MANUAL (default value), time sent to the Nodebus stations is based on Node-
bus Time Mode (default value is STANDARD) regardless if The MESH is in STANDARD or
DAYLIGHT time mode. The only way to change the Nodebus station times from Standard Time
to Daylight Savings Time or vice versa is for the operator to manually change the Nodebus Time
Mode via SMDH (see “Setting Time from SMDH” on page 53). If DST mode is AUTO, time
sent to the Nodebus stations is the same as The MESH time mode (STANDARD or DAY-
LIGHT).
Systems Management (SMDH) provides the following DST support:
 Changes to DST Mode (MANUAL/AUTO) via DST button
 Confirmation of selection on SMDH message line
 Changes to Nodebus Time Mode (STANDARD/DAYLIGHT) via DST button
 Changes can be made before or after actual DST changes occur on The MESH
 DST button selection (always pickable unless no ATS configured).
If DST Mode is AUTO, SMDH presents a pop-up box that allows selection to MANUAL
If DST Mode is MANUAL, SMDH presents a pop-up box that displays the current Nodebus
Time Mode and the current Time Mode on The MESH. The Pop-up box allows DST Mode
change to AUTO, or Nodebus Time Mode change to STANDARD / DAYLIGHT.
The message “Do not reboot any workstation for 1 minute” on the SMDH message line confirms
that the SMDH selection has been processed. The operator is warned not to intentionally reboot
workstations until 1 minute to allow all workstations to record the SMDH time selection thus
making the time selection persistent should a workstation later fail and a new Master Timekeeper
takeover. The worst scenario that could happen is that the Primary MTK workstation fails imme-
diately after a time selection is made and other workstations do not get a chance to record the new
time selection. This could result in the Nodebus stations going to the selected SMDH time state
57
and immediately reverting back to the previous time state when a new Master Timekeeper takes
over. The operator would have to repeat their desired time selection again.
! WARNING
Operators should only make DST changes via SMDH if all workstations that are up
and running are able to communicate on the network. Isolated workstations can
cause problems due to multiple MTKs.
MTK generates system messages indicating if The MESH and Nodebus networks are operating in
the same time mode (STANDARD vs. DAYLIGHT)
DST Procedures
Systems that use Address Translation Stations (ATS) to connect The MESH control network to
Nodebus Networks have a DST button on the System Monitor Domain Display (see Figure 3-3)
to access DST modes.
1. To access the DST modes from the System Monitor Domain Display, click DST but-
ton (see Figure 3-3).
Figure 3-3. System Monitor Domain with Daylight Savings Time Button
If the DST mode is Manual, a CURRENT DST TIME MODES pop-up box appears
(see Figure 3-4 and Figure 3-5). This pop-up box allows you to change the Nodebus
time mode or to change the DST Mode to AUTO. The following four combinations
of Nodebus and The MESH network time modes apply:
58
1. If the time mode of the Nodebus is STANDARD and The MESH network is
DST, the Nodebus is displayed as STANDARD TIME and The MESH network
is displayed as DAYLIGHT SAVINGS TIME (see Figure 3-4).
Figure 3-4. Current DST Time Mode
2. If the time mode of the Nodebus is DST and The MESH network is DST, the
Nodebus is displayed as DAYLIGHT SAVINGS TIME and The MESH network
is displayed as DAYLIGHT SAVINGS TIME (see Figure 3-5).
3. If the time mode of the Nodebus is STANDARD and The MESH network is
STANDARD, the Nodebus is displayed as STANDARD TIME and The MESH
network is displayed as STANDARD TIME (not shown).
4. If the time mode of the Nodebus is DAYLIGHT SAVINGS TIME and The
MESH network is STANDARD, the Nodebus is displayed as DAYLIGHT
SAVINGS TIME and The MESH network is displayed as STANDARD TIME
(not shown).
59
Figure 3-5. Current DST TIme Modes
2. If no change to the DST Mode or the Nodebus Time Mode is desired, click CANCEL.
3. To change the DST Mode or Nodebus Time Mode, click one of the following:
a. AUTO, (DST MODE)
Selecting AUTO will cause Nodebus stations to automatically track time of
MESH stations when they change from Standard Time to Daylight Savings Time
and vice versa.
b. NODEBUS: STANDARD TIME, (Time Mode)
Selecting NODEBUS: STANDARD TIME will cause Nodebus stations to
change from Daylight Savings Time to Standard Time.
c. NODEBUS: DAYLIGHT SAVINGS TIME (Time Mode).
Selecting NODEBUS: DAYLIGHT SAVINGS TIME will cause Nodebus sta-
tions to change from Standard Time to Daylight Savings Time.
4. After selecting the TIME MODE, the message “Do not reboot any workstation for 1
minute” on the SMDH message line confirms that the selection has been processed.
The operator is warned not to intentionally reboot workstations until 1 minute
expires to allow all workstations to record the SMDH time selection. The CUR-
RENT DST TIME MODES pop-up box will disappear.
5. To verify the time mode selections, click DST again.
If the mode of the system is AUTO, the pop-up displays CURRENT DST MODE IS
AUTO (see Figure 3-6).
60
Figure 3-6. DST Mode Auto
6. If you do want to change the DST Mode to MANUAL, click CANCEL.

7. To change the DST Mode to MANUAL, click: MANUAL.
Selecting MANUAL requires manual intervention for Nodebus stations to change
from Standard Time to Daylight Savings Time and vice versa.
8. Repeat steps 1 through 7 to change or review the DST Mode and Nodebus Time
Mode settings.
DST Examples
DST Example 1
On an initial V8.1 (or later) installation with ATS(s), the operator wants initial time settings dif-
ferent than the DST default values (default is MANUAL, STANDARD). There are 2 possible
changes - 1) AUTO, 2) MANUAL, DAYLIGHT.
1. Disconnect ATS from Nodebus stations.
2. Get The MESH system up and running.
3. Click DST button (see Figure 3-6).
4. Change DST Mode to AUTO or leave DST Mode in MANUAL and change Node-
bus Time Mode to DAYLIGHT (see Figure 3-4).
5. Connect ATS to Nodebus stations.
61
DST Example 2
To change the Nodebus Time Mode from Daylight Savings Time to Standard Time on an opera-
tional system because The MESH has just automatically changed from Daylight Savings Time to
Standard Time in the fall.
2. Verify Current Nodebus Time Mode is DAYLIGHT and Current Time Mode on The
MESH is STANDARD.
Time on Nodebus stations should be 1 hour or more ahead of stations on The
MESH.
3. Click NODEBUS: STANDARD TIME.
Time on Nodebus stations and stations on The MESH should now be the same.
DST Example 3
To change the Nodebus Time Mode from Standard Time to Daylight Savings Time on an opera-
tional system because The MESH has just automatically changed from Standard Time to Day-
light Savings Time in the spring.
2. Verify Current Nodebus Time Mode is STANDARD and Current Time Mode on
The MESH is DAYLIGHT (see Figure 3-4).
Time on Nodebus stations should be 1 hour or more behind stations on The MESH.
3. Click NODEBUS: DAYLIGHT SAVINGS TIME (see Figure 3-4).
Time on Nodebus stations and stations on The MESH should now be the same.
DST Example 4
To change the DST Mode to AUTO on an operational system so that The MESH and Nodebus
station times are always the same.
2. Click AUTO (see Figure 3-4 or Figure 3-5).
3. Click DST button.
4. Verify The MESH and Nodebus Time Modes are the same.
Time on Nodebus stations and stations on The MESH should be the same.
62
4. Responding to Alarms
This chapter covers system alarms and how to acknowledge, identify, respond, and inhibit those
alarms.
You have two choices for responding to alarms:
 From the System Monitor Domains Display or the System Monitor Domain Display,
click ACK ALL in the top menu bar to acknowledge all System Management equip-
ment failures for the domain or domains displayed.
 Access the System Alarm List Display to view and respond to alarms.
Acknowledging Alarms Collectively for a Domain

The letterbugs of any System Monitor domains with equipment failure states appear in the Sys-
tem Monitor Domains Display or System Monitors Display. You can globally acknowledge all
equipment failures.
You can view unacknowledged health changes only from workstations configured for fault notifi-
cation. Unacknowledged health changes for system equipment appear as blinking, color-coded
system monitor names and station letterbugs, and are shown with asterisks.
To acknowledge all faulted devices collectively:
 Click ACK ALL.
The station monitor names and station letterbugs return to their normal states. The system gener-
ates a low-priority event message for each device acknowledged.
Identifying Alarms
You can view a list of station failures, and all devices and cables currently in system alarm, from
either the System Monitor Domains Display, System Monitors Domain Display or System Moni-
tors Display.
63
B0193JC – Rev U 4. Responding to Alarms
System Management
System System
System
Monitor Monitor
Monitors
Domain Domains
SAL
System
Alarm
Figure 4-1. System Monitor Domains Display Hierarchy
To view all station failures and devices and cables in system alarm condition:
1. Click SAL.
The System Alarm List Display appears with all station failures and devices and cables
in system alarm condition.
2. To view the most current alarm information, click the REFRESH soft key to manually
refresh this display.
NOTE
The System Alarm List Display does not show any failed equipment for which
alarming is inhibited.
The initial System Alarm List Display shows all system alarms including acknowl-
edged alarm.
3. To view only the equipment with unacknowledged alarms in the System Alarm Dis-
play, click the DSP UNACK soft key.
Figure 4-2 shows a System Alarm List Display with both acknowledged and unacknowledged
alarms. An asterisk indicates that the station 55AW51 has an unacknowledged alarm.
64
4. Responding to Alarms B0193JC – Rev U
Figure 4-2. System Alarm List Display
Acknowledging Alarms
In the System Alarm List Display, you can acknowledge all alarms shown, or only selected alarms.
Letterbugs or logical names representing the stations or peripherals in alarm appear in the display
with an asterisk (*).
The alarm acknowledge options, ACK, ACK ALL, and ACK CABLE, are available only if there
are related, unacknowledged system alarms which the System Management Display Handler is
permitted to acknowledge. In addition, ACK is available only if a selected alarm can be
acknowledged.
NOTE
The System Alarm List may display alarms that cannot be acknowledged from the
workstation that you are using. The alarms you can acknowledge depend on the
security mode in which the station is operating.
To acknowledge one alarm:

1. From the System Alarm Display, select the alarm entry. When the entry can be
acknowledged, it is highlighted in green.
2. Click ACK to acknowledge that alarm.
If you are only displaying unacknowledged alarms (DSP UNACK), the system
removes any alarms that you acknowledge.
65
B0193JC – Rev U 4. Responding to Alarms
Responding to Network Alarms

To acknowledge all unacknowledged, non-cable alarms from the System Alarm List Display:
 Click ACK ALL.
If you are only displaying unacknowledged alarms (DSP UNACK), the system removes any
alarms that you acknowledge.
Inhibiting Alarms
Inhibiting alarms causes the system to filter alarm conditions so that the System Monitor contin-
ues to indicate overall system and network health even while equipment is failed or off-line.
To inhibit an alarm:
1. From the System Alarm Display, select the alarm to inhibit.
2. Click INHIBIT. The inhibited alarm is removed from the list of alarms.
If successful, the inhibited alarm does not appear on the System Alarm List Display again until
you manually enable the alarm.
NOTE
You can also inhibit alarming when changing equipment or diagnosing network
problems. See Chapter 7 “Equipment Changes and Diagnostics”.
66
5. Monitoring the System
This chapter describes in detail how to monitor the system, including viewing equipment with
inhibited alarms, and configuration information. It also provides procedures on using
information displays for stations and peripherals, and explains displays and fields for each type.
Monitoring the system consists of:
 “Viewing Equipment with Inhibited Alarming” on page 68
 “Equipment Information Displays for Stations, Peripherals, FCMs and Switches” on
page 73.
Figure 5-1 shows the path and displays used for monitoring the system. Stations that are part of
an LAN Interface (LI) domain appear in the NETWORK view of the System Management Display
Handler (SMDH), while stations that are part of a switch domain appear in the SW NETWORK
view of SMDH. ATS modules appear in both the Network view and the Switch Network view.
System Monitors System Monitor System Monitor

Domain Domains
NETWORK SW NETWORK
ATS?
No Yes Switched
Network
CB LAN?
ATS
Yes No
Network
Switch
Ports
Carrierband
Nodebus
LAN
Figure 5-1. Displays and Path for Monitoring the System
Selecting the Network brings up the Carrierband LAN network, Nodebus view, or ATS Network
display, as appropriate. If there is a Carrierband LAN and Address Translation Stations on the sys-
tem, a dialog box (see Figure 5-2) is presented to select which view to use.
67
B0193JC – Rev U 5. Monitoring the System
Figure 5-2. ATS or LI Nodebus Dialog
Selecting SW NETWORK brings up The MESH control network and its associated displays.
Viewing Equipment with Inhibited Alarming

Overview of the Inhibited Information
You use the alarming inhibit capabilities to permit or prohibit alarming for selected equipment.
By inhibiting alarming, you filter alarm conditions for the defined equipment such that the Sys-
tem Monitor continues to indicate overall system and network health even while equipment is
failed or off-line. The system does not send alarm messages to the printer or Historian for equip-
ment with alarming inhibited.
The Inhibited Information Display lists all equipment on the network for which alarming is
inhibited. This equipment includes all cables (Carrierband LAN, Nodebus, and Fieldbus), station
transmitters/receivers, (Carrierband LAN and Nodebus), stations, switches, and devices. Manu-
ally refresh this display to view the most current list of inhibited equipment.
When a device has its system alarming capabilities disabled, SMDH shows a < symbol on three
levels, it’s parent, the device, and the system monitor name. If the parent of the device is an AW
with a direct connect printer and the alarming for the device is disabled, the disable symbol is only
seen on the device and system monitor name. You should use the Inhibited Information display to
see all stations and devices that have their alarming capabilities currently inhibited.
Viewing Equipment with Inhibited Alarming

To access the Inhibited Information Display:
1. From the System Monitor Domain Display or System Monitors Display, click
INH DISP.
The Inhibited Information Display appears (Figure 5-3).
68
5. Monitoring the System B0193JC – Rev U
Figure 5-3. Inhibited Information Display
2. To update the Inhibited Information Display, click REFRESH. An updated list of all
inhibited alarming information appears.
Viewing Configuration Information

Overview of the Configuration Information
The Configuration Information Display contains system domain and network configuration
information for selected stations. You can use the information shown in this display when verify-
ing conditions from system health displays or network health displays, before you perform any
actions, and when diagnosing system problems.
For example,
 Through system health displays, you can access the letterbug of the LAN Interface (or
Address Translation Station) to which the currently selected station is attached.
 Before rebooting a station, you can verify the name of its boot host AW or processor
and then use the various system displays to verify the health status of the AW or
processor.
Accessing the Configuration Information

You can access the Configuration Information Display from any network display, or from the Sta-
tion Display, for a station selected from an initial health display.
69
Accessing from a Network Display

To access the Configuration Information Display for Carrierband LANs or ATSs from a Network
display:
1. From either the Carrierband LAN Display, Nodebus Display, PIO Network Display,
Multiple Bus Display or Bus Display, select a station. If necessary, from the Carrier-
band LAN, Nodebus or Multiple Bus Displays, click NEXT LEVEL to display the next
network level display to access the station.
2. Click CONFIG INFO. The configuration information specific to the selected station
appears (Figure 5-4).
To access the Configuration Information Display for Ethernet Switches or ATS modules from a
SW NETWORK display:
1. From the Switched Network Display, Switch Domain Display, or Switch Ports Dis-
plays, click NEXT LEVEL to display the next network level display to access the station.
2. Click CONFIG INFO. The configuration information specific to the selected station
appears (Figure 5-5).
Accessing from a System Health Display

To access the Configuration Information Display from system health displays:
1. From either the System Monitor Domains Display or System Monitor Domain Dis-
play, select the station and click CONFIG.
The Station Display appears with that station preselected.
2. Click CONFIG INFO. The configuration information for the selected station appears.
Figure 5-4. Configuration Information Display for Carrierband LAN
70
Figure 5-5. Configuration Information Display for Ethernet Switches
3. Use the Return soft key (double triangle icon) to return to the previous display.
Configuration Information
Table 5-1 lists the equipment information displayed for a Carrierband LAN network and a Switch
network.
Table 5-1. Equipment Configuration Information
Field Description
STATION NAME Name (letterbug) of the selected station
TYPE Type of station selected
SMON NAME System Monitor name (letterbug) for the selected station
SMON AP NAME System Monitor host name (letterbug)
LI NAME The station name (letterbug) of the LAN interface or the Address
Translation Station for the selected Nodebus station
BOOT HOST Boot host name (letterbug) for the selected station
IP ADDR Internet Protocol (IP) Address such as, 158.128.081.001 for the
selected station in the switch network
SW CONNECTION The names (letterbugs) of the Ethernet switches that are connected to
the selected station such as, SW001, SW001B, SW002A, SW002B,
and so forth
71
Configuration Information Display Actions

From the Configuration Information Display you can:
 View the current configuration information regarding the selected station
 Return to the previous Network Display or Station Display.
Equipment Information Display

Overview of the Equipment Information Display
The Equipment Information Display contains information for selected stations or peripherals,
including configuration information, current health status, equipment change action status infor-
mation, and hardware and software information.
When the key is available, there is a faulted device that this workstation is configured to acknowl-
edge. Use the ACK key to acknowledge the health status of that device.
Information About PIO Network (Fieldbus) Selection

The Equipment Information Display for a selected FBM indicates the last cable access status for
both Cable A and Cable B. The Equipment Information Display for the Primary FBM (also IIT)
indicates the active bus, the switch mode (as enabled or disabled), if periodic switching is cur-
rently enabled, and if the operator selection for the PIO Bus (Fieldbus) is periodic switching.
Accessing Equipment Information Displays

You can access the Equipment Information Display from either the system health displays or the
network health displays. The Equipment Information Display is also directly accessible from the
NOTE
You cannot access the Equipment Information Display from stations with unknown
status.

To access the Equipment Information Display from a System Health Display:
1. From an initial system health display, select the letterbug of the station for which you
desire information.
2. Click CONFIG. The Station Display appears.
3. From the Station Display, select the graphical representation of the station or any
peripheral for which you want information.
4. Click EQUIP INFO. The Equipment Information Display appears.
Accessing from a Network Health Display

To access the Equipment Information Display from a Network Health Display:
1. From the network health display, select the desired station or peripheral.
72
2. Click EQUIP INFO. The Equipment Information Display appears with actions spe-
cific to the selected device (either a station or peripheral).
Accessing for NEXT LEVEL Intelligent Field Devices

To access the Equipment Information Display for NEXT LEVEL Intelligent Field Devices:
1. From the Station Display, click NEXT LEVEL.
2. In the displayed Intelligent Devices Display, select the intelligent field device and click
EQUIP INFO. The Equipment Information Display appears with information specific
to the device selected.
Equipment Information Display Actions

From the Equipment Information Display for the selected device it is possible to:
 Select the ACK key in the top menu bar to acknowledge the device, if faulted.
 View the current equipment information. See “Intelligent Field Devices Equipment
Information Fields” on page 215 for a description of the information available for the
various stations and peripherals.
 Select the EQUIP CHG soft key to access the Equipment Change options for the pre-
viously selected device.
 Select the Paging keys to access the next or previous page.
 Select the Return (double triangle icon) soft key to return to the Station Display.
Equipment Information Displays for Stations,

Peripherals, FCMs and Switches
Equipment Information Display for Station/Switch
The Equipment Information fields contain information specific to the station selected. The con-
tents of these fields may change under two conditions: when a status change occurs, or when the
display is recalled. The fields updated when a status change occurs are:
 RUN MODE  FAIL STATE

 FAIL ACK STATE  FT STATE
 FAIL DEV ATT  FAIL DEV ACK
 DIAG STATE  EE UPDATE STATE
 DOWNLOAD STATE  PRIMARY MODE/SHADOW MODE
 ALARMING STATE  MT REPORT STATE
 Power 1 and Power 2  CABLE
The following fields are also updated when a fault-tolerant or redundant station role change
(operator or system-initiated) takes place:
73
 PRIM ROM ADDRESS  SHAD ROM ADDRESS

 PRIM HARD PART  SHAD HARD PART
 PRIM HARD REV  SHAD HARD REV
 PRIM HARD DATE  SHAD HARD DATE
 PRIM EEPROM REV  SHAD EEPROM REV
NOTE
When a fault-tolerant or redundant module replacement takes place, it is necessary
to recall the display to access the equipment information fields associated with the
new module.
NOTE
If faults appear in any devices under a Control Processor (such as FBMs), the health
status of the Control Processor is set to the appropriate failed color (see “Under-
standing System Health Color-Coding” on page 21) with the “UNACK Symbol”
indicator.
The Control Processor’s Equipment Information Display will have FAIL DEV ATT
= YES, and FAIL DEV ACK = NOT ACKNOWLEDGED. However, the ACK
selection on top of the display is disabled so you will not be able to acknowledge this
fault for the CP on this display. The fault actually exists in the devices under the Con-
trol Processor (such as FBMs).
SMDH shows the Control Processor as failed with the “UNACK Symbol” indicator
to propagate the UNACK status to the System Monitor Display level, to allow you to
navigate to the fault more easily.
To acknowledge the alarms for the Control Processor, navigate to the System Moni-
tor Domains Display and select ACK ALL.
All other fields are static or change when the display is recalled.
STATION NAME
The station letterbug assigned during definition of system hardware is shown.
For stations with Windows 7, the default name shown is WSTA70.
For stations with Windows Server 2008, the default name shown is WSVR70.
TYPE
The type of station defined when the letterbug is assigned during the system definition phases.
Typical types of stations are:
Table 5-2. Station Types
Station Type Definition Graphic Name

A-B™ GW Redundant Redundant A-B Gateway (ABG-R)
Addr Trans Sta Address Translation Station (ATS)
74
Table 5-2. Station Types (Continued)

Addr Trans Sta Redundant Address Translation Station Redundant (ATS-R)
Allen-Bradley GW Allen-Bradley Gateway (ABG)
Allen-Bradley GW30 Allen-Bradley Integrator 30 (AB30)
Allen-Bradley GW30B Allen-Bradley Integrator 30B (AB30B)
Allen-Bradley Station Allen-Bradley Station (AB STA)
App Proc 20 Application Processor 20 (AP20)
App Procs 50, 51 Application Processors 50, 51 (AP50, AP51)
App Work Stas 50, 51 or 70 Application Workstations 50, 51,70 (AW50/AW51, AW70)
Comm Processor Communication Processor (CMP)
Comm Processor 15 Communication Processor (CMP15)
Cont Processor 10 Control Processor 10 (CP10)
Cont Processor 30B Control Processor 30B (CP30B)
Cont Processor 40B Control Processor 40B (CP40B)
Disp Sta Proc Display Processor (DP)
F Ctl Proc270 Field Control Processor 270 FCP270
Field Device Int Field Device System Integrator FDSI
NOTE: This is an FBM,
not a station.
Foreign Device GW Foreign Device Gateway (Gateway)
Foreign Device GW30A Device Integrator 30 (FD30)
Foreign Device GW30B Device Integrator 30 Style B (FD30)
Info Net Int 10 Information Network Interface (INI10)
Info Net Int 15 Information Network Interface (INI15)
Instrument GW Instrument Gateway (IG)
INTERSPEC 30 INTERSPEC Integrator 30 (IS30)
INTERSPEC 30B INTERSPEC Integrator 30B (IS30B)
LAN Interface Carrierband LAN Interface (LAN)
Modbus GW Modicon Gateway (MODG)
Modbus GW 30 Modicon Integrator 30 (MG30)
Modbus GW 30B Modicon Integrator 30B (MG30B)
Network Printer Network Printer with SNMP NETPRN
Pers Computer Personal Computer (PC)
S Interface Proc SPECTRUM Interface Processor (SIP)
S Intrfc Proc-R Redundant SPECTRUM Inter Proc (SIP-R)
S Slave Gateway SPECTRUM Slave Gateway (SSG)
75
Table 5-2. Station Types (Continued)

Sitewide LAN Int Sitewide LAN Interface (SLI)
SW w/16ports 16-Port Ethernet Switch SW16P
SW w/24 ports 24-Port Ethernet Switch SW24P
SW w/48 ports 48-Port Ethernet Switch SW48P,
Switch Displayed for N7 Ethernet Switch Switch
Tank Processor Tank Processor (TP)
Workstation Windows 7 Workstation WSTA70
Workstation Windows Server 2008 Station WSVR70
Work Sta Proc 20 Workstation Processor 20 (WP20)
Work Sta Proc 25J Workstation Processor 25 (WP25J)
Work Sta Proc 30 Workstation Processor 30 (WP30)
Work Sta Procs 50, 51, 70 Workstation Processors 50, 51, 70 (WP50, WP51, WP70)
Triconex Triconex ACM (TRICON)
Micro-I/A Micro-I/A Station (OMC)
Z Ctl Proc270 Z-Module Control Processor 270 ZCP270
NOTE
The fault-tolerant stations available include: AB30-FT, AP20-FT, CP10-FT,
CP30-FT, CP40-FT, CP60-FT, FCP270-FT, IS30-FT, MG30-FT, ZCP270-FT.
Redundant stations available include: ATS-R or LI-FT.
76
Figure 5-6. Equipment Information Display for Station
Figure 5-7. Equipment Information Display for Station (Continued)
77
RUN MODE
On-line or Off-line. This field is initially Off-line. It changes to On-line when the station reports
to the System Monitor after booting up. If reporting is disabled, the last known state appears in
this field.
RUN MODE and FAIL STATE should be viewed as separate, but related fields for some stations.
Although certain Equipment Change options change the RUN MODE to Off-line, they do not
fail the station. However, a failed station results in the RUN MODE changing to Off-line.
The field changes to Off-line if any of the following occur:
 A reboot of the station
 An EEPROM update or IMAGE update
 An off-line diagnostic request
 A physical pull/push of the station (requiring more than two minutes to come back
on-line)
 Any station hardware failure or communication failure that results in the station no
longer being able to send its internal reports for two minutes or more.
For fault-tolerant stations refer to the PRIMARY MODE and SHADOW MODE fields for the
current RUN MODE of each module of the pair.
FAIL STATE
Failed or Not Failed. This field is initially Not Failed. This field changes to Failed if any of the fol-
lowing occur:
 The operator selects the FAIL soft key after running off-line diagnostics.
 A hardware problem causes the station to fail for more than two minutes.
on-line) is performed.
longer being able to send its internal reports for two or more minutes.
Operator-initiated equipment change actions (REBOOT, EEPROM UPDATE) or off-line diag-
nostics change the RUN MODE to Off-line, but do not change the FAIL STATE to Failed.
For fault-tolerant stations, refer to the PRIMARY MODE and SHADOW MODE fields for the
current FAIL STATE of each module in the fault-tolerant pair.
FAIL ACK STATE

Acknowledged or Not Acknowledged. This field is initially set to Acknowledged. If the FAIL
STATE changes from Not Failed to Failed, the FAIL ACK STATE field changes to Not Acknowl-
edged to indicate this transition. Use the ACK key in the top menu bar of the Equipment Infor-
mation Display to acknowledge the selected faulted device or use the ACK ALL key in the top
menu bar of the initial System Management Display to acknowledge all the unacknowledged
devices for which the workstation has responsibility.
FT STATE
No Information for non-fault-tolerant stations; Operational or Non-Operational for fault-toler-
ant or redundant stations. If one of the two modules in the fault-tolerant or redundant pair is off-
line or failed, Non-Operational is specified.
78
ALARMING STATE
Indicates whether alarming is Enabled or Inhibited for the device. When alarming is Inhibited for
a device, the System Monitor still updates its status, but alarm messages are not logged to the
printer or the Historian.
FAIL DEV ATT

Yes or No. Yes is specified if one or more peripherals attached to the station are reported as failed.
FAIL DEV ACK

Acknowledged or Not Acknowledged. This field is initially set to Acknowledged. If any of the
attached devices become unacknowledged, the field changes to Not Acknowledged.
DIAG STATE
Diagnostics Active or Not Active. This field is initially set to Not Active. When off-line diagnos-
tics are selected, the status changes to Diag Active until either the RESTART or the FAIL soft key
is selected. For fault-tolerant stations, refer to the PRIMARY MODE and SHADOW MODE
fields for the current Diagnostic State.
EE UPDATE STATE
EE Updating or Not Updating. This field is initially set to Not Updating. When EEPROM
UPDATE or IMAGE UPDATE is selected under Equipment Change options, the status changes
to EE Updating until the action is completed. For fault-tolerant stations, refer to the PRIMARY
MODE and SHADOW MODE fields for the current EEPROM Updating State.
DOWNLOAD STATE
Downloading or Not Downloading. This field is initially set to Not Downloading. When the sta-
tion is rebooted via an operator-initiated request, the status changes to Downloading until the
action is completed. For fault-tolerant stations, refer to the PRIMARY MODE and SHADOW
MODE fields for the current Downloading State.
MAC ADDRESS
A six-octet Media Access Control (MAC) Address. To the networking protocol in the I/A Series
stations, this field specifies the MAC address of the Primary Station assigned during system
definition.
MT REPORT STATE
Enabled or Not Enabled or Not Configured. The I/A Series network can have only one Master
Timekeeper enabled at a time. Master Timekeeper application software is found in AWs only.
Other stations cannot have a Master Timekeeper configured. For stations/devices that can receive
a time strobe signal using the optional I/A Series Time Synchronization equipment, this field can
be as follows:
STATE Description
Pulsed STK Receiving UTC time from MTK and time
strobe from both ports A and B.
79
STATE Description
Sync_A_In_Fail Receiving UTC time from MTK and time
strobe only from port B.
Sync_B_In_Fail Receiving UTC time from MTK and time
strobe only from port A.
Sync_AB_In_Fail Receiving UTC time from MTK, but lost time
strobe from ports A and B.
Sync_not_Cfg Not configured as a Sync Pulse station.
AB Fail Not Configured Lost time strobe from ports A and B for more
-OR- than 48 hours and station has returned to
AB Fail Running Internal internal time keeper mode.
SM REPORT STATE
Report All, No Counters, or No Reporting. This refers to the type of internal reporting taking
place from the Station Manager to the System Monitor. The various states are selectable from the
Equipment Change Display ENABLE ALL REPORTS, ENABLE EXCEPTION REPORTS,
and DISABLE ALL REPORTS. The setting is typically Report All unless it was changed via the
PRIMARY MODE
Single Primary, Married Primary, EE Updating, Downloading, Failed, or Diags Active appears if
the station is fault-tolerant or redundant. No Information appears if station is not redundant or
fault-tolerant. If the station is not configured to be fault-tolerant or redundant, refer to the fields
on screen one for the latest status.
SHADOW MODE
Married Shadow, EE Updating, Downloading, Failed, Off-line, or Diags Active appears if the sta-
tion is fault-tolerant. No Information appears if the station is not configured to be redundant or
fault-tolerant.
PRIM ROM ADDRESS

A six-octet Media Access Control (MAC) Address. This field specifies the MAC address of the
Primary module assigned during manufacturing.
SHAD ROM ADDRESS

A six-octet Media Access Control Address. This field specifies the MAC address of the Shadow
module assigned during manufacturing.
STATION ADDRESS
A six-octet Media Access Control Address. To the networking protocol in the I/A Series stations,
this field specifies a unique MAC address for a fault-tolerant or redundant station pair. (LI FT sta-
tions have their own unique numbers. ATSs in the LI mode use the same unique numbers as LIs.)
PRIM HARD PART/SHAD HARD PART

PRIM HARD REV/SHAD HARD REV
PRIM HARD DATE/SHAD HARD DATE
Dates and revision levels are supplied by manufacturing.
80
PRIM EEPROM REV

EEPROM revision level is updated each time a new revision of EEPROM is performed through
the Equipment Change actions on the Primary module of a fault-tolerant pair.
SHAD EEPROM REV

the Equipment Change actions on the Shadow module of a fault-tolerant or redundant pair.
SOFTWARE VERSION
Indicates the release level of station software currently running in the station. Not currently used
on some stations such as FCP270, ZCP270, or ATS (see the paragraph “CABLE”).
CABLE
For the FCP270, ZCP270 or ATS, Fault or OK indicates the status of The MESH control net-
work Ethernet cables to/from ATS or the status of the Nodebus cable. If a fault in cable A or cable
B is detected, Fault appears in this field. The faulty Ethernet cable is identified on the SWITCH
DOMAIN DISPLAY and Nodebus cable is identified on the NODEBUS DISPLAY by the mne-
monic RA (Receive A), RB (Receive B), or RAB (Receive A and Receive B) appearing next to the
receive cable as shown below:
RA RB
Multiple cable failures from the same switch would suggest a failure of the switch.
Equipment Information Display for Network Printer

The Equipment Information Display for network printers is described below. As network printers
are treated as stations, their Equipment Information Displays share some of the same fields as the
stations (described in “Equipment Information Display for Station/Switch” on page 73). The fol-
lowing fields are specific to the network printer only.
The contents of these fields may change under two conditions: when a status change occurs, or
when the display is recalled.
 PRINTER STATUS  PRINTER QUEUE
 PRINTER NAME  BACKUP NAME
 NUM OF INPUT  NUM OF OUTPUT
 MARKER TECH  COLOR PRINTER
81
The following fields are only displayed when an alarm is raised for the network printer:
 ALERT SUB UNIT  ALERT SEVERITY
 ALERT DESCRIPTION
Figure 5-8. Equipment Information Display for Network Printer
82
Figure 5-9. Equipment Change Display for Network Printer
STATION NAME
This is the station’s letterbug.
RUN MODE
There are the same three states for a USB and network printer as with the previous versions of
I/A Series software. Possible states are:
STATE Description
ONLINE (white) Ready to print alarms
OFFLINE (cyan) Transition of a printer to or from the OFFLINE state can only be
achieved by manual user action
NOTE
USB and network printers cannot be put into the
OFFLINE state unless a print driver is loaded for
that printer, and the print driver is renamed to the
printer’s configured logical name (LP##).
83
STATE Description
Not FAILED (red) All other conditions. This could be:
 Print driver is un-installed or not installed, OR
 Print driver name does not match its LP name, OR
 Printer is not connected, OR
 Printer is not powered up, OR
 Printer has critical fault(s) that prevent printing
 Precedence of the FAILED vs. OFFLINE state has changed. For the above FAILED
conditions, operators can put the USB or network printer into the OFFLINE state.
This was not the case for previous versions of I/A Series software; for a condition that
could result in the FAILED state, the printer's status was either OFFLINE or
FAILED depending on the type of fault.
 The OFFLINE state for a printer is “persistent”. For a printer in the OFFLINE state,
a reboot of the printer's hosting computer results in the printer's status retaining its
OFFLINE state.
 If a USB or network printer does not have a print driver installed, and does not have a
configured backup printer, then no alarms are queued. Previously for serial and paral-
lel printers, there was always a driver installed and therefore the alarms were always
queued, or forwarded to a backup printer.
 If a USB or network printer does not have a print driver installed, but the configured
backup does have a print driver installed, then the alarms directed to this USB or net-
work printer will be forwarded to the configured backup printer.
 If a USB or network printer does not have a print driver installed, and its configured
backup printer is a USB or network printer that also does not have a print driver
installed, then the alarms are not sent by the alarm source (usually a CP, but could also
be a System Monitor).
PRINTER STATUS
This field indicates overall status of network printer. It can one of the following statuses:
STATE Description
Non-Critical Alert This indicates that one or more sub-units have a non-critical alert
active, such as “low paper”, “low toner” or “service requested.”
Critical Alert This indicates that one or more sub-units have a critical alert active,
such as “paper jammed”, “no paper”, “no toner” and “cover open”.
Unavailable The printer or sub-unit is unavailable for use. Typically, a trained ser-
vice person is necessary to resolve this issue.
Warmup The printer is preparing to go on-line.
Moving off-line The printer is preparing to go off-line.
Idle The printer or sub-unit is available, in idle state.
Active The printer or sub-unit is printing or performing another primary
function (sending a fax, etc.).
84
STATE Description
Busy The printer or sub-unit is performing a function and is not immedi-
ately available for printing or any other primary function.
Printer driver is Issue with the printer driver.
installed or not
PRINTER QUEUE
This field indicates that the printer is on-line or off-line and the following states (mutually
exclusive):
STATE Description
Pause An operator has selected off-line mode (printer queue is paused)
Ready An operator has selected on-line mode (printer queue is ready)
PRINTER NAME
The primary printer name. It is recommended that this be set to the printer’s LPxx logical name.
(Refer to Printer Installation for I/A Series Software V8.8 and Later (Windows 7 and Windows Server
2008 Platforms) (B0700EW).) Alternatively, this can also be set as the station’s letterbug or a user-
defined name. It is retrieved by an SNMP query.
BACKUP NAME
The backup printer name.
NUM OF INPUT
This field indicates the number of input trays in the printer. Each input tray provides a mecha-
nism for feeding paper (or other media) into the printer.
NUM OF OUTPUT
This field indicates the number of output trays in the printer. Each output tray provides a mecha-
nism for retaining the paper (or other media) on which the printer has printed.
MARKER TECH
The type of marking technology used in the printer.
COLOR PRINTER
This field indicates whether the printer supports color or not.
ALERT SUB UNIT

This field indicates the type of sub-unit in the printer which has the current alert. If there is no
alert, the field will not be displayed.
ALERT SEVERITY
The level of severity of the alert in the printer if there is an alert active for the printer.
ALERT DESCRIPTION
A description of the alert in the language set for the printer (provided by the printer’s
manufacturer).
85
Equipment Information Display for USB Printer

The Equipment Information Display for local printers attached by a USB port is described below.
USB printers are supported for systems with I/A Series software v8.8 or later.
As USB printers are treated as devices, their Equipment Information Displays share some of the
same fields as the devices. The following fields are available with the USB printer.
The contents of these fields may change under two conditions: when a status change occurs, or
when the display is recalled.
 NAME  TYPE
 RUN MODE  FAIL STATE
 FAIL ACK MODE  ALARMING STATE
 READY STATE  BACKUP NAME 1
 BACKUP NAME 2  SELECTED
 PAPER EMPTY  CLASS NAME
Figure 5-10. Equipment Information Display for UDB Printer
NAME
This field is the USB printer’s name which is configured by SysDef.
86
TYPE
This field should be “USB PRINTER”.
RUN MODE
There are the same three states for a USB and network printer as with the previous versions of
I/A Series software. Possible states are:
STATE Description
ONLINE (white) Ready to print alarms
OFFLINE (cyan) Transition of a printer to or from the OFFLINE state can only be
achieved by manual user action
NOTE
USB and network printers cannot be put into the
OFFLINE state unless a print driver is loaded for
that printer, and the print driver is renamed to the
printer’s configured logical name (LP##).
Not FAILED (red) All other conditions. This could be:

 Print driver is un-installed or not installed, OR
 Print driver name does not match its LP name, OR
 Printer is not connected, OR
 Printer is not powered up, OR
 Printer has critical fault(s) that prevent printing
 Precedence of the FAILED vs. OFFLINE state has changed. For the above FAILED
conditions, operators can put the USB or network printer into the OFFLINE state.
This was not the case for previous versions of I/A Series software; for a condition that
could result in the FAILED state, the printer's status was either OFFLINE or
FAILED depending on the type of fault.
 The OFFLINE state for a printer is “persistent”. For a printer in the OFFLINE state,
a reboot of the printer's hosting computer results in the printer's status retaining its
OFFLINE state.
 If a USB or network printer does not have a print driver installed, and does not have a
configured backup printer, then no alarms are queued. Previously for serial and paral-
lel printers, there was always a driver installed and therefore the alarms were always
queued, or forwarded to a backup printer.
 If a USB or network printer does not have a print driver installed, but the configured
backup does have a print driver installed, then the alarms directed to this USB or net-
work printer will be forwarded to the configured backup printer.
 If a USB or network printer does not have a print driver installed, and its configured
backup printer is a USB or network printer that also does not have a print driver
installed, then the alarms are not sent by the alarm source (usually a CP, but could also
be a System Monitor).
The system updates this field when a status change occurs.
87
You can change the RUN MODE using the GO ON-LINE and GO OFF-LINE options in the
RUN MODE and FAIL STATE should be viewed as separate, but related fields for some stations.
Although certain Equipment Change options change the RUN MODE to Off-line, they do not
fail the printer. However, a failed printer results in the RUN MODE changing to Off-line.
FAIL STATE
The system updates this field when a status change occurs. Possible states are:
STATE Description
Not Failed The USB printer is considered healthy and running as normal.
Failed Fatal hardware or other fatal fault reported by the USB printer.
Not Ready A transition state.
FAIL ACK STATE

Displays Acknowledged (default) or Not Acknowledged. If the FAIL STATE field changes from
Not Failed to Failed, the value in this field changes to Not Acknowledged. Click ACK in this dis-
play to acknowledge the selected faulted USB printer; or click ACK ALL in the initial System
Management Display to acknowledge all unacknowledged USB printers for which the
workstation is responsible.
ALARMING STATE
Indicates whether alarming is enabled or inhibited for this USB printer.
READY STATE
Indicates the overall status of the device. Possible states are:
STATE Description
Ready The USB printer is considered healthy and running as normal.
Not Ready Fatal hardware or other fatal fault reported by the USB printer.
BACKUP NAME 1
This field displays the first backup USB printer’s name if it is configured. Otherwise the field is
empty.
NOTE
BACKUP NAME 2 is unused.
SELECTED
This field indicates whether the Select or Online button on the USB printer is enabled. Possible
states are:
STATE Description
Yes The Select or Online button is enabled.
88
STATE Description
No The Select or Online button is not enabled or has been de-selected.
PAPER EMPTY
This field indicates whether paper has been fully loaded in the printer’s input tray or not. Possible
states are:
STATE Description
No The printer’s input tray has paper loaded on it.
Yes The printer’s input tray does not have paper loaded on it.
CLASS NAME
This field should be “PRTUSB”.
Equipment Information Display for Primary ECB (FBM0)

NOTE
This section describes the Equipment Information Display for the primary ECB
(FBM_0), which is actually the primary ECB (ECBP). For information on Equip-
ment Information Displays for non-primary FBMs, refer to “Equipment Informa-
tion for Fieldbus Module (FBM)” on page 96.
The following paragraphs describe the Equipment Information Display fields for the Primary
ECB (FBM0). These fields contain information specific to the selected primary ECB, which
resides in the station. The contents of these fields may change under two conditions: when a sta-
tus change occurs, or when the display is recalled. The primary ECB (FBM_0) fields updated
when a status change occurs are:
 RUN MODE  DEVICE STATE
 FAIL ACK STATE  ALARMING STATE
 ACTIVE PIO BUS (Fieldbus)  SWITCHING MODE
 PERIODIC SWITCH  PERIODIC CONFIG
 CP POWER 1  CP POWER 2
 SWITCHING MODE  DIAG STATUS 1
 PRIM CHK POINT  SHAD CHK POINT
 SELF HOSTING
All other fields are static, are updated when the display is recalled, or are unused.
89
Figure 5-11. Equipment Information Display for Primary ECB (FBM0)
Figure 5-11. Equipment Information Display for Primary ECB (FBM0) (Continued)
90
NAME
The letterbug of the station in which the primary ECB (FBM_0) is located.
TYPE
FBM 0 represents the primary ECB.
RUN MODE
On-line or Off-line. The primary ECBP is installed as On-line after it is “fixed” and configured.
For the primary ECB (FBM_0) located in a station or gateway, changing the FBM_0 status to
Off-line causes all communication to the Fieldbus, respective highway or converter box to stop.
Subsequently, all attached FBMs or gateway peripherals fail. As a result, a number of messages
appear at the printer indicating communication failures and peripheral equipment failures.
Changing an FBM peripheral or gateway peripheral status to Off-line causes communications to
that specific device to stop.
You can change the RUN MODE using the GO ON-LINE and GO OFF-LINE options in the
Equipment Change Display. If station reporting is disabled, the last known run state appears in
this field.
DEVICE STATE
The system updates this field when a status change occurs. The possible mutually exclusive states
are:
 Not Failed: The device is healthy.
 On Scan: The device is connected to the control strategy, though measurements are
not guaranteed to be good.
 Comm Failures: No real device information is available.
 Failed: Fatal hardware or other fatal fault reported by the device. Presupposes that
communication has not failed.
 Not Ready: A transition state. The device is healthy and normal automatic start-up
procedures are bringing the device On Scan.
 Out of Service: The device is healthy, but is operating in a mode incompatible with its
normal control functions.
FAIL ACK STATE

Displays Acknowledged (default) or Not Acknowledged. If the DEVICE STATE value changes
from Not Failed to Failed, the value in this field changes to Not Acknowledged.
Click ACK in this display to acknowledge the selected faulted device; or click ACK ALL in the
initial system management display to acknowledge all unacknowledged devices for which the
Not Acknowledged Status: Check printed/historical log for type of failure. To clear, click ACK or
ACK ALL on the configured application workstation (AW).
91
ALARMING STATE
Indicates whether alarming is enabled or inhibited for this device. When alarming is inhibited,
the System Monitor continues to indicate overall system and network health while equipment is
failed or off-line, and any system alarm messages are not logged to the system printer or to the
Historian.
Not Responding or Not Acknowledged status: Check the hardware.
DOWNLOAD STATE
This field does not apply to the primary ECB (FBM_0). It displays “Not Downloading” for
FCP270 and ZCP270.
DEVICES ATT and FAIL DEV ATT

This field does not apply to the primary ECB (FBM_0). It displays “No”.
ACTIVE PIO BUS

Indicates the current Fieldbus, either BUS A ONLY, BUS B ONLY, or BUS A&B AUTO. This
value is set initially to BUS A ONLY or to the value saved in the checkpoint file. If SWITCHING
MODE is enabled, this field updates automatically if you switch communications on the current
Fieldbus to the other Fieldbus. BUS A&B AUTO indicates that both Bus A and Bus B are active,
and the control processor determines which bus to use for each transaction.
For the Allen-Bradley Gateway, the Modicon Gateway or the Instrument Gateway, this field indi-
cates which port is being used for communications to the respective A-B Data Highway™ or
Modbus Highway. Bus A indicates Port 1 and Bus B indicates Port 2.
SWITCHING MODE
Displays Enabled (default) or Not Enabled. If Enabled, automatic switching can occur in the
event of a bus fault for the following modes: PERIODIC PIO BUS SWITCH and BUS AUTO
SELECT.
You can change this field to Not Enabled by selecting BUS A DISABL SWITCHING or BUS B
DISABL SWITCHING in the Equipment Change Display.
This field applies to the Allen-Bradley and Modicon Gateways, and does not apply to the Instru-
ment Gateway.
PERIODIC SWITCH
Displays Enabled (default) or Not Enabled, or the saved value in the checkpoint file. If Enabled,
periodic automatic switching between Bus A and B occurs every hour such that each bus is in
periodic use.
If a fault occurs, one of the following events takes place:
 The system selects the better bus and automatic switching (due to a fault) to the
RUN A or B ENABLED mode occurs. The PERIODIC SWITCH mode changes to
Not Enabled.
 The system determines both buses have an equal number of FBM failures. The
PERIODIC SWITCH mode remains Enabled.
92
PERIODIC CONFIG
Displays Yes if you configured the Run AB Periodic mode in the Equipment Change Display;
otherwise, displays No. The default is No. For FCP270 displays BUS AUTO SELECT.
DIAG STATUS 1
This field applies only to FBM_0s associated with the Allen-Bradley, Modicon, and Instrument
Gateways and FCP270.
 Gateways: Indicates the electrical status of Port 1 communications
 All other FBM_0s: The value 0 indicates this field is not applicable
 For FCP270:
 0 = CP Power 1 okay and CP Power 2 Okay
 1 = CP Power 1 Failed
 2 = CP Power 2 Failed
DIAG STATUS 2
This field applies only to FBM_0s associated with the Allen-Bradley, Modicon, and Instrument
Gateways.
 Gateways: Indicates the electrical status of Port 2 communications.
 All other FBM_0s: The value 0 indicates this field is not applicable.
DIAG STATUS 3
This field does not apply to FBM_0. Displays 0 for FCP270 and ZCP270.
DIAG STATUS 4
This field only applies to FBM_0s associated with the Allen-Bradley Gateway.
 Allen-Bradley Gateway: Represents A-B server task errors.
 All other FBM_0s: The value 0 indicates this field is not applicable.
HARDWARE TYPE
This field does not apply to FBM_0. Displays 0.
FIELD BUS A and FIELD BUS B

Displays OK or Not OK to indicate the status of communications over Ethernet fieldbus A or B.
PRIM CMD STAT

A number representing a communication status code. This field applies to a gateway primary
ECB (AB, MODG, and IG). The codes are as follows:
Code Explanation
0 No communication error
1 Communication error, but retry was successful
4 Communication error
40 Device failure
93
Code Explanation
70 8044 hardware fault
FBM CMD STATUS

This field does not apply to FBM_0. Displays 0.
FBM STATUS
This field does not apply to non-gateway stations. For a gateway station, the field may contain a
hexadecimal value representing an error code. Refer to the following Allen-Bradley, Modicon, and
Instrument Gateway lists for the FBM_0 error code. Displays 0 for FCP270.
This field applies to Allen-Bradley, Modicon, and Instrument Gateway stations only and contains
a hexadecimal value representing an error code.
Error Code Explanation of Codes for Allen-Bradley Gateway

1 through 9 LOCAL errors: those errors generated by the station interface module.
10 through f0 REMOTE errors: those errors generated by the target controller.
F8 SC_POST error: interface was unable to post to A-B driver.
F9 BAD_QUEUE: an unrecognized return queue has been detected.
FA FRAMING error: A-B driver routines detected a framing error.
FB RCV OVR error: A-B driver routines detected a RCV Buffer Overrun
error in the communications chip.
FC PARITY error: A-B driver routines detected a parity error.
FD NO ACK error: the CAM did not ACK our message transmission.
FE BCC error: A-B driver did not match the calculated BCC with the
transmitted BCC.
FF TIMEOUT error: A-B driver did not receive a response from the target
PLC.
Code Explanation of Codes for Modicon Gateway

1 through 9 LOCAL errors: errors generated by the station interface module.
(not used)
1 through ef REMOTE errors: errors generated by the target controller.
F1 BAD FNC: returned function code did not match transmitted function code.
F7 Used for message pass through; bad message size.
F8 SC_POST error: interface was unable to post to driver.
F9 BAD_QUEUE: an unrecognized return queue is detected.
FA FRAMING error: MOD driver routines detected a framing error.
FB RCV OVR error: MOD driver routines detected an RCV buffer overrun error
in the communication chip.
FC PARITY error: MOD driver routines detected a parity error.
94
Code Explanation of Codes for Modicon Gateway

FD BCC error: MOD driver did not match the calculated BCC with the transmit-
ted BCC.
FF TIMEOUT error: MOD driver did not receive a response from the target
PLC.
Code Explanation of Codes for Instrument Gateway

F7 Used for message pass through; bad message size.
F8 SC_POST error: interface was unable to post to driver.
F9 BAD_QUEUE: an unrecognized return queue has been detected.
FA FRAMING error: driver routines detected a framing error.
FB RCV OVR error: driver routines detected a RCV buffer overrun error in the
communications chip.
FC PARITY error: driver routines detected a parity error.
FE CRC error: CRC bytes do not match.
FF TIMEOUT error: did not receive a response from the controller.
LOGICAL ADDR
For gateways, the primary FBM logical address depends on the Communication Access
Module (CAM). This address is configured using the ICC or IACC.
For all other FBM_0s, the value 0 indicates this field is not applicable. Displays ff for FCP270
and ZCP270.
PRIM CHK POINT

SHAD CHK POINT
This field used to display the number of times the primary or shadow FCP270 or ZCP270 mod-
ule’s flash memory has been burned. Refer to Field Control Processor (FCP270) User’s Guide
(B0700AR) and Z-Module Control Processor 270 (ZCP270) User’s Guide (B0700AN) for addi-
tional information on self-hosting mode.
SELF HOSTING
This field is set to Enabled when the FCP270 or ZCP270 controller is in self-hosting mode (Bit 8
of the CFGOPT Station block parameter is set to 1), and Not Enabled when the controller is not
in self-hosting mode (Bit 8 of the CFGOPT Station block parameter is set to 0, the default).
To enable self-hosting in an FCP270 or ZCP270, use control configuration software to set the
self-hosting bit (Bit 8) of the CFGOPT parameter and issue a Checkpoint command. Refer to
Integrated Control Block Descriptions (B0193AX) for additional information on the CFGOPT Sta-
tion block parameter.
When the self-hosting capability of an FCP270 or ZCP270 is enabled, the controller can restart
and execute its configured control scheme without communicating with a host workstation. Refer
to Field Control Processor (FCP270) User’s Guide (B0700AR) and Z-Module Control Processor 270
(ZCP270) User’s Guide (B0700AN) for additional information on self-hosting mode.
95
CP POWER 1
OK or Failed indicates the state of primary power to FCP270. (This is not displayed for a
ZCP270).
CP POWER 2
OK or Failed indicates the state of secondary power to FCP270. (This is not displayed for a
ZCP270).
Fields Not Applicable to the Primary ECB

The following fields do not apply to the primary ECB.
 HARDWARE PART NO.  HARDWARE REV

 DATE  SERIAL NUMBER
 SOFTWARE REV  EEPROM REV
Equipment Information for Fieldbus Module (FBM)

The following fields are available for the Equipment Information Display for the I/A Series Field-
bus Modules (FBM0-199) and the DIN rail mounted Fieldbus Modules (FBM200-FBM299).
NOTE
For Equipment Information Display information relating to:
FBM220/221 refer to FOUNDATION fieldbus H1 Interface Module
(FBM220/221) User Guide (B0400FD).
FBM223 and related slave device information refer to
PROFIBUS-DP Communication Interface Module (FBM223) User’s Guide
(B0400FE).
FBM214/214b215/216/216b/218/244/245, the HART-capable FBM247 and
related slave devices refer to HART™ Communication Interface Modules User’s Guide
(B0400FF).
FBM224 refer to the Modbus Communication Interface Module (FBM224) User’s
Guide (B0400FK).
FCP270 refer to I/A Series FCP270 User’s Guide (B0700AR).
ZCP270 refer to I/A Series ZCP270 User’s Guide (B0700AN).
FBMs230/231/232/233 refer to I/A Series System Field Device System Integrators
(FBM230/231/232/233) User’s Guide (B0700AH).
FBM228 refer to FOUNDATION™ fieldbus User’s Guide for the Redundant
FBM228 Interface (B0700BA).
Address Translation Station User’s Guide (B0700BP).
96
NOTE
If both System Management and the Current Alarm Display (CAD) report the same
bad I/O condition, then the fault is in the I/O and not in the block software. If Sys-
tem Management does not report the same I/O failure as the CAD, then the point
value has been declared bad by the block software, and this can be caused by the
AIN block detecting an out-of-range signal.
NAME
Letterbug assigned to the FBM.
TYPE
This type is determined by the primary FBM when checking the devices on its Fieldbus. Refer to
the EXTENSION TYPE field for a listing of FBM Expansion Unit types.
Refer to the appendix “FBM - ECB Cross Reference” in Control Processor 270 (CP270) Integrated
Control Software Concepts (B0700AG) for the latest list of 100 Series and 200 Series FBM types.
RUN MODE
Displays On-line or Off-line (default). You can set the RUN MODE using the GO ON-LINE
and GO OFF-LINE options in the Equipment Change Display.
If station reporting is disabled, the last known FBM run state appears in this field.
If the field indicates an Off-line status:
 Check hardware.
 Download if necessary (that is, FBM).
 Check related fields, such as DOWNLOAD EEPROM UPDATE.
DEVICE STATE
are as follows:
 On Scan: The device is connected to the control strategy, but measurements may be
invalid.
 Failed: Fatal hardware or other fatal fault reported by the device. Assumes that com-
munication has not failed.
 Not Ready: A transition state indicating that the device is healthy and normal auto-
matic startup procedures are bringing the device On Scan.
 Out of Service: The device is healthy but is operating in a mode incompatible with its
If the field indicates a Failed status:
 Check peripheral hardware.
 Download if necessary.
97
FAIL ACK STATE

Click ACK in this display to acknowledge the selected faulted device; or click ACK ALL in the
initial system management display to acknowledge all unacknowledged devices for which the
If the field indicates a Not Acknowledged status:
 Check printed/historical log for type of failure.
 To clear, click ACK or ACK ALL on the configured workstation processor.
ALARMING STATE
Historian.
DOWNLOAD STATE
Displays Downloading if the FBM is downloading its application image; otherwise, displays Not
Downloading when the application image download is complete (successfully or unsuccessfully).
WARNING CONDITION
Displays Yes if the device has a non-fatal error condition; otherwise, displays No.
DEVICES ATT
Displays Yes if the peripheral has devices attached; otherwise, displays No.
LAST CABLE ACCESS

Reflects the health of both cables as follows: Both Cables OK, Cable A Not OK, Cable B
Not OK, or Both Cables Not OK. This field applies to the selected device and indicates whether
transmissions were successfully sent the last time either Bus A or B was used.
If the field displays a Not OK status, it indicates a PIO Bus send failure. To resolve:
 Check the PIO Bus.
 Switch to the other cable if the bus is bad.
FAIL DEV ATT

Failed Device Attached displays Yes if one or more peripherals attached to the station report as
failed; otherwise, displays No.
If the status is Yes, one or more of the attached peripherals have failed. Verify status of
peripherals.
98
COMPOUND NAME
Displays the compound name for the device.
FAIL DEV ACK

Displays Acknowledged (default) or Not Acknowledged. If any of the attached devices become
unacknowledged, displays Not Acknowledged.
If the status is Not Acknowledged, one or more of the attached peripherals has failed. To clear:
 Verify status of peripherals.
 To clear the failure and the asterisk (*) on the station, click ACK or ACK ALL on the
configured workstation processor.
BLOCK NAME
Displays the block name for the device.
DIAG STATUS 1
Diagnostic Status 1 is a hexadecimal value related to the previous FBM status error condition.
Typically this value is 4, indicating a previous non-fail-safe condition (green light condition).
For FBM200s:
Bit Position Set Condition Cause

Bit 0 No power (+24 V dc) on bus A Power Supply A Failure
Bit 1 No power (+24 V dc) on bus B Power Supply B Failure
For resolution of the FBM hardware and software errors indicated in the various diagnostic status
fields, contact IOM Global Customer Support at 1-866-746-6477 or visit the website at:
http://support.ips.invensys.com.
HARDWARE TYPE
Number associated with this FBM type.
DIAG STATUS 2
Diagnostic Status 2 is a hexadecimal value indicating the last FBM startup condition. The list of
possible starting conditions is related to hexadecimal bit settings. If the value is 0, there is no his-
tory of the last start condition; this indicates that there is an absence of data due to lack of com-
munications. If this is the case, all four diagnostic status bits are meaningless.
fields, contact the GPS center.
Diagnostic bits and the related conditions are as follows:
Hex Value Bit Position Set Condition

1 Bit 0 Cold start (power up)
2 Bit 1 Power fail recovery, cold reset recovery
99
Hex Value Bit Position Set Condition

4 Bit 2 Watchdog timer failure, if watchdog is not used
than diagnostic running (some FBM 200s)
8 Bit 3 Warm reset (equip change download)
0x10 Bit 4 Flash ROM contains fatal error information
0x20 Bit 5 PIO downloading (on some FBMs200s)
0x40 Bit 6 PIO warmstart (on some FBM200s)
0x80 Bit 7 PIO allocating memory (on some FBM200s)
SOFTWARE TYPE
Indicates the type of application software being used with the designated FBM hardware type.
NOTE
The FBM Software Type ID is not the ECB type. Also, any FBM module with
expansion ability can support any expansion unit; however, an FBM module typi-
cally supports an expansion unit with the same I/O type.
Refer to the appendix “FBM - ECB Cross Reference” in Control Processor 270 (CP270) Integrated
Control Software Concepts (B0700AG) for the latest list of ECBs and their associated hardware
(100 Series and 200 Series FBMs).
DIAG STATUS 3
Diagnostic Status 3 is a hexadecimal value relating to the previous software or hardware errors for
the selected FBM. It is the count of errors stored in Error Log (the maximum is 3F hex. and the
counter stops at 3F hex.)
HARDWARE PART NO.

The hardware part number related to this FBM.
DIAG STATUS 4
Hexadecimal value relating to the current software or hardware error for the selected FBM. (Typi-
cally, this value is 0.)
Hex Value Condition

00 OK
01 Did not become bus master (FPB10 only)
02 I/O gate array failure (FBP11-14, migration, FBM100s), Error at read
strobe (FBP10)
03 Clock generator failure (FBP11-14, migration, FBM100s), Error at write
strobe (FBP10)
04 Watchdog timer failure during cold start (FBP11-14, migration,
FBM100s), UART Rcv Error (FPB10)
05 WDT failure as part of WDT recovery diagnostics (FBP11-14, migration,
FBM100s), UART Xmit Error (FBP10)
100
Hex Value Condition

06 Clear diagnostic register command (FBP11-14, migration, FBM100s), Sta-
tus sequencer failed (FBP10)
07 Warm start command (FBP11-14, migration, FBM100s), Watchdog test
error (FBP10)
08 RAM failure (FBP11-14, migration, FBM100s), Buffer management error
(FBP10)
09 8044 test failure (FBP11-14, migration, FBM100s), Buffer management is
full (FBP10)
0A No data from other FBP10 (FBP10 only)
0B VRTX error (FBP10 only)
0C Int with bus command not equal data sent (FBP10 only)
0D ACT0/ACT1 mismatch (FBP10 only)
0E FIA database failure (FBP10 only)
0F Fieldbus comm failure (FBP10 only)
10 IOM configuration table invalid (except FBP10), Partner has access to more
I/O (FBP10)
11 FBM is fatal babbler (FBM200s only)
12 Secure write failed (except FBP10)
13 Clock overrun (except FBP10)
14 Analog input conversion overrun (except FBP10)
15 IOM hardware type mismatch (except FBP10)
16 IOM software type mismatch (except FBP10)
17 Expansion type mismatch (except FBP10)
18 No response command error (except FBP10)
19 Illegal factory ID (except FBP10)
1A Unknown reset condition (FBM100s only)
1B RAM Checksum failed after download (except FBP10)
1C Illegal (unexpected) interrupt occurred (except FBP10)
1D Module ID mismatch (except FBP10 and FBM200s)
1E Pulse input overrun (FBM100s and FBM200s only)
1F ROM function level mismatch (FBM100s only)
20 I/O gate array bus error (FBM100s only)
21 Expansion I/O gate array bus error (FBM100s only)
23 Flash ROM update failed (FBM200s only)
25 Logic machine execution error (FBM200s and FBP11-14 only)
40 EEPROM checksum error (FBMs and FBP11-14 only)
80 Expansion port failure (FBMs and FBP11-14 only)
101
NOTE
Either one or both of the hexadecimal values 40 and 80 can display in combination
with the value of 6.
fields, contact the Global Customer Support Center (Global CSC).
HARDWARE REV
The hardware release level of this FBM hardware type.
POWER 1 and POWER 2
NOTE
Power 1 and Power 2 are displayed for the DIN rail mounted FBMs only.
The Power 1 and Power 2 fields denote whether power is applied to the selected primary FBM
and, if present, its secondary FBM. These fields can have the following values:
Field Description
POWER 1 OK/FAILED = Primary power to FBM is OK/FAILED.
POWER 2 OK/FAILED = Secondary power to FBM is OK/FAILED.
PRIM CMD STAT

Primary Command Status is a hexadecimal value related to the status of communication between
the primary FBM and the selected FBM. Typically, this value is 0 or 1, where a value of 1 indi-
cates that a successful retry took place and communication has been restored to normal.
The descriptions of these Primary Command Status bits vary depending whether they are dis-
played for the I/A Series FBMs or the DIN rail mounted FBMs.
I/A Series FBMs

For the I/A Series FBMs, values 0 and 1 for Primary Command Status indicate there is no prob-
lem; values other than 0 or 1 indicate a failed transmission.
Table 5-3. Explanations of the Bits (Set to 1) Related to the Primary Command Status
(I/A Series FBM01 to FBM99)
Bit Description
Bit 0 Set if an exchange has been completed with a retry.
Bit 1 Set only if an exchange times out.
Bit 2 Set if response from the FBM to the primary FBM is invalid. Validity
varies with transaction type.
Bits 3 and 4 Stage at which error occurred. 00 – Stage 0 Attempt by the primary
FBM to reset the datalink.
Bit 01 First exchange of messages failed.
102
Table 5-3. Explanations of the Bits (Set to 1) Related to the Primary Command Status
(I/A Series FBM01 to FBM99) (Continued)
Bit Description
Bit 10 Second exchange of messages failed.
Bit 11 Currently unassigned code.
Bit 5 Mode flag; set if the device is off-line. These definitions apply when
this bit is = 0 (on-line).
Bit 6 Set if command is invalid.
Bit 7 Miscompare error if set (MSB). Relates to fault-tolerant station. This
bit triggers FT error recovery.
DIN Rail Mounted FBMs

For the DIN rail mounted FBMs, Primary Command Status can have the following values, as
described in Table 5-4.
Table 5-4. Primary Command Status Field Values (DIN Rail Mounted FBMs)
Value Description
=0 Normal, no error
=1 Success with retry (this condition is very rare)
=2 FCM timed out FBM
=3 CP timed out FCM
>3 Link level protocol error (this condition is very rare, and transient)
SOFTWARE REV
Release level of this FBM software.
FBM CMD STATUS

FBM Command Status is a hexadecimal value associated with the return status included in the
header of every response from the FBM to the primary FBM.
Typically, the hexadecimal value is 0, indicating the command was understood and action was
taken.
Table 5-5. Bit Positions Set to 1
Hexadecimal Bit Position

Value Set Description
1 0 Command not understood.
2 1 Command understood, but unable to take action.
4 2 Invalid argument.
EEPROM REV
Firmware release for this FBM.
103
FBM STATUS
Hexadecimal value related to the current FBM status. Typically this value is 4, indicating the
instructions are valid (Bit 2 is set).
Table 5-6. Explanations of the Bits (Set to 1) Related to the FBM Status
Bit Value Description

Bit 0 0x01 Set if the FBM status changes - requests CP to poll for extended status.
Bit 1 0x02 Set if the Diagnostic Register is non-zero. This indicates a fatal error. The
FBM does not start if this bit is set.
Bit 2 0x04 Normally set for non-fail-safe condition - this is the typical status for an FBM
(DIN Rail Mounted FBMs have a green status LED on). Reset only if the out-
put mode of operation is fail-safe.
Bit 3 0x08 Not used.
Bit 6 0x40 Set only if the FBM is off-line. In off-line mode, the software control is ROM-
based; in On-line mode, the software is RAM-based.
Bit 7 0x80 Set if initialization is taking place. All channel and I/O data is initializing.
Also, set if a DIN rail mounted FBM has a delayed response message ready.
This is normally associated only with FBMs that support child devices (such
as the FoxCom™ transmitters).
SERIAL NUMBER
Serial number assigned to this FBM hardware module.
LOGICAL ADDR
Logical Address is the number of the FBM, 1 through nn.
FBMs are typically numbered as they appear in the display (left to right) beginning at 1. The
order of FBMs is the order in which the FBMs were “fixed” using the Integrated Control Config-
urator. However, if an FBM is deleted and another added later, the new FBM is given the lowest
number available. For example, if FBM02 is deleted from the sequenced group of FBM01,
FBM02, and FBM03, the next FBM added results in the following sequence group: FBM01,
FBM03, and FBM02.
Refer to the EXTENSION TYPE field for a listing of FBMs (main modules).
MANUF DATE
Date of manufacture for this FBM. One of the three date standards, determined during site plan-
ning and system definition, is used: US (MM-DD-YYYY), ISO (YY-MM-DD), UR or
European (DD-MM-YY).
EXTENSION TYPE
FBM expansion type number.
104
Table 5-7. Expansion Units for FBMs
FBM Description
FBM12 Contact/dc Input Expander (16 DI)
FBM13 120 V ac Input Expander (16 DI)
FBM14 Contact/dc Input/Output Expander (8 DI/8 DO)
FBM15 120 V ac Input/Output Expander (8 DI/8 DO)
FBM16 240 V ac Input/Output Expander (8 DI/8 DO)
FBM21 240 V ac Input Expander (16 DI)
FBM25 125 V dc Contact Expander (16 DI)
FBM27 125 V dc Input/Output Expander (8 DI/8 DO)
FBM42 0 to 60 V dc Contact/dc (8 DI/8 DO)
NUMBER I/O POINTS

Number of points in alarm, active, and so forth.
Equipment Information for Fieldbus Communications Modules

(FCMs)
The Equipment Information fields contain information specific to the FCM selected. The con-
tents of these fields may change under two conditions: when a status change occurs, or when the
display is recalled. The fields updated when a status change occurs are:
 RUN MODE  EEPROM STATE

 FAIL ACK STATE  FCM STATE
 FAIL DEV ATT  MAIN STATUS
 DLOAD STATE  BACKUP STATUS
NOTE
When a fault-tolerant module replacement takes place, it is necessary to recall the
display to access the equipment information fields associated with the new module.
All other fields are static or change when the display is recalled.
The designation A, or MAIN, on the Equipment Information display refers to the module located
in the first position of a module pair in a baseplate and the designation B, or BACKUP, on the
Equipment Information display refers to the module located in the second position of a module
pair in a baseplate.
Examples of Equipment Information displays are shown in Figure 5-12 through Figure 5-17. The
first three figures show typical Equipment Information displays for a redundant pair of FCM
modules (FCM100Et shown). Figure 5-15 through Figure 5-17 show the pages of a typical
Equipment Information display for an FCM100E.
105
NOTE
Simplex FCM100E modules display “Not Configured” in the Equipment Informa-
tion Display fields for the “B” module.
NOTE
The FCM100E does not support the optional GPS time strobe synchronization,
Transient Data Recorder (TDR), or Sequence of Events (SOE) functionality.
Figure 5-12. Equipment Information Display for FCM100Et (Page 1)
106
107
Figure 5-15. Equipment Information Display for FCM100E (Page 1)
108
FCM NAME
The FCM letterbug assigned during definition of system hardware is shown.
TYPE
The type of FCM defined when the letterbug is assigned during the system definition phases.
Typical types of FCMs are:

COMM100Et Field Communications Module100Et FCM100
COMM100E Field Communications Module100E FCM100
COMM10Ef Field Communications Module10Ef FCM10Ef
COMM10E Field Communications Module10E FCM10E
RUN MODE A and B

On-line or Off-line. This field is initially Off-line. It changes to On-line when the FCM reports
to its host control processor after booting up. If reporting is disabled, the last known state appears
in this field.
RUN MODE should be viewed as a separate, but related field. Although certain Equipment
Change options change the RUN MODE to Off-line, they do not fail the FCM. However, a
failed FCM results in the RUN MODE changing to Off-line.
The RUN MODE changes to Off-line if any of the following occur:
 A reboot of the FCM
109
 An EEPROM update
 A physical pull/push of the FCM
 Any FCM hardware failure or communication failure.
DEVICE STATE A and B

lowing occur:
 The operator selects the FAIL soft key after running off-line diagnostics
 A hardware problem
 A physical pull/push of the FCM
 Any FCM hardware failure or communication failure.
Operator-initiated equipment change actions (GO-OFF-LINE, EEPROM UPDATE) change the
RUN MODE to Off-line, but do not change the FAIL STATE to Failed.
REDUN STATUS A and B

Redundant Status, Master or Tracker defines what module is currently the Master or Tracker
module.
NOTE
The FCM100E module does not support the Master/Tracker functionality. This
field does not appear on FCM100E Equipment Information displays.
FAIL ACK STATE

edged to indicate this transition. Use the ACK key in the top menu bar of the Equipment Infor-
mation Display to acknowledge the selected faulted device or use the ACK ALL key in the top
menu bar of the initial System Management Display to acknowledge all the unacknowledged
devices for which the selected System Monitor has responsibility.
ALARMING STATE
Alarming State indicates whether alarming is Enabled or Inhibited for the FCM. When alarming
is inhibited, the System Monitor continues to indicate overall system and network health while
equipment is Failed or Off-line.
FAIL DEV ATT

Yes or No. Yes is specified if one or more peripherals attached to the FCM are reported as failed.
FAIL DEV ACK

Acknowledged or Not Acknowledged. This field is initially set to Acknowledged. If any of the
attached devices become unacknowledged, the field changes to Not Acknowledged.
COMPOUND NAME
Compound name containing the FCM ECB.
110
BLOCK NAME
Block name for the FCM ECB.
EEPROM STATE A and B

EE Updating or Not Updating. This field is initially set to Not Updating. When EEPROM
UPDATE is selected under Equipment Change options, the status changes to EE Updating until
the action is completed.
DLOAD STATE A and B

Downloading or Not Downloading. This field is initially set to Not Downloading. When the sta-
tion is rebooted via an operator-initiated request, the status changes to Downloading until the
action is completed.
ETHERNET ADDR A and B

The system configurator (SysDef or IACC) assigns two MAC (Media Access Control) addresses
for each FCM on the network.
IP ADDRESS A and B
The system configurator (SysDef or IACC) assigns two IP addresses. One is assigned to the pri-
mary port of the FCM and the other is assigned to the alternate port of the FCM.
NETWORK MASK
The subnet mask of the FCM is normally set to 255.255.128.0 as assigned during system defini-
tion.
POWER 1, A and B
OK or Failed indicates the state of primary power to FCM.
POWER 2, A and B
OK or Failed indicates the state of secondary power to FCM.
MANUF DATE A and B

Date of manufacture for this FCM: first 2 characters = factory number, second two characters =
year of manufacture, third two characters = week of manufacture.
HARDWARE PART A and B

Hardware part number related to this FCM.
HARDWARE REV A and B

Hardware release level of this FCM hardware type.
SOFTWARE REV A and B

Indicates the release level of software currently running in the FCM.
PROGRAM A and B
Normal or Backup. Indicates that the software running in module A or B is the Backup or Nor-
mal (main) module software.
111
SOFTWARE TYPE
Type of application software (ECB) used with this FCM hardware type.
ECBs for the FCMs are:
Definition ECB
Field Communications Module100Et 210
Field Communications Module100E 210
Field Communications Module10Ef 110
HARDWARE TYPE
FCM number related to this FCM. Hardware types for the FCMs are:
Definition Hardware Type

Field Communications Module100Et 210
Field Communications Module10Ef 110
PRIMARY CMD STATUS

Primary Command Status is a value related to the status of communication between the FCM,
CP and the FBMs. For the FCMs, Primary Command Status can have the following values:
Value Condition
0 = Normal, no error
1 = Success with retry (this condition is very rare)
2 = FCM timed out FBM
3 = CP timed out FCM
> 3 = Link level protocol error (this is very rare and transient)
FCM CMD STATUS

FCM Command Status is a hexadecimal value associated with the return status included in the
header of every response from the FBMs to the FCM. Typically, the hexadecimal value is 0, indi-
cating the command was understood and action was taken.
Value Condition
0 Command understood, action taken.
1 Command not understood.
2 Command understood, but unable to take action.
4 Invalid argument.
112
MAIN ENET_A ERRS A and B

Number of messages received from the Ethernet A that have errors. The threshold should be less
than one error message per million messages.
BKUP ENET_B ERRS A and B

Number of messages received from the Ethernet B that have errors. The threshold should be less
than one error message per million messages.
MAIN HDLC_A ERRS A and B

Number of messages received from the Module Fieldbus A that have errors. The threshold should
be less than one error message per million messages.
BKUP HDLC_B ERRS A and B

Number of messages received from the Module Fieldbus B that have errors. The threshold should
be less than one error message per million messages.
IOM STATUS
Hexadecimal status code describing the status of the active FCM100 module.
FCM STATE
FCM State indicates the main FCM operational state.
TDR/SOE CLIENTS
(FCM100Et only) Indicates the number of Transient Data Recorder (TDR) and Sequence of
Events (SOE) clients.
HDLC BUS SPEED

268K or 2Mb indicates on which fieldbus the FCM100 module is communicating.
SYNC STATE
(FCM100Et only) Indicates whether or not the FCM100Et is configured to receive the time
strobe signals.
STROBE STATE, A and B

(FCM100Et only) Indicates the status of the time strobe signal on FCM100Et module A or B.
MAIN STATUS, BACKUP STATUS

Normal, Not Operational, Master, or Tracker.
MAIN HDLC 01
HDLC Bus A fault state for Main side.
MAIN HDLC 02
HDLC Bus B fault state for Main side.
BACKUP HDLC 01
HDLC Bus A fault state for Backup side.
113
BACKUP HDLC 02
HDLC Bus B fault state for Backup side.
MAIN INTERLINK
Interlink cable A fault state for Main side.
BACKUP INTERLINK
Interlink cable B fault state for Backup side.
MAIN ETHERNET
Ethernet cable A fault state for Main side.
BACKUP ETHERNET
Ethernet cable B fault state for Backup side.
114
6. Monitoring Performance
This chapter gives a general overview of monitoring system performance, including accessing
performance displays, viewing system management counters, and viewing device counters for
each peripheral.
This chapter contains the following topics:
 “Accessing the Performance Options Display” on page 115
 “Viewing System Management Counters” on page 116
 “System Management Counter Displays” on page 118
 “Viewing Peripheral Device Counters” on page 130.
Overview of Monitoring Performance

The I/A Series system monitors the communication performance of both stations and peripherals.
You use this information to balance and manage communication traffic within the network.
You can monitor communication performance by accessing the following counters:
 The System Management Counters provide information relating to the communica-
tion performance of the station, and of the station within the network. These
cumulative counters represent communication events. Examples of communication
events include the number of successful transmissions, the number of retries, and the
number of messages dropped.
 The Peripheral Counter options provide counter information concerning the commu-
nication performance of any peripheral attached to the station. Examples of
communication events include the number of times the station read or wrote to the
device and the number of errors or retries.
Accessing the Performance Options Display

To access the Performance Options Display:
1. From an initial system health display (System Monitor Domains Display or System
Monitor Domain Display), select the desired station.
2. Click the PERF soft key.
115
B0193JC – Rev U 6. Monitoring Performance
Figure 6-1. Performance Options Display
Viewing System Management Counters

To view system management counter information:
1. From the Performance Options Display select SYSTEM MANAGEMENT COUNTERS.
116
6. Monitoring Performance B0193JC – Rev U
Figure 6-2. System Management Counter Categories Display
The System Management Counter Categories Display shows:

 Categories for each of the network communication layers used by the selected
station
 A software loading parameters category.
2. Select a communication layer or the Loading Parameters.
See the following figures for the set of counters associated with each category:
 “Application Layer” on page 126
 “Loading Parameters Display” on page 129.
3. To view the most current values for all counters, click READ ALL.
Monitoring Changes in Performance

You can monitor the increase in counter values by noting the initial value and periodically reread-
ing the values using the READ ALL soft key.
To reset one counter value for periodic monitoring:
1. Select the individual counter to be reset from the listing. The RESET ONE soft key
becomes selectable.
2. Select the RESET ONE soft key to set the counter to zero and automatically reread the
latest counter value.
117
3. If desired, reread the counter periodically by selecting the READ ALL soft key. Con-
tinue to periodically reread the counter to determine how fast the counter value is
increasing.
To reset all counter values for periodic monitoring:
1. Select the RESET ALL soft key to set all the displayed counters to zero and automati-
cally reread the latest counter value.
2. If desired, reread the counters periodically by selecting the READ ALL soft key. Con-
increasing.
You can monitor changes in performance by reading counter values periodically or by resetting
the counters at specific intervals.
System Management Counter Displays

This section contains the following figures and a description of the displays:
 “Application Layer” on page 126
 “Loading Parameters Display” on page 129.
Resolution of Exceeded Counter Threshold Conditions

Invensys Customer Service personnel use counter information to determine and diagnose prob-
lems and failures. Threshold values are on a “per hour basis”.
You can resolve some problems that cause thresholds to be exceeded; others require that you call
the Global CSC.
118
MAC Sublayer
Figure 6-3. MAC Sublayer Counters Display
119
Table 6-1. MAC Sublayer Counters Display
Threshold Possible Reason

Counter* Description Value1 For Increment
MAC RESETS Number of times the Nodebus 2 Bad cable or bad
MAC or The MESH MAC was receiver if very large
initialized due to transmission values are observed
errors and hot remarries. over short periods of
time. Low values
(less than threshold)
are norm for
30 second intervals.
Possible heavy net-
work traffic.
802.4 MAC RESETS Number of times the tokenbus 2 Possible bad cable,
(Carrierband LAN Nodebus bad receiver or very
resets) MAC was initialized due heavy loaded net-
to transmission errors and hot work for large value
remarries. This counter applies over short periods.
to the LI station only.
DMA UNDERRUNS Number of times the station 4 (LI, PW) all Signifies a hardware
ran out of internal bus band- others = 1 error on local sta-
width. Not reported for a fault- tion, notify service.
tolerant station (excluding the
LI station) running married.
EXCESS COLLI- For Nodebus it indicates the 1 Bad cable or bad
SIONS number of unsuccessful trans- receiver.
missions because the number of Possible very heavy
collisions exceeded the maxi- network traffic.
mum number of retries.
For stations on The MESH, 0 for normal Bad cable or bad
indicates the number of times operation of receiver.
the primary port failed commu- The MESH Problem in Ethernet
nications with the backup port. network switches.
CRC ERRORS Number of properly aligned 0.1% of frames Bad cable or bad
frames received with CRC received local receiver or
errors. Not reported for a fault- remote transmitter if
tolerant station (excluding the threshold is exceeded
LI station) running married. in 30 seconds.
ALIGN ERRORS Number of received, misaligned 0.1% of frames Bad local receiver or
frames with CRC errors. Not received external transmitter.
reported for a fault-tolerant sta-
tion (excluding the LI station)
running married.
120
Table 6-1. MAC Sublayer Counters Display (Continued)

Counter* Description Value1 For Increment
NO RECEIVE Number of received frames lost 0.1% of frames Signifies hardware
RESOURCES due to memory resource prob- received error on local station
lems in the station. Not notify service per-
reported for a fault-tolerant sta- sonnel.
running married.
DMA OVERRUN Number of frames lost because 4 (LI, PW) all Possible station over-
the memory bus was not avail- others = 0 load or incoming
able to the controller chip. Not traffic in process.
running married.
FRAMES TRANS- Number of frames successfully 180,000 Each message trans-
MITTED transmitted by the MAC. mitted on network
increments this
counter by 1.
FRAMES RECEIVED Number of frames successfully N/A Each message
received by the MAC. received on network
increments this
counter by 1.
COLLISIONS Number of collisions experi- Nodebus - Bad cable, bad hard-
enced by the controller chip 5.0% of trans- ware, hot remarries.
during transmission attempts. mitted frames;
Not reported for a fault-toler- The MESH - 0
ant station (excluding the LI collisions
station or ATS) running mar-
ried.
TRANSMITS Number of times the controller 5.0% of trans- Bad cable, bad hard-
DEFERRED chip deferred traffic during the mitted frames ware, hot remarries.
first transmission attempt. Not
running married.
1. The values of these counters are not reported for a fault-tolerant station (excluding the LI station)
running married: DMA Underruns, Excess Collisions, CRC Errors, Align Errors, No Receive
Resources, DMA Overrun, Collisions, and Transmits Deferred.
121
Network Layer
These counters apply to LI stations and ATSs only.
Figure 6-4. Network Layer Display (Available for LI Stations Only)
Table 6-2. Network Layer Display
Threshold Possible Reason for

Counter Description Value1 Increment
DESTINATION Number of messages dropped 1 Destination LI not avail-
UNKNOWN because the destination node ID was able. Physical address of
unknown. destination node not
known.
PDUS RELAYED Number of PDU (Protocol Data 1,080,000 Packets routed.
Unit) messages which pass through
the LI (LAN Interface) or ATS.
1. The values of these counters are guidelines and can be affected by system dynamics. Exceeding one of these
values is not a definite indication of a problem or system error.
122
Transport Layer
Figure 6-5. Transport Layer Counters Display
123
Table 6-3. Transport Layer Counters

Counter Description Value* For Increment
CURRENT # Number of Fox™ IPC N/A N/A
CONNECTIONS connections currently
established. You cannot set
this counter.
RETRANS DATA TPDUS Number of retransmitted 0.2% of trans- Heavily loaded net-
ON A Transport Protocol Data mitted TPDUs work.
Units (TPDUs) on
Cable A.
RETRANS DATA TPDUS Number of retransmitted 0.2% of trans- Heavily loaded net-
ON B TPDUs on Cable B. mitted TPDUs work.
CONNECT DATA TPDUS Number of successfully N/A Each connection data
TRANS transmitted, connection- packet transmitted
oriented TPDUs. (non-ack) incre-
ments by 1.
CONNECT DATA TPDUS Number of successfully N/A Each connection data
RECVD received, connection-ori- packet received incre-
ented TPDUs. ments counter by 1.
CHECKSUM ERRORS Number of TPDUs 1 System overload
received with checksum condition.
errors.
CONNECTS DENIED – Number of connection 1 Application not
RES requests denied due to lack ready to get connec-
of Transport Layer (TL) tions.
local resources.
CONNECTS DENIED – Number of connection 10 The local TL detects
APP requests denied by a local one of the following
application. errors; peer connec-
tion not valid; desti-
nation station not
available.
CONNECTS DENIED – Number of connection 1 The local TL
TL requests denied by the TL. detected one of the
following errors:
packet format error
from peer; no
response from peer;
peer TL denied the
connection due to
one of these two
error conditions.
124
Table 6-3. Transport Layer Counters (Continued)

DISCONNECTS DUE TO Number of established 4 for LI, all This counter is incre-
ERRORS connections that broke others = 1. mented only if an
due to error. established connec-
tion experiences one
of the following con-
ditions: retransmits
were exceeded and
the TL did not
acknowledge a
TPDU; no TPDUs
were received from
the peer TL in a suf-
ficient time period;
the peer TL broke
connection due to
one of two error con-
ditions.
DISCONNECTS Number of established N/A N/A
REQUESTED connections broken due to
a local or remote applica-
tion request.
* The values of these counters are guidelines and can be affected by system dynamics. Exceeding one
of these values is not a definite indication of a problem or system error.
125
Application Layer
Figure 6-6. Application Layer Counters Display
126
Table 6-4. Application Layer Counters

CNLS-UNACK Number of connectionless, 200 Each transmitted
TRANSMITTED unacknowledged data pack- connectionless
ets transmitted by the Appli- unacknowledged
cation Layer (AL). packet increments
this counter by one.
CNLS-UNACK Number of connectionless, N/A Each received con-
RECEIVED unacknowledged data pack- nectionless unac-
ets received by the AL. These knowledged packet
data packets have a minimal increments this
overhead, provide no con- counter by one.
nection-oriented services,
and neither send nor receive
acknowledgment. Delivery is
further assured by sending
the message a second time
on the primary and second-
ary cables.
NO TUCBS AVAILABLE Number of connectionless 5 A lack of available
data packets not sent due to TUCBs indicates
a lack of available Transmit the control struc-
Unit Control Blocks tures a located to
(TUCBs). A lack of available process current out-
TUCBs indicates the control going message to
structures allocated to pro- the traffic is insuffi-
cess the current outgoing cient.
traffic are insufficient. You
may need to reconfigure the
allocation.
NO RUCBS AVAILABLE Number of connectionless 5 A lack of available
data packets rejected due to RUCBS indicates
lack of Receive Unit Control an insufficient
Blocks (RUCBs). A lack of number of control
available RUCBs indicates structure allocated
an insufficient number of to process current
control structures allocated incoming traffic
to process the current and reconfigura-
incoming traffic. You may tion may be neces-
need to reconfigure the allo- sary.
cation.
127
Table 6-4. Application Layer Counters (Continued)

RETRANS CL-ACK ON A Number of retransmitted, 0.2% of Cable problems
connectionless, acknowl- CL-ACK (one or more cables,
edged data packets on Cable transmitted or transitory prob-
A. Cable problems (one where: lems may be
cable, two cables or transi- CL-ACK is responsible for ack
tory problems affecting both sum of A and never arriving,
cables) may be responsible B CL-ACKs. resulting in retrans-
for the acknowledgment mission.
never arriving; this may
result in retransmissions.
RETRANS CL-ACK ON B Number of retransmitted 0.2% of Cable problems
connectionless, acknowl- CL-ACK (one or more cables,
edged data packets on Cable transmitted, or transitory prob-
B. Cable problems (one where: lems may be
cable, two cables, or transi- CL-ACK is responsible for ack
tory problems affecting both sum of A and never arriving,
cables) may be responsible B CL-ACKs. resulting in retrans-
for the acknowledgment mission.
never arriving; this may
result in retransmissions.
CNLS-ACK Number of connectionless, 180,000 Incremented by 1
TRANSMITTED acknowledged data packets where: when received.
transmitted by the AL. CNLS-ACK
is sum of
transmitted
and received
CNLS-
ACKs.
CNLS-ACK RECEIVED Number of connectionless, 180,000 Incremented by 1
acknowledged data packets where: when received.
received by the AL. CNLS-ACK
is sum of
transmitted
and received
CNLS-
ACKs.
LLC FRAMES Number of frames transmit- N/A Incremented by 1
TRANSMITTED ted directly to the Logical each time received.
Link Control layer (LLC),
bypassing the Transport and
Network layers.
128
Table 6-4. Application Layer Counters (Continued)

LLC FRAMES RECEIVED Number of LLC frames N/A Incremented by 1
received directly from the each time sent.
LLC layer, bypassing the
Transport and Network lay-
ers.
LLC FRAMES DIS- Number of LLC frames N/A Memory overload:
CARDED received directly from the lack of space avail-
LLC layer, but discarded able.
because a lack of memory
prevented the AL from copy-
ing and passing the message.
* The values of these counters are guidelines and can be affected by system dynamics. Exceeding one
of these values is not a definite indication of a problem or system error.
Loading Parameters Display
Figure 6-7. Loading Parameters Display
129
Table 6-5. Loading Parameters
Counter Description Static Value

RLS_RETRY_COUNT Number of times the ROM Load Server 1000 retries
(RLS) requests completion status from a
Loadable Device (LD).
MAX_BLOCK_SIZE Maximum data block size, in octets, that 1280 octets
a station can accept for loading.
MIN_BLOCK_SIZE Minimum data block size, in octets, that 0 octets
a station can accept for loading.
MAX_BLOCK_DELAY Maximum number of counts (converted 15000 milliseconds
to milliseconds) that an LD can tolerate
between transmission of individual data
blocks.
BLOCK_PER_GROUP Number of blocks in a logical group. 256 blocks/ logical
(Files are segmented into groups for the group at 1400 octets
purpose of loading station images.) per block
LD_RETRY_COUNT1 Number of times a load request is sent 1 time
before the load is considered failed.
LD_TIMER_T1 Number of counts, converted to millisec- 8000 milliseconds
onds, the LD waits for a load response
before issuing another Load Request.
Viewing Peripheral Device Counters

The Peripheral Counters Display shows current information for each peripheral counter. The
types of counters associated with a peripheral vary according to the peripheral group. For exam-
ple, the types of counters associated with a printer or terminal differ from the types of counters
associated with FBMs.
Accessing Peripheral Counters

Access Peripheral Counter Displays as follows:
1. From an initial system health display, select the letterbug of the station to be
monitored.
2. Select the PERF soft key to access the Performance Options Display for the selected
station.
3. Select PERIPHERAL COUNTERS from the option list on the Performance Options
Display.
The Peripheral Names and Types Display appears. For each peripheral attached to the
station this display lists:
 The peripheral letterbug
 The type of peripheral.
130
Each peripheral letterbug and type is color-coded to indicate its health status.
A flashing letterbug followed by an asterisk indicates an unacknowledged fault status.
4. On the Peripheral Names and Types Display, select a peripheral.
The counters for the selected peripheral appear. The counters vary depending on the
type of peripheral chosen. For a list of counters, see the individual peripheral type in
the section “Peripheral Names and Types Display” on page 131.
5. To view the most current counter values, select the READ ALL soft key.
Monitoring Changes in Performance

NOTE
The RESET ONE and RESET ALL soft keys are selectable only if the workstation
has access to secured actions.
You can monitor the increase in counter values by noting the initial value and periodically reread-
ing the values using the READ ALL soft key.
To reset one counter value for periodic monitoring:
1. Select the individual counter to be reset from the listing. The RESET ONE soft key
becomes selectable.
2. Select the RESET ONE soft key to set the counter to zero and automatically reread the
latest counter value.
3. If desired, reread the counter periodically by selecting the READ ALL soft key. Con-
increasing.
To reset all counter values for periodic monitoring:
1. Select the RESET ALL soft key to set all the displayed counters to zero and automati-
cally reread the latest counter value.
2. If desired, reread the counters periodically by selecting the READ ALL soft key. Con-
increasing.
Peripheral Names and Types Display

The following figures are examples of Peripheral Names and Types Displays for communication
processors, control processors, Ethernet switches and Fieldbus Modules.
NOTE
Peripherals associated with a workstation do not have counters.
131
Figure 6-8. Peripheral Names and Types Display (Communication Processor)
Figure 6-9. Peripheral Names and Types Display (Control Processor)
132
Figure 6-10. Peripheral Names and Types Display (Ethernet Switches)
Figure 6-11. Peripheral Counters, Page 1 (Ethernet Switch Ports)
133
Figure 6-12. Peripheral Counters, Page 2 (Ethernet Switch Ports)
Table 6-6. Peripheral Counters, Ethernet Ports
Counter Description
DROP EVENTS Total number of times that a switch was forced to discard frames due
to lack of available switch device resources. This does not display the
number of frames dropped, only the number of times the switch was
forced to discard frames.
UNDERSIZE PKTS Number of packets that were less than 64 octets.
FRAGMENTS Number of received frames that are not the minimum number of bytes
in length.
-OR-
Number of received frames that have a bad or missing Frame Check
Sequence (FCS), were less than 64 bytes in length (excluding framing
bits, but including FCS bytes) and had an invalid CRC.
In both cases, since the switches on The MESH always use full-duplex
connections, there should be no increments in the Fragment counter
due to CRC or collisions. Increments would typically occur only on a
half-duplex network where fragments are a normal result of collisions.
COLLISIONS Number of collisions experienced by the controller chip during trans-
mission attempts.
CRC ALIGN ERRORS Number of properly aligned frames received with CRC errors.
OVERSIZE PKTS Number of packets that were greater than 1517 octets.
134
Table 6-6. Peripheral Counters, Ethernet Ports (Continued)
Counter Description
JABBERS Number of jabber failures that were reported. This number should be
zero (0) with Ethernet switches.
OCTETS Number of octets that were transmitted.
PKTS Number of packets that were transmitted.
BROADCAST PKTS Number of broadcast packets that were transmitted to all stations.
MULTICAST PKTS Number of multicast packets that were transmitted.
PACKETS x TO y Number of packets of the specified size that were transmitted.
OCTETS
where x and y represent
various sizes
Figure 6-13. Peripheral Counters (Printer/Terminal Counters)
135
Figure 6-14. Peripheral Counters (FBM)
NOTE
The RESET ONE and RESET ALL soft keys are selectable only if the workstation
has access to secured actions.
Table 6-7. Peripheral Counters For SCSI (Printers, Floppy, Disk, Terminals) Devices
Threshold
Counter Name Explanation of Counter Value Possible Reason for Increment
RECVRED ER Number of times a device 1 Possible temporary failure on
encountered an error but was device. The operation suc-
able to recover. Number of ceeded on retries.
errors.
MEDIUM ER Number of times medium 1 Retries failed writing or read-
error occurred on medium ing device.
hard disk, floppy, tape, and so
forth.
HARDWARE ER Number of errors occurred 1 Hardware error noticed at the
due to hardware failure (con- device, notify field service
troller, and so forth). personnel.
PARITY ER Number of errors occurred on 1 Can be bad SCSI bus or sta-
SCSI bus. tion/ device SCSI bus interface
if threshold is reached.
136
Table 6-7. Peripheral Counters For SCSI (Printers, Floppy, Disk, Terminals) Devices (Continued)
Threshold
Counter Name Explanation of Counter Value Possible Reason for Increment
MSGS DROP Number of alarm messages 30 Exceeding the threshold in a
that could not be printed 30 second interval can mean
because output devices failed. the primary and backup print
devices are non-operational.
Incorrectly configured pri-
mary and backup devices can
be the cause also.
137
138
7. Equipment Changes and
Diagnostics
This chapter covers system equipment change displays, station changes, peripheral changes,
calibration, and on-line network, and off-line diagnostics.
Performing Equipment Changes

Use the Equipment Change Display to perform equipment status operations on selected stations
or peripheral devices. Only workstations designated (during System Monitor configuration) to
perform secured actions on selected devices can access the Equipment Change Display.
The Equipment Change Display for the Primary FBM indicates the operator-initiated selection
for the PIO bus (Fieldbus).
The list of change actions available from the Equipment Change Display differ between stations
and peripherals.
! CAUTION
Accessing Equipment Change

You can access the Equipment Change Display from various system health displays and network
health displays, and from the Equipment Information Display. Access to the Equipment Change
Display is permitted only from workstations configured with access to secured actions.

To access the Equipment Change Display from a system health display:
1. From an initial system health display, select the letterbug of the desired station.
3. From the Station Display, select the graphic representing the peripheral on which you
wish to perform an equipment change action; if you do not select a graphic, the sta-
tion remains preselected.
To perform changes on an intelligent device, select the appropriate FBM graphic and
click NEXT LEVEL. In the Intelligent Devices Display, select the appropriate letterbug.
4. Click EQUIP CHG. The Equipment Change Display appears with actions specific to
the selected device (either a station or peripheral).
Accessing from a Network Health Display

To access the Equipment Change Display from a network health display:
1. From the network health display, select the desired station or peripheral.
139
B0193JC – Rev U 7. Equipment Changes and Diagnostics
2. Click EQUIP CHG. The Equipment Change Display appears with actions specific to
the selected device (either a station or peripheral). If the EQUIP CHG is unavailable in
the network health display, the selected station in that display has an unknown status.
Accessing from an Equipment Information Display

To access the Equipment Change Display from an Equipment Information Display:
 Click EQUIP CHG.
Station Changes
Equipment Change Display actions for all stations include:
 Checkpoint Command: Records process tuning changes for a station in a checkpoint
file, which is sent to the host file server. If the self-hosting capability of the FCP270 or
ZCP270 controller is enabled, the checkpoint file is also burned to the controller’s
flash memory.
 Inhibit or enable station alarming actions
 Reboot action: Manually reloads the station image from the station’s flash memory
and the checkpoint file from the station’s host workstation if self-hosting is disabled or
from the station’s flash memory if self-hosting is enabled.
 EEPROM Update or IMAGE UPDATE action
 Downloads: Enables you to reboot the station or update the EEPROM
 Uploads: Enables you to record the memory dump when a station fails in a file on the
host AP
 Enable or disable all reports actions.
! CAUTION
Figure 7-1 shows a typical Equipment Change Display for stations, except FCP270 or ZCP270.
Figure 7-2 shows a typical Equipment Change Display for FCP270 or ZCP270 stations.
Figure 7-3 shows a typical Equipment Change Display for Address Translation Station (ATS).
140
7. Equipment Changes and Diagnostics B0193JC – Rev U
Figure 7-1. Equipment Change Display for Stations, Typical
Figure 7-2. Equipment Change Display for FCP270 or ZCP270 Stations
141
Figure 7-3. Equipment Change Display for Address Translation Station
Checkpoint Command
To retain controller tuning changes, you must save them to a checkpoint file before you reboot (or
restart) the station. This checkpoint file contains an image of the current database, and is sent to
the host file server. If the self-hosting capability of the FCP270 or ZCP270 controller is enabled,
the checkpoint file is also burned to the controller’s flash memory.
Normally, you reboot the station for each official Invensys software release, or to resolve system
maintenance issues. For example, you should save changes before you use the REBOOT action
from the Equipment Change Display or you perform a pull/push reboot after running off-line
diagnostics for the station.
When you restart (or reboot) the station, the system downloads the current checkpoint file to the
station.
When you initiate a Checkpoint, the following changes will be saved to the checkpoint file:
 Control database configuration changes
 Lock tuning changes made through the process displays
 FBM status changes (made outside SMDH).
Saving Control Processor Changes

You can use the Checkpoint action to save process tuning changes to the checkpoint file database
on the file server (AP). If the self-hosting capability of the FCP270 or ZCP270 controller is
enabled, the checkpoint file is also burned to the controller’s flash memory. When you use the
Checkpoint action, the system copies the current checkpoint file to a backup file and saves the
142
database from the station into the current checkpoint file. Once the process tuning changes are
saved, you can safely reboot the system.
To save recent control processor changes to the checkpoint file:
1. From the Equipment Change Display, select Checkpoint.
(You can make another selection while checkpoint is in progress.)
2. To verify that the checkpoint action completed successfully, check the message line or
connected printer indicating the following:
a. If self-hosting is not enabled, verify that a message appears indicating that the
checkpoint was successful. For example:
10-31-07 09:58:38 0 SYSMON = SYSMN1 CP0008 Software Manager
SYSMON -00021 Checkpoint Successful
b. If an FCP270 or ZCP270 is configured for self-hosting, a series of messages will
appear in the System Monitor log. The Checkpoint Successful message indi-
cates that the checkpoint file was successfully sent to the host workstation, but at
this point, the checkpoint file has not yet been burned to the controller’s flash
memory. The checkpoint is not complete until the Checkpoint installed
into flash message appears in the System Monitor log. Following is an example
of the series of messages that will appear if the FCP270 or ZCP270 is configured
for self-hosting:
2007-10-17 14:25:51 ZP0101 Process = Checkpoint CIO_DB
000015 -
Checkpoint to Flash Requested
2007-10-17 14:25:51 ZP0101 Process = Checkpoint CIO_DB
000015 -
Wait For Message 'Checkpoint installed into flash'
2007-10-17 14:26:33 ZP0101 Software Manager SYSMON -00021
Checkpoint Successful
2007-10-17 14:26:35 ZP0101 Process = Self Hosting RDHSS
000131 -
Checkpoint loading to Flash
000131 -
Backup Checkpoint erased
000131 -
Checkpoint File verified
000131 -
Checkpoint installed into flash
Checkpointing Information for ICC Databases

The database file developed with the I/A Series Configuration Component or the Integrated Con-
trol Configurator (ICC) and maintained in the application processor (AP) is a separate file from
the checkpoint file used by the control processor. The ICC database is not affected by checkpoint-
ing within System Management. You must use the I/A Series Configuration Component or Inte-
grated Control Configurator to change the ICC database. Before exiting, the Integrated Control
Configurator saves the ICC database changes to the checkpoint file. The I/A Series Configuration
143
Component saves the ICC database automatically after a download to the CP, or manually when
requested by the operator.
Refer to Integrated Control Configurator (B0193AV) or I/A Series Configuration Component (IACC)
User’s Guide (B0400BP) for additional information.
Inhibit or Enable Station Alarming Actions

Overview of Station Alarming
You can enable or inhibit station alarming through Equipment Change Display actions, thus pre-
venting alarms from being propagated up the equipment hierarchy. These two actions filter alarm
conditions so that the System Monitor continues to indicate overall system and network health,
even while equipment is failed or off-line. When alarms are filtered, system alarm messages for
those devices are not logged to the system printer or to the Historian.
You can put healthy equipment in the alarm inhibit state and then re-enable alarming on that
inhibited equipment. You can view a list of all equipment with inhibited alarming from the initial
system health displays (System Monitor, System Monitor Domain, and System Monitor
Domains).
Procedures for Station Alarming

When you perform the inhibit or enable alarming action, the system prints two messages: one
message when it receives the request, and another message when it completes the request, success-
fully or otherwise.
To Inhibit Alarming
From the Equipment Change Display, select INHIBIT STATION ALARMING. The inhibit mode
becomes the current state for the station.
If the inhibit alarming action is unsuccessful (that is, the station is not responding), verify that the
device or station processor is on-line and not failing.
To Enable Alarming
From the Equipment Change Display, select ENABLE STATION ALARMING. The Enable mode
becomes the current state for the station.
Reboot Action
Overview of Reboot Action
You can select to reload a selected station’s image and, if necessary, reload the database related to
that station. While a station is rebooting, it is off-line until the reboot is complete; this suspends
any access to the station database.
Rebooting typically is used after official Invensys software releases, or to resolve maintenance
issues.
144
! CAUTION
FOR AP20 STATIONS: Do not perform consecutive reboots on fault-tolerant
AP20s; the information on either hard disk can become unusable or inaccurate if
the mirroring task fails to complete. When rebooting either the Shadow or Primary
module, you must wait until the mirroring task is complete (approximately
45 minutes to 1 hour) before performing another equipment change action on
either stations.
! CAUTION
FOR A SINGLE CARRIERBAND LAN INTERFACE OR SINGLE ATS MOD-
ULE: If you perform reboots on a single Carrierband LAN Interface (LI) or a single
ATS module, the Nodebus is isolated from the network. During the reboot, any fur-
ther actions on that LI or ATS through System Management are inhibited. To avoid
network isolation, initiate reboots only on one LI or ATS module of a redundant
pair at a time.
Reloading the Station Image

You can reload a selected station’s image and, if necessary, reload the database related to that
station.
To reload a station image:
1. In the Equipment Change Display, ensure that the Enable Download state is active. If
it is not, select ENABLE DOWNLOAD.
2. Select REBOOT STATION.
If this is a fault-tolerant or redundant station, a list of the stations available for
EEPROM updates appears. (The MAC addresses in the PRIM ROM ADDRESS and
SHAD ROM ADDRESS fields of the Equipment Information Display appear for a
specific station.)
3. Select the station to reboot. The system reboots that station.
If there is an error, the system displays a message.
NOTE
If you cannot reboot a non-50 Series WP using the REBOOT STATION option,
press CTRL+ALT+F1. To perform an upload before the reboot, ensure that
Caps Lock mode is active.
EEPROM Update Action

Overview of the EEPROM Update Action for Stations
You can use the EEPROM Update action to update the existing EEPROM in a station with new
EEPROM firmware. (EEPROM updates are not available to workstations.) The update down-
loads a file, burns a new EEPROM, and reboots the system. During the EEPROM operation, the
station is off-line and access to the database for that station is suspended.
145
Invensys supplies the EEPROM update software. It is recommended that you perform an
EEPROM update only after an official Invensys software release, or if an FBM stays red/green
after a reboot. You must perform an EEPROM update on a WP20 station before you update any
peripheral firmware (such as the mouse and keyboard) attached to that station.
If you initiate a single EEPROM update for a selected workstation processor (WP), the system
updates both the WP and the GCIO processor in the WP.
! CAUTION
FOR WP70 STATIONS: Do not perform EEPROM updates on FBMs that use
DCI blocks. WP70s do not include a DCI server. If an FBM that uses DCI is
selected for eeprom update from SMDH running on a WP70, the FBM goes off-
line and does not complete the eeprom update action. A reboot of the FBM is
required to recover from the failure.
! CAUTION
FOR AP20 STATIONS: Do not perform consecutive EEPROM updates on fault-
tolerant AP20s. The information on either hard disk can become unusable or inac-
curate if the mirroring task fails to complete. When updating either the Shadow or
Primary module, you must wait until the mirroring task is complete (approximately
45 minutes to 1 hour) before you can perform another equipment change action on
either station. If they are not to be updated together, it is recommended that you
update the shadow first.
! CAUTION
FOR FCM100E MODULES: Use caution when using the GO OFF-LINE,
EEPROM UPDATE, and DOWNLOAD Equipment Change actions on an
FCM100E. Performing these actions may cause you to lose communication to the
FCM100E pair and to the I/O. See “Bus Selection Warning Dialog Boxes” on
page 160.
! CAUTION
FOR A SINGLE CARRIERBAND LAN INTERFACE OR A SINGLE ATS
MODULE: If you perform EEPROM updates on a single Carrierband LAN Inter-
face (LI) or a single ATS module, the Nodebus is isolated from the network. During
the update, any further actions on that LI or ATS through System Management are
inhibited. To avoid network isolation, initiate EEPROM updates only on one LI or
ATS module of a redundant pair at a time.
Updating EEPROM Firmware with New EEPROM Firmware

You can update an existing EEPROM in a station with new EEPROM firmware. You can perform
up to ten EEPROM station updates consecutively, as long as at least one “EEPROM update in
progress” message appears before you start the next EEPROM update.
146
To update existing EEPROM station firmware:

1. Access the Equipment Change Display for that station.
2. To ensure that all changes to the station are recorded in the host server, click
Checkpoint.
3. Ensure that ENABLE DOWNLOAD is the current state. If it is not, use the procedure in
“Enable or Disable Download Actions” on page 147 to enable downloads.
4. Select EEPROM UPDATE. A message appears in the message line.
If this is a fault-tolerant station, a list with the stations available for EEPROM updates
appears. (The MAC addresses in the PRIM ROM ADDRESS and SHAD ROM
ADDRESS fields of the Equipment Information appear for a specific station.)
5. Select the station on which to perform the EEPROM update. While the EEPROM
update processes, the system sends standard update progress messages to the printer.
Upon completion of the EEPROM update, the station reboots.
6. To verify the new revision levels, enter the VT100 mode on each application processor
(AP) hosting updated modules and start the frev utility by typing one of the follow-
ing commands:
 For Intel™, Inc.-based processors, use:
/usr/fox/bin/tools/frev >/usr/tmp/frev.log
 For Sun Microsystems™, Inc.-based processors, use:
/opt/fox/bin/tools/frev >/tmp/frev.log
If the EEPROM operation does not complete correctly, the system displays a message.
Fault Tolerant EEPROM Update

On-Line Upgrade features in I/A Series software allow you to upgrade to subsequent software on
fault-tolerant Control Processors (CPs) and Integrators, safely and with minimum hold-control
time. Non-fault-tolerant CPs and Integrators are upgraded off-line.
Image Update
Image Update is an EEPROM Update for Field Control Processors 270 (FCP270FT), Z-Module
Control Processors 270 (ZCP270FT) and Address Translation Stations (ATS). Selecting IMAGE
UPDATE on an Equipment Change Display for the FCP270, ZCP270 or ATS brings up a dialog
box that asks whether you want to do an EEPROM Update. For more information, refer to the
document Control Processor 270 (CP270) On-Line IMAGE Upgrade (B0700BY).
Enable or Disable Download Actions

In order to reboot a station or to update the EEPROM, you must enable downloads. Note that
the availability of these actions varies, depending upon the selected equipment.
If you enable a station for reboots and EEPROM updates, and then attempt to reboot the station,
you must manually push and pull the module before the station can start requesting boots again.
To enable downloads:
1. From the Equipment Change Display for the station, select ENABLE DOWNLOAD.
2. Perform a pull/push procedure on the module as follows:
a. Disengage the module by releasing the elevator.
147
b. Pull the module slightly out of its slot.

c. Push it back into the slot.
d. Re-engage the elevator.
To disable downloads:
 Select DISABLE DOWNLOAD.
If the enable or disable download action fails, an “Action Not Taken” message appears.
If the ENABLE UPLOAD or DISABLE UPLOAD actions fail, do the following:
 Verify the host application processor (AP) for the station.
 Verify the host application processor (smdh_spf ) for the Workstation Processor
(WP).
 Make sure no other WPs are running the CIO configurator for the control processor
(CP).
 Make sure no other WPs are running the Equipment Change options for the WP via
the SMDH.
Enable or Disable Uploads Actions

Overview of the Enable Upload and Disable Upload Actions
When a station is rebooted due to a software failure, the system uploads the station image to a
local file on the host Application Processor (AP) or Application Workstation (AW). From the
Equipment Change Display, you can permit or prohibit the system from uploading this image
when the station fails under certain conditions.
Station Failure Events

When the station fails, the following events occur:
1. The system sends a message regarding the station failure to the printer.
2. When you reboot the station, the station boots with an upload request from the ROM
firmware.
3. If the following conditions are true, the host AP performs the station upload (adding
approximately 15 minutes to the total reboot time):
 The host is an AP or an AW50/51.
 The UPLOAD_SRVR process is currently running.
 An upload is not currently taking place in the AP or AW.
 Uploads are enabled for this station.
4. The system sends a message indicating memory dump success and file name to the
printer.
NOTE
For non-50 Series WP stations, the system uploads the station images automatically
if you reboot the station using CTRL+ALT+F1. If this is the standard reboot proce-
dure, you can select DISABLE UPLOAD for the WP station.
148
Enable or Disable All Reports Actions

Enabling all reports permits the internal reporting of all status information for the station and any
attached devices, as well as reporting of system and peripheral counters to the System Monitor.
While reporting is enabled, all displays are updated with the current status of station and periph-
erals, and you can acknowledge equipment failures.
Disabling all reports stops all internal reporting. While reporting is disabled, the Equipment
Information and Equipment Change Displays may contain outdated information, you cannot
acknowledge equipment failures, and the station health status may not be accurate in terms of the
peripherals attached to the station.
NOTE
It is recommended that you do not disable all reports unless you need to reduce traf-
fic on the network to diagnose a problem.
If you have disabled all reports and an ECB is deleted using ICC, the ECB icon will still appear in
System Management displays. Follow this procedure to correct this situation and accurately dis-
play the peripherals connected to the CP:
1. In SMDH, select the CP and click the EQUIP CHG soft key.
2. In the Equipment Change Display, select ENABLE ALL REPORTS.
3. On all SMDH displays, do one of the following:
 Click HOME in the top menu bar.
-Or-
 Close and re-open SMDH.
4. Select the CP again, and click CONFIG to view the attached peripherals. The icon for
the deleted ECB should no longer be displayed.
Refer to the Equipment Information Display for the current station reporting state found in the
field SM REPORT STATE – Report All or No Reporting.
Refer to System Management subsystem software for information concerning internal reporting
among the different system management subsystem software.
On-Line Image Update

On-Line Image Update allows you to upgrade to subsequent software on fault-tolerant Field
Control Processors 270 (FCP270FT) and Z-Module Control Processors 270 (ZCP270FT), safely
and with minimum hold-control time. Non-fault-tolerant Field Control Processors 270
(FCP270) and Z-Module Control Processors 270 (ZCP270) are upgraded off-line.
149
Figure 7-4. FCP270FT/ZCP270FT Image Upgrade
When performing an On-Line Update, all blocks initialize. There is an option to specify “Warm
Start” or “Cold Start” for continuous control block initialization.
For more information, refer to the document Control Processor 270 (CP270) On-Line IMAGE
Upgrade (B0700BY).
Peripheral Changes
NOTE
For Equipment Information Display specifics relating to:
FBM220/221 refer to FOUNDATION fieldbus H1 Interface Module
(FBM220/221) User Guide (B0400FD).
FBM223 and related slave device information refer to
PROFIBUS-DP Communication Interface Module (FBM223) User’s Guide
(B0400FE).
FBMs 214/215/216 and 218 and related slave devices refer to HART™ Communi-
cation Interface Modules User’s Guide (B0400FF).
FBM224 refer to the Modbus Communication Interface Module (FBM224) User’s
Guide (B0400FK).
FCP270 refer to I/A Series FCP270 User’s Guide (B0700AR). For ZCP270 refer to
I/A Series ZCP270 User’s Guide (B0700AN).
FBMs230/231/232/233 refer to I/A Series System Field Device System Integrators
(FBM230/231/232/233) User’s Guide (B0700AH).
FBM228 refer to FOUNDATION™ fieldbus User’s Guide for the Redundant
FBM228 Interface (B0700BA).
Address Translation Station User’s Guide (B0700BP).
Equipment Change actions for peripherals include:

 GO ON-LINE or GO OFF-LINE actions
 GENERAL DOWNLOAD action
 DOWNLOAD action
 EEPROM UPDATE action
150
 PERIODIC PIO BUS SWITCH, BUS A: ENABLE SWITCHING, BUS B:

ENABLE SWITCHING, BUS A: DISABLE SWITCHING, BUS B: DISABLE
SWITCHING actions
 INHIBIT DEVICE ALARMING or ENABLE DEVICE ALARMING actions
 RESET ATTENTION BIT action
 SWITCH ROLES for redundant equipment.
Go On-Line or Go Off-Line
You can put peripherals on-line and take them off-line using the SMDH. For example, you can
turn selected peripherals off before performing EEPROM updates or before performing mainte-
nance on those peripherals, such as changing paper and ribbons on a printer.
Understanding Peripheral Response to On-Line and Off-Line Actions

Peripherals respond differently to the on-line and off-line actions, as follows:
 It is recommended that you place an FBM_0 off-line for diagnostic purposes only.
Placing an FBM_0 off-line stops all communication to the Fieldbus. The system
sends multiple messages to the printer indicating PIO Bus cable failures. An IIT reacts
the same as an FBM_0 in terms of stopping communication to the Fieldbus when off-
line.
 If you place an FBM on-line from a cold start, the FBM fail-safe condition for the
FBM outputs is zero (outputs are de-energized). If you place an FBM on-line while it
is running under control, the FBM fail-safe condition is dictated by the ECB configu-
ration. If the fail-safe timer is enabled, the outputs go to fail-safe as configured; if the
fail-safe timer is not enabled, the outputs hold.
 If you remove FBMs from a rack, or power them off, ensure that you place those
FBMs off-line to prevent them from being scanned.
 If you place an intelligent field device on-line, the FBM uploads the intelligent field
device database.
 If you place an Allen-Bradley, Modicon, Instrument Gateway or INTERSPEC 30
peripheral device off-line, communications specific to that device stop. If the control-
ler is failed and on-line, and reporting is enabled on the gateway, the gateway re-
establishes communications to the controller as soon as it comes back on-line. How-
ever, if you suspect that the controller will be failed for a period of time, you should
put it off-line to reduce communications traffic on the RS-232 side.
 If you take a printer off-line or if there is a paper outage, the processor fills its own
buffers until the printer is put on-line. The station’s buffers may become saturated.
When you turn the printer back on, all information in the buffer prints; however, any
data that arrived after the buffer was saturated is lost. If you must take the printer off-
line, try shutting off the power instead.
 You cannot place workstation processor (WP) peripherals on-line and off-line.
151
! CAUTION
For FCM100E modules and FCM100Et modules running in dual simplex mode:
Use caution when using the GO OFF-LINE, EEPROM UPDATE, and DOWN-
LOAD Equipment Change actions on an FCM100E or FCM100Et running in
dual simplex mode. Performing these actions may cause you to lose communication
to the FCMs and to the I/O. See “Bus Selection Warning Dialog Boxes” on
page 160.
Procedures for Putting a Peripheral On-Line or Off-Line

You can put a selected peripheral on-line or off-line through the Equipment Change Display.
Note that turning off a Primary FBM stops all communication to the Fieldbus, respective high-
way, or converter box.
! CAUTION
Only authorized personnel should put control or communication devices on-line or
off-line.
To Put a Peripheral On-line

From the Equipment Change Display, select GO ON-LINE. The system sends a message to the des-
ignated printer. If the GO ON-LINE action is unavailable, the peripheral is already on-line.
To Put a Peripheral Off-line

From the Equipment Change Display, select GO OFF-LINE. The system sends a message to the
designated printer. If the GO OFF-LINE action is unavailable, the peripheral is already off-line.
General Download for All FBM Images

Overview of the General Download
The GENERAL DOWNLOAD action downloads FBM images for all off-line/failed FBMs
attached to a selected control processor (CP), tank processor (TP) or display processor (DP). This
action is available from the primary FBM (FBM_0) for the CP, or from any OMC station.
Use the GENERAL DOWNLOAD action when you add a new FBM to the CP and the FBM
data is not already in the checkpoint file. Typically, you use the GENERAL DOWNLOAD action
to download FBM images after you perform integrated control configuration and FBM fix on
each of the new FBMs.
If the file information in the station already includes the selected FBM data (that is, checkpoint-
ing was performed while the FBMs were on-line), downloading occurs automatically, when neces-
sary.
152
Downloading all FBM Images

You can download FBM images for all off-line, failed FBMs attached to a selected control proces-
sor (CP), tank processor (TP) or display processor (DP) from the Equipment Change Display.
This option applies to the primary FBM (FBM_0) for the CP, or for any OMC stations.
To download FBM images for all off-line/failed FBMs:
1. From the Equipment Change Display, select GENERAL DOWNLOAD. This loads the
FBM images to all off-line/failed FBMs.
For a ZCP270 and a CP60, you must pick the GENERAL DOWNLOAD key twice when
performing a GENERAL DOWNLOAD after a LoadAll. The first pick downloads all
the FCMs and the second pick downloads all the FBMs.
Messages indicating the success or failure of the action for each downloaded FBM
appear. If the GENERAL DOWNLOAD action is successful, each FBM goes on-line.
If there is a failure, the system displays a “Not Responding” message.
2. If you use the GENERAL DOWNLOAD option during initial start-up, perform a
checkpoint to the control processor after downloading to all the FBMs. This preserves
the on-line state of the FBMs in the checkpoint file. Refer to “Checkpoint Com-
mand” on page 142.
Download
Overview of the Download Selected FBM Image
You can use the DOWNLOAD action to download a selected FBM with its image. If the check-
point file information does not include the FBM data, you must download the new FBM added
to the control processor (CP) after performing Integrated Control configuration and FBM fix.
If the checkpoint file information in the CP already includes the selected FBM data (that is,
checkpointing was performed while the FBMs were on-line), downloading occurs automatically,
when necessary.
The DOWNLOAD action is available for the following peripherals only:
 FBM  CORINT
 DISP STA PROC  GAS CHR
 HIU  FCM
Procedure for Downloading a Selected FBM Image

You can download a selected FBM with its image.
To download a selected FBM with its image:
1. From the Equipment Change Display, select DOWNLOAD to load the FBM image.
The system displays a message indicating the success or failure of the action for each
downloaded FBM. If the download is successful, the FBM goes on-line. If there is an
error, the system displays a “Not Responding” message.
2. After the FBM image download is complete, perform a checkpoint to the control pro-
cessor. This preserves the on-line state of the FBM in the checkpoint file on the host
file server. Refer to “Checkpoint Command” on page 142.
153
EEPROM Update
Overview of the EEPROM Update for Peripherals
You can use the EEPROM UPDATE action to update the firmware in a selected peripheral with
updated EEPROM software provided by Invensys. It is advised that you use this action only after
an official Invensys software release.
For FBMs (such as HIUs, CORINTS, and DS), you can perform numerous, consecutive
EEPROM updates without waiting for the completion of each. However, all EEPROM updates
must be completed successfully before you perform a download. Check the revision level of all sta-
tions after the FBMs are downloaded to ensure that the update was successful before you perform
a download.
For peripherals attached to a WP20, you must update the station firmware prior to performing
EEPROM updates on the peripherals.
The EEPROM update action is available for the following peripherals only:
 FBM  WP PERIPH:
 DISP STA PROC  Annun. Panel
 HIU  Keyboard
 CORINT  Mouse/Touchscreen
 GAS CHR
Updating Peripheral Firmware with Updated EEPROM Software

You can update the firmware for a selected peripheral with updated EEPROM software provided
by Invensys. It is recommended that you use this option only after official Invensys software
releases of EEPROM software.
! CAUTION
Do not attempt to use or power down the peripheral while the EEPROM is being
updated. A power failure, or an I/O hardware interrupt such as mouse movement or
keyboard activity, can cause an update failure.
To Update Firmware in a Peripheral with Updated EEPROM Software

From the Equipment Change Display, select EEPROM UPDATE. The peripheral is put off-line, as
indicated by the GO ON-LINE option becoming available for selection.
The update is complete when the peripheral is back on-line, as indicated by the GO OFF-LINE
option becoming available for selection again. The system displays a message indicating that the
device is back on-line. If the update action fails, the system sends a failure message to the message
line.
Additional Steps for FBM (DS, HIU, or CORINT) Devices

1. After the device is back on-line, select DOWNLOAD to download the database informa-
tion from the control processor (CP), display processor (DP) or tank processor (TP).
2. Access the Equipment Change Display for the station and select the appropriate con-
trol processor.
154
3. Perform the Checkpoint action to update the control database in the application pro-
cessor (AP).
PIO Bus Switching, Enabling and Disabling

This section covers the following peripheral changes for PIO bus:
 PERIODIC PIO BUS SWITCH
 BUS B: ENABLE SWITCHING
 BUS B: DISABLE SWITCHING
 BUS A: ENABLE SWITCHING
 BUS A: DISABLE SWITCHING
Overview of the PIO Bus Switching Actions

The PIO bus switching actions for the Allen-Bradley, Modicon, Instrument gateways, and
INTERSPEC Integrator 30 differ from those of a control processor.
These actions are available for the primary FBM device (FBM_0 located in the CP, TP, DP, ABG,
IG, or MODG; the IIT located in the IS30) only.
You can do PIO bus switching only from CP10, CP30, CP40 and CP60 stations.
You can select the desired PIO bus mode for CPs, DPs, TPs, ABGs, ABG-Rs, AB30s, MODGs,
MD30s, IGs, and IS30s.
Figure 7-5 shows a typical Equipment Change display for periodic PIO Bus switching.
Figure 7-5. Equipment Change, PIO Bus Switching
155
Overview of Periodic PIO Bus Switching Mode

This PIO bus mode automatically switches at a one-hour intervals if both buses are “equally”
good. The PERIODIC PIO BUS SWITCH mode applies to control processor (CP), tank proces-
sor (TP), and display processor (DP) stations run in a periodic switching mode. The PIO bus
switches the buses from the control processor to the FBMs.
The difference between the number of FBM access failures recorded per bus determines whether
switching occurs. The system checks the other bus to eliminate switching to a bad or worse bus.
The following scenarios can occur:
 If the current bus has a failure(s) and the other bus has fewer or no failures, the system
automatically switches to the better bus invoking the RUN ENABLED mode. The
system returns to the PERIODIC PIO BUS SWITCHING mode when the buses are
equal in terms of failures.
 If, prior to periodic switching, the alternate bus reports a larger number of FBM
access failures, the system automatically invokes the RUN ENABLED mode on the
current bus. The system returns to the PERIODIC PIO BUS SWITCHING mode
when the buses are equal in terms of failures.
 If both buses have an equal number of FBM access failures, the system remains in the
PERIODIC PIO BUS SWITCHING mode.
NOTE
The IIT does not support the PERIODIC PIO BUS SWITCHING action.
Periodic PIO Bus Switching Information for Specific Peripherals

Allen-Bradley Gateway and Integrator
The Allen-Bradley Gateway and Integrator support automatic path selection for gateways with
dual communication paths to the PLCs as follows: if only one PLC is experiencing communica-
tion problems, that PLC is rerouted to the other path and all other PLCs still access the current
path.
The action BUS A: ENABLE SWITCHING allows communication to Port 1; BUS A: DISABLE
SWITCHING stops communications over Port 1. BUS B: ENABLE SWITCHING allows com-
munications over Port 2; BUS B: DISABLE SWITCHING stops communications over Port 2.
Modicon Gateway
The Modicon Gateway supports automatic path selection as described for the Allen-Bradley
gateway.
INTERSPEC Integrator 30
The INTERSPEC Integrator 30 supports automatic path selection as described for the
Allen-Bradley gateway for the devices supported by the IS30: AIM, CCM, UIO, UFM.
Instrument Gateway (IG)

Port switching and automatic path selection are not available for the Instrument Gateway. The
actions BUS A: ENABLE SWITCHING or BUS B: ENABLE SWITCHING allow communica-
156
tions over Port 1 or 2 respectively. The actions BUS A: DISABLE SWITCHING or BUS B: DIS-
ABLE SWITCHING stop communications over Ports 1 and 2, respectively.
BUS A: ENABLE SWITCHING and BUS B: ENABLE SWITCHING Modes

These PIO bus switching modes cause the system to switch to the other bus in the event of an
FBM access failure only if the other bus has equal or fewer FBM access failures. BUS A: ENABLE
SWITCHING and BUS B: ENABLE SWITCHING run on the selected bus (A or B) until a
fault is detected on that bus.
NOTE
No periodic switching takes place with the BUS A: ENABLE SWITCHING or
BUS B: ENABLE SWITCHING selections.
BUS A: DISABLE SWITCHING and BUS B: DISABLE SWITCHING Modes

These PIO bus switching modes disable automatic switching in the event of an FBM access fail-
ure. These modes run on the selected bus regardless of fault detection.
Use the BUS A: DISABLE SWITCHING and BUS B: DISABLE SWITCHING actions for
diagnostic purposes, or when only one bus is available (such as when you are replacing a defective
bus).
NOTE
No periodic switching takes place with the BUS A: DISABLE SWITCHING or
BUS B: DISABLE SWITCHING selections.
Using the PIO Bus Switching Options

There are five PIO bus switching options available from the Equipment Change Display.
To automatically switch between Bus A and Bus B at one-hour intervals:
 From the Equipment Change Display, select PERIODIC PIO BUS SWITCH. The sys-
tem cycles between Bus A and Bus B at one-hour intervals. If the selected bus is not
available or is not functioning, the previous bus selection is maintained. If there is an
error, the system displays a message.
To designate Bus A as the current bus and automatically switch to the other bus when failures
occur:
 From the Equipment Change Display, select BUS A: ENABLE SWITCHING. If the
selected bus is not available or is not functioning, the previous bus selection is main-
tained. The system displays a message if an error occurs.
To designate Bus A as the current bus and deactivate automatic switching:
 From the Equipment Change Display, select BUS A: DISABLE SWITCHING. The sys-
tem does not check the current health of the bus. The system displays a message if an
error occurs.
To designate Bus B as the current bus and automatically switch to the other bus when failures
occur:
157
 From the Equipment Change Display, select BUS B: ENABLE SWITCHING. If Bus A
is not available or is not functioning, Bus B remains the current bus. The system dis-
plays a message if an error occurs.
To designate Bus B as the current bus and deactivate automatic switching:
 From the Equipment Change Display, select BUS B: DISABLE SWITCHING. The sys-
tem does not check the current health of the bus. The system displays a message if an
error occurs.
When you successfully select the PIO mode, the system sends a bus switch message to the printer,
and the selected PIO mode option is unavailable.
Errors with the PIO Bus Switching Modes

BUS A: ENABLE SWITCHING or BUS B: ENABLE SWITCHING
Message: Action Not Taken
If the BUS A: ENABLE SWITCHING or BUS B: ENABLE SWITCHING operations fail, do
the following:
 Make sure the station is on-line and not failed.
 Make sure the FBM is on-line and not failed.
 Check the PIO cable states (hardware).
PERIODIC PIO BUS SWITCH

This is an automatic default mode that switches buses at one-hour intervals. If a problem exists
with either A or B bus, the system switches to RUN-ENABLED on the good, or best, bus. The
system returns to AB PERIODIC when the bus problem is corrected.
BUS A – DISABLED or BUS B – DISABLED

Message: Action Not Taken
If the BUS A: DISABLE SWITCHING or BUS B: DISABLE SWITCHING operations fail, do
the following:
 Make sure the station is on-line and not failed.
 Make sure the FBM is on-line and not failed.
 Check PIO cable states (hardware).
FCM100Et, FCM100E, FCP270 and ZCP270 Module Fieldbus

Switching Actions
This section covers the following equipment changes for the Module Fieldbus:
 SELECT BUS A ONLY
 SELECT BUS B ONLY
 BUS AUTO SELECT
You can select the desired Module Fieldbus (A and/or B) from the FCM100Et, FCM100E,
FCP270, or ZCP270 stations. The Module Fieldbus is a redundant bus that communicates with
the modules installed in the Modular Baseplates. These actions are available from the primary
FBM device (FBM_0 located in the FCM100Et, FCM100E, FCP270, or ZCP270) only.
158
Figure 7-6 shows a typical Equipment Change display for FCM100Et, FCM100E, FCP270, or
ZCP270 Module Fieldbus switching.
Figure 7-6. FCP270, FCM100Et, FCM100E and ZCP270 Module Fieldbus Selection
Overview of FCM100Et, FCM100E, FCP270, or ZCP270 Module Fieldbus

Switching Mode
The control processor or communications module (station) records the number of FBM access
failures per cable/bus A and/or B and determines whether switching occurs. The system checks
the other cable/bus to eliminate switching to a bad or worse cable/bus.
The following scenarios can occur:
 If the current Module Fieldbus has a failure(s) and the other bus has fewer or no fail-
ures, the station automatically switches to the better bus if the BUS AUTO SELECT
mode is selected.
 If both cables/bus have an equal number of FBM access failures, the station continues
transmission over the existing bus if the BUS AUTO SELECT mode is selected.
 If SELECT BUS A ONLY or SELECT BUS B ONLY are selected the station
attempts to continue transmission over the selected cable/bus regardless of the failure.
159
Using the FCM100Et, FCM100E, FCP270, or ZCP270 Module Fieldbus

Switching Options
There are three FCM100Et, FCM100E, FCP270, or ZCP270 Module Fieldbus switching
options available from the Equipment Change Display.
To automatically switch between Module Fieldbus A and B:
 From the Equipment Change Display, select BUS AUTO SELECT. The system selects
Bus A and Bus B. If the selected bus is not available or is not functioning, the previous
bus selection is maintained. If there is an error, the system displays a message.
To designate Module Fieldbus A as the current bus and deactivate automatic switching:
 From the Equipment Change Display, select SELECT BUS A ONLY. The system does
not check the current health of the bus. The system displays a message if an error
occurs.
To designate Module Fieldbus B as the current bus and deactivate automatic switching:
 From the Equipment Change Display, select SELECT BUS B ONLY. The system does
not check the current health of the bus. The system displays a message if an error
occurs.
Use the SELECT BUS A ONLY or SELECT BUS B ONLY switching actions for diagnostic purposes,
or when only one bus is available (such as when you are replacing a defective cable or Modular
Baseplate).
Bus Selection Warning Dialog Boxes

Use caution when using the GO OFF-LINE, EEPROM UPDATE, and DOWNLOAD Equip-
ment Change actions on an FCM100E module or FCM100Et modules running in dual simplex
mode. Performing these actions may cause you to lose communication to the FCM100E pair or
the simplex FCM100Et and to the I/O. For example, if an FCM100E pair is running on Bus A
and you choose GO OFF-LINE for the Main FCM100E, a warning dialog box appears with the
message shown in Figure 7-7. To continue with the selected operation, click YES. Otherwise,
click NO or CANCEL.
Figure 7-7. Redundant FCM100E Bus Selection Warning Message
Similarly, for a simplex FCM100Et module, a warning dialog box appears with the message
shown in Figure 7-8. To continue with the selected operation, click YES. Otherwise, click NO or
CANCEL.
160
Figure 7-8. Simplex FCM100Et Bus Selection Warning Message
If you are configuring an FCM100E and there are one or more simplex FCM100Es in the system,
selecting SELECT BUS B ONLY causes the warning dialog box shown in Figure 7-9 to appear.
To continue with the selected operation, click YES. Otherwise, click NO or CANCEL.
Figure 7-9. Simplex FCM100E Warning Message
Inhibit Device Alarming or Enable Device Alarming

You can permit (enable) or prohibit (inhibit) alarming from a selected device. When you select to
prohibit alarming, the system filters alarm conditions so that the System Monitor continues to
indicate overall system and network health while equipment is failed or off-line. While alarming is
prohibited, system alarm messages are not logged to the system printer or the Historian.
You can also put healthy equipment into the alarm inhibit state and then re-enable alarming on
that inhibited equipment. The System Monitor, System Monitor Domain, and System Monitor
Domains Displays contain current lists of the inhibited equipment.
When a device is inhibited, it will be indicated at the device level and the system monitor level
with the inhibited symbol (‘<‘). The parent station will not be inhibited and there will not be any
indication of the inhibition at the station level. The indication at the system monitor level will
indicate the user that there is a device or a station in its domain for which alarms are inhibited. If
the user wishes to find the inhibited device, he would select the system monitor and then bring up
the Inhibited Display page to see all stations and devices that are currently inhibited.
161
To Inhibit Alarming
From the Equipment Change Display, select INHIBIT DEVICE ALARMING. The Inhibit mode
becomes the current state.
To Enable Alarming
From the Equipment Change Display, select ENABLE DEVICE ALARMING. The Enable mode
becomes the current state.
Reset Attention Bit

When the Universal Input/Output module (UIO) or the Universal Field Multiplexer (UFM)
INTERSPEC Integrator peripheral has a status setting of either LOC (local), FLK (flunk) or
momentary loss of power to the peripheral, you need to reset the attention bit.
The RESET ATTENTION BIT action is only available for the UIO and UFM INTERSPEC
Integrator peripherals when the attention bit needs to be reset.
Before you can perform the RESET ATTENTION BIT action, you must clear the unacknowl-
edged bit.
To reset the attention bit:
1. From the Equipment Information Display for the specific peripheral, click ACK. This
clears the unacknowledged bit.
2. From the Equipment Change display, select RESET ATTENTION BIT. The attention
bit is reset.
Switch Roles for Redundant Equipment

You can switch the roles of the main and backup modules. This operation applies only to Redun-
dant equipment.
To switch the main and backup module roles for redundant equipment:
 Select SWITCH ROLES from the Equipment Change Display.
NOTE
Because the FCM100E module does not support the Master/Tracker functionality,
the SWITCH ROLES selection on the FCM100E’s Equipment Change display is
disabled. Similarly, the SWITCH ROLES selection on the FCM100Et’s Equipment
Change display is disabled when the module is configured single.
Switch Changes
Equipment Change actions for switches include:
 INHIBIT ALARMING and ENABLE ALARMING actions
 DISABLE REPORTS and ENABLE REPORTS actions.
162
Inhibit or Enable Switch Alarming

You can permit (enable) or prohibit (inhibit) alarming from a selected switch. When you select to
inhibit alarming, you prevent Switch alarms from propagating up the equipment hierarchy,
thereby inhibiting Switch alarm messages.
To Inhibit Alarming
From the Equipment Change Display, select INHIBIT ALARMING. The Inhibit mode becomes the
current state.
To Enable Alarming
From the Equipment Change Display, select ENABLE ALARMING. The Enable mode becomes the
current state.
Disable or Enabling Reports

You can enable or disable all internal reporting of all Switch and port statuses and counter infor-
mation to the host System Monitor.
Running On-Line Network Diagnostics

Overview of the On-Line Diagnostics
The On-Line Diagnostics Display contains on-line diagnostic tests specific to a selected network
display. The on-line diagnostic tests available differ based on network type, and include the
following:
 Cable testing
 Viewing the current Nodebus master
 Selecting a station as the Nodebus master
 Selecting the default Nodebus Master.
For example, if you access this display from the Carrierband LAN or Nodebus Displays, you can
run Nodebus or tokenbus tests; if you access this display from a PIOM-type display (for an
FBM0), you can inhibit PIO cable alarms.
You can use the On-Line Diagnostics Display to test Carrierband LAN cables and the
Nodebus cables on-line.
Testing Nodebus Station Cables

You can initiate Nodebus station cable testing from the On-Line Diagnostics Display. If the sys-
tem finds a cable test failure, you should notify the appropriate maintenance personnel to resolve
the problem. When the problem is resolved, you should run a cable test to verify correction.
NOTE
Maintenance personnel must have knowledge of the network topology in order to
isolate cable failures on Nodebuses with multiple Nodebus extenders.
163
Figure 7-10. On-Line Diagnostics for Nodebus
Overview of the Nodebus Cable Test

The cable test involves three stations:
 A station designated as the Nodebus Test Initiator
 The station from which you are currently working
 A station selected during the test.
The Nodebus cable test involves a series of loop-back tests. The test sequences is as follows:
1. The first loop-back test sends a series of characters from the initiator to each of the
other two stations over the A cable and receives a response over the A cable.
2. The second loop-back test sends a series of characters from the initiator to each of the
other two stations over the B cable and receives a response over the B cable.
3. If either of the first two loop-back tests fail, two more loop-back tests occur:
 The initiator sends to both stations over the A cable and looks for a response
on the B cable.
 The initiator sends to both stations over the B cable and looks for a response
on the A cable.
If multiple communication failures occur on a single station, the last failure detected appears.
Procedure for Running the Nodebus Cable Test

To test the Nodebus station cable:
164
1. From the Nodebus Display, click ON-LINE DIAG. The station On-Line Diagnostics
Display appears with information specific to the Nodebus station.
2. To verify the location of the current Nodebus cable test initiator, select CURRENT
NODEBUS CABLE TEST INITIATOR to verify the location of the current Nodebus
cable test initiator.
The letterbug of the station appears in the message line.
3. Select RUN NODEBUS STATION CABLE TEST.
A list of all the station letterbugs associated with the Nodebus appears.
4. From the listing, select the second station to use in the Nodebus cable test.
If one of the stations selected is the current cable test initiator, the initiator automati-
cally selects another station for the test.
The initiation, progress, and results of the cable test appear in the message line of the
workstation initiating the cable test and at the printer designated for system fault
notification.
The system sends the cable test results to all workstations only if the cable test fails. If
you select a failed station as one of the two stations for testing, the system sends an
error condition report to that station as the cable test result.
Changing the Nodebus Cable Test Initiator

Usually you do not need to change the cable test initiator. However if there are problems with the
L1 station, you can change the test initiator as follows:
1. From the On-Line Diagnostics (Node) Display, select a station (AP20, AP50/AP51,
AW50/AW51, or AW70).
2. Select CHANGE NODEBUS CABLE TEST INITIATOR.
This designates the selected station as the new Nodebus cable test initiator and the let-
terbug (ATS, LI, AP20, AP50/AP51, AW50/AW51, or AW70) of the selected Node-
bus cable test initiator appears in the message line.
If there is an ATS on a node, the ATS is the default Nodebus Test Initiator, not the LI.
You can only change the Nodebus Test Initiator from the ATS to another station from
SMDH on The MESH station. Trying to change from a Nodebus station results in
“Unable to process request” message.
If the Nodebus Test Initiator is not the ATS and you change the test initiator to
another station beside the ATS, the ATS overrides the change and re-assumes master-
ship.
3. Run the Nodebus cable test as described in “Procedure for Running the Nodebus
Cable Test” on page 164.
4. To change the test initiator back to the default station (an ATS if present, or an LI if
an ATS is not present), select DEFAULT NODEBUS CABLE TEST INITIATOR.
The message “Action in progress” appears. This same message appears when the initia-
tor takes over.
165
Carrierband LAN Cable Testing

The Carrierband LAN Network Fault Detection (NFD) task resides in each LAN Interface (LI)
station. The Carrierband LAN cable test isolates communication faults related to the following
hardware:
 LAN Cables A and B
 LAN drop cables
 LI station transmitters (for LAN communications)
 LI station receivers (for LAN communications).
On-Line Cable Tests

The system automatically tests Carrierband LAN and Fiber Optic cables to isolate faults and
check the integrity of the communication path. In addition, you can perform cable tests to verify
that communication problems are resolved.
Before you initiate a Carrierband LAN on-line cable test, you first need to repair the faulted com-
munication hardware. Review the Carrierband LAN Display to determine which communication
hardware is faulted.
The system prints cable test messages to the message line and defined logging device(s).
For an example of the display, see “Carrierband LAN On-Line Diagnostics Display” on page 40.
Carrierband LAN On-line Diagnostics Cable Test Options

 Run Carrierband Cable Test
Checks the ability of all LAN Interfaces (LIs) to communicate on the Carrierband
LAN and the fiber-optic LAN. The system test all LIs automatically, regardless of the
LI selected.
 Current Carrierband Test Initiator
Displays the letterbug identifier of the LI selected to be the test initiator. All LIs can be
test initiators; however, only one LI is selected to initiate testing.
 Change Carrierband Test Initiator
Specifies the letterbug identifier of the LI selected to be the test initiator. All LIs be
test initiators; however, only one LI is selected to initiate testing.
Performing Off-Line Diagnostics

Overview of the Off-Line Diagnostic Display
The Off-Line Diagnostic Display contains diagnostic tests for a selected station. You can use off-
line diagnostic tests to verify the proper operation of the station components.
Off-line diagnostic tests are station specific; when the Off-Line Diagnostic Display appears for a
selected station, the display shows only those tests available for that station.
You can run off-line diagnostics locally (across the Nodebus) and remotely (across the Carrier-
band LAN or fiber optic LAN). PW (Personal Workstations) and Solaris based workstations do
not support off-line diagnostics.
166
You use the EXEC ONCE, EXEC ALL, and EXEC LOOP soft keys to run the off-line diagnostic
tests.
Accessing the Off-Line Diagnostic Display

You can access the Off-Line Diagnostic Display from either the System Monitor Domain Display
or System Monitor Domains Display for a selected station. Note that this display is not accessible
for personal workstations or Solaris based workstations.
! CAUTION
The OFF-LINE action takes the specified station off-line. Only authorized person-
nel, aware of the results of taking the station off-line, should perform this action.
To access the Off-Line Diagnostic Display:

1. From either the System Monitor Domains or System Monitor Domain Display, select
the station on which you want to run diagnostics.
2. Click OFF-LINE. One of the following occurs:
 For non-fault tolerant stations, the system displays a message prompting you to
confirm the selected action. If you do not want the system to put the station off-
line to run the off-line diagnostic tests, select NO. To have the station put off-line
and to access the Off-Line Diagnostic Display for the selected station, select YES.
 For fault-tolerant stations, the system displays a dialog box prompting you to
select the station on which you want to run off-line tests. To return to the System
Monitor Domain or System Monitor Domains Display, click CANCEL.
3. The selected station goes off-line and the Off-Line Diagnostic Display lists the avail-
able off-line diagnostic tests.
NOTE
You cannot reboot stations in Off-Line Diagnostics mode from the Equipment
Change Display. You must click RESTART in the Off-Line Diagnostic Display to
restart the station, or FAIL to indicate that the station is to be repaired or replaced,
and to leave it in its current off-line state.
Running Off-Line Diagnostic Tests

You can run diagnostic tests on a selected station to check or verify the proper operation of the
components of that station.
Running the Off-Line Diagnostic Tests

To run off-line diagnostic tests:
1. From the Off-Line Diagnostic Display, select one or more tests to run for the selected
station. The tests you select appear in red text. (To clear a selected test, select it again.)
2. Select how you want the selected test(s) run, as follows:
 EXEC ONCE: Execute selection only once. Select the test(s) to run, then click this
execution command.
167
 EXEC LOOP: Executes the selected test(s) continuously until you click HALT in the
Off-Line Diagnostic Results Display. Select the test(s) to run, then click this exe-
cution command.
 EXEC ALL: Executes all diagnostic tests shown in the Off-Line Diagnostic
Display.
The system runs the selected tests as designated. The Off-Line Diagnostic Results Dis-
play appears, showing the tests that ran and the results of each as it completes, includ-
ing the total number of tests passed and the total number of tests failed.
Viewing the Results of the Off-Line Diagnostic Test

Possible off-line diagnostic test results are:
 PASSED: Indicates the station passed the diagnostic test(s).
 FAILED (DOWNLOAD): When shown in yellow text, indicates the diagnostic test
did not run because the system could not download it to the station (not currently
used).
 FAILED (EXECUTE): When shown in red text, indicates the station failed the diag-
nostic test.
 NO RESPONSE: Indicates that the station is not responding to the test execution
request. If the “NO RESPONSE” message appears three times consecutively, testing
stops and the system displays the message “Station Not Responding”.
After running the off-line diagnostic test(s), you have several options, including failing or restart-
ing the station, or returning to another display.
168
Figure 7-11. Off-Line Diagnostics Displaying Test Results
After Running Off-Line Diagnostic Tests

After performing the off-line diagnostic tests, you can click the Return soft key in the Results
Display to return to the Off-Line Diagnostic Display. In the Off-Line Diagnostic Display, you
can restart or fail the station, or move to another display, as follows:
 Click HOME, DOMAIN, or CLOSE to leave the station in diagnostic mode while returning
to another display.
 Click RESTART to reboot/reload the station after running off-line diagnostic tests, or
to rerun the off-line diagnostics. (Do not click REBOOT in the Equipment Change
Display.)
 Click FAIL to take the station off-line indefinitely. This is recommended if the station
has a problem, such as intermittent failure. Use FAIL when the station needs repair or
replacement.
If you take the station off-line using FAIL, you must pull/push the module when you are ready to
bring the station back on-line. When you replace this station, the system automatically reboots
new station when you push it into the rack.
169
Types of Off-Line Diagnostic Tests

Communication Processor 10 and 760/761 Gateway Diagnostic Tests
Table 7-1. Communication Processor 10 and 760/761 Gateway Diagnostic Tests
Test Description
DMA WRITE Tests the hardware interface to the Direct Memory Access
(DMA) controller.
SCC RD/WRT Verifies hardware registers located inside both Serial Communi-
cations Controllers (SCC).
M/P/M TEST Performs a memory to SCC synchronous loopback to memory
DMA transfer and verifies the results.
ASYNC LPBK Performs an internal loopback test on both channels of each
SCC.
LETTERBUG Tests the module identifier address character and compares the
value against configuration table for validity and position.
Communication Processor 15/30, INIs, and Gateways Diagnostic Tests

The tests described in this section apply to the following stations:
Station types for the diagnostic tests are:
 Allen-Bradley Data Highway Gateway
 Allen-Bradley Data Highway Gateway Redundant
 Communication (Gateway) Processor 15
 Control Processors (CP)
 Device Integrator, Device Integrator 30
 Information Network Interface 15
 Instrument Gateway, Instrument Gateway (Version 2)
 Integrator 30 for ABDH, Integrator 30 for ABDH Redundant
 Integrator 30 for Modicon
 LAN Interfaces (LI)
 Modicon Gateway
 SPECTRUM Master Gateway – Redundant (SIP), SPECTRUM Master Gateway –
Non-redundant (SIP-R).
 Communication Processor 15/30, INIs, and Gateways Diagnostic Tests
Table 7-2. Communication Processor 15/30, INIs, and Gateways Diagnostic Tests
Test Description
DMA WRITE Tests the hardware interface to the Direct Memory Access (DMA)
controller.
SCC RD/WRT Verifies hardware registers located inside both Serial Communica-
tions Controllers (SCC).
170
Table 7-2. Communication Processor 15/30, INIs, and Gateways Diagnostic Tests
Test Description
M/P/M TEST Performs a memory to SCC synchronous loopback to memory
DMA transfer and verifies the results.
ASYNC LPBK Performs an internal loopback test on both channels of each SCC.
LETTERBUG Tests the module identifier address character and compares the
value against configuration table for validity and position.
8087 TEST Verifies mathematical functions of 8087.
Table 7-3. Control Processors Diagnostic Tests
Test Description
NODEBS COM Verifies fault-tolerant compare logic using built-in test functions. This
is a Nodebus compare logic test. (Not available for the CP30 and
CP40.)
LETTERBUG Tests the module identifier address character and compares the values
returned against configuration tables for validity and position.
FBM PORT Verifies the shared RAM interface to the Fieldbus subassembly; then
initiates the Fieldbus diagnostics which run via the 8044 I/O Processor
and verifies the results. This is an I/O processor test.
Table 7-4. Application Processor 20 Diagnostic Tests
Test Description
SCSI TESTS Verifies the shared RAM interface to the Small Computer System
Interface (SCSI) subassembly; then initiates the SCSI diagnostics
which run via the 8051 I/O processor, and verifies the results using the
following tests:
 CPU – Verifies 8051 internal RAM and Processor function.
 Program RAM – Tests the 8051 program RAM.
 Shared RAM – Verifies the shared RAM from the 8051 side.
This is an I/O processor test.
MEM DMA Performs memory-to-memory DMA transfer and verifies results.
ADMA DMA Verifies all addressable hardware registers located inside the ADMA
DMA controller.
LETTERBUG Tests the module identifier address character and compares the value
against the configuration table for validity and position.
CLNDR CLK Tests the ability to write a date and time to the calendar clock IC and
verifies that the clock runs.
171
Table 7-5. Workstation Processor 30 Diagnostic Tests
Test Description
GSP_GE Tests the internal 386 graphics engine and memory (video RAM and
dynamic RAM).
8087 TEST Verifies the mathematical functions of the 8087.
GCPIO Verifies the shared RAM interface to the workstation processor I/O
subassembly after a cold start diagnostic test, then initiates the WP
I/O diagnostics and verifies the results.
GSP_HOST Tests the letterbug of the host and compares the value against a table
for validity and position.
against configuration tables for validity and position.
Table 7-6. SPECTRUM Slave Gateway Diagnostic Tests
Test Description
NODEBS COM Verifies fault-tolerant compare logic using built-in test functions.
This is a Nodebus compare logic test.
CLNDR CLK Tests the ability to write a date and time to the calendar clock IC and
verifies that the clock runs.
PORT TEST Tests the Port Command Registers and the SSG Interrupt Controller.
DMA TEST Tests the DMA request logic for the Main Data Flow Controller and
the ability of the ADMA to perform I/O to memory transfers.
ADMA DMA Verifies all addressable hardware registers located inside the ADMA
DMA Controller.
SSG MAIN Performs a loopback test on the Main Data Flow Controllers.
SSG SEC Performs a loopback test on the Secondary Data Flow Controllers.
Table 7-7. Tank Processor 10 Diagnostic Tests
Test Description
NODEBS COM Verifies fault-tolerant compare logic using built-in test functions. This is
a Nodebus compare logic test.
against physical tables for validity and position.
172
Table 7-7. Tank Processor 10 Diagnostic Tests
Test Description
I/O PORT Verifies the shared RAM interface to the I/O subassembly, then initiates
the I/O diagnostics which run via the 8044 I/O Processor; and verifies
the results using the following tests:
 CPU – Verifies 8044 internal RAM and processor function.
 Program RAM – Tests the 8044 program RAM.
 Shared RAM – Verifies the shared RAM from the 8044 side.
 Timer Test – Functionally tests the 82C54 programmable timer IC.
 Peripheral Interface Test – Verifies the interface to the 82C55
Peripheral Interface IC. This is an I/O processor test.
Table 7-8. Carrierband LAN Interface Diagnostic Tests
Test Description
Table 7-9. INTERSPEC Integrator (IS30) Diagnostic Tests
Test Description
I/O PROCESS Tests the integrity of the 186 (I/O) subsystem of the station.
LETTERBUG Tests the module identifier character and compares the values against con-
figuration tables for validity and position.
173
174
8. Calibrating Equipment
This chapter covers system equipment change displays, station changes, peripheral changes,
calibration, and on-line network, and off-line diagnostics.
Overview of the Calibrate Actions Display

You can use the Calibrate Actions Display to perform calibration actions on Intelligent field
devices and Hydrostatic Tank Gauge units.
See the appropriate instructional manual for additional calibration information.
This section contains:
 “Accessing the Calibrate Actions Display” on page 176
 “Calibrate Transmitters to Zero” on page 176
 “Calibrate Transmitters to Zero Flow” on page 176
 “Calibrate Transmitters to Zero Total” on page 176
 “Calibrate Pressure to Zero on the P1 Transmitter” on page 177
 “Correct Measurement Errors in Height of Sensors” on page 178
 “Correct Measurement Errors in Distance Between Sensors” on page 178.
Figure 8-1. Calibration Actions Display (Typical)
175
B0193JC – Rev U 8. Calibrating Equipment
Accessing the Calibrate Actions Display

You can access the Calibrate Actions Display from the Equipment Change Display for either an
intelligent field device or the Hydrostatic Tank Gauge Interface Unit (HIU).
To access the Calibrate Actions Display:
1. From an initial system health display, select the letterbug of the station (control pro-
cessor or tank processor) containing the peripheral on which you wish to perform a
change action.
3. From the Station Display, select the appropriate FBM or HIU.
4. If you select an FBM18, FBM39, FBM43, FBM44, or FBM46, click NEXT LEVEL
and in the Intelligent Devices Display shown, select the intelligent field device to
recalibrate.
5. Click EQUIP CHG. The Equipment Change Display appears.
6. From the Equipment Change Display, click CALIB. The Calibrate Actions Display
appears listing the calibration actions available for the selected device.
Calibrate Transmitters to Zero

You can send a command from an I/A Series workstation to recalibrate transmitter to read zero.
This action is available for 820 and 860 Series pressure transmitters only.
Make sure you calibrate the transmitters to zero only when there is zero input pressure (that is,
not based on the digital measurement). Before recalibrating the transmitter, verify that the input
to the transmitter actually is zero.
To calibrate a transmitter to zero:
1. From the Calibrate Actions Display for a selected 820/860 Pressure Transmitter, select
CALIBRATE TO ZERO.
2. Start the Intelligent Transmitter Maintenance toolbox and use it with SMDH to cali-
brate the transmitter.
Calibrate Transmitters to Zero Flow

You can send a command from an I/A Series station to recalculate a transmitter so that it indicates
a zero flow reading. This action is available for CFT10 Mass Flow (Coriolis) transmitters only.
Before recalculating the transmitter to zero, verify that the transmitter flow actually is zero.
To calibrate a transmitter to zero flow:
 From the Calibrate Actions Display for the selected Mass Flowmeter, select
CALIBRATE ZERO FLOW.
Calibrate Transmitters to Zero Total

You can calibrate a transmitter so that it has a zero total. This action is available for CFT10 Mass
Flow (Coriolis) transmitters only.
To calibrate transmitters to zero totals:
 From the Calibrate Actions Display for the selected Mass Flowmeter, select
CALIBRATE ZERO TOTAL.
176
8. Calibrating Equipment B0193JC – Rev U
Calibrate Pressure to Zero on the P1 Transmitter

You can send a command to the Hydrostatic Tank Interface unit (HIU) to recalibrate the P1
transmitter in the Hydrostatic Tank Gauge System to read zero pressure.
Before recalibrating the pressure to zero, verify that the pressure on the transmitter is actually zero
(although the reading does not indicate zero).
NOTE
Before performing this recalibration, refer to TankExpert Hydrostatic Gauging and
Inventory Management System installation documentation for complete informa-
tion regarding sensor preparation.
To recalibrate the P1 transmitter to read zero pressure:

1. Verify that the pressure to transmitter P1 is zero.
2. From the Calibrate Actions Display for the selected HIU transmitter, select
CALIBRATE TRAN P1 TO ZERO PRESSURE. The system updates the HIU database
and the P1 Offset (39).

NOTE


177
B0193JC – Rev U 8. Calibrating Equipment
NOTE

Correct Measurement Errors in Distance Between Sensors

You can correct any measurement errors in the distance between Sensor P1 and Sensor P2 by per-
forming the Density Equalization Calibration action. This action is available for the Hydrostatic
Tank Gauge Interface Unit (HIU) only.
To perform the Density Equalization Calibration action:
1. Determine the liquid density through a laboratory test.
2. In the IT Maintenance Environment, change the Liquid Density Reference (21) to
the tested density value.
3. From the Calibrate Actions Display for the selected HIU transmitter, select PERFORM
DENSITY EQUAL CALIB. The Distance P1-P2 (24) parameter is updated with the
correct value.
Correct Measurement Errors in Height of Sensors

You can correct any measurement error in the height of Sensor P1 by performing the Level Equal-
ization Calibration action. This action is available for the Hydrostatic Tank Gauge Interface Unit
(HIU) only.
To perform the Level Equalization Calibration action:
1. Determine the liquid level in the tank.
2. In the IT Maintenance Environment/Configurator, change the Calibration Level
(138) to the liquid level in the tank.
PERFORM LEVEL EQUAL CALIB. The Height P1 (25) parameter is updated with the
correct value.
178
Appendix A. Device-Specific
Equipment Information
This Appendix contains device-specific information for Equipment Information.
Device specific information not found in this Appendix or in the chapters of this document can
be found in the document(s) listed in the Preface of this document.
Device specific information contained in this Appendix are:
 “Equipment Information for A-B Redundant Gateway ECB” on page 180
 “Equipment Information Fields for Allen-Bradley PLC Devices
(ECB63, ECB64, ECB65)” on page 182
 “Equipment Information for the A-B Station” on page 184
 “Equipment Information for the A-B Station PLC5 Series” on page 189
 “Equipment Information for the A-B Station Rack” on page 191
 “Equipment Information Fields for AW70 with Bristol Babcock RTUs ECB96” on
page 193
 “I/O Driver Counters” on page 193
 “Equipment Information Fields for AW70 for Bristol Babcock RTUs ECB97
Devices” on page 199
 “Equipment Information Fields for Device-Oriented ECB Devices” on page 204
 “Equipment Information for Device Integrator Peripherals” on page 206
 “Gateway Peripherals Equipment Information Fields” on page 208
 “GE Controllers (ECB66, ECB67, ECB68) Equipment Information Fields” on
page 212
 “INI10, INI15 or SPECTRUM Interface Processor Peripheral Equipment Informa-
tion Fields” on page 214
 “Intelligent Field Devices Equipment Information Fields” on page 215
 “820 and 860 Series Transmitter, Magnetic Flowmeter, Vortex Intelligent
Transmitter and Temperature Transmitter” on page 216
 “CORINT Mass Flowmeter” on page 227
 “931D Gas Chromatograph” on page 232
 “Hydrostatic Interface Unit (HIU)” on page 236
 “INTERSPEC Integrator Translator Equipment Information” on page 247
 “INTERSPEC Integrator 30 Peripherals Equipment Information” on page 249
 “AIM (Analog Input Module) and CCM (Controlled Communication Mod-
ule)” on page 249
 “UIO (Universal Input/Output) and UFM (Universal Field Module)” on
page 253
179
B0193JC – Rev U Appendix A. Device-Specific Equipment Information
 “I/O Gate Peripherals Equipment Information” on page 256

 “Micro-I/A AB-IO Peripherals Equipment Information” on page 259
 “Micro-I/A AB-PIO Peripherals Equipment Information” on page 260
 “Micro-I/A AB-RIO Peripherals Equipment Information” on page 262
 “Micro-I/A GE-IO Peripherals Equipment Information” on page 263
 “Micro-I/A GE-PIO Peripherals Equipment Information” on page 264
 “Micro-I/A Station Equipment Information” on page 266
 “Modicon Devices (ECB60/61/62) Equipment Information” on page 269
 “Port ECB Devices Equipment Information” on page 271
 “Redundant FBM46 Equipment Information” on page 273
 “760 Micro Controller Devices Equipment Information” on page 277
 “Workstation Processor Peripherals Equipment Information” on page 278
Equipment Information for A-B Redundant Gateway

ECB
Displays communication information specific to the Allen-Bradley Redundant Gateway
station (ECB).
Figure 8-2. Equipment Information for Allen-Bradley Redundant Gateway
NAME
The physical letterbug assigned to the Allen-Bradley Gateway.
180
Appendix A. Device-Specific Equipment Information B0193JC – Rev U
NOTE
Each half of a redundant gateway pair has a unique physical letterbug. The system
references a redundant partner (ABG-R) via a logical letterbug. This field identifies
the redundant partner’s letterbug.
TYPE
Redundant refers to the redundant gateway ECB. This ECB contains additional software infor-
mation that allows you to monitor the current operational state of the Allen-Bradley Gateway
with which it is associated.
RUN MODE
On-line. The redundant ECB is installed initially as On-line after the primary FBM is “fixed” and
configured.
If the station is currently in control, you can select GO OFF-LINE from the Equipment Change
Display to change the operation state of the station from control (CTL) to track (TRK). This
change in state occurs only if the redundant partner is ready and able to assume the CTL state;
otherwise, selecting GO OFF-LINE has no effect.
Off-line status:
 Check hardware.
 Download, if necessary.
 Check related fields (DOWNLOAD and EEPROM UPDATE).
FAIL STATE
Displays Failed or Not Failed (default). This value changes to Failed if a CIO configurator error
occurs in the A-B Gateway in the tracking mode.
Failed status:
 Check PIO Bus and A-B PLC.
 Check software.
 Check for Gateway station (Primary A-B or ECBP).
FAIL ACKED
Displays Acknowledged (default) or Not Acknowledged. If the FAIL STATE value changes from
Not Failed to Failed, the value in this field changes to Not Acknowledged to indicate this
transition.
Click ACK to acknowledge the selected faulted device or click ACK ALL in the initial system man-
agement display to acknowledge all the unacknowledged devices for which the workstation has
responsibility.
If the Not Acknowledged status appears, check printed/historical log for type of failure. To clear,
click ACK or ACK ALL on the configured workstation processor.
181
DATABASE UPLOAD MODE

Indicates when the station is uploading a memory dump of its current state to a file on the host.
DATABASE DOWNLOAD MODE

Indicates when a station is downloading the station’s image from the host. This downloading
occurs when a station is rebooted.
LAST SWITCH
Displays Successful if the last switch-over to the redundant partner gateway (from Control to
Track or from Track to Control) was successful; otherwise, displays Not Successful.
If this field displays a Failed status condition (indicates failure to switch to other redundant
gateway):
 Check hardware.
HARDWARE TYPE
The ECB number, 41, associated with the A-B GW redundancy software. This software provides
additional monitoring information regarding the selected gateway.
SOFTWARE TYPE
This number, 24, is associated with the software used in the redundant gateway.
SOFTWARE REV
The revision level of the software associated with the A-B GW redundant ECB.
OPERATION STATE
The mode related to the A-B gateway station with which the ECB is associated. The possible val-
ues are:
 CTL: The ABG-R station is interfacing with A-B PLCs and updating all com-
pounds/blocks associated with A-B PLCs.
 TRK: The ABG-R station is tracking all processing performed by the controlling gate-
way station. The redundant gateway is ready to assume control (CTL) as required.
 SBY: The ABG-R station is reloading or has no communication with the
Allen-Bradley PLCs.
 SBY/FAIL: There is a database failure. You need to reboot the ABG-R station from
the Equipment Change Display.
Equipment Information Fields for Allen-Bradley PLC

Devices (ECB63, ECB64, ECB65)
NAME
User-supplied ECB name, as configured using ICC.
182
TYPE
Identifies the type of Allen-Bradley device as follows: AB PIOM (A-B Port ECB63); AB PLC
(A-B PLC ECB64); AB SCAN (A-B Scan ECB65).
RUN MODE
On-line or Off-line (default). This value changes to On-line when the station reports to the Sys-
tem Monitor after booting up. You can change the RUN MODE using the GO ON-LINE and GO
OFF-LINE options in the Equipment Change Display. If station reporting is disabled, the last
known run state appears in this field. If reporting is disabled, the last known state appears in this
field. The system updates this field when a status change occurs.
RUN MODE and FAIL STATE are separate but related fields for some stations. Although you can
use the GO ON-LINE and GO OFF-LINE options to change the RUN MODE to Off-line, this does
not fail the station. However, a failed station changes the RUN MODE to Off-line.
This value changes to Off-line if any of the following occur:
 A reboot of the station.
 An EEPROM update.
 An off-line diagnostic request.
on-line).
For fault-tolerant stations, refer to the PRIMARY MODE and SHADOW MODE fields for the current
RUN MODE of each module of the pair.
DEVICE STATE
lowing occur:
 A hardware problem causes the station to fail for more than two minutes
on-line) is performed
 Any station hardware failure or communication failure results in the station not able
to send its internal reports for two or more minutes
 Operator-initiated equipment change actions (REBOOT, EEPROM UPDATE) or off-line
diagnostics change the RUN MODE to Off-line, but do not change the FAIL STATE to
Failed.
FAIL ACK STATE

edged to indicate this transition. Use the ACK key in the top menu bar of the Equipment Informa-
tion Display to acknowledge the selected faulted device or use the ACK ALL key in the top menu
bar of the initial System Management Display to acknowledge all the unacknowledged devices for
which the workstation has responsibility.
183
ALARMING STATE
the System Monitor continues to indicate overall system and network health (a green System bar)
while equipment is failed or off-line, and any system alarm messages are not logged to the system
printer or to the Historian.
HARDWARE TYPE
Number associated with the peripheral hardware, as follows: 103 (ECB63); 104 (ECB64); 105
(ECB65). This value is configured with the ICC for the specific ECB.
SOFTWARE TYPE
Number identifying the software used in the DIW devices, as follows: 63 (ECB63); 64 (ECB64);
65 (ECB65). This value is configured with the ICC for the ECB.
COMPOUND NAME
Displays the compound name for the device. This field does not apply to the ECB63 device.
BLOCK NAME
Displays the block name for the device. This field does not apply to the ECB63 device.
PRIM CMD STAT

Primary Command Status represents a communication status code. This field does not apply to
the ECB63 device.
Code Associated Status Condition

0 Does not apply
4 Device failure
PLC ERROR STAT

0; This field does not apply to the ECB63 device.
PLC EXT STAT

Equipment Information for the A-B Station

Contains information specific to the A-B station. The A-B station consists of the A-B station
module and any of the following PLC5 Series processors integrated into the I/A Series architec-
ture: PLC5/11, PLC5/20, PLC5/30, PLC5/40, PLC5/60, or PLC5/80.
STATION NAME
Station letterbug assigned during system hardware configuration.
184
TYPE
The information in this section is specific for the Allen-Bradley station (ABSTA). For other sta-
tions, see “TYPE” on page 74.
RUN MODE
tem Monitor after booting up. You can change the RUN MODE using the GO ON-LINE and
GO OFF-LINE options in the Equipment Change Display. If station reporting is disabled, the last
on-line)
For fault-tolerant stations refer to the PRIMARY MODE and SHADOW MODE fields for the current
FAIL STATE
Failed or Not Failed (default). The system updates this field when a status change occurs.
The following can change this field to a Failed state:
 You click FAIL after running off-line diagnostics
 You pulled/pushed the station, and it required more than two minutes to come back
on-line
 Any station hardware failure or communication failure that prevents the station from
sending its internal reports for two or more minutes.
The operator-initiated equipment change actions (REBOOT, EEPROM UPDATE) and the off-line
diagnostics change the RUN MODE to Off-line, but do not change the FAIL STATE to Failed.
FAIL STATE of each module in the fault-tolerant pair.
FAIL ACK STATE

Failure Acknowledged State Displays Acknowledged (default) or Not Acknowledged. If the FAIL
STATE value changes from Not Failed to Failed, the value in this field changes to Not Acknowl-
edged to indicate this transition.
185
responsibility.
If the status is Not Acknowledged, check printed/historical log for type of failure. To clear, click
ACK or ACK ALL on the configured workstation processor.
ALARMING STATE
Historian.
If the state is Not Responding or Not Acknowledged, check hardware.
FT STATE
No Information for non-fault-tolerant stations; and Operational or Non-Operational for fault-
tolerant stations. If one of the two modules in the fault-tolerant pair is off-line or failed, the state
is Non-Operational.
ALARMING STATE
Historian.
FAIL DEV ATT

Failed Device Attached displays Yes if one or more devices attached to this station are failed.
FAIL DEV ACK

Failed Device Acknowledged displays Acknowledged (default) or Not Acknowledged. If any of
the attached devices become unacknowledged, displays Not Acknowledged.
Not Acknowledged status indicates that one or more of the attached peripherals has failed.
To clear:
1. Verify status of peripherals.
2. To clear the failure and the asterisk (*) on the station, click ACK or ACK ALL on the
186
DIAG STATE
Diagnostic State displays Diag Active or Not Active (default). When you select off-line diagnos-
tics, the status changes to Diag Active until you click either RESTART or FAIL.
For fault-tolerant station displays, the primary and shadow information is valid if the FT STATE is
either Operational or Non-Operational.
Diagnostic status:
 Module in OLDD. (OLDD tests are available to diagnose failures.)
 Perform RESTART in Off-Line Diagnostic Display.
EE UPDATE STATE
Displays EE Updating or Not Updating (default). When you select EEPROM UPDATE from the
Equipment Change Display, this value changes to EE Updating until the action completes.
DOWNLOAD STATE
Displays Downloading or Not Downloading (default). When the station is rebooted because of
an operator-initiated request, the status changes to Downloading until the reboot is completed.
DOWNLOAD STATE.
MT REPORT STATE
Reports the Master Timekeeper state for the station. The I/A Series network can have only one
Master Timekeeper enabled at a time. Master Timekeepers are found only in application proces-
sors (APs), application workstations (AWs), and personal workstations (PWs) – except PW-OE.
Other stations cannot have a Master Timekeeper configured.
Possible Status Conditions:
 Enabled: This station can support a Master Timekeeper, and the master is currently
active.
 Not Enabled: This station can support a Master Timekeeper, and the master is cur-
rently inactive.
 Not Configured: This station cannot support a Master Timekeeper.
SM REPORT STATE
Station Manager Report State indicates the type of internal reporting taking place from the Sta-
tion Manager to the System Monitor, as follows:
 Report All: All event and counters are reported. Report All is the default unless
changed in the Equipment Change Display.
 No Counters: Only events are reported.
 No Reporting: No reporting of events or counters.
The states available from the Equipment Change Display are as follows: ENABLE ALL REPORTS
and DISABLE ALL REPORTS.
187
PRIMARY MODE
If this station is fault-tolerant, the following values can appear:
 Single Primary: Only one of the fault-tolerant modules is running. Check the shadow
hardware. Check the interlink.
 Married Primary: Both modules running are married. This one is primary.
 EE Updating: Module updating firmware.
 Downloading: Module downloading image.
 Failed: This module has failed. Check module hardware. Check the interlink.
 Diags Active: Diagnostics active on this module.
If this station is not fault-tolerant, this field displays No Information.
For fault-tolerant station displays, the primary information is valid if the FT STATE is either
Operational or Non-Operational.
If the station is not configured to be fault-tolerant, refer to the FAIL STATE field on this display
for the latest status.
SHADOW MODE
 Married Shadow: Both modules running are married. This one is shadow.
PRIM ROM ADDRESS

this field specifies the MAC address of the Primary Station assigned during manufacturing.
When a fault-tolerant module replacement occurs, you must recall this display to access informa-
tion for the new module.
SHAD ROM ADDRESS

this field specifies the MAC address of the Shadow Station assigned during manufacturing.
STATION ADDRESS
this field specifies a unique MAC address for a fault-tolerant station pair when married. This field
is unique if the station can be configured to be fault-tolerant. This field specifies the same address
as the PRIM ROM ADDRESS if the station cannot be configured to be a member of a fault-tolerant
pair. (LI FT stations and ATSs have their own unique numbers.)
188
PRIM HARD PART/SHAD HARD PART

PRIM HARD REV/SHAD HARD REV
PRIM HARD DATE/SHAD HARD DATE
Dates and revision levels are supplied by manufacturing.
PRIM EEPROM REV

SHAD EEPROM REV

the Equipment Change actions on the Shadow module of a fault-tolerant pair.
SOFTWARE VERSION
Indicates the release level of station software currently running in the station. Not currently used.
Equipment Information for the A-B Station PLC5 Series

NAME
Letterbug assigned to the PLC.
TYPE
The type is determined by the A-B station when checking the devices on its PLC.
The type for this A-B PLC can be one of the following: PLC5/11, PLC5/20, PLC5/30, PLC5/40,
PLC5/60, or PLC5/80.
RUN MODE
tem Monitor after booting up. You can change the RUN MODE using the GO ON-LINE and
GO OFF-LINE options in the Equipment Change Display. If the station reporting is disabled, the
last known run state appears in this field. If reporting is disabled, the last known state appears in
this field. The system updates this field when a status change occurs.
189
on-line)
FAIL STATE
on-line
FAIL ACK STATE

Failure Acknowledged State displays Acknowledged (default) or Not Acknowledged. If the FAIL
responsibility.
If the state is Not Acknowledged, check printed/historical log for type of failure. To clear, click
ALARMING STATE
Historian.
PLC MODE
Displays the PLC mode, as follows:
 RUN Mode: The PLC is running the ladder program and is driving the outputs.
190
 PROGRAM Mode: The PLC is being programmed with ladder logic, is not running a
ladder program, and is not driving the outputs.
 TEST Mode: The PLC is running the ladder program and updating in-memory data
fields, but is not driving the outputs.
DH ADDRESS
Address of the PLC on the A-B Data HighwayPlus™ displayed in decimal.
RAM STATUS
Displays the PLC RAM status as either good or bad. If bad, refer to the PLC documentation.
MAX PROGRAM SCAN

The Maximum Program Scan is the current maximum value (in milliseconds) for the last pro-
gram scan.
MAJOR FAULT
A bit pattern display of major faults in the PLC. Major faults (for example, a hardware fault) halt
the processor and stop it from processing information. Consult your PLC documentation for the
meaning of fault codes.
FAULTED PGM RUNG

The rung number of the ladder program executing when the fault occurred.
MINOR FAULT 1
A bit pattern display of minor faults in the PLC. Minor faults indicate a problem that is not severe
enough to halt the processor. Consult your PLC documentation for the meaning of fault codes.
FAULTED PGM FILE

The name of the file that contains the ladder program executing when the fault occurred.
MINOR FAULT 2
A bit pattern display of minor faults in the PLC. Minor faults indicate a problem that is not severe
enough to halt the processor. Consult your PLC documentation for the meaning of fault codes.
FAULT CODE
Consult your PLC documentation for the error corresponding to the fault code.
Equipment Information for the A-B Station Rack

The A-B Station Rack is always a site specific I/O card. All rack-specific fields indicate status and
cannot be set.
NAME
Letterbug assigned to the A-B Rack.
TYPE
A-B Rack.
191
RUN MODE
on-line)
FAIL STATE
 You click FAIL after running Off-line Diagnostics
on-line
FAIL ACK STATE

responsibility.
192
If the state is Not Acknowledged, check printed/historical log for type of failure. To clear, click
ALARMING STATE
Historian.
RACK FAULT
Displays Yes if the rack configuration is correct; otherwise, displays No.
RACK QUEUE FULL

Displays Yes if the block transfer queue is full; otherwise, displays No.
RACK INHIBIT
Displays Yes if the rack is inhibited; otherwise, displays No. If the rack is inhibited, the A-B Sta-
tion does not scan the I/O.
RACK RESET
Displays Yes if the outputs to the rack are turned off and stay off until the Rack Reset is cleared;
otherwise, displays No. When the PLC gets no response from the rack after 100 ms, it issues a
Reset.
I/O SLOT 0-15

User-defined names for I/O devices installed in the related slots.
Equipment Information Fields for AW70 with Bristol

Babcock RTUs ECB96
The Equipment Information Display for the AW70 with Bristol Babcock RTUs displays a variety
of information about the equipment, including communications statistics received from the
OBSI (ECB96).
I/O Driver Counters

I/O driver counters are performance statistics provided by the AW70 I/O driver that indicate the
I/O load being placed on the AW70. The six I/O driver counters provide information useful for
tuning the AW70 to obtain the desired I/O performance.
The counters’ numbers, if taken at their individual absolute face values, do not provide useful
information. They must be considered together, relative to each other, to provide an indication of
the load that the configuration has put on the I/O.
Communications statistics, at a frequency derived from the data obtained from the RTU OBSI
configuration, update the station manager. For a small system (for example, a few RTUs and few
193
levels or one level of communication), this update frequency may be thirty seconds. For a large,
widely distributed, multi-level system, this update frequency may be ten minutes.
The AW70 I/O driver cycles every half-second (500 ms) to service transaction requests from the
blocks and from the maintenance task, and to effect the periodic polling for signal values that are
in the live database. Each time the driver executes, it keeps track of how long it takes to do its
work, maintaining a counter for each of the six I/O driver counters.
The maintenance task, at its own frequency, retrieves communications statistics from OBSI, from
each configured RTU, and from the I/O driver (the six counters), and forwards this data to the
station manager, where it may be viewed using the Equipment Information Displays. Each time
the I/O driver sends the (requested) counts to the maintenance task, the counters are reset to zero
for the next cycle.
Relatively low I/O loads are indicated when the I/O LOAD LO-LO is large relative to the other
counts; and a relatively large value in the I/O LOAD HI-HI counter indicates a high I/O load.
Overruns indicate that the I/O driver could not complete its work in its allotted time (500 ms).
NAME
TYPE
The type of station, either BB Port or BB RTU, is defined when the letterbug is assigned during
system hardware configuration.
RUN MODE
On-line or Off-line. The device is installed as Off-line. This value changes to On-line when the
station reports to the System Monitor after booting up. If reporting is disabled, this field displays
the last known state.
RUN MODE and FAIL STATE are related fields for some stations. Although certain Equipment
Change options change the RUN MODE to Off-line, they do not fail the station. However, a failed
station results in the RUN MODE changing to Off-line.
This field changes to Off-line if any of the following occur:
on-line)
DEVICE STATE
Failed or Not Failed. This field is initially Not Failed.
This field changes to Failed if any of the following occur:
194
on-line
The operator-initiated equipment change actions (REBOOT, EEPROM UPDATE) and off-line diag-
FAIL ACK STATE

responsibility.
ALARMING STATE
Historian.
FAIL DEV ATT

FAIL DEV ACK

the attached devices become unacknowledged, it displays Not Acknowledged.
COMPOUND NAME
Compound name for this ECB69 or ECB97 device.
BLOCK NAME
The text string configured (through ICC) for the NAME parameter of this ECB96 or ECB97.
All I/O blocks use this name in their IOM_ID parameter to reference the device.
HARDWARE TYPE
Number for this device configured through ICC for the associated ECB type.
ECB Type Hardware Type

ECB96 158
ECB97 159
195
SOFTWARE TYPE
Number configured through the ICC for the software used with the associated ECB type.
ECB Type Software Type

ECB96 0
ECB97 0
PORT FLAGS
Indicates type and status of data exchange.
Currently the flags are as follows:
Flag Description
0x02 WAIT LOCK The process attached to the message exchange is currently accessing
the wait packet queue.
0x20 THROTTLE A message exchange which allows requests to be sent if the quota of
buffers used exceeds the maximum allotted.
0x40 UNSOL MSG A message exchange which is expecting requests from the remote sys-
tem, but in an asynchronous fashion. If this flag is not set, if a solic-
ited type message (one without the BSI_UNSOL_MSG flag set)
arrives without a matching wait packet, the message is discarded.
0x80 CRIT APP If this bit is set, the open BSI cannot be shutdown until the current
message exchange is released.
PRM CMD STAT

Primary Command Status represents a communication status code.

0 Normal – No Problem
1 A retry will be made in an attempt to clear a problem.
2 Device did not respond.
4 The response from the device had one of the following errors:
 Exception code returned by the device (which is saved in
DEVICE STATUS),
 Parity, framing, buffer overrun,
 Block-check (CRC) error.
DEVICE STATUS
Exception error code sent by the device in a reply message.
Code Number Meaning

1 Normal – No error
196
Code Number Meaning

2 No communications event present
DEV CMD STATUS

Device Command Status is a non-zero value indicating that an error was detected by the commu-
nication driver software.
If the condition persists (preventing successful communications) and is not eliminated by a hard-
ware reset of the AW70, replace the communications card. If the condition occurs frequently, but
is not debilitating, report it to your Invensys representative.
MESSAGE SENT
Number of messages sent from this message exchange since the last time the MEX was allocated
or the statistics initialized.
WAIT MESSAGE
Number of message blocks awaiting processing by the current process.
MESSAGE RECV
Number of messages processed by this message exchange.
LOCAL MESSAGE
If non-zero, the message exchange currently has message data which was copied to the local
queue.
BUFFER OVERFLOW
Number of times this server attempted to send out more messages than allowed by its reserved
buffer count.
WAIT RESPONSES
Number of responses for which the current service is waiting.
NO BUFFERS
Number of times that an allocate buffer or send message was refused due to a lack of buffers in the
system. This value should always be zero.
MAX BUFFERS
Maximum number of buffers allowed to be reserved by this message exchange (task). A buffer is
reserved when the MEX expects a response to a previously sent message.
LOCK ERROR
Number of times a conflict occurred, locking this message exchange.
USED BUFFERS
Number of buffers currently reserved for use by the message exchange (task). In general, the num-
ber of buffers cannot exceed the maximum buffer count; however, exceptions can arise during
peak communications loading.
197
MESSAGE TIMEOUTS
The number of messages that timed out while waiting for a response.
NEXT TIMEOUT
Count of time-out intervals before the first waiting message for this MEX times out.
BUFFER TIMEOUTS
Number of buffers moved from the WAIT queue due to slow processing.
NOTE
The entire message that timed out must have expired before a buffer was removed.
LAST TIMEOUT
Count of intervals before the last message on the incoming queue times out.
BUFFERS MOVED
Count of buffers moved from the WAIT queues to the process local queue due to a shortage of
free buffers in the system.
IO LOAD LO_LO
Number of scheduled I/O driver executions, during the most recent reporting cycle, that had an
elapsed total execution time in the range 0 to 100 ms.
IO LOAD LO
IO LOAD MED
IO LOAD HI
IO LOAD HI-HI
IO OVERRUNS
Number of scheduled I/O driver executions, during the most recent reporting cycle, that overran.
198
Equipment Information Fields for AW70 for Bristol Babcock

RTUs ECB97 Devices
NAME
TYPE
RUN MODE
On-line or Off-line. The device is installed as Off-line. This value changes to On-line when the
station reports to the System Monitor after booting up. If reporting is disabled, this field displays
the last known state.
RUN MODE and FAIL STATE are related fields for some stations. Although certain Equipment
Change options change the RUN MODE to Off-line, they do not fail the station. However, a failed
station results in the RUN MODE changing to Off-line.
This field changes to Off-line if any of the following occur:
on-line)
DEVICE STATE
Failed or Not Failed. This field is initially Not Failed.
This field changes to Failed if any of the following occur:
on-line
FAIL ACK STATE

199
responsibility.
ALARMING STATE
Historian.
FAIL DEV ATT

FAIL DEV ACK

the attached devices become unacknowledged, displays Not Acknowledged.
COMPOUND NAME
Compound name for this ECB69 or ECB97 device.
BLOCK NAME
The text string configured (through ICC) for the NAME parameter of this ECB96 or ECB97.
All I/O blocks use this name in their IOM_ID parameter to reference the device.
HARDWARE TYPE
Number for this device configured through ICC for the associated ECB type.
ECB Type Hardware Type

ECB96 158
ECB97 159
PORT STATUS
Flags indicating current status of the current RTU.
The applicable values are as follows:
Value Description
0x01= PORT_OFFLINE Indicates that the RTU is not configured into system.
0x02= TIME SYNC NEEDED Set when the RTU is due to receive a time sync message.
0x04= PORT_DEAD Set when the current RTU will not accept messages.
200
Value Description
0x08= CONFIG ERROR Set when an RTU is declared inactive due to a configuration
error on the current communication line.
0x10= DOWNLOADING Download to current RTU is in progress.
0X20= NEED POLL The attached RTU requires a poll on the next poll pass. Used
to implement a preferred poll pass of only those nodes which
responded to the previous poll pass.
PRIM CMD STATUS

The Primary Command Status represents a communication status code.

0 Normal – No Problem.
1 CMD_INV = invalid command used
PORT FLAGS
Flags indicating the options used for the current RTU.
Value Description
0x01= LOCAL SLAVE This is directly connected to RTU.
0x02= FIRST SLAVE Current RTU is the first slave defined on the line.
0x04= DIAL LINE This RTU is on a line which must be dialed.
0x08= MODEM This RTU requires RTS/CTS keying.
DEV CMD STATUS

The Device Command Status is the request type.
PORT TYPE
Flags indicating the protocol used.
 0x01 = BSAP
 0x02 = REMOTE
 0x03 = EBSAP.
DEVICE STATUS
Exception error code sent by the RTU in a reply message.
Code Number Meaning

1 Normal – No error
2 No communications event present
201
Code Number Meaning

3 Node requires local download
20 Data stored in user buffer
21 Some data has been stored
22 Data not available – communications error
23 Error attempting to send to BSI
24 Node name not found
25 Error parsing response
27 Node’s load version has changed
-100 MEX not initialized for process
-101 Service already allocated by other process
-102 No unused service found
-105 Unable to reserve wait packet for response
-115 System not initialized
-116 Initialization already performed
-117 Not correct NETTOP version number
-118 First level slave not accepting message
-119 Message to send has invalid length
-121 Invalid MEX number specified
-122 Invalid first level slave number specified
-126 RTU not located in NETTOP file
-127 Communication line already started with /name
READ MESSAGE CNT

Read messages sent/received.
READ NAK COUNT

Read NAK sent/received.
READ TIMEOUTS
Read timeouts on sent/received.
READ CRC ERRORS

Read CRC errors statuses sent/received.
WRITE MSG COUNT

Write messages sent/received.
WRITE NAK COUNT

Write NAK sent/received.
WRITE TIMEOUTS
Write timeouts on sent/received.
202
WRITE CRC ERRORS

Write CRC errors statuses sent/received.
BUFFER OVERFLOW
Input character buffer overflowed before receiving the end of message sequence.
MISSING END MSG

A start message sequence was detected before receiving the corresponding end codes for the previ-
ous message.
INVALID DLE
An invalid DLE sequence was received: the DLE (10 hex) was not followed by an ETX (03 hex),
STX (02 hex), SOH (01 hex), or DLE.
NO BUFFERS
A buffer was not available to load an incoming message.
INVALID ACK
An unexpected ACK message was received, or the ACK message contained an invalid message
identifier.
DUPLICATE ID
Number of times that a message was received with a duplicated sequence number. This can occur
when a remote system misses an ACK message.
ACK TIMOUTS
The number of times an acknowledgment for a message was not received with the allowable time
interval.
DIAL OK
Number of times this RTU was connected successfully via a dial operation.
DIAL FAIL
Number of times a dial operation failed to the current RTU. This value is available only on sys-
tems that support dial-up.
OUT QUEUE
Number of messages waiting to be sent to this RTU.
NOTE
When using direct connect BSAP, this field is maintained for the first slave on the
communication line only.
RETRY COUNT
Number of attempts made to send the current message out of the communication port. For direct
connect BSAP, this field is maintained on the first slave on the communication line only.
203
Equipment Information Fields for Device-Oriented

ECB Devices
This display provides general purpose information for the device-oriented ECB devices
(DEVICE) attached to the related station. These ECB devices act as generic placeholders for your
specific second level of addressing.
Refer to the documentation for your device or gate for complete information.
NAME
Network device.
TYPE
RUN MODE
Initializes to Off-line when installed.
Display to change the operational state from On-line to Off-line.
Off-line status occurs as an operator action, or if this is a newly installed ECB that has never been
put on-line.
DEVICE STATE
 Port is configured to receive a specific GO-OFF-LINE trigger and a trigger event occurs
 I/O gate terminates
 Server terminates
 Foreign device indicates failure to I/O gate.
Making the I/O gate and/or server operational causes the system to change the status to Not
Failed as long as the port is on-line.
When foreign device indicates on-line to I/O gate, the status changes to Not Failed.
FAIL ACK STATE

transition.
responsibility.
ALARMING STATE
204
Historian.
COMPND NAME
The Compound name for this ECB device.
BLOCK NAME
The Block name for this ECB device.
HARDWARE TYPE
The ECB number associated with the device-oriented ECB device communications software.
SOFTWARE TYPE
This number identifies the software used in the device-oriented ECB device communications.
FAIL ALGO
Failure Algorithm indicates the failure algorithm used to cause the device to fail internally even if
it is connected and on-line. When the device fails, the system generates a trigger ID if the
TRG_OF is configured. Triggers communicate event information between ECBs and can be used
to initiate status changes in the destination ECBs. This failure algorithm can be configured to
determine the ratio of error communications to good (complete) communications.
The possible values are as follows:
 1 = WatchDog timeout
 2 = Trigger Event.
0x10, 0x100, or 0x1000 = the ratio of errors to good messages over the last 10,100, or 1000 mes-
sages, respectively.
NOT FAIL ALGO

The Not Failed Algorithm identifies the algorithm that causes the device to go to the Not Failed
state. When the ECB returns to the Not Failed state from Failed, the system generates a pre-
defined trigger ID if TRGONF is configured with the ID.
Refer to the documentation for the specific device for complete information.
 1 = The device goes back on-line based on the On-line timer value.
 2 = The device goes back on-line based on the Trigger ID generated.
SERVER TYPE
This field is blank for ECB devices.
SERVER NAME
Identifies the name of the server (driver) used for communications with the related gate. (Each
gate type can have more than one server.)
205
WD TIMER
Indicates the value of the device ECB watchdog timer (in seconds). When this value is zero, the
watchdog timer expires and the device goes off-line.
ONL TIMER
The On-line Timer indicates the number of seconds before the off-line ECB device attempts to
go on-line.
PARENT NAME
Identifies the parent ECB port for this device.
This name should be the name of the port ECB and not the name of the port ECB’s IOM_ID.
ALT NAME
The Alternate Parent Name is an optional field. It identifies the alternate parent ECB port for this
device, if one is defined.
This alternate port takes over if the designated parent ECB port fails.
This name should be the name of the port ECB and not the name of the port ECB’s IOM_ID.
Equipment Information for Device Integrator

Peripherals
This Equipment Information Display contains information specific to the selected Device Inte-
grator peripheral.
NAME
This name, PORT 00, 01, 02 or 03, is predefined by the gateway device.
TYPE
This type, FD_RS-232, identifies that the Foreign Device Gateway supports the FD_RS-232
device.
RUN MODE
On-line or Off-line. You can change the RUN MODE using the GO ON-LINE and GO OFF-LINE
options in the Equipment Change Display. If the gateway is disabled, the last known run state of
this peripheral appears.
Off-line status:
 Check hardware.
FAIL STATE
Not Failed or Failed. The Foreign Device Gateway peripheral is installed as Failed, Off-line and
remains as such until you put it on-line.
206
The following actions change this field to Failed:

 You physically disconnect the port.
 A physical failure occurs.
If the field indicates a Failed status:
 Check Fieldbus and Foreign Device Gateway (FDG).
FAIL ACK STATE

Failure Acknowledged State displays Acknowledged (default) or Not Acknowledged. If the
DEVICE STATE value changes from Not Failed to Failed, the value in this field changes to Not
Acknowledged.
Click ACK in this display to acknowledge the selected faulted device; or click ACK ALL in the ini-
tial system management display to acknowledge all unacknowledged devices for which the work-
station is responsible.
If the field indicates a Not Acknowledged state:
ALARMING STATE
Historian.
PROTOCOL
Identifies the protocol used on the port. Refer to the programmer’s reference guide for the specific
device to determine the protocol this number represents.
STOP BITS
Displays the number of stop bits, 1 or 2, required by the foreign device. You set this value during
integrated control configuration.
PARITY
Indicates the type of parity required, as either None, Odd, or Even. You set this value during Inte-
grated Control Configuration.
ECHO ENABLED
Indicates the echo mode as either enabled (Yes) or disabled (No). You set this value during inte-
grated control configuration.
207
WAIT FOR EOM

Displays the amount of time the system waits for the end of message signal. This number repre-
sents the value in tenths of a second, for example, 5 indicates 0.5 of a second.
WAIT FOR RSP

Indicates the amount of time the system waits for a response signal. This number represents the
value in tenths of a second, for example, 5 indicates 0.5 of a second.
RETRY COUNT
The number of times a device tries to resend a message before timing out. The range of configu-
rable counts depends on the type of Foreign Device peripheral; this value is set during Integrated
Control Configuration.
LINE TIME
Length of time to validate a change of state when the data carrier detects signal changes. This
number represents the value in tenths of a second, for example, 5 indicates 0.5 of a second.
MAX INPUT BYTES

The maximum number of bytes in a message. The range of configurable bytes depends on the
type of Foreign Device peripheral.
BAUD RATE
The rate for sending transmissions, 300, 600, 1200, 2400, 4800, 9600, or 19200. The range of
configurable baud rates depends on the type of Foreign Device peripheral and is set during Inte-
grated Control Configuration.
DATA BITS
The number of data bits per message word, 8, 7, 6, or 5. This number depends on the type of
Foreign Device peripheral.
Gateway Peripherals Equipment Information Fields

This Equipment Information Display contains information specific to the selected gateway
peripheral, Allen-Bradley (A-B), Modicon (MOD) or Instrument Gateway (IG).
NAME
The logical letterbug name of the gateway peripheral.
Peripheral Types Default Letterbugs

PLC (Allen-Bradley) PLC001 through PLC008
PC (Modbus PC) PLC001 through PLC008
760/761 (Controller) SSM001 through SSM030 (Port 1)
SS2031 through SS2060 (Port 2)
208
These letterbugs and ECB-type assignments can be changed by the user before a “fix” is done in
the Integrated Control Configurator to reflect the actual number and order of the devices on the
communication link.
TYPE
Type of gateway peripheral, related to the gateway to which it is attached.
Gateway Interfaces Gateway Peripheral Types

Allen-Bradley Gateway (ABG) Allen-Bradley PLC (AB PLC)
Modicon Gateway (MODG) Modbus PC (MOD PC)
Instrument Gateway (IG) 760 Controller (D760), 761 Controller (D761)
RUN MODE
On-line or Off-line. This field initially is Off-line for the A-B PLC, MOD PC, and the 760/761
controllers. The system updates this field when a status change occurs.
If the status is Off-line:
 Check hardware.
DEVICE STATE
are:
 Not Ready: A transition state, indicates the device is healthy, and normal automatic
startup procedures are bringing the device On Scan.
FAIL ACK STATE

This field does not apply to gateway peripherals.
ALARMING STATE
Historian.
209
DOWNLOAD STATE
Downloading or Not Downloading. The field changes to Downloading when the FBM is in the
process of downloading its application image. Upon completion, the field changes back to Not
Downloading whether the process was successful or not successful. This field is updated when a
status change occurs.
DEVICES ATT
This field does not apply to gateway peripherals.
LAST CABLE ACCESS

A Not OK status indicates a PIO Bus send failure. To resolve:
FAIL DEV ATT

Does not apply to gateway peripherals.
COMPOUND NAME
Compound name for the device.
FAIL DEV ACK

Does not apply to gateway peripherals.
BLOCK NAME
Block name for the device.
DIAG STATUS 1
Peripheral Explanation
AB PLC Decimal value for the number of Block Check Code
(BCC) errors determined by the gateway.
MOD PC, 760, 761 Decimal value for the number of CRC errors determined
by the gateway.
HARDWARE TYPE
Number associated with the peripheral hardware type.
Peripheral Types Hardware Type

AB PLC 31
MOD PC 32
210
Peripheral Types Hardware Type

760 34
761 35
DIAG STATUS 2
For the various peripherals (PLC, PC, 760, 761), this field is a decimal value for the number of
parity or framing errors determined by the gateway.
SOFTWARE TYPE
Number associated with the software used with the peripheral.
Peripheral Types Software Types

AB PLC 15
MOD PC 16
760 19
761 21
LOGICAL ADDR
1 through 48. FBMs are typically numbered as they appear in the display (left to right) beginning
at 1. The order of FBMs is the order in which the FBMs were “fixed” using the Integrated Con-
trol Configurator. However, if an FBM is deleted and another added later, the new FBM is given
the lowest number available. For example, if FBM02 is deleted from the sequenced group of
FBM01, FBM02, and FBM03, the next FBM added results in the following sequence group:
FBM01, FBM03, and FBM02.
MANUF DATE
The date (MM-DD-YY) of manufacture. One of the three date standards, determined during site
planning and system definition, is used: US (MM-DD-YYYY), ISO (YY-MM-DD), UR or Euro-
pean (DD-MM-YY). This format is different from the format used by the HHT display, which is
Jan 01 98.
FBM STATUS
Hexadecimal value returned in the error field of all gateway reply messages.
Fields Not Applicable to Gateway Peripherals

 DIAG STATUS 3 SOFTWARE REV
 HARDWARE PART NO.
 DIAG STATUS 4
 HARDWARE REV
 PRIM CMD STAT
 FBM CMD STATUS
 EEPROM REV
 SERIAL NUMBER
 EXTENSION TYPE.
211
GE Controllers (ECB66, ECB67, ECB68) Equipment

Information Fields
NAME
User-supplied ECB name as configured using the Integrated Control Configurator.
TYPE
Identifies the type of GE controller device, as follows: GE PORT (ECB66), GE PLC (ECB67) or
GE SCAN (ECB68).
RUN MODE
on-line)
DEVICE STATE
lowing occur:
 Any station hardware failure or communication failure that results in the station not
able to send its internal reports for two or more minutes
Failed.
212
FAIL ACK STATE

ALARMING STATE
Indicates whether alarming is Enabled or Inhibited for the device. When alarming is Inhibited,
while equipment is failed or off-line. System Alarm messages are not logged to the system printer
or the Historian.
HARDWARE TYPE
Number associated with the peripheral hardware, either 106 (ECB66), 101 (ECB67) or
102 (ECB68). This value is configured with the ICC for the specific ECB.
SOFTWARE TYPE
Number identifying the software used in the I/O Gate devices, 66 (ECB66), 67 (ECB67) or
68 (ECB68). This value is configured with the ICC for the ECB.
COMPOUND NAME
BLOCK NAME
PRIM CMD STAT

Primary Command Status represents a communication status code. This field does not apply to
the ECB66 device.

0 Does not apply
4 Device failure.
PLC ERROR STAT

PLC EXT STAT

213
LAST CABLE ACCESS

This field does not apply to the ECB66 device.
LOGICAL ADDRESS
The logical address, 1 through 16, of the peripheral. This value is configured using the ICC. The
logical address order of the peripherals is the order in which the peripherals were “fixed” during
configuration. This field does not apply to the ECB66 device.
ALTERNATE PORT
No Bkup Possible or None. Identifies whether backups are permitted to the alternate parent ECB
port for this device. This alternate port takes over if the designated parent ECB port fails or has a
change of state. This field does not apply to the ECB66 device.
INI10, INI15 or SPECTRUM Interface Processor

Peripheral Equipment Information Fields
This Equipment Information Display contains information specific to the Information Network
Interface 10 (INI10), Information Network Interface 15 (INI10), or SPECTRUM Interface Pro-
cessor (SIP). The INI10, INI15, and SIP each can have only one peripheral device, the X.25 port.
NAME
This name, PORT 00, 01, 02, or 03, is predefined by the gateway device.
TYPE
This type, FD_RS-232, identifies that the Foreign Device Gateway supports the FD_RS-232
device.
RUN MODE
 Check hardware.
214
FAIL STATE
on-line
If the status is Failed:
 Check Printer/Terminal/CPU hardware.
 Check communication path with parent station.
 Check configuration information.
FAIL ACK STATE

If the state is Not Acknowledged:
ALARMING STATE
Historian.
Intelligent Field Devices Equipment Information

Fields
This section contains equipment information specific to an Intelligent Device attached to a
selected FBM18, FBM39, FBM43, or FBM44.
Types of intelligent field devices:
215
 820 and 860 Series Transmitter

 Magnetic Flowmeter
 Vortex Intelligent Transmitter
 Temperature Transmitter
 CORINT Mass Flowmeter
 931D Gas Chromatograph
 Hydrostatic Interface Unit (HIU)
Most Intelligent Field Devices display the same information about transmitters and diagnostics
codes. The equipment information displays for the CORINT Mass Flowmeter, 931D Gas Chro-
matograph, and the Hydrostatic Interface Unit contain additional fields and are described
separately.
820 and 860 Series Transmitter, Magnetic Flowmeter,

Vortex Intelligent Transmitter and Temperature Transmitter
The Equipment Information Display for a selected station or peripheral includes type-specific
configuration information, the current health status of the station or peripheral, equipment
change action status, hardware and software information, and so forth. Equipment status fields
update when a status update occurs or when the display is re-entered. Dynamic value fields (for
intelligent devices) update every five seconds.
Refer to the equipment information for a specific device for additional information regarding
field updates.
Resolution of Intelligent Field Device Errors

For resolution of Mass Flowmeter hardware and software errors indicated in the diagnostic status
fields, see MI 019-123, CFT10 Mass Flow Transmitter Operation, Calibration and Configuration
Using Model HHT Hand-Held Terminal, and documents for CFT15.
NAME
Letterbug assigned to the intelligent device during site planning and system definition, such as
FT1302. This name is assigned to a particular channel of the FBM or interface module and must
be the same as the DEVICE NAME of the intelligent device.
TYPE
Intelligent Dev. This is a label for devices attached to the FBM18, FBM39, FBM43, or FBM44.
This type is not configurable from the IT Maintenance Environment.
RUN MODE
On-line or Off-line. The true status of the intelligent field device appears on the second page of
this display (XMTR MODE). When communicating with the transmitter, this field is updated every
five seconds on this display; otherwise, this field is updated when a status change occurs.
The run mode field changes only with the operator-initiated equipment change actions (GO OFF-
LINE and GO ON-LINE). If communication is lost between the intelligent device and the FBM or
the Fieldbus Interface Modules, the last known state appears.
216
 Check hardware.
 Download, if necessary (FBM).
 Check related fields (DOWNLOAD, EEPROM UPDATE).
DEVICE STATE
are:
 On Scan: the device is connected to the control strategy, though measurements are
 Comm Failures: no real device information is available.
 Not Ready: A transition state. The device is healthy, and normal automatic startup
FAIL ACK STATE

COMPOUND NAME
DIAGNOSTIC ERROR
For Release 4.0, an ASCII representation of the DIAGNOSTIC ERROR appears as text on the sec-
ond page of the Equipment Information Display. The system updates this field automatically
every five seconds.
To resolve ROM Checksum Error (code 2) and EEPROM checksum Error (code 3) status condi-
tions (820 and Vortex), take transmitter off-line and place on-line again. If the error code still
exists, replace the amplifier.
To resolve Fatal Input Range Error Code 7 (820 and Vortex), take transmitter off-line and place
on-line again. If the error code still exists, replace the sensor.
To resolve Arithmetic Error (code A) and Real Time Clock Error (code B) (820 and Vortex), take
transmitter off-line and place on-line again. If the error code still exists, replace amplifier.
217
Table 8-1. Magflow Status Conditions
Code 02 ROM Checksum error. Replace transmitter.

Code 0C Hardware failure. Replace transmitter.
Code 0D Shorted wire or switch failure. Replace transmitter.
Code 10 Amplifier malfunction. Replace transmitter.
Code 12 Malfunction in coil, amplifier, or electrodes. Check wiring.
Code 13 Electrodes error, or wiring problem. Check wiring and clean electrodes.
Code 14 Intermittent in coil, open wire, or low drive. Check wiring.
Code 1B External RAM test failed. Replace transmitter.
Code 20 Underrange. Wired or installed backwards.
Code 21 Overrange. High flow exists.
Code 30 Factory calibration data lost. Replace transmitter.
Code 31 Invalid user data (P1 to P5). Re-enter data.
Code 32 Invalid user data (HHT). Re-enter data.
BLOCK NAME
FBM CHAN STATUS

FBM Channel Status (Status Byte 1) indicates the status of communications to the intelligent
field device as represented by an eight-bit word. A “1” in one of the defined positions indicates the
current status.
Letterbug Name Mismatch Fault Flag (1)

Database Change (1) Calibration in Progress (1)
Communication Download (1)
Failure (1) Initializing (1)
0 0 0 0 0 0 0 0
(Bit Position 7 6 5 4 3 2 1 0)
Figure 8-3. FBM Channel Status Byte
This field contains dynamic data which is updated automatically by the system every five
seconds.
Activities or events associated with the setting of each bit to 1.
Table 8-2. FBM Channel Status Byte Bit Descriptions
Bit Description
Bit 0 The transmitter is resetting to the On-line mode.
218
Table 8-2. FBM Channel Status Byte Bit Descriptions (Continued)
Bit Description
Bit 1 A download from the FBM to the transmitter is in progress.
Bit 2 The transmitter is in the calibration mode via an HHT operation. To reset
the bit to 0 after the completion of the calibration procedure, upload the
database using the Equipment Change Display option.
Bit 3 The XMTR STATUS NO. 1 is not zero (unless an 820 transmitter is config-
ured to continue in degraded mode). Refer to the XMTR STATUS NO. 1 and
the XMTR STATUS NO. 2 field explanations.
Bit 4 A letterbug name mismatch has occurred. The system configured letterbug
does not match the Device Name in the intelligent transmitter.
Bit 5 Database has been changed. To reset the bit to zero, upload the database
using the Equipment Change Display option.
Bit 7 Communication failure has occurred and all data on the screen may be
invalid. Failed temperature measurement. Repeat Bit 1 check procedures.
TAG NUMBER
User-specified, twelve-character, alphanumeric tag number assigned during Integrated Control
Configurator (ICC).
You can change this tag number through the ICC or the HHT, as follows:
 If you use the HHT to change this tag number, you must perform an UPLOAD DATA-
BASE from the Equipment Change Display for this device.
 If you use the ICC to change this tag number, you must perform a DOWNLOAD DATA-
XMTR STATUS NO. 1 (Status Byte 2)

XMTR Status Number 1 (Status Byte 2) indicates the status of the transmitter in the form of an
eight-bit word.
Initialization Needed (1) Intelligent Trans. Busy (1)

Initialization Mag Flow (1) On-line: (00)
Diagnostic Error (1) Off-line: (01)
See Xmtr Status No 2 (1) (10) calibrate
(11) off-line
0 0 0 0 0 0 0 0
(Bit Position 7 6 5 4 3 2 1 0)
Initializing Mass Flow
Note: 0 = good, 1 = bad or subsequent action required

Figure 8-4. XMTR Status Number 1, Status Byte 2, Bit Positions
This field contains dynamic data which is updated automatically by the system every five
seconds.
219
Table 8-3. Activities or Events Associated with the Setting of Each Bit or Bits
Bits 0 to 1 Represent the transmitter mode (on-line or off-line); a two-bit counter.

Bit 2 Transmitter is busy. This bit is set temporarily while the transmitter is
busy. If the 1 does not automatically return to a zero within two screen
update cycles, place the transmitter off-line. Return the transmitter on-
line from the Equipment Change Display. If 1 still appears in the bit posi-
tion, turn the transmitter power off by disconnecting and then reconnect-
ing one of the leads attached to FBM18. If 1 still appears, replace the
transmitter.
Bit 3 Indicates the Mass Flowmeter is initializing. N/A to other devices.
Bit 4 For all devices except Magnetic Flowmeter, initialization is needed. For the
Magnetic Flowmeter, the device is currently initializing.
Bit 5 This field indicates whether the Diagnostics Error is a current or previous
error. See the DIAGNOSTIC ERROR field information.
Bit 6 XMTR STATUS NO. 2 is not all zeros; see XMTR STATUS NO. 2 field
information.
Bit 7 N/A for all devices.
XMTR TYPE NO.

The integer relating to the field device model code.
Table 8-4. Transmitter Type Number
Device Type Field Device Number Model Code

Mass Flowmeter 32 (CORINT)
Magnetic Flowmeter 42 (IMT10/IMT20/IMT25)
870 IT 44
860 Series 45
860 Style B 46
Temperature 49 (RTT10, RTT20)
Vortex IT (E83) 51
Table 8-5. 820 Series Transmitter Type Number
Field Device Number Model Code Description

01 823DP-1H 750 in H2O
02 821AL-M 280 mmHg
03 821AL-H 1400 mmHg
04 821AM-L 50 PSI
05 821AM-M 150 PSI
06 821AM-H 600 PSI
220
Table 8-5. 820 Series Transmitter Type Number (Continued)
Field Device Number Model Code Description

07 821GH-M 2000 PSI
08 821GH-H 6000 PSI
09 821GM-L 50 PSI
10 821GM-M 150 PSI
11 821GM-H 650 PSI
12 823DP-1M 150 in H2O
13 823DP-3M 150 in H2O
14 823DP-3H 750 in H2O
15 823DP-6M 150 in H2O
16 823DP-6H 750 in H2O
17 823EP-M 150 in H2O
18 823EP-H 750 in H2O
19 823MP-M 150 in H2O
20 823MP-H 750 in H2O
21 827DF-L 30 in H2O
22 827DF-M 150 in H2O
23 827DF-H 750 in H2O
24 823DP-2M 150 in H2O
25 823DP-2H 750 in H2O
28 823DP-3L 5 in H2O
NOTE
L, M, or H indicates the sensor range (low, medium, or high). The 1, 3, 6 indicates
the maximum static pressure for the 823 d/p Cell™ transmitter.
XMTR STATUS NO. 2

Indicates the status of the transmitter in the form of an eight-bit word. All undefined bits are con-
sidered spare bits. This field contains dynamic data that the system updates automatically, every
five seconds.
221
F1 Range Error (820) Poor Health (820)
Flow Alarm (Coriolis) Bad Message Content (all devices)
Bad Sensor #1 (Temp)
F3 Range Error (820) Signal Lock (Mag Flow)
Temp Alarm (Coriolis) Total Invalid (Coriolis)
Standards Failure (Temp)
0 0 0 0 0 0 0 0
(Bit Position 7 6 5 4 3 2 1 0 )
F2 Range Error (820) Updating EEPROM (820, Temp)

Density Alarm (Coriolis) Tube Operation Alarm (Coriolis)
Bad Sensor #2 (Temp) Bad Function (820, Temp, Coriolis)
Figure 8-5. XMTR Status Number 2, Status Byte 3 Description
Table 8-6 shows activities or events associated with setting each bit to 1.
Table 8-6. Transmitter Bit Settings
Bit Position Description

Bit 0 This bit is set to 1 if a MagFlow signal lock or a Mass Flow tube imbalance
occurs.
Bit 1 This bit is set temporarily while the transmitter is busy with EEPROM
updating for 820/860 Transmitter or Temperature Transmitter; or if a tube
operation alarm occurs in the Mass Flowmeter. If the 1 does not automati-
cally return to 0 within two screen update cycles, place the transmitter off-
line. Return the transmitter on-line from the Equipment Change Display. If
1 still appears in the bit position, turn the transmitter power off by discon-
necting and then reconnecting one of the leads attached to FBM18. If 1 still
appears, replace the transmitter.
Bit 2 Bad message was received. This should not occur. If the bit is set to 1, repeat
the check procedure described for setting Bit 1.
Bit 3 This bit is set if a bad message header is received by an 820/860 Transmitter,
Temperature Transmitter, or Mass Flowmeter. This bit position is not appli-
cable to the Magnetic Flowmeter.
Bit 4 This bit indicates poor health for an 820/860.
Bit 5 This bit represents a Frequency 1 Error for the 820/860 Transmitter; a flow
alarm for a Mass Flowmeter, and a bad sensor #1 for the Temperature Trans-
mitter. This bit position is not applicable to Magnetic Flowmeter.
Bit 6 This bit represents a Frequency 2 Error for 820/860 Transmitter; a density
alarm for a Mass Flowmeter, and a bad sensor #2 for the Temperature Trans-
mitter. The totalized flow has exceeded 6 digits in length (over 99999 units).
This bit position is not applicable to Magnetic Flowmeter.
222
Table 8-6. Transmitter Bit Settings (Continued)

Bit 7 This bit represents a Frequency 3 Error for 820/860 Transmitter; a tempera-
ture alarm for a Mass Flowmeter, and a standards failure for a Temperature
Transmitter. If an 820/860 Transmitter is configured to operate in a degraded
mode and the temperature sensor fails, XMTR STATUS NO. 2 Bit 7 and XMTR
STATUS NO. 1 Bit 7 are both set. However, the FBM CHAN STATUS Bit 3 is
not set and the channel remains Not Failed. If temperature measurement
fails, repeat Bit 1 check procedures. This bit position is not applicable to
Magnetic Flowmeter.
NOTE
The failure of one sensor on a Temperature Transmitter configured for dual differ-
ence or average also causes the Fault Flag in the FBM CHAN STATUS field to be set.
The failure of one sensor on a Temperature Transmitter configured to be dual
redundant does not cause the Fault Flag in the FBM CHAN STATUS to be set.
XMTR TYPE NAME

The name of the intelligent field device. The possible values are possible for this field: 820, 860,
IMT10/IMT20/IMT25 (MAGFLOW), RTT10/RTT20 (TEMP), CORINT (CORIOLIS).
DIAGNOSTIC ERROR
For Release 4.0, an ASCII representation of the DIAGNOSTIC ERROR appears as text on the sec-
ond page of the Equipment Information Display. The system updates this field automatically
every five seconds.
Resolving Problems:
 For Error Code 2, ROM Checksum Error, and error code 3, EEPROM checksum
error, for 820 and Vortex devices, take the transmitter off-line and place on-line again.
If the error code still exists, replace the amplifier.
 For Error Code 7, Fatal Input Range Error, for the 820 and Vortex devices, take the
transmitter off-line and place on-line again. If the error code still exists, replace the
sensor.
 For Code A, Arithmetic Error, and Code B, Real Time Clock Error, for 820 and
Vortex devices, take the transmitter off-line and place on-line again. If the error code
still exists, replace amplifier.
Table 8-7. Magflow Transmitter Error/Status Code
Error Code Description

Code 02 ROM Checksum error. Replace transmitter.
Code 0C Hardware failure. Replace Transmitter.
Code 0D Shorted wire or switch failure. Replace transmitter.
223
Table 8-7. Magflow Transmitter Error/Status Code
Error Code Description

Code 12 Malfunction in coil, amplifier, or electrodes. Check wiring.
Code 13 Electrodes error, or wiring problem. Check wiring and clean electrodes.
Code 14 Intermittent in coil, open wire, or low drive. Check wiring.
Code 1B External RAM test failed. Replace transmitter.
Code 20 Underrange. Wired or installed backwards.
Code 30 Factory calibration data lost. Replace transmitter.
Code 31 Invalid user data (P1 to P5). Re-enter data.
Code 32 Invalid user data (HHT). Re-enter data.
XMTR STATUS ERR

For Release 4.0, an ASCII representation of this error(s) appears as text on the second page of the
Equipment Information Display.
XMTR STATUS ERR

The device status, represented by bytes 1 and 2 of the device status packed boolean. Status bits 10
through 23 inclusive (bits 16 through 23 have different meanings for different devices) are as
follows:
Table 8-8. Transmitter Status Bits 10 to 23
Hexadecimal Value Bit Position Set Condition

400 Bit 10 Busy
800 Bit 11 Initializing (CFT only)
1000 Bit 12 Initialization Required
2000 Bit 13 Diagnostic error
4000 Bit 14 Secondary status error
8000 Bit 15 Unused
Generic IT
10000 Bit 16 Unused
20000 Bit 17 Unused
40000 Bit 18 Bad Message
80000 Bit 19 Bad Function
100000 Bit 20 Unused
820
10000 Bit 16 Unused
224
Table 8-8. Transmitter Status Bits 10 to 23 (Continued)

20000 Bit 17 Prog EEPROM
100000 Bit 20 Poor Health
200000 Bit 21 f1 out of range
IMT
10000 Bit 16 Signal Lock
20000 Bit 17 Unused
80000 Bit 19 Unused
RTT
10000 Bit 16 Unused
20000 Bit 17 Prog EEPROM
200000 Bit 21 Bad sen1
400000 Bit 22 Bad sen2
800000 Bit 23 Stan Fail
XMTR MODE
The transmitter status, represented by bits 8 and 9 of byte 1. Possible values are: On-line (00),
Local (01), Calib (10) and Off-line (11).
FBM STATUS ERRORS

For Release 4.0, an ASCII representation of the FBM status appears as text on the second page of
the Equipment Information Display.
FBM STATUS ERRORS

The device status, represented by Byte 0 of the device status packed boolean.

1 Bit 0 Initializing
225

2 Bit 1 Write
4 Bit 2 Calibrate
8 Bit 3 Fault
10 Bit 4 Letterbug error
20 Bit 5 Database
40 Bit 6 Unused
80 Bit 7 Comm
GEO LOCATION
A 14-character alphanumeric location. A user-defined geographic location of the device assigned
during integrated control configuration. The location can be changed via the ICC or HHT.
CHANNEL NUMBER
The channel number, from 1 to 8, corresponds to the FBM channel connection used by the
selected intelligent field device. This number is not in the memory of the intelligent field device.
SERVICE DESCRIPTION
User-specified 12-character, alphanumeric tag name assigned during integrated control
configuration.
You can change this service description through the ICC or the HHT. If you use the HHT to
change this service description, you must perform an UPLOAD DATABASE from the Equipment
Change Display for this device.
HIST DIAG ERROR

The last known DIAGNOSTIC ERROR if the diagnostic error is not current.
XMTR REVISION
The firmware release level for the intelligent field device. This is not the revision letter of the
amplifier.
MANUFACTURE DATE
The date (MM-DD-YY) of manufacturing. One of the three date standards, determined during
site planning and system definition, is used: US (MM-DD-YYYY), ISO (YY-MM-DD), UR or
European (DD-MM-YY). This format is different from the format used by the HHT Display,
which is Jan 01 98.
DEVICE NAME
A six-character, alphanumeric name for the related device. If the Secure option in the FBM is on,
the DEVICE NAME must be set to the channel letterbug.
ALARMING STATE
Historian.
226
CORINT Mass Flowmeter

The CORINT module can support one Mass Flowmeter. The contents of these fields may change
when a status update occurs or when the display is recalled.
For additional information regarding the interpretation of the fields related to measurements and
calculations, see MI 019-123, CFT10 Mass Flow Transmitter Operation, Calibration and Configu-
ration Using Model HHT Hand-Held Terminal, and documents for CFT15.
NAME
The letterbug assigned to the intelligent device during site planning and system definition, such as
COR20C.
TYPE
Label for the Mass Flowmeter, which is CORIOLIS INT.
RUN MODE
On-line or Off-line. Refer to “RUN MODE” on page 216.
DEVICE STATE
are:
FAILURE ACKNOWLEDGED STATE

from Not Failed to Failed, the value in this field changes to Not Acknowledged. Refer to “FAIL
ACK STATE” on page 217.
ALARMING STATE
Historian.
227
DOWNLOAD STATE
FBM DIAGNOSTIC STATUS 1

Hexadecimal value relating to the previous FBM status error condition. Typically the value is 4,
which indicates a previous non fail-safe condition.
Table 8-9. Bit Settings for the FBM Status Conditions

1 Bit 0 Initializing
2 Bit 1 Write
4 Bit 2 Calibrate
8 Bit 3 Fault
10 Bit 4 Letterbug error
12 Bit 5 Database
14 Bit 6 Unused
16 Bit 7 Comm
LAST CABLE ACCESS

A Not Successful status indicates a PIO Bus send failure. Check the PIO Bus and switch to the
other cable if the bus is bad.

Hexadecimal value for the last FBM startup condition. The list of possible starting conditions is
related to hexadecimal bit settings. A value of 0 indicates there is no history of the last start condi-
tion; this implies an absence of data resulting from lack of communications. If this is the case, all
four diagnostic status bytes are meaningless.
Table 8-10. Hexadecimal Bit Settings

2 Bit 1 Power fail recovery
4 Bit 2 Watchdog timer failure
10 Bit 4 Expansion status
228
COMPOUND NAME
The compound name for the device.

Hexadecimal value relating to the previous software or hardware error for the selected FBM.
Table 8-11. Hexadecimal Values for FBM Software Errors
Hexadecimal Value Description

0 OK
2 I/O gate array failure
3 Clock generator failure
4 Watchdog timer (WDT) failure during cold start
5 WDT failure as part of WDT recovery diagnostics
6 Clear diagnostic register command
7 Warm start command
8 RAM failure
9 8044 failure
10 FBM configuration table invalid
11 FBM is a fatal babbler
12 Secure write failed
13 Clock overrun
14 Analog input (ai) conversion overrun
15 FBM hardware type mismatch
16 FBM software type mismatch
17 Expansion type mismatch
18 No response command error
19 Invalid factory ID
1A Unknown reset condition
1B RAM checksum test failure
1C Invalid interrupt
1D Module ID mismatch
1E PI overrun
1F ROM FN (functional) level mismatch
20 I/O bus error
21 Expansion I/O bus error
22 Bad I/O clock
23 EEPROM update failed
25 L (logic) machine execution error
37 Fault tolerant miscompare on alternate bus test
40 Test EEPROM chksum failed
229
Table 8-11. Hexadecimal Values for FBM Software Errors (Continued)

80 Test expansion port failed
NOTE
Either or both of the above hexadecimal values (40 and/or 80) may be displayed in
combination with the previously mentioned values of 6 and 37.
BLOCK NAME
The block name for the device.
FBM DIAGOSTIC STATUS 4

Hexadecimal value for the current software or hardware error for the selected FBM. Typically, the
value is 0. See the list of possible errors in “FBM DIAGNOSTIC STATUS 3” on page 229.
FBM HARDWARE TYPE

Number associated with the FBM type. See FBM SOFTWARE TYPE field.
PRIMARY COMMAND STATUS

Hexadecimal value related to the status of communication between the primary FBM and the
selected FBM. Typically the value is 0 or 1. The value of 1 indicates that a successful retry took
place and communication has been restored to normal. Either hexadecimal value indicates there is
not a problem; any other value implies a failed transmission.
FBM SOFTWARE TYPE

The value 22 indicates the type of application software being used with the designated FBM hard-
ware type.
FBM COMMAND STATUS

Hexadecimal value associated with the return status included in the header of every response from
the FBM to the primary FBM.
The following list represents the bit positions set to 1. Typically the hexadecimal value is 0, indi-
cating the command was understood and action was taken.
Hexadecimal Value Bit Position Set Description

2 1 Command understood; but unable to take action.
FBM HARDWARE REVISION LEVEL

The hardware release level of the FBM hardware type. See HARDWARE TYPE field.
230
FBM STATUS
Hexadecimal value relating to the current FBM status. Typically the value is 4 indicating the
instructions are valid (Bit 2 is set).
Table 8-12. Explanations of the Bits (Set to 1) Relating to the FBM Status

Bit 0 Set if the FBM status changes.
Bit 1 Set if the Diagnostic Register is non-zero. The FBM does not start if
this bit is set.
Bit 2 Normally set for non-fail-safe condition. Reset only if the output
mode of operation is fail-safe.
Bit 3 Not used.
Bit 4 Not used.
Bit 5 Not used.
Bit 6 Set only if the FBM is off-line. In off-line mode the software control
is ROM-based; in on-line mode the software is RAM-based.
Bit 7 Set if initialization is taking place. All channel and I/O data is
initializing.
FBM SOFTWARE REVISION LEVEL

The FBM software type release level.
LOGICAL ADDRESS
1 through 48. FBM modules are typically numbered as they appear in the display (left to right)
beginning at 1. The order of FBMs is the order in which the FBMs were “fixed” using the Inte-
grated Control Configurator. However, if an FBM is deleted and another added later, the new
FBM is given the lowest number available. For example, if FBM02 is deleted from the sequenced
group of FBM01, FBM02, and FBM03, the next FBM added results in the following sequence
group: FBM01, FBM03, and FBM02.
FBM EEPROM REVISION LEVEL

The firmware release level for the FBM.
MANUFACTURING DATE
The date (MM-DD-YY) of manufacture. One of the three date standards, determined during site
planning and system definition, is used: US (MM-DD-YYYY), ISO (YY-MM-DD), UR or Euro-
pean (DD-MM-YY). This format is different from the format used by the HHT Display, which is
Jan 01 98.
XMTR TYPE NUMBER

Type number 32 relates to the field device model code.
231
DIAGNOSTIC ERROR
An ASCII representation of the DIAGNOSTIC ERROR appears as text on the second page of the
Equipment Information Display. The system updates this field automatically every five seconds.
For code descriptions, see “DIAGNOSTIC ERROR” on page 223.
XMTR TYPE NAME

The name of the intelligent field device. The possible options are as follows: 820, 860,
IMT10/IMT20/IMT25 (MAGFLOW), RTT10/RTT20 (TEMP), CFT10 (CORIOLIS INT).
FBM/XMTR STATUS
For Release 4.0, an ASCII representation of the same field appears on the second page of the
CORINT Mass Flowmeter Equipment Information Display.
TAG NUMBER
User-specified, twelve-character, alphanumeric tag number assigned when using the
Integrated Control Configurator (ICC).
You can change this tag number through the ICC or the HHT, as follows:
 If you use the HHT to change this tag number, you must perform an UPLOAD DATA-
 If you use the ICC to change this tag number, you must perform a DOWNLOAD DATA-
XMTR STATUS NUMBER 1 (STATUS BYTE 2)

Indicates the status of the transmitter in the form of an eight-bit word. This field contains
dynamic data which is updated automatically by the system. For a description, see “XMTR STA-
TUS NO. 1 (Status Byte 2)” on page 219.
SERVICE DESCRIPTION
User-specified 12-character, alphanumeric tag name assigned during Integrated Control Configu-
rator (ICC).
You can change this service description through the ICC or the HHT. If you use the HHT to
change this service description, you must perform an UPLOAD DATABASE from the Equipment
Change Display for this device.
XMTR STATUS NUMBER 2 (STATUS BYTE 3)

Indicates the status of the transmitter in the form of an eight-bit word (See “XMTR Status Num-
ber 2, Status Byte 3 Description” on page 222). All undefined bits are considered spare bits.
DIAGNOSTIC ERROR
An ASCII representation of the DIAGNOSTIC ERROR appears as text on the second page of the
Equipment Information Display. The system updates this field automatically every five seconds.
For a description of error codes, see “DIAGNOSTIC ERROR” on page 217.
931D Gas Chromatograph

The Equipment Information fields contain information specific to the selected GC. The contents
of these fields may change when a status update occurs or when the display is recalled.
232
NAME
Letterbug, such as GC0001, assigned to the intelligent device during site planning and system
definition.
TYPE
Label for the 931D, which is GAS CHROMATOGRAPH.
RUN MODE
On-line or Off-line. This field is initialized as On-line until an internal report received by the Sys-
tem Monitor “reconfirms” the On-line state. The true status of the intelligent field device appears
on the second page of this display. When communicating with the transmitter, this data is
updated every five seconds on this display; otherwise, the system updates this field when a status
change occurs.
You can change the RUN MODE with GO ON-LINE and GO OFF-LINE options the Equipment
Change Display. If communication is lost between the intelligent device and the FBM, the last
known state appears.
For an Off-line status:
 Check hardware.
 Download, if necessary (FBM).
DEVICE STATE
are:
FAIL ACK STATE

233
ALARMING STATE
Historian.
DOWNLOAD STATE
Displays Downloading or Not Downloading (default). This value changes to Downloading when
the FBM is in the process of downloading its application image. Upon completion, the field
changes back to Not Downloading, whether the process was successful or not successful.
A Downloading status indicates that the station is rebooting; this is not a fault.
DIAG STATUS 1
Diagnostic Status 1 is a hexadecimal value related to the previous status error condition. Typically
the value is 4, indicating a previous non-fail-safe condition.
Table 8-13. Bit Settings for the FBM Status Conditions
Bit Description
Bit 0 Set if the FBM status changes.
Bit 1 Set if the Diagnostic Register is non-zero. The FBM does not start if this bit is set.
Bit 2 Normally set for non-fail-safe condition. Reset only if the output mode of opera-
tion is fail-safe.
Bit 3 Not used.
Bit 4 Not used.
Bit 5 Not used.
Bit 6 Set only if the FBM is off-line. In Off-line mode, the software control is ROM-
based; in On-line mode, the software is RAM-based.
Bit 7 Set if initialization is taking place. All channel and I/O data is initializing.
LAST CABLE ACCESS

A Not Successful status indicates a PIO Bus send failure. Check the PIO Bus and switch to the
other cable if the bus is bad.
DIAG STATUS 2
Diagnostic Status 2 is a hexadecimal value for the last FBM startup condition. The list of possible
starting conditions are related to hexadecimal bit settings. A value of 0 indicates there is no history
of the last start condition; this implies an absence of data due to lack of communications. If this is
the case, all four diagnostic status bytes are meaningless.
234

10 Bit 4 Expansion status
COMPOUND NAME
DIAG STATUS 3
Diagnostic Status 3 is a hexadecimal value relating to the previous software or hardware error for
the selected FBM. See the list of possible errors in “FBM DIAGNOSTIC STATUS 3” on
page 229.
BLOCK NAME
DIAG STATUS 4
Diagnostic Status 4 is a hexadecimal value for the current software or hardware error for the
selected device. Typically, the value is 0. See the list of possible errors in “FBM DIAGNOSTIC
STATUS 3” on page 229.
HARDWARE TYPE
Number associated with the FBM type. The type of application hardware being used with the
designated FBM software type.
PRIM CMD STAT

Hexadecimal value related to the status of communication between the primary FBM and the
selected GC. Typically the value is 0 or 1, where a value of 1 indicates that a successful retry took
place and communication has been restored to normal, and either value indicates there is not a
problem. Any value other than 0 or 1 in this field indicates a failed transmission.
SOFTWARE TYPE
Indicates the type of application software being used with the designated FBM hardware type.
FBM CMD STATUS

the GC to the primary FBM. For code descriptions, see “FBM COMMAND STATUS” on
page 230.
HARDWARE PART NO.

Hardware part number related to the device.
235
FBM STATUS
Hexadecimal value relating to the current FBM status. Typically the value is 4, indicating the
instructions are valid (Bit 2 is set). For code descriptions, see “FBM STATUS” on page 231.
HARDWARE REV
LOGICAL ADDR
1 through 48. FBMs are typically numbered as they appear in the display (left to right) beginning
at 1. The order of FBMs is the order in which the FBMs were “fixed” using the Integrated Con-
trol Configurator. However, if an FBM is deleted and another added later, the new FBM is given
the lowest number available. For example, if FBM02 is deleted from the sequenced group of
FBM01, FBM02, and FBM03, the next FBM added results in the following sequence group:
FBM01, FBM03, and FBM02.
SOFTWARE REV
MANUF DATE
Manufacturing Date is the date (MM-DD-YY) of manufacture. One of the three date standards,
determined during site planning and system definition, is used: US (MM-DD-YYYY), ISO
(YY-MM-DD), UR or European (DD-MM-YY). This format is different from the format used
by the HHT Display, which is Jan 01 98.
EEPROM REV
SERIAL NUMBER
Number assigned to each FBM hardware module.
Hydrostatic Interface Unit (HIU)

The Equipment Information fields contain information specific to the HIU selected. The con-
tents of these fields may change when a status update occurs or when the display is recalled.
Engineering units do not appear with the values for temperature and pressure on the Equipment
Information Display for the HIU. Therefore, you must be aware of the engineering units specified
in the ICC database.
Resolution of HIU Diagnostic Errors

For HIU hardware errors, refer to MI 020-068, 880PFC TankExpert™ Hydrostatic Gauge and
Inventory Maintenance.
NAME
The letterbug assigned to the HIU during site planning and system definition phase. If a primary
FBM (FBM_0 located in the Tank Processor) is selected, the letterbug of the tank processor
appears.
236
TYPE
This type, HTG INTERFACE, is determined by the primary FBM in the Tank Processor when
checking the devices on its Fieldbus.
RUN MODE
Displays On-line or Off-line. An HIU is installed initially as Off-line. You can change the RUN
MODE using the GO ON-LINE and GO OFF-LINE Equipment Change options. If station reporting
is disabled, the last known run state appears in this field.
Off-line status:
 Check hardware.
 Check the DOWNLOAD and EEPROM UPDATE fields.
DEVICE STATE
are:
 Not Ready: A transition state. The device is healthy and normal automatic startup
Failed status:
 Check Fieldbus and HIU.
FAIL ACK STATE

Displays Acknowledged (default) or Not Acknowledged. If the DEVICE STATE changes from Not
Failed to Failed, the FAIL ACK STATE field changes to Not Acknowledged.
Click ACK to acknowledge the selected faulted device; or click ACK ALL in the initial system man-
agement display to acknowledge all unacknowledged devices for which the workstation is respon-
sible.
237
ALARMING STATE
Historian.
DOWNLOAD STATE
Displays Downloading or Not Downloading (default). This value changes to Downloading when
the FBM is in the process of downloading its application image. Upon completion, the field
changes back to Not Downloading, whether the process was successful or not successful.
The Downloading status indicates that the station is rebooting; this is not a fault.
DIAG STATUS 1
Diagnostic Status 1 is a hexadecimal value related to the previous HIU status error condition.
Typically the value is 4, indicating a previous non-fail-safe condition. For a description of codes,
see “DIAG STATUS 1” on page 234.
LAST CABLE ACCESS

Reflects the health of both cables as follows: Both Cables OK, Cable A Not OK, Cable B Not
OK, or Both Cables Not OK.
If the status is Not OK indicating a PIO Bus send failure:
DIAG STATUS 2
Diagnostic Status 2 is a hexadecimal value for the last HIU startup condition. For a description of
codes, see “DIAG STATUS 2” on page 234.
COMPOUND NAME
DIAG STATUS 3
the selected HIU. See the list of possible errors in “FBM DIAGNOSTIC STATUS 3” on
page 229.
BLOCK NAME
DIAG STATUS 4
the selected HIU. See the list of possible errors in “FBM DIAGNOSTIC STATUS 3” on
page 229.
238
HARDWARE TYPE
This number, 23, relates to the HIU hardware.
PRIM CMD STAT

Primary Command Status is a hexadecimal value related to the status of communications between
the primary FBM and the selected HIU. Typically, the value is 0 or 1. A value of 1 indicates that a
successful retry took place and communication has been restored to normal, and either value indi-
cates there is not a problem. Any other value indicates a failed transmission.
Table 8-14. Explanations of the Bits (Set to 1) Relating to the Primary Command Status
Bit Description
Bit 0 Set if an exchange has been completed with a retry.
Bit 1 Set only if an exchange times out.
Bit 2 Set if response from the FBM to the primary FBM is invalid. Validity varies
with transaction type.
Bits 3 and 4 Stage at which error occurred:
 00 – Attempt by the primary FBM to reset the datalink.
 01 – First exchange of messages failed.
 10 – Second exchange of messages failed.
 11 – currently unassigned code.
Bit 5 Mode flag; set if the device is off-line. [The above definitions apply when this
bit is set to 0 (On-line)].
Bit 6 Command is invalid.
Bit 7 Miscompare error if set (MSB). Relates to fault tolerant station. This bit trig-
gers FT error recovery.
SOFTWARE TYPE
This number, 13, relates to the type of application software being used with the HIU hardware.
FBM CMD STATUS

the HIU to the primary FBM. The following list represents the bit positions set to 1. Typically the
hexadecimal value is 0 indicating the command was understood and action was taken.

2 1 Command understood; but unable to take action.
HARDWARE PART NO
Hardware part number related to the device.
239
FBM STATUS
Hexadecimal value relating to the current FBM status. Typically the value is 4, indicating the
instructions are valid (Bit 2 is set). For code descriptions, see “FBM STATUS” on page 231.
HARDWARE REV
LOGICAL ADDR
Logical Address can be 1 through 48. FBMs are typically numbered as they appear in the display
(left to right) beginning at 1. The order of FBMs is the order in which the FBMs were “fixed”
using the Integrated Control Configurator. However, if an FBM is deleted and another added
later, the new FBM is given the lowest number available. For example, if FBM02 is deleted from
the sequenced group of FBM01, FBM02, and FBM03, the next FBM added results in the follow-
ing sequence group: FBM01, FBM03, and FBM02.
SOFTWARE REV
MANUF DATE
Manufacturing Date is the date (MM-DD-YY) of manufacture. One of the three date standards,
determined during site planning and system definition, is used: US (MM-DD-YYYY),
ISO (YY-MM-DD), UR or European (DD-MM-YY). This format is different from the format
used by the HHT Display, which is Jan 01 98.
EEPROM REV
SERIAL NUMBER
Number assigned to each FBM hardware module.
HIU TEMPERATURE
Number within the range of -100 and 1000. Measured temperature inside the HIU enclosure.
P1 FREQUENCY
Number within the range of 0 and 9000. Measured frequency of pressure sensor P1.
HIU FREQUENCY
Number within the range of 0 and 9000. Measured temperature signal frequency of HIU.
P2 FREQUENCY
RTD RESISTANCE
Number within the range of -100 and 900. Measured RTD resistance of liquid product
temperature.
240
P3 FREQUENCY
RTD FREQUENCY
Number within the range of 0 and 9000. Measured temperature signal frequency of RTD.
T1 TEMPERATURE
Number within the range of -100 and 1000. Measured temperature of pressure sensor P1
housing.
CHANNEL STATUS
Indicates the status of communications between the tank processor and the HIU as represented by
an eight-bit word (see figure). A “1” in one of the defined positions below indicates the current
status. This field contains dynamic data which is automatically updated by the system.
Bit 3 = 1 represents a hardware fault.
The list of hardware faults associated with the setting of Bit 3 to 1 is as follows:
 Database Error
 EEPROM Write Failure
 Calibration Error
 Sensor Power Lost
 Pressure P1, P2, or P3 Lost
 Temperature T1, T2, or T3 Lost
 RTD Lost
 Enclosure (HIU) Temperature Lost
 Level Mismatch.
The hardware fault flag is set equal to 0 when none of the above conditions are present.
T2 TEMPERATURE
housing.
GENERAL STAT1 LOW

Indicates the status of the HTG in the form of an eight-bit word. This field is updated
periodically.
241
Test/Calibrate Mode (HIU) (1) Database Change by HIU (1)

Program Mode by I/A (1) Tank currently empty (1)
Program Mode by HIU (1) Tank filling (1)
Tank emptying (1)
0 0 0 0 0 0 0 0
(Bit Position 7 6 5 4 3 2 1 0 )
Figure 8-6. General Status 1 Low for HIU
T3 TEMPERATURE
housing.
GENERAL STAT1 HI
General Status 1 High (Status Byte 2) indicates the status of the HTG in the form of an eight-bit
word. This field is updated periodically.
PIO Fieldbus Connected (1) FIU connected

Contact I/O Opt Implemented (1) Test/Calibrate in progress (1)*
HIU initializing (1)* EEPROM update in progress (1)
Alarm is present (1) Maintenance Link installed (1)
0 0 0 0 0 0 0 0
(Bit Position 7 6 5 4 3 2 1 0)
* Same as the following bits in the Channel Status field.
General Stat Hi Channel Status

Bit 2 Bit 2
Bit 6 Bit 0
Figure 8-7. General Status 1 High for HIU
T1 CURRENT
Number within the range of 0 and 900. Measured temperature signal current of pressure sensor
P1.
GENERAL STAT2 LOW

General Status 2 Low (Status Byte 15) indicates the status of the HTG in the form of an eight-bit
242
Program Mode by I/A (1)

Test/Calibrate mode (1)
Unused No Outbound Movement Allowed
No Inbound Movement Allowed
0 0 0 0 0 0 0 0
(Bit Position 7 6 5 4 3 2 1 0)
Figure 8-8. General Status 2 Low for HIU
T2 CURRENT
P2.
GENERAL STAT2 HI
Unused value.
T3 CURRENT
P3.
ALARM STAT 1 LOW

periodically.
High level status (1) Low level status (1)

High-high level status (1) Critical zone status (1)
Level mismatch (1)a RTD uncovered (1)
Mass Deviation status Level below P2 (1)
0 0 0 0 0 0 0 0
(Bit Position 7 6 5 4 3 2 1 0)
a Status conditions which cause the hardware fault flag (Channel

Status Byte, Bit 3) to be set in the HIU
Figure 8-9. Alarm Status 1 Low HIU
243
T1 FREQUENCY
Number within the range of 0 and 9000. Measured temperature signal frequency of pressure sen-
sor P1.
ALARM STAT 1 HI
Alarm Status 1 High (Status Byte 4) indicates the status of the HTG in the form of an eight-bit
High Density Alarm (1)

HIU Link UART Error (1)b Low Density Alarm (1)
Calibration Error (1)a High Temperature Alarm (1)
Database Error (1)a Low Temperature Alarm (1)
0 0 0 0 0 0 0 0
(Bit Position 7 6 5 4 3 2 1 0)
a Status conditions which cause the hardware fault flag (Channel Status Byte, Bit3)
to be set in the HIU
b Status conditions which cause the low priority fault flag (Status Byte 14, Bit7)
T2 FREQUENCY
Number within the range of 0 and 9000. Measured temperature signal frequency of pressure
sensor P2.
ALARM STAT 2 LOW

Alarm Status 2 Low (Status Byte 5) indicates the status of the HTG in the form of an eight-bit
244
Low Pressure 1 Alarm (1)b High Pressure 2 Alarm (1)b

High Pressure 1 Alarm (1)b Low Pressure 2 Alarm (1)b
Low Water Level Alarm (1) High Pressure 3 Alarm (1)b
High Water Level Alarm (1) Low Pressure 3 Alarm (1)b
0 0 0 0 0 0 0 0
(Bit Position 7 6 5 4 3 2 1 0)
b Status conditions which cause the low priority fault flag

(Status Byte 14, Bit 7) to be set in the HIU
T3 FREQUENCY
Number within the range of 0 and 9000. Measured temperature signal frequency of pressure
sensor P3.
ALARM STAT 2 HI
Alarm Status 2 High (Status Byte 6) indicates the status of the HTG in the form of an eight-bit
word.
Inboard Product Movement Alarm (1)b Density ROC Alarm (1)b

Outboard Product Movement Alarm (1)b Low Flowrate Alarm (1)b
CIO Board Lost High Flowrate Alarm (1)b
API Bad Alarm (1)b
0 0 0 0 0 0 0 0
(Bit Position 7 6 5 4 3 2 1 0)

Figure 8-12. Alarm Status 2 High HIU
INPUT STAT LOW

periodically.
245
RTD Temp Input Lost (1)a Pressure Transducer 1 Lost (1)a

Temp Comp Input 3 Lost (1)a Pressure Transducer 2 Lost (1)a
Temp Comp Input 2 Lost (1)a Pressure Transducer 3 Lost (1)a
Temp Comp Input 1 Lost (1)a Sensor Power Lost (1)a
0 0 0 0 0 0 0 0
(Bit Position 7 6 5 4 3 2 1 0)
a Status conditions which cause the hardware fault flag (Channel Status Byte, Bit 3)
Figure 8-13. Input Status Low HIU
INPUT STAT HI
periodically.
Trans2 High Temp. Alarm (1)b Trans2 Low Temp. Alarm (1)b
Trans1 Low Temp. Alarm (1)b Trans3 High Temp. Alarm (1)b
Trans1 High Temp. Alarm (1)b Trans3 Low Temp. Alarm (1)b
Enclosure Temp Input Lost (1)a
0 0 0 0 0 0 0 0
(Bit Position 7 6 5 4 3 2 1 0)
a Status conditions which cause the hardware fault flag (Channel Status Byte, Bit 3)
Figure 8-14. Input Status High HIU
246
INTERSPEC Integrator Translator Equipment

Information
This Equipment Information Display contains information specific to the selected
INTERSPEC Integrator Translator (IIT). The IIT translates bidirectional communications
between RS-232 and the INTERSPEC Integrator 30 station.
NAME
Letterbug of the INTERSPEC Integrator 30 station containing the INTERSPEC Integrator
Translator (IIT).
TYPE
ISEC Intgr Trans (INTERSPEC Integrator Translator).
RUN MODE
On-line or Off-line. The IIT is installed as On-line after it is “fixed” and configured. For the
INTERSPEC Integrator Translator (IIT) located in the station, changing the IIT status to Off-
line causes all communication to the integrator to stop and, therefore, all attached gateway
peripherals to fail. As a result, the system sends numerous messages to the printer indicating com-
munication and peripheral equipment failures.
Changing a peripheral status to Off-line causes communications to that specific device to stop.
You can change the RUN MODE using the GO ON-LINE and GO OFF-LINE Equipment Change
options. If station reporting is disabled, the last known run state appears in this field.
Off-line status:
 Check hardware.
FAIL STATE
Failed or Not Failed (initial setting). This field updates when a status change occurs. The follow-
ing events change this field to Failed:
 Failure of the 186 chip
 Loss of Data Carrier Detect (DCD), indicating a cable break
 Software problem.
The field changes to Failed if any one of the following occurs to the IIT:
 Power is lost to the local I/A Series enclosure.
 The peripheral connection (elevator) is disengaged on the Integrator.
 If communications are not established to the IIT from the gateway station.
Failed status:
 Check INTERSPEC bus and INTERSPEC device.
247
FAIL ACK STATE

transition.
responsibility.
ALARMING STATE
Historian.
ACTIVE PIO BUS

Bus A or Bus B. This field initially is set to Bus A, or to the value saved in the checkpoint file.
This field indicates the current port used for communications to the INTERSPEC Integrator 30:
Bus A indicates Port 1; Bus B indicates Port 2.
SWITCHING MODE
Enabled (initial setting) or Not Enabled. When this field is set to Enabled, automatic switching
can occur in the event of a bus fault for the following modes: BUS A: ENABLED and BUS B:
ENABLED.
To change this field to Not Enabled, select the BUS A: DISABLED or BUS B: DISABLED action
from the Equipment Change Display.
DIAG STATUS 1
Diagnostic Status 1 indicates the electrical status of Port 1 communications.
Electrical Status Definition

00 Status appears before IIT has run diagnostics to determine the
DCD and communication statuses.
08 Status indicates the DCD test to indicate the presence of a cable
was successful; but the loopback diagnostics test was unsuccessful.
80 Status indicates the DCD test was unsuccessful; the last loopback
diagnostics test was successful.
88 Status indicates that the cable is present and the loopback diagnos-
tics was successful.
248
DIAG STATUS 2
Diagnostic Status 2 indicates the electrical status of Port 2 communications.
Electrical Status Definition

00 Status appears before IIT has run diagnostics to determine the DCD
and communication statuses.
08 Status indicates the DCD test to indicate the presence of a cable was
successful; but the loopback diagnostics test was unsuccessful.
80 Status indicates the DCD test was unsuccessful; the last loopback diag-
nostics test was successful.
88 Status indicates that the cable is present and the loopback diagnostics
test was successful.
SOFTWARE REV
This field is not applicable to the INTERSPEC Integrator Translator.
INTERSPEC Integrator 30 Peripherals Equipment

Information
The Equipment Information fields contain information specific to the INTERSPEC Integrator
30 peripheral selected. There are two groups of IS30 peripherals (excluding the IIT): AIM and
CCM and UIO and UFM.
AIM (Analog Input Module) and CCM (Controlled

Communication Module)
NAME
Logical letterbug name assigned to the AIM or CCM peripheral.
TYPE
Type of peripheral, either Analog Input Mod (AIM) or Control Comm Mod (CCM).
RUN MODE
Off-line status:
 Check hardware.
249
FAIL STATE
Failed or Not Failed (initial setting). The system updates this field when a status change occurs.
The following occurrences change this field to Failed:
 The AIM or CCM peripheral does not respond to the “heartbeat” requests from the
INTERSPEC Integrator 30.
If the state is Failed:
FAIL ACK STATE

transition.
responsibility.
ALARMING STATE
Historian.
LAST CABLE ACCESS

OK, or Both Cables Not OK. This field applies to the selected device and indicates whether trans-
missions were successfully sent the last time either Bus A or B was used.
A Not OK status indicates a PIO Bus send failure. Check the PIO Bus. Switch to the other cable
if the bus is bad.
A/D CONVERTER
Indicates hardware health as either Failed (A/D failure) or OK.
BATTERY BACKUP
Indicates hardware health as either Failed (battery backup failure) or OK.
250
DP10 POWER
Indicates hardware health as either Failed (loss of DP10 power) or OK.
SYSTEM FLUNK
Indicates hardware health as either Flunked or Unflunked.
SYSTEM POWER
Indicates hardware health as either Failed (loss of system power) or OK.
PORT1 FLUNK
PORT2 FLUNK
SPEC200 POWER
Indicates hardware health as either Failed or OK.
PARITY COUNTER
Number of parity errors since the last reset.
To reset the parity counter, reboot the station or turn the peripheral device off/on.
OVERRUN COUNTER
Number of receive communication errors in the FIFO buffer of the station.
FRAMING COUNTER
Number of misaligned frames that occurred.
CRC/BCH COUNTER
The number of BCH (Bose-Chaudhuri-Hocquenhem) errors detected.
HARDWARE TYPE
Peripheral Type Hardware Type

AIM 46
CCM 47
SOFTWARE TYPE
Peripheral Type Software Type

AIM 29
CCM 30
251
LOGICAL ADDRESS
You configure the logical address of the gateway peripheral (1 through 16) using the Integrated
Control Configurator (ICC).
The logical address order of the peripherals is the order in which the peripherals were “fixed” dur-
ing configuration.

Represents a communication status code.

4 Device failure. (Refer to the FBM STATUS and FBM CMD STATUS fields.)
FBM COMMAND STATUS

Hexadecimal value that further defines the communication error shown in the FBM STATUS field.
Code Description
00 No error has occurred
01 DCD (Data Carrier Detect) was lost during the message
02 Bytes arriving faster than being processed on input
04 Parity error on input
08 Byte with missing stop bits on input
80 Receive/send timeout before end of message (input/output)
FBM STATUS
Code Description
F4 Communication error from 386 chip to 186 chip (refer to FBM CMD
STATUS field)
F5 Not used
F6 Fault-tolerant error
F7 A/D conversion failure
F8 Buffer ID not found
F9 Communication error from 186 chip to device (refer to FBM CMD
STATUS field)
FA Communication framing error (refer to FBM CMD STATUS field)
FB Communication overrun error (refer to FBM CMD STATUS field)
FC Communication parity error (refer to FBM CMD STATUS field)
252
Code Description
FD Incoming message does not have appropriate BCH code
FE Negative acknowledge from device
FF Station unable to communicate with device; timeout (refer to FBM CMD
STATUS field for type of timeout)
COMPOUND NAME and BLOCK NAME

The compound name and block name for the device.
UIO (Universal Input/Output) and UFM (Universal Field

Module)
NAME
Logical letterbug name assigned to the UIO or UFM peripheral.
TYPE
Type of peripheral, either Universal I/O Mod (UIO) or Universal Field MUX (UFM).
RUN MODE
this peripheral appears. The system updates this field when a status change occurs.
Off-line status:
 Check hardware.
FAIL STATE
Failed or Not Failed (initial setting). The system updates this field when a status change occurs.
The following events change this field to Failed:
 The UIO or UFM peripheral does not respond to the “heartbeat” requests from the
gateway.
FAIL ACK STATE

transition.
253
responsibility.
ALARMING STATE
Historian.
LAST CABLE ACCESS

A Not OK status indicates a PIO Bus send failure. Check the PIO Bus. Switch to the other cable
if the bus is bad.
CONTROL PANEL SET

Indicates hardware health as either Local or On-line.
If the status is Not OK, the control panel is in the Off-line mode.
SYSTEM FLUNK
SPEC 200 POWER

Indicates hardware health as either Failed (loss of SPEC 200 power) or OK.
ATTENTION BIT STATE

Indicates if the attention bit is set (Set) or needs to be reset (Reset).
The attention bit is set under the following conditions:
 The device is set to local or manual mode,
 The device is flunked, or
 Power to the device is momentarily lost.
Not Set status indicates one or more I/O components may have experienced memory content
changes as a result of:
 Momentary power failure
 Flunk condition
254
 The UIO module being momentarily switched to Off-line mode at the service panel.
PARITY COUNTER
Number of parity errors since the last reset. To reset the parity counter, reboot the station or turn
the peripheral device off/on.
OVERRUN COUNTER
The number of receive communication errors in the FIFO buffer of the station. A Not Set status
indicates a loss of characters.
FRAMING COUNTER
Number of misaligned frames that occurred.
CRC/BCH COUNTER
The number of BCH (Bose-Chaudhuri-Hocquenhem) errors detected.
HARDWARE TYPE
Peripheral Type Hardware Type

UIO 48
UFM 49
SOFTWARE TYPE
Peripheral Type Software Type

UIO 31
UFM 32
LOGICAL ADDRESS
You configure the logical address of the gateway peripheral (1 through 16) using the Integrated
Control Configurator (ICC).
The logical address order of the peripherals is the order in which the peripherals were “fixed” dur-
ing configuration.

Represents a communication status code.

255

4 Device failure. (Refer to the FBM STATUS and FBM CMD STATUS fields.)
FBM COMMAND STATUS

Hexadecimal value that further defines the communication error shown in the FBM STATUS field.
Code Description
00 No error has occurred
01 DCD (Data Carrier Detect) was lost during the message
02 Bytes arriving faster than being processed on input
04 Parity error on input
08 Byte with missing stop bits on input
80 Receive/send timeout before end of message (input/output)
FBM STATUS
Code Description
F4 Communication error from 386 chip to 186 chip (refer to FBM CMD STATUS field)
F5 Not used
F6 Fault-tolerant error
F7 A/D conversion failure
F8 Buffer ID not found
F9 Communication error from 186 chip to device (refer to FBM CMD STATUS field)
FA Communication framing error (refer to FBM CMD STATUS field)
FB Communication overrun error (refer to FBM CMD STATUS field)
FC Communication parity error (refer to FBM CMD STATUS field)
FD Incoming message does not have appropriate BCH code
FE Negative acknowledge from device
FF Station unable to communicate with device; timeout (refer to FBM CMD STATUS field
for type of timeout)

I/O Gate Peripherals Equipment Information

The Equipment Information fields contain information specific to the selected I/O Gate devices,
including character-oriented Port ECB (ECB98), message-oriented Port ECB (ECB99), and
Device ECB (ECB100).
256
NAME
The letterbug assigned during system definition for hardware configuration: PORT1 (ECB98),
PORT2 (ECB99) or DEV_M1 (ECB100).
TYPE
Type of ECB defined when the letterbug is assigned during site planning and system definition:
PORT-CHARACTER (ECB98), PORT-MESSAGE (ECB99) or PORT-DEVICE (ECB100).
RUN MODE
OFF-LINE options in the Equipment Change Display. Changing the ECB status to Off-line
causes all communication to the respective device to stop and all attached devices to fail. As a
result, a number of messages appear at the printer indicating communication failures and device
equipment failures.
If reporting is disabled, the last known run state appears in this field. The system updates this field
when a status change occurs.
DEVICE STATE
are:
 Not Failed: The device is connected to the control strategy, though measurements are
 Failed: Fatal hardware or other fatal fault reported by the device.
FAIL ACK STATE

Displays Acknowledged (default) or Not Acknowledged. If the DEVICE STATE changes from Not
Failed to Failed, the FAIL ACK STATE field changes to Not Acknowledged.
Click ACK to acknowledge the selected faulted device; or click ACK ALL in the initial system man-
agement display to acknowledge all unacknowledged devices for which the workstation is respon-
sible.
ALARMING STATE
Historian.
HARDWARE TYPE
Number associated with the peripheral hardware: 160 (ECB98), 161 (ECB99) or 162 (ECB100).
This value is configured with the ICC for the specific ECB.
257
SOFTWARE TYPE
Number identifying the software used in the DIW devices: 98 (ECB98), 99 (ECB99) or 100
(ECB100). This value is configured with the ICC for the ECB.
FAIL ALGO
Failure Algorithm indicates the failure algorithm used to cause the port to fail internally even if
the port is connected and on-line. When the port fails, the system generates a trigger ID. Triggers
communicate event information between ECBs and can be used to initiate status changes in the
destination ECBs. This failure algorithm uses the generated trigger IDs to determine the ratio of
errored communications to good (complete) communications.
 1 = The port fails when the WatchDog timer reaches zero.
 2 = The port fails based on a predefined Trigger Event.
 Other = 0x10, 0x100, or 0x1000.
NOT FAIL ALGO

Not Failed Algorithm identifies the algorithm that causes the port to transition from Failed to
Not Failed state. When the ECB returns to the Not Failed state from Failed, the system generates
a predefined trigger ID.
Refer to the documentation for the specific port for complete information.
 0 = No Information available.
 1 = The port goes back on-line based on the WatchDog timer value (Time delay).
 2 = The port goes back on-line based on the Trigger ID generated (Trigger Event).
SERVER TYPE
Identifies the type of server (IOGATE) I/A Series uses to communicate with this ECB device.
Refer to the IOGATE documentation for your specific ECB device for complete information.
The values are as follows:
 1 = DDE (Dynamic Data Exchange protocol)
 2 = OLE (Object Linking and Embedding).
SERVER NAME
Identifies the name of the server application (driver) used for communications with the related
gate. (Each gate type can have more than one server.) Refer to the documentation which accom-
panies each IOGATE for valid options.
WD TIMER
Watchdog Timer indicates the value of the port ECB watchdog timer (in seconds). When this
value is zero, the watchdog timer has expired and the device goes off-line. If no communications
activity occurs for the specified time, the port goes to Off-line state.
258
ONL TIMER
On-line Timer indicates the number of seconds before the off-line port with the ECB device
attempts to transition to on-line.
PARENT NAME
Identifies the parent port as Port 1 for ECB99 or ECB100. Not applicable (N/A) for ECB98.
ALT NAME
Alternate Parent Name identifies the alternate parent port for this ECB99 or ECB100 device.
This alternate port takes over if the designated parent ECB port fails or has a change of state.
Not applicable (N/A) for ECB98.
Micro-I/A AB-IO Peripherals Equipment Information

Name
Type
Identifies the type of AB-IO device as AB-IO MOD 4 AO.
RUN MODE
on-line)
DEVICE STATE
lowing occur:
259
 Any station hardware failure or communication failure that results in the station not
able to send its internal reports for two or more minutes
Failed.

ALARMING STATE
Indicates whether alarming is Enabled or Inhibited for the device. When alarming is Inhibited,
while equipment is failed or off-line. System Alarm messages are not logged to the system printer,
nor the Historian.
COMPOUND NAME AND BLOCK NAME

Displays the compound name and block name for the device.
HARDWARE TYPE
Number, 123, associated with the peripheral hardware type.
FAULT BYTE
All AB-IO analog devices report per channel faults. Underrange is reported for analog input for a
signal type (SIG) of 2 only (4 to 20 mA). Wire broken or load resistance high is reported for ana-
log outputs for a signal type (SIG) of 1 or 2 only (0 to 20 or 4 to 20 mA).
For the 1794-IB8S sensor module, a fault present on a smart sensors connected to a point sets the
matching bit in the FAULT BYTE.
Each bit represents one channel. Bit 0 (right-most bit on display) is Channel 1 (0 on the
module).
MODULE NUMBER
Displays a value from 1 to 8 defining the position of the module with regard to the RIO adapter.
Module 1 is the closest to the AB-RIO adapter.
Micro-I/A AB-PIO Peripherals Equipment Information

NAME
260
TYPE
Identifies the type of AB-PIO device as AB PRIMARY IO.
RUN MODE
tem Monitor after booting up. For more information, see “RUN MODE” on page 259.
DEVICE STATE
Failed or Not Failed. This field is initially Not Failed. For more information, see “DEVICE
STATE” on page 259.

Acknowledged or Not Acknowledged. This field is initially set to Acknowledged. For more infor-
mation, see “FAILURE ACKNOWLEDGED STATE” on page 260.
ALARMING STATE
Indicates whether alarming is Enabled or Inhibited for the device. For more information, see
“ALARMING STATE” on page 260.
FAILED DEVICE ATTACHED

Displays Yes if one or more peripherals attached to the station report as failed; otherwise, displays
No.
peripherals.

HARDWARE TYPE
PORT
Displays 2, 3 or 4. This field displays the PCMCIA card’s port number, which corresponds with
the Micro-I/A Station slot number in which the card is plugged.
NUMBER OF ADAPTERS
Displays the number (1 through 32) representing the number of actively scanned RIO adapters
on the A-B network.
FAULTED ADAPTERS
Displays the number (0 through 32) indicating the number of RIO adapters that are in the fault
state.
MODE
Indicates the mode (program or run) the AB-PIO Bus device is currently in. Mode 1 is program
and 2 is run.
261
DUPLICATE SCANNER
This field displays a 0 or a 1. The AB-RIO adapters do not work properly when there is more
than one AB-PIO Bus device connected to a single network. A value of 1 indicates duplicate
active scanners; 0 indicates that only one AB-PIO Interface card is connected.
BAUD RATE
This field indicates the baud rate at which the bus is operating. The value in this field describes
the configuration of the ECB, and must match the rate configured by the Adapter DIP switches
(jumper-configured rate) at the AB-RIO modules.
Value Baud Rate (Kbd)

0 57.6
1 115.2
2 230.4
Micro-I/A AB-RIO Peripherals Equipment Information

NAME
TYPE
Identifies the type of AB-RIO device as AB-RIO ADAPTER.
RUN MODE
DEVICE STATE

ALARMING STATE

No.
If the status is Yes, one or more of the attached peripherals have failed. Verify status of peripherals.
262

HARDWARE TYPE
RESTART LOCKOUT
This field is not currently supported.
FAULT GROUP ID
An RIO adapter can be configured to be part of a fault group. The Fault Group ID identifies the
number of the fault group (1 through 15) to which the RIO is configured.
ADAPTER ON-LINE
Indicates the current state of the AB-RIO adapter, where Off-line is 0 and On-line is 1.
GROUP FAULT
Normally, this field displays a 0. If one of the adapters in the fault groups has a fault, this value is
a 1.
RACK NUMBER
Displays the value from 1 to 32 representing the rack number configured to the ECB as set by the
adapter DIP switches. This value appears as a one-based decimal, as opposed to the DIP switches
on the module which are set with zero-based octal values.
Micro-I/A GE-IO Peripherals Equipment Information

NAME
TYPE
Identifies the type of GE-IO device as GE-IO Mod 8 AI.
RUN MODE
DEVICE STATE

263
ALARMING STATE

HARDWARE TYPE
ERROR CODE
This field is normally 0. If an error is detected in the GE-IO module, this field is set to a non-zero
value.
MODULE NUMBER
1 through 8, inclusive. This value indicates the position of the GE-I/O module with regard to the
GE FANUC™ bus device. Module 1 is closest to the field interface cable.
Micro-I/A GE-PIO Peripherals Equipment Information

NAME
TYPE
Identifies the type of GE-PIO device as GE PRIMARY IO.
RUN MODE
DEVICE STATE

ALARMING STATE

No.
264
peripherals.

HARDWARE TYPE
PORT
Displays 2, 3 or 4. This field displays the PCMCIA card’s port number, which corresponds with
the Micro-I/A station slot number in which the card is plugged.
HARDWARE REVISION
MANUFACTURE DATE
EROM REVISION
SERIAL NUMBER
SOFTWARE REVISION
ORIENTATION
Identifies the GE FANUC bus device orientation using the following values:
0 A left-to-right physical orientation indicates that the field interface cable

attaches to the field terminal base such that with the I/O module installed the
cable enters on the side nearest the label text “SLOT.”
1 A right-to-left physical orientation indicates that the field interface cable
attaches to the field terminal base such that with the I/O module installed the
cable enters on the side nearest the label text “PWR.”
ERROR CODE
This field is normally 0. If an error is detected in the GE FANUC bus device, this field is set to a
non-zero value.
NOTE
Refer to Micro-I/A station maintenance documentation for error code identifica-
tion, description and corrective action.
265
Micro-I/A Station Equipment Information

NAME
Station letterbug assigned during system definition of hardware.
TYPE
Type of station defined when the letterbug is assigned during site planning and system definition.
RUN MODE
DEVICE STATE

ALARMING STATE
FT STATE
Displays No Information for non-fault-tolerant stations, and Operational or Non-Operational for
fault-tolerant stations. If one of the two modules in the fault-tolerant pair is off-line or failed, dis-
plays Non-Operational.

No.
If the status is Yes, one or more of the attached peripherals have failed. Verify status of peripherals.
FAILED DEVICE ACKNOWLEDGED

Displays Acknowledged (default) or Not Acknowledged. If any of the attached devices become
unacknowledged, displays Not Acknowledged.
If the status is Not Acknowledged, one or more of the attached peripherals has failed. Verify status
of peripherals. To clear the failure and the asterisk (*) on the station, click ACK or ACK ALL on the
266
DIAGNOSTIC STATE
Displays Diag Active or Not Active (default). When you select off-line diagnostics, the status
changes to Diag Active until you click either RESTART or FAIL.
Diagnostic status:
 Module in OLDD. (OLDD tests are available to diagnose failures.)
 Perform RESTART in Off-Line Diagnostic Display.
EE UPDATE STATE
Displays EE Updating or Not Updating (default). When you select EEPROM UPDATE from the
Equipment Change Display, this value changes to EE Updating until the action completes.
For fault-tolerant station displays, the primary and shadow information is valid if the FT State is
DOWNLOAD STATE
Displays Downloading or Not Downloading (default). When the station reboots because of an
operator-initiated request, the status changes to Downloading until the reboot is complete.
SM REPORT STATE
Indicates the type of internal reporting taking place from the Station Manager to the System
Monitor as Report All, No Counters or No Reporting.
Report All is the default unless changed in the Equipment Change Display. The SM REPORT
states are available from Equipment Change Display options, as follows:
 ENABLE ALL REPORTS
 DISABLE ALL REPORTS
SOFTWARE VERSION
The release level of station software currently running in this station. This field is not currently
used.
PRIMARY MODE
 Single Primary: Only one of the fault-tolerant modules is running. Check the shadow
hardware. Check the interlink.
 Married Primary: Both modules running are married. This one is primary.
267
For fault-tolerant station displays, the primary information is valid if the FT State is either Oper-
ational or Non-Operational.
If the station is not configured to be fault-tolerant, refer to the FAIL STATE field on this display
for the latest status.
SHADOW MODE
 Married Shadow: Both modules running are married. This one is shadow.
SHADOW ROM ADDRESS

this field specifies the MAC address of the shadow station assigned during manufacturing.
PRIMARY HARD PART and SHADOW HARD PART

PRIMARY HARD REVISION LEVEL and SHADOW HARD REVISION LEVEL
PRIMARY HARD DATE and SHADOW HARD DATE
Dates and revision levels supplied by manufacturing.
When a fault-tolerant module replacement occurs, you must recall the display to access informa-
PRIMARY EEPROM REVISION LEVEL

SHADOW EEPROM REVISION LEVEL

The EEPROM revision level is updated each time a new revision of EEPROM is performed
through the Equipment Change Display on the Shadow module of a fault-tolerant pair.
268
STATION ADDRESS
this field specifies a unique MAC address for a fault-tolerant station pair when married.
This field is unique if the station can be configured to be fault-tolerant. This field specifies the
same address as the PRIM ROM ADDRESS if the station cannot be configured to be a member of a
fault-tolerant pair. (LI FT stations and ATSs have their own unique numbers.)
MASTER TIMEKEEPER REPORT STATE

Displays Enabled, Not Enabled or Not Configured. The I/A Series network can have only one
Master Timekeeper enabled at a time. Master Timekeepers are found only in application worksta-
tions (AWs). Other stations cannot have a configured Master Timekeeper.
Possible Status Conditions:
 Enabled: This station can support a Master Timekeeper, and the master is currently
active.
 Not Enabled: This station can support a Master Timekeeper, and the master is cur-
rently inactive.
 Not Configured: This station cannot support a Master Timekeeper.
Modicon Devices (ECB60/61/62) Equipment

Information
NAME
TYPE
Identifies the type of Modbus device as follows: MODBUS PIOM (ECB60); MODBUS PLC
(ECB61); MODBUS SCAN (ECB62).
RUN MODE
DEVICE STATE

ALARMING STATE
269
HARDWARE TYPE
100 (ECB60); 101 (ECB61); 102 (ECB62).
SOFTWARE TYPE
60 (ECB60); 66 (ECB61) or 62 (ECB62).


Represents a communication status code. This field does not apply to the ECB60 device.

0 Does not apply
4 Device failure
PLC ERROR STATUS

PLC EXT STATUS

0, This field does not apply to the ECB60 device.
LAST CABLE ACCESS

LOGICAL ADDRESS
The logical address, 1 through 16, of the gateway peripheral; this value is configured using the
ICC. The logical address order of the peripherals is the order in which the peripherals were “fixed”
during configuration. This field does not apply to the ECB60 device.
ALTERNATE PORT
No Bkup Possible or None. Identifies whether backups are permitted to the alternate parent ECB
port for this device. This alternate port takes over if the designated parent ECB port fails or has a
change of state. This field does not apply to the ECB60 device.
270
Port ECB Devices Equipment Information

This section describes the fields for the Port ECB devices. The Port ECB devices act as generic
devices and are used as placeholders for your specific third-party devices.
Port ECB devices include:
 Character-oriented Port ECB devices (IC-PORT)
 Ethernet or message-oriented Port ECB devices (IM-PORT).
NOTE
The information for both character-oriented and message-oriented devices is the
same except where noted below. Refer to the documentation for your port or gate
for complete information.
NAME
Name of port.
TYPE
Type is either:
 Port-Character (character-oriented Port ECB)
 Port_Message (message-oriented Port ECB).
RUN MODE
The ECB is installed initially as Off-line.
Display to change the operation state of the station from On-line to Off-line.
Off-line status occurs as an operator action, or if this is a newly installed ECB that has never been
put on-line.
DEVICE STATE
 Port is configured to receive a specific GO OFF-LINE trigger and a trigger event
occurs.
 I/O gate terminates.
 Server terminates.
 Foreign device indicates failure to I/O gate.
Making the I/O gate and/or server operational causes the system to change the status to Not
Failed as long as the port is on-line.
When foreign device indicates on-line to I/O gate, the status changes to Not Failed.

The compound name and block name for this ECB device.
271
HARDWARE TYPE
The ECB number associated with the port communications software.
SOFTWARE TYPE
This number identifies the software used in the port communications.
FAILURE ALGORITHM
Indicates the failure algorithm used to cause the port to fail internally even if the port is connected
and on-line. When the port fails, the system generates a trigger ID if the TRG_OF is configured.
Triggers communicate event information between ECBs and can be used to initiate status changes
in the destination ECBs. This failure algorithm can be configured to determine the ratio of
errored communications to good (complete) communications.
 1 = The port fails when the WatchDog timer reaches zero
 2 = The port fails based on a predefined Trigger Event.
Other = 0x10, 0x100, or 0x1000 indicates the ratio of errors of bad messages to good messages
over the last 10,100, or 1000 messages, respectively. This value indicates the message bit error
ratio that, when reached, causes the port to fail.
NOT FAILED ALGORITHM

Identifies the algorithm that causes the port to go to the Not Failed state. When the ECB returns
to the Not Failed state from Failed, the system generates a predefined trigger ID if the TRG_OF is
configured with the ID.
Refer to the documentation for the specific port for complete information.
 1 = The port goes back on-line based on the on-line timer value
 2 = The port goes back on-line based on the Trigger ID generated.
SERVER TYPE
Identifies the type of server (gate) the I/A Series system uses to communicate with the Port ECB.
Refer to the documentation for your specific ECB device for complete information.
Currently, the acceptable values are as follows:
 DDE = Dynamic Data Exchange protocol
 OPC = Object Linking and Embedding for Process Control.
The acceptable values are strings and indicate what you configured.
SERVER NAME
Identifies the name of the server as configured by the server application.
WATCHDOG TIMER
Indicates the value (in seconds) of the watchdog timer.
ON-LINE TIMER
Indicates the value (in seconds) of the on-line timer.
272
Redundant FBM46 Equipment Information

MAIN MODULE
Letterbug ID of the main FBM46.
MAIN STATE
Redundancy state of the main FBM46. The possible states are Main Active, Main Track, Main
Off-line or Main Failed.
BACKUP MODULE
Letterbug ID of the backup FBM46.
BACKUP STATE
Redundancy state of the backup FBM46. The possible states are Backup Active, Backup Track,
Backup Off-line or Backup Failed.
TYPE
FBM46R.
ACTIVE CABLE ACCESS

Fieldbus cable accessibility to the active FBM46R.

Acknowledged (default) or Not Acknowledged. Indicates if the failure is acknowledged.
Not acknowledged status: Check printed/historical log for type of failure. To clear, click ACK or
ACK ALL on the configured workstation processor.
TRACKING CABLE ACCESS

Fieldbus cable accessibility of Tracking FBM46.
WARNING CONDITION
Displays Yes if any of the special FBM46R bits are set.

Displays Yes if a configured device has a failure.

ALARMING STATE
Historian.
273

Displays Yes if any of the associated I/O points fail.
HARDWARE TYPE
FBM46R hardware type: 98.
MAIN COMMAND STATUS

Primary status code describing the communication with the active FBM46.
SOFTWARE TYPE
FBM46R software type: 49.
COMMAND STATUS
Status code describing the iom.status byte of the active FBM46.
MAIN LOGICAL ADDRESS

Logical address (1 to 240) used by the control processor (CP) during normal operation.
MAIN HARDWARE PART NUMBER

Part number of the main FBM46.
MAIN HARDWARE REVISION LEVEL

Hardware revision level of the main FBM46.
MAIN EEPROM REVISION LEVEL

Revision level of EEPROM installed on the main FBM46.
MAIN SERIAL NUMBER

Serial number of the main FBM46.
MAIN MANUFACTURING DATE

Manufacturing date of the main FBM46.
BACKUP LOGICAL ADDRESS

Logical address (1 through 240) used by the control processor (CP) during normal operation.
BACKUP HARDWARE PART NUMBER

Part number of the backup FBM46.
BACKUP HARDWARE REVISION LEVEL

Hardware revision level of the backup FBM46.
BACKUP EEPROM REVISION LEVEL

Revision level of EEPROM installed on the backup FBM46.
BACKUP SERIAL NUMBER

Serial number of the backup FBM46.
274
BACKUP MANUFACTURING DATE

Manufacturing date of the backup FBM46.
MAIN (or BACKUP) DIAGNOSTIC STATUS 1
Table 8-15. Fan/Power Monitor States
State Designation Description

0 OK
1 No access to power monitor card
4 External Binary Signal occurred
5 Communication to second PM20 failed
6 Power supply at first slot failed
7 Power supply at second slot failed
8 Power supply at third slot failed
9 Power supply at fourth slot failed
A Power supply at fifth slot failed
B Power supply at sixth slot failed
12 Power rail voltage out of tolerance
13 Current balance between power supplies disturbed
MAIN (OR BACKUP) DIAGNOSTIC STATUS 2

Hexadecimal value for the last FBM46 start-up condition. The list of possible starting conditions
is related to hexadecimal bit settings. A value of 0 indicates that there is no history of the last start
condition. This implies an absence of data due to lack of communications. If this is the case, all
four diagnostic status bytes are meaningless.

A Bit 4 Expansion status
Table 8-16. FBM46 Diagnostic Status 3 Errors

0 No error
1 EA1 does not become master
2 Error at Read Strobe
3 Error at Write Strobe
275
Table 8-16. FBM46 Diagnostic Status 3 Errors (Continued)

4 UART-Error at Reading
5 UART-Error at Writing
6 STAUS-Sequencer failed
7 Error at Watchdog test
8 Error at Buffer management
9 Buffer management is full
A No data from other FBM46
B Error from VRTX
C EA1 Interrupt Error

Hexadecimal value for the current software or hardware error for the selected FBM46. Typically,
the value is 0.
Hardware Errors:
0 OK
Software Errors:
15 FBM46 hardware type mismatch
16 FBM46 software type mismatch
18 No response command error
19 Invalid factory ID
1A Unknown reset condition
1B RAM checksum test failure
1C Invalid interrupt
1D Module ID mismatch
20 I/O bus error
23 EEPROM update failed
40 Test EEPROM checksum failed
80 Test expansion port failed
Either or both of the hexadecimal values 40 and 80 can display in combination with the related
description values.
276
760 Micro Controller Devices Equipment Information

NAME
TYPE
Identifies the type of Micro controller device as follows: SSM PORT (ECB60); SSM DEV
(ECB69); SSM SCN (ECB70, ECB71, ECB72).
RUN MODE
DEVICE STATE

ALARMING STATE
HARDWARE TYPE
Number configured with the ICC for the associated peripheral hardware, as follows:
109 (ECB60); 110 (ECB69); 111 (ECB70, ECB71, ECB72).
SOFTWARE TYPE
Number identifying the software used in the Micro controller devices, as follows: 60 (ECB60); 69
(ECB69); 70 (ECB70, ECB71, ECB72).
COMPOUND NAME
The name of the compound that contains the ECB.
BLOCK NAME
The text string configured (with ICC) for the ECB’s NAME parameter. This name is used by all
I/O blocks (in their IOM_ID parameter) to reference the device.

Represents a communication status code. This field does not apply to the ECB60 device.

0 Does not apply
277

4 Device failure
PLC ERROR STATUS

PLC EXT STATUS

LAST CABLE ACCESS

LOGICAL ADDRESS
The logical address, 1 through 16, of the peripheral. This value is configured using the ICC. The
logical address order of the peripherals is the order in which the peripherals were “fixed” during
configuration. This field does not apply to the ECB60 device.
ALTERNATE PORT
No Backup Possible or None. Identifies whether backups are permitted to the alternate parent
ECB port for this device. This alternate port takes over if the designated parent ECB port fails or
has a change of state. This field does not apply to the ECB60 device.
Workstation Processor Peripherals Equipment

Information
This Equipment Information Display contains information specific to the selected workstation
processor peripheral.
NOTE
Annunciator keyboards are represented as device boxes in this display. The keyboard
and mouse are not represented.
STATION NAME
Logical name assigned to the peripheral during configuration.
278
TYPE
This type, Annunciator Panel, Keyboard, Mouse/Touchscreen, GCIO Primary or Graphics
Engine, is supplied from the configuration files.
The AW50/51 can have either a GCIO device or a printer. This display identifies one of the fol-
lowing in the GCIO device box graphic.
ID Description
PRI Primary GCIO interface with no touchscreen.
SEC Secondary GCIO interface with no touchscreen.
P/TS # Primary GCIO interface with touchscreen. (# is the letterbug of the touch-
screen configured.)
S/TS # Secondary GCIO interface with touchscreen. (# is the letterbug of the
touchscreen configured.)
RUN MODE
 Check hardware.
FAIL STATE
Not Failed. This field is the only state recorded since the WP peripheral cannot provide its status
to the station.
 Check Printer/Terminal/CPU hardware.
ALARMING STATE
Historian.
FT STATE
Displays No Information for non-fault-tolerant stations, and Operational or Non-Operational for
fault-tolerant stations. If one of the two modules in the fault-tolerant pair is off-line or failed, dis-
plays Non-Operational.
279

Displays Yes if one or more peripherals attached to this station are failed.

Acknowledged (default) or Not Acknowledged. If any of the attached devices become unacknowl-
edged, displays Not Acknowledged.
DIAGNOSTIC STATE
Displays Diag Active or Not Active (default). When off-line diagnostics are selected, the status
changes to Diag Active until you click either RESTART or FAIL.
EE UPDATE STATE
Displays EE Updating or EE Not Updating (default). When you select EEPROM UPDATE option
from the Equipment Change Display, the status changes to EE Updating until the action is
completed.
If the state is EE Not Updating after selecting the EEPROM UPDATE option, the module is not per-
forming firmware update. To resolve:
DOWNLOAD STATE
SM REPORT STATE
Indicates the type of internal reporting taking place from the Station Manager to the System
Monitor as either Report All, No Counters or No Reporting.
Report All is the default unless changed in the Equipment Change Display. The SM REPORT
states are available from Equipment Change Display options, as follows:
 ENABLE ALL REPORTS
 DISABLE ALL REPORTS.
SOFTWARE VERSION
Indicates the release level of station software currently running in the station. Not currently used.
280
PRIMARY MODE and SHADOW MODE

Displays Single Primary, Married Primary, EE Updating, Downloading, Failed or Diags Active if
the station is fault-tolerant. Displays No Information if the station is not fault-tolerant.
If the station is not configured to be fault-tolerant, refer to the FAIL STATE field for the latest
status.
SHADOW MODE
Displays Married Shadow, EE Updating, Downloading, Failed, Off-line or Diags Active if the sta-
tion is fault-tolerant; displays No Information if the station is not fault-tolerant.
PRIMARY ROM ADDRESS

this field specifies the MAC address of the Primary Station assigned during manufacturing.
281
282
Appendix B. System Messages
This appendix contains system messages that can appear in SMDH displays.
NOTE
Refer to V8.x System Error Messages (B0700AF) for a complete list of the system
error messages.
Table B-1. System Management Event Messages for SMDH
Message Description/Cause Corrective Action(s)

<Peripheral Equipment Indicates the success or failure of the Retry action if failed.
Change Action> following peripheral equipment
Succeeded or
change actions: Upload Database,
Failed:<Letterbug>
Download Database, Download,
EEPROM Update.
Action not allowed You attempted to perform an illegal Verify that the action can, and should,
action. This could be due to net- be requested for this station type.
work operation, station status or an Check the system health, then try the
action not available to that action again. Check the station health,
workstation. network health, and so forth, then try
again.
Cannot unlock station Unable to unlock station records. Determine if another utility such as a
letterbug available This prohibits station actions such configuration or another SMDH is
as reboots. running and has locked the station.
Checkpoint succeeded Indicates the success or failure of the If checkpoint failed, retry checkpoint
or failed: <Station checkpoint equipment change action. If the problem continues, con-
Letterbug>
action for a specific type of station tact the Global CSC. Check the
(control processor, selected gate- printer for appropriate error code.
ways, display station processor). Check the applicable subsystem.
Deleted equipment The device (station or peripheral) Return to a previous screen to force
requires returning to you are viewing has been deleted, the SMDH to rerequest the device
previous screen
and the SMDH information for information; this ensures that the
that device may be incorrect. information displayed is accurate.
Observe the new set of peripherals.
Equipment deleted Station or peripheral is not available Equipment has changed or was
or not responding. deleted. Request the equipment again
through SMDH.
Master timekeepers SMDH cannot initiate communica- Check for an on-line application pro-
not responding tions with a master timekeeper. You cessor (AP). There must be an on-line
cannot set the date and time. AP to run a master timekeeper.
283
B0193JC – Rev U Appendix B. System Messages
Table B-1. System Management Event Messages for SMDH (Continued)

Network error SMDH cannot communicate with Verify network configuration health
the network using Invensys Inter- and revision levels.
Process Communication (IPC).
No counters available SMDH counter data file is not Verify the existence of the path and
for <layer level> available, or there are no counters data file /usr/fox/sysmgm/coun-
for this layer. [See System Operations ters.dat.
Guide (B0193CR) and System
Maintenance (B0193AD).]
No devices exist for You requested to view the peripheral Check the database for configuration
this equipment devices for a particular station, and information concerning peripherals
none are declared. associated with the station, if any.
Check CP database files
USR/FOX/SPC10. Check to see that
FBM gets fixed in configurator Fix
menu. Check if the checkpoint file
exists in USR/FOX/SPUSER. Make sure
Checkpointing is done when the CP is
rebooted.
No Help available at On-line, background (embedded) Verify existence of
this time Help process not running, or /usr/edoc/mdh1.hlp file. No help is
SMDH help file supported for the WP10s. Contact the
(/usr/edoc/mdh1.hlp) is not Global CSC to insure “embedded” is
available. Unable to access file sys- active on the WP.
tem.
No message available Cannot access message files. Check the communication path to the
WP’s file system. Check
/usr/fox/error_msg. Usually the
AP is disconnected.
No Off-line Diagnos- SMDH cannot recognize the type Verify the station type, and the exis-
tics for this station of station, or SMDH’s off-line test tence of /usr/fox/sys-
data file (ofldgn.dat) is not mgm/smdh/ofldgn.dat.
available.
No System Monitors The System Monitor data file Verify the existence of
configured or (smonlst.cfg) is not available and /usr/fox/sysmgm/smonlst.cfg,
responding
no System Monitors responded to verify network communication, verify
SMDH’s request for information. existence of active System Monitor(s).
Reset disable for Message only. This counter cannot be reset.
current number of
connections
Select home for cur- Communications between SMDH Click HOME to re-establish the
rent status:<Sys Mon> and the indicated System Monitor connection.
were broken.
SMDH not in list The System Monitor cannot honor Click HOME. This re-enrolls SMDH
requests from the SMDH. with all System Monitors.
284
Appendix B. System Messages B0193JC – Rev U
Table B-1. System Management Event Messages for SMDH (Continued)

SYSMON not responding Inability to communicate with a Check path to the AP hosting the Sys-
System Monitor. tem Monitor and the load on the AP.
Call the IOM Global Customer Sup-
port.
Unable to communicate SMDH was unable to access System Verify existence of SPF configuration
with SMDH_SPF Configuration Information or the files, and verify that the SMDH/SPF
Software Processing Facility (SPF) interface process smdh_spf is actively
resources. running on the workstation processor’s
(WP) host application processor (AP).
Unable to acquire SMDH was unable to allocate suffi- This indicates a problem with the sta-
needed memory cient memory space to operate. tion/PC running SMDH only. Close
and re-enter SMDH. If the problem
continues, contact the IOM Global
Customer Support.
Unable to initiate General error indicating SMDH Verify communications between
action cannot communicate with a remote SMDH and remote subsystem. If
subsystem (that is, System Monitor, communications are positive, try the
Station Manager, Software Process- action again.
ing Facility).
Unable to open text A particular SMDH private data file Verify the existence of indicated file
file cannot be accessed. The file name is and access to the WP’s file system.
appended to the message.
Network Fault Detection Message

Table B-2. Network Fault Detection Messages
Message Description Action

Configuration Integ- SMDH cannot communicate with, or Check for File Server utility
rity In Question does not know who is, the current operation; close and restart
Nodebus initiator. SMDH.
Standard Coded/Printed Messages

Table B-3. Standard Coded and Printed Messages
Code Message
-1 System monitor(s) have no access
-2 System monitor(s) not responding
-3 Master timekeeper(s) not responding
-4 Checkpoint success
285
B0193JC – Rev U Appendix B. System Messages
Table B-3. Standard Coded and Printed Messages (Continued)
Code Message
-5 Checkpoint failure
-6 Deleted equipment requires returning to previous screen
-7 Unable to initiate network communications – Sys_Mgmt termi-
nating
-8 Unable to acquire needed memory – Sys_Mgmt terminating
-9 Diagnostic supervisor : Execute loop halt
-10 Diagnostic supervisor : Communication failure
-11 Diagnostic supervisor : Restart attempt passed
-12 Diagnostic supervisor : Fail attempt failed
-13 Diagnostic supervisor : Restart attempt failed
-14 No Message
-15 Station added on_line – Reconfigure display?
-16 Diagnostic supervisor : Restart attempt passed
-17 No devices exist for this equipment
-18 Unable to access configuration database
-19 Station already busy – do you wish to override?
-20 Missing station information – do you wish to continue?
-21 Network error – unable to perform operation at this time
-22 Test passed
-23 Test failed
-24 Console interface error – Sys_Mgmt terminating
-25 Text files missing – Do you wish to continue?
-26 No historian available for this system monitor
-27 No system monitors configured or responding
-28 Unable to initiate action
-29 Action not allowed
-30 No counters available
-31 Illegal station type in of ldgn.dat
-32 No Off-line diagnostics for this station
-33 Unable to execute diagnostics
-34 No Help available at this time
-35 No Help required for this screen
-36 Action not allowed on a failed station
-37 Unable to access historian database
286
Appendix C. Device-Specific
Peripheral Counter Background
Information
This appendix contains device-specific information for Peripheral Counters.
Allen-Bradley, Modicon, or Instrument Gateway

NOTE
The Peripheral Counters Display for Allen-Bradley and Modicon scanner devices
shows the “@” character to the left of the controller graphic if there are Level 2
counters available. If there are Level 2 counters, click NEXT LEVEL to access that
counter information.
Counter Description
TIMEOUTS Number of times an ABG, MODG or IG timed-out an attached
device during communication attempts.
INVAL CMND For an ABG, the number of invalid commands from the A-B inter-
face module.
INVAL RESP For an ABG or MODG, the number of invalid commands from a
controller on the Data Highway; for an IG, the number of invalid
commands from a 760 or 761 controller.
Allen-Bradley PLC Devices

NOTE
No PLC remote I/O level cable information is displayed for the AW70. A standard set of commu-
nication counters are maintained by the AW70.
Counter Description
DATE ACCESS READ Number of times read accesses occurred.
DATE ACCESS WRITE Number of times write accesses occurred.
DATE ACCESS READ ERRORS Number of times read data errors occurred.
287
B0193JC – Rev U Appendix C. Device-Specific Peripheral Counter
Counter Description
DATE ACCESS WRITE ERRORS Number of times write access error occurred.
Allen-Bradley Redundant Gateway

NOTE
All fields are initialized to zero when booting the ABG station, when switching to/from CTL
state, and when you select the RESET COUNTERS action.
Counter Description
RDM XMIT COUNT Total number of IPC messages transmitted to alternate gateway.
RDN RECV COUNT Total number of IPC messages received from alternate gateway.
PROCESS UPDATES Number of ABSCAN block updates transmitted to tracking gate-
way if in control mode, or the number of messages received if in
track or standby mode.
RDN OM UPDATES Number of one-time object sets, om-writes, or peer-to-peer scan
updates transmitted if in control or received if in track or standby
mode.
RDN DB UPDATES Number of CIO Configurator database change requests transmitted
if in control mode, or received if in track or standby mode.
RDN IPC UPDATES Number of communication errors detected in IPC link to alternate
gateway.
RDN DB TIMEOUTS Number of times that a heartbeat period (six seconds) expired with-
out receiving an IPC message from the alternate gateway.
RDN RCV UPDATES Number of unrecognized IPC messages received from alternate
gateway.
RDN OM UPDATES Number of one-time object sets, om-writes or peer-to-peer scan
updates resulting in errors detected by tracking gateway.
Allen-Bradley Station PLC

NOTE
288
Appendix C. Device-Specific Peripheral Counter Background Information B0193JC – Rev U
No PLC remote I/O level cable information is displayed for the AW70. A standard set of commu-
nication counters are maintained by the AW70.
Counter Description
DATE ACCESS READ Number of times read accesses occurred.
DATE ACCESS WRITE Number of times write accesses occurred.
DATE ACCESS READ ERRORS Number of times read data errors occurred.
DATE ACCESS WRITE ERRORS Number of times write access error occurred.
Device Integrator
Counter Description
NUM XMIT Number of messages transmitted by the Device Integrator.
NUM ERRS Number of errors that occurred during the transmission of messages from
the gateway.
NUM TMOUT Number of timeouts that occurred during the transmission of messages from
gateway.
NUM RECV Number of messages successfully received by the gateway. Messages are
counted in groups of 10.
RECV ERRS Number of errors that occurred during the receipt of messages to the gate-
way that are not due to a timeout condition (for example, line disconnects).
RECV TMOUT Number of errors that occurred during the receipt of messages to the gate-
way due to timeouts.
RSP TMOUT Number of timeout errors that occurred between the transmission of a mes-
sage and the receipt of a reply.
CHKSUM ERR Number of messages received by the gateway with checksum errors (not all
messages contain checksums).
SEQ NM ERR Number of messages received by the gateway with sequence number errors
(that is, not all messages contain sequence numbers).
BT CNT ERR Number of messages received by the gateway with bad byte counts (that is,
not all messages are transmitted with byte count checks).
PARITY ERR Number of messages received by the gateway with parity byte errors.
DISCONS Number of times the RS-232 port connection on the gateway was
disconnected.
QUEUE FULL Number of messages discarded by the gateway because its queues were full.
289
GE FANUC Programmable Controller Devices
Counter Description
TIMEOUTS Number of times the primary station timed out a GE controller
during communication attempts.
PROTOCOL ERRORS Number of protocol-specific-routine errors detected during commu-
nications with the GE controller.
CRC ERRORS Number of properly aligned frames received with CRC errors.
FRAMING ERRORS Number of misaligned frames that occurred.
COMMUNICATION Number of communication errors detected in GE Controller com-
ERRORS munications link.
BUSY ERRORS Number of times the station attempted communications with the
GE controller and recorded an error because the controller was busy.
INI10 Peripheral, INI15 Peripheral, and SIP
Counter Description
T1 EXPIRES Number of X.25 frame level T1 timer expirations.
PKT LVL TO Number of X.25 packet level timeouts (T20, T21, T22, T23 timers).
ERROR PKTS Number of error packets transmitted and received.
DATA XMTD Number of data packets successfully transmitted and received.
DATA RCVD Number of data packets successfully received.
RR FRAMES Number of Received Ready (RR) frames transmitted and received.
ERR FRAMES Number of error frames transmitted and received.
INTERSPEC Integrator Translator/INTERSPEC Integrator 30
Counter Description
TIMEOUTS Number of times the IIT timed out a peripheral during communica-
tion attempts.
INVAL CMND Number of commands received by the IIT that were invalid in the
present state.
INVAL RESP Number of invalid messages received by the IIT from a peripheral.
I/O Gate ECB98 Devices
Counter Description
SUCCESSFUL Number of messages successfully sent since the last time the statistics
TRANSMITS were initialized.
290
Counter Description
SUCCESSFUL Number of messages successfully received since the last time the statistics
RECEIVES were initialized.
NO RESPONSE CTR Number of times that there was no response to the Clear To Receive
(CTR) signal since the last time the statistics were initialized.
CONNECT ERRS Number of errors generated while attempting to establish
communications.
DISCONNECTS Number of times that the link disconnected since the last time the statis-
tics were initialized. This is the number of established connections that
broke due to error. This counter is incremented only if an established
connection experiences one of the following conditions: retransmits
were exceeded and the client did not acknowledge; no messages were
received from the server in a sufficient time period; the server broke con-
nection due to one of the previous conditions.
AUXILIARY CTR Reserved for use by the application.
I/O Gate ECB99 and ECB100 Devices
Counter Description
SUCCESSFUL Number of messages successfully sent since the last time the statistics
INCOMPLETE Number of incomplete messages sent since the last time the statistics
OTHER Number of errors generated during the transmission of messages that
TRANSMIT ERRS are not due to a time-out condition (for example, link disconnects).
SUCCESSFUL Number of messages successfully received since the last time the statis-
RECEIVES tics were initialized.
INCOMPLETE Number of incomplete messages received since the last time the statis-
RECEIVES tics were initialized.
OTHER RECEIVE Number of errors received that occurred during the reception of mes-
ERRORS sages that are not due to a time-out condition (for example, link dis-
connects).
CHECKSUM Number of checksum errors generated since the last time the statistics
ERRORS were initialized.
PARITY ERRORS Number of parity errors generated since the last time the statistics were
initialized.
DROPPED CHARS Number of characters dropped since the last time the statistics were
initialized.
291
Counter Description
DISCONNECTS Number of times that the link disconnected since the last time the sta-
tistics were initialized. This is the number of established connections
that broke due to error. This counter is incremented only if an estab-
lished connection experiences one of the following conditions: retrans-
mits were exceeded and the client did not acknowledge; no messages
were received from the server in a sufficient time period; the server
broke connection due to one of the previous conditions.
Micro-I/A Station Devices

A Micro-I/A station connects GE and A-B devices to the I/A Series system. Peripheral counters
for A-B Flex™ I/O and GE FANUC devices are not implemented in Software Release
Version 6.0, but will be in a later release.
Modicon Programmable Controllers Devices
Counter Description
TIMEOUTS Number of times the primary station timed out a GE Controller dur-
ing communication attempts.
PROTOCOL Number of protocol errors generated in communications with the
ERRORS Modbus PC.
Protocol-specific-routine errors are detected and reported by the driver
and usually signify an error in the communications link.
CRC ERRORS Number of properly aligned frames received with CRC errors.
FRAMING ERRORS Number of misaligned frames that occurred.
COMMUNICATION Number of communication errors detected in the Modbus communi-
ERRORS cations link.
BUSY ERRORS Number of times the station attempted communications with the
Modbus controller and recorded an error because the controller was
busy.
Primary FBM/FBM Device

These counters are currently not being reported and, therefore, are zero.
Counter Description
TIMEOUTS Number of times the primary station timed out an FBM during com-
munication attempts.
INVAL CMND Number of commands received by the primary station that were
invalid in the present state of the station.
INVAL RESP Number of invalid messages received by the primary station from an
FBM.
292
Printer and Terminal Devices
Counter Description
MSGS DROP Number of alarm messages that could not be printed because the output
device failed.
293
294
Index
760 Micro controller devices 277

820 Series transmitters 216
860 Series transmitters 216
A
A-B Redundant Gateway ECB 180
A-B station 184
PLC5 Series 189
A-B station rack 191
Access
configuration information display 69
equipment change display 139
equipment information 72
performance display 115
peripheral counters display 130
system counters displays 116
system health displays 9
Accessing
for NEXT LEVEL Intelligent Field Devices 73
from a Network Display 70
from a Network Health Display 72
from a System Health Display 70, 72
ACK ALL 51
ACK CBL 16
Actions
configuration information display 72
equipment information display 73
ALARMING STATE 79, 110
Alarms
acknowledging 65
identifying 63
inhibiting 66
responding to network 66
Allen-Bradley
data highway gateway
diagnostics 170
data highway gateway redundant
diagnostics 170
gateway 287
peripheral device off-line 151
PLC Devices
fields 182
peripheral counters 287
295
B0193JC – Rev U Index
redundant gateway 288

station PLC 288
AW70 for Bristol Babcock RTUS ECB97 devices 199
AW70 with Bristol Babcock RTUs ECB96 193
B
Blinking letterbug 21
Block tuning changes 142
C
Change station
action 140
Changes
block tuning 142
FBM status 142
Checkpoint 142
AP file server 142
CLOSE 16
CLR MSG 16
Color-coded device letterbugs 21
Color-coding
health 21
Configuration information display
access 69
actions 72
CORINT Mass Flowmeter 227
Counters
peripheral 136
D
Database
AP server image file 142
Date
setting 54
Device integrator
peripheral counter 289
Device integrator peripherals 206
Device-oriented ECB devices 204
DIAG STATE 79, 110
DISABLE ALL REPORTS 80
Display
configuration information 69
equipment change 139
equipment information 72
for stations and peripherals 73
performance options 115
peripheral names and types 131
296
Index B0193JC – Rev U
primary ECB (FBM0) equipment information 89

set date, time and time zone 53
system counters 116
system health 67
system management counter categories 116
system monitor domains 51
Display handler
system management 21
Display security 19
DOMAIN 16
DOWNLOAD STATE 79, 111
E
EE UPDATE STATE 79, 111
ENABLE ALL REPORTS 80
ENABLE EXCEPTION REPORTS 80
Entry
system health 11
EQUIP CHG 20
Equipment change display access 139
Equipment information
760 Micro controller devices 277
A-B Redundant Gateway ECB 180
display actions 73
display for network printer 81
display for primary ECB (FBM0) 89
display for station 73
display for USB printer 86
displays 72
displays access 72
displays for stations and peripherals 73
fields for Allen-Bradley PLC devices 182
fields for AW70 for Bristol Babcock RTUs ECB97 devices 199
fields for AW70 with Bristol Babcock RTUs ECB96 193
fields for device-oriented ECB devices 204
for device integrator peripherals 206
for Fieldbus Communications Module (FCM) 105
for Fieldbus Module (FBM) 96
for the A-B station 184
for the A-B station PLC5 Series 189
for the A-B station rack 191
Gateway peripherals fields 208
GE controllers (ECB66, ECB67, ECB68) fields 212
I/O Gate peripherals 256
INI10, INI15 or SPECTRUM interface processor peripheral fields 214
intelligent field devices fields 215
INTERSPEC Integrator 30 peripherals 249
INTERSPEC integrator translator 247
Micro-I/A AB-IO peripherals 259
297
Micro-I/A AB-PIO peripherals 260

Micro-I/A AB-RIO peripherals 262
Micro-I/A GE-IO peripherals 263
Micro-I/A GE-PIO peripherals 264
Micro-I/A Station 266
Modicon devices (ECB60/61/62) 269
Port ECB devices 271
Redundant FBM46 273
workstation processor peripherals 278
Exceeded counter threshold conditions
resolution 118
F
FAIL ACK STATE 78, 110
FAIL DEV ACK 79, 110
FAIL DEV ATT 79, 110
FAIL STATE 78, 110
Fault
equipment 51
system equipment 20
Fault-tolerant station
role change 73
FBM
general download for off-line or failed 152
on-line and off-line actions 151
status changes 142
Fieldbus module 96
primary ECB equipment information 89
File server (AP)
checkpoint 142
database image 142
Flashing letterbug
followed by an asterisk 131
FT STATE 78
G
Gateway peripherals fields 208
GE controllers (ECB66, ECB67, ECB68) fields 212
GE FANUC programmable controller devices 290
H
Health color-coding 21
Health displays
system 67
HELP 16
Hierarchy 11
HOME 16
298
I
I/O gate
ECB100 devices 291
ECB98 devices 290
ECB99 291
peripherals 256
Image file
AP server database 142
Image Update 147, 149
Inhibited alarming 68
INI10 interface processor peripheral field 214
INI10 peripheral counter 290
INI15 interface processor peripheral field 214
INI15 peripheral counter 290
Instrument gateway 287
Intelligent field devices
NEXT LEVEL 73
Intelligent field devices fields 215
INTERSPEC
integrator 30 290
Integrator 30 peripherals 249
integrator translator 247, 290
L
Layers
network communication 117
Letterbug
blinking 21
color-coded 21
id 21
Logical name
station 21
M
MAC ADDRESS 79, 111
MAC sublayers 119
Micro-I/A AB-IO peripherals 259
Micro-I/A AB-PIO peripherals 260
Micro-I/A AB-RIO peripherals 262
Micro-I/A devices
Micro-I/A GE-IO peripherals 263
Micro-I/A GE-PIO peripherals 264
Micro-I/A Station 266
Modicon
devices (ECB60/61/62) 269
gateway 287
299
programmable controllers peripheral counters 292

MT REPORT STATE 79
N
Names of peripherals 131
Network
conditions, verification 69
fault detection 4
information 69
Network fault detection subsystem 4
Network printer
NEXT LEVEL
intelligent field devices 73
NFD (network fault detection) 4
Notification
system equipment faults 20
O
On-Line Image Update
Update 149
Overview 1
P
Parameters
software loading 117
Performance display
access 115
Performance options display 115
Peripheral
counters 136
counters displays access 130
names and types display 131
Peripheral counters
Allen-Bradley PLC devices 287
Allen-Bradley redundant gateway 288
Allen-Bradley station PLC 288
device integrator 289
gateways
Allen-Bradley 287
instrument gateway 287
Modicon 287
GE FANUC programmable controller devices 290
I/O gate ECB98 devices 290
I/O gate ECB99 and ECB100 devices 291
INI10 peripheral, INI15 peripheral, and SIP 290
INTERSPEC integrator translator/INTERSPEC Integrator 30 290
300
Micro-I/A devices 292

Modicon programmable controllers devices 292
primary FBM/FBM devices 292
printer and terminal devices 293
Port ECB devices 271
PRIM EEPROM REV 81, 113
PRIM HARD DATE/SHAD HARD DATE 80
PRIM HARD PART/SHAD HARD PART 80
PRIM HARD REV/SHAD HARD REV 80
PRIM ROM ADDRESS 80
PRIMARY MODE 78, 80, 112
Priorities
system event message 6
R
Redundant FBM46 273
RESET ALL 20
RESET ONE 20
Resolution of exceeded counter threshold conditions 118
Role change
fault-tolerant station 73
RUN MODE 78, 109
S
Server
AP database checkpoint image file 142
Set date and time procedure 54
SHAD EEPROM REV 81
SHAD ROM ADDRESS 80
SHADOW MODE 78, 80
SIP peripheral counter 290
SM REPORT STATE 80
SMDH 21
Software manager subsystem 3
Software subsystems 2
network fault detection 4
software manager 3
station manager 3
system management display handler 4
system monitor 2
SOFTWARE VERSION 81
SPECTRUM interface processor peripheral field 214
Station
change action 140
logical name 21
STATION ADDRESS 80
Station manager subsystem 3
STATION NAME 74, 109
301
Sublayer
MAC 119
Subsystems
see software subsystems 3
System
alarms 63
counters display access 116
display condition verification 69
domain information 69
event message priorities 6
event messages 5
health displays 51
health displays access 9
management counter categories display 116
System management display handler 21
System management display handler subsystem 4
System messages 283, 287
System monitor domains display 51
System monitor subsystem 2
T
Threshold
resolving exceeded counter threshold 118
Time
setting 54
Types of peripherals 131
U
UFM (Universal Field Module) 253
UIO (Universal Input/Output) 253
USB printer
V
Verifying network display conditions 69
Verifying system display conditions 69
View configuration information 69
Viewing equipment with inhibited alarming 68
W
Workstation processor peripherals 278
302
303
Invensys Operations Management
5601 Granite Parkway Suite 1000
Plano, TX 75024
United States of America
http://www.iom.invensys.com
Global Customer Support

Inside U.S.: 1-866-746-6477
Outside U.S.: 1-508-549-2424 or contact your
local Invensys representative.
Website: http://support.ips.invensys.com

b0193jc U

Uploaded by

Copyright:

Available Formats

b0193jc U

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

b0193jc U

Uploaded by

Copyright:

Available Formats

What is the purpose of the software license and copyright information section?

What is the purpose of the software license and copyright information section?

What are the main software subsystems discussed in the document?

What are the main software subsystems discussed in the document?

I/A Series® System

Copyright 1992-2012 Invensys Systems, Inc.

SOFTWARE LICENSE AND COPYRIGHT INFORMATION

1. System Management Overview.......................................................................................... 1

2. Introduction to the User Interface ..................................................................................... 9

System Management Display Security ..................................................................................... 19

Station Display Overview ................................................................................................... 46

3. Controlling Date, Time and Time Zone ......................................................................... 53

4. Responding to Alarms ..................................................................................................... 63

5. Monitoring the System.................................................................................................... 67

Overview of the Configuration Information ....................................................................... 69

6. Monitoring Performance ............................................................................................... 115

7. Equipment Changes and Diagnostics ............................................................................ 139

Station Changes .................................................................................................................... 140

Switch Roles for Redundant Equipment ........................................................................... 162

8. Calibrating Equipment.................................................................................................. 175

Appendix A. Device-Specific Equipment Information ....................................................... 179

Gateway Peripherals Equipment Information Fields .............................................................. 208

Appendix B. System Messages ........................................................................................... 283

Appendix C. Device-Specific Peripheral Counter Background Information ...................... 287

Modicon Programmable Controllers Devices ................................................................... 292

Index .................................................................................................................................. 295

5-8. Equipment Information Display for Network Printer ................................................. 82

8-13. Input Status Low HIU .............................................................................................. 246

8-7. Magflow Transmitter Error/Status Code ................................................................... 223

Nodebus Interconnection Configurations

Accessing System Management

System Management Subsystem Software

System Monitor Subsystem

Station Manager Subsystem

Software Manager Subsystem

Server Manager Subsystem

Printer Monitor Subsystem

System Management Display Handler Subsystem

Network Fault Detection Subsystem

Nodebus Cable Faults

Carrierband LAN Cable Faults

PIO Bus Cable Faults

System Event Messages

Operator Notification of System Events

Table 1-1. Event Messages Priorities

Level Related System Event Messages

Accessing System Management Displays

Figure 2-1. Accessing System Management from FoxView

Figure 2-2. Accessing System Manager from Display Manager

Hierarchy of System Management Displays

Table 2-1. Initial System Health Displays

Initial Display Size of System Description

Viewing the Initial Display

Figure 2-3. System Monitor Domains Display (Typical)

Figure 2-4. System Monitors Display (Typical)

Figure 2-5. System Monitor Domain Display (Typical)

Understanding System Management Display Hierarchy

INH DISP TIME NETWORK SW NETWRK PERF OFF-LINE

Equipment Equipment Configuration On-line Intelligent