B0750ap F PDF
B0750ap F PDF
System Manager
B0750AP
Rev F
October 26, 2011
All rights reserved. No part of this documentation shall be
reproduced, stored in a retrieval system, or transmitted by any means,
electronic, mechanical, photocopying, recording, or otherwise,
without the prior written permission of the Invensys Systems, Inc. No
copyright or patent liability is assumed with respect to the use of the
information contained herein. Although every precaution has been
taken in the preparation of this documentation, the publisher and the
author assume no responsibility for errors or omissions. Neither is any
liability assumed for damages resulting from the use of the
information contained herein.
The information in this documentation is subject to change without
notice and does not represent a commitment on the part of Invensys
Systems, Inc. The software described in this documentation is
furnished under a license or nondisclosure agreement. This software
may be used or copied only in accordance with the terms of these
agreements.
Trademarks
Invensys Foxboro, FoxCom, FoxView, InFusion, I/A Series, the
Invensys logo, Tricon, Triconex and Trident are trademarks of
Invensys plc, its subsidiaries and affiliates.
All other brand names may be trademarks of their respective owners.
iii
Contents
CHAPTER 1: Getting Started ..............................1
Overview ................................................................................................ 1
Features............................................................................................... 2
System Management Resources ......................................................... 2
System Monitors................................................................................. 3
System Messages ................................................................................ 5
Security ............................................................................................... 5
Installation and Setup ............................................................................. 6
Interoperability Considerations .......................................................... 6
Installation Procedures ....................................................................... 7
Configuring Interoperability between I/A Series Workstations ......... 9
Starting System Manager.................................................................. 14
The System Manager Service............................................................... 15
Starting and Stopping the System Manager Service......................... 15
Checking if the System Manager Service is Fully Up and Running 15
The System Manager Window ............................................................. 19
How Information is Maintained ....................................................... 20
Viewing Equipment Information.......................................................... 20
System Monitor View ....................................................................... 21
Address Translation Station (ATS) View.......................................... 21
LAN Interface (LI) View .................................................................. 22
Switch View...................................................................................... 24
Health and Alarm Indicators............................................................. 24
Responding to Alarms.......................................................................... 27
Alarms Tab in the Accessories Pane................................................. 27
Acknowledging Alarms .................................................................... 28
Inhibiting Alarms.............................................................................. 29
Next Step .............................................................................................. 29
EEPROM Updates...........................................................................189
Switching Roles...............................................................................190
Module Fieldbus Switching Actions ...............................................190
Index ................................................................313
C H A P T E R 1
Getting Started
This chapter introduces the System Manager software, and describes how to
open the System Manager window and perform several basic functions such as
responding to alarms. Chapter 2, “System Manager Window” provides detailed
information about the user interface, while subsequent chapters describe how
to use System Manager to manage various types of equipment.
Contents
• Overview
• Installation and Setup
• The System Manager Service
• The System Manager Window
• Viewing Equipment Information
• Responding to Alarms
• Next Step
Overview
System Manager is a distributed application for monitoring the health and
performance of all components of an I/A Series system, and managing network
operations.
System Manager software has two components:
• The System Manager service is installed on one or more I/A Series
workstations running the Windows Server® 2003 or Windows XP®
operating systems and interacts with other system management
subsystems including:
• System monitors
• Station Manager software on each workstation and control station
• Software Manager software on each workstation
• Server Manager software on Windows Server operating system only
• Network monitoring facilities
• System Manager client software, which also operates on I/A Series
workstations running the Windows Server 2003 or Windows XP®
Features
The System Manager application provides the capability to:
• View the health of the system equipment, including workstations and their
peripherals, control stations, Fieldbus modules and field devices.
• Monitor the health of network communications hardware including
Ethernet switches, fiber optic cables, Fieldbuses (PIO buses), ATS and
LIs.
• Set the network time on systems without a Global Positioning System
(GPS). For a system with GPS, date and time are set automatically by
GPS.
• Perform Nodebus DST (Daylight Savings Time) adjustments.
• View station configuration information regarding location, system
monitor, host workstation, and so forth.
• For each station, fieldbus device and peripheral, view the current status of
the hardware and software, run mode, failure mode, error status, and so
forth.
• Analyze the performance of each station and field device by monitoring
counters.
• Perform equipment change actions, such as checkpoint, reboot, system
software image/EEPROM update, and download and upload of the control
database.
• Perform online cable tests (LAN and Nodebus) for stations and offline
station diagnostic tests. These tests are useful to field service or
maintenance personnel in identifying and correcting equipment problems.
• Review and acknowledge system alarms.
• Inhibit alarm functions for specific equipment and view the equipment for
which alarms have been inhibited.
• Print and save data contained in various System Manager displays.
• Access on-demand help functions.
workstations, two of which host system monitors. The switches and field
devices are not shown.
AWST01 AWST21
System Monitor
SMON01
SMON01 SMON22
System System
AWST02 Monitor Monitor AWST22
System Manager Domain Domain System Monitor:
Service Only SMON22
System Manager
Service and Client
AWST03 AWST23
System Manager System Manager
Client Only Client Only
Control Stations
FCP100 through
FCP900
System Monitors
A system monitor is a service that runs on an I/A Series workstation and
monitors the health of the stations configured in its domain. The system
monitor application is a standard component in the I/A Series workstation
software.
During system definition, the system monitor software is enabled on one or
more workstations. Other workstations, control stations and switches are
assigned to each system monitor’s domain.
The system monitor supplies status information retrieved from each station in
its domain to designated workstations via a variety of displays including
System Manager.
The system monitor maintains accurate information concerning the health,
current status, and performance of each station and its attached devices.
The system monitor routes standard error messages and system alarm
messages to the designated workstations, logging devices such as printers, and
historians. In addition, the system monitor responds to operator actions and
reports those actions to the System Manager application.
The system monitor domains are configured during the site planning and
system definition phases.
Station Manager
The Station Manager software residing on each station in the network performs
the following functions:
• Maintains communication with the system monitor software
• Maintains a database of equipment information in order to process
requests for changes to equipment status as well as report any status
information to the system monitor
• Provides services such as rebooting stations, initiating diagnostics,
updating software image information, and switching buses.
Software Manager
A Software Manager subsystem located in each workstation performs the
following functions:
• Downloads station images, control databases, and FBM software
• Performs software image updates
• Uploads station images under certain conditions
• Checkpoints control databases.
Server Manager
Server Manager is only installed on Windows Server operating system with
V8.6 and later I/A Series software. It performs the following functions:
• Monitors Dell® critical components that reside on Windows Server
operating system only.
• Utilizes the Simple Network Management Protocol (SNMP) to
communicate with the Microsoft SNMP Service to obtain the status for the
Dell components.
!
Caution The Microsoft SNMP Services are installed on Windows Server
systems running I/A Series V8.6 or later. The services include the SNMP
service and SNMP Trap service. After the installation of I/A Series V8.6 or
later, the SNMP Trap service is disabled and it should not be manually
enabled since the Windows Server, which monitors switches, would be
affected.
System Messages
The system monitors and other workstation functions generate network
operation, equipment health, and equipment status event messages.
Messages may be a general response to an operator’s request, or may contain
an error response reflecting status change, completion messages, operation
results, station limitations, communication malfunctions, or other problems
associated with the station or communication path.
System Manager stores the most recent 500 messages in local memory and
displays them in the Accessories pane Messages tab. For each message, the tab
displays the following:
• Index reflecting the order in which the messages were received by System
Manager
• Date and time the messages were received by System Manager
• System generated message text.
Security
The System Manager software provides two levels of access control:
• The software supports the access scheme defined in the configuration of
the system monitors. System Manager menus and toolbar buttons reflect
the equipment change action privileges configured for the workstation.
Thus, for example, the System Manager Equipment Change Action menu
includes the Reboot command only if the workstation has been assigned
that privilege.
• System Manager can be configured to require the user to confirm
equipment change actions and record the reason for taking the actions.
Refer to “Options Menu” on page 61 for information on these action
settings.
On a workstation running I/A Series V8.5 SE software (with security
enhancements), two criteria must be met in order to perform System Manager
Equipment Change actions such as EEPROM updates, rebooting stations, and
putting stations on-line/off-line:
1. You must be running in a user account that has permission to perform such
actions. For example, a user account that belongs to the Plant Operators
group does not have permission to perform Change Actions, but a user
account that belongs to the Plant Engineers or Plant Maintenance group
does have permission to perform Change Actions. For more information
Interoperability Considerations
Note the following interoperability requirements when installing System
Manager software on I/A Series workstations:
• The System Manager Client and Service must be at the same version in
order to communicate.
• System Manager software is not supported on Solaris™ workstations or
on Windows® workstations running I/A Series software versions prior to
V8.2.
• System Manager V2.2 can be installed on workstations running I/A Series
V8.2 through V8.7.
Warning:
You must follow the steps below to install the Quick Fixes for System Manager
V2.2:
1. Any existing System Manager software must be uninstalled before the
Quick Fixes can be applied. From the Control Panel > Add or Remove
Programs, uninstall currently existing System Manager software.
2. Read the following instructions carefully to determine which Quick Fixes
are required for System Manager V2.2:
a. If the System Manager Server component is installed on a
workstation running I/A Series software versions 8.2 through 8.4.x,
the following Quick Fixes, QF1014714, QF1014716, and
QF1014717, must be installed before the installation of System
Manager V2.2. All three Quick Fixes must be installed for correct
I/A Series operation.
b. If the System Manager Server component is installed on a
workstation running I/A Series software version 8.5, the following
Quick Fixes, QF1014718, QF1014719, and QF1014720, must be
installed before the installation of System Manager V2.2. All three
Quick Fixes must be installed for correct I/A Series operation.
Installation Procedures
During the installation of System Manager software, you are prompted to
install the Client and/or Service components.
This dialog box displays entries for the installation of Microsoft .NET 4.0
Framework software, required by the System Manager software. The pre-
requisite packages for installing this software may vary, depending on your
system. The packages shown in Figure 1-2 are provided as an example.
Click Install to proceed with the loading of pre-requisites.
If the error shown in Figure 1-3 appears during the installation process, you
must first download and install Windows Installer version 3.1, which is the
minimum requirement necessary to have the Visual C++ runtime libraries
installed. Then you can try to install Microsoft .NET 4.0 Framework software
again.
More information about Windows Installer version 3.1 is available at this site:
http://support.microsoft.com/kb/893803
You can download Windows Installer version 3.1 from this site:
http://www.microsoft.com/download/en/details.aspx?amp;displaylang=en&id
=25
Once the System Manager setup starts, it will ask for the selection of
components to be installed. By default, the client component is selected and
the server component is not.
For each I/A Series system, install the System Manager Server only on a
limited number of stations (for example, one or two) to avoid having excessive
traffic on the network.
If System Manager was previously installed with the server component
selected and removed in the previous step, then the server component will be
automatically selected in the following dialog box. Otherwise, the default is
not selected.
There are two interoperability issues that may arise when accessing remote
files between workstations running I/A Series software with and without
security enhancements:
1. If the System Manager Service is installed on an I/A Series workstation
without security enhancements and the System Manager Client is
installed on an I/A Series workstation with security enhancements, the
Options > Configure display in the client reports that the System
Manager Service is not installed.
2. If the System Manager Client is installed on an I/A Series workstation
with security enhancements, you cannot view the System Monitor log that
resides on a workstation without security enhancements.
These two issues exist because the workstation with security enhancements
cannot access the file system of the workstation without security
enhancements.
To configure interoperability between workstations running I/A Series
software with and without security enhancements, perform the following
procedure before invoking the System Manager client:
1. On the workstation with security enhancements, before starting System
Manager, click Start > My Network Places.
3. From the Welcome to the Add Network Place Wizard, click Next:
5. From the ‘What is the address of the network place?’ display, enter the
station name and share name of the I/A Series workstation without
security enhancements, then click Next.
6. Enter the user name and password of the workstation running I/A Series
software without security enhancements, then click OK.
7. If desired, enter a name for the network place on the 'What do you want to
name this place?' display, then click Next.
8. Click Finish on the Completing the Add Network Place Wizard display.
Note
1. Only a user with administrative privileges can access the Event Viewer
application.
2. The System Manager service may take approximately one to two minutes to
be fully up and running.
From the Application page, select an entry where the Source column says
System Manager Service to view the status of the service.
When the System Manager service starts, the presence of the following four
log entries shows that the System Manager service is completely ‘up and
running’. Log entry #4 may take approximately 1 to 2 minutes, depending on
the number of stations in the system.
Information Pane
The window displays system status and equipment information in three panes:
Navigation A tree view of the system equipment arranged by either
system monitor domains, ATS domain, LI domain or
switch domains. When an item is selected in the Navigation
pane, tables in the Information pane provide status,
configuration and equipment information about the item.
Right-click the item in the Navigation pane to display a
context menu of equipment change actions.
Information The content of the Information pane varies with the type of
equipment selected, but generally includes information on
the equipment’s current status, configuration and connected
devices.
Accessories Tabbed pages in the Accessories pane display system-wide
information including messages, system alarms, equipment
for which alarms have been inhibited, counters and system
monitor logs.
Note Choose Help > Legend from the main menu to display a legend of the
icons used in the Navigation pane to identify equipment types.
• Click to the left of any station on the next level to display the
equipment attached to the station.
LIs are configured on the I/A Series network, the LI button on the navigation
tool bar and the LAN Interface view will be disabled. The order of LIs shown
in this display does not indicate the order of physical connections on the bus.
• Click to the left of the device to reveal all the stations residing on a
particular LI domain.
• Click to the left of any station on the next level to display the
equipment attached to the station.
Switch View
When the Switch view is selected, the Navigation pane shows the selected
switch and all the stations and switches connected to it.
• Use the pull-down list to the right of the Switch button to select the switch.
• Click to the left of the switch to display the stations and switches
connected to it.
• Click to the left of any station on the next level to display the
equipment attached to the station.
The symbol attached to a system monitor reflects the most severe condition of
any equipment within its domain. For example, when the problem with
FCP704 (Figure 1-16) is resolved and the FBM returns to normal operation,
the failure symbol is cleared from the FBM, and the warning symbol is cleared
from FCP701, the FBM’s parent control station. The red symbol is removed
from SYSMN1 if there are no other failures in the system monitor domain.
The procedures for resolving an equipment problem vary with the types of
devices involved, but generally include these steps:
1. Expand the marked equipment in the Navigation pane to identify all the
problem devices.
2. Select each device to display its status in the Information pane.
3. Right-click the item in the Navigation pane and choose the appropriate
equipment change action from the context menu.
To display the status of all FBMs connected to a control station:
1. Click the control station in the Navigation pane to display its status and
equipment information in the Information pane.
2. Click the Connections tab in the Information pane to list the connected
devices by name, type, status, run mode and failure mode (Figure 1-17).
3. Click any column header to sort the FBMs by the data in that column.
The item is selected in the Navigation pane and its status and equipment
information are shown in the Information pane.
Responding to Alarms
Acknowledging system alarms and resolving the underlying equipment
problem are separate but related activities in System Manager. Thus, if an
alarm is still unacknowledged when the equipment returns to normal, the
asterisk remains attached to the equipment (ZCP706 in Figure 1-16, for
example).
There are two types of system alarms:
• Alarms reporting a failure in a piece of equipment such as a station, field
device, or peripheral. These are generally referred to as station alarms.
• Alarms concerning communication faults associated with Ethernet cables
and module Fieldbuses. These are generally referred to as cable alarms.
You can view and respond to both types of system alarms in the Alarms tab in
the Accessories pane.
Alarms
Tab
Toolbar
The Alarms tab lists alarms in a multi-column display containing the fields
described in Table 1-1:
3. Click the column header to sort the rows on that column; click the same
column header to reverse the sort order.
4. Select a column and drag it to the left or right to arrange the order of the
columns.
5. Click in the tab toolbar to refresh the table and show the latest alarms.
Acknowledging Alarms
There are multiple ways to acknowledge system alarms using the Alarms tab,
the Navigation pane context menus, and the main menu and toolbar:
Single Alarm
To acknowledge an individual system alarm:
• Select the alarm in the Alarms tab and click in the tab toolbar.
Station Alarms
To acknowledge all equipment failures associated with a station or field
device:
1. Select the equipment in the Navigation pane.
2. Do one of the following:
• Choose Actions > Equipment Change > Acknowledge Station from
the main menu.
• Right-click the selection and choose Acknowledge Station or
Acknowledge Device from the context menu.
Cable Alarms
To acknowledge cable alarms:
• Click in the toolbar, or choose Actions > Acknowledge All Cable
Alarms from the main menu.
Inhibiting Alarms
Inhibiting alarms causes the system to filter alarm conditions so that the system
monitor continues to indicate overall system and network health even while the
equipment is failed or off-line.
To inhibit alarms for a station or device:
• Select an alarm from the equipment in the Alarms tab and click in
the tab toolbar.
• Right-click the equipment in the Navigation pane and choose
Inhibit Alarming or Inhibit Device Alarming from the context menu.
The alarms from the equipment are cleared from the Alarms tab and the
equipment is listed in the Inhibited tab in the Accessories pane. In the
Navigation pane and the Hierarchy Navigation box, a is added to the icons
for the equipment, and the system monitor to indicate that alarms are being
inhibited.
To re-enable the alarms:
• Right-click the equipment in the Navigation pane and choose
Enable Alarming or Enable Device Alarming from the context menu.
Next Step
For additional information about using System Manager:
• Choose Help > Contents or Help > Index from the main menu for
information on specific features.
• Review the next chapter for a catalog of the menus, toolbar features and
other features of the System Manager window. By necessity, Chapter 2,
“System Manager Window”, repeats some of the material in this getting-
started section.
• Reference the relevant equipment-specific chapter for detailed
descriptions of Information pane fields and equipment change actions:
• Chapter 3, “System Monitors”
• Chapter 4, “Workstations and Peripherals”
C H A P T E R 2
This chapter describes the features of the System Manager window, including
the Navigation pane, Information pane, Accessories pane, menus and the
toolbar. The chapter provides information on selecting equipment, displaying
status and equipment information, responding to alarms and performing
equipment changes actions.
Subsequent chapters contain more in-depth information on displays and
procedures for specific equipment.
Contents
• Starting System Manager
• Major Components
• Navigation Pane
• Information Pane
• Accessories Pane
• Menus
• Toolbar
Major Components
Figure 1-10, which is a typical System Manager window on startup, identifies
the major components of the user interface.
Navigation Pane
The Navigation pane on the left side of the window is the principal means for
selecting equipment to display status and equipment information and to
perform equipment change actions.
Information Pane
The area to the right of the Navigation pane provides status and equipment
information for the selected equipment. Depending on the type of equipment,
the pane can include one or more of the following tabular displays:
• General includes tables with status and equipment information, and for
stations and switches, shows the Ethernet switch to which the equipment
is connected, as described in the section “General Tab” on page 41.
• Connections identifies the equipment connected to a station or field
device and gives the status of the connected equipment; see “Connections
Tab” on page 42.
• Ports provides status and equipment information for ports on an Ethernet
switch, as described in the section “Ports Tab” on page 241.
• Counters, described in section “Counters Tab” on page 44, displays
counters read from the selected equipment.
Accessories Pane
The Accessories pane below the Information pane provides system-wide
information. The pane includes the following tabs:
• Messages displays all or selected system messages (page 47).
• Alarms lists system alarms and provides tools for acknowledging and
inhibiting alarms (page 49).
• Inhibited shows the equipment for which alarms are inhibited and allows
you to enable alarming (page 51).
• Search allows you to navigate to a specific piece of equipment based on a
variety of search criteria such as name and equipment type (page 52).
• Watch tracks user-selected counters for various pieces of equipment
(page 53).
• Smon Log displays the log for a selected system monitor (page 56).
Menus
The main menu provides a set of menus for acknowledging alarms, performing
equipment change actions, selecting views, and saving and loading
preferences. Context menus with equipment-specific commands can also be
accessed from each item in the Navigation pane.
Toolbar
The toolbar functions include acknowledging alarms, choosing view options,
selecting equipment, setting the system time and Daylight Saving Time (DST)
adjustment is supported for Address Translation Stations.
Status Bar
The status bar at the bottom of the window identifies the connected System
Manager service and, when a System Manager preference has been loaded
from a file (as described in “Saving and Loading Preferences” on page 57), the
name of the preference file.
Navigation Pane
The Navigation pane is a hierarchical display of equipment in the network,
enabling you to select individual equipment items to be displayed in the
Information pane. The equipment is shown in a tree view similar to the Folders
display in Explorer and other Windows operating system applications.
The Navigation pane displays equipment in one of four selectable tree views:
• System Monitor view displays the system monitors and the equipment in
each system monitor domain. On startup, only the system monitors are
displayed, but each system monitor can be expanded to show the assigned
switches and stations, and each station can be expanded to show connected
equipment.
To select the System Monitor view:
• Click at the top of the Navigation pane, or choose View >
Navigation > System Monitor View from the main menu.
• The ATS view displays all configured ATS modules configured in LAN
Interface mode. Expanding an ATS reveals the stations residing under an
ATS node and its attached devices. This display is available only for
systems that have ATS modules configured in LAN Interface mode.
To select the ATS view:
• Click at the top of the Navigation pane or choose View >
Navigation > ATS View.
• The LAN Interface view displays all configured LAN Interface modules.
Expanding the LAN Interface view reveals all the stations residing in a
particular node. The order of LIs shown in this display does not indicate
the order of physical connections on the bus.
To select the LAN Interface view:
• Click at the top of the Navigation pane or choose View >
Navigation > LAN Interface View.
• The Switch view displays all stations and switches connected to a specific
network switch. Each station can be expanded to display the field devices
or peripherals connected to the station.
To select the Switch view:
• Click at the top of the Navigation pane and select a switch
using the pull-down list to the right of the button.
You can also select the view by choosing View > Navigation > Switch
View from the main menu.
Each system monitor or piece of equipment is identified by an icon and its
name (letterbug). Equipment status is indicated by symbols attached to the
equipment icon. Additional symbols show when there are unacknowledged
alarms and when alarms are inhibited.
On startup, the System Monitor view is selected and the Navigation pane
shows only the system monitors and the first level of the hierarchy. If you
choose the ATS, LAN Interface, or the Switch view, the Navigation pane
displays the corresponding selected stations and respective hierarchies.
• Click to the left of any view (System Monitor, ATS, LAN Interface, or
Switch) or double-click the name to display the stations and switches
assigned to it.
• Click to the left of any station on the next level or double-click the
station name, to display the equipment attached to the station.
• Click to the left of any expanded equipment or double-click the
equipment name to collapse the display and hide the equipment attached
to the item.
You can resize the Navigation pane or use the scroll bars on the right side and
bottom of the pane to bring equipment into view when the tree does not fit in
the pane.
To maximize the display of the system hierarchy in the Navigation pane, you
can select/deselect viewing options for both the Information pane and the
Accessories pane.
• Choose View > Information from the main menu, or click in the
toolbar, to toggle display of the Information pane on and off.
• Choose View > Accessories from the main menu, or click in the
toolbar, to toggle display of the Accessories pane on and off.
• Choose View > Navigation from the main menu, or click in the
toolbar, to toggle display of the Navigation pane on and off.
Navigation Buttons
Use the buttons at the bottom of the Navigation pane to expand and collapse
the display, select equipment, and print the contents of the Navigation pane:
Table 2-1. Navigation Pane Buttons
Expands the display of the selected system monitor or switch domain.
The first time in a session that the button is clicked for a system
monitor, the hierarchy is expanded to show workstations and their
peripherals, controls stations and their primary ECBs, and switches.
Thereafter, the button expands the full hierarchy to display FCMs,
FBMs, and field devices also. Likewise in the Switch view, the first
expansion of a switch domain adds peripherals to workstations and
primary ECBs to control stations. Thereafter, the domain is expanded
to show FCMs, FBMs, and field devices.
In the System Monitor view, collapses the system monitor domain
hierarchy so that only the system monitor name is displayed. The
button can be applied from the system monitor or any object
beneath it.
In the Switch view, collapses the tree view so that only the switch is
shown. The button can be selected from any object in the tree.
Expands the display of the selected equipment so that its child devices
are displayed. This is equivalent to clicking to the left of the item.
Collapses the display of the selected equipment, hiding any child
devices. This is equivalent to clicking to the left of the item.
Moves the focus to the parent of the selected item. The parent
equipment or system monitor is selected in the Hierarchy Navigation
box and the Information pane.
Moves the focus to the first child of the selected item. The child
equipment is selected in the Hierarchy Navigation box and the
Information pane.
Selecting Equipment
When you select a system monitor or piece of equipment in the tree:
• The Information pane displays status and equipment information about the
system monitor or equipment.
• The Hierarchy Navigation box displays the equipment icon and name to
the right of its parent equipment and the system monitor (if the System
Monitor view is selected) or switch (if the Switch view is selected).
• Equipment-specific commands selected from the main menu or the toolbar
are applied to the selected item.
• Equipment change actions are available from the context menu when you
right-click on the equipment (Figure 2-1).
You can also change the selection in the Navigation pane by doing any of the
following:
• Click a parent item in the Hierarchy Navigation box in the toolbar.
• Use the Go-To button and combo box in the toolbar (as described in “Go-
To Feature” on page 79).
• Double-click an item listed in an Information pane Connections tab.
• Double-click an item listed in the results table in the Accessories pane
Search tab.
Equipment Icons
The following table shows the icons that identify system monitors and various
types of equipment:
Table 2-2. Equipment Icons
Symbol Description
This icon is used to identify system monitors, which are displayed in
the top level of the hierarchy when the System Monitor view is
selected in the Navigation pane. System monitors are not shown when
other views are selected. Refer to Chapter 3, “System Monitors” for
information on the displays and equipment change commands
available when a system monitor is selected.
The computer and video display icon represents a workstation. The
workstations are on the second level of the hierarchy below the
station’s system monitor.
Refer to Chapter 4, “Workstations and Peripherals” for additional
information.
Peripherals such as annunciator panels and printers are attached to
their host workstations.
Refer to Chapter 4, “Workstations and Peripherals” for additional
information.
Control stations include modules such as CP and ATS. The 2 adjacent
to the upper right corner of the icon indicates that the station is a
fault-tolerant control station or redundant ATS.
Refer to Chapter 5, “Control Stations, ATSs, and LIs” for additional
information about control stations.
This icon is used to identify LAN Interface Modules, which are
displayed in the top level of the hierarchy when the LAN Interface
view is selected in the Navigation pane. This will also be shown as an
LI station in the System Monitor view.
The 2 adjacent to the upper right corner of the icon indicates that the
station is a fault-tolerant LI.
Symbol Description
A small block icon under each control station represents the station’s
Primary ECB (also known as the Primary FBM), an equipment
control block that manages communications with the attached FBMs.
When the station is an FCP270, CP30, or CP40, a label at the upper
right corner of the block indicates which channel in the module
fieldbus is being used to communicate with the station’s FBMs. When
the station is a ZCP270 or CP60, the label indicates which Fieldbus
cable is being used to communicate with the attached FCMs.
• AUTO when the station automatically switches to the better
channel or cable
• Bus A when the A channel or A cable has been selected by an
operator
• Bus B when the B channel or B cable has been selected by an
operator
Refer to Chapter 5, “Control Stations, ATSs, and LIs” for information
on channel selection.
Fieldbus Communication Modules (FCMs) are baseplate-mounted
modules that connect FBMs to a ZCP270 or CP60 over an optionally
redundant Ethernet fieldbus. One or more FCMs can be shown on the
level below the ZCP270 or CP60’s Primary ECB (Primary FBM).
A label at the upper right corner of the FCM icon indicates which
channel in the module fieldbus is being used to communicate with the
FBMs:
• AUTO when the station automatically switches to the better
performing of the two channels
• Bus A when the A channel has been selected by an operator
• Bus B when the B channel has been selected by an operator
Refer to Chapter 7, “FCMs” for information on channel selection.
The icons for baseplate mounted Fieldbus Modules (FBMs) are
shown below the Primary ECB for the host FCP270/CP30/CP40 or
the FCM that connects the FBMs to a ZCP270/CP60.
Labels to the right of the FBM icon indicate the status of
communication between the FBM and its host FCP270/CP30/CP40
or FCM including communication failures and inhibited cable alarms.
Refer to Chapter 8, “Fieldbus Modules” for detailed information on
these status indicators.
Symbol Description
Certain FBMs can be expanded in the Navigation pane to show a
second level of the attached intelligent field devices. These FBMs
include the FoxCom™ dual-baud rate intelligent device interface and
the Distributed Communication Interface (DCI) modules that support
various fieldbus standards such as HART™, PROFIBUS-DP™, and
FOUNDATION™ fieldbus. The second-level items can be selected to
view device status and equipment information, and to perform
equipment change actions.
Refer to Chapter 8, “Fieldbus Modules” for information on the DCI
based FBMs, including a list of user guides for the specific fieldbus
technologies.
When the System Monitor view is used, the icon for an Ethernet
switch in the The Mesh Control Network is on the second level of the
Navigation pane hierarchy under the switch’s assigned system
monitor. When the Switch view is used, the selected switch is at the
top of the hierarchy, and stations and switches connected to it are
displayed on the second level. Refer to Chapter 9, “Networking
Equipment” for additional information about switches.
The port icon does not appear in the Navigation pane, but is used in
the Ports tab of the Information pane when a switch is selected.
Refer to Chapter 9, “Networking Equipment” for additional
information about ports.
Status Indicators
System Manager indicates system alarms by attaching symbols to the upper
left corner of the icon. This scheme is used in the Navigation pane, the
Hierarchy Navigation box, the Connections tab in the Information pane, and
the results table in the Accessories pane Search tab. The table below shows
how the symbols are used.
Table 2-3. Status Indicators
Symbol Condition
The question mark on a blue background indicates the equipment
is off-line or not ready.
Alarm Conditions
The status of alarms associated with the equipment is indicated by symbols
attached to the lower left corner of the icon in Navigation pane, the Hierarchy
Navigation box, the Connections tab in the Information pane, and the results
table in the Accessories pane Search tab. Table 2-4 shows how these symbols
are used with a workstation.
Name Condition
Yellow The equipment has a warning condition, most often because an
attached peripheral or field device has failed.
Name Condition
Red The equipment has failed.
Black The equipment is operating normally or is off-line. The name
will continue to blink if the alarm has not been acknowledged
even though the equipment has returned to normal.
The blinking stops and the name is displayed in black when the alarm is
acknowledged.
Information Pane
The area to the right of the Navigation pane is used to display information
about the selected equipment.
• Choose View > Information from the main menu, or click in the
toolbar, to toggle display of the Information pane on and off.
The information is arranged in one or more tabular displays depending on the
type of equipment that is selected and whether it has attached devices.
General Tab
The General tab displays status and equipment information for the selected
equipment (Figure 2-2). The Equipment Status table is updated dynamically,
while the Equipment Information table is updated periodically.
Values are displayed in green when they change from the previous update.
An Equipment Status field remains green until the next status update received
from the equipment results in no change to that field. For example in Figure 2-
2, the Failed Acknowledged State is green indicating that field was changed to
Acknowledged when the user acknowledged an alarm. If several minutes later,
the same or another user enables alarms, the Alarming State field will change
from Inhibited to Enabled and Failed Acknowledge State will change from
Acknowledged to Acknowledged. Depending on what is happening with the
equipment, a status field may remain green for several seconds, several
minutes, or even for the remainder of the session.
Equipment Information fields remain green for 10 seconds and then change to
black if there is no change detected on the next scan of the equipment
information.
The fields in both tables vary with the type of equipment selected. Figure 2-2 is
the General tab for a fault-tolerant FCP270. Subsequent chapters catalog the
fields for system monitors and various equipment types:
• “System Monitors” on page 85
• “Workstations and Peripherals” on page 91
• “Control Stations, ATSs, and LIs” on page 111
• “Primary ECB (Primary FBM) Information” on page 136
• “FCMs” on page 177
• “Fieldbus Modules” on page 193
• “Networking Equipment” on page 237.
The General tab for stations and switches also includes a Switch Connections
area that shows the switches to which the equipment is connected.
Do one of the following to select a connected switch for display in the
Information pane:
• Double-click the switch name
• Right-click the switch name choose Navigate to <switch name> from the
context menu.
Connections Tab
The Connections tab provides a summary of the attached equipment selected in
the Navigation pane. It is available for stations, FCMs, FBMs, System
Monitors, and Switches with attached devices. The Connections tab shows the
hierarchical next level connections for the selected component. The
Connections tab has been extended for LI and ATS, but in these two cases it
shows logical connections rather than attached devices. Logical connections
represent the stations residing under an ATS node (ATSs which are configured
in LI mode) or an LI node. The Connections tab will not be shown for ATS if
configured in 'Extended Mode'. Additionally, no Connections tab will be
shown for ATS when seen under the Switch View. Figure 2-3 shows an
example of the Connection Tab view.
In the Name column, the tab identifies each piece of equipment and its status
using the same icons and symbols used in the Navigation pane. The other
columns list the equipment type, status, run mode and failure mode.
To modify the table layout:
• Drag a column header to the right or left to change the order of the
columns.
• Drag the right edge of a column to the right to increase the column width
or the left to decrease the width.
• Scroll the displays if necessary using the scroll bars on the right side or
bottom of the tab.
• Click any column header to sort the rows on that category; click the
column a second time to reverse the sort order.
To navigate to equipment listed in the tab, do one of the following:
• Double-click the equipment name.
Counters Tab
System Manager provides access to a variety of counters maintained by the
equipment itself to assist in monitoring performance and isolating problems.
The counters track items such as messages sent and received, invalid
commands, communication overruns, timeouts and so on.
Use the Counters tab for a selected station or peripheral device to periodically
read the counters for the equipment. The tab also enables you to reset selected
or all counters maintained by the equipment, if the workstation has the
appropriate equipment change action privileges.
Individual counters can be selected in the Information pane tab and placed on a
watch list to be monitored with counters for other system equipment (as
described in “Watch Tab” on page 53).
The types of counters vary with the equipment and are described in subsequent
chapters. Common features in the display are shown in Figure 2-4 with the
Counters tab for an FCP270 selected in the Information pane and the Watch tab
displayed in the Accessories pane.
The Counters tab includes one or more tables showing the Current and
Previous values and the Maximum and Minimum readings for each counter.
Maximum and Minimum are the highest and lowest values read from the
equipment in the current System Manager session.
When you select the tab, System Manager reads the counter values from the
equipment, and updates the columns accordingly. If this is the first time in a
System Manager session that the counters are read, the Current, Maximum,
and Minimum values are equal, and the Previous column is empty. You can
then read all or selected counters. The new Current value is displayed in green
text if it differs from the previous value.
The Counters tab for workstations and control stations include five separate
tables of counters, which are selected using the Counter Categories radio
buttons (Figure 2-4). These tables of counters are:
• MAC Sublayer
• Network Layer
• Transport Layer
• Application Layer
• Loading Parameters
Note Network Layer option will be enabled for LI and ATS stations only.
• To select multiple counters, click the first counter and then press Ctrl as
you click each additional item.
The Counters tab toolbar includes the function buttons listed in the following
table:
Table 2-6. Counters Tab Toolbar Buttons
Reads the selected counters and updates the Current, Previous,
Maximum and Minimum values accordingly. The new value is
displayed in green if it differs from the previous reading.
Reads all counters in the table from the equipment and updates the
Current, Previous, Maximum and Minimum columns accordingly.
Accessories Pane
The Accessories pane, which is positioned below the Information pane,
provides system-wide information and navigation tools in the following tabbed
pages:
• Messages
• Alarms
• Inhibited
• Search
• Watch
• Smon Log
To show or hide the Accessories pane:
• Click in the toolbar or choose View > Accessories from the main
menu.
Each tab features a toolbar with buttons that enable you to perform related
tasks, navigate to specific equipment, and print and save the tab contents. You
can also do any of following to adjust the display:
• Drag the bottom edge of the Information pane up or down to adjust the
number of rows displayed in the Accessories pane.
• Drag a column header to the right or left to re-arrange the order of the
columns.
• Use the scroll bars on the right side of a tab to view additional rows in a
table.
• Click a column header to sort the table rows on the data in the column;
click the header a second time to reverse the sort order. This feature is not
available in the Messages and Smon Log tabs.
Each tab includes three buttons for printing and saving the tab contents:
• Click to open the Page Setup dialog box from which you can format
and preview a printed report of the tab contents.
• Click to open the Page Setup dialog box from which you can format
and print a report of the tab contents.
• Click to output the contents of the tab to a file.
See “Printing System Manager Information” on page 58 for additional
information on printing.
Messages Tab
The first tab in the Accessories pane lists system messages in a three-column
display, showing the message index, a timestamp when the message was
received by System Manager and the message text (Figure 2-5).
When System Manager is started it begins accumulating system messages in a
list, and makes these messages available in the Messages tab. When there are
500 messages in the list, incoming messages replace older messages on a first-
in, first-out basis. The message index is not reset until the list is cleared.
The messages are cleared from local memory when the System Manager
session is ended. Click in the Messages tab toolbar to save messages in a
separate file.
Messages
Tab
Toolbar
Message Filtering
Use the message filtering controls to select which messages are displayed in
the tab. The selection can use any combination of three criteria:
• Date and time range
• Messages that include a specific text string (Match)
• Messages that do not include specified text (Filter).
To display only messages of immediate interest:
1. Click in the tab toolbar to display filtering controls in the tab
(Figure 2-6).
2. Check Date/Time Range and use the Begin and End controls to specify
the range.
• The dates can be changed manually or with a calendar control pulled
down with the arrow button on the right edge of each date field.
• The times can be specified manually (using a 24-hour clock) or by
clicking the spinner buttons on the right edge of each time field.
• Uncheck Date/Time Range to display messages from the full range
stored by System Manager.
3. Right-click Match and choose Create from the context menu to add a
match string (with the default name edit text) under Match.
4. Right-click the string, choose Edit from the context menu, and specify the
text to be used in the match.
The Match and Filter fields use substring searches. Thus, for example,
CP12 would find FCP123, ZCP122, and ZCP129.
5. Add other match strings.
6. Right-click any match string and choose Edit from the context menu to
change the string or Delete to remove it.
7. Right-click Filter and add filtering criteria using the same procedures as
used for creating, editing and deleting Match strings.
8. Check the box for Match and the box for each individual match string you
want to apply.
As set in Figure 2-6, the Messages tab will display any message that
includes the string Inhibit, but it will not apply the match string FC.
9. Check the box for Filter and the box for each filter criteria you want to
apply.
10. Click Apply to display only messages that meet the criteria.
System Manager clears the tab and displays messages that match the
criteria. New messages are displayed only if they meet the specified time,
match and/or filter criteria.
Alarms Tab
The Alarms tab (Figure 2-7) lists both device and cable alarms in a multi-
column display:
Table 2-8. Alarms Tab Display Fields
* An asterisk indicates that an alarm has not yet been
acknowledged. Otherwise, the column is blank.
Index A unique ID number.
Date/Time The timestamp indicates when the alarm was generated.
Source Source from which System Manager received the alarm,
usually a system monitor.
Alarms
Tab
Toolbar
Inhibited Tab
System Manager enables you to inhibit alarming for selected equipment so that
the system monitor continues to indicate overall system and network health
even while the equipment is failed or off-line. When alarming is inhibited, the
system does not send alarm messages for the equipment to the printer or
historian.
To inhibit alarms from a specific piece of equipment, do one of the following:
• Right-click the equipment in Navigation pane and choose Inhibit
Alarming, Inhibit Device Alarming or Inhibit PIO Bus Cable A/B
Alarms from the context menu.
• Select an alarm from the equipment in the Alarms tab and click in the
Alarms tab toolbar.
The Inhibited tab (Figure 2-8) lists all equipment on the network for which
alarming is inhibited. This equipment can include cables, stations, switches,
and field devices.
The Item column lists the system monitor, the parent devices and the
equipment.
To change the way the inhibited items are displayed:
• Drag a column header to the right or left to re-arrange the order of the
columns.
• Click a column header to sort the rows on data in the column; click the
column a second time to reverse the sort order.
Inhibited
Tab Toolbar
To enable alarming:
1. Select the equipment in Navigation pane.
2. Choose Enable Alarming, Enable Device Alarming, or Enable PIO
Bus Cable A/B Alarms from the context menu.
Search Tab
Use the Search tab (Figure 2-9) to find a specific piece of equipment based on
a variety of search criteria such as name and equipment type, and then navigate
to the equipment. The tab consists of fields on the left for specifying search
criteria and a table on the right to display search results.
The Search tab toolbar includes the following buttons:
Table 2-11. Search Tab Toolbar Buttons
Clears the search criteria and empties the results table.
Opens the Page Setup dialog box from which you can format and
preview a printed report of the search results.
Opens the Page Setup dialog box from which you can format and
print a report of the search results.
Outputs the equipment listed in the results table to a text file.
Search Tab
Toolbar
To find equipment:
1. Use the Category pull-down menu to select system monitors or one of the
following general categories of equipment:
• SMON
• Switch
• Workstation
• Control Processor
The tab displays fields for additional search criteria appropriate for the
selected category.
2. Enter additional search criteria in the additional fields if desired.
• Use the drop-down list in fields such as Type and SMON to select
additional criteria.
• Enter a text string in the name field, using an asterisk as a wildcard.
For example:
• Enter FCP123 to find the device whose name matches the string
FCP123 exactly.
• Enter FCP* to search for names that start with the FCP.
• Enter *CP* to find all names that contain the string CP.
• Enter *804 to find all names that end with the string 804.
The drop-down lists contain the search strings used for previous
searches. The strings are cleared when System Manager is closed.
• To find a classic workstation or control processor, select None in the
Switch Connection drop-down menu. All is the default option in the
Switch Connection field. Refer to Figure 2-9.
3. Click Search to start the search and display the results in the table to the
right.
4. Do one of the following to navigate to an item in the table, select the item
in the Navigation pane and display the equipment status and information
in Information pane:
• Double-click the equipment name.
• Right-click the equipment and choose Navigate to <equipment
name> from the context menu.
To change the way the search results are displayed:
• Drag a column header to the right or left to re-arrange the order of the
columns.
• Click a column header to sort the rows on data in the column; click the
column a second time to reverse the sort order.
Watch Tab
Use the Watch tab to monitor up to 25 counters for different pieces of
equipment. The counters are selected from the Counters tabs for the equipment
to be monitored. Figure 2-10 shows a Counters tab for an FCP270 above the
Watch tab.
The counter is identified by name and the equipment letterbug (Source). The
Current, Previous, Maximum and Minimum values are copied from the
Counters tab, but once copied, these values can be read and reset from the
Watch tab.
To change the way the counters are displayed:
• Drag a column header to the right or left to re-arrange the order of the
columns.
• Click a column header to sort the rows on data in the column; click the
column a second time to reverse the sort order.
To select multiple counters in the Watch tab:
• Click the first counter and then press Ctrl while clicking the additional
counters.
The Watch tab toolbar includes the following buttons:
Table 2-12. Watch Tab Toolbar Buttons
Clears the all counters from the watch list.
Note
1. System Manager does not support creating or viewing System Monitor logs
hosted on Solaris stations.
2. The View button is disabled when you select a System Monitor with
unknown status.
3. If the Smon host workstation is not reachable, an error message appears
stating that Cannot access Smon Log on <Station Name>,
Station unreachable.
System Manager reads the selected log and displays approximately 1,000
of the most recent entries.
The tab shows when the log was created and the current size of the log in
the system monitor workstation.
2. Use the scroll bar on the right side of the tab to scroll to previous log
entries.
The Smon Log tab toolbar includes the following buttons:
Table 2-13. Smon Log Tab Toolbar Buttons
Clears the selected system monitor log. This command is only
available if the workstation has equipment change action privileges.
Opens the Page Setup dialog box from which you can format and
preview a printed report of the tab contents.
Opens the Page Setup dialog box from which you can format and
print the log.
Outputs the contents of the tab to a file.
Menus
This section describes the menus that can be pulled down from the System
Manager main menu. Many of the options in these menus can be accessed from
a toolbar icon or from a context menu when you right-click the equipment
name in the Navigation pane.
File Menu
The File menu contains selections for printing System Manager information,
saving and loading preferences, and exiting the application.
User Name
2. Use the dialog box to specify a folder and a file name (but not extension)
for the preferences.
Figure 2-12 shows the default path for preferences files, the Applications
Data folder in the user’s Documents and Settings. Note that the two
variable elements in this path are the user name and the version number.
3. Click Save.
Multiple preferences files can be created.
When it initializes, System Manager always uses a default layout and connects
to the System Manager service in use at the end of the previous session. You
can load a previously saved setup at any time during a session.
To load previously saved preferences, do one of the following:
• Choose File > Load Preferences from the main menu, use the Windows
operating system Open dialog box to browse for and select the preference
file, and click Open.
• Choose File > Recent Files > {File Name} from the main menu.
Recent Files lists preference files loaded in the current and previous
sessions.
2. Use the dialog box controls to make changes in the page layout, and if
desired, click Printer to select a printer and printer properties.
The printer properties dialog boxes vary with the type of printer selected.
3. Click OK to display the report in the Print preview window (Figure 2-
14).
4. Use the controls at the top of the window to scale the preview and select
the number of pages to be displayed in the preview.
5. Click Close to return to the Page Setup page if the page layout requires
change.
6. Click to print the report using the selected printer and layout.
The Navigation pane and each of the Accessories tabs include two print
selection buttons that also enable you to print the contents of the window area:
Opens the Page Setup dialog box (Figure 2-13) from which you can
format and preview a printed report of the selected display.
Opens the Page Setup dialog box from which you can format and
print a report of the selected display.
Exit
To end a System Manager session:
• Choose File > Exit from the main menu, or click at the right edge of
the title bar.
If a preference file is currently loaded, a dialog box prompts you to save
changes made to the System Manager layout during the current session
(Figure 2-15), even if no changes were made to the loaded layout. There is
no prompt to save changes made to the Default layout.
If you issued commands such as Acknowledge All Stations just before closing
the window, the commands may still be executing after you exit. Once
initiated, the commands are not dependent on the window remaining open.
View Menu
Use the View menu to select viewing and navigation options:
• Choose View > Accessories, or click in the toolbar, to toggle display
of the Accessories pane on and off.
The Accessories pane is described on page 46.
• Choose View > Information, or click in the toolbar, to toggle
display of the Information pane on and off.
The Information pane is described page 41.
• Choose View > Navigation, or click in the toolbar, to toggle display
of the Navigation pane on and off.
• Choose View > Navigation View > Hierarchy to toggle display of the
Hierarchy Navigation box in the toolbar.
The Hierarchy Navigation box is described page 79.
• Choose View > Navigation View > System Monitor View to change the
Navigation pane to the System Monitor view.
• Choose View > Navigation View > ATS View to change the Navigation
pane to ATS view.
• Choose View > Navigation View > LAN Interface View to change the
Navigation pane to the LAN Interface view.
• Choose View > Navigation View > Switch View to change the
Navigation pane to the Switch view.
• Choose View > Status bar to toggle display of the status bar at the bottom
of the window.
The status bar displays the connected System Manager service, the most
recent system message, and the name of the preferences file.
• Choose View > Toolbar to toggle display of the toolbar.
Options Menu
The Configure command in the Options menu opens a dialog box for
specifying connection to a System Manager service, setting requirements for
equipment change actions, and choosing view preferences (Figure 2-16).
When System Manager is started for the first time on a workstation, the
application displays a Configuration dialog box so that you can specify a local
or remote connection to a System Manager service.
Proxy Settings
On startup, System Manager automatically connects to a System Manager
service on a workstation specified in the Proxy Settings group in the
Configuration dialog box (Figure 2-16).
Note If you are running I/A Series software with security enhancements, you
must be logged in to a user account with administrative privileges in order to
switch to a System Manager Service running on a Windows Server 2003
workstation. If you are logged in to an Operator account, for example, System
Manager will report an error if you attempt to connect to a System Manager
Service on a Windows Server 2003 workstation.
If either of the errors as shown in Figure 2-18 and Figure 2-19 appears,
clicking No cancels the connection process, and clicking Yes allows you to
connect to another System Manager service.
To connect to a different System Manager service:
1. Click Yes and the Configuration dialog box appears.
2. Use the Connect To pull-down menu on the Configuration dialog box to
select a workstation.
3. Confirm that the service is operating on the station (that is, Service
Installed is Yes and Service Status is Running), and then click OK.
Manager graphical user interface is grayed out and the status bar indicates that
the workstation is disconnected.
Action Settings
Action Settings are applied to the equipment change actions such as Reboot
and Off-Line that affect the operational status of the selected station or device.
The settings are not applied to alarm acknowledgments, commands to inhibit
and enable alarms, and channel/cable switching.
The equipment change commands are initiated from the Actions menu and the
equipment’s context menus in the Navigation pane. There are two settings:
• When Confirmation Required is checked, System Manager displays a
confirmation dialog box when one of the commands is initiated (Figure 2-
22, top).
View Settings
When Enable blinking is checked, the names of system monitors and
equipment with unacknowledged alarms blink on and off in the Navigation
pane, and color-coding of the names is used to indicate the item’s status (red
for failed, yellow for warning and so forth). When the alarm is acknowledged
the names of the affected equipment stop blinking and are displayed in black.
When the option is not checked, all names are displayed in black without
blinking, regardless of the item’s alarm status.
Actions Menu
The Actions menu includes the following items: Equipment Change,
Acknowledge Smon Domain, Acknowledge Cable Alarms, Set Date and Time,
DST Options, and Download FF Devices File.
Equipment Change
Only workstations assigned the appropriate equipment change action
privileges can access the equipment change commands.
• Choose Actions > Equipment Change to display a menu of commands
for the selected equipment.
The list of equipment change actions varies with the type of device and its
current status. Figure 2-24 shows the commands available when an FCP270 is
selected from a workstation with full equipment change action privileges.
The Actions > Equipment Change menu of a station includes some or all of
the following items in Table 2-14:
Table 2-14. Actions > Equipment Change Menu Items
The Actions menu includes some or all of the following items (Table 2-15) for
ECBs:
Table 2-15. Actions > Equipment Change Menu Items for ECBs
Table 2-15. Actions > Equipment Change Menu Items for ECBs
The equipment change actions menu items that are applicable for each device
group are given in Table 2-16
Table 2-16. Equipment Change Actions for Device Groups
Equipment Change
Actions Device Groups
EEPROM update FCM10E and GE PIO
Enable Device Alarming All device groups
Inhibit Device Alarming
General Download AB PIO and GE PIO
Profibus Gate
Echelon Gate
PLC5 Gate
Modbus Gate
Go On-line All device groups except Bristol Babcock Port
Go Off-line and F2068 Port
Periodic PIO Bus Switching AB Port
Bus A Enable Switching Modbus Port
Bus B Enable Switching GIT devices
Bus A Disable Switching
Bus B Disable Switching
PLC - Program ABPLC devices
PLC - Run
PLC - Test
Upload Database
Reset Major Fault
Reset Minor Fault
Download AB PIO and GE PIO
AB RIO Adaptor
DST Options
Instructions to configure Daylight Saving Time adjustments and the DST
Options command are given in “Daylight Saving Time (DST)” on page 81.
2. When the Download FF Devices File dialog box is being loaded, “Loading
the dialog box” appears in the left corner of the System Manager status
bar, and the progress is indicated in the right corner of the status bar.
3. The Download FF Devices File dialog box appears and lists workstations
that are currently running. Select those workstations to which you want to
copy the FFRegistered.xml file. When the download is being performed, a
description of the current status appears in the left corner of the Download
FF Devices File dialog box, and the progress is indicated in the right
corner of the status bar, as shown in Figure 2-27.
7. If the download fails for any of the selected workstations, the following
dialog box appears and lists the workstations for which the download
failed.
8. If the download procedure fails, you may need to modify file sharing
properties on each of the workstations for which the download failed.
Perform the following steps:
a. Open Windows Explorer software.
b. Select Tools > Folder Options.
c. From the Folder Options dialog box, click the View tab.
Help Menu
The Help menu contains the following items:
About Displays the version and copyright notices for the System
Manager software.
Legend Provides a key to the equipment icons and the status
symbols used in the Navigation pane and the Hierarchy
Navigation box.
Contents Starts compiled HTML Help for the System Manager user
interface and displays the Help Contents tab.
Index Starts HTML Help and displays the Help Index tab.
Search Starts HTML Help and displays the Help Search tab.
Toolbar
The toolbar contain buttons for commonly used functions, commands,
additional navigational controls, and tools for setting network time. In
addition, the toolbar displays the current system date and time, DST Options
and the Master TimeKeeper. Figure 2-30 displays an example of the toolbar.
DST Options
Acknowledge Information System Date
Cable Alarms Pane and Time
Navigation Pane
Set Date/Time
Acknowledge Navigation Hierarchy Master Timekeeper
Smon Domain Go To Device
Accessories
Pane
Alarm Icons
• Select a system monitor in the Navigation pane and click to
acknowledge all station alarms in the system monitor domain.
Clicking this icon is the same as choosing Actions > Acknowledge Smon
Domain from the main menu, or Acknowledge Smon Domain from the
system monitor’s context menu.
• Click to acknowledge all communication faults associated with
cables, transmitters, receivers, and fieldbuses.
Clicking this icon is the same as choosing Actions > Acknowledge Cable
Alarms from the main menu.
These buttons are only selectable if the workstation has been designated to
perform secured actions during system monitor software configuration
and the system monitor is currently active.
View Icons
• Click to toggle display of the Accessories pane.
Clicking this icon is the same as choosing View > Accessories from the
main menu.
• Click to toggle display of the Information pane.
Clicking this icon is the same as choosing View > Information from the
main menu.
• Click to toggle display of the Navigation pane.
Clicking this icon is the same as choosing View > Navigation from the
main menu.
Go-To Feature
The Go-To icon (Figure 2-31) and the drop-down menu to its right enable you
to search for and navigate to system monitors, stations and field devices by
name. The found item is selected in the Navigation pane and the Hierarchy
Navigation box, and displayed in the Information pane.
2. Click to find the next instance of the string specified in the combo
box and select that item in the Navigation pane.
3. Click to the right of the box to pull down a list of previous search
strings.
The list of previous search strings is cleared when System Manager is
closed.
Hierarchy Navigation
The Hierarchy Navigation box (Figure 2-32) is used to view and quickly
navigate to predecessors in the selected equipment’s hierarchy.
When the System Monitor view is selected for the Navigation pane, the box
displays the currently selected station or device, its parent equipment and
system monitor using the same symbols that are used in the Navigation pane.
When the Switch view is selected for the Navigation pane, the box displays the
currently selected station or device, its parent equipment and the switch using
the same symbols that are used in the Navigation pane.
When a clock icon is shown to the left of the master timekeeper name, the
system date and time can be set from System Manager.
Caution Resetting the time can affect other activities on the network, such as
historian collection, trending and reporting. Only authorized personnel should
set the time and date.
To keep all stations on the node synchronized, you must make time and date
changes through the Set Date and Time command, not through the Windows
operating system Adjust Time/Date functions (selected from the tool tray or
Control Panel) on individual workstations.
To adjust the master timekeeper when the time is not sourced from the GPS:
1. Choose Actions > Set Date and Time, or click in the toolbar, to open
a dialog box for setting the date and time (Figure 2-34).
adjustments are provided that allow an operator to determine when DST time
adjustments are sent to Nodebus stations. This feature provides protection for
applications where changing time backwards (from Daylight Saving Time to
Standard Time) could cause problems.
The DST Options dialog box is shown when you click the DST Options
button (Figure 2-35). You can choose to have DST time adjustments sent
automatically or manually. These options ensure backward-compatibility for
I/A Series system releases with Nodebus networks, where the operator decides
when to manually change time using System Manager to adjust for DST.
DST Options
button
DST Options
Figure 2-36 shows the information presented on the DST Options dialog box.
When you click the DST Options button on the Toolbar, the DST Options
dialog box appears and shows the current time settings of the Nodebus and
The Mesh network.
• If Nodebus DST Mode is set to Automatic, time sent to the Nodebus
stations is the same as The Mesh time mode (Standard Time or Daylight
Saving Time). Any selection made under Nodebus Network has no effect.
• If Nodebus DST Mode is set to Manual, time sent to the Nodebus
stations is based on Nodebus Time Mode regardless if The Mesh is in
Standard Time or Daylight Saving Time mode.
To change the Nodebus station times from Standard Time to Daylight Saving
Time or vice versa:
1. Make sure Nodebus DST Mode is set to Manual. This enables the
Standard Time and Daylight Saving Time options available under Time
Settings.
2. Choose Standard Time or Daylight Saving Time under Time Settings
for the Nodebus Network.
3. Click Apply.
The message “Do not reboot any workstation for 1 minute” on the System
Manager message line confirms that the System Manager selection has been
processed. The user is warned not to intentionally reboot workstations until 1
minute to allow all workstations to record the System Manager time selection
thus making the time selection persistent should a workstation later fail and a
new Master Timekeeper take over. The worst scenario that could happen is that
the Primary MTK workstation fails immediately 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 System
Manager time state and immediately reverting back to the previous time state
when a new Master Timekeeper takes over. You would then have to repeat
their desired time selection.
C H A P T E R 3
System Monitors
When the System Monitor view is selected, the system monitors are shown at
the top of the tree in the Navigation pane. Each system monitor is identified by
the icon and the system monitor name (Figure 3-1).
Contents
This chapter describes status symbols attached to the system monitor, the
Information pane displays when a system monitor is selected and how to
acknowledge all station alarms within the domain.
• Status and Alarm Symbols
Symbol Condition
There is at least one alarm in the system monitor domain that
has not been acknowledged.
The status of the system monitor reflects the most severe condition in its
domain. If the System Manager service cannot communicate with a system
monitor, the Unknown symbol is attached to upper left corner of the icon and
the system monitor name is displayed in gray italicized text, as shown in
Figure 3-2.
Field Description
Name Name of the system monitor
Host Letterbug Name of the workstation on which the system monitor is
running
LI Letterbug Name of the LAN Interface host name (letterbug) for the
selected Carrierband LAN station
Historian Name of the historian acquiring messages from the
system monitor
Revision Level Revision level of the system monitor software
Monitored Equipment
To access additional information about stations and switches in the system
monitor domain:
1. Click the Connections tab to display a table of the stations and switches.
The table lists the monitored equipment by name and type, and shows the
status, run mode and error mode of each item (Figure 3-4).
2. Click any column header in the table to sort the rows on that column; click
the column header a second time to reverse the sort order.
3. Drag a column header to the right or left to change the column order.
4. Do one of the following to navigate to a station or switch:
• Double-click the equipment name.
• Right-click the equipment name and chose Navigate to <equipment
name> from the context menu (Navigate to FCP702 in Figure 3-4).
The item is selected in the Navigation pane and the Information pane
General tab displays status and equipment information tables for the
selected device.
Acknowledging Alarms
The asterisk is attached to the bottom left corner of the system monitor icon if
there is at least one unacknowledged station alarm in the system monitor’s
domain. There are multiple ways of acknowledging alarms:
• The System Manager toolbar contains a button for acknowledging all
station alarms in the selected system monitor domain and a button for
acknowledging all cable alarms system-wide.
• The Alarms tab toolbar contains buttons for acknowledging all alarms and
individual alarms.
• The context menus in the Navigation pane contain selections for
acknowledging alarms at the equipment level and/or domain level.
To acknowledge all station alarms in a system monitor domain:
1. Select the system monitor in the Navigation pane.
C H A P T E R 4
Contents
• Identification of Workstations and Peripherals
• Workstation Information
• Connected Peripherals
• Counters Tab
• Peripherals Information
• Equipment Change Actions
Alarms from WP
are inhibited Station transmitter/
receiver cable alarms
are inhibited for
Nodebus A and B
Station transmitter/
receiver cable alarms
for Nodebus A
are inhibited
Figure 4-2. Nodebus Workstations and Peripherals in the Navigator
Symbol Condition
The top right corner is used for indicators of a fault in the
station’s connection to the network when the fault is with
A channel (Receiver A) and middle right when the fault is in
B channel (Receiver B).
Workstation Information
When a workstation or a server is selected, the General tab in the Information
pane (Figure 4-3) displays the station’s status and equipment information in
two tables.
An area at the bottom of the tab identifies the switches to which the station is
connected.
Do one of the following to navigate to a connected switch:
• Double-click the switch name.
• Right-click the switch name and choose Navigate to <switch name> from
the context menu.
The switch is selected in the Navigation pane, and its status and equipment
information are displayed in the Information pane.
Equipment Status
The following table describes the Equipment Status grid:
Table 4-1. Equipment Status Display Fields
Field Description
Name The station letterbug assigned during system hardware
definition.
Type Type of hardware specified when the letterbug was
defined. (For example “Windows Server Workstation.”)
IP Address I/A Series station network address.
Switch Connections Number of switches connected to this station.
SMON System monitor domain to which the station is
assigned.
SMON Host Host station for the system monitor.
Run Mode On Line or Off Line. The field 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.
Field Description
Failed State Failed or Not Failed. The field changes from Not
Failed to Failed if either of the following occurs:
• A hardware problem causes the station to fail for
more than two minutes.
• A station hardware failure or communication
failure results in the station not being able to send
its internal reports for one minute or more.
Alarm Enabled Indicates whether alarming is Enabled or Inhibited for
State the station. When alarming is inhibited for a
workstation, the system monitor still updates its status,
but alarm messages are not displayed in System
Manager, and are not logged to the printer or the
historian.
• To inhibit alarming, right-click the station name in
the Navigation pane and choose Inhibit Alarming
from the context menu.
• To enable alarming, right-click the station name in
the Navigation pane and choose Enable Alarming
from the context menu.
Failed Acknowledged or Not Acknowledged. This field
Acknowledged changes from Acknowledged to Not Acknowledged,
State when Failed State changes from Not Failed to Failed.
To return the field to Acknowledged:
• Right-click the station name in the Navigation pane
and choose Acknowledge Station from the context
menu to acknowledge the status change.
Failed Devices Yes, if a peripheral attached to the station is reported as
Attached failed; otherwise, No. To determine which peripherals
are failed:
• Click the Connections tab to list the type, current
status, run mode and failure mode of each
peripheral as described in “Connected Peripherals”
on page 104.
Field Description
Failed Devices Yes or No. This field is initially set to Yes. If an
Acknowledged attached device fails, the field is set to No until the
system alarm from the peripheral is acknowledged.
• Right-click the peripheral in the Navigation pane
and choose Acknowledge Device from the context
menu to acknowledge the failed device.
Server Status Good, Critical or Not Applicable. This status
indicates the overall status of the components that are
residing in Windows Server workstation as shown in
Table 4-2, “Equipment Information Fields,” on
page 97.
Critical if any of the server components listed in
Table 4-2, “Equipment Information Fields,” on page 97
are in failure state.
Good if all the server components listed in Table 4-2,
“Equipment Information Fields,” on page 97 are in
healthy state.
Not Applicable if the workstation is not a Windows
Server.
Equipment Information
The following table describes the fields in the Equipment Information table:
Table 4-2. Equipment Information Fields
Field Description
Reporting State Indicates whether the station is reporting its status to its
system monitor; values can be:
• Reporting All
• No Reporting
• No Counters
• No Information
To change the Reporting State:
• Right-click the station name in the Navigation
Pane and choose Disable All Reports or Enable
All Reports from the context menu.
Cable State Status of cable connections between the workstation
and the switch:
• Both Cables Okay
• Fault
• No Information
Field Description
Station Address A six-octet media access control (MAC) address
assigned during system definition and used by the
networking protocol in the I/A Series stations
Master Timekeeper If GPS is enabled:
Reporting
• GPS Config
• GPS Enabled MTK
• GPS Failed
• GPS Failed MTK
If GPS is not enabled:
• GPS Not Config MTK
• GPS Not Config
Server Model The model of the Windows Server operating system,
for example, PowerEdge 2900.
Field Description
Server Cooling The operational state of the fans located in Windows
Server system is shown as one of the following:
• Good when all the fans are operating.
• Critical when one or more fans are not working.
• Unknown when the health status of the fans is
unknown.
Field Description
Server Memory The status of random-access memory (RAM) which
Device indicates normal, prefailure or failure performance of
the connection or slot for a memory device. The status
of the memory device can be one of the following:
• Good
• Non-critical
• Critical
• Unknown
Field Description
Power 2 The health status of power supply 2 located in Windows
Server system is shown as one of the following:
• Good indicates power supply 2 is operating.
• Non-critical condition indicates the power supply
condition that should be addressed soon or at the
next scheduled maintenance.
• Critical condition means the cable cord of power
supply 2 is unplugged or the power supply is
operating outside of wattage limit which takes the
power supply offline. It requires immediate
attention.
• Unknown/Undefined when the health status of
power supply 2 is unknown or cannot be
determined.
Field Description
Power 4 The health status of power supply 4 located in Windows
Server system is shown as one of the following:
• Good indicates power supply 4 is operating.
• Non-critical condition indicates the power supply
condition that should be addressed soon or at the
next scheduled maintenance.
• Critical condition means the cable cord of power
supply 4 is unplugged or the power supply is
operating outside of wattage limit which takes the
power supply offline. It requires immediate
attention.
• Unknown/Undefined when the health status of
power supply 4 is unknown or cannot be
determined.
Field Description
Cooling Redundant Redundant fan can prevent system shutdown due to fan
State failure.
• Full when all the fans located in Windows Server
system are working.
• Lost when one or more fan is not working.
• Undefined if the redundancy status is not available
for some models of Windows Server systems, such
as, PowerEdge T610.
Note
1. The Microsoft SNMP Service and Server Manager must be installed on the
Windows Server in order to view the status for the fields applicable to
Windows Servers. The Microsoft SNMP Service and Server Manager are
installed during I/A Series V8.6 software installation. For information on
installing V8.6 software, refer to V8.6 Release Notes and Installation
Procedures (B0700SD).
!
Caution The Microsoft SNMP Services are installed on Windows Server
systems running I/A Series V8.6 or later. The services include the SNMP
service and SNMP Trap service. After the installation of I/A Series V8.6 or
later, the SNMP Trap service is disabled and it should not be manually
enabled since the Windows Server system that monitors switches would be
affected.
Connected Peripherals
To access additional information about a workstation’s peripherals:
1. Click the Connections tab to display a table listing the workstation
peripherals by name and type, and showing their status, run mode and
error mode (Figure 4-4).
2. Click any column header in the table to sort the rows on that column; click
the column header a second time to reverse the sort order.
3. Drag a column header to the right or left to change the column order.
4. Do one of the following to navigate to a peripheral:
• Double-click the equipment name.
• Right-click the equipment name and chose Navigate to <equipment
name> from the context menu (Navigate to AKP 1 in Figure 4-4).
The peripheral is selected in the Navigation pane and the General tab in
the Information pane displays status and equipment information tables for
the selected device (Figure 4-6).
Counters Tab
The Counters tab (Figure 4-5) provides statistics on the workstation
performance such as the number of transactions and errors. Counters from the
tab can be added to a watch list that includes counters from other workstations
or other equipment.
To access counters for a workstation:
1. Select the workstation in the Navigation pane and click the Counters tab
in the Information pane.
2. Click the radio button at the top of the page to select the category to be
displayed.
The tab consists of a five-column table with the counter names, current
and previous values, and high and low values. Figure 4-5 is a workstation
Counters tab with the MAC Sublayer category selected.
Buttons in the Counters tab toolbar are used to read and reset values in the
table, and add selected counters to the Watch tab. See “Counters Tab” on
page 44 and “Watch Tab” on page 53 for additional information on using
features of the Counters and Watch tabs, respectively.
Workstations and control stations maintain the same counters, and these are
described in detail in Chapter 6, “Station Counters”
Peripherals Information
When a peripheral is selected, the General tab in the Information pane displays
Equipment Status and Equipment Information tables similar to those for the
annunciator in Figure 4-6 or the printer in Figure 4-7.
Field Description
Equipment Status
Name Device name (letterbug) assigned during hardware
definition
Type Equipment type
Run Mode On Line or Off Line. The status changes to Off Line
when you initiate an EEPROM update, and returns to
On Line when the update is completed.
Failed State Failed or Not Failed
Failed Acknowledged or Not Acknowledged. The field
Acknowledge State changes to Not Acknowledged when Failed State
changes from Not Failed to Failed.
• Right-click the peripheral name in the Navigation
pane and choose Acknowledge Device from the
context menu to acknowledge the failed peripheral.
Alarming State Indicates whether alarming is Enabled or Inhibited for
the peripheral. When alarming is Inhibited for the
device, the system monitor still updates the device
status, but system alarm messages are not sent to
System Manager and are not logged to the printer or the
historian.
Field Description
EEPROM Update EEPROM Updating when the workstation is
State downloading peripheral software; otherwise, Not
Updating
Equipment Information
Release Date Date of the revision level
EEPROM Revision Revision level of the peripheral software image
Hardware Revision Revision level of the hardware
Hardware Part Part number of the peripheral
Panel Slot 1 Type of annunciator in the slot: Annunciator/Keypad,
Annunciator/Numeric Keypad, or Modular Keyboard
Manufacture Date Date the hardware was manufactured
Panel Slot 2 Type of annunciator in the slot: Annunciator/Keypad,
Annunciator/Numeric Keypad, or Modular Keyboard
Panel Slot 3 Type of annunciator in the slot: Annunciator/Keypad,
Annunciator/Numeric Keypad, or Modular Keyboard
Printers
The table layout in Figure 4-7 is used to display status and equipment
information for printers. The data fields are described in the table that follows
the example.
Field Description
Equipment Status
Name Device name (letterbug) assigned during hardware
definition
Type Equipment type
Run Mode On Line or Off Line
Failed State Failed or Not Failed
Failed Acknowledged or Not Acknowledged. The field
Acknowledge State changes to Not Acknowledged when Failed State
changes from Not Failed to Failed.
• Right-click the peripheral name in the Navigation
pane and choose Acknowledge Device from the
context menu to acknowledge the failed peripheral.
Alarming State Indicates whether alarming is Enabled or Inhibited for
the peripheral. When alarming is Inhibited for the
device, the system monitor still updates the device
status, but system alarm messages are not sent to
System Manager and are not logged to the printer or the
historian.
Ready State Ready or Not Ready
Equipment Information
Backup Name 1 Letterbugs of the backup printers
Backup Name 2
Auto Recovery Yes or No indicating whether Auto Recovery is enabled
Lockable Yes or No indicating whether access to the printer can
be restricted
Port Number Port connecting the printer to the workstation
Class Name Type of printer
Peripherals Counters
The Counters tab for printers display the number of messages dropped.
Annunciator and GICO peripherals do not maintain counters.
See “Counters Tab” on page 44 and “Watch Tab” on page 53 for additional
information on using the Counters and Watch tabs, respectively.
Managing Alarms
There are multiple ways to acknowledge alarms associated with a workstation
or one of its peripherals:
• Use the Alarms tab in the Accessories pane to identify and acknowledge
an individual alarm, or acknowledge all alarms (see “Alarms Tab” on
page 49).
• Right-click the workstation in the Navigation pane and choose
Acknowledge Station from the context menu to acknowledge all alarms
for the selected station.
• Right-click the peripheral in the Navigation pane and choose
Acknowledge Device from the context menu to acknowledge an alarm
from the selected device.
• Acknowledge all alarms in the system monitor domain to which the
workstation is assigned by selecting the system monitor in the Navigation
pane and doing one of the following:
• Choose Actions > Acknowledge Smon Domain from the main
menu.
• Click in the toolbar.
• Right-click the system monitor and choose Acknowledge Smon
Domain from the context menu.
You can inhibit all alarms for the workstation or one of its peripherals so that
no alarm conditions are reported to the system monitor.
To inhibit workstation alarms:
1. Right-click the workstation in the Navigation pane.
2. Choose Inhibit Alarming from the context menu.
The workstation is marked with the symbol to indicate that alarms are
being inhibited.
To inhibit alarms from one of the station’s peripherals:
1. Right-click the peripheral in the Navigation pane.
2. Choose Inhibit Device Alarming from the context menu.
The peripheral’s icon is marked with the symbol to indicate that alarms
are being inhibited.
To re-enable the alarms:
1. Right-click the peripheral in the Navigation pane.
2. Choose the appropriate command from the context menu:
Enable Alarming
Enable Device Alarming
Note Disabling reports is not recommended unless you need to reduce traffic
on the network to diagnose a problem.
C H A P T E R 5
This chapter describes how to use System Manager software to monitor control
stations and perform equipment change actions.
Note The examples used in this chapter involve the Field Control Processor
270 (FCP270) and Z-Module Control Processor 270 (ZCP270).
Contents
• Identification of Control Stations, ATSs, and LIs
• Station Information for Control Processors and ATSs
• Station Information for LI
• Connected FBMs
• Control Station, ATS, and LI Counters
• Primary ECB (Primary FBM) Information
• Equipment Change Actions
This Primary ECB can be selected to view additional information about the
control station and perform equipment change actions that affect the FBMs and
the Fieldbus communications.
Non-fault-tolerant FCP270
in a normal operating state
Primary ECB for FCP805
Non-fault-tolerant ZCP270 in
the normal operating state
Primary ECB for ZCP711
Labels attached to the control station or ATS icon indicate the state of
communications with its attached field devices and with switches in the
network:
Table 5-1. Equipment Status Indicators for CP and ATS
Symbol Condition
The lightning symbol to the left of the station icon indicates
that there is a cable fault with at least one of the field devices
attached to the station.
This symbol is not shown until the station node in the
Navigation pane is expanded for the first time in the session so
that System Manager retrieves the identity and status of the
attached devices.
The lightning symbol on the top right of the CP/ATS indicates
that there is a failure in Cable A.
Symbol Condition
The CP with the symbol on the bottom right indicates
that the station has devices attached to the single cable (that is,
ThinNet).
The red outline around an ATS letterbug indicates that there is:
• A communication fault on the Nodebus cable
• A communication fault with connected station or FBM
(indicates the communication fault path)
Symbol Condition
When the station is an FCP270, CP30, or CP40, a label at the
upper right corner of the block indicates which channel in the
module fieldbus is being used to communicate with the
station’s FBMs.
Failure in
Nodebus
ATS alarms Cable A
are inhibited
Communication
fault exists underneath
Cable alarms ATS
are inhibited
for Nodebus Station transmitter/receiver
Cable B cable alarms are
inhibited for
Nodebus Cable A
Failed station
receiver on
Nodebus Cable A
Labels attached to the LI icon indicate the state of communications with its
attached equipment.
Symbol Condition
The lightning symbol on the top right of the LAN Interface
station indicates that there is a failure in Cable A on the
Nodebus or Carrierband LAN.
Symbol Condition
• For Carrierband LAN, the symbol at the top right corner
indicates the failed Transmitter A in the primary module
on the LAN side of the LI.
• For the Nodebus, the symbol at the top right corner
indicates a failed station transmitter on Nodebus Cable A.
The symbol on the right side of the LI icon represents a
possible Drop Cable A fault.
For more information on the type of fault and where the fault
has occurred (either on the Carrierband LAN, the Nodebus, or
both simultaneously), go to the LI’s Equipment Information
pane and refer to the Faults group (Figure 5-7).
• For Carrierband LAN, the symbol at the middle right
indicates the failed Transmitter B in the primary module
on the LAN side of the LI.
• For the Nodebus, this symbol at the middle right indicates
a failed station transmitter on Nodebus Cable B.
The symbol on the right side of the LI icon represents a
possible Drop Cable B fault.
For more information on the type of fault and where the fault
has occurred (either on the Carrierband LAN, the Nodebus, or
both simultaneously), go to the LI’s Equipment Information
pane and refer to the Faults group (Figure 5-7).
The LAN Interface station with symbol indicates that
station transmitter/receiver cable alarms are inhibited for
Nodebus Cable A.
Symbol Condition
The LAN Interface station with symbol on top left
indicates that the cable alarms are inhibited for Carrierband
LAN A.
Failed Cable A
on Carrierband LAN
LI station transmitter/
receiver cable alarms Communication
are inhibited for fault exists
Carrierband LAN underneath LI
station
Alarms from
LI station
are inhibited
Failed station
receiver on
Nodebus Cable B
Station transmitter/
receiver cable alarms
are inhibited for
Nodebus Cable B
* For more information on the type of fault and where the fault has occurred
(either on the Carrierband LAN, the Nodebus, or both), go to the LI’s
Equipment Information pane and refer to the Faults group Figure 5-7.
The area at the bottom of the pane displays the switches to which the station is
connected.
Do one of the following to navigate to a connected switch:
• Double-click the switch name.
• Right-click the switch name and choose Navigate to <switch name> from
the context menu.
The switch is selected in the Navigation pane, and its status and equipment
information are displayed in the Information pane.
Equipment Status
Field Description
Name The station letterbug assigned during system hardware
definition
Type Type of hardware specified when the letterbug was
defined
Boot Host Host station for the CP/ATS
SMON System monitor domain to which the station is assigned
SMON Host Host station for the system monitor
IP Address I/A Series station network address
Switch Number of switches connected to this station
Connections
Fault Tolerant Yes or No. Indicates whether the station is fault-tolerant.
Fault Tolerant State Operational or Non-Operational for fault-tolerant
controllers only. Fault Tolerant State indicates Non-
Operational if the shadow module is not installed or
configured.
Redundant State Operational or Non-Operational for redundant ATSs
only. Fault Tolerant State indicates Non-Operational if
the shadow module is not installed or configured.
Run Mode On Line or Off Line. This field is initially Off Line, but
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 Failed State are separate, but related
fields. 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
occurs:
• Reboot of the station
• Image update
• Power failure
• Any station hardware failure or communication
failure that results in the station not being able to
send its internal reports for one minute or more.
For fault-tolerant stations, refer to the Primary Mode
and Shadow Mode fields for the current Run Mode of
each module in the pair.
Field Description
Failed State Failed or Not Failed. This field changes from Not
Failed to Failed if any of the following occurs:
• A hardware problem causes the station to fail for
more than two minutes.
• A physical pull/push of the module is performed to
reboot the station, and the station requires more
than two minutes to come back on-line.
• Any station hardware failure or communication
failure that results in the station not being able to
send its internal reports for one minute or more.
For fault-tolerant stations, refer to the Primary Mode
and Shadow Mode fields for the current Fail State of
each module.
Alarming State Indicates whether alarming is Enabled or Inhibited for
the device. When alarming is Inhibited for a station, the
system monitor still updates the control station’s status,
but faults do not result in system alarm messages.
• To inhibit alarming, right-click the station name in
the Navigation pane and choose Inhibit Alarming
from the context menu.
• To enable alarming, right-click the station name in
the Navigation pane and choose Enable Alarming
from the context menu.
Failed Acknowledged or Not Acknowledged. If the Failed
Acknowledged State changes from Not Failed to Failed, the Failed
State Acknowledged State field changes to Not
Acknowledged to indicate this transition. To
acknowledge the failed state:
• Right-click the station in the Navigation pane and
choose Acknowledge Station from the context
menu.
Failed Devices Yes if one or more Fieldbus devices attached to the
Attached station are reported as failed; otherwise, No
Failed Devices Yes or No. If any of the attached devices becomes
Acknowledged unacknowledged, the field changes from Yes to No. Do
one of the following to acknowledge the failed
equipment:
• Use the Connections tab to identify the failed
device, right-click the equipment in the Navigation
pane, and choose Acknowledge Device from the
context menu.
• Use the Alarms tab in the Accessories pane to
identify and acknowledge the alarm.
Field Description
Image/EEPROM Image Updating or EEPROM Updating (for classic
Update State stations) when the station’s operating software image is
being updated; otherwise, Not Updating. For fault-
tolerant stations, refer to the Primary Mode and Shadow
Mode fields for the current Image Updating State.
Download State Downloading when the station is rebooted via an
operator-initiated request; otherwise, Not
Downloading.
For fault-tolerant stations, refer to the Primary Mode
and Shadow Mode fields for the current Download
State.
Diagnostics State Active for a non-fault-tolerant station that is off-line;
otherwise, Not Active
Equipment Information
Field Description
Reporting State Status of the station’s reporting to the system monitor
is shown as one of the following:
• Report All
• No Reporting
• No Counters
• No Information
To change the Reporting State:
• Right-click on the station name in the Navigation
Pane and choose Disable All Reporting or
Enable All Reporting from the context menu.
Master Timekeeper Indicates the status of UTC and time strobe from the
Reporting system timekeeper
(STK), as received by the station. If STK
synchronization (STK SYN) is enabled, the status can
be:
• Pulsed STK: Receiving UTC time from MTK
and time strobe from both ports A and B.
• 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.
If STK SYN is not enabled, the status can be either
AB Fail Not Config or Sync Not Config.
Station Address A six-octet media access control (MAC) address
assigned during system definition and used by the
networking protocol in the I/A Series stations
Cable State The state of communications between the control
station and the attached field devices is reported as:
• Both Cables Okay
• Fault
• No Information
Field Description
Primary Mode Shows the mode of the Primary module:
• Single Primary when the station is a non-
redundant station and it is on-line
• Married Primary for the primary module in a
redundant pair that is operating normally
• Image Updating when the primary station
software image is being updated
• Off Line
• Downloading when the control database is being
downloaded to the primary station
• Failed
• No Information
Primary ROM A six-octet MAC address of the Primary controller
Address assigned during manufacturing. The last six characters
of this address are the module hardware ID which is
stamped on a label on the module’s outer cover.
Primary Hardware Part number for a non-fault-tolerant station or for the
Part Number Primary module in a fault-tolerant pair
Primary Hardware Revision level of the hardware for a non-fault-tolerant
Revision station or of the Primary module hardware in a fault-
tolerant pair
Primary Hardware Manufacturing date of the hardware for a non-fault-
Date tolerant station or of the Primary module hardware in
a fault-tolerant pair
Primary Image Revision number for the operating software image in a
Revision non-fault-tolerant station or in the Primary module
hardware in a fault-tolerant pair
Shadow parameters are only shown for fault-tolerant stations.
(“Backup” is used in place of “Shadow” when referring to a redundant
ATS.)
Shadow Mode • Married Shadow for the shadow module in a
redundant pair that is operating normally
• Image Updating when the software for a shadow
station in a redundant pair is being updated
• Downloading when the control database is being
downloaded to the shadow station
• Diags Active when the station is performing
Offline Diagnostics
• Off Line
• Failed
• No Information
Field Description
Shadow ROM A six-octet MAC address of the Shadow controller
Address assigned during manufacturing. The last six characters
of this address are the module hardware ID which is
stamped on a label on the module’s outer cover.
Shadow Hardware Part number for the Shadow module.
Part Number
Shadow Hardware Revision level of the Shadow module hardware.
Revision
Shadow Hardware Manufacturing date of the Shadow module hardware.
Date
Shadow Image Revision number for the operating software image in
Revision the Shadow module hardware.
The Faults area at the bottom of the pane describes Nodebus and Carrierband
LAN faults. Because the symbols in the LAN Interface view can represent a
cable fault on the Carrierband LAN, the Nodebus, or on both simultaneously,
the General tab displays a Faults group.
The left table under the Faults group displays Nodebus cable faults, and the
right table displays Carrierband LAN faults.
Equipment Status
Field Description
Name The station letterbug assigned during system hardware
definition
Type Type of hardware specified when the letterbug was
defined
Field Description
Boot Host Host station for the LI
LI Name LI’s logical name
SMON System monitor domain to which the station is assigned
SMON Host Host station for the system monitor
Fault Tolerant Yes or No. Indicates whether the station is fault-tolerant.
Fault Tolerant State Operational or Non-Operational for fault-tolerant LIs
only. Fault Tolerant State indicates Non-Operational if
the shadow module is not installed or configured.
Run Mode On Line or Off Line. This field is initially Off Line, but
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 Failed State are separate, but related
fields. 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
occurs:
• Reboot of the station
• Image update
• Power failure
• Any station hardware failure or communication
failure that results in the station not being able to
send its internal reports for one minute or more.
For fault-tolerant stations, refer to the Primary Mode
and Shadow Mode fields for the current Run Mode of
each module in the pair.
Failed State Failed or Not Failed. This field changes from Not
Failed to Failed if any of the following occurs:
• A hardware problem causes the station to fail for
more than two minutes.
• A physical pull/push of the module is performed to
reboot the station, and the station requires more
than two minutes to come back on-line.
• Any station hardware failure or communication
failure that results in the station not being able to
send its internal reports for one minute or more.
For fault-tolerant stations, refer to the Primary Mode
and Shadow Mode fields for the current Fail State of
each module.
Field Description
Alarm Enabled Indicates whether alarming is Enabled or Inhibited for
State the device. When alarming is Inhibited for a station, the
system monitor still updates the control station’s status,
but faults do not result in system alarm messages.
• To inhibit alarming, right-click the station name in
the Navigation pane and choose Inhibit Alarming
from the context menu.
• To enable alarming, right-click the station name in
the Navigation pane and choose Enable Alarming
from the context menu.
Failed Acknowledged or Not Acknowledged. If the Failed
Acknowledged State changes from Not Failed to Failed, the Failed
State Acknowledged State field changes to Not
Acknowledged to indicate this transition. To
acknowledge the failed state:
• Right-click the station in the Navigation pane and
choose Acknowledge Station from the context
menu.
Failed Devices Yes if one or more Fieldbus devices attached to the
Attached station are reported as failed; otherwise, No
Failed Devices Yes or No. If any of the attached devices becomes
Acknowledged unacknowledged, the field changes from Yes to No. Do
one of the following to acknowledge the failed
equipment:
• Use the Connections tab to identify the failed
device, right-click the equipment in the Navigation
pane, and choose Acknowledge Device from the
context menu.
• Use the Alarms tab in the Accessories pane to
identify and acknowledge the alarm.
EEPROM Update EEPROM Updating (for classic stations) when the
State station’s operating software image is being updated;
otherwise, Not Updating. For fault-tolerant stations,
refer to the Primary Mode and Shadow Mode fields for
the current EEPROM Update State.
Download State Downloading when the station is rebooted via an
operator-initiated request; otherwise, Not
Downloading.
For fault-tolerant stations, refer to the Primary Mode
and Shadow Mode fields for the current Download
State.
Diagnostics State Active for a non-fault-tolerant station that is off-line;
otherwise, Not Active
Equipment Information
Field Description
Reporting State Status of the station’s reporting to the system monitor
is shown as one of the following:
• Report All
• No Reporting
• No Counters
• No Information
To change the Reporting State:
• Right-click on the station name in the Navigation
Pane and choose Disable All Reporting or
Enable All Reporting from the context menu.
Master Timekeeper Indicates the status of UTC and time strobe from the
Reporting system timekeeper
(STK), as received by the station. If STK
synchronization (STK SYN) is enabled, the status can
be:
• Pulsed STK: Receiving UTC time from MTK
and time strobe from both ports A and B.
• 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.
If STK SYN is not enabled, the status can be either
AB Fail Not Config or Sync Not Config.
Station Address A six-octet media access control (MAC) address
assigned during system definition and used by the
networking protocol in the I/A Series stations
Field Description
Primary Mode Shows the mode of the Primary module:
• Single Primary when the station is a non-
redundant station and it is on-line
• Married Primary for the primary module in a
redundant pair that is operating normally
• Image Updating when the primary station
software image is being updated
• Off Line
• Downloading when the control database is being
downloaded to the primary station
• Failed
• No Information
Primary ROM A six-octet MAC address of the Primary controller
Address assigned during manufacturing. The last six characters
of this address are the module hardware ID which is
stamped on a label on the module’s outer cover.
Primary Hardware Part number for a non-fault-tolerant station or for the
Part Number Primary module in a fault-tolerant pair
Primary Hardware Revision level of the hardware for a non-fault-tolerant
Revision station or of the Primary module hardware in a fault-
tolerant pair
Primary Hardware Manufacturing date of the hardware for a non-fault-
Date tolerant station or of the Primary module hardware in
a fault-tolerant pair
Primary EEPROM Revision number for the operating software image in a
Revision non-fault-tolerant station or in the Primary module
hardware in a fault-tolerant pair
Shadow parameters are only shown for fault-tolerant stations.
Shadow Mode • Married Shadow for the shadow module in a
redundant pair that is operating normally
• Image Updating when the software for a shadow
station in a redundant pair is being updated
• Downloading when the control database is being
downloaded to the shadow station
• Diags Active when the station is performing
Offline Diagnostics
• Off Line
• Failed
• No Information
Field Description
Shadow ROM A six-octet MAC address of the Shadow controller
Address assigned during manufacturing. The last six characters
of this address are the module hardware ID which is
stamped on a label on the module’s outer cover.
Shadow Hardware Part number for the Shadow module.
Part Number
Shadow Hardware Revision level of the Shadow module hardware.
Revision
Shadow Hardware Manufacturing date of the Shadow module hardware.
Date
Shadow Image Revision number for the operating software image in
Revision the Shadow module hardware.
Faults
The Faults tables give additional information about the symbols associated
with the LI in the navigation pane. For example, if an LI had an icon with the
symbols , you can look at the faults table for more information on where
the faults have occurred, either in the Carrierband LAN, the Nodebus, or both.
By looking at the Faults tables in Figure 5-8, you can determine that there is a
Connected FBMs
To display a list of the Fieldbus devices attached to a control station:
1. Select the station in the Navigation pane and click the Connections tab in
the Information pane.
For a control processor, the Connections tab lists the attached field devices
by name, type, status, run mode, and failure mode (Figure 5-9). The tab
lists the Primary ECB, the attached FCMs (if the station is a ZCP270 or
CP60) and the connected FBMs. The Connections tab can also be selected
from the Primary ECB, in which case it lists the attached FCMs and
FBMs.
For an ATS or LAN Interface module, the Connections tab lists the CP30,
CP40, or CP60 and the workstation that resides on the particular network.
ats_connection_tab
2. Click any column header to sort the rows on the values in that column;
click the column header a second time to reverse the sort order.
3. Drag a column header to the right or left to change the column order.
4. Double-click a device name, or right-click the name and choose
Navigate to <Name> to go to the selected FCM or FBM (Navigate to
FCP704 in Figure 5-9).
The device is selected in the Navigation pane and its information is
displayed in the Information pane. If there are devices connected to the
FCM or FBM, the Connections tab is shown in the Information pane;
otherwise, the General tab is displayed.
Buttons in the Counters tab toolbar are used to read and reset values in the
table, and add selected counters to the Watch tab. See “Counters Tab” on
page 44 and “Watch Tab” on page 53 for additional information on using
features of the Counters and Watch tabs, respectively.
Control stations and workstations maintain the same counters, and these are
described in detail in Chapter 6, “Station Counters”.
Note When a station status is off-line, the primary ECB, any attached FCMs
(if station is a ZCP270 or CP60), and connected FBMs and devices will be
removed from station hierarchy and will be restored once the station has
returned to an on-line status.
Field Description
Name Same as the name of the control station. The Primary
ECB does not have its own letterbug designation.
Type Always FBM0
Run Mode On Line or Off Line. The primary ECB is installed
as On Line after it is “fixed” and configured.
Changing the Primary ECB status to Off Line causes
all communication to the Ethernet Fieldbus or
module Fieldbus to stop. All attached FBMs and
FCMs go off-line.
Refer to “Go Off-Line/Go On-Line” on page 161 for
additional information.
Device State Failed or Not Failed
Field Description
Alarming State Enabled or Inhibited. When alarms are inhibited,
Primary ECB failures do not result in system alarms.
To change Alarming State:
• Right-click the Primary ECB in the Navigation
pane and choose Enable Device Alarming or
Inhibit Device Alarming from the context
menu.
Failed Acknowledge Acknowledged or Not Acknowledged. The field
State changes to Not Acknowledged when Device State
transitions to Failed.
Periodic Switch Enabled or Not Enabled. When Enabled, automatic
switching between Bus A and B occurs periodically.
Active PIO Bus On an FCP270, the module fieldbus being used by
the control station to communicate with the attached
FBMs. On a ZCP270, the Ethernet fieldbus cable
being used to communicate with the attached FCMs.
• Bus A when bus A has been selected by an
operator
• Bus B when bus B has been selected by an
operator
• Bus A & B Auto when Switching Mode is
enabled
See “Ethernet and Module Fieldbus Switching
Actions” on page 162 for additional information.
The following fields are only displayed for an FCP270 Primary ECB:
CP Power 1 Status of the control station’s primary power cable is
either Ok or Failed
CP Power 2 Status of the control station’s secondary power cable
is either Ok or Failed
The following fields are only displayed for a CP30, CP40, CP60, or ZCP270
Primary ECB:
Switching Mode Automated switching for the Ethernet fieldbus is
either Enabled or Not Enabled
Periodic Config Yes if Periodic Switching has been enabled by an
operator; otherwise, No
The following fields are only displayed for a ZCP270 Primary ECB:
Field Bus A Status of the A fieldbus cable connecting the control
station and the FCMs is either OK or Failed
Field Bus B Status of the B fieldbus cable connecting the control
station and the FCMs is either OK or Failed
Field Description
Diag Status 1 through Hexadecimal values relating to the status of the FBM.
Diag Status 4 If the module is operating properly, these values can
be safely ignored. If there are hardware and software
errors, these values will assist the Global Customer
Support Center (CSC) in resolving the problem.
Primary Cmd Status Value indicating health of communications with the
FBMs and FCMs:
0x0 Normal
0x1 Success with retry
0x3 The control station has timed out the FBM
>0x3: Link level protocol error
FBM Status [not used]
Self Hosting Enabled or Not Enabled. This field is set to Enabled
when the FCP270 or ZCP270 controller is in self-
hosting mode, and Not Enabled when the controller is
not in self-hosting mode.
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; a host
workstation is only required when changing the
system configuration or the controller image.
To enable self-hosting in an FCP270 or ZCP270, use
your 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 Station block parameter.
When a checkpoint is performed on a FCP270 or
ZCP270, the selected station’s database is saved in a
checkpoint file on the host file server and Bit 8 of the
CFGOPT parameter is evaluated to determine the
controller’s mode of operation.
• If the FCP270 or ZCP270 is not currently in self-
hosting mode and was not in self-hosting mode
prior to the Checkpoint command being issued,
the checkpoint is complete.
• If the FCP270 or ZCP270 is in self-hosting mode,
the controller requests a copy of the checkpoint
file from the download server. This file is then
copied (burned) into the control station’s flash
memory.
Field Description
Logical Address Address used by the control station to communicate
with FBMs and FCMs. The Primary ECB is always
0xFF.
Primary Check Point Field used to display the number of times the primary
Shadow Check Point or shadow FCP270 or ZCP270 module’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 additional information on self-
hosting.
Counter Description
Timeouts Number of times the primary ECB timed out an FBM
during communication attempts.
Inval Cmnd Number of commands received by the primary ECB
that were invalid in the present state of the station.
Inval Resp Number of invalid messages received by the primary
ECB from an FBM.
See “Counters Tab” on page 44 and “Watch Tab” on page 53 for additional
information on using the Counters and Watch tabs, respectively.
Inhibit
You can inhibit alarms for the control station so that no alarm conditions are
reported to the system monitor.
To inhibit station alarms:
• Right-click the station in the Navigation pane and choose Inhibit
Alarming from the context menu.
Any unacknowledged alarms are acknowledged, and the station is marked
with the symbol to indicate that alarms are being inhibited.
To re-enable alarms:
• Right-click the inhibited equipment in the Navigation pane and choose
Enable Alarming from the context menu.
Note Disabling reports is not recommended unless you need to reduce traffic
on the network to diagnose a problem.
If you have disabled all reports and an FBM is deleted using ICC, the FBM
icon will still appear in System Manager displays.
When you re-enable reporting, expand the station node in the Navigation pane
so that System Manager retrieves status and equipment information for the
connected devices.
Checkpointing
Checkpointing copies the control database in the control station to the boot
host checkpoint file. Use the checkpoint command to save current controller
tuning before you reboot the station to resolve system maintenance issues.
If the control station is in self-hosting mode, the control station obtains the
current checkpoint file from its flash memory when the station restarts. If the
control station is not in self-hosting mode (default), the control station
downloads the current checkpoint file from the boot host. (Refer to Field
Control Processor 270 (FCP270) User’s Guide (B0700AR) and Z-Module
Control Processor 270 (ZCP270) User’s Guide (B0700AN) for information on
CP270 self-hosting mode.
Checkpoint saves the following control station changes to the checkpoint file:
• Control database configuration changes
• Tuning changes made through the process displays
• FBM status changes made outside System Manager
To save recent control processor changes to the checkpoint file:
1. Right-click the station and choose Checkpoint from the context menu.
2. Enter the reason for the checkpointing and click OK in the confirmation
dialog box (Figure 5-14) if these actions settings are configured (see
“Action Settings” on page 64).
Reboot
The Reboot action restarts the selected control station and reloads the station’s
control database from a file server. While a station is rebooting, it is off-line
until the reboot is complete; this suspends any access to the station database.
3. Make an entry in the Reason field if the field is included in the dialog box.
The Reason Required action setting is set in the Configuration dialog box
(see “Action Settings” on page 64).
4. Select one or both modules, and click OK.
5. Review the messages in the Accessories pane or the status bar to verify
that the reboot was completed successfully.
To reboot a non-fault-tolerant station:
1. Right-click the station in the Navigation pane, and choose Enable
Download if the command is listed in the context menu.
2. Right-click the station in the Navigation pane, and choose Reboot from
the context menu.
A dialog box is displayed if confirmation is required.
• Make an entry in the Reason field if the field is included in the dialog
box, and click OK.
3. Review the messages in the Accessories pane or the status bar to verify
that the reboot was completed successfully.
Image Update
The Image Update action updates the operating system software in the selected
station. The action downloads a file and burns a new image to flash memory.
During the update, the station is off-line and access to the database for that
station is suspended.
Note Although Image Update is available for both fault-tolerant and non-
fault-tolerant stations, use On-Line Image update instead on fault-tolerant
stations to minimize hold-control time.
EEPROM Update
The EEPROM Update action updates the firmware in a selected classic station
such as an LI, CP30, CP40, or CP60, etc. with new EEPROM firmware. The
update downloads a file, burns a new EEPROM, and reboots the system.
During the update, the station is off-line and access to the database for that
station is suspended.
Update the station’s EEPROM to implement an official Invensys software
release or to resolve a maintenance issue.
To update existing EEPROM station firmware:
1. Right-click the station and choose Checkpoint from the context menu to
ensure that all changes to the control database are recorded in the host
server.
2. Right-click the station and choose Enable Download if the action appears
in the context menu.
3. Right-click the station and choose EEPROM Update from the context
menu.
With a fault-tolerant station, the station places the Shadow module off-line
and then downloads and burns the new image in the Primary module.
After verification, the Primary reboots automatically. When the Primary
finishes rebooting, it sends the new firmware to the Shadow. The Shadow
reboots and the module pair marries using the new firmware.
4. While the EEPROM update processes, the system sends standard update
progress messages to the printer.
Upon completion of the EEPROM update, the station reboots.
Note Both cables connecting the control modules to the network must be
attached and functional to perform an on-line image update, as one module
must continue using the A cable for control while the other is using the B cable
for downloading the new image.
Note In conjunction with the Warm Start option, the control loops in the
control station can be configured to initialize bumplessly by reading back
the current output values and performing an upstream initialization of the
blocks in the control loop.
The fault-tolerant pair goes single, and the Primary module downloads the
image from the host (messages are sent to the system printer to indicate
progress) and passes the image to the Shadow module.
The Shadow module updates its flash memory with the new image and
reboots. The Primary module performs a checkpoint of the database and
turns off the B cable. When complete, the Primary module tells the
Shadow module (with the new image) to perform a database download.
The Shadow module downloads the database on the B cable and then
assumes control via a role switch.
5. Evaluate the station operation under the new software, and perform one of
the following steps:
If you are satisfied with the behavior of the station:
• Right-click the control station in Navigation pane, choose Reboot
from the context menu and select the Shadow module in the Reboot
dialog box.
This completes the update process by implementing the new image in the
pair.
If you do not want to continue running with the new software image:
• Right-click the control station in Navigation pane, choose Reboot
from the context menu and select the Primary module in the Reboot
dialog box.
This causes the module running the old software image to reboot,
download the database, and then assume control. The other module that
was running the new image relinquishes control, reboots, then copies the
old image from the running module, re-burns the image, and reboots
again. The end result is that the modules resume fault-tolerant operation
running the old software image.
When a station is rebooted due to a software failure, the system uploads the
station image to a local file on the boot host workstation. You can permit or
prohibit the system from uploading this image when the station fails under
certain conditions.
To enable uploading:
• Right-click the station and choose Enable Upload if it is listed in the
context menu.
To disable uploading:
• Right-click the station and choose Disable Upload if it is listed in the
context menu.
If the Enable Upload or Disable Upload actions fail, do the following:
• Check the boot host for the station.
• Make sure no other workstations are running the CIO configurator for the
station.
• Make sure no other workstations are executing equipment change actions
for the station using System Manager.
Offline Diagnostics
The Offline Diagnostic tests are used to verify proper operation of the station
components. Offline diagnostic tests are station specific; when Offline
Diagnostics appears for a selected station, the menu shows only those tests
available for that station.
Offline Diagnostics are applicable to FCP270, ZCP270, ATS, LI, and classic
stations. For classic stations, offline diagnostics can be performed locally
(across the Nodebus) and remotely (across the Carrierband LAN or fiber optic
LAN).
2. Type an entry in the Reason field if the field is included in the dialog box.
3. Select the module to be taken off-line and click OK.
The selected module goes off-line, and its status changes to Diagnostics
Active. The status of the other module changes to Single Primary.
4. Right-click the station a second time and choose Offline Diagnostics. The
submenu for Offline Diagnostics can differ depending on the station type.
5. Choose Execute Tests to run the diagnostic test, Restart to reboot the
station, or Fail to mark the station as failed. Refer to “Performing Offline
Diagnostics” on page 151.
To perform Offline Diagnostics with a non-fault-tolerant control station:
1. Right-click the control station and choose Offline Diagnostics from the
context menu.
A dialog box prompts you to confirm the action if Confirmation Required
is checked in the Configuration dialog box. Type an entry in the Reason
field if the field is included in the dialog box, and click OK to take the
station off-line.
singleCP_offlineDiag.bmp
2. Execute the selected tests. Click Execute All, Execute Once, or Execute
Loop, as described in Table 5-9.
Table 5-9. Offline Diagnostics Test Execution Options
Button Description
Execute All Click Execute All to perform all the tests shown
in the Offline Diagnostics dialog box.
Execute Once Select the desired test(s) and click Execute Once
to perform each selected test one time.
Execute Loop Select the desired test(s) and click Execute Loop
to perform each selected test continuously. The
Execute Loop button changes to a Halt button,
and the tests will continue executing until you
click Halt in the Offline Diagnostics dialog box.
Figure 5-21. Offline Diagnostics Dialog Box for CP60 Showing the Halt
Option
The system runs the selected tests as designated. The Offline Diagnostics
results appear, showing the tests results of each as it completes. The result
count section on the Offline Diagnostics dialog box shows the total number of
tests passed and the total number of tests failed.
Result Description
Pass Indicates that the station passed the diagnostics
test(s).
Fail When shown in red text, it indicates that the
station failed the diagnostics test.
No Response Indicates that the station is not responding to the
test execution request.
After performing the Offline Diagnostics test(s), you can restart or set the
station to fail.
Devices Tests
Control processors:- DB XFER
CP30 style-B/CP30FT LETTERBUG
style-B, CP40 style- FBM PORT
B/CP40FT style-B, MATH TEST
CP60/CP60FT NB INT LBK
NB JABBER
NB PCS
STATE SEQ
A-B Integrator 30B, I/O PROCES
INTERSPEC Integrator LETTERBUG
(IS30) 80387 TEST
Carrier band LAN LETTERBUG
Interface
Devices Tests
Comm Processor 10 LETTERBUG
ASYNC LPBK
M/P/M TST
SCC RD/WRT
DMA WRITE
Applic Proc 10 LETTERBUG
DMA WRITE
SER R LOOP
SER P LOOP
FLOPY READ
SCSI RD/WR
CLNDR CLK
Applic Proc 20 LETTERBUG
CLNDR CLK
ADMA DMA
MEM DMA
SCSI TESTS
Spect Slave Gateway LETTERBUG
8087 TEST
NODEBS COM
CLNDR CLK
PORT TEST
DMA TEST
ADMA DMA
SSG MAIN
SSG SEC
Wrksta Processor 20, LETTERBUG
WP20 - Japanized GE KERNEL
8087 TEST
SHARED RAM
REG TEST
INTR LOGIC
I/O PORT
PLANE MASK
PIXEL MASK
Display Panel, PW for LETTERBUG
Hydrostatic Sys I/O PORT
NODEBS COM
8087 TEST
Modbus Plus Integrator LETTERBUG
80387 TEST
Online Diagnostics
Online Diagnostics enables you to perform on-line diagnostic tests specific to a
selected network.
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.
You can use Online Diagnostics to test Carrierband LAN cables and the
Nodebus cables on-line.
You can perform on-line diagnostics for Carrierband LAN operations as listed
in Table 5-12.
Function Definition
Run Cable Test Runs the carrierband cable test.
Current Test Initiator Shows the current carrierband test initiator.
Set As Test Initiator Set the current selected LI station as carrierband
test initiator.
Function Definition
Enable/Inhibit Allows/Inhibits reporting of carrierband LAN
Carrierband Cable A Cable A alarms.
Alarms
Enable/Inhibit Allows/Inhibits reporting of carrierband LAN
Carrierband Cable B Cable B alarms.
Alarms
Enable/Inhibit Allows/Inhibits reporting of the selected
Carrierband Cable A transmitter/receiver alarms of Cable A for the
Station TxRx Alarms selected station on the carrierband.
Enable/Inhibit Allows/Inhibits reporting of the selected
Carrierband Cable B transmitter/receiver alarms of Cable B for the
Station TxRx Alarms selected station on the carrierband.
Enable/Inhibit Entire Allows/Inhibits reporting of all the equipment on
Nodebus and Cable A the selected LI station, and nodebus Cable A
Alarms alarms.
Enable/Inhibit Entire Allows/Inhibits reporting of all the equipment on
Nodebus and Cable B the selected LI station, and nodebus Cable B
Alarms alarms.
When you select the Set As Test Initiator from either the Actions menu or the
context menu for an LI station, a confirmation dialog box appears (Figure 5-
23).
Click the Detail button to show or hide the current messages. The most recent
message is at the top of the message display area.
Diagnostics window in the order of occurrence, that is, the most recent
message will be shown on the top level.
On-line diagnostics test results will be directed to the configured fault
notification printer. The System Manager Navigation pane will be updated
with appropriate icons to represent the cable test results. The system will send
the cable test results to all workstations only if the cable test fails. If any of the
station involved in the cable test is in failed state, appropriate error messages
will be appended to the Message pane.
Function Definition
Enable/Inhibit Nodebus Cable A Allows/disallows reporting of nodebus
Alarms LAN Cable A alarms.
Enable/Inhibit Nodebus Cable B Allows/disallows reporting of nodebus
Alarms LAN Cable B alarms.
Function Definition
Enable/Inhibit Nodebus Cable A Allows/disallows reporting of the
Station TxRx Alarms selected transmitter/receiver alarms of
Cable A for the selected station on the
nodebus.
Enable/Inhibit Nodebus Cable B Allows/disallows reporting of the
Station TxRx Alarms selected transmitter/receiver alarms of
Cable B for the selected station on the
nodebus.
Enable/Inhibit Entire Nodebus Allows/disallows reporting of all the
and Cable A Alarms equipment on the selected LI nodebus
station, its PIO bus (if any), and nodebus
Cable A alarms.
Enable/Inhibit Entire Nodebus Allows/disallows reporting of all the
and Cable B Alarms equipment on the selected LI nodebus
station, its PIO bus (if any), and nodebus
Cable B alarms.
The following equipment change actions are available when the Primary ECB
for other classic stations is selected:
• Inhibit Device Alarming or Enable Device Alarming
• Go Off-Line or Go On-Line
• General Download
• Periodic PIO Bus Switch
• Bus A Enable Switching or Bus A Disable Switching
• Bus B Enable Switching or Bus B Disable Switching
• Inhibit PIO Bus A
• Inhibit PIO Bus B
Managing Alarms
From the Primary ECB, you can inhibit all alarms for the Primary ECB so that
no alarm conditions are reported to the system monitor. When the station is an
FCP270, you can also inhibit all cable alarms on either or both module fieldbus
channels connecting the station to the field devices. When the station is
ZCP270, inhibiting and enabling cable alarms are initiated from the FCMs
(refer to “Cable Alarms” on page 186).
To inhibit device alarms:
• Right-click the Primary ECB in the Navigation pane and choose Inhibit
Device Alarming from the context menu.
The Primary ECB is marked with the symbol to indicate that alarms
are being inhibited.
To inhibit cable alarms for the FBMs attached to an FCP270:
• Right-click the Primary ECB and choose Inhibit PIO Bus Cable A
Alarms or Inhibit PIO Bus Cable B Alarms from the context menu.
A symbol ( , or ) attached to lower right corner of each FBM
icon indicates which cables have alarms inhibited.
To re-enable the alarms:
• Right-click the Primary ECB in the Navigation pane and choose the
appropriate command from the context menu.
Enable Device Alarming
Enable PIO Bus Cable A Alarms
Enable PIO Bus Cable B Alarms
Go Off-Line/Go On-Line
The Go Off-Line action takes all Fieldbus devices attached to the station off-
line. Placing a Primary ECB off-line stops all communication to the Fieldbus.
The system sends multiple messages to the printer indicating PIO Bus cable
failures.
General Download
General Download updates FBM images for all off-line and failed FBMs
attached to a selected station.
Use this command 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 checkpoint file information in the station already includes the selected
FBM data (that is, checkpointing was performed while the FBMs were on-
line), downloading occurs automatically, when necessary.
Depending on how the Actions Settings are configured (see “Action Settings”
on page 64), System Manager may prompt you to confirm the action and enter
a reason when you select General Download.
To download FBM images for all off-line and failed FBMs:
• Right-click the Primary ECB in the Navigation pane and choose General
Download from the context menu.
Note For a ZCP270, you must choose General Download a second time
when performing a General Download after a LoadAll. The first command
downloads all the FCMs and the second action downloads all the FBMs.
Note 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 “Checkpointing” on page 142.
• Right-click the Primary ECB and choose Bus Auto Select from the
context menu.
On a ZCP270, select Enet Auto Select.
The Primary ECB records the number of FBM access failures on each
channel or cable and periodically determines whether switching should
occur. If the current channel or cable has failures and the other has fewer
failures, the station automatically switches. If both have an equal number
of FBM or FCM access failures, the station continues transmission over
the existing bus.
To disable auto-switching:
• Right-click the Primary ECB and choose Select Bus A Only or Select Bus
B Only from the context menu.
On a ZCP270, choose either Enet A Only or Enet B Only from the
context menu.
The station attempts to continue transmission over the selected cable/bus
regardless of the number of failures in each module.
C H A P T E R 6
Station Counters
Contents
• Counters Tab for Stations
• MAC Sublayer
• Network Layer
• Transport Layer
• Application Layer
• Loading Parameters
Note Network Layer option is only enabled for LI and ATS stations.
Note The entries on the counter are blank if the station is off-line:
See “Counters Tab” on page 44 and “Watch Tab” on page 53 for additional
information on using features of the Counters and Watch tabs, respectively.
MAC Sublayer
The following table describes the MAC Sublayer counters. A problem with the
equipment may be indicated if the counter exceeds the threshold listed in the
Value column (the threshold is usually counts per hour).
Table 6-1. MAC Sublayer Counters Display Fields
Possible Reason
Counter Description Value For Increment
802.3 MAC Number of times the 2 Bad cable or bad receiver
Resets Nodebus MAC was if very large values are
initialized due to observed over short
transmission errors and periods of time. Low
hot remarries. values (less than
threshold) are norm for
30 second intervals.
Possible heavy network
traffic.
802.4 MAC Number of times the 2 Possible bad cable, bad
Resets tokenbus MAC was receiver or very heavy
initialized due to loaded network for large
transmission errors and value over short periods.
hot remarries. This Occasionally DEFER
counter applies to the LI may appear, and is
station only. acceptable if less than
thresh- hold levels over
30 seconds.
Align Errors Number of received, 0.1% of Bad local receiver or
misaligned frames with frames external transmitter.
CRC errors. Not received
reported for a fault-
tolerant station
(excluding the LI
station) running
married.
Collisions Number of collisions 5.0% of Bad cable, bad hardware,
experienced by the transmitt hot remarries.
controller chip during ed frames
transmission attempts.
Not reported for a fault-
tolerant station
(excluding the LI
station) running
married.
CRC Errors Number of properly 0.1% of Bad cable or bad local
aligned frames received frames receiver or remote
with CRC errors. Not received transmitter if threshold is
reported for a fault- exceeded in 30 seconds.
tolerant station
(excluding the LI
station) running
married.
Possible Reason
Counter Description Value For Increment
DMA Number of frames lost 0 Possible station overload
Overrun because the memory or incoming traffic in
bus was not available to process.
the controller chip. Not
reported for a fault-
tolerant station
(excluding the LI
station) running
married.
DMA Number of times the 1 Signifies a hardware error
Underruns station ran out of on local station, notify
internal bus bandwidth. service.
Not reported for a fault-
tolerant station
(excluding the LI
station) running
married.
Excess Number of unsuccessful 1 Bad cable or bad receiver.
Collisions transmissions because Possible very heavy
the number of collisions network traffic.
exceeded the maximum
number of retries.
Frames Number of frames N/A Each message received
Received successfully received by on network increments
the MAC. this counter by 1.
Frames Number of frames 180,000 Each message transmitted
Transmitted successfully transmitted on network increments
by the MAC. this counter by 1.
No Receive Number of received 0.1% of Signifies hardware error
Resources frames lost due to frames on local station notify
memory resource received service personnel.
problems in the station.
Not reported for a fault-
tolerant station
(excluding the LI
station) running
married.
Transmits Number of times the 5.0% of Bad cable, bad hardware,
Deferred controller chip deferred transmitt hot remarries.
traffic during the first ed frames
transmission attempt.
Not reported for a fault-
tolerant station
(excluding the LI
station) running
married.
Network Layer
This layer is enabled only for ATS and LI stations.
Transport Layer
Possible Reason
Counter Description Value For Increment
Checksum Number of TPDUs 1 System overload condition.
Errors received with checksum
errors.
Connect Data Number of successfully N/A Each connection data packet
TPDUS Recvd received, connection- received increments counter
oriented TPDUs. by 1.
Connect Data Number of successfully N/A Each connection data packet
TPDUS Trans transmitted, connection- transmitted (non-ack)
oriented TPDUs. increments by 1.
Connects Number of connection 10 The local TL detects one of
Denied – APP requests denied by a the following errors; peer
local application. connection not valid;
destination station not
available.
Connects Number of connection 1 Application not ready to get
Denied – RES requests denied due to connections.
lack of Transport Layer
(TL) local resources.
Possible Reason
Counter Description Value For Increment
Connects Number of connection 1 The local TL detected one of
Denied – TL requests denied by the the following errors: packet
TL. format error from peer; no
response from peer; peer TL
denied the connection due to
one of these two error
conditions.
Current # Number of Fox IPC N/A N/A
Connections connections currently
established. You cannot
set this counter.
Disconnects Number of established 1 This counter is incremented
Due To Errors connections that broke only if an established
due to error. connection experiences one
of the following conditions:
retransmits were exceeded
and the TL did not
acknowledge a TPDU; no
TPDUs were received from
the peer TL in a sufficient
time period; the peer TL
broke connection due to one
of two error conditions.
Disconnects Number of established N/A N/A
Requested connections broken due
to a local or remote
application request.
Retrans Data Number of 0.2% of Heavily loaded network.
TPDUS on A retransmitted Transport transmit
Protocol Data Units ted
(TPDUs) on Cable A. TPDUs
Retrans Data Number of 0.2% of Heavily loaded network.
TPDUS on B retransmitted TPDUs on transmit
Cable B. ted
TPDUs
Application Layer
Possible Reason
Counter Description Value For Increment
CNLS-ACK Number of 180,000 Incremented by 1
Received connectionless, where: when received.
acknowledged data CNLS-ACK
packets received by the is sum of
AL. transmitted
and received
CNLS-ACKs.
CNLS-ACK Number of 180,000 Incremented by 1
Transmitted connectionless, where: when received.
acknowledged data CNLS-ACK
packets transmitted by is sum of
the AL. transmitted
and received
CNLS-ACKs.
Possible Reason
Counter Description Value For Increment
CNLS-UNACK Number of N/A Each received
Received connectionless, connectionless
unacknowledged data unacknowledged
packets received by the packet increments
AL. These data packets this counter by one.
have a minimal
overhead, provide no
connection-oriented
services, and neither
send nor receive
acknowledgment.
Delivery is further
assured by sending the
message a second time
on the primary and
secondary cables.
CNLS-UNACK Number of 200 Each transmitted
Transmitted connectionless, connectionless
unacknowledged data unacknowledged
packets transmitted by packet increments
the Application Layer this counter by one.
(AL).
LLC Frames Number of LLC frames N/A Memory overload:
Discarded received directly from lack of space
the LLC layer, but available.
discarded because a
lack of memory
prevented the AL from
copying and passing the
message.
LLC Frames Number of LLC frames N/A Incremented by 1
Received received directly from each time sent.
the LLC layer,
bypassing the Transport
and Network layers.
LLC Frames Number of frames N/A Incremented by 1
Transmitted transmitted directly to each time received.
the Logical Link
Control layer (LLC),
bypassing the Transport
and Network layers.
Possible Reason
Counter Description Value For Increment
No RUCBS Number of 5 A lack of available
Available connectionless data RUCBS indicates an
packets rejected due to insufficient number
lack of Receive Unit of control structure
Control Blocks allocated to process
(RUCBs). A lack of current incoming
available RUCBs traffic and re-
indicates an insufficient configuration may be
number of control necessary.
structures allocated to
process the current
incoming traffic. You
may need to reconfigure
the allocation.
No TUCBS Number of 5 A lack of available
Available connectionless data TUCBs indicates the
packets not sent due to a control structures a
lack of available located to process
Transmit Unit Control current outgoing
Blocks (TUCBs). A message to the traffic
lack of available is insufficient.
TUCBs indicates the
control structures
allocated to process the
current outgoing traffic
are insufficient. You
may need to reconfigure
the allocation.
RETRANS Number of 0.2% of Cable problems (one
CL-ACK on A retransmitted, CL-ACK or more cables, or
RETRANS connectionless, transmitted transitory problems
CL-ACK on B acknowledged data where: may be responsible
packets on Cable A or CL-ACK is for ack never
Cable B. Cable sum of A and arriving, resulting in
problems (one cable, B CL-ACKs. retransmission.
two cables or transitory
problems affecting both
cables) may be
responsible for the
acknowledgment never
arriving; this may result
in retransmissions.
Loading Parameters
The following table describes the Loading Parameters. These counters are
static values, and as such cannot be reset or added to the Watch tab in the
Accessories pane.
Table 6-5. Loading Parameters Display Fields
C H A P T E R 7
FCMs
Contents
• Identifying FCMs in the Navigation Pane
• Symbols for FCM100
• Symbols for FCM10
• Connected FBMs
• Equipment Change Actions
A symbol attached to the upper left corner of the FCM icon indicates an
adverse condition with the module or one of the attached field device. The
status of alarms associated with the FCM is indicated by symbols on the lower
left side of the module.
Labels attached to the right side of the station’s Primary ECB indicate the state
of communications between the FCM and the FBMs, and the status of
communications between the FCM and the control station.
• Choose Help > Legend from the main menu to identify the equipment
health and alarm status symbols, or refer to “Status Indicators” on page 39.
Figure 7-1 shows a Navigation pane in which a ZCP270 and its Primary ECB
(both labeled ZCP703) have been expanded to display an FCM100Et
(FCM300). The FCM in turn has been expanded to display the attached FBMs.
The attached FBMs include a module that is off-line (FCM308) and another
that has failed (FCM311). Thus, the yellow warning symbol is attached to the
FCM icon. The FBM failure has not been acknowledged, and an asterisk has
been attached to the FBM, the FCM, and the host control station.
Host ZCP270
Connected FBMs
Labels and symbols attached to the right side of the FCM indicate the state of
communications between the FCM and the attached FBMs and the FCM and
the control station, as described in the following table:
Table 7-1. Symbols for FCM100
Symbol Condition
A label attached to the upper right corner of the FCM icon
indicates which module Fieldbus channel is being used for
communications between the FCM and the FBMs:
• Bus A when the A cable has been selected by an operator
• Bus B when the B cable has been selected by an operator
• AUTO when the station automatically switches to the
better cable based on a periodic check of the number of
faults on each cable
See “Module Fieldbus Switching Actions” on page 190 for
information on specifying the module Fieldbus channel.
A lightning symbol attached to the right side of the FCM icon
indicates that there is a cable fault with one of the attached
FBMs.
A red line with A, B or AB attached to the right side of the
FCM icon indicates a PIO bus failure, that is, a failure in one
or both of the Fieldbus cables connecting the FCM with its
host control station.
Symbol Condition
A lightning symbol attached to the right side of the FCM icon
indicates that there is a cable fault with one of the attached
FBMs.
A red line with A, B or AB attached to the right side of the
FCM icon indicates a PIO bus failure, that is, a failure in one
or both of the Fieldbus cables connecting the FCM with its
host control station.
Field Description
Name FCM letterbug assigned during definition of system
hardware
Type Model number of the FCM defined during the system
definition
Run Mode A Gives the run mode of each module in a redundant
Run Mode B pair as either On Line or Off Line. The field changes
from Off-Line 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.
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.
Run Mode changes to Off Line if any of the
following occurs:
• An EEPROM update
• A physical pull/push of the module to reboot the
module
• Any FCM hardware failure or communication
failure
Device State A Normally Not Failed. The field displays Failed if
Device State B any of the following occurs:
• A physical pull/push of the module to reboot the
module
• Any module failure or communication failure
Failed Acknowledged Acknowledged or Not Acknowledged. If the Device
State State changes to Failed, the Failed Acknowledged
State changes to Not Acknowledged until the failed
state is acknowledged.
Refer to “Managing Alarms” on page 186.
Alarming State Alarming for the FCM is either Enabled or
Inhibited. When alarming is inhibited, the system
monitor continues to indicate overall system and
network health while equipment is failed or off line.
Refer to “Managing Alarms” on page 186.
Failed Devices Yes if one or more attached FBMs are reported as
Attached failed; otherwise, No
Failed Devices No until all attached devices that have failed are
Acknowledged acknowledged; otherwise, Yes
Field Description
EEPROM State A Updating while the module’s operating software is
EEPROM State B being updated from a workstation; otherwise, Not
Updating.
Refer to “EEPROM Updates” on page 189.
Download State A Downloading, while the module is rebooting after a
Download State B download of the FCM’s control configuration;
otherwise, Not Downloading.
Refer to “Downloading” on page 188.
Field Description
Redundant Status A Status of each module in a redundant pair is shown
Redundant Status B as:
• Master when the module in a redundant pair
is in control
• Tracker when the module is ready to take
over control if the other module fails
• Off-Line when Run Mode (A, B) is Failed
• Not Operational when the module has been
taken off-line by an operator action
Compound Name Compound name containing the FCM’s ECB
Block Name Name of the FCM’s ECB
Field Description
Ethernet Address A A six-octet media access control (MAC) address
Ethernet Address B assigned to each module during system definition
and used by the networking protocol in the
I/A Series stations. The A (Main) module in a
redundant pair has the lower MAC address.
IP Address A Internet Protocol address of each module assigned
IP Address B during system definition and used by the
networking protocol in the I/A Series stations
Network Mask The subnet mask of the FCM is normally set to
255.255.128.0 as assigned during system
definition.
Sync Sate • Network Time
• Sync Pulse
• Drifting
• No Sync Pulse
Power 1 A Failed if there is a fault with the module’s primary
Power 1 B power supply; otherwise, OK
Power 2 A Failed if there is a fault with the module’s
Power 2 B secondary power supply; otherwise, OK
Manufacture Date A Manufacturing date for each module
Manufacture Date B
Hardware Part A Module part number
Hardware Part B
Hardware Revision A Release level of the module hardware
Hardware Revision B
Software Revision A Release level of the software running in the FCM
Software Revision B
Program A The software running in module A or B is the
Program B Backup or Normal (main) module software.
Software Type Number indicating the software running in the
FCM:
210 for an FCM100Et or FCM100E
Hardware Type Number indicating the FCM hardware type:
200 for an FCM100Et or FCM100E
Primary CMD Status Value related to the status of communication
between the FCM and the control station and
between the FCM and the FBMs:
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)
Field Description
FCM CMD Status 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, indicating the command
was understood and action was taken.
0 = Command understood, action taken
1 = Command not understood
2 = Command understood, but unable to take
action
4 = Invalid argument
Main Ethernet A Errors Number of messages with errors received from the
Backup Ethernet A Errors control station over the A cable
Main Ethernet B Errors Number of messages with errors received from the
Backup Ethernet B Errors control station over the B cable
Main HDLC A Errors Number of messages with errors received from
Backup HDLC A Errors FBMs over the module Fieldbus A channel
Main HDLC B Errors Number of messages with errors received from
Backup HDLC B Errors FBMs over the module Fieldbus B channel
IOM Status Code used by Invensys service personnel, usually
0.
FCM State Main FCM operational status, same as the Main
Status field
Strobe Status A Not applicable
Strobe Status B
Main Status Status of each module:
Backup Status
• Normal for a non-redundant FCM operating
under normal conditions
• Master for the controlling FCM in a
redundant pair
• Tracker for a module in a redundant pair that
is ready to take control if the other module
fails
• Not Operational for a module that is Off Line
Main HDLC 01 Status of communications on the A channel of the
Backup HDLC 01 module Fieldbus
Main HDLC 02 Status of communications on the B channel of the
Backup HDLC 02 module Fieldbus
Main Interlink Status of communications on the A cable of the
Backup Interlink Ethernet Fieldbus connection with the control
station
Main Ethernet Status of communications on the B cable of the
Backup Ethernet Ethernet Fieldbus connection with the control
station
Connected FBMs
To display a list of the FBMs attached to the FCM:
1. Select the FCM in the Navigation pane and click the Connections tab in
the Information pane.
Connections lists the attached FBMs by name, type, status, run mode, and
failure mode (Figure 7-4).
2. Click any column header to sort the rows on the values in that column;
click the column header a second time to reverse the sort order.
3. Drag a column header to the right or left to change the column order.
4. Double-click an FBM name or right-click the name and choose
Navigate to <FBM name> to go to the selected module (Navigate to
FCM517 in Figure 7-4).
The FBM is selected in the Navigation pane and its information is
displayed in the Information pane. If there are devices connected to the
FBM, the Connections tab is shown in the Information pane; otherwise,
the General tab is displayed.
Managing Alarms
Acknowledge
There are multiple ways to acknowledge system alarms associated with an
FCM:
• Use the Alarms tab in the Accessories pane to identify and acknowledge
individual alarms (see “Alarms Tab” on page 49).
• Right-click the FCM in the Navigation pane and choose Acknowledge
Device from the context menu to acknowledge device alarms for the
selected FCM.
• Acknowledge all alarms in the FCM’s system monitor domain by
selecting the system monitor in the Navigation pane and doing one of the
following:
• Choose Actions > Acknowledge Smon Domain from the main
menu.
• Click in the toolbar.
• Right-click the system monitor and choose Acknowledge Smon
Domain from the context menu.
Inhibit Alarms
You can inhibit all device alarms for the FCM so that no alarm conditions are
reported to the system monitor.
To inhibit FCM device alarms, do one of the following:
• Right-click the FCM in the Navigation pane and choose Inhibit Alarming
from the context menu.
• Select the FCM in the Accessories pane Alarms tab and click in the
tab toolbar.
The FCM icon is marked with the symbol to indicate that alarms are
being inhibited.
To re-enable alarms:
• Right-click the FCM in the Navigation pane and choose the Enable
Device Alarming from the context menu.
Cable Alarms
To inhibit cable alarms:
• Right-click the FCM and choose Inhibit PIO Bus Cable A Alarms or
Inhibit PIO Bus Cable B Alarms from the context menu.
A symbol ( , or ) attached to lower right corner of each FBM
icon indicates which cables have alarms inhibited.
To re-enable cable alarms:
• Right-click the FCM in the Navigation pane and choose the appropriate
command from the context menu:
Enable PIO Bus Cable A Alarms
Enable PIO Bus Cable B Alarms
2. For redundant modules, click the check box for Main, Backup or both.
The second module in a redundant pair to be brought on line automatically
assumes the Tracker role.
If you take one module off line, the other assumes the Master role if it is
not already in control. If you take both modules off line, all the attached
FBMs also go off line.
For non-redundant FCMs, click the check box for Main.
3. Enter a reason for the action if the Reason field is displayed in the dialog
box.
This action setting is configured in the Configuration dialog (refer to
“Options Menu” on page 61).
4. Click OK to complete the command.
Downloading
Downloading takes the FCM off line, copies the module’s configuration
database from the ZCP270, and brings the module back on line.
When you download to a non-redundant FCM, the attached FBMs are off-line
while the FCM is off-line. For redundant FCMs, you can download to either or
both modules in one command.
To download to an FCM:
1. Right-click the FCM in the Navigation pane and choose Download from
the context menu.
A dialog box displays the current run mode of each module and prompts
you to select which module is to be updated (Figure 7-6). Note that Main
is the module located in the first baseplate position, and not necessarily the
Master (or controlling) module.
2. For redundant modules, click the check box for Main, Backup or both.
If you download one module, the other assumes the Master role if it is on-
line and not already in control.
For non-redundant FCMs, click the check box for Main.
3. Enter a reason for the action if the Reason field is displayed in the dialog
box.
This action setting is configured in the Configuration dialog (refer to
“Options Menu” on page 61).
4. Click OK to complete the command.
EEPROM Updates
An EEPROM Update takes the FCM off line, loads the module’s operating
system software to the FCM’s flash memory and restarts the module. During
an EEPROM update of a non-redundant FCM, the attached FBMs are off-line,
but are automatically returned to their prior status when the FCM is restarted.
For a redundant pair, you can only update one module at a time.
To update an FCM operating system image:
1. Right-click the FCM in the Navigation pane and choose EEPROM
Update from the context menu.
A dialog box displays the current run mode of each module and prompts
you to select which module is to be updated (Figure 7-7). Note that Main
is the module in the first baseplate position, and not necessarily the Master
(or controlling) module.
2. For redundant modules, click the check box for Main or Backup.
If both modules are on-line, the module selected for the update goes off-
line and the other assumes the Master role if it is not already in control.
For a non-redundant FCM, click the check box for Main.
3. Enter a reason for the action if the Reason field is displayed in the dialog
box.
This action setting is configured in the Configuration dialog, as described
in “Options Menu” on page 61.
4. Click OK to complete the command.
Switching Roles
In a redundant FCM pair, one module assumes control of the module Fieldbus
(the Master role) and the other module operates in the Tracker role, ready to
take over if the other module fails. The current role of each module is
displayed in the Redundant State A and Redundant State B fields in the
General tab Equipment Information table (Figure 7-3).
To force the modules in a redundant pair to switch roles:
1. Right-click the FCM in the Navigation pane and choose Switch Roles
from the context menu.
The Switch Roles dialog box displays the current run mode of each
module and prompts you to confirm the action (Figure 7-8). Note that
Main is the module in the first baseplate position, and not necessarily the
Master (or controlling) module.
• If both modules are not on line, click Cancel, use the Go On Line
command to change the run mode of the modules, and select the
Switch Roles command a second time.
2. Click OK in the Switch Roles dialog box to complete the switch.
• If the current module Fieldbus has failures and the other bus has fewer
failures, the station automatically switches to the better bus.
• If the channels have an equal number of FBM access failures, the FCM
continues transmission over the existing bus.
When the operator selects Bus A Only or Bus B Only, the FCM attempts to
transmit over the selected channel regardless of the number failures on that
channel.
• Right-click the FCM in the Navigation pane and choose the switching
option:
Select Bus A
Select Bus B
Bus Auto Select
C H A P T E R 8
Fieldbus Modules
This chapter describes how to use System Manager software to monitor and
control Fieldbus Modules (FBMs) and their attached field devices.
The information in this chapter applies to the 200 Series (DIN rail mounted)
FBMs listed in Table 8-1 and the 100 Series FBMs listed in Table 8-2. For a
list of equivalent migration FBMs and Fieldbus Cluster I/O modules, refer to
Appendix A, “Supported Migration and Fieldbus Cluster I/O Modules”.
Table 8-1. Supported 200 Series FBMs
FBM Description
FBM201 8-Channel 0 to 20 mA Input, Channel Isolated (8 AI)
FBM201b 8-Channel 0 to 100 mV dc Input, Channel Isolated (8 AI)
FBM201c 8-Channel 0 to 5 V dc Input, Channel Isolated (8 AI)
FBM201d 8-Channel 0 to 10 V dc Input, Channel Isolated (8 AI)
FBM201e 8-Channel 0 to 20 mA Input, Channel Isolated (8 AI)
FBM202 8-Channel Thermocouple/Millivolt Input, Channel Isolated
(8 AI)
FBM203 8-Channel RTD Input (platinum or nickel), Channel
Isolated, 0 to 320 ohm (8 AI)
FBM203b 8-Channel RTD Input (platinum or nickel), Channel
Isolated, 0 to 640 ohm (8 AI)
FBM203c 8-Channel RTD Input (copper), Channel Isolated, 0 to 30
ohm (8 AI)
FBM203d 8-Channel 4-wire RTD Input (Pt, Ni, Cu), Channel
Isolated, 0 to 320 ohm (8 AI, FBM3 replacement)
FBM204 8-Channel 0 to 20 mA I/O (4 Input, 4 Output), Channel
Isolated (can have redundant outputs)
FBM205 Redundant 0 to 20 mA Input/Output (4 Input and 4
Output), Channel Isolated (4 AI/4 AO)
FBM206 8-Channel Pulse Input, Channel Isolated (8 PI)
FBM206b 4-Channel Pulse Input,
4-Channel 0 to 20 mA Output (non-HART), Channel
Isolated (FBM06 replacement)
FBM207 Redundant Ready
6-Channel Voltage Monitoring, Channel Isolated (16 DI)
FBM Description
FBM207b Redundant Ready
16-Channel 24 V dc Contact Sense, Channel Isolated
FBM207c Redundant Ready
16-Channel 48 V dc Contact Sense, Channel Isolated
FBM208 Redundant with Readback, 0 to 20 mA Input/Output
(4 Input and 4 Output), Channel Isolated (4AI/4AO)
FBM208b Redundant with Readback, 0 to 20 mA Input/Output
(4 Input and 4 Output), Channel Isolated (FBM05
Replacement)
FBM211 16-Channel Differential Analog Input,
0 to 20 mA, Differential Isolated (16 AI)
FBM212 14-Channel Differential Analog Input, Thermocouple,
Differential Isolated (14 AI)
FBM213 RTD (Platinum and Nickel) (8 AI)
FBM214 8-Channel 0 to 20 mA, HART® Input
FBM214b 8-Channel 0 to 20 mA, HART® Input (FBM01
replacement with HART capability)
FBM215 8-Channel 0 to 20 mA, HART Output
FBM216 Redundant 8-Channel 0 to 20 mA, HART Input
FBM216b Redundant 8-Channel 0 to 20 mA, HART Input
FBM217 Redundant Ready
32-Channel Discrete Input, Group Isolated (32 DI)
FBM218 Redundant 8-Channel 0 to 20 mA, HART Output
FBM219 24-Channel Voltage Monitor, Plus
8-Channel Discrete Output, External Source, Group
Isolated
FBM220 1-Channel Interface to H1 FOUNDATION fieldbus (one
segment)
FBM221 4-Channel Interface to H1 FOUNDATION fieldbus (four
segments)
FBM222 Redundant Ready
2-Channel Interface to Redundant PROFIBUS-DP™
FBM223 2-Channel Interface to PROFIBUS-DP™
FBM224 4-Port RS-232, RS-422 and/or RS-485 Interface to
Modbus® Devices
FBM227 4-Channel 0 to 10 V dc Input, 2-Channel 0 to 10 V dc
Output 4-Channel Discrete Input, 4-Channel Discrete
Output; Discrete channels are isolated in channel pairs
(FBM17 replacement with MDACT and DPIDA control)
FBM228 Redundant Ready
4-Channel Interface to H1 FOUNDATION fieldbus
FBM229 1-Channel Interface to up to 64 DeviceNet devices
FBM Description
FBM230 RS-232, RS-422, and/or RS-485 Field Device System
Integrator (FDSI) Interface
FBM231 Redundant RS-232, RS-422, and/or RS-48 Field Device
System Integrator (FDSI) Interface
FBM232 Ethernet Field Device System Integrator (FDSI) Interface
FBM233 Redundant Field Device System Integrator (FDSI)
Interface
FBM237 Redundant Ready
8-Channel 0 to 20 mA Output, Redundant, Channel
Isolated (8 AO)
FBM238 24-Channel Voltage Monitor, Plus
8-Channel Discrete Output, External Source, Group
Isolated (FBM9/14, 10/15, 11/16, 26/27, 41/42
replacements)
FBM239 16-Channel Voltage Monitor, Plus
16-Channel Discrete Output, External Source, Group
Isolated (FBM9/14, 10/15, 11/16, 26/27, 41/42
replacements)
FBM240 Redundant Ready
8-Channel Externally Sourced Discrete Output with
Readback, Channel Isolated (8 DO)
FBM241 8-Channel Voltage Monitor, Plus
8-Channel Discrete Output, External Source, Channel
Isolated (8 DI/8 DO)
FBM241b 8-Channel Voltage Monitor, Plus
8-Channel Discrete Output, Internal Source, Channel
Isolated
FBM241c 8-Channel Contact Sense, Plus
8-Channel Discrete Output, External Source, Channel
Isolated
FBM241d 8-Channel Contact Sense, Plus
8-Channel Discrete Output, Internal Source, Channel
Isolated
FBM242 16-Channel Externally Sourced Discrete Output, Channel
Isolated (8 DO)
FBM243 8-Channel Bi-directional FoxCom™ Dual Baud Rate
Intelligent Device Interface Communication
FBM243b 4-Channel Bi-directional FoxCom™ Dual Baud Rate
Intelligent Device Interface Communication, Plus
4-Channel 0 to 20 mA, Output (FBM39 and FBM44
replacement)
FBM244 4-Channel 0 to 20 mA Input and 4-Channel 0 to 20 mA
Output (with HART® Support on All Channels) (FBM04
replacement)
FBM Description
FBM245 Redundant 4-Channel 0 to 20 mA Input and 4-Channel
0 to 20 mA Output (with HART® Support on All
Channels) (FBM05 replacement)
FBM246 Redundant, 8-Channel Bi-directional FoxCom Dual Baud
Rate Intelligent Device Interface Communication
FBM246b Redundant, 4-Channel Bi-directional FoxCom Dual Baud
Rate Intelligent Device Interface Communication, Plus
4-Channel 0 to 20 mA, Output (FBM46 replacement)
FBM247 8-Channel Current/Voltage Analog/Digital/Pulse I/O
Configurable Channel Interface Module (with HART®
Support on All Channels) - Includes support for additional
communication types
FBM Description
FBM01 0 to 20 mA Input (8 AI)
FBM02 Thermocouple/mV Input (8 AI)
FBM03 RTD Input (8 AI)
FBM04 0 to 20 mA Input/Output (4 AI/4 AO)
FBM05 0 to 20 mA Input/Output Interface (4 AI/4 AO) (Redundant
I/O)
FBM06 Pulse Input, 0 to 20 mA Output (4 PI/4 AO) (can be
redundant)
FBM07 Contact/dc Input (16 DI)
FBM08 120 V ac Input (16 DI)
FBM09 Contact/dc Input/Output (8 DI/8 DO)
FBM10 120 V ac Input/Output (8 DI/8 DO)
FBM11 240 V ac Input/Output (8 DI/8 DO)
FBM12 Contact/dc Input Expander
FBM13 120 V ac Input Expander
FBM14 Contact/dc Input/Output Expander
FBM15 120 V ac Input/Output Expander
FBM16 240 V ac Input/Output Expander
FBM17 0 to 10 V dc, Contact/dc Input/Output (4 AI/2 AO and
4 DI/4 DO)
FBM18 Intelligent Field Device (8 Inputs)
FBM20 240 V ac Input (16 DI)
FBM21 240 V ac Input Expander
FBM22 Single 0 to 20 mA Input/Output with Auto/Manual (1 AI/1
AO)
FBM Description
FBM23 (HIU) HTG Interface Unit
FBM24 Contact/125 V dc Input Interface (16 DI)
FBM25 Contact/125 V dc Input Interface
FBM26 Contact/125 V dc Input/Output (8 DI/8 DO)
FBM27 Contact/125 V dc Input/Output Expander
FBM33 RTD Input (Copper) (8 AI)
FBM36 Type R Thermocouple/mV Input (8 AI)
FBM37 0 to 20 mA Output (8 AO)
FBM38 Mass Flow Transmitter
FBM39 Intelligent Field Device Input and 0 to 20 mA Output
(4 Inputs/4 AO) (can be redundant)
FBM41 Contact 24 V dc Input/0 to 60 V dc Output (8 DI/8 DO)
FBM42 Contact 24 V dc Input/0 to 60 V dc Output Expander
FBM43 Intelligent Field Device Dual Baud Rate
Intelligent Interface (8 Inputs)
FBM44 Intelligent Field Device Dual Baud Rate
Intelligent Transmitter Interface/0 to 20 mA Output
(4 Inputs/4 AO) (can have redundant outputs)
FBM46 Redundant Dual Baud Rate Interface to Intelligent
Transmitters and Redundant 0 to 20 mA Outputs (4
Inputs/4 AO)
PDISP Panel-Mounted Display
Equipment information
Device Group Devices supported reference
Foreign Device Group Foreign Device RS232 Refer to “Equipment Information
for Device Integrator Peripherals”
on page 257
INI X.25 Port group INI X.25 Port ECB Refer to “INI10, INI15 or
SPECTRUM Interface Processor
Peripheral Equipment Information
Fields” on page 259
SIP group Spectrum Interface Proc ECB Refer to “SIP ECB Equipment
Information Displays” on page 261
IS30 GIT device group IS30 GIT device Refer to “INTERSPEC Integrator
Translator Equipment Information”
on page 262.
Equipment information
Device Group Devices supported reference
Allen Bradley ECBs AB Port Refer to “Equipment Information
group AB PLC view for the Allen-Bradley Port
AB Scan (ECB 63, ECB 64, and ECB 65)”
on page 265
Allen Bradley PLC Allen Bradley 540 PLC type Refer to “Equipment Information
device group Allen Bradley 560 PLC type for the A-B Station PLC5 Series”
Allen Bradley 511 PLC type on page 267
Allen Bradley 520 PLC type
Allen Bradley 530 PLC type
Allen Bradley 530 PLC type
Allen Bradley rack Allen Bradley Rack type Refer to “Equipment Information
device group for the A-B Station Rack” on
page 269
ModBus ECBs group MG Port Refer to “Equipment Information
MG PLC Display for Modicon Port ECB
MG Scan (ECB60, ECB61, and ECB62)” on
page 271
AB primary port OMC FC Primary ECB for AB Refer to “Micro-I/A AB-PIO
Peripherals Equipment
Information” on page 273
GE primary port OMC FC Primary ECB for GE Refer to “Micro-I/A GE-PIO
Peripherals Equipment
Information” on page 274
AB Remote Adapter for FC AB RIO Adaptor Refer to “Equipment Information
OMC Display for an AB-RIO Adapter”
on page 276
AB and GE I/O Modules FC GE 8 DO #GEDC/GE120AO Refer to “Equipment Information
FC GE 16 DO #GE24DO Display for a GE I/O Device and
FC GE 8 AI #GE20 A-B I/O Device” on page 277
FC GE 16 DI #GE24/48/120 DI
FC GE 4 AO #GE04
FC AB 8 AI #1794-IE8
FC AB 8 DI #1794-IB8S/IA8
FC AB 16 DI #1794-IB16
FC AB 4 AO #1794-OE4
FC AB 4AI/2AO #1794-IE4OE2
FC AB 16 DO #1794-OB16
FC AB 8 DO #1794-OA8/OW8
FC AB T/C #1794-IT8
FC AB RTD #1794-IR8
SCADA (port device) Port (Bristol-Babcock) Refer to “Equipment Information
Display for ECB96 Port” on
page 279
SCADA (device) RTU (Bristol-Babcock) Refer to “Equipment Information
Display for ECB97 RTU” on
page 283
Equipment information
Device Group Devices supported reference
ACM (Main Processor) TRICON Monitor Refer to “FoxGuard Manager
device Equipment Information” on
page 287
ACM (I/O Cards) TRICON 32 DI Refer to “I/O Module Equipment
TRICON 64 DI Information Display” on page 290
TRICON 8 PI
TRICON 16 DO
TRICON 8 DO
TRICON 32 DO
TRICON 32 AI
TRICON 16 AI
TRICON 64 AI
TRICON 32 TC
TRICON 16 TC
TRICON 8 AO
DI-WIN-NT Character Port for Character Protocols Refer to “Equipment Information
Port group, Display for ECB98, ECB99, and
DI-WIN-NT Message Port for Msg protocols ECB100” on page 292
Port group, and
DI-WIN-NT Device Generic Device
group
FOX2068 Port group Fox2068 Port Refer to “ECB80 Equipment
Information” on page 295
FOX2068 RTU group Fox2068 RTU Refer to “ECB81 Equipment
Information” on page 296
Profibus Gate group Profibus Gate Refer to “Equipment Information
Display for PROFIBUS-DP Gate
and Devices” on page 297
Profibus Device group Profibus Device Refer to “Equipment Information
Display for PROFIBUS-DP
Devices” on page 298
PLC5 Gate Group PLC5 Gate Refer to “Equipment Information
Displays for AB-PLC5/E Gate
Devices” on page 299
PLC5 Device Group PLC5 Device Refer to “Equipment Information
Displays for the AB-PLC5/E
Device” on page 300
Modbus Gate Group Modbus Gate Refer to “Equipment Information
Displays for the Modbus Gate and
Modbus Devices” on page 301
Modbus Device Group Modbus Device Refer to “Equipment Information
Displays for the Modbus Device”
on page 302
Contents
• Identification of FBMs and Attached Devices
Note 100 Series upgrade FBMs are treated as if they were 200 Series FBMs.
For example, the selected FBM in Figure 8-1 (FBM232) is an FDSI module
with four devices attached. Each of the devices can be selected to display
device status and equipment information in the Information pane and to
perform equipment change actions.
FOUNDATION fieldbus FBM228 device names are prefixed with <P1>, <P2>,
<P3> or <P4> to identify the H1 segment on which the device is operating.
The first time an FBM228 device is shown in a System Manager session, the
device is identified by its segment and six-character DEV_ID. When you click
on the device, System Manager retrieves complete status and equipment
information for the device and changes the display so that the device is
identified by its segment, block name, and DEV_ID for the remainder of the
System Manager session.
Note Depending on the block name and the DEV_ID of the device, FBM228
devices may appear out-of-order on the Navigation pane as shown below:
NEW
Status Indicators
A symbol attached to the upper left corner of the FBM or device icon indicates
an adverse condition with the equipment. The status of alarms associated with
the FBM and attached devices is indicated by symbols on the lower left side of
the equipment icon.
• Choose Help > Legend from the main menu to identify the equipment
health and alarm status symbols, or refer to “Status Indicators” on page 39.
Labels attached to the right side of the FBM (for example, FCM50A in
Figure 8-1) indicate the state of communications between the FBM and the
control station or FCM:
Symbol Condition
A red label to the right of the FBM indicates a problem with
communications between the FBM and the control station or
FCM in one or both of the module Fieldbus channels.
The first two fields in the Equipment Status table identify the FBM by name
and type. The remainder of the fields in this group provide status information
and are updated dynamically. The fields in the Equipment Information group
are updated periodically.
The I/O Points group at the bottom of the tab shows the quality of the data
from each point handled by the FBM. This display is available only if the bad
I/O bit is set in BADALM parameter (BADALM: 1) of the control station’s
Primary ECB (that is, the ECBP or Primary ECB in the station’s ECB
compound). This requirement does not apply to the DCI-based FBMs.
The fields displayed in the General tab vary with the type of FBM. For
example, the displays for redundant FBMs have additional fields that apply to
the Main and Backup modules.
The FBM206 information in Figure 8-2 is an example of the format used for
the following non-DCI FBMs:
FBM Description
FBM Description
FBM05 0 to 20 mA Input/Output Interface (4 AI/4 AO)
(Redundant I/O)
FBM06 Pulse Input, 0 to 20 mA Output (4 PI/4 AO) (can be
redundant)
FBM07 Contact/dc Input (16 DI)
FBM08 120 V ac Input (16 DI)
FBM09 Contact/dc Input/Output (8 DI/8 DO)
FBM10 120 V ac Input/Output (8 DI/8 DO)
FBM11 240 V ac Input/Output (8 DI/8 DO)
FBM12 Contact/dc Input Expander
FBM13 120 V ac Input Expander
FBM14 Contact/dc Input/Output Expander
FBM15 120 V ac Input/Output Expander
FBM16 240 V ac Input/Output Expander
FBM17 0 to 10 V dc, Contact/dc Input/Output (4 AI/2 AO and
4 DI/4 DO)
FBM18 Intelligent Field Device (8 Inputs)
FBM20 240 V ac Input (16 DI)
FBM21 240 V ac Input Expander
FBM22 Single 0 to 20 mA Input/Output with Auto/Manual (1
AI/1 AO)
FBM23 (HIU) HTG Interface Unit
FBM24 Contact/125 V dc Input Interface (16 DI)
FBM25 Contact/125 V dc Input Interface
FBM26 Contact/125 V dc Input/Output (8 DI/8 DO)
FBM27 Contact/125 V dc Input/Output Expander
FBM33 RTD Input (Copper) (8 AI)
FBM36 Type R Thermocouple/mV Input (8 AI)
FBM37 0 to 20 mA Output (8 AO)
FBM38 Mass Flow Transmitter
FBM39 Intelligent Field Device Input and 0 to 20 mA Output
(4 Inputs/4 AO) (can be redundant)
FBM41 Contact 24 V dc Input/0 to 60 V dc Output (8 DI/8 DO)
FBM42 Contact 24 V dc Input/0 to 60 V dc Output Expander
FBM43 Intelligent Field Device Dual Baud Rate
Intelligent Interface (8 Inputs)
FBM44 Intelligent Field Device Dual Baud Rate
Intelligent Transmitter Interface/0 to 20 mA Output
(4 Inputs/4 AO) (can have redundant outputs)
FBM Description
FBM46 Redundant Dual Baud Rate Interface to Intelligent
Transmitters and Redundant 0 to 20 mA Outputs (4
Inputs/4 AO)
PDISP Panel-Mounted Display
FBM Description
FBM246b 4 Redundant FoxCom Dual Baud (4800 or 600 Baud) &
(ECB49) 4 AO (4-20mA);
[FBM46 replacement]
FBM247 0 to 20 mA, non-HART or 4-20 mA, HART, over eight
channels, each of which can be individually configured
for a specific type of field I/O signal, and as either an
input or output.
Also supports:
• 0 to 10 V and 0 to 5 V analog input, non-HART
• Digital dry contact sense 24 V dc
• Discrete voltage monitor, configurable 0 and 1
thresholds 0-10 V
• NAMUR sensor discrete input - Signal level
according to DIN EN 50227 (NAMUR):
• “On” switching threshold 2.1 mA ± 10%
• “Off” switching threshold 1.6 mA ± 10%
• Input impedance 123 Ohms
• Pulse count, frequency, acceleration and jerk,
contact sense or voltage input
• Discrete Output 24 V, 20 mA current or solid state
switch output
The Equipment Status and Equipment Information tables for these FBMs are
described below.
Formats used for other FBMs are covered in the following sections:
• “FBM246 Status and Equipment Information” on page 211
• “DCI Based FBMs” on page 212
• “Migration FBMs” on page 213
• For the DeviceNet FBM229, refer to the “FBM229 Equipment
Information” section in Implementing a DeviceNet Network on the
I/A Series System (B0750CH).
• For the HART-capable FBM247, refer to the “HART-Capable FBM247
Equipment Status and Information Display” section in HART™
Communication Interface Modules User’s Guide (B0400FF).
Field Description
Name Letterbug assigned to the FBM
Type Type is determined by the Primary ECB when checking
the devices on its Fieldbus. Table 8-1 describes the
available 200 Series FBMs and Table 8-2 describes the
available 100 Series FBMs.
Run Mode On Line or Off Line. You can set the Run Mode using
the Go On-Line and Go Offline actions from the
module’s context menu.
If station reporting is disabled, the last known FBM run
mode appears in this field. If the field indicates an Off-
line status:
• Check the hardware.
• Download to the module if necessary.
• Check related fields such as Download State.
Device State Failed or Not Failed
Failed Acknowledged or Not Acknowledged. If the Device
Acknowledge State value changes from Not Failed to Failed, the value
State in this field changes to Not Acknowledged.
Do the following if the field indicates a Not
Acknowledged status:
• Check the Alarms tab in the Accessories Pane for
the type of failure.
• Acknowledge system failures using the Alarms tab
in the Accessories pane or right-click FBM in the
Navigation pane and choose Acknowledge Device
from the context menu.
Alarming State Enabled or Inhibited. When device 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. To
change the Alarming State:
• Right-click the FBM icon in the Navigation pane
and choose Inhibit Device Alarming or Enable
Device Alarming from the context menu.
Inhibiting alarms acknowledges any unacknowledged
alarms.
Download State Downloading if the FBM is downloading its application
image; otherwise, Not Downloading
Warning Condition Yes if the device has a non-fatal error condition or if an
attached field device has failed; otherwise, No
Field Description
Devices Attached Yes if the FBM has devices attached; otherwise, No
Failed Devices Yes if a device attached to the FBM has failed;
Attached otherwise, No
Last Cable Access The status of both module Fieldbus channels is reported
as:
• Both Cables OK
• A Okay / B Fail
• A Fail / B Okay
• A Fail / B Fail
Failed Devices No if a failure of an attached device has yet to be
Acknowledged acknowledged; otherwise, Yes.
Refer to “Managing Device Alarms” on page 217.
Field Description
Compound Name Name of the compound that holds the FBM’s equipment
control block (ECB)
Block Name ECB name of the FBM, typically but not necessarily the
same as the FBM (letterbug) name
Hardware Type Number associated with this FBM type
Software Type Software type being used with the designated FBM
hardware type. The FBM Software Type is not the ECB
type. Software types for supported FBMs are given in
Table 8-5.
Hardware Part The hardware part number related to this FBM
Hardware The hardware release level of this FBM hardware type
Revision
Software Revision Release level of this FBM’s software
EEPROM Firmware release for this FBM
Revision
Serial Number Serial number assigned to this module
Manufacture Date Date of manufacture for this module
Diag Status 1 Hexadecimal values relating to the status of the FBM. If
through the module is operating properly, these values can be
Diag Status 4 safely ignored. If there are hardware and software errors,
these values will assist the Global CSC in resolving the
problem.
Field Description
Logical Address Logical Address is the number of the FBM based on the
order in which the FBMs were “fixed” using the
Integrated Control Configurator. If an FBM is deleted
and another added later, the new FBM is given the
lowest number available. For example, if 0x02 is deleted
from the sequenced group of 0x01, 0x02, and 0x03, the
next FBM added results in the following sequence
group: 0x01, 0x03, and 0x02.
Primary Cmd State A hexadecimal value associated with the return status
included in the header of every response from the FBM
to the Primary ECB:
0 = the command was understood and action was taken.
1 = the command was not understood.
2 = the command understood, but unable to take action.
4 = the argument was invalid.
IOM Status Hexadecimal values relating to the status of the FBM. If
IOM Cmd Status the module is operating properly, these values can be
safely ignored. If there are hardware and software errors,
these values will assist the Customer Service Center in
resolving the problem.
Power 1 OK if power is applied to the primary module in a
redundant FBM or to a non-redundant module;
otherwise, Failed
Power 2 For a redundant FBM, OK if power is applied to the
secondary module in the redundant pair; otherwise,
Failed.
For a non-redundant FBM, always Failed
Extension Type Not used in this version of System Manager
For the FBM233 and similar DCI modules, more detailed descriptions of the
Information pane fields are available in the user’s guide for the FBM or the
fieldbus standard, as listed in the following table:
FBM Document
FBM220, FBM221 FOUNDATION fieldbus H1 Interface Module
(FBM220/221) User Guide (B0400FD)
FBM222 Implementing Profibus Networks in Foxboro Control
Software Applications (B0750BE)
FBM223 and related PROFIBUS-DP Communication Interface Module
slave devices (FBM223) User’s Guide (B0400FE)
FBM214, FBM215, HART Communication Interface Module
FBM216, FBM218 (FBM214/215/216/218) User’ Guide (B0400FF)
and related slave
devices
FBM224 Modbus Communication Interface Module (FBM224)
User’s Guide (B0400FK)
FBM228 • Implementing FOUNDATION™ fieldbus on the
I/A Series System (B0700BA)
• Implementing FOUNDATION™ fieldbus
(B0750BC, for InFusion V1.2.2 and earlier
systems)
• Implementing FOUNDATION™ fieldbus in
Foxboro Control Software Applications
(B0750DA, for InFusion V2.0 and later systems
or Foxboro Control Software V3.0 and later
systems)
FBM229 Implementing a DeviceNet Network on the I/A Series
System (B0750CH)
FBM230, FBM231, I/A Series System Field Device System Integrators
FBM232, FBM233 (FBM230/231/232/233) User’s Guide (B0700AH)
FBM247 HART Communication Interface Modules User's
Guide (B0400FF)
Migration FBMs
The Invensys Plug-in Migration program enables users of legacy DCS systems
that are no longer supported to migrate to the I/A Series system. In this
program, the legacy I/O modules are replaced with I/A Series migration FBMs
that plug into the existing I/O racks and use existing field wiring. System
Manager includes support for several such programs. The Siemens/Moore
APACS+ and Westinghouse WPDF migration programs are based on 200
Series FBM technology. The SPEC 200, SPEC 200 MICRO, CCM, Spectrum
(UCM, UIO, UFM, FIO), Cluster, and Competitive Migration (Honeywell,
Bailey, Provox) programs are based on 100 Series FBM technology.
The migration FBMs, called DCS Fieldbus Modules, are represented in the
I/A Series system by ECBs that are the same or similar to those used for
standard 100 Series or 200 Series FBMs. For example, the ADO115 is an
I/A Series FBM242 packaged in a Moore APACS+ form factor. The module is
displayed in System Manager as if it were an FBM242. Some migration FBMs
consist of two I/A Series FBMs in a single module and are thus represented by
two ECBs. For example, the ASA211 for Moore APACS+ migration is
displayed in System Manager as two FBM211s. System Manager uses the
same icons, status indicators and Information pane formats as it does for other
FBMs.
For specific information on the content of Status and Equipment Information
displays and on the available equipment change actions, refer to the user’s
guide for the particular migration program:
• DCS Fieldbus Modules for Moore® APACS+ Systems (B0700BK)
• DCS Fieldbus Modules for Westinghouse® WPDF Systems User’s Guide
(B0400BA)
• DCS Fieldbus Modules for Bailey® NET90 and INFI90 Systems User’s
Guide (B0193XG)
• DCS Fieldbus Modules for Fisher® PROVOX Controller Series Systems
User’s Guide (B0400AR)
• DCS Fieldbus Modules for Fisher® PROVOX Series 10 Systems User’s
Guide (B0193WV)
• DCS Fieldbus Modules for Fisher® PROVOX Series 20 Systems User’s
Guide (B0193YV)
• DCS Fieldbus Modules for Honeywell® TDC 2000 Systems User’s Guide
(B0193VL)
• DCS Fieldbus Modules for Honeywell® TDC 3000 Systems User’ Guide
(B0193YW)
• Fieldbus Cluster I/O User’s Guide (B0193RB)
• SPEC 200 MICRO® Control Integrator User’s Guide (B0193RR)
• SPEC 200® CCM Control Integrator User’s Guide (B0193VU)
• SPEC 200® Control Integrator User’s Guide (B0193RD)
• SPECTRUM™ Migration Integrator User’s Guide (B0193RC)
Connections Tab
To display a list of the devices attached to an FBM:
1. Select the FBM in the Navigation pane and click the Connections tab in
the Information pane.
The Connections tab lists the attached field devices by name, type, status,
run mode, and failure mode (Figure 8-5).
2. Click any column header to sort the rows on the values in that column;
click the column header a second time to reverse the sort order.
3. Drag a column header right or left to rearrange the column order.
4. Double-click a device name, or right-click the name and choose
Navigate to <device name> to go to the selected device.
The device is selected in the Navigation pane and its information is
displayed in the Information pane.
Counters Tab
The Counters tab for an FBM (Figure 8-6) displays three statistics:
Counter Description
Timeouts Number of times the primary ECB timed out an FBM
during communication attempts.
Inval Cmnd Number of commands received by the primary ECB
that were invalid in the present state of the station.
Inval Resp Number of invalid messages received by the primary
ECB from an FBM.
See “Counters Tab” on page 44 and “Watch Tab” on page 53 for additional
information on using the Counters and Watch tabs, respectively.
Acknowledge
There are multiple ways to acknowledge system alarms associated with an
FBM or its attached devices:
• Use the Alarms tab in the Accessories pane to identify and acknowledge
individual alarms, or acknowledge all alarms (see “Alarms Tab” on
page 49).
• Right-click the FBM in the Navigation pane and choose Acknowledge
Device from the context menu to acknowledge all alarms for the selected
FBM.
• Acknowledge all alarms in the FBM’s system monitor domain by
selecting the system monitor in the Navigation pane and doing one of the
following:
• Choose Actions > Acknowledge Smon Domain from the main
menu.
• Click in the toolbar.
• Right-click the system monitor and choose Acknowledge Smon
Domain from the context menu.
Inhibit Alarms
You can inhibit alarms for an FBM and its attached devices so that no alarm
conditions are reported to the system monitor.
To inhibit device alarms, do one of the following:
• Right-click the FBM in the Navigation pane and choose Inhibit Device
Alarming from the context menu.
• Select a device in the Accessories pane Alarms tab and click in the tab
toolbar.
The FBM icon is marked with the symbol to indicate that alarms are
being inhibited.
To re-enable device alarms:
• Right-click the FBM in the Navigation pane and choose Enable Device
Alarming.
acknowledge all cable alarms including those associated with the selected
FBM.
You can inhibit all cable alarms on either or both cables/busses connecting the
FBM to its host station.
To inhibit cable alarms:
• Right-click the FBM and choose Inhibit PIO Bus Cable A Alarming or
Inhibit PIO Bus Cable B Alarming from the context menu.
A symbol ( , or ) attached to lower right corner of the FBM
icon indicates which cables have alarms inhibited.
To re-enable the alarms:
• Right-click the FBM in the Navigation pane and choose the appropriate
command from the context menu:
Enable PIO Bus Cable A Alarming
Enable PIO Bus Cable B Alarming
2. Enter a reason for the action (if prompted), and click OK.
Download or Reboot
The Download or Reboot actions takes the FBM off line, loads the FBM’s
control configuration from the control station, and brings the FBM back on
line.
If the checkpoint file information does not include the FBM data, you must
download the new FBM added to the control station after performing
integrated control configuration and FBM fix.
If the checkpoint file information in the control station already includes the
selected FBM data (that is, checkpointing was performed while the FBM was
on line), downloading occurs automatically, when necessary. Refer to
“Checkpointing” on page 142.
A dialog box prompts you to confirm the action. For redundant FBMs, the
dialog box also prompts you to select which modules to update: Main,
Backup or both (Figure 8-9).
2. Check the box for one or both modules if the FBM is a redundant pair.
3. Enter a reason for the download if prompted.
4. Click OK.
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 Manager displays a message
in the Message tab.
5. After the FBM image download is complete, right-click the control station
in the Navigation pane and choose Checkpoint from the context menu to
align the control database in the checkpoint file in the boot host with the
control station.
EEPROM Update
The EEPROM Update copies FBM operating system software from the host
workstation to the module’s flash memory and restarts the module.
It is advised that you use this action only after an official Invensys software
release.
Note For FBMs 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 stations after the FBMs are downloaded to ensure that the
update was successful before you perform a download.
2. For 200 Series FBMs, observe the Run Mode field to see when the FBM
is returned to On-Line.
For 100 Series FBMs, follow Step 3 to perform Download (or Reboot)
action in order to bring the FBM back on-line.
The update is complete when the FBM is back on-line. The system
displays a message indicating that the device is back on-line. If the update
action fails, a failure message is shown in the Messages tab.
3. Right-click the FBM in the Navigation pane and choose Download (or
Reboot) from the context menu to download the control configuration
from the control station.
4. Right-click the control station and choose Checkpoint from the context
menu to update the control database in the host workstation.
5. Review the Messages tab in the Accessories pane to verify success of the
EEPROM Update, Download, and Checkpoint actions.
To update firmware in a redundant FBM:
1. Right-click the FBM in the Navigation pane and choose EEPROM
Update from the context menu.
Reset FBM
The Reset FBM action is only available for the FDSI modules: FBM230,
FBM231, FBM232 and FBM233.
The action restarts the FBM logic without downloading the image to the FBM.
For the redundant FBM231 and FBM233, the confirmation dialog box prompts
selection of either the Main or Backup module for the reset.
Software Download
The Software Download action is only available for the FDSI modules:
FBM230, FBM231, FBM232 and FBM233.
The action downloads the I/O Device Driver (.ziph) to the FBM and restarts
the FBM logic. For the redundant FBM231 and FBM233, the confirmation
dialog box prompts selection of either the Main or Backup module for the
driver download.
See I/A Series System Field Device System Integrators (FBM230/231/232/233)
User’s Guide (B0700AH) for details.
DB Download
The DB Download action updates port configuration files in the following
FBMs:
• Profibus: FBM223 and FBM222
• Modbus: FBM224
• FDSI modules: FBM230, FBM231, FBM232 and FBM233
• APACS+ DCS Fieldbus Modules: FBM234, FBM235, FBM236 and
FBM237
For the redundant modules, the configuration database is downloaded to the
Master module, which in turn updates the Tracker module. For details on the
DB Download action refer to the maintenance section of the appropriate FBM
user guide:
• I/A Series System Field Device System Integrators
(FBM230/231/232/233) User’s Guide (B0700AH)
• PROFIBUS-DP Communication Interface Module (FBM223) User’s
Guide (B0400FE)
• Implementing Profibus Networks in Foxboro Control Software
Applications (B0750BE)
• Modbus Communication Interface Module (FBM224) User’s Guide
(B0400FK)
• DCS Fieldbus Modules for Moore APACS+ Systems (B0700BK)
Switch Roles
For some DCI based FBMs, two modules are installed for redundant operation
with one module taking control (the Master role) and the other playing the role
of Tracker, ready to assume control if there is a failure with the Master. The
module with the lower system network address is identified in System
Manager as Main, while the second module is referred to as Backup. When
both modules are on line, you can assign the Master role to either.
The Switch Roles action can be selected for the following FBMs:
• FBM216 and FBM218 HART Interfaces
• FBM222 Profibus Interfaces
• FBM228 FOUNDATION fieldbus interface (when installed as a redundant
pair and defined with an ECB202)
• FBM231 and FBM233 FDSI modules
To switch the module roles for a redundant FBM:
1. Right-click the FBM in the Navigation pane and choose Switch Roles
from the context menu.
The Switch Roles dialog box displays the operating mode for each module
(Figure 8-12).
Note that the first time you use this function, you must expand the
FBM222 or FBM228 in order to enable or disable communications for
multiple devices. If the FBM222/228 is not expanded the first time, the
following message appears:
3. If no device is selected from the list view, the following message appears:
If there are any devices attached to the FBM that are off-line, System
Manager displays the Enable Communications dialog box (Figure 8-18):
The Enable Communications dialog box can also be opened from the
Connections tab in the Information pane, as discussed in the next section.
Click the check box for individual devices or click Check All, and then
click Start. If all devices are already on line, System Manager displays a
dialog box displayed in Figure 8-19.
2. Disable Control for Multiple Devices works the same way as the Enable
Control equipment change action. The command opens a Disable
Communications dialog box when there are devices on control and shows
a dialog box advising All the devices are off-line when there are no
devices on control.
Device Displays
Do one of the following to display detailed status and equipment information
for a device:
• Select the device in the Navigation pane.
• Right-click the device listed in the Connections tab for the FBM in the
Information pane, and choose Navigate to <device name> from the
context menu.
The Information pane General tab includes an Equipment Status display and an
Equipment Information table.
The information displays and context menus for device ECBs attached to the
DCI based FBMs vary with the supported fieldbus technology. Refer to the
System Management section of the individual FBM user guide for a
comprehensive discussion regarding information provided by these displays.
For the DeviceNet FBM229’s device display, refer to the “Device Information
Displays” section in Implementing a DeviceNet Network on the I/A Series
System (B0750CH).
Device Actions
The following commands are available from the context menu of a device:
• Acknowledge Device when there is an unacknowledged alarm.
• Inhibit Device Alarming (when alarms are enabled) to disable
communication of alarms generated by the device.
System Manager marks any unacknowledged alarm from the device as
acknowledged, and places the symbol next to bottom left corner of the
device icon to indicate that alarms are being inhibited.
• Enable Device Alarming (when alarms are inhibited) to re-enable
communication of alarms generated by the device.
System Manager clears the symbol from the bottom left corner of the
device icon.
• Enable Control/Communications (when the device is off-line) to enable
communications between the FBM and the device and place the device on
control.
A dialog box prompts you to confirm the action (Figure 8-21):
The TRICON Main Chassis Diagnostics display, shown in Figure 8-24, allows
you to observe the diagnostic status of each chassis in a TRICON system.
3. The following warning message will appear if there is an error opening the
FoxView Diagnostic Display.
Figure 8-27 shows the Information pane for a Triconex device attached to an
FDSI FBM. A bit in the DDIAG1 device status determines the presence of the
Triconex Device in Alarm state field.
C H A P T E R 9
Networking Equipment
This chapter describes how to use the System Manager application to monitor
and control switches and switch ports in The Mesh Control Network.
Contents
• Identifying Switches in the Navigation Pane
• Switch Status and Equipment Information
• Connected Stations and Switches
• Ports Tab
• Equipment Change Actions
Labels on the right side of the switch icon indicate the state of communications
between the switch and stations and switches in its domain:
Symbol Condition
The RCVR label attached to the right side of the switch icon
indicates a receiver failure for one or more stations in the switch
domain.
• Select the switch and use the Connections tab in the
Information pane to identify the station with an A channel or
B channel receiver fault.
The fault is marked on the lower right corner of the station icon
with or .
The RCVR error on the switch cannot be cleared by inhibiting or
acknowledging the alarm. The RCVR error will remain on the
switch until all the receiver faults for that station(s) in the switch
domain are fixed.
• Right-click the switch and choose Navigate to <switch name> from the
context menu.
The switch is selected in the Navigation pane and its equipment
information is displayed in the Information pane.
Field Description
Name The station letterbug assigned during system
hardware definition
Type Type of hardware specified when the letterbug
was defined
SMON System monitor domain to which the station is
assigned
SMON Host Host station for the system monitor
Manufacturer Original equipment manufacturer
IP Address I/A Series station network address
Switch Connections Number of other switches connected to the
switch
Failed State Failed or Not Failed
Run Mode Displays either On-Line or Off-line
Alarming State Indicates whether alarming is Enabled or
Inhibited for this switch
Field Description
Failed Acknowledged Indicates whether the last reported failed state
State was acknowledged. To acknowledge the failed
state:
• Right-click the switch in the Navigation
pane and choose Acknowledge Station
from the context menu.
See “Equipment Change Actions” on page 245
for information on acknowledging switch
alarms.
Failed Devices No if there are switch port failures that have not
Acknowledged been acknowledged; otherwise, Yes. To
acknowledge a switch port failure:
• Right-click the failed port in the Ports tab in
the Information pane and choose
Acknowledge Device from the context
menu.
See “Ports Tab” on page 241.
Failed Devices Attached Yes if a switch port has failed or is off-line;
otherwise, No. To review the status of individual
ports:
• Click the Ports tab in the Information pane.
See “Ports Tab” on page 241.
Station Address The six-octet media access control (MAC)
address assigned during system definition and
used by the networking protocol in the
I/A Series stations
Reporting State Indicates whether status of the switch and its
ports is being reported to the system monitor. To
change the Reporting State:
• Right-click the switch in the Navigation
pane and choose Disable All Reports or
Enable All Reports from the context menu.
2. Click a column header to sort the rows in the table on the data in that
column. Click the column header a second time to reverse the sort order.
3. Drag a column header to the right or left to rearrange the column order.
4. Do one of the following to go to a connected station or switch:
• Double-click the equipment name.
• Right-click the equipment name and choose Navigate to <equipment
name> from the pop up menu (Navigate to AWSM02 in Figure 9-3).
The equipment is selected in the Navigation pane, and displayed in the
Information pane. If there are items connected to the new selection, the
Connections tab is shown in the Information pane; otherwise, the General
tab is displayed.
Ports Tab
To review information about a specific switch port:
1. Click the Ports tab in the Information pane to display the Ports tab
(Figure 9-4).
The Switch Ports pane at the top of the Ports tab displays the status of each port
in the selected switch using the icons and symbols listed in the following table:
Symbol Condition
The port is on-line, alarming is enabled and there are no
unacknowledged alarms associated with the port.
Field Description
Name Port name (P01 for example)
Type Port type, Switch Port
Run Mode On Line or Off Line
Device State Failed if the port is failed; otherwise, Not Failed
Failed Acknowledged if the last port failure (Device State is
Acknowledged State Failed) has been acknowledged; otherwise, Not
Acknowledged. To acknowledge a failed port:
• Right-click the port name in the Switch Ports pane
and choose Acknowledge Device from the
context menu.
Alarming State Whether alarming for the port is Enabled or
Inhibited. To change the Alarming State:
• Right-click the port name in the Switch Ports pane
and choose Inhibit Device Alarming or Enable
Device Alarming from the context menu
(Figure 9-4).
Inhibiting alarms acknowledges any unacknowledged
alarms for the port.
Warning Condition Yes if the port has a non-fatal error condition;
otherwise, No
Comm State OK or Failed
Number Port number
Admin State Port Enabled or Port Not Enabled
Current Sate Port Running or Port Not Running
Interface State Indicates the communications protocol in use by the
port
Port Position Physical location of the port, usually the same as the
port number
Port Counters
The Counters tab for a switch consists of the Switch Ports display used in the
upper half of the Ports tab and a table of counters for the port selected in the
Switch Ports display (Figure 9-5).
As with the Counters tab for other equipment, the buttons in the tab toolbar
enable you to read counters for the selected port, and add counters to the list in
the Accessories pane Watch tab. However, unlike the tabs for other equipment,
the reset buttons are not enabled as switch port counters cannot be reset from
System Manager. See “Counters Tab” on page 44 and “Watch Tab” on page 53
for additional information on using the Counters and Watch tabs, respectively.
The switch ports counters are described in the following table:
Table 9-3. Switch Port Counters Display Fields
Counter Description
Broadcast PKTS Number of broadcast packets that were transmitted to all
stations.
Collisions Number of collisions experienced by the controller chip
during transmission attempts. This number should be
zero (0) on The MESH switches.
CRC Align Errors Number of properly aligned frames received with CRC
errors. This number should be non-incrementing.
Counter Description
Drop Events The number of times packets that were dropped because
the device could not keep up with the flow of traffic on
the network. The number reflects the number of times
packets were dropped, not the number of packets.
Fragments The number of packets that were undersized (less than
64 bytes) and had either a non-integral number of bytes
(alignment error) or a CRC error.
Jabbers The number of packets that were oversized (greater than
1518 bytes) and had either a non-integral number of
bytes (alignment error) or a CRC error.
This number should be 0 with Ethernet switches.
Multicast PKTS Number of multicast packets that were transmitted.
Octets Number of octets that were transmitted.
Oversize PKTS Number of packets that were greater than 1518 octets.
PKTS Number of packets that were transmitted.
PKTS <range> Number of packets of the specified size that were
Octets transmitted.
Undersize PKTS Number of packets that were less than 64 octets.
Switches
When a switch is selected, the following commands are available from the
equipment’s context menu and from the Actions > Equipment Change
submenu pulled down from the main menu:
• Acknowledge Station
Acknowledges device alarms related to the switch. This command is
displayed only when there is an unacknowledged alarm.
• Inhibit Device Alarming/Enable Device Alarming
Inhibits/enables reporting of switch alarms to the system monitor.
• Disable All Reports/Enable All Reports
Disables/enables all internal reporting from the switch, including the
status of individual ports, to the assigned system monitor.
Ports
When a port number is selected in the Ports tab, the following commands are
available from the port’s context menu:
• Acknowledge Device
A P P E N D I X A
Module Description
FBP11 UCM Spectrum Migration Interface
FBP11R Redundant UCM Spectrum Migration Interface
3A2-V2D High Level, Isolated
3A2-V3D High Level
3A2-E2D ac Voltage Input
3A2-I2D Current Input, Isolated
3A2-I2DA High Level, Isolated
3A2-I3D Current Input
3A2-I3DA High Level
3A2-H3D High Level
3A4-I2D Quad Current Input
3A2-M2D MV/TC Adj Range
3A2-T2DJ1 Thermocouple Input
3A2-T2DJ2 Thermocouple Input
3A2-T2DK1 Thermocouple Input
3A2-T2DK2 Thermocouple Input
3A4-M2DA1 Millivolt/TC Input
3A4-M2DA2 Millivolt/TC Input
3A4-M2DA3 Millivolt/TC Input
3A4-M2DA4 Millivolt/TC Input
3A4-M2DA5 Millivolt/TC Input
Module Description
3A4-M2DA6 Millivolt/TC Input
3A4-M2DA7 Millivolt/TC Input
3A2-R2DC Copper RTD
3A2-R2DN Nickel RTD
3A2-R2DP Platinum 1 RTD
3A2-R2DP Platinum 2 RTD
3A2-R2DP Platinum 3 RTD
3A2-R2DP2 Platinum RTD
3C8-C3D Octal Contact Input
3C8-E2D Octal Line V Mon
3A2-F2D Pulse Rate Counter
3A2-Q2D Pulse Input Count
3A2-D3V Dual Voltage Output
3A2-D2I Dual Current Output
3A2-D3I Dual Current Output
3C4-D2CS DC Switch Output
3C4-D2KS AC Switch Output
3C8-D2CS Octal Contact Output
3C4-D2VS dc Volt Output
3C4-D2CP dc Pulse Output
3C4-D2KP ac Pulse Output
3C4-D2VP dc Pulse Output
3AS-I2I Single Loop I/O
3AS-I3I Single Loop I/O
3AD-I3I Dual Loop I/O
3A2-V2D High Level, Isolated
3A2-V3D High Level
3A2-E2D ac Voltage Input
3A2-I2D Current Input, Isolated
3A2-I2DA High Level, Isolated
3A2-I3D Current Input
3A2-I3DA High Level
3A2-H3D High Level
FBP12 FIO Spectrum Migration Interface
3F8-V2DA1 Octal High Level
3F8-V2DA2 Octal High Level
3F8-V2DA Octal High Level
3F4-I2D1A Quad 0 to 20 mA dc, 16V
Module Description
3F4-I2D2A Quad 0 to 20 mA dc, 22V
3F8-I2DA Octal High Level
3F8-H2DA Octal High Level
3F8-T2DA1 Octal Thermocouple
3F8-T2DA2 Octal Thermocouple
3F8-T2DA3 Octal Thermocouple
3F8-T2DA4 Octal Thermocouple
3F8-T2DA5 Octal Thermocouple
3F8-T2DA6 Octal Thermocouple
3F8-T2DA7 Octal Thermocouple
3F8-M2DA1 Octal Millivolt
3F8-M2DA2 Octal Millivolt
3F8-M2DA3 Octal Millivolt
3F8-M2DA4 Octal Millivolt
3F8-M2DA5 Octal Millivolt
3F8-M2DA6 Octal Millivolt
3F8-M2DA7 Octal Millivolt
3F8-R2DCA Octal RTD (Copper)
3F8-R2DNA Octal RTD (Nickel)
3F8-R2DPA1 Octal RTD (Platinum 1)
3F8-R2DPA2 Octal RTD (Platinum 2)
3F8-R2DPA3 Octal RTD (Platinum 3)
3F8-C2DCA Octal Contact
3F8-C2DNA Octal Prox Sensor
3F8-E2DA Octal HL Digital
3F4-F2DA Quad Pulse Rate
3F4-Q2DA Quad Pulse Counter
3F4-D2VA Quad High Level Output
3F4-D2IA Quad High Level Output
3F8-D2CSA Octal dc Switch
3F8-D2ZA Octal Solenoid Dvr
3F8-D2KSA Octal ac Switch
3F4-D2WA Quad Solenoid Dvr
3F8-D2CPA Octal dc Pulse Sw
3F8-D2KPA Octal ac Pulse Sw
3F8-V2DA1 Octal High Level
3F8-V2DA2 Octal High Level
3F8-V2DA Octal High Level
Module Description
3F4-I2D1A Quad 0 to 20 mA dc, 16V
3F4-I2D2A Quad 0 to 20 mA dc, 22V
3F8-I2DA Octal High Level
3F8-H2DA Octal High Level
3F8-T2DA1 Octal Thermocouple
3F8-T2DA2 Octal Thermocouple
3F8-T2DA3 Octal Thermocouple
3F8-T2DA4 Octal Thermocouple
3F8-T2DA5 Octal Thermocouple
3F8-T2DA6 Octal Thermocouple
3F8-T2DA7 Octal Thermocouple
3F8-M2DA1 Octal Millivolt
3F8-M2DA2 Octal Millivolt
3F8-M2DA3 Octal Millivolt
3F8-M2DA4 Octal Millivolt
3F8-M2DA5 Octal Millivolt
3F8-M2DA6 Octal Millivolt
3F8-M2DA7 Octal Millivolt
3F8-R2DCA Octal RTD (Copper)
3F8-R2DNA Octal RTD (Nickel)
3F8-R2DPA1 Octal RTD (Platinum 1)
3F8-R2DPA2 Octal RTD (Platinum 2)
3F8-R2DPA3 Octal RTD (Platinum 3)
3F8-C2DCA Octal Contact
3F8-C2DNA Octal Prox Sensor
3F8-E2DA Octal HL Digital
3F4-F2DA Quad Pulse Rate
3F4-Q2DA Quad Pulse Counter
3F4-D2VA Quad High Level Output
3F4-D2IA Quad High Level Output
3F8-D2CSA Octal dc Switch
3F8-D2ZA Octal Solenoid Dvr
3F8-D2KSA Octal ac Switch
3F4-D2WA Quad Solenoid Dvr
3F8-D2CPA Octal dc Pulse Sw
3F8-D2KPA Octal ac Pulse Sw
FBP13 UFM Spectrum Migration Interface
3A8-V2D1 Octal High Level
Module Description
3A8-I2D1 Octal High Level
3A8-M2D1 Octal Millivolt
3A8-M2D2 Octal Millivolt
3A8-M2D3 Octal Millivolt
3A8-T2D1 Octal Thermocouple
3A8-T2D2 Octal Thermocouple
3A8-T2D3 Octal Thermocouple
3A8-R2DC1 Octal RTD (Copper)
3A8-R2DN1 Octal RTD (Nickel)
3A8-R2DP1 Octal RTD (Platinum 1)
3A8-R2DP2 Octal RTD (Platinum 2)
3A8-R2DP3 Octal RTD (Platinum 3)
3D8-C2D1 Octal Contact
FBP14 UIO Spectrum Migration Interface
Module Description
S2BM04 Spec200 0 to 10 V dc I/O
S2BM17 Spec200 0 to 10 Volt
S2MM09 Extended Control Integrator
S2MM17 Basic Control Integrator
Module Description
F1M01A/C/E/F Analog Input
F1M02 Analog Input
F1M03 Analog Input, 4 RTD
F1M04A/B Analog Output
F1M06 Pulse Input
F1M07 Discrete Input
F1M09 Digital Output
F1SFIA/B Fieldbus Isolator
Module Description
F2M214 Analog HART Input FBM
F2M215 Analog HART Output FBM
F2M239 Discrete I/O FBM
F2DFBI Dual Baud Fieldbus Isolator, installed in F2DFBC Dual
Baud Fieldbus Isolator Carrier Board
F2M67A Discrete FBM (Replaced by F2M239)
(Legacy)
F2M68A Analog I/O FBM (Analog inputs replaced by F2M214,
(Legacy) analog outputs replaced by F2M215)
F2SFBI Fieldbus Isolator
FRM701 Configurable Controller FBM
FRM711 Computing Controller FBM
FRMMPU Integrator for Fisher Interactive Controller
Module Description
H2C02A,B,D-H,J-N,P-Z Analog Input
H2D02A-E,G,H Analog Input
H2J02A-H Analog Input
H2M01A,B,C,D Analog Input
H2M02A,B,E Analog Input
H2M03A-G Analog Input
H2M04 Analog Output
H2M06, 6A Pulse Input
H2M07,7E Digital Input
H2M09 Digital Output
H2M17 AI/AO/DO
H2M24 Digital Input
H2M26 Digital Output
H2SFBI, H3SFBI Fieldbus Isolator
H2V02B-R Analog Input
H3M01 Analog Input
H3M02A DCS Integrator Kit
H3M02B DCS Integrator Kit
H3M03 Analog Input
H3M04 DCS Integrator
Module Description
H3M06 Pulse Input
H3M07 Digital Input
H3M09 Digital Output
H3M37 Analog Output
H3SFBI DCS Fieldbus Isolator
Module Description
BAMM01 Analog Input
BAOM37 Analog Output
BASIO1 Analog Input
BASIO3 Analog Input
BASM01 Analog Input
BASM02 Analog Input
BASM03 Analog Input
BASM33 Analog Input
BASO37 Analog Output
BCOM17 AI/DI/AO/DO
BDSI07 Discrete Input
BDSM06 Pulse Input
BDSM09 Discrete Output
BDSM09A Discrete Input
BDSM09B Discrete Input/Output
BDSO10 Discrete Output
BDSO26 Discrete Output
BDSO41 Discrete Output
BSEM01 Discrete Input
BSBE2 Fieldbus A/B Switch
BFBI Fieldbus Isolator
Module Description
WAH01 Analog Input
WAI02A Thermocouple Input
WAI01 Analog Input
WAO37 Analog Output
WAV02A Thermocouple Input
WAW01 Analog Input
WAX01 Analog Input
WAX02A Thermocouple Input
WBO09 Discrete Output
WCI07A Contact Input
WDI07 Contact Input External
WID07 Contact Input
WLJ04 Analog I/O
WPA06A Pulse Accumulator
WRF03 RTD Input
WRO09 Relay Output
WRT03 RTD Input
WTO09 TRIAC Output
Following are the Fieldbus Cluster I/O modules supported by System Manager
software. Refer to B0193RB.
Table A-7. Fieldbus Cluster I/O Modules
Module Description
FBP10 Fieldbus processor
FBP10R Redundant Fieldbus Processor
FBC01 0 to 20 mA Input - 32
FBC01R 0 to 20 mA Input - 32 - Redundant
FBC02 T/C Input -32
FBC04R 0 to 20 mA Output – 16 - Redundant
FBC07A 24 Volt dc Inputs – 32
FBC07A/R 24 Volt dc Inputs – 32 - Redundant
FBC07B Contact Input - 32
FBC07B/R Contact Input – 32 - Redundant
FBC09 Contact Output – 32
Module Description
FBC09R Contact Output – 32 - Redundant
FBC10 Digital Input/Output - 64
FBC17 0 to 10 Volt Digital Input - 32
FBC17R 0 to 10 Volt Digital Input - 32 - Redundant
FBC21 0 to 20 mA Input - 16
FBC21R 0 to 20 mA Input – 16 - Redundant
A P P E N D I X B
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.
The system updates this field when a status change occurs.
Off-line status:
• Check hardware.
• Download, if necessary.
• Check related fields (DOWNLOAD and EEPROM UPDATE).
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.
The following actions change this field to Failed:
• You physically disconnect the port.
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.
The system updates this field when a status change occurs.
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 Integrated Control Configuration.
ECHO ENABLED
Indicates the echo mode as either enabled (Yes) or disabled (No). You set this
value during integrated control configuration.
RETRY COUNT
The number of times a device tries to re-send a message before timing out. The
range of configurable 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.
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 Integrated 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.
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.
The system updates this field when a status change occurs.
If the status is Off-line:
• Check hardware.
• Download, if necessary.
• Check related fields (DOWNLOAD and EEPROM UPDATE).
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
• A hardware problem causes the station to fail for more than two
minutes.
• 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 off-line diagnostics 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.
If the status is Failed:
• Check Printer/Terminal/CPU hardware.
• Check communication path with parent station.
• Check configuration information.
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.
The system updates this field when a status change occurs.
TYPE
Redundant ECB Selected (Black)
RUN MODE
On-Line. The ECB24 is placed On-Line when it is created and cannot be
placed Off-Line. However, requesting “GO OFF LINE” through the
EQUIPMENT CHANGE page for the AW51RS that is in the CTL state forces
a switch to the other AW51RS in the redundant pair, if it is in the TRK state at
the time of the request.
FAIL STATE
Failed or Not Failed. An ECB24 is in the normal, Not Failed state when the
two AW51RSs in the redundant pair are able to communicate with each other
normally. When there is a failure in these inter-processor communications, the
ECB24 is Failed.
ALRMING STATE
Indicates whether alarming is Enabled or Inhibited for the Device. When
alarming is inhibited, the System Monitor continues to indicate overall system
and network health (a green “SYS BAR”) while equipment is failed or off-line.
System Alarm messages are not logged to the system printer, nor the Historian.
LAST SWITCH
Successful or Unsuccessful last switch of control between the two AW51RSs.
HARDWARE TYPE
41 for ECB24.
SOFTWARE TYPE
24 for ECB24.
ALT LETTERBUG
Physical letterbug of the other AW51RS in the redundant pair.
OPERATION STATE
CTL, SBY, TRK, or SBY/FAIL
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 Offline 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
communication 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.
The system updates this field when a status change occurs.
Off-line status:
• Check hardware.
• Download, if necessary.
• Check related fields (DOWNLOAD and EEPROM UPDATE).
FAIL STATE
Failed or Not Failed (initial setting). This field updates when a status change
occurs. The following 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 peripheral hardware.
• Download, if necessary.
• Check INTERSPEC bus and INTERSPEC device.
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.
The system updates this field when a status change occurs.
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.
DIAG STATUS 2
Diagnostic Status 2 indicates the electrical status of Port 2 communications.
SOFTWARE REV
This field is not applicable to the INTERSPEC Integrator Translator.
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 System Monitor after booting up. You can change the RUN
MODE using the GO ON-LINE and GO OFFLINE 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.
• 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.
DEVICE STATE
Failed or Not Failed. This field is initially Not Failed. This field changes to
Failed if any of the following 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.
• A physical pull/push of the station (requiring more than two minutes
to come back on-line) is performed.
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 (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.
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
On-line or Off-line (default). This value changes to On-line when the station
reports to the System 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. 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
• 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 (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
• A hardware problem causes the station to fail for more than two
minutes
• You pulled/pushed the station, and it required more than two minutes
to come back on-line
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.
The system updates this field when a status change occurs.
If the state is Not Responding or Not Acknowledged, check hardware.
PLC MODE
Displays the PLC mode, as follows:
• RUN Mode: The PLC is running the ladder program and is driving the
outputs.
• 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.
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.
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.
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.
NAME
Letterbug assigned to the A-B Rack.
TYPE
A-B Rack.
RUN MODE
On-line or Off-line (default). This value changes to On-line when the station
reports to the System Monitor after booting up. You can change the RUN
MODE using the GO ON-LINE and GO OFFLINE 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.
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
• A hardware problem causes the station to fail for more than two
minutes
• 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.
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.
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.
The system updates this field when a status change occurs.
If the state is Not Responding or Not Acknowledged, check hardware.
RACK FAULT
Displays Yes if the rack configuration is correct; otherwise, displays No.
RACK INHIBIT
Displays Yes if the rack is inhibited; otherwise, displays No. If the rack is
inhibited, the A-B Station 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.
TYPE
Identifies the type of Modbus device as follows: MODBUS PIOM (ECB60);
MODBUS PLC (ECB61); MODBUS SCAN (ECB62).
RUN MODE
On-line or Off-line (default). This value changes to On-line when the station
reports to the System Monitor after booting up.
DEVICE STATE
Failed or Not Failed. This field is initially Not Failed.
ALARMING STATE
Indicates whether alarming is Enabled or Inhibited for the device.
HARDWARE TYPE
100 (ECB60); 101 (ECB61); 102 (ECB62).
SOFTWARE TYPE
60 (ECB60); 66 (ECB61) or 62 (ECB62).
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.
TYPE
Identifies the type of AB-PIO device as AB PRIMARY IO.
RUN MODE
On-line or Off-line (default). This value changes to On-line when the station
reports to the System Monitor after booting up.
DEVICE STATE
Failed or Not Failed. This field is initially Not Failed.
ALARMING STATE
Indicates whether alarming is Enabled or Inhibited for the device.
HARDWARE TYPE
Number, 123, associated with the peripheral 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.
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.
TYPE
Identifies the type of GE-PIO device as GE PRIMARY IO.
RUN MODE
On-line or Off-line (default). This value changes to On-line when the station
reports to the System Monitor after booting up.
DEVICE STATE
Failed or Not Failed. This field is initially Not Failed.
ALARMING STATE
Indicates whether alarming is Enabled or Inhibited for the device.
HARDWARE TYPE
Number, 113, associated with the peripheral 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
This field is not currently supported.
MANUFACTURE DATE
This field is not currently supported.
EROM REVISION
This field is not currently supported.
SERIAL NUMBER
This field is not currently supported.
SOFTWARE REVISION
This field is not currently supported.
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.
TYPE
Identifies the type of AB-RIO device as AB-RIO ADAPTER.
RUN MODE
On-line or Off-line (default). This value changes to On-line when the station
reports to the System Monitor after booting up.
DEVICE STATE
Failed or Not Failed. This field is initially Not Failed.
ALARMING STATE
Indicates whether alarming is Enabled or Inhibited for the device.
If the status is Yes, one or more of the attached peripherals have failed. Verify
status of peripherals.
HARDWARE TYPE
Number, 114, associated with the peripheral 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.
TYPE
GE-IO Mod B AI and AB-IO Mod 4 AO
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.
The system updates this field when a status change occurs.
DEVICE STATE
Failed or Not Failed.
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.
The system updates this field when a status change occurs.
If the state is Not Responding or Not Acknowledged, check hardware.
COMPOUND NAME
PORT3 and PORT4
BLOCK NAME
GE4752 and TS5783
HARDWARE TYPE
123
FAULT BYTE
Only A-B I/O analog devices report per channel faults in the FAULT BYTE
field. If a channel is not set active, the fault byte information is not set.
Each bit represents one channel. Bit 0 (the right-most bit on display) is channel
1 (0 on the module).
The following can be displayed in the FAULT BYTE field:
MODULE NUMBER
This value, 1 through 8 inclusive, indicates the position of the GE I/O module
with regard to the GE Fanuc bus device, with Module 1 being the closest to the
field interface cable.
This value, 1 to 8 inclusive, defines the position of the module with regard to
the RIO adapter. Module 1 is the closest to the AB-RIO adapter, and Module 8
is the furthest away.
ERROR CODE
This field is normally 0. If an error is detected in the GE I/O module, this field
is set to a nonzero value.
TYPE
Shows the type of station defined when the letterbug is assigned during System
configuration.
RUN MODE
On-line. This field is always on-line (ECB96 is always on line) when the
station reports to the System Monitor.
DEVICE STATE
On Scan or Not Ready. This field is initially On Scan.
This field changes to Not Ready if any of the following occur:
ALARMING STATE
Indicates whether alarming is Enabled or Inhibited for the device. When
alarming is Inhibited, the System Monitor continues to indicate overall system
and network health (a green “SYS BAR”) while equipment is failed or off-line.
System Alarm messages are not logged to the system printer, nor the Historian.
COMPOUND NAME
The name of the compound that contains the ECB96. Database.
BLOCK NAME
The text string configured (with ICC) for the ECB96’s NAME parameter. This
name is used by all I/O blocks (in their IOM_ID parameter) to reference the
device.
HARDWARE TYPE
158 (as configured with the ICC for ECB96).
SOFTWARE TYPE
Zero (as configured with the ICC for ECB96).
PORT FLAGS
Indicates type and status of data exchange. Currently the flags are:
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 system, but
in an asynchronous fashion. If this flag is not set, if a solicited 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.
DEVICE STATUS
Exception error code sent by the device in a reply message.
Code
Number Meaning
1 Normal – No error
2 No communications event
present
are not possible) and is not eliminated by a hardware reset of the AW70,
replace the communications card.
If the condition happens often, but is not debilitating, report it to you Foxboro
Service Representative
MESSAGE SENT
Number of messages sent from this message exchange since the last time the
MEX was allocated, or the statistics were initialized
WAIT MESSAGE
Number of message blocks waiting for 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 which this server attempted to send out more messages than
allowed by its reserved buffer count
WAIT RESPONSES
Number of responses being waited for by the current service
NO BUFFERS
Number of times that an allocate buffer or send message was refused due to a
lack of buffers in the system. This field 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 is expecting a response to a
previously sent message
LOCK ERROR
Number of times that a conflict has occurred locking this message exchange
USED BUFFERS
Number of buffers currently reserved for use by the message exchange (task).
In general, the number of buffers cannot exceed the maximum buffer count;
however, exceptions can arise during peak communications loading
TYPE
BB RTU. Shows type of station defined when the letterbug is assigned during
System configuration.
RUN MODE
On-line or Off-line. This field is initially off-line. It changes to on-line when
the station, after booting up, reports to the System Monitor. If reporting is
disabled, the last known state appears in this field.
RUN MODE and DEVICE STATE should be viewed as separate, but related
fields. 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.
• An off-line diagnostic request.
• Any station hardware failure or communication failure that results in
the station not able to send its internal reports for two or more
minutes.
DEVICE STATE
On Scan or Not Ready. This field is initially Not Ready. This field changes to
Not Ready if any of the following occur:
• A hardware problem causes the station to fail for more than two
minutes.
• Any station hardware failure or communication failure that 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 DEVICE STATE to Not Ready.
in the top menu bar of the initial System Management Display to acknowledge
all the unacknowledged devices for which the workstation has responsibility.
ALARMING STATE
Indicates whether alarming is Enabled or Inhibited for the device. When
alarming is Inhibited, the System Monitor continues to indicate overall system
and network health (a green “SYS BAR”) while equipment is failed or off-line.
System Alarm messages are not logged to the system printer, nor the Historian.
COMPOUND NAME
AWNT01_ECB. Name of the compound that contains the ECB97.
BLOCK NAME
Text string configured (with ICC) for the ECB97’s NAME parameter. All I/O
blocks use this name (in their IOM_ID parameter) to reference the device.
HARDWARE TYPE
159 (as configured with the ICC for ECB96).
SOFTWARE TYPE
Zero (as configured with the ICC for ECB96).
PORT STATUS
Flags indicating current status of the current RTU:
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 synch message.
0x04= PORT_DEAD
Set when the current RTU will not accept messages.
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.
PORT FLAGS
Flags indicating the options used for the current RTU:
0x01= LOCAL SLAVE
Direct 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
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.
READ TIMEOUTS
Read Time-outs on Send/Receive
WRITE TIMEOUTS
Write Time-outs on Send/Receive
BUFFER OVERFLOW
Input character buffer overflowed before receiving the end of message
sequence.
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 in an incoming message.
INVALID ACK
An ACK message has been received when one was not expected, or the
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 TIMEOUTS
Number of times that a messages ACK has not returned within the time
interval allowed.
DIAL OK
Available only on systems which support dial-up. It is the number of times that
this RTU has successfully been connected via a dial operation.
DIAL FAIL
Available only on systems which support dial-up. It is the number of times that
a dial operation failed to the current RTU.
OUT QUEUE
Number of messages waiting to be sent to this RTU. Note: When using direct
connect BSAP, this field is only maintained for the first slave on the
communication line.
RETRY COUNT
Number of attempts which have been made to send the current message out of
the communication port. For direct connect BSAP, this field is only maintained
on the first slave on the communication line.
TYPE
Always FoxGuard Monitor based on the ECB hardware type parameter
(HWTYPE).
RUN MODE
The FoxGuard Manager mode is either on-line or off-line.
DEVICE STATE
Indicates whether the Advanced Communications Module has failed.
ALARMING STATE
Indicates whether device alarming to the Nodebus level has been enabled or
inhibited. Device alarming can be enabled or inhibited with the Equipment
Change overlay.
WARNING CONDITION
Yes indicates that there is a warning condition concerning the FoxGuard
Manager hardware, either Power Supply Failure or Maintenance Required.
COMPOUND NAME
Name of the ECB compound, <letterbug>_ECB, where letterbug is the
letterbug of the DNBI.
LOGICAL ADDRESS
This field is not used in the FoxGuard Manager.
BLOCK NAME
TRICON_ECB, the block name of the FoxGuard Monitor ECB.
HARDWARE TYPE
The ECB85 hardware type is 142.
SOFTWARE TYPE
The software type of the FoxGuard Monitor ECB is always 285.
DEVICE STATUS
Reserved for future use.
WRITE PROTECT
Indicates whether the Advanced Communications Module is configured in the
TRICON as a read-only module or as a read/write module.
PROGRAM MODE
Reports the current state of the TRICON control program as Running, Halted,
or Paused.
KEY SWITCH
Indicates the front panel key switch position on the TRICON main chassis as
Remote, Run, Program, or Stop.
MAJOR VERSION
Name of the current TRICON control program downloaded from the
TRISTATION.
NODE NUMBER
Node number of the TRICON main chassis in a networked system. Node can
be 1 through 10. A stand-alone TRICON is 0.
MAINTENANCE REQ
Yes, if at least one TRICON module has reported a fault.
MINOR VERSION
Version number of the TRICON control program. The version number is
incremented by one each time the program is downloaded from the
TRISTATION.
SCAN TIME
The time allocated by the control program for the TRICON to scan its I/O
modules and execute one cycle of the control program.
RUN MODE
The FoxGuard Manager mode is either on-line or off-line.
WARNING CONDITION
Reserved for future use.
LOGICAL ADDRESS
This field is not used in the FoxGuard Manager.
HARDWARE TYPE
For I/O module ECBs, Hardware Type identifies the referenced
TRICON hardware are as follows:
143: discrete input, 32 points
144: discrete input, 64 points
145: discrete (pulse) input, 8 points
146: discrete output, 16 points
147: discrete output, 8 points
148: discrete output, 32 points
149: analog input, 32 points
150: analog input, 16 points
151: analog input, 64 points
152: analog input, 32 points, thermocouple
153: analog input, 16 points, thermocouple
154: analog output, 8 points
For window ECBs, Hardware Type indicates function as follows:
140: input (ECB90, ECB91, ECB92)
141: output (ECB93, ECB94, ECB95)
TYPE
Describes the ECB based on the HARDWARE TYPE parameter.
DEVICE STATE
Indicates whether the Advanced Communications Module has failed.
ALARMING STATE
Indicates whether device alarming to the Nodebus level has been Enabled or
Inhibited. Device alarming can be enabled or inhibited with the Equipment
Change overlay.
COMPOUND NAME
Name of the ECB compound, <letterbug>_ECB, where letterbug is the
letterbug of the DNBI.
BLOCK NAME
Displays the NAME parameter of the configured ECB.
SOFTWARE TYPE
Reserved for future use.
DIAG STATUS 1
Reserved for future use.
MODULE TYPE
For I/O module ECBs, displays a description of the referenced TRICON
module read from the TRICON configuration data. For FoxGuard Manager
window ECBs, this field displays the description of the block from the
MDSCRP parameter, which copies the user-configured DESCRP parameter.
DEVICE STATUS
Used with I/O module ECBs only.
Shows the status of modules in the referenced logical slots as follows:
0 No problem.
0x01 Left physical slot is empty.
0x02 Right physical slot is empty.
0x03 Both physical slots are empty.
0x04 There is an I/O module fault.
0x08 There is a load/fuse warning.
0x10 TRICON did not accept a write request packet from the FoxGuard
Manager.
0x20 An output from this ECB was the first write in the packet to be rejected
by the TRICON.
MS CODE
For I/O module ECBs, displays a model number of the referenced TRICON
module as read from the TRICON configuration data.
For FoxGuard Manager window ECBs, the codes are as follows:
ECB90 READ BOOL
ECB91 READ REAL
ECB92 READ INT
ECB93 WRITE BOOL
ECB94 WRITE REAL
ECB95 WRITE INT
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
On-line or Off-line (default). This value changes to On-line when the station
reports to the System 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. 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
The system updates this field when a status change occurs. The possible
mutually exclusive states are:
• Not Failed: The device is connected to the control strategy, though
measurements are not guaranteed to be good.
• Failed: Fatal hardware or other fatal fault reported by the device.
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.
The system updates this field when a status change occurs.
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.
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.
The possible values are as follows:
• 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.
SERVER TYPE
Identifies the type of server (IOGATE) I/A Series uses to communicate with
this ECB device.
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 accompanies 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.
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.
TYPE
User-supplied ECB type descriptor, as configured using ICC.
RUN MODE
On-Line. The ECB80 is put On-Line when it is created, and cannot be put Off-
Line.
FAIL STATE
Failed or Not Failed. The ECB80 is Failed if and only if the SCADA database
becomes inaccessible to the Control database.
There are several events that can result in failure of the ECB80. Although such
events are abnormal, and recovery from them should be automatic, if the
Failed state persists for more than a few minutes, the AW51RS should be shut
down and restarted. A failure of the ECB80 in the AW51RS that is in the CTL
state causes a switch to the other AW51RS if it is in the TRK state.
ALRMING STATE
Indicates whether alarming is enabled or inhibited for the device. When
alarming is inhibited, the System Monitor continues to indicate overall system
and network health (a green “SYS BAR”) while equipment is failed or off-line.
System Alarm messages are not logged to the system printer, nor the Historian.
TYPE
User-supplied ECB type descriptor, as configured using ICC.
RUN MODE
On-Line or Off-Line. The ECB81 is placed Off-Line when it is created and
whenever it is modified via the ICC. Thereafter, its On-Line/Off-Line state can
be changed only via the EQUIPMENT CHANGE function of the System
Manager display.
When the AW51RS is rebooted, the Run Mode of all ECBs, including the
ECB81, is whatever their Run Mode was at the time of the last database
checkpoint prior to the reboot. The Run Mode is controlled solely by the user
actions in the Control database. No operating conditions can change the Run
Mode, nor can any state changes in the SCADA database.
When an ECB81 is in the Off-Line state, all control blocks that have been
configured to access data in the RTU represented by the ECB81, or in any
equipment (such as an IT) whose ECB is parented by the Off-Line ECB81,
have their live data (i.e., inputs and outputs) marked Out of Service.
FAIL STATE
Failed or Not Failed. An ECB81 is in the normal, Not Failed state when the
RTU it represents is being polled successfully by the SCADA software, and
when the port ECB (ECB80) is Not Failed. If any operator actions or
equipment failures cause the SCADA polling of the RTU to be discontinued
intentionally or disrupted unintentionally, the ECB81 goes to the Failed state
and remains in this state until successful polling by the SCADA software is
resumed. Also, if the ECB80 goes to the Failed state, all ECB81s go to the
Failed state.
All control blocks that have been configured to access data in an RTU
represented by a failed ECB81, or in any equipment (such as an IT) whose
ECB is parented by the failed ECB81, have their live data (i.e., inputs and
outputs) marked Out of Service.
ALRMING STATE
Indicates whether alarming is Enabled or Inhibited for the device. When
alarming is inhibited, the System Monitor continues to indicate overall system
and network health (a green “SYS BAR”) while equipment is failed or off-line.
System Alarm messages are not logged to the system printer, nor the Historian.
DEVICES ATT
Indicates (yes/no) whether one or more devices are attached to this ECB.
BLOCK NAME
This identifies the block-level name for the PROFIBUS-DP ECB, as assigned
using the Integrated Control Configurator.
GATE
This identifies the number of the gate where the PROFIBUS is located.
HARDWARE TYPE
This identifies the ECB responsible for interfacing with the port
communications message control software.
BAUD RATE
This indicates the baud rate at which the bus is operating.
IDENT NUMBER
This is the identifying number of the PROFIBUS-DP as defined by the
PROFIBUS User Organization and entered through the Integrated Control
Configurator.
ERROR CODE
This field is normally 0. If an error is detected in the PROFIBUS gate
operation, this field is set to a nonzero value.
MASTER ADDRESS
This identifies the address of the Micro-I/A station that is the parent for the
PROFIBUS-DP card.
OPERATION MODE
This indicates the operational state in hexadecimal format of the PROFIBUS-
DP gate.
DP HARDWARE VER
This displays DDLM/USIF release information.
DP FIRMWARE VER
This displays DDLM/USIF release information.
BLOCK NAME
This identifies the block-level name for the PROFIBUS-DP ECB, as assigned
using the Integrated Control Configurator.
HARDWARE TYPE
This identifies the ECB responsible for interfacing with the port
communications message control software.
IDENT NUMBER
This is the identifying number of the PROFIBUS-DP device as defined by the
PROFIBUS User Organization (PROFIBUS Nutzer Organization) and entered
through the Integrated Control Configurator.
ERROR CODE
This field is normally 0. If an error is detected in the PROFIBUS-DP module,
this field is set to a nonzero value.
SLAVE ADDRESS
This identifies the unique identifier for each PROFIBUS device, which is
assigned using the Integrated Control Configurator.
MASTER ADDRESS
This identifies the address of the Micro-I/A station that is the parent for the
PROFIBUS-DP card.
DIAGNOSTIC INFO
This gives common diagnostic information. ECB103 contains specific error
information, and associated error codes, that are displayed based on analysis of
data from regular software calls.
DIAGNOSTIC EXT
This gives diagnostic information for each slave device channel. This is split
into two parts: a device part and a module/channel part. Information appearing
in this field is device dependent and information must be determined during
configuration based on vendor supplied information.
BLOCK NAME
This identifies the block-level name for the AB-PLC5/E ECB, as assigned
using the Integrated Control Configurator.
GATE
This identifies the number of the gate where the AB-PLC5/E is located.
HARDWARE TYPE
This identifies the ECB responsible for interfacing with the port
communications message control software.
DIAGNOSTIC EXT
This gives diagnostic information for each slave device channel. This is split
into two parts: a device part and a module/channel part. Information appearing
in this field is device dependent and information must be determined during
configuration based on vendor supplied information.
SERIAL NUMBER
This displays user-entered information when applicable.
BLOCK NAME
This identifies the block-level name for the AB-PLC5/E ECB, as assigned
using the Integrated Control Configurator.
HARDWARE TYPE
This identifies the ECB responsible for interfacing with the port
communications message control software.
IP ADDRESS
This identifies the address of the AB-PLC5/E. It is a 4-byte unsigned integer.
Display shows an incorrect data type.
GATEWAY ADDRESS
This identifies the address of the router assigned to the network. It is a 4-byte
unsigned integer.
BOOTP ID
This identifies the address of the starting address assigned to calling stations. It
is a 4-byte unsigned integer. It is displayed in decimal format.
NETMASK
This identifies the Gate Subnet Mask. It is a 4-byte unsigned integer. Display is
in decimal format with a period between each byte.
STATUS
This is not currently supported. It identifies the PLC5/E processor status. It is a
2-byte integer. It represents the PLC5/E Status File Word 1.
FAULT
This is not currently supported. It identifies the PLC5/E fault codes. It is a 2-
byte integer. It represents the PLC5/E Status File Word 12.
MJ FAULT
This is not currently supported. It identifies the PLC5/E major fault flags. It is
a 2-byte integer. It represents the PLC5/E Status File Word 11.
MN FAULT
This is not currently supported. It identifies the PLC5/E minor fault flags. It is
a 2-byte integer. It represents the PLC5/E Status File Word 10.
BLOCK NAME
This identifies the block-level name for the Modbus gate ECB, as assigned
using the Integrated Control Configurator.
HARDWARE TYPE
This identifies the ECB responsible for interfacing with the port
communications message control software.
GATE
This identifies the number of the gate where the Modbus is located, as assigned
using the Integrated Control Configurator.
DIAG STATUS
This indicates the status of the communications port.
GATE STATUS
This indicates the specific operational status of messages passing through the
gate. The gate may have an error specific to a message being passed or there
can be a general problem with input/output.
LOGICAL ADDR
This indicates the logical address of the gate as assigned when it is configured
using the Integrated Control Configurator BUSOPT parameter.
BLOCK NAME
This identifies the block-level name for the Modbus ECB, as assigned using
the Integrated Control Configurator.
HARDWARE TYPE
This identifies the ECB responsible for interfacing with the port
communications message control software, as assigned using the Integrated
Control Configurator.
DIAG STATUS 1
This indicates the number of misaligned frames that occurred.
DIAG STATUS 2
This indicates the number of receiver buffer overruns.
DIAG STATUS 3
This indicates the number of parity errors.
DIAG STATUS 4
This indicates the number of properly aligned frames received with CRC
errors.
DEVICE STATUS
This indicates the failure state of the device. A failure may be the result of
termination of gate activity, a user-defined event triggering an off-line state, or
server failure.
LOGICAL ADDR
This indicates the logical address of the gate, as assigned using the Integrated
Control Configurator.
A P P E N D I X C
System Messages
This section contains system messages that can appear in the System Manager
display.
Table C-1. System Manager Event Messages
A P P E N D I X D
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 interface 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.
Counter Description
DATE ACCESS Number of times read accesses occurred.
READ
DATE ACCESS Number of times write accesses occurred.
WRITE
Counter Description
DATE ACCESS Number of times read data errors occurred.
READ
ERRORS
DATE ACCESS Number of times write access error occurred.
WRITE
ERRORS
Counter Description
RDM XMIT Total number of IPC messages transmitted to alternate
COUNT gateway.
RDN RECV Total number of IPC messages received from alternate
COUNT gateway.
PROCESS Number of ABSCAN block updates transmitted to
UPDATES tracking gateway if in control mode, or the number of
messages received if in track or standby mode
RDN OM Number of one-time object sets, om-writes, or peer-to-
UPDATES 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 Number of communication errors detected in IPC link
UPDATES to alternate gateway
RDN DB Number of times that a heartbeat period (six seconds)
TIMEOUTS expired without receiving an IPC message from the
alternate gateway.
RDN RCV Number of unrecognized IPC messages received from
UPDATES alternate gateway.
RDN OM Number of one-time object sets, om-writes or peer-to-
UPDATES peer scan updates resulting in errors detected by
tracking gateway.
Counter Description
DATE ACCESS READ Number of times read accesses occurred.
DATE ACCESS WRITE Number of times write accesses occurred.
DATE ACCESS READ Number of times read data errors occurred.
ERRORS
DATE ACCESS WRITE Number of times write access error
ERRORS 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 gateway that are not due to a
time-out condition (for example, line
disconnects).
RECV TMOUT Number of errors that occurred during the receipt
of messages to the gateway due to time-outs
RSP TMOUT Number of time-out errors that occurred between
the transmission of a message 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.
Counter Description
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
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 communications 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
ERRORS Controller communications link.
BUSY ERRORS Number of times the station attempted
communications with the GE controller and
recorded an error because the controller was busy.
Counter Description
T1 EXPIRES Number of X.25 frame level T1 timer expirations.
PKT LVL TO Number of X.25 packet level time-outs (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.
Counter Description
TIMEOUTS Number of times the IIT timed out a peripheral
during communication 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.
Counter Description
SUCCESSFUL Number of messages successfully sent since the
TRANSMITS last time the statistics were initialized.
SUCCESSFUL Number of messages successfully received since
RECEIVES the last time the statistics 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 statistics 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 connection due to one of
the previous conditions.
AUXILIARY CTR Reserved for use by the application.
Table D-10. Counter Descriptions for I/O Gate ECB99 and ECB100
Devices
Counter Description
SUCCESSFUL Number of messages successfully sent since the
TRANSMITS last time the statistics were initialized.
INCOMPLETE Number of incomplete messages sent since the
TRANSMITS last time the statistics were initialized
OTHER TRANSMIT Number of errors generated during the
ERRS transmission of messages that are not due to a
time-out condition (for example, link disconnects)
SUCCESSFUL Number of messages successfully received since
RECEIVES the last time the statistics were initialized.
INCOMPLETE Number of incomplete messages received since
RECEIVES the last time the statistics were initialized.
OTHER RECEIVE Number of errors received that occurred during
ERRORS the reception of messages that are not due to a
time-out condition (for example, link
disconnects).
CHECKSUM ERRORS Number of checksum errors generated since the
last time the statistics 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.
DISCONNECTS Number of times that the link disconnected since
the last time the statistics 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 connection due to one of
the previous conditions.
Counter Description
TIMEOUTS Number of times the primary station timed out a
GE Controller during communication attempts.
PROTOCOL ERRORS Number of protocol errors generated in
communications with the 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
ERRORS Modbus communications link.
BUSY ERRORS Number of times the station attempted
communications with the Modbus controller and
recorded an error because the controller was busy.
Counter Description
TIMEOUTS Number of times the primary station timed out an
FBM during communication 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.
Counter Description
MSGS DROP Number of alarm messages that could not be
printed because the output
device failed.
Index
A
About dialog box 77
access control 5
Accessories pane 46
Alarms tab 49
hiding and showing the pane 46, 61
Inhibited tab 51
Messages tab 47
re-arranging columns 46
Smon Log tab 56
Watch tab 53
Acknowledge All Stations
Actions menu 154
Action Settings in the Configuration dialog box 64
Actions menu 66
Acknowledge All Stations 154
Download FF Devices File 82
Equipment Change 67
Set Date and Time 80
alarm status indicators
ports 241
system monitors 86
alarms
acknowledging alarms 28
acknowledging all alarms in a system monitor domain 88
control stations 141
enabling alarms 29, 51
FBMs 217
FCMs 186
inhibiting alarms 29, 51
peripherals 109
Primary ECB 161
unacknowledged and inhibited indicators 40
workstations 109
Alarms tab 49
acknowledge all alarms 49
acknowledge selected alarm 49
changing the column order 49
inhibit alarms 49
sorting alarms by equipment, acknowledge status, time 49
asterisk symbol 40
AUTO indicator
FCMs 177
Primary ECB 113
B
blinking of equipment names 40
Bus Auto Select
FCMs 190
bus switching
FCMs 190
Primary ECB 162
C
cable alarms
FBMs 217
FCMs 186
Checkpoint
control stations 142
client
description 1
Cold Start option when performing an On-line Image Update 146
color-coding of equipment names 40
communication fault indicators
FBMs 202
Configuration dialog box 61
Confirmation Required for equipment change actions 64
connected devices
FBMs 214
connected FBMs
control stations 134
FCMs 185
connected stations and switches
switches 240
Connections tab 42
system monitors 87
workstations 104
control stations 111
Checkpoint 142
connected FBMs 134
counters 165
Counters tab 136
EEPROM Update 145
Enable/Disable All Reports 142
Enable/Disable Downloads 148
Enable/Disable Uploads 148
equipment change actions 141
Image Update 145
Offline Diagnostics 149
On-line Image Update 146
Reboot 143
status and equipment information 121, 127
counters
adding counters to the Watch tab 53
Counters tab 44
control stations 136, 165
FBMs 215
functions and features 44
peripherals 108
See also Watch tab 44
switches 243
workstations 105, 165
D
data tree. See Navigation pane. 33
DB Download
FBMs 223
DCI based FBMs
status and equipment information 212
DCS Fieldbus Modules 213
DIN Rail Mounted Fieldbus Modules. See FBMs 193
Download
FBMs 219
FCMs 188
Download FF Devices File
Actions menu 82
E
ECBP. See Primary ECB 111
EEPROM Update
control stations 145
FBMs 220
FCMs 189
EEPROM update
peripherals 110
Enable blinking in the Configuration dialog box 66
Enable/Disable All Reports
control stations 142
Enable/Disable Downloads
control stations 148
Enable/Disable uploads
control stations 148
equipment change actions 66
configuration of Confirmation Required and Reason Required 64
control stations 141
FBMs 216
FCMs 186
peripherals 109
ports 245
Primary ECB 160
switches 245
workstations 109
Equipment Change menu 67
equipment icon
ports 241
switches 237
equipment icons
FBMs 200
F
FBM0. See Primary ECB 111
FBM246s
status and equipment information 211
FBMs 193
alarms 217
cable alarms 217
communication fault indicators 202
connected field devices 214
Counters tab 215
DB Download 223
Download 219
EEPROM Update 220
equipment change actions 216
equipment icon 200
Go On-Line / Go Off-Line 218
Reset FBM 222
Software Download 223
status and equipment information 202
supported modules 193
Switch Roles 223
FCMs 177
alarms 186
cable alarms 186
connected FBMs 185
Download 188
EEPROM Update (Image Update) 189
equipment change actions 186
equipment icon 177
Go On-Line / Go Off-Line 187
Select Bus A / Select Bus B / Bus Auto Select 190
status and equipment information 179
SwA / Sw B / AUTO indicators 177
Switch Roles 190
Field Communication Modules. See FCMs 177
G
General Download
Primary ECB 162
General tab 41
Go On-Line / Go Off-Line
FBMs 218
FCMs 187
Go To feature 79
H
Help 77
on-demand help 78
Help menu 77
Hierarchy Navigation 79
I
Image Update
control stations 145
FBMs 220
FCMs 189
Information pane
Connections tab 42
Counters tab 44
hiding and showing the pane 61
Inhibited tab 51
changing the column order 51
sorting the display 51
sorting the table of inhibited alarms 51
updating the table 51
initial display 32
installation 6
InTouch software 31
L
Legend 77
M
Menus 57
View 61
menus
Actions 66
Help 77
Options 61
messages
displayed by System Manager 5
Messages tab 47
filtering messages 48
migration FBMs 213
Moore APACS migration FBMs 213
N
Navigation pane 33
alarm status indicators 40
buttons at the bottom of the pane 35
expanding and collapsing the data tree 33
selecting equipment 36
status indicators 39
view selection buttons 33
network monitoring facilities 5
O
Offline Diagnostics
control stations 149
On-line Image Update
Cold Start versus Warm Start 146
control stations 146
Options menu 61
P
peripherals 91
Counters tab 108
equipment change actions 109
status and equipment information 105
updating the software image (EEPROM update) 110
ports
alarm status indicators 241
equipment change actions 245
equipment icons 241
status indicators 241
Ports tab 241
previewing printed reports 57
Primary ECB
alarms 161
bus switching 162
equipment change actions 160
General Download 162
icons 111
status and equipment information 136
SwA / Sw B / AUTO indicators 113
Primary FBM. See Primary ECB 111
print and print preview buttons
Accessories pane 46
Print menu 57
printers. See peripherals 105
Proxy Settings group in the Configuration dialog box 62
R
Reason field in equipment change action confirmation dialog box 64
Reason Required for equipment change actions 64
Reboot
control stations 143
Refresh Rate in the Configuration dialog box 66
reports
enabling and disabling reports for a workstation 110
Reset FBM
FBMs 222
S
save button
Accessories pane 46
Search tab 52
changing the column order 52
sorting the search results 52
security 5
Select Bus A / Select Bus B
FCMs 190
selecting equipment 36
service
description of System Manager service component 1
service connection
first time System Manager is used on a workstation 14
Set Date and Time 80
SMDH
and System Manager 1
Smon button 33
Smon Log tab 56
SMON. See system monitors 85
Software Download
FBMs 223
software manager subsystem 4
station manager software 4
status and equipment information
control stations 121, 127
DCI based FBMs 212
FBM246s 211
FBMs 202
FCMs 179
peripherals 105
Primary ECB 136
switches 238
workstations 94
Status bar
showing and hiding the bar 61
status indicators 39
ports 241
system monitors 86
SwA / Sw B indicators
FCMs 177
Primary ECB 113
Switch button 33
Switch Roles
FBMs 223
FCMs 190
Switch view
selecting the view 61
switches 237
connected stations and switches 240
counters 243
equipment change actions 245
equipment icon 237
port status information 241
status and equipment information 238
symbols. Choose Help > Legend from the menu bar 77
system alarms. See alarms 27
system management components 2
System Manager
and SMDH 1
client software 1
features 2
installation 6
product structure 1
service component 1
startup 31
user interface 19
System Manager service connection
on startup 32
System Manager window 32
system messages 5
system monitor
role in system management 3
Smon Log tab in the Accessories pane 56
status table in the Information pane 86
System Monitor view
selecting the view 61
system monitors
acknowledging all alarms in a system monitor domain 88
alarm status in a system monitor domain 86
displaying equipment in the system monitor domain 87
displays in the Navigation pane 85
name displayed in italic 86
status indicators 86
T
toolbar
buttons 78
showing and hiding the toolbar 61
V
View menu 61
View Settings
Enable Blinking 66
W
Warm Start option when performing an On-line Image Update 146
Watch tab 53
changing the column order 53
sorting the display of watched counters 53
Westinghouse WPDF migration FBMs 213
Windows operating system Start menu 31
workstations 91
connected peripherals 104
counters 105, 165
enabling and disabling reports 110
equipment change actions 109
status and equipment information 94
Z
Z-Form Control Processor 270 (ZCP270). See control stations 111