System Configurator User Manual

`
System Configurator
User Manual
for the: RTU50

SCD5200
Document ID: 2005663

Revision: 1.3
System Configurator User Manual
for the RTU50 and SCD5200
2005663 - Rev. 1.3
Document Revision History:
Rev. Date Comments Prepared By

1.0 25 Mar 2003 Initial writing. A. Hussey
1.1 15 Sep 2003 Major rewrite to include all features offered by the System L. Murray
Configurator, and the complete process for configuring these
features for I/A SCADA remote devices.
1.2 24 Sep 2004 Changed text and pictures to reflect changes in the GUI and J. McDonald
menus. Add information for new IEC 60870-5-101 Master and
Slave support.
1.3 07 Mar 2005 Add information for new IEC 60870-5-104 Slave, Serial Event J. McDonald
Logger and Analog Logger support. Add description of new drag-
and-drop feature for moving cards and ports. Revise descriptions
of installation and backup/restore procedures.
This revision corresponds to release 1101155-PMR-1 of the RTU
Software, and release 1101191-C MR-1 of the System
Configurator.
I/A Series Intelligent SCADA System Page 3 of 70

2005663 - Rev. 1.3
Contents
1. Introduction............................................................................................................ 8
1.1 Scope..............................................................................................................................8
1.2 Abstract..........................................................................................................................8
1.2.1 Supported functionality........................................................................................ 8
1.3 Definitions and Abbreviations.....................................................................................10
1.4 Referenced Documents ................................................................................................10
2. Installation of System Configurator ................................................................... 11
2.1 System Requirements...................................................................................................11

2.1.1 Installing PostgreSQL (existing Cygwin installation) ....................................... 11
2.2 Installing System Configurator ....................................................................................12
3. Getting Started with System Configurator......................................................... 13
3.1 Starting up....................................................................................................................13
3.2 Menus and dialog boxes ..............................................................................................14
3.3 Navigating the configuration tree ................................................................................14
3.4 Managing configuration items .....................................................................................15

3.4.1 Creating new configuration items...................................................................... 15
3.4.2 Editing configuration items................................................................................ 17
3.4.3 Deleting configuration items.............................................................................. 18
3.5 Getting help..................................................................................................................18
4. The Configuration Tree........................................................................................ 20
4.1 RTU Configuration node .............................................................................................20
4.2 Sites node.....................................................................................................................20

4.2.1 Optonets node .................................................................................................... 20
4.2.2 RTUs node ......................................................................................................... 21
4.3 Equipment node ...........................................................................................................21
4.4 Calc Sources node........................................................................................................22
5. Configuration Overview....................................................................................... 23
6. Configuring Sites ................................................................................................. 24

2005663 - Rev. 1.3
7. Configuring OptoNet Networks .......................................................................... 25
8. Configuring I/A SCADA Remote Devices ........................................................... 27
8.1 Creating the Remote Device ........................................................................................27
8.2 Creating a card file.......................................................................................................27
8.3 Configuring slots..........................................................................................................28

8.3.1 CPU Slot ............................................................................................................ 28
8.3.2 Ethernet Slot ...................................................................................................... 29
8.3.3 Slot 1 .................................................................................................................. 29
8.3.4 Slots 2 to 11 ....................................................................................................... 29
8.4 Moving cards and ports................................................................................................31
9. Importing Existing Configurations ..................................................................... 32
9.1 Importing a configuration ............................................................................................32
9.2 Notes on Configuration Import....................................................................................32
10. Configuring Electrobus ....................................................................................... 33
11. Configuring Optobus Master .............................................................................. 36
12. Configuring I/O modules ..................................................................................... 39
13. Configuring DCBs (Dual Communications Boards) .......................................... 40
13.1 Configure the board .....................................................................................................40
13.2 Configure the port........................................................................................................40
13.3 Configure the protocol .................................................................................................41
14. Configuring OptoNet modules ............................................................................ 43
15. Configuring serial ports ...................................................................................... 44
15.1 Configure the serial card..............................................................................................44
15.2 Configure the serial port ..............................................................................................45
15.3 Configure the protocol .................................................................................................45
16. Configuring Ethernet ........................................................................................... 46
17. Configuring Protocols ......................................................................................... 48
17.1 Configuring master protocols ......................................................................................48

2005663 - Rev. 1.3
17.2 Configuring slave protocols for I/A SCADA remote devices .....................................50
17.3 Configuring slave protocols for IEDs ..........................................................................51
17.4 Configuring SALL HLSI .............................................................................................51
18. Configuring calculations ..................................................................................... 53
18.1 IDF – Intrinsic Database Functions .............................................................................53
18.2 SALL – State And Logic Language.............................................................................54
18.3 ISaGRAF......................................................................................................................55
19. Predefined points................................................................................................. 57
20. Generating and Browsing Configuration Files .................................................. 59
20.1 Generating configuration files .....................................................................................59

20.1.1 Generating a configuration for a remote device ................................................ 59
20.1.2 Generating configurations for a site................................................................... 59
20.1.3 Generating configurations for an OptoNet network .......................................... 60
20.2 Browsing configuration files .......................................................................................60
21. Database Maintenance Utilities........................................................................... 61
21.1 Backup the configuration database ..............................................................................61
21.2 Restore the configuration database..............................................................................61
21.3 Compressing the configuration database .....................................................................62
22. Troubleshooting................................................................................................... 63
22.1 The required services are not running. ........................................................................63
22.2 Check that all temporary files created by the PostgreSQL service have been deleted.65
22.3 Check permissions on PostgreSQL files......................................................................65
22.4 The Cygwin “Administrator” user must exist on the local machine. ..........................65
22.5 Check that the ROOTDB and SYSCFG databases exist on the PostgreSQL service. 66
22.6 Domain server access...................................................................................................66
22.7 The jdbc version is incompatible with the PostgreSQL version..................................67
22.8 User could not be correctly authenticated ...................................................................67
22.9 Database scripts ...........................................................................................................67
23. Appendices........................................................................................................... 68

2005663 - Rev. 1.3
Appendix A Definitions and Abbreviations..............................................................68
Appendix B Referenced Documents.........................................................................70

2005663 - Rev. 1.3
1. Introduction
1.1 Scope
This document describes the use of the System Configurator to configure the
I/A SCADA remote devices, the RTU50 and SCD5200. In particular, this
document describes:
• Installation procedures.
• Overview of the functionality provided by the System Configurator.
• Discussion of the configuration process, including the required
sequencing of activities.
Detailed discussion of configurable items and their corresponding parameters is
contained in the on-line help feature of the System Configurator and in the User
Manuals for specific RTU protocols and subsystems.
This document is intended as a reference for users who are installing or using
the System Configurator to configure I/A SCADA remote devices and is not
written to be read from cover to cover. To gain an understanding of System
Configurator and to get started with a configuration, read Sections 3 to 6. After
that, choose the sections that are relevant to your particular configuration.
The functionality described by this user manual corresponds to release
1101155-P of the RTU Software and 1101191-C of the System Configurator.
1.2 Abstract
The System Configurator is a JavaTM-based configuration tool for the I/A
SCADA remote devices, the RTU50 and SCD5200, which runs under the
Microsoft Windows operating system. The System Configurator is graphical
and mouse-based, permitting browsing and editing of configurations in a
windowed environment.
Configuration of hardware and protocols not yet supported by the System
Configurator continues to be provided by the RTU Configurator (RTUCFG)
[9]. The functionality supported by the System Configurator for the SCD5200
and RTU50 is detailed in Section 1.2.1.
Note: Throughout this document, the RTU50 and SCD5200 are collectively
referred to as I/A SCADA remote devices. The names RTU50 and SCD5200
are used when specifically referring to these devices.
Note: Throughout this document, menus, menu commands, dialog names, and
parameter names are shown in bold.
1.2.1 Supported functionality

Table 1 details the functionality currently supported by the System
Configurator for the RTU50 and SCD5200.

2005663 - Rev. 1.3
SCD5200 RTU50
Card Files: • 1 Slot I/O • 2 Slot Backplane
• 5 Slot I/O • 3 Slot Backplane
• 10 Slot I/O • 6 Slot 19-inch rack
• 7 Slot Backplane
• Optobus files
CPU Cards: • COPE • PII, PIIE, P3E
Comms Cards: • OptoNet (part of COPE) • OptoNet
• Ethernet (part of COPE) • Ethernet
• 8 Channel Serial • 8 Channel Serial
• 12 Channel Serial
• V.11 DCB • V.11 DCB
• V.23 DCB • V.23 DCB
• V.28 DCB • V.28 DCB
• Glass Optical DCB • Glass Optical DCB
I/O Cards: • 20 AI (non-isolated) • 20 AI
• 20 AI (isolated) • 20 AI Type 2
• 32DI / 4AI (non-isolated) • ADI
• 32DI / 4AI (isolated) • ADI Type 2
• 4AO • AO
• 24DI / 6AI / 8DO • Multi IO
• 24DI / 6AI / 6DO
• 12 DO • TDO
• 12 DO (10 Amp) • TDO (10 Amp)
• CTVT (AC Transducer) • AC Transducer
Protocols: • Modbus Slave – 8 Channel Serial, • Modbus Slave – 8 and 12 Channel
CPU Serial (COM2) Serial, CPU Serial (COM2)
• Modbus Master – 8 Channel Serial, • Modbus Master – 8 and 12 Channel
CPU Serial (COM2) Serial, CPU Serial (COM2)
• OpenModbus/TCP Master – TCP/IP • OpenModbus/TCP Master – TCP/IP
• DNP3 Slave – 8 Channel Serial, CPU • DNP3 Slave – 8 and 12 Channel
Serial (COM2), V.11, V.23, V.28, Serial, CPU Serial (COM2), V.11,
Optical DCBs, TCP/IP, Dialup V.23, V.28, Optical DCBs, TCP/IP,
Dialup
• DNP3 Master – 8 Channel Serial, CPU • DNP3 Master – 8 and 12 Channel
Serial (COM2), V.11, V.23, V.28, Serial, CPU Serial (COM2), V.11,
Optical DCBs, TCP/IP, Dialup V.23, V.28, Optical DCBs, TCP/IP,
Dialup
• C300 Slave – V.23, V.28 DCBs • C300 Slave – V.23, V.28 DCBs
• C3000 Slave – V.23, V.28 DCBs • C3000 Slave – V.23, V.28 DCBs
• Conitel Slave – V.23, V.28 DCBs • Conitel Slave – V.23, V.28 DCBs
• Conitel Master – V.23, V.28 DCBs • Conitel Master – V.23, V.28 DCBs
• IEC 60870-5-101 Slave – V.28 DCB • IEC-60870-5-101 Slave – V.28 DCB
• IEC 60870-5-101 Master – 8 Channel • IEC 60870-5-101 Master – 8 and 12
Serial, CPU Serial (COM2) Channel Serial, CPU Serial (COM2)

2005663 - Rev. 1.3
SCD5200 RTU50
• IEC 60870-5-103 Master – Optical • IEC 60870-5-103 Master – Optical
DCB DCB
• IEC 60870-5-104 Slave – TCP/IP • IEC 60870-5-104 Slave – TCP/IP
Miscellaneous: • Terminal Server • Terminal Server
• Serial Event Logger Type 2 • Serial Event Logger Type 2
• Analog Logger • Analog Logger
Calculation • IDF (Intrinsic Database Functions) • IDF (Intrinsic Database Functions)
Subsystems: • SALL (State And Logic Language) • SALL (State And Logic Language)
• IEC 61131-3 (ISaGRAF) • IEC 61131-3 (ISaGRAF)
Table 1: Supported Functionality
1.3 Definitions and Abbreviations

Definitions and abbreviations found in this manual are listed in Appendix A.
1.4 Referenced Documents

Documents referenced in this manual are listed in Appendix B.

2005663 - Rev. 1.3
2. Installation of System Configurator

This section describes the system (hardware and software) necessary to install
and run the System Configurator, and the installation process.
2.1 System Requirements

The minimum system configuration for running the System Configurator is:
• Windows NT/2000/XP (Professional Edition) Operating System.
Windows XP (Home Edition) is not supported at this time.
• 256 MB RAM.
• 140 MB hard disk space for installation files and 50 MB of swap space.
It is recommended that the System Configurator be run on a PC with a 400Mhz
Pentium, or faster, CPU.
The System Configurator makes use of the Cygwin UNIX environment for
Windows and the PostgreSQL Database Server, both of which are included in
the System Configurator installer.
Some users may have pre-existing installations of Cygwin and the install
process permits the user to not install this component in this case. Usually the
pre-existing installation of Cygwin will be without the PostgreSQL database,
which must be installed within the Cygwin environment prior to installing the
System Configurator.
Section 2.1.1 discusses how to install PostgreSQL into an existing Cygwin
environment. Section 22 provides troubleshooting advice for the installation of
the PostgreSQL database.
2.1.1 Installing PostgreSQL (existing Cygwin

installation)
The information contained within this section relies on the user having some
knowledge of Cygwin installation and the Cygwin utilities. For detailed
information refer to the appropriate Cygwin documentation, which can be
found on the Cygwin website (http://www.cygwin.com).
The user must first install the PostgreSQL package and any packages on which
it depends using the standard Cygwin installer.
The user must then follow the instructions for an NT install in the file
/usr/share/doc/Cygwin/postgresql-<version>.readme.
Due to the requirement to install packages as services on the local machine
the user performing the installation must have administrator rights on the
machine.

2005663 - Rev. 1.3
2.2 Installing System Configurator

The System Configurator is provided as part of the 1101190: RTU50 and
SCD5200 Installation and Configuration Suite. For most users, a short
introductory menu, similar to the screen displayed in Figure 1, displays
automatically when the release CDROM is loaded into the CDROM drive. If
this does not happen automatically, open the file menu.exe in the root directory
of the CDROM drive.
Figure 1: 1101190 Installation and Configuration Suite Menu

The introductory menu contains links to the installation program for the System
Configurator, and for several other related I/A SCADA remote device products.
• Make sure the checkbox next to the System Configurator option is
checked.
• Click Install to begin installation.
• Follow the on-screen instructions to select the installation directory.
Accepting the default installation path is strongly recommended.
A desktop shortcut and Start Menu entry (Programs Foxboro) for the System
Configurator are created.
When upgrading the System Configurator software to a later release, if the
installation process detects that a configuration database already exists, the user
is prompted to choose if they wish to backup the existing database to a file. If
the user proceeds with the backup, the file is placed in the file
userdatabackup.dat in the parent directory of the installation directory. The
database saved to this file can be restored as System Configurator’s database by
following the process described in Section 21.2.

2005663 - Rev. 1.3
3. Getting Started with System

Configurator
This section describes how to get started with System Configurator. The
System Configurator screen and the menus and dialog boxes are explained.
Navigating the configuration tree is described, along with how to create, edit,
and delete configuration items. System Configurator provides extensive online
help facilities, and access to these is discussed.
3.1 Starting up
There are two main methods of accessing System Configurator:
1. Double-click the System Configurator icon on the desktop; or
2. Click the Start button and choose Programs Foxboro System
Configurator.
The System Configurator starts and opens the System Configurator window
shown in Figure 2.
Left Pane Splitter Bar Right Pane
Figure 2: System Configurator Window

The System Configurator window has left and right panes separated by a
splitter bar. The left pane displays the configuration tree that contains the
configuration items available to the user. The configuration tree provides easy
navigation of the configuration items, and enables configuration items to be
created, deleted, edited and viewed. The tree gives a hierarchical view of the
configuration. The top level of the tree is the RTU Configuration node. Below
this node are nodes for Sites, Equipment, and Calc Sources. The right pane
holds sub-windows for any node in the tree that the user is currently editing.
The splitter bar separating the two panes allows the user to alter the widths of
the left and right panes.

2005663 - Rev. 1.3
3.2 Menus and dialog boxes

As shown in Figure 2, the System Configurator has three menus: File, Window
and Help. The File menu has one item, Exit that terminates the System
Configurator. The Window menu has one item for each of the open windows in
the right pane, allowing the user to switch between the open windows. The
Help menu has two active options: Contents and About. The Contents option
opens the Help System window. The help facilities are discussed in detail in
Section 3.5. About displays the System Configurator version number and
copyright notice.
Access to configuration commands is through context-sensitive menus. This
means that to access a menu for a configuration item, the user right-clicks on
the item in the tree, and a context-sensitive menu appears, offering the
commands applicable to the item selected.
To configure items in the tree, the user must configure the parameters that
comprise the item. These parameters are grouped in windows that appear in the
right pane when selections are made from the context-sensitive (right-click)
menus in the tree. The buttons OK, Close, Cancel, Apply, Refresh and Help
appear on most of the windows that appear in the right pane and have the
following effects when clicked:
1. OK saves any changes made in the window and closes it.
2. Close closes the window. The Close button becomes a Cancel button
when there are unsaved changes in the window.
3. Cancel closes the window without saving the changes made. The user
is warned that any changes will be lost, and is given the opportunity not
to proceed. The Cancel button becomes the Close button if changes to
the configuration parameters in the window are saved (by clicking the
Apply button).
4. Apply saves any changes made in the window without closing the
window.
5. Refresh refreshes the values contained in the window from the
database, discarding any edits that have been made.
6. Help opens the help page containing help information on the current
window.
3.3 Navigating the configuration tree

The System Configurator configuration tree presents all configuration data in a
hierarchical tree structure, providing a direct method of browsing and
manipulating configuration data. The tree displays in the left pane of the
System Configurator window, as shown in Figure 2.
The tree in the left pane contains both static and dynamic nodes. Static nodes
are permanent nodes that the user cannot remove, such as RTU Configuration,
and the Sites, Equipment, and Calc Sources nodes below it. Every item
configured becomes a node in the configuration tree.

2005663 - Rev. 1.3
To the left of each node is a switch icon. A closed switch, , indicates that the
tree below the node can be expanded to reveal more items. An open switch, ,
indicates that the tree below the node is expanded. To expand a node, double-
click on the name of the node, or click on the closed switch icon to the left of
the node’s name. To collapse the tree below the node, double-click on the name
of the node, or click on the open switch icon.
3.4 Managing configuration items

This section describes how to create, edit, and delete configuration items.
3.4.1 Creating new configuration items

To create a configuration item, right-click on the group or item it belongs to,
and choose Create from the popup menu. For example:
• To create a Site, right-click on the Sites node (icon or name).
• To create an OptoNet, right-click on the Optonets node (icon or name),
under an existing site.
• To create a remote device, right-click on the RTUs node (icon or
name), under an existing site.
• To create a Card File in a remote device, right-click on the Card Files
node (icon or name), under the remote device’s node.
• To create a card for a slot in a card file, right-click on the [slot
number]<EMPTY> node (icon or name), under the card file’s node.
A window appears in the right pane with parameters that the user must
configure to create the item. Some tabs or parameters may be unavailable
(greyed-out) when the window first displays, but become available once
mandatory parameters have been entered and saved (by clicking the Apply
button). Figure 3 shows the window for an ADI card, showing the default name
provided by System Configurator, with the ADI Card Details, DI Points, and AI
Points tabs unavailable as the name has not yet been saved.
The process of providing and saving the mandatory parameters causes the
System Configurator to create the item. Every item must be configured with a
name, by which it is known in the System Configurator. The System
Configurator provides a default name for most items. The default name can be,
and generally should be, altered to uniquely identify the new configuration
item. It is provided as a convenient starting point. The name of the item appears
in the configuration tree. Figure 4 shows the window for an ADI card once the
name parameter has been applied – notice that all of the tabs are now available.

2005663 - Rev. 1.3
Figure 3: ADI window - before mandatory parameter configuration.

The method used to generate default names for items depends on what the item
is. For example, default point names are constructed as
Entity_Name “_” Node_Number File_Number Slot_Number “_” Point_Name
Where the node and slot numbers are two digits and the file number is one
digit.
So, the health point of an ADI card named “ADI” in slot 2 of card file 1, in an
RTU with node number 3, is named ADI_03102_HlthPnt, by default. Point
names for an I/A SCADA remote device are limited to 25 characters. The
System Configurator abbreviates the entity name and point name components
of the default point name, so that it fits into 25 characters.
Figure 4: ADI window - after mandatory parameter configuration.

2005663 - Rev. 1.3
3.4.2 Editing configuration items

To view or edit the currently configured parameters for an item, right-click on
the item’s node (icon or name) and choose Edit from the popup menu. The
item’s window appears in the right pane with its current parameters. Before any
changes are made in the window, only the Close and Help buttons are
available, as shown in Figure 5.
Figure 5: Edit Window before changes.

If parameters in the window are modified, the window transitions to an edited
state, and the remaining buttons (OK, Apply, Refresh) become available. An
asterisk is added to the beginning of the windows title bar, and the Close button
becomes the Cancel button. This is shown in Figure 6. These changes to the
window indicate to the user that their modifications to the parameters have not
been saved. Clicking the Apply button causes the changes to be saved and the
window to return to an unedited state as shown in Figure 5.
Figure 6: Edit Window after changes.

2005663 - Rev. 1.3
3.4.3 Deleting configuration items

All items that a user configures can be deleted, that is, removed permanently,
from the configuration. BE WARNED that the System Configurator has no
“undo” feature, and once a deletion has occurred the item cannot be recovered.
Also be aware that all items in sub-trees of the configuration tree of the item to
be deleted will also be removed permanently in the deletion process.
To delete an item from the configuration tree, right-click on the item’s node
(icon or name) and select Delete from the popup menu. A Confirm Deletion
dialog displays, asking the user to confirm that they wish to proceed with the
deletion. Clicking OK in this dialog deletes the selected item. Clicking Cancel
leaves the item in the configuration tree.
3.5 Getting help

System Configurator has extensive online help facilities that can be accessed
through the Help menu or via the Help button in configuration windows.
Selecting Get Help from the Help menu opens the Help System window
providing access to the complete help system for System Configurator. Figure 7
displays the Help System window and a description of its features follows.
Clicking the Help button in a window opens the Help System window with the
help page describing that window and its parameters.
Forward Page Setup

Back Print Title Bar
Left Pane Splitter Bar Right Pane
Figure 7: System Configurator Help System Window

The parts of the Help System window are identified in Figure 7. The title bar at
the top of the window identifies that the user is in a System Configurator
window. There are four buttons in the upper left corner of the window: Back,
Forward, Print, and Page Setup. As the user navigates through the help
pages, the help system keeps a list of the pages viewed. The Back and
Forward buttons navigate through this list. The Print button displays the Print
dialog, which enables the user to print the current help page. The Page Setup

2005663 - Rev. 1.3
button displays the Page Setup dialog, allowing the user to configure printing
parameters.
The main area of the Help System window is divided into left and right panes
separated by a splitter bar. The left pane displays a table of contents with the
help pages grouped under topics. The right pane displays a selected help page.
To display a help page, click on its heading in the left pane, and the page will
display in the right pane.
The widths of the left and right panes can be changed by moving the splitter bar
that separates them.

2005663 - Rev. 1.3
4. The Configuration Tree

This section explains the top-level contents of the configuration tree (situated in
the left pane of the System Configurator window). From these top levels the
user begins the configuration process for configuring OptoNet networks and
I/A SCADA remote devices, so an understanding of how to configure items in
the top levels of the tree is imperative. All menu options available for each top-
level node are also discussed.
4.1 RTU Configuration node

When the System Configurator window first appears, the only tree nodes
visible are the RTU Configuration node and its three children; Sites,
Equipment and Calc Sources.
The RTU Configuration node has no popup menu. The selections that are
available for its child nodes are described in the following sections.
4.2 Sites node

A site is a grouping of OptoNet networks and/or remote devices. A site
configured in System Configurator relates to a physical site –or location – that
contains OptoNet networks and remote devices. All sites are configured from
the Sites node, and appear in the configuration tree under this node. All
OptoNet networks and remote devices must belong to a site, so the first step in
a configuration is to create a site. During the configuration, the user must
provide a name for the site. Once configuration is complete, a new node
appears in the configuration tree, under the Sites node, with the name given to
the new site.
The Sites node menu has two active items – Create and Refresh.
Create - displays a window in the right pane that enables the user to
configure a new Site.
Refresh - refreshes the display of the configuration tree under the Sites node.
When a site node is opened, two nodes display below it – Optonets and RTUs.
If the site contains an OptoNet network, the user must configure the OptoNet
from the Optonets node. This configuration process is explained in Section
4.2.1 below. Configuration of remote devices that are not part of an OptoNet
network occurs at the RTUs node. This process is described in Section 4.2.2
below.
4.2.1 Optonets node

An OptoNet network is configured from the Optonets node. This is the first
step in configuring an OptoNet network. During the configuration, the user
must provide a name for the OptoNet network. Once configuration is complete,
a new node appears in the configuration tree, under the Optonets node, with
the name given to the new OptoNet network.
The Optonets node menu has two active items: Create and Refresh.

2005663 - Rev. 1.3
Create - displays a window in the right pane that enables the user to
configure a new OptoNet network.
Refresh - refreshes the display of the configuration tree under the Optonets
node.
From the OptoNet network node, the user can configure the remote devices that
make up the network. OptoNet network configuration is described in more
detail in Section 7.
4.2.2 RTUs node

Each I/A SCADA remote device that is not part of an OptoNet network is
configured from the RTUs node. During the configuration, the user must
provide a name for the remote device. Once configuration is complete, a new
node appears in the configuration tree, under the RTUs node, with the name
given to the new remote device.
The RTUs node menu has four options: Create, Generate CFGs, Import File,
and Refresh.
Create - displays a sub-menu that allows the user to choose to configure an
RTU50 or SCD5200. Once a choice is made, a window displays in
the right pane that enables the user to configure the chosen device.
Generate CFGs – displays a window in the right pane allowing the user to
generate configuration files for selected (or all) remote devices
configured in the current site.
Import File - displays a window in the right pane allowing the user to import
the configuration of a remote device from a file. The configuration
file being imported can have been previously created using the
System Configurator, RTU Configurator, or other means (as long
as it is compliant with the Configuration File Specifications). For
the import to succeed, the configuration must obey all rules, and
notably must provide a unique name for the remote device within
the current site.
Refresh - refreshes the display of the configuration tree under the RTUs
node.
I/A SCADA remote device configuration is described in detail in Section 8.
4.3 Equipment node

Equipment describes the configuration components that are not associated
with a site, and are available for use by remote devices configured in all sites.
Presently, the only type of equipment that is available is IED.
The Equipment node menu has one option: Refresh.
Refresh - refreshes the display of the configuration tree under the
Equipment node.
The IED (Intelligent Electronic Device) node allows configuration of slave

2005663 - Rev. 1.3
devices that can be attached (connected) to master protocols in remote device

configurations. This feature is used when the slave is a third party device. The
parameters that can be configured for the slave are a restricted set of those that
are available if the slave was configured as an I/A SCADA remote device
within a site.
Currently, IEDs can be created for the following protocols:
• DNP3 Slave,
• Conitel Slave
• Modbus Slave,
• IEC 60870-5-101 Slave,
• IEC 60870-5-103 Slave.
During the configuration, the user must provide a name for the device. Once
configuration is complete, a new node appears in the configuration tree, under
the IED node, with the name given to the new slave device.
The IED node menu has two options: Create and Refresh.
Create - displays a sub-menu that allows the user to choose the slave
protocol. Once a choice is made a window is displayed in the right
pane allowing the user to configure the new slave device.
Refresh - refreshes the display of the configuration tree under the IED node.
4.4 Calc Sources node

ISaGRAF calculations can be configured for I/A SCADA remote devices. For
these calculations to be available for configuration in remote devices, their
calculation sources must be configured so the System Configurator is aware of
them. The configuration of the calculation sources occurs at the ISaGRAF
node, which is located under the Calc Sources node.
The Calc Sources node menu has one option: Refresh.
Refresh - refreshes the display of the configuration tree under the Calc
Sources node.
During configuration of an ISaGRAF calculation’s sources, the user must
provide a name for the ISaGRAF calculation source. Once configuration is
complete, a new node appears in the configuration tree, under the ISaGRAF
node, with the name given to the new calculation source.
The ISaGRAF node menu has two options: Configure ISaGRAF Source and
Refresh.
Configure ISaGRAF Source – displays a window in the right pane that
enables the user to configure a new ISaGRAF calculation source.
Refresh - refreshes the display of the tree under the ISaGRAF node.
The configuration of ISaGRAF calculations for I/A SCADA remote devices is
discussed in detail in Section 18.3.

2005663 - Rev. 1.3
5. Configuration Overview
The general process for configuring I/A SCADA remote devices is illustrated in
Figure 8. The diagram is meant as a guide for the order in which configuration
steps should occur. Not all steps are mandatory, as indicated by the shaded box
for OptoNet network creation (that is, remote devices do not have to be part of
an OptoNet network, they can be stand-alone). The annotations to the right and
left of the diagram indicate the relevant sections in this document to find
information about each step.
Section 6 Create a Site
Section 7 Create an OptoNet network
Section 8 Create an RTU50 or SCD5200
Create Card Files (including

Sections 10 and 11 Electrobus and Optobus files)
Section 12 Configure I/O Modules
Configure Communications Configure Calculations – IDFs,

Sections 13 to 17 Section 18
Modules and Protocols SALL and ISaGRAF
Compile SALL Calculations Section 18.2
Section 18 Generate Configuration File
Transfer Configuration File,

SALL executable (.elf) files, and
ISaGRAF executable (.isa) files to
RTU50 or SCD5200
Restart RTU50 or SCD5200
Figure 8: Configuration process.

2005663 - Rev. 1.3
6. Configuring Sites
All I/A SCADA remote devices and OptoNet networks are configured within a
site. Therefore, before configuring a remote device or OptoNet network, the
site it is to belong to must be configured. The selection of a site for a remote
device or OptoNet network requires careful consideration, as remote devices
cannot be moved between sites without generating a configuration file and then
importing it into a different site.
In the System Configurator, all sites are configured from, and appear under, the
Sites node in the configuration tree. To configure a new site, right-click on the
Sites node and select Create from the menu. The Site window displays in the
right pane. It is recommended that the site be named descriptively in
accordance with its purpose and/or physical location. A node appears in the
configuration tree under the Sites node, with the name the site is configured
with.
A site node menu has three active items: Edit, Delete, and Refresh.
Edit - displays the Site window, allowing the user to view and change
the parameters currently configured for the site.
Delete - displays a dialog prompting the user to confirm that they wish to
proceed with the deletion of the site. BE AWARE that deleting a
site deletes all remote devices and OptoNet networks configured in
the site. If the user confirms that they want to delete the site, the
site and all of its information is removed from the configuration. If
the user chooses not to proceed with the deletion, the configuration
remains unchanged.
Refresh - refreshes the display of the configuration tree under the site’s
node.

2005663 - Rev. 1.3
7. Configuring OptoNet Networks

The OptoNet subsystem for the I/A SCADA remote devices provides the ability
to support peer-to-peer communications between remote devices, by using a
high-speed optical ring network interface, with high isolation and noise
immunity. Each remote device constitutes a node on the OptoNet network, and
is able to communicate with all other remote devices on the network. OptoNet
distributes information between remote devices without interfering with the
normal operation of the remote device. Communications with the SCADA
Master can occur from a single network node, or from many.
An OptoNet network can have up to 63 I/A SCADA remote devices. Each
remote device within the network must have a unique node number between 1
and 63. Node Numbers are configured as part of the RTU50 or SCD5200
configuration.
Configuring an OptoNet network of remote devices within a site consists of two
main steps:
1. Configure the OptoNet network. This is described below.
2. Configure the remote devices within the OptoNet network (Section 8),
and configure an OptoNet module for each device (Section 14).
To configure an OptoNet network for a site, right-click on the Optonets node
in the configuration tree, under the site and select Create. The Optonet
window displays in the right pane. When the OptoNet network configuration is
saved, a node appears in the configuration tree under the Optonets node, with
the name the OptoNet network is configured with.
The OptoNet network node menu has six options: Create, Edit, Delete,
Generate CFGs, Import File, and Refresh.
Create - displays a sub-menu that allows configuration of an RTU50 or
SCD5200. Once a choice is made, a window displays in the right
pane, allowing the user to configure a new RTU50 or SCD5200 as
part of the OptoNet network.
Edit - displays the OptoNet Network window, allowing the user to view
and change the parameters currently configured for the OptoNet
network.
proceed with the deletion of the OptoNet network. BE AWARE
that deleting an OptoNet network deletes all remote devices
configured in the network. If the user confirms that they want to
delete the OptoNet network, the network and all of its information
is removed from the configuration. If the user chooses not to
proceed with the deletion, the configuration remains unchanged.
Generate CFGs – displays a window allowing the user to generate
configuration files for selected (or all) remote devices configured
in the OptoNet network.
Import File - displays a window that enables the user to import the
configuration of a remote device from a file. The configuration file

2005663 - Rev. 1.3
being imported can have been previously created using the System
Configurator, RTU Configurator, or other means (as long as it is
compliant with the Configuration File Specifications). For the
import to succeed, the configuration must obey all rules, and
notably must provide a unique node number and unique name for
the remote device. See Section 9 for detailed information on
importing configuration files.
Refresh - refreshes the display of the configuration tree under the OptoNet
network’s node.
For detailed information about OptoNet networks and modules refer to the
“OptoNet Software User Manual for the RTU50 and SCD5200” [7].

2005663 - Rev. 1.3
8. Configuring I/A SCADA Remote

Devices
This section describes the process for configuring I/A SCADA remote devices.
There are some differences between configuration of an RTU50 and an
SCD5200. These differences are explained below. The process for configuring
the majority of the communications and I/O modules is identical for the RTU50
and SCD5200, and these are described in Section 10.
Note: Before configuring an I/A SCADA remote device, the user must decide
what Site the device is to be created in. This decision has importance when
using the System Configurator, as once an RTU50 or SCD5200 is created it
cannot be moved between Sites.
8.1 Creating the Remote Device

A remote device can be created as a stand-alone device or as part of an OptoNet
network. The process for configuring the device in both cases is the same,
except for whereabouts in the configuration tree the device is created.
To create a stand-alone device, choose the site, right-click on the RTUs icon
and choose Create from the menu. From the sub-menu that displays, select
RTU50 or SCD5200 to display a window for the new device. This window
will be identical for RTU50 and SCD5200 except that a different set of options
will appear in the CPU Card Type list.
Configure the parameters and then select OK or Apply. A node with the name
of the device will appear in the tree under the RTUs node.
To create a remote device that is part of an OptoNet network, open the
Optonets node under the site. Below the Optonets node in the configuration
tree, are nodes for each OptoNet network currently configured for the site.
Select the OptoNet network that the new device is to belong to, right-click on
its node, and choose Create from the menu. From the sub-menu that displays,
select RTU50 or SCD5200 to display a window for the new device.
Note: Each remote device in an OptoNet network must have a unique Node
Number and a unique Name.
Configure the parameters and then select OK or Apply. A node with the name
of the new device will appear in the tree under the OptoNet network’s node.
The parameters configured for the device can be modified later by right-
clicking on the device in the tree and selecting Edit from the popup menu.
Each remote device in the tree has two more nodes below it: Card Files and
Calculations. A card file must be configured for every remote device, and this
is described below in Section 8.2. The configuration of calculations is
described in Section 18.
8.2 Creating a card file

To create a card file, right-click on the Card Files node (below the remote

2005663 - Rev. 1.3
device’s node) and choose Create from the menu. A sub-menu displays with
the types of card files available for that remote device as shown in Table 2.
RTU50 SCD5200
2 Slot Backplane 1 I/O File
3 Slot Backplane 5 I/O File
6 Slot 19 inch Rack 10 I/O File
7 Slot Backplane
Table 2: Card File Types

Select the appropriate card file for the device. The card file window displays.
Configure the parameters. A node appears in the configuration tree, under the
Card Files node, with a name that reflects that this is the primary card file (File
Number 1) and the type of the card file. For example, if the card file chosen is a
7 Slot Backplane, the name of the node is [1] 7_Slot_Backplane.
Only one primary card file can be configured for a remote device. The RTU50
can be expanded with subsequent card files through the Electrobus interface,
which is explained in Section 10, or the Optobus interface, which is explained
in Section 11. The SCD5200 cannot be expanded.
Opening a configured card file’s node reveals a node for each slot in the card
file available for configuration, and a node for the Electrobus interface (RTU50
only). The configuration of slots is discussed below.
8.3 Configuring slots

This section describes the configuration of slots in a remote device’s card file.
8.3.1 CPU Slot

For SCD5200 devices the CPU slot will be labelled [CPU] COPE. For an
RTU50 the CPU slot will be labelled either [1C] P2E or [1C] P3E, depending
on the user’s choice of CPU card.
Opening the CPU slot’s node reveals two nodes below it – one for each
communications port on the main processor board. Communications port 1
(COM1) has a node labelled [1] DIAGNOSTICS. This port is reserved for use
with the diagnostic utilities, Remote Terminal Viewer and TOOL32, and is not
available for configuration. Communications port 2 (COM2) has a node
labelled [2] <UNASSIGNED>. This port is available for configuration of a
protocol that operates over serial communications, and this configuration
process is described in Section 15.
The CPU slot may also be used to attach instances of the Serial Event Logger
and Analog Logger modules. Serial Event Logger instances attached to the
CPU slot instead of a serial port will log events to the RTU flash file system
only.

2005663 - Rev. 1.3
8.3.2 Ethernet Slot

All SCD5200 CPU cards and RTU50 P3E CPU cards have a built-in Ethernet
interface. The Configurator will create this interface automatically and
configure it with default values when the primary card file is created. In the
configuration tree this interface will be labelled [IP] Eth. In general, the user
must edit the default Ethernet configuration, as described in Section 16.
RTU50 P2E CPU cards may have an optional Ethernet interface daughter
board. As this interface is optional, the Configurator will not automatically
configure it but provides a placeholder in the tree, labelled [IP] <Empty>,
should the user wish to configure the Ethernet interface, as described in Section
16.
8.3.3 Slot 1
For SCD5200 devices, slot 1 always refers to the CPU card’s built-in OptoNet
interface. In the tree this slot is labelled [OPT] Optonet.
For RTU50 devices, slot 1 may be used for OptoNet or for any of the available
Dual Communications Boards (DCBs). In the tree this slot is labelled as [1B]
<EMPTY>. To configure a card in slot [1B], right-click on its node and
choose Create from the menu. A sub-menu displays with the options:
• Generic DCB
• Glass Optic DCB
• OptoNet
• V.11 DCB
• V.23 DCB
• V.28 DCB
Choose the item appropriate for the module in the physical slot to display the
window for that type of card. DCB configuration is described in Section 10.
Configuration of an OptoNet module is described in Section 14.
Note: Generic DCBs – A Generic DCB is used when the type of the DCB in
the physical slot is unknown. All DCB parameters are offered for configuration,
and the RTU Software ignores those that are not required by the DCB that
physically resides in the slot.
8.3.4 Slots 2 to 11
The remaining physical slots in the card file, each have a node in the
configuration tree named [slot number] <EMPTY>. For any of these slots the
following communications modules and I/O modules can be configured:
RTU50 SCD5200
Generic DCB Generic DCB

2005663 - Rev. 1.3
RTU50 SCD5200
Glass Optic DCB Glass Optic DCB
OptoNet
V.11 DCB V.11 DCB
V.23 DCB V.23 DCB
V.28 DCB V.28 DCB
8 Channel Serial Card 8 Channel Serial Card
12 Channel Serial Card
20 Analog Inputs Module (non-isolated) – 20 20 Analog Inputs Module (non-isolated) – 20

AI AI (non-isol)
20 Analog Inputs Module (isolated) – 20 AI 20 Analog Inputs Module (isolated) – 20 AI

Type 2 (isol)
4 Analog Inputs/32 Digital Inputs Module 4 Analog Inputs/32 Digital Inputs Module
(non-isolated) – ADI (non-isolated) – ADI (non-isol)
4 Analog Inputs/32 Digital Inputs Module 4 Analog Inputs/32 Digital Inputs Module
(isolated) – ADI Type 2 (isolated) – ADI (isol)
4 Analog Outputs Module – AO 4 Analog Outputs Module – AO
24 Digital Inputs/6 Analog Inputs/8 Digital 24 Digital Inputs/6 Analog Inputs/8 Digital
Outputs Module – Multi IO Outputs Module – 24DI/6AI/8DO
24 Digital Inputs/6 Analog Inputs/6 Digital

Outputs Module – 24DI/6AI/6DO
12 Digital Outputs Module – TDO 12 Digital Outputs Module – 12DO
12 Digital Outputs (10 Amp) Module – TDO 12 Digital Outputs (10 Amp) Module – 12DO
(10 Amp) (10 Amp) Note: This module cannot be
configured for the last slot (right-most) in a
card file.
AC Transducer (also known as the CTVT CTVT (also know as the AC Transducer
module or the 3 phase transducer module) module or the 3 phase transducer module)
Note: This module cannot be configured for
the last slot (right-most) in a card file.
Optobus Master
To configure a module for a slot, right-click on the slot’s node and choose
Create from the menu. A sub-menu displays with the above items. Select the
item applicable to the physical module in the slot to display the configuration
window for that module.
Configuration of an Optobus Master module is described in Section 11.
Configuration of I/O modules is described in Section 12. Configuration of

2005663 - Rev. 1.3
DCBs is described in Section 13. Configuration of OptoNet modules is

described in Section 14. Configuration of 8 and 12 Channel Serial Cards is
described in Section 15.
8.4 Moving cards and ports

The System Configurator provides a limited drag-and-drop facility for moving
cards between slots and for moving ports within a serial card or DCB.
Cards may only be moved to a compatible and unoccupied slot in the same
RTU. This includes moving cards between cards files in an RTU50.
The following restrictions apply to moving cards and ports:
• A DCB may be moved to any empty slot of an RTU50 or SCD5200.
• An OptoNet card may be moved to any empty slot of an RTU50.
(OptoNet cannot be moved on SCD5200 as it is built into the CPU
card.)
• CPU, Ethernet and ElectroBus extender cards cannot be moved.
• 12 Digital Output cards and AC Transducer cards can be moved to any
empty slot of an RTU50, except slot 1B, and any empty slot of an
SCD5200 as long as there is also an extra empty slot after it.
• Other cards can be moved to any empty slot, except slot 1B of an
RTU50.
• DCB ports and serial ports can be moved to any empty port within the
same card.
A card or port can be moved by positioning the mouse cursor over the card or
port, then holding down the left mouse button and dragging the card or port to
the desired location. When the user attempts to drag a card or port to another
slot, the mouse cursor will change to indicate whether the card or port can be
moved to the location that is currently under the mouse cursor. When the
cursor is over a suitable location, releasing the left mouse button completes the
move operation.

2005663 - Rev. 1.3
9. Importing Existing Configurations

If a configuration file already exists for a remote device, this configuration can
be imported into the System Configurator, rather than reconfiguring the device
from the beginning. The configuration file may have been generated using the
System Configurator, RTU Configurator, or any other means (providing it is
compliant with the Configuration File Specifications). A configuration can be
imported into an OptoNet network or as a stand-alone remote device.
9.1 Importing a configuration

To import a configuration into a site as a stand-alone remote device, right-click
on the RTUs node under the site in the configuration tree. From the menu that
displays choose Import File to display the Import File window.
To import a configuration into an OptoNet network, open the Optonets node in
the site. Select the OptoNet network that the device is to become a part of, and
right-click on its node. From the menu that displays choose Import File to
display the Import File window.
In the Import File window, select the appropriate device type and RTU
Software part number from the drop-down lists. Enter the name of the
configuration file to be imported, or browse to the file.
Once a file is selected, its contents display in the File Preview section of the
window. Prior to importing, the file can be edited by clicking on the View
button. To proceed with the import, click the OK or Apply button.
The status bar at the bottom of the window indicates the progress of the import.
A node appears in the configuration tree under the OptoNet network’s node,
with the name of the imported device. If the import is not successful, an error
dialog appears, and the node in the tree may be incomplete.
9.2 Notes on Configuration Import

To successfully import one or more configuration files, the following rules
must be taken into account:
• Each remote device in an OptoNet network must have a unique name
and node number within the network.
• Each stand-alone device must have a unique name within the site.
• When importing an RTU50 configuration as an SCD5200, the
Configurator will automatically relocate any card in slot 1 (except an
OptoNet card) to another available slot, as slot 1 is the built-in OptoNet
interface for SCD5200.
• When importing configurations into an OptoNet network, nodes
defining databases points should be imported before the nodes that use
those points. If circular dependencies prevent such an ordering being
chosen, some points may be lost during the import process and the user
will need to manually re-enter some configuration data.

2005663 - Rev. 1.3
10. Configuring Electrobus

The Electrobus expansion interface is only available for the RTU50.
Electrobus expansion is used to place I/O modules into distributed files using
an electrical extender assembly, which allows an RTU50 to consist of up to
four card files.
The RTU50 that contains the CPU board is known as the main file, and is
numbered 1 (one). Using the Electrobus extender, another card file is connected
to the main file, and is numbered file 2 (two). Similarly, a third file can be
connected to file 2 and a fourth file can be connected to file 3. Files 2, 3 and 4
each have a power supply module in slot 1, but no CPU card. The remaining
slots in files 2 to 4 can be configured with I/O modules. Figure 9 illustrates the
expansion of an RTU50 main file using Electrobus expansion.
In the configuration tree, the Electrobus expansion slot appears after the I/O
card and DCB slots and is labelled [EBUS] <EMPTY> before configuration.
To configure an Electrobus expansion interface, right-click on this node and
select Create. The sub-menu lists the card files that may be configured, and
these are:
• 6 Slot 19 inch Rack
Select the appropriate card file. The card file’s window displays in the right
pane. Configure the parameters.
The node in the tree for the Electrobus expansion interface is renamed to
Ebus_to_File_x, where x is the file number automatically assigned by the
System Configurator. In the RTU50’s configuration tree, at the card file level,
appears a node labelled [x] card file type, where x is as above. For example, if
the node is labelled [2] 3_Slot_Backplane, this indicates that a 3 Slot
Backplane is configured as card file 2. This is shown in Figure 10. It is from
this node that the card file’s slots can be configured. It is also from this node
that the card file is deleted if it is no longer required.

2005663 - Rev. 1.3
RTU50 Main File
1 2 3 4 5 6
Power Supply &
Electrobus
CPU
1
Power Supply & 2 3
I/O Module
I/O Module
File Number 2
Electrobus
Electrobus
1 2 3 4 5 6
Power Supply &
I/O Module
I/O Module
I/O Module
I/O Module
I/O Module File Number 3

Electrobus
Electrobus
1 2 3
Power Supply &
File Number 4
I/O Module
I/O Module
Electrobus
Electrobus
Figure 9: Example Electrobus configuration.

In file 2, a slot in the card file labelled [EBUS1] <EMPTY> is where another
Electrobus expansion interface to another card file can be configured, following
the process described in this section. A slot labelled [EBUS2]
EBUS_to_File_1, is reserved for the Electrobus expansion connection back to
file 1 and is not available for configuration. For the remaining slots, the
following I/O modules can be configured:
• 20 AI
• 20 AI Type 2
• ADI
• ADI Type 2
• AO

2005663 - Rev. 1.3
• Multi IO
• TDO
• TDO (10 Amp)
• AC Transducer
The configuration process for these modules is the same as described in Section
12.
Electrobus Node
Card File Node
Figure 10: Electrobus expansion nodes.

2005663 - Rev. 1.3
11. Configuring Optobus Master

Optobus Master is only available for the RTU50.
Optobus is used to place I/O modules into distributed files via optical, star
topology links. The RTU50 that contains the Optobus Master module is known
as the main file. The distributed files are known as sub-files, and each contains
an Optobus Slave module that the Master connects to. Each Optobus Master
module can connect to as many as eight Optobus Slave units. The main file can
accommodate up to three Optobus Master modules, for a maximum of 24
distributed sub-files containing I/O modules. Each sub-file has its own power
supply but no processor or communications controller.
Figure 11 illustrates the expansion of an RTU50 main file using Optobus. The
main file contains two Optobus Master modules (in slots 3 and 5), each of
which connect to sub-files containing Optobus Slave modules and I/O modules.
RTU50 Main File
Optobus Master Module
1 2 3 4 5 6
Power Supply &
CPU
1 2 3 1 2 3
Power Supply &
Power Supply &

Optobus Slave
Optobus Slave
I/O Module
I/O Module
I/O Module
I/O Module
1 2 3 4 5 6 1 2 3
Power Supply &
Power Supply &

Optobus Slave
Optobus Slave
I/O Module
I/O Module
I/O Module
I/O Module
I/O Module
I/O Module
I/O Module
Figure 11: Example Optobus configuration.

To configure Optobus Master, right-click on the slot’s node and from the menu
select Create. From the sub-menu that displays select Optobus Master. The
Optobus Master window displays in the right pane. The node’s name in the
tree changes to the name the Optobus Master module is configured with.

2005663 - Rev. 1.3
The Optobus Master node menu has three options: Edit, Delete, and Refresh.
Edit - displays the Optobus Master window in the right pane, allowing
the user to view and change the parameters currently configured
for the module.
proceed with the deletion of the Optobus Master module. BE
AWARE that deleting an Optobus Master module also deletes all
ports configured for the module, and all card files configured for
the ports. If the user confirms that they want to delete the Optobus
Master module, the module and all of its information is removed
from the configuration. If the user chooses not to proceed with the
deletion, the configuration remains unchanged.
Refresh - refreshes the display of the configuration tree under the Optobus
Master module’s node.
Opening the Optobus Master’s node displays eight nodes, one for each port,
numbered [1] to [8]. For each port, sometimes known as a channel or sub-file, a
card file can be configured. To configure a card-file for an Optobus Master
port, right-click on the port’s node and choose Configure from the menu. A
sub-menu displays with the possible choices of card files, which are:
• 6 Slot 19 inch Rack
Select the appropriate card file and configure the card file’s parameters.
The node in the tree for the Optobus Master port is renamed to
Obus_to_File_ab, where a is the number of the slot that the Optobus Master
module is configured in, and b is the number of the Optobus Master port that
the card file is configured for. In the RTU50’s configuration tree, at the card
file level, appears a node labelled [ab] card file type, where a and b are as
above. For example, if the node is labelled [62] 2_Slot_Backplane, this
indicates that the Optobus Master module is configured in slot 6, and a 2 Slot
Backplane is configured for port 2 of the Optobus Master module. This is
illustrated in Figure 12. It is from this node that the card file’s slots can be
configured. It is also from this node that a card file connected via Optobus
Master can be deleted.

2005663 - Rev. 1.3
Optobus Master Node

Optobus Master Port Node
Card File Node
Figure 12: Optobus Master nodes.

The first slot of the card file is reserved for the Optobus connection and is not
available for configuration. For the remaining slots, the following I/O modules
can be configured:
• 20 AI
• 20 AI Type 2
• ADI
• ADI Type 2
• AO
• Multi IO
• TDO
• TDO (10 Amp)
• AC Transducer
The configuration process for these modules is the same as described in Section
12.

2005663 - Rev. 1.3
12. Configuring I/O modules

The I/O modules available for the RTU50 and SCD5200 are listed in Table 3.
This table identifies the names that are used for each I/O module in each remote
device.
RTU50 SCD5200
20 AI 20 AI (non-isolated)
20 AI Type 2 20 AI (isol)
ADI 32DI / 4AI (non-isol)
ADI Type 2 32DI / 4AI (isol)
AO 4AO
Multi IO 24DI / 6AI / 8DO
24DI / 6AI / 6DO
TDO 12DO
TDO (10 Amp) 12DO (10 Amp)
AC Transducer CTVT
Table 3: I/O Modules

Any I/O module can be configured in any slot except for the following
restrictions:
• For an RTU50, if a TDO (10 Amp) or AC Transducer module is
configured in the last slot (right-most slot), the Electrobus expansion
interface is unavailable.
• For an SCD5200, when a 12DO (10 Amp) or CTVT module is
configured, the slot immediately to its right is unavailable.
• For an SCD5200, a 12DO (10 Amp) or CTVT module cannot be
configured in the last slot (right-most slot).
The configuration process for all I/O modules is identical. To configure an I/O
module for a slot, right-click on the slot in the tree and choose Create from the
menu. From the sub-menu that displays, select the I/O module. The I/O
module’s window displays in the right pane. Configure the parameters. In the
tree, the node’s name changes to the name the I/O module is configured with.
The I/O module node menu has three options: Edit, Delete, and Refresh.
Edit - displays the I/O module’s window in the right pane, allowing the
user to view and change the parameters currently configured for
the module.
proceed with the deletion of the I/O module. If the user confirms
that they want to delete the module, the I/O module and all of its
information is removed from the configuration. If the user chooses
not to proceed with the deletion, the configuration remains
unchanged.
Refresh - refreshes the display of the configuration tree under the I/O
module’s node.

2005663 - Rev. 1.3
13. Configuring DCBs (Dual

Communications Boards)
There are three steps to configuring a DCB in a remote device:
1. Configure the board.
2. Configure the ports (channels).
3. Configure the protocol for each port (channel).
Each of these steps is described in the sections below.
13.1 Configure the board

At this point in the configuration, a DCB has been chosen as the item to
configure for a slot. The DCB window displays in the right pane. Configure the
parameters. In the tree, the slot is renamed to the name of the DCB.
Opening the DCB slot node reveals two nodes below it, one for each port
(channel), currently named: [1] <UNASSIGNED> for port 1 and
[2] <UNASSIGNED> for port 2. The configuration of the ports is described
below.
The DCB node menu has three options: Edit, Delete, and Refresh.
Edit - displays the DCB window, allowing the user to view and change
the parameters currently configured for the DCB.
proceed with the deletion of the DCB. BE AWARE that deleting a
DCB also deletes its ports and any protocols configured for its
ports. If the user confirms that they want to delete the DCB, the
DCB and all of its information is removed from the configuration.
If the user chooses not to proceed with the deletion, the
configuration remains unchanged.
Refresh - refreshes the display of the configuration tree under the DCB’s
node.
13.2 Configure the port

To configure a DCB’s port, right-click on the port’s node and choose
Configure Port from the menu. The Port window is displayed in the right
pane. Configure the parameters. The name of the port’s node in the tree updates
to the name the port is configured with. A protocol can now be configured for
the port. This is described in the section below.
The DCB port node menu has four options: Create, Edit, Delete and Refresh.
Create - displays a sub-menu listing the protocols available for
configuration on this port. Note: this menu item is only available if
there is no protocol currently configured for the port.

2005663 - Rev. 1.3
Edit - displays the Port window in the right pane, allowing the user to
view and change the parameters currently configured for the port.
proceed with the deletion of the port. BE AWARE that deleting a
port also deletes the protocol configured for the port. If the user
confirms that they want to delete the port, the port and all of its
unchanged.
Refresh - refreshes the display of the configuration tree under the port’s
node.
13.3 Configure the protocol

The protocols available for configuration for a DCB port, are dependent on the
type of the DCB. Table 4 identifies the protocols that can be configured for
each DCB. indicates the protocol is available, indicates that it is not.
Protocol: V.11 V.23 V.28 Optical Generic

DNP3 Slave
DNP3 Master
IEC 101 Slave
IEC 103 Master
Conitel Slave
Conitel Master
C300 Slave
C3000 Slave
Table 4: DCB Protocols
Note: Generic DCBs – A Generic DCB is used when the type of the DCB in
the physical slot is unknown. All DCB parameters are offered for configuration,
and those that are not required by the DCB that physically resides in the slot,
are ignored.
To configure a protocol for a DCB’s port, right-click on the port’s node and
choose Create from the menu. A sub-menu of protocols available for the port is
displayed. Select the appropriate protocol and configure its parameters. A node
with the name the protocol is configured with appears in the tree under the
port’s node. Protocol configuration is further discussed in Section 17.
Note: Ensure that the correct protocol is selected for the DCB physically
located in the remote device. For example, System Configurator will allow
DNP3 Slave, DNP3 Master and IEC 103 Master to be configured for an Optical
DCB. However, for the configuration to load successfully on the remote device,

2005663 - Rev. 1.3
the DCB must have the correct firmware for the protocol configured. So, if
DNP3 Slave is configured for the DCB’s port, the physical DCB in the remote
device must have the DNP3 firmware.

2005663 - Rev. 1.3
14. Configuring OptoNet modules

For each remote device on an OptoNet network, exactly one OptoNet module
must be configured. A remote device cannot have more than one OptoNet
module. Remote devices that do not belong to an OptoNet network should not
have an OptoNet module configured.
Each SCD5200 has the node [OPT] OptoNet in its configuration tree, as the
OptoNet module is part of the SCD5200’s main processor board. To configure
the parameters for the OptoNet module or change it’s name, right-click on the
node and choose Edit from the menu. The OptoNet window displays in the
right pane. Configure the parameters. In the tree, the name of the slot changes if
the name is changed in the OptoNet window.
For an RTU50, the OptoNet module can be configured in any unoccupied slot.
Unlike the SCD5200, the OptoNet module is not automatically created for the
RTU50, as the user must choose which slot to configure the module in.
To create an OptoNet module for an RTU50, right-click on the chosen slot in
the tree and select Create from the menu. From the sub-menu that displays,
select OptoNet. The OptoNet window displays in the right pane. Configure the
parameters. In the tree, the slot’s name changes to the name of the OptoNet
module.
The OptoNet module node menu has three options: Edit, Delete, and Refresh.
Edit - displays the OptoNet module’s window in the right pane, allowing
for the module.
proceed with the deletion of the OptoNet module. If the user
confirms that they want to delete the module, the OptoNet module
and all of its information is removed from the configuration. If the
user chooses not to proceed with the deletion, the configuration
remains unchanged.
Refresh - refreshes the display of the configuration tree under the OptoNet
module’s node.
For detailed information about OptoNet networks and modules refer to the
“OptoNet Software User Manual for the RTU50 and SCD5200” [7].

2005663 - Rev. 1.3
15. Configuring serial ports

This section describes configuration of serial ports, including the COM2 serial
port and the ports of the 8 and 12 channel serial cards.
Each serial port may be configured as a standard serial port (providing a direct
connection to an external device) or as a dialup serial port (providing a
connection via a modem and telephone line).
There are two steps to configuring a COM2 port in a remote device:
1. Configure the port (channel).
2. Configure the protocol for the port (channel).
There are three steps to configuring an 8 or 12 Channel Serial Card in a remote
device:
1. Configure the serial card.
2. Configure the port/s (channels).
3. Configure the protocol for each port (channel).
Each step is described in the sections below.
15.1 Configure the serial card

At this point in the configuration, 8 Chn Serial or 12 Chn Serial has been
chosen as the item to configure for a slot. The Serial Card window displays in
the right pane. Configure the parameters. In the tree, the name of the slot
changes to the name the serial card is configured with.
Opening the card’s node reveals a node for each port (channel) on the card. For
an 8 Channel Serial Card eight nodes display numbered [1] to [8] and all named
<UNASSIGNED>. For a 12 Channel Serial Card, twelve nodes display
numbered [1] to [12] and all named <UNASSIGNED>. The configuration of
the ports is described below.
The serial card node menu has three options: Edit, Delete, and Refresh.
Edit - displays the Serial Card window in the right pane, allowing the
the serial card.
proceed with the deletion of the serial card. BE AWARE that
deleting a serial card also deletes its ports and any protocols
configured for its ports. If the user confirms that they want to
delete the serial card, the card and all of its information is removed
Refresh - refreshes the display of the configuration tree under the serial
card’s node.

2005663 - Rev. 1.3
15.2 Configure the serial port

To configure COM2 or a serial card’s port, right-click on the port’s node and
choose Configure from the menu, then choose Port or Dialup Port from the
sub-menu. The Port or Dialup Port window is then displayed in the right pane.
Configure the parameters. In the tree, the name of the port updates to the name
the port is configured with. A protocol can now be configured for the port. This
is described in the section below.
The serial port node menu has four options: Create (if no protocol is currently
configured for the port), Edit, Delete and Refresh.
configuration on this port. Note: This menu item is only available
if there is no protocol currently configured for the port.
Edit - displays the Port dialog, allowing the user to view and change the
parameters currently configured for the port.
proceed with the deletion of the port. BE AWARE that deleting a
port also deletes the protocol configured for the port. If the user
confirms that they want to delete the port, the port and all of its
unchanged.
Refresh - refreshes the display of the configuration tree under the serial
port’s node.
15.3 Configure the protocol

The protocols available for configuration on serial ports are:
• DNP3 Slave – Serial and Dialup
• DNP3 Master – Serial and Dialup
• Event Logger
• IEC 60870-5-101 Master
• Modbus Slave
• Modbus Master
• SALL HLSI
• Terminal Server
To configure a protocol for a serial card’s port, right-click on the port’s node
and choose Create from the menu. A sub-menu of protocols available for the
port is displayed. Select the appropriate protocol and configure its parameters.
A node with the name the protocol is configured with appears in the tree under
the port’s node. Protocol configuration is further discussed in Section 17.

2005663 - Rev. 1.3
16. Configuring Ethernet

The RTU Ethernet interface enables various SCADA protocols to be carried
over TCP/IP and UDP/IP.
The Ethernet part of the main processor board has a node in the tree named [IP]
Eth by default for an SCD5200 and an RTU50 with a CPU card type of P3E,
and [IP] <EMPTY> for an RTU50 with a CPU card type of P2E. For this latter
type of RTU50 it is necessary to create the Ethernet card. This is not necessary
for an SCD5200 or an RTU50 with the P3E CPU card, as Ethernet is a built-in
feature of these main processor boards.
To configure Ethernet for the RTU50 with the P2E CPU card, right-click on the
[IP] <EMPTY> node and choose Create from the menu. From the sub-menu
that displays, choose Ethernet. The Ethernet window displays in the right
pane. Configure the parameters. Note: Channel A must be configured for the
Ethernet interface to operate. In the tree the node name is changed to the name
the Ethernet interface is configured with.
The Ethernet node menu has four options: Create, Edit, Delete, and Refresh.
configuration on the Ethernet interface.
Edit - displays the Ethernet window in the right pane, allowing the user
to view and change the parameters currently configured.
Delete - For an SCD5200 or RTU50 with a P3E CPU card, a dialog
displays informing the user that Ethernet is part of the main
processor board and cannot be deleted.
For an RTU50 with a P2E CPU card, a dialog displays prompting

the user to confirm that they wish to proceed with the deletion. BE
AWARE that deleting the Ethernet configuration also deletes the
protocol configured. If the user confirms that they want to proceed,
all of the Ethernet information is removed from the configuration.
If the user chooses not to proceed with the deletion, the
configuration remains unchanged.
Refresh - refreshes the display of the configuration tree under the TCP/IP
node.
To configure a protocol for the Ethernet interface, right-click on the Ethernet
node and choose Create from the menu. A sub-menu displays, listing the
protocols available for configuration on the Ethernet interface. Select the
appropriate protocol and configure its parameters. A node with the name the
protocol is configured with appears in the tree under the Ethernet node.
Protocol configuration is further discussed in Section 17. Protocols available
for configuration on an Ethernet port are:
• DNP3 Slave (via TCP/IP and UDP/IP)
• DNP3 Master (via TCP/IP and UDP/IP)
• Modbus/TCP Master (via TCP/IP only)
In the I/A SCADA remote devices, the Ethernet interface has two channels, A

2005663 - Rev. 1.3
and B. The two channels simply act as two alternate connections to the single
TCP/IP and UDP/IP interface. Any combination of multiple protocol instances
can be configured to operate on this interface concurrently. That is, the TCP/IP
interface is NOT restricted to having one protocol configured at a given time.
For detailed information about the Ethernet interface and its configuration,
refer to the “TCP/IP Software User Manual for the RTU50, SCD5200 and
CLS” [3].

2005663 - Rev. 1.3
17. Configuring Protocols

Protocols provide SCADA communications capability between devices.
Devices are designated as either masters or slaves. A “master” device collects
data from one or more slaves, usually by “polling” the slave devices regularly
for updates of data. The master controls the flow of data (hence the name
“master”). It may also initiate control operations as an output to the slave
device.
This section describes the configuration of all master and slave protocols that
may be configured for I/A SCADA remote devices. Master protocol
configuration is described in Section 17.1, and slave protocol configuration is
described in Section 17.2. I/A SCADA remote devices that are configured with
master protocols can communicate with slave devices that are not I/A SCADA
devices. In this case, the slave device is configured as an IED (Intelligent
Electronic Device) as described in Section 17.3. The configuration of the SALL
High Level Serial Interface for an I/A SCADA remote device is described in
Section 17.4.
17.1 Configuring master protocols

There are three steps to configuring a master protocol for an I/A SCADA
remote device using the System Configurator:
1. Configure the Master Group.
2. Configure the Master Entity (includes selecting the slave to connect to).
3. Configure the Polling Groups.
Points configured in polling groups result in the creation of these points by the
master protocol. When the master polls the slaves these points are updated.
Steps 2 and 3 are repeated for each slave device that the master communicates
with. Figure 13 illustrates the comparison of a physical representation of a
master device and the slave devices it communicates with, with the System
Configurator’s representation of the same master and slaves.
Slave devices can be previously configured I/A SCADA remote devices, or
IEDs (that is, slave devices where all that is known about them is what is
required for the Master to be able to poll data). An IED slave device can be
created at the IED node in the configuration tree, or from the Master entity
window at the Connected Slave tab.
Figure 14 shows where the components of a Master protocol configuration
appear in the configuration tree, including slave devices that are configured as
IEDs. In this example, DNP3 Master is configured for a V.28 DCB’s port. The
DNP3 Master group is named DNPM_Grp1, and it connects to three slave
devices, denoted by the three Master entities under the group node. The slaves
that the Master entities connect to are a DNP3 Slave configured for a V.28
DCB port (DNPS1) in an RTU50, and two IEDs configured as DNP3 Slaves
(DNPS_IED1, DNPS_IED2). These connections are identified in the
configuration tree by the numbers that appear to the left of the Master entity
node names and the slave device node names. For the slave device nodes, these

2005663 - Rev. 1.3
numbers represent the address configured for the slave. For the Master entity
nodes, these numbers represent the address of the slave that the Master entity is
connected to. Therefore, from the tree we can deduce that Master entity
DNPM1 is connected to a slave device with address 5, and the slave device
with address 5 is DNPS1.
Master Port Slave Device 1
Physical Slave Device 2

Representation
Slave Device 3
Configure Configure Configure Master Attach Slave

Port Master Group Entity 1 Device 1
Configure Master Attach Slave

System Entity 2 Device 2
Configurator
Representation Configure Master Attach Slave
Entity 3 Device 3
Figure 13: Physical versus System Configurator representations.
The following Master protocols can be configured for I/A SCADA remote
devices using the System Configurator:
• Conitel Master
• DNP3 Master
• IEC 60870-5-101 Master
• IEC 60870-5-103 Master
• Modbus Master
Configuration of each of these protocols, including detailed descriptions of all
configuration parameters, is described in the User Manual for that protocol and
in the System Configurator Online Help system.

2005663 - Rev. 1.3
Master group node

Master entity nodes
DNP3 Slave device
IED DNP3 Slave

devices
Figure 14: Master protocol configuration.
17.2 Configuring slave protocols for I/A

SCADA remote devices
There are two steps to configuring slave protocols using the System
Configurator:
1. Configure the slave.
2. Configure the scan groups for the slave.
Configuring scan groups includes the configuration of points. A slave protocol
allows existing points in the remote device (I/O points, calculation points) to be
telemetered to a master device. To simplify the selection of points for slave
protocols, the System Configurator provides a query capability, enabling the
user to select groups of points in one step rather than selecting many points one
at a time. The query function is accessed via the Select Points button in each
scan group window.
The following slave protocols can be configured for I/A SCADA remote
devices using the System Configurator:
• C300 Slave
• C3000 Slave
• Conitel Slave

2005663 - Rev. 1.3
• DNP3 Slave
• IEC 60870-5-101 Slave
• IEC 60870-5-104 Slave
• Modbus Slave
Configuration of each of these protocols, including detailed descriptions of all
configuration parameters, is described in the User Manual for that protocol and
in the System Configurator Online Help system.
17.3 Configuring slave protocols for IEDs

Where a slave device is not an I/A SCADA remote device, the user must
configure an IED to represent the slave device. The IED configuration contains
only the subset of the protocol’s parameters required for the master to connect
to the slave and poll data.
The following slave protocols can be configured for IEDs using the System
Configurator:
• Conitel Slave
• DNP3 Slave
• IEC 60870-5-101 Slave
• IEC 60870-5-103 Slave
• Modbus Slave
The configuration of these protocols as IEDs using the System Configurator is
similar to configuring the same protocols on an I/A SCADA remote device, as
described above. Parameters that are specific to I/A SCADA remote devices
are omitted for IEDs.
17.4 Configuring SALL HLSI

The HLSI (High Level Serial Interface) allows the user to define asynchronous,
byte-oriented, communications protocols and to develop applications that
communicate using those protocols. The protocol definition is generated using
the SALLHLSI.EXE configuration program (external to the System
Configurator). The protocol definition file is used to build a SALL HLSI task.
The HLSI provides a suite of functions that can be called within a SALL (State
And Logic Language) program. These functions perform on-line input and
output operations within a SALL task based on the protocol definition. Any of
the three available SALL calculations in an I/A SCADA remote device may use
the HLSI facilities.
There are four steps involved in configuring and using the SALL High Level
Serial Interface:
1. Produce a protocol definition using the SALLHLSI.EXE program.
2. Produce a SALL program that uses the protocol support operations.

2005663 - Rev. 1.3
3. Configure SALL HLSI for a serial port. This step is described below.
4. Configure and compile the SALL program. This step is described in
section 18.
The link between the serial port configured in step 3 above, and the SALL High
Level Serial Interface implemented in the SALL program, is established in the
SALL program by calling the protocol support function SerialInitialise(). It is
therefore important that the port initialised in the SALL program is the same
port that is configured in the remote device with a SALL High Level Serial
Interface.
In an I/A SCADA remote device, SALL HLSI (State And Logic Language High
Level Serial Interface) can be configured for the CPU Serial (COM2) port, 8
Channel Serial Card ports, and 12 Channel Serial Card ports (RTU50 only).
The configuration of the serial ports is described in Section 15.
To configure SALL HLSI for a serial port, right-click on the port’s node, and
choose Configure from the menu. A sub-menu displays, listing the available
protocols – select SALL HLSI. The SALL HLSI window displays in the right
pane. Configure the parameters. A node appears in the configuration tree, under
the port’s node, with the name SALL HLSI is configured with.
The SALL HLSI node menu has two options: Edit and Delete.
Edit - displays the SALL HLSI window in the right pane, allowing the
user to view and change the parameters currently configured.
proceed with the deletion of SALL HLSI for the port. If the user
confirms that they want to delete the interface, the interface is
removed from the configuration. If the user chooses not to proceed
with the deletion, the configuration remains unchanged.
For detailed information on the SALL High Level Serial Interface, refer to the
“SALL High Level Serial Interface User Manual for the RTU50, RTU10,
SCD5200 and CLS” [8].

2005663 - Rev. 1.3
18. Configuring calculations

Each configured remote device has a Calculations node in its configuration
tree. From this node the user can configure IDF (Intrinsic Database Function)
Calculations, SALL (State And Logic Language) Calculations, and ISaGRAF
Calculations.
The Calculations node menu has one active item: Refresh.
Refresh - refreshes the display of the configuration tree under the
Calculations node.
Opening the Calculations node reveals three nodes below it – one for each type
of calculation that can be configured for a remote device:
• IDF
• SALL
• ISaGRAF
18.1 IDF – Intrinsic Database Functions

The Intrinsic Database Functions (IDFs) expand the analog and digital
processing capabilities of the remote device and provide a flexible way to
manipulate and derive calculated data within the remote device. The IDFs
provide a range of embedded functions that can be applied to a remote device’s
database points (source points) to produce new database points (result points).
The result points are then available for use by communications protocols,
physical outputs, and other calculations. IDFs provide several categories of
equations, including arithmetic calculations on analog values, logical
calculations on digital values, operation of controls, evaluation of redundant
inputs and outputs, out-of-range alarming of analog values, and manipulation of
point quality flags. In the I/A SCADA remote devices, one IDF Calculation
group is configured per device. This group is made up of all of the IDF
calculations for the device. Detailed information on IDFs can be found in the
“Intrinsic Database Functions User Manual for the SCD5200, RTU50 and
RTU10” [4].
To configure an IDF calculation group, right-click on the IDF node and select
Configure IDF Calc from the menu. The IDF Calc window displays in the
right pane. Equations are built using the IDF Equation Builder, which is
accessed from the Set AI Eqn and Set DI Eqn buttons (on the IDF Result
Points tab). Configure the calculation parameters and the equations.
The calculation compiles when the Apply button is clicked in the IDF Calc
window. The compiler output displays on the Task Details tab of the window.
Calculations are compiled using the IDF compiler installed with the System
Configurator. A node with the name of the calculation appears under the IDF
node in the configuration tree, when the IDF Calc window is closed.
The IDF calculation node menu has three options: Edit, Delete, and Refresh.
Edit - displays the IDF Calc window in the right pane, allowing the user
to view and change the parameters and equations currently

2005663 - Rev. 1.3
configured for the calculation.

proceed with the deletion of the IDF calculation module. BE
AWARE that deleting an IDF calculation also deletes all
equations configured for the calculation. If the user confirms that
they want to delete the IDF calculation, the calculation and all of
its information is removed from the configuration. If the user
chooses not to proceed with the deletion, the configuration remains
unchanged.
Refresh - refreshes the display of the configuration tree under the IDF
calculation’s node.
18.2 SALL – State And Logic Language

The State And Logic Language (SALL) allows the user to configure both
traditional calculation equations, and calculations based upon the SALL state
machine model, for execution within the framework of the remote device’s
embedded software. A SALL program defines a sequence of instructions that is
executed from beginning to end either at regular intervals (at a periodic rate
stipulated by the programmer) or on demand whenever there is a change in an
input value referenced by the program. SALL itself is, in many aspects, similar
to the C programming language but it has a simpler syntax and some extensions
relating to remote device real-time operation. Detailed information on SALL
can be found in the “RTU Programming User Manual – State And Logic
Language Reference (SALL) for the SCD5200, RTU50 and RTU10” [5].
Configuring a SALL calculation to execute on a remote device involves two
steps:
1. The SALL calculation must be created and/or configured so the System
Configurator is aware of it.
2. The SALL calculation must be compiled for the remote device it is to
execute on. This is described below. The resultant file (.elf file) is
loaded into the remote device’s flash file system.
A maximum of three (3) SALL calculations can be configured at any one time
for a remote device.
Opening the SALL node reveals three nodes below it, one for each calculation
that can be configured for the remote device, and all initially named
[Calc No] <UNASSIGNED>. To configure a SALL calculation, right-click on
one of these nodes and select Configure SALL Calc from the menu. The
SALL Calc window displays in the right pane.
In the SALL Calc window, browse to the source file containing the calculation
program. If the calculation uses the SALL High-Level Serial Interface
(SALLHLSI), the user must also browse to the Protocol Definition File
generated by the external SALLHLSI utility.
When the user clicks the Apply button, the System Configurator will attempt to
perform a test compile of the calculation, showing the output of the compilation
process in the calculation window. If compilation is successful, the System

2005663 - Rev. 1.3
Configurator will fill in the other details of the calculation (priority, periodicity,
etc) and will determine which database points referenced in the calculation
belong to other configured subsystems of the RTU (external points) and which
will need to belong to the SALL calculation itself (internal points). The lists of
internal and external points are displayed on the Parameter Bindings tab.
The SALL calculation node menu has three options: Configure SALL Calc,
Edit, and Delete.
Configure SALL Calc – displays the SALL Calc window in the right pane,
allowing the user to configure a SALL calculation. Note: This
menu item is only available if a calculation is not currently
configured for the node.
Edit - displays the SALL Calc window in the right pane, allowing the
the calculation.
proceed with the deletion of the SALL calculation. If the user
confirms that they want to delete the calculation, it is removed
Note that the test compile does not produce a binary (.elf) file for the
calculation. A “real” compile of a SALL calculation, that is a compile that
produces an executable (.elf) file, is invoked from the remote device’s menu.
Right-click on the RTU50’s or SCD5200’s node and select Compile SALL
from the menu. The SALL Compile window displays in the right pane. The
executable (.elf) SALL files generated are saved in the directory specified by
the Output path parameter. Change this parameter if necessary. To compile
configured SALL calculations, click the Compile and Export SALL Calcs
button. The output from the compiler displays in the Compiler Output area,
and notifies the user of the success or failure of the compilation. Compiled files
have the same name as the source files but with a .elf extension.
18.3 ISaGRAF
The International Standard IEC 61131-3 specifies the syntax and semantics of
the unified facilities suite of programming languages for programmable
controllers. The I/A SCADA remote devices use ISaGRAF, a third party IEC
61131-3 compliant software package, to provide a programming and runtime
environment. Detailed information on ISaGRAF can be found in the “IEC
61131-3 Programming and Runtime Environment User Manual for the RTU50
and SCD5200” [6].
Configuring an ISaGRAF calculation to execute on a remote device involves
four steps:
1. The ISaGRAF calculation’s executable file and connection file names
must be configured by adding the calculation to the tree under the Calc
Sources | ISaGRAF node.
2. Configuration of the Ethernet interface (Section 16) or serial
communications (Section 15) port to use for ISaGRAF debugging.

2005663 - Rev. 1.3
3. The ISaGRAF calculation must be configured as a task for the remote

device. This is also known as configuring the database connections and
is described below.
4. Configuration of an IDF calculation for the controls. This provides an
interface between ISaGRAF and the remote device’s output subsystem,
and is needed to maintain the security of controls associated with
master communications protocols or output modules. Configuring IDFs
is described in Section 18.1.
A maximum of three (3) ISaGRAF calculations can be configured at any one
time for a remote device. Opening the ISaGRAF node reveals three nodes
below it, one for each calculation that can be configured for the remote device,
and all initially named [Calc No] <UNASSIGNED>. To configure an
ISaGRAF calculation, right-click on one of these nodes and select Configure
ISaGRAF Calc from the menu. The ISaGRAF Calc window displays in the
right pane. Configuring the calculation’s parameters means the calculation is
configured as a task in the remote device. The calculation’s node in the
configuration tree is renamed to the name the calculation is configured with.
The ISaGRAF calculation node menu has three options: Configure ISaGRAF
Calc, Edit, and Delete.
Configure ISaGRAF Calc – displays the ISaGRAF Calc window in the right
pane, allowing the user to configure an ISaGRAF calculation.
Note: This menu item is only available if a calculation is not
currently configured for the node.
Edit - displays the ISaGRAF Calc window in the right pane, allowing
for the calculation. Note: this menu item is only available if a
calculation is currently configured for the node.
proceed with the deletion of the ISaGRAF calculation. If the user
confirms that they want to delete the calculation, it is removed
deletion, the configuration remains unchanged. Note: this menu
item is only available if a calculation is currently configured for
the node.

2005663 - Rev. 1.3
19. Predefined points

For each RTU, there is a set of analog and digital database points that are
always defined. These points belong to the RTU’s System Monitor (SysMon)
subsystem and are automatically created at RTU startup.
Aside from the fact that these points are pre-defined and do not appear in the
configuration file, the System Configurator treats these points just like any
other point of the same type. The pre-defined points may be included in
protocol telemetry lists, may be used in IDF equations, may be used as a control
inhibit point (digital points only), and so on.
The names of the pre-defined points are shown in Table 5. These names are
reserved and may not be used for other points in the user’s configuration. In
the table, n refers to the RTU’s OptoNet node number (usually 1 for a stand-
alone RTU). For example, the System Fail point for OptoNet node 23 would be
called SysFail23.
Name: Type: Description:
SysFailn Digital System Failure point.
RTUResetn Digital RTU reset indicator. Communications
protocols usually clear this point after
reporting it.
Flash_OKn Digital Indicates whether the Flash File System
is present, enabled and healthy
FlashIdentn Analog Checksum of running software,
configuration and calculation files.
DynamicHeapSizen Analog The amount of memory available for
dynamic allocation after startup.
DynamicHeapLeftn Analog The amount of memory in the dynamic
heap not currently allocated.
LargestDynamicBlockn Analog The largest contiguous block available
in the dynamic heap.
StaticHeapSizen Analog The amount of memory available after
loading the RTU Software and
allocating the dynamic heap.
StaticHeapLeftn Analog The amount of memory not used after
loading the running configuration and
calculation files.
Calc1Sizen Analog The size of the first running SALL
calculation, or 0 if no calculation is
running.
Calc2Sizen Analog The size of the second running SALL
running.

2005663 - Rev. 1.3
Name: Type: Description:

Calc3Sizen Analog The size of the third running SALL
running.
LocalToolSessionn Digital Indicates whether a diagnostic session
is currently running on the local COM1
serial port.
RemoteToolSessionn Digital Indicates whether a diagnostic session
is currently running via OptoNet or
TCP/IP.
IsaGraf1Sizen Analog The size of the first running ISaGRAF
running.
IsaGraf2Sizen Analog The size of the second running
ISaGRAF calculation, or 0 if no
calculation is running.
IsaGraf3Sizen Analog The size of the third running ISaGRAF
running.
BatteryBackUpFailedn Digital Indicates whether the CPU backup
battery requires replacement.
NVRAMFailedn Digital Indicates that a failure of non-volatile
RAM hardware or corruption of point
values stored in non-volatile RAM has
been detected.
NVRAMSizen Analog The amount of non-volatile RAM fitted
to the RTU, usually 32K for P2 and
P2E CPU cards and 128K for COPE
and P3E CPU cards.
NVRAMLeftn Analog The amount of non-volatile RAM that is
not used by the current configuration.
Table 5 - Reserved point names

2005663 - Rev. 1.3
20. Generating and Browsing

Configuration Files
System Configurator provides features for generating (creating) and browsing
(viewing) configuration files for an I/A SCADA remote device. Generating
configuration files is described in Section 20.1. The browsing feature allows
the user to view different versions of a remote device’s configuration file, and
this is described in Section 20.2.
20.1 Generating configuration files

A configuration file can be generated (created) for an I/A SCADA remote
device. Configuration files have a .cfg extension, and are transferred to the
remote device’s flash file system using one of the diagnostic utilities, TOOL32
and the Remote Terminal Viewer. System Configurator provides facilities for
generating a configuration file for a single remote device, for all stand-alone
remote devices in a site, and all remote devices in an OptoNet network. How to
use System Configurator to generate configuration files is described in the
sections below.
20.1.1 Generating a configuration for a remote device

To generate a configuration for an I/A SCADA remote device, right-click on
the remote device’s node in the configuration tree and select Generate CFG.
The Generate Configuration window displays in the right pane. If directory
path and file names have been configured, these appear in the Configuration
file field. This field can be changed if necessary. To generate the configuration
file for the remote device, click the Generate Configuration button. The status
bar at the bottom of the window indicates the progress and success of the
generation. If the configuration file generation is successful, the configuration
displays in the Generated Configuration panel of the window. If the
generation fails, a dialog displays informing the user of which part of the
configuration failed. To save the generated configuration to the nominated file,
click the Save to File button. The status bar at the bottom of the window
indicates the success of the save.
20.1.2 Generating configurations for a site

Configuration files can be generated for all, or a selected group, of stand-alone
remote devices within a site (stand-alone means that the remote devices are not
part of an OptoNet network). Right-click on the RTUs node under the site’s
node, and choose Generate CFGs. The Bulk Configuration Generator
window displays listing all remote devices currently configured for the site.
Select the remote devices to generate configuration files for by clicking the
Select All button to select all of the remote devices, or checking the check
boxes to the left of the remote device’s names, for selected devices. The
currently configured file path and name for each remote device’s configuration
file displays to the right of the device’s name. To change the file name and/or
path, click the … button that appears to the right of the file name.

2005663 - Rev. 1.3
To generate the configuration files for the selected remote devices, click the
Generate button. The status bar at the bottom of the window indicates the
progress and success of the generation. If the generation is successful, a
message stating that the generation is complete appears in the status bar. If the
generation fails, a dialog box displays informing the user of which part of the
generation failed.
20.1.3 Generating configurations for an OptoNet

network
Configuration files can be generated for all, or a selected group, of remote
devices within an OptoNet network. Right-click on the OptoNet network’s node
and choose Generate CFGs. The Bulk Configuration Generator window
displays listing all remote devices currently configured for the OptoNet
network. Select the remote devices to generate configuration files for by
clicking the Select All button to select all of the remote devices, or checking
the check boxes to the left of the remote device’s names, for selected devices.
The currently configured file path and name for each remote device’s
configuration file displays to the right of the device’s name. To change the file
name and/or path, click the … button that appears to the right of the file name.
To generate the configuration files for the selected remote devices, click the
Generate button. The status bar at the bottom of the window indicates the
progress and success of the generation. If the generation is successful, a
message stating that the generation is complete appears in the status bar. If the
generation fails, a dialog box displays informing the user of which part of the
generation failed.
20.2 Browsing configuration files

The browsing feature of the System Configurator allows the user to select a
version of an I/A SCADA remote device’s configuration file. Each time a
configuration is generated for a remote device, a new version of the device’s
configuration is created and it is timestamped to uniquely identify it.
To browse an I/A SCADA remote device’s configuration files, right-click on
the remote device’s node in the configuration tree and select Browse CFG
from the menu. The Browse Configuration Files window displays in the right
pane. Select the version of the configuration file from the Date of Generated
Configuration list. The format of the date and time stamp is:
Year-Month-Day Hour:Minute:Second.Milliseconds.
Once a selection is made the contents of the configuration file displays in the
Generated Configuration for Selected Date area of the dialog.
The user can also save different versions of the remote device’s configuration
file with different file names from this window. To do this, enter the new file
name in the Configuration file field, and click the Save to File button.

2005663 - Rev. 1.3
21. Database Maintenance Utilities

Within the System Configurator, individual remote device configuration may
be backed up and restored using the configuration generation and import
features.
However, at various points within the development of a project, it may be
desirable to make a backup or snapshot of the entire configuration database.
When upgrading the System Configurator software to a later release, the
installation program will offer to make a backup of any existing configuration
database before performing the upgrade. If the user proceeds with the backup,
the backup file is placed in the userdatabackup.dat file in the parent directory
of the System Configurator installation directory.
At other times, the user may backup the database by using the backup and
restore utility supplied with the System Configurator, as described in Section
21.1.
A database backup can be restored using the same utility by following the
process described in Section 21.2.
As a user’s configuration database grows, the System Configurator’s
performance may begin to degrade. This can be addressed by using the
database compression utility as described in Section .
21.1 Backup the configuration database

All configurations created with System Configurator on one computer reside in
one database. To backup (or save) this database to a file:
1. Close the System Configurator if it is running.

2. Click on the Start button and select Programs Foxboro System
Configurator Database Backup.
3. Enter the backup path and file name in the edit box or clock the …
button to browse to a suitable location.
4. Click the Backup button to begin the backup.
21.2 Restore the configuration database

The System Configurator database can be restored from a file created using the
backup utility described above in Section 21.1. BE AWARE that restoring the
database will destroy any existing configurations currently in the System
Configurator database.
To restore the System Configurator database from a backup file:
2. Click on the Start button and select Programs Foxboro System
Configurator Database Backup.

2005663 - Rev. 1.3
3. Enter the path and file name of an existing backup file in the edit box or
clock the … button to browse to a suitable file.
4. Click the Restore button to begin the restore.
21.3 Compressing the configuration database

From time to time, the performance of the System Configurator can be
optimised by compressing the database to eliminate deleted records.
To compress the database:
2. Click on the Start button and select Programs Foxboro Compress
System Configurator Database.

2005663 - Rev. 1.3
22. Troubleshooting
This section provides information and solutions to known causes that prevent
System Configurator from operating correctly. These causes are not listed in
any particular order and all should be checked.
22.1 The required services are not running.

The status of the postmaster and ipc-daemon services can be checked by
starting the Service Manager. This program is called Services and can be
found in either Control Panel on Windows NT machines or Control
Panel/Administrative Tools on Windows 2000 and Windows XP machines. If
the services have started, the word Started appears in the Status column to the
right of the service’s name. If either of the services has not started, then initially
try to start them manually by selecting the required service and clicking the
Start button (located in the toolbar at the top of the dialog).
If the services fail to start, there are a number of possible reasons that are
detailed below.
• The postmaster.pid file was not deleted when the postmaster service last
stopped. This usually occurs because the computer was rebooted without
shutting down properly.
Delete the postmaster.pid file using the steps described below and restart
the service using the method described above or restart the machine.
Deleting the postmaster.pid file

To delete the postmaster.pid file, follow these steps:
• Using Windows Explorer or My Computer, navigate to the [Cygwin
Base]\usr\local\postgresql\data directory. [Cygwin Base] is the
directory path to where the Cygwin directory is installed.
• delete the postmaster.pid file. If a message displays that you do not
have permission to delete the file, continue with the steps below.
Depending on the version of Cygwin/PostgreSQL installed on the
machine, this file may have its owner set to SYSTEM. To be able to delete
the file, the ownership of the file must be changed to the current user. To
change the ownership on a Windows 2000 or Windows XP machine:
• right-click on postmaster.pid and choose Properties from the menu.
The postmaster.pid Properties dialog displays.
• Click the Security tab. If you receive a Security dialog stating that
you only have permission to view the current security information,
click the OK button to dismiss the dialog.
• On the Security tab, click the Advanced button. The Access Control
Settings for postmaster.pid dialog displays.
• Click the Owner tab. The Current owner of this item needs to be the
user of System Configurator.

2005663 - Rev. 1.3
• Click the user’s name or identifier in the Change owner to list and
click the OK button.
• Click the OK button in the postmaster.pid Properties dialog.
It is now necessary to set the permissions for the new owner. To do this:
• Right-click on postmaster.pid and select Properties from the menu.
• Click the Security tab.
• In the Name list select the user’s identifier.
• In the Permissions list, allow Full Control.
• Click the OK button.
• Delete the postmaster.pid file.
To change the ownership on a Windows NT machine:

• right-click on postmaster.pid and choose Properties from the menu.
• Click the Security tab.
• On the Security tab, click the Ownership button. The Owner dialog
displays. The owner needs to be the user of System Configurator.
• Click the Take Ownership button. The current user becomes the
owner of the postmaster.pid file, and the Owner dialog closes.
• In the postmaster.pid Properties dialog, click the Permissions
button. Ensure that the user (now the owner) has Full Control
privileges, and click the OK button.
• Click the OK button in the postmaster.pid Properties dialog.
• Delete the postmaster.pid file.
• The services may not be installed properly.

Remove the existing services, ipc-daemon and postmaster, and reinstall
these services.
The services are removed by running the remove_postgresql_services.bat
file, which is found in the [Foxboro Directory]\Batch Files directory.
The services are installed by running the install_postgresql_services.bat
file, which is also found in the [Foxboro Directory]\Batch Files
directory.
If this method to create services does not succeed, then attempt the method
outlined in [Cygwin Directory]\usr\doc\Cygwin\postgresql-*.README
file. This document will take you through the steps of installing the
services from first principles (do not add another user (postgresql)).

2005663 - Rev. 1.3
• If the error “Network password not correct when starting the ipc-daemon
or postmaster” is displayed while attempting to start the services this
indicates that the current user does not have sufficient privileges to start
the services. The current user must log off the computer and the
Administrator must log in to the computer to start the services, which can
be achieved by running the commands:
net start ipc-daemon
cygrunsrv –S postmaster
in the displayed order. After this is done and the services are started the
Administrator can log off and the normal user can log on and continue.
22.2 Check that all temporary files created by

the PostgreSQL service have been
deleted.
The files created, while the PostgreSQL service is running, can be determined
by the following search string:
[Cygwin_home]\tmp\.s.pgsql.5432*
If these files do exist on the machine at the location specified then delete them
and try restarting the System Configurator.
22.3 Check permissions on PostgreSQL files

Check the log file found in [Cygwin base]var\log\postmaster.log using a text
editor such as Notepad. Ensure that this file is readable and writable by
everyone (if not change it so that it is and restart System Configurator).
If the log file reports that files are not readable or do not exist, ensure that all
files and folders under [Cygwin base]usr\local\postgresql\data have
permissions for everyone to read, write and execute.
Ensure that the file postgres.exe can be executed by everyone. From Cygwin,
this can be achieved by the command chmod 755 /bin/postgres.exe.
22.4 The Cygwin “Administrator” user must

exist on the local machine.
To create the Administrator user simply run the createuser command as
follows:
C:\>createuser
Enter name of user to add: Administrator
Shall the new user be allowed to create databases? (y/n) y

2005663 - Rev. 1.3
Shall the new user be allowed to create more new users? (y/n) y
CREATE USER
C:\>
22.5 Check that the ROOTDB and SYSCFG

databases exist on the PostgreSQL
service.
This can be checked by running the command
C:\>Psql -l
If the ROOTDB and SYSCFG databases do not appear in the generated list
then the databases may not have not initialised correctly. To initialise the
databases run recreate_all.cmd which is located in the [Foxboro
Directory]\System Configurator\Docs\PostgreSQL directory.
NOTE: During the initialisation of the databases a command prompt will
appear on the screen to display the output of the various commands. Depending
on what was previously installed some of these commands may fail and
produce output that indicates an error has occurred. To ensure that the
initialisation has occurred successfully wait until all of the commands have
finished and repeat the steps indicated at the start of this section to check that
the ROOTDB and SYSCFG databases exist.
BE AWARE that the recreate_all script deletes any existing configuration
data. Extreme caution should be exercised when deciding to invoke this script
and it is recommended that Foxboro Australia’s support group (SPS) be
contacted before doing so. SPS can be contacted by email at
sps@invensys.com.
22.6 Domain server access

During the installation phase of the System Configurator the installation
program attempts to connect to the domain server to resolve the username of
the current user.
If this connection fails then the installation program attempts to connect to the
local machine. Occasionally, although the user logs on to the machine
specifying a domain, any attempt to later connect to the domain server fails and
therefore the installation fails as a result. If this is suspected, create a user on
the local machine using the same username/password combination and attempt
the installation again. Another workaround is to just log on to the local machine
using an account that is valid (that is, exists on the local machine and has
administration rights). Once the installation has been successful then any
account may be used.

2005663 - Rev. 1.3
22.7 The jdbc version is incompatible with the

PostgreSQL version.
The current version of System Configurator has been tested against version 7.4
of the PostgreSQL database. The compatible version of the jbdc Java utility is
supplied with the System Configurator. The supplied jbdc file is backwards
compatible with some earlier versions of PostgreSQL, but may not be
compatible with later versions. Please contact the support group (email
sps@invensys.com) for assistance with changing the version of the jbdc utility
used by the System Configurator.
22.8 User could not be correctly authenticated

During the installation process the logon details of the current user on the
computer are verified automatically. There are situations that exist where this
process will fail and therefore the installation cannot continue. An example
situation is when the user, who exists a domain but not as a local user, logs on
to the domain and then without logging out removes the machine from the
domain before the installation process. This procedure is commonly done with
laptops when the suspend or hibernate facility is used when removing the
laptop from the office environment. The end result is that the user cannot be
authenticated as all the details are located on the domain which is not reachable
during the installation process. If this error is encountered ensure that the
current user session can be authenticated before attempting the installation
again. The usual method is to log off the current session and start a new session
to ensure the system can find the user details.
22.9 Database scripts

Located in the [Foxboro Directory]\System Configurator\Docs\PostgreSQL
directory, are two scripts for updating the database used by the System
Configurator. These scripts are named: update_all.cmd and recreate_all.cmd.
Use these scripts with EXTREME CAUTION, and only under the direction of
Foxboro support staff.
The recreate_all.cmd script DELETES all configuration data that has been
configured on the machine. This data cannot be retrieved (other than by
importing individual remote devices’ configuration files into the System
Configurator).
The update_syscfg.cmd script is used to upgrade the database and is
automatically executed as part of an upgrade of the System Configurator
software. This script does not alter existing configuration data.

2005663 - Rev. 1.3
23. Appendices
Appendix A Definitions and Abbreviations

The following terms and acronyms are defined here within the context of this
document.
TERM DEFINITION
ADI Analog/Digital Inputs module

AI Analog Input
AO Analog Output
CDROM Compact Disk Read Only Memory
CFG Configuration
COM2 Communications port 2 on the main
processor board
Comms Communications
CPU Central Processing Unit
Cygwin A port of UNIX commands to the Windows
environment
DCB Dual Communications Board
DI Digital Input
DNP3 Distributed Network Protocol
DO Digital Output
HLSI High Level Serial Interface
I/A SCADA remote devices The RTU50 and SCD5200.
IDF Intrinsic Database Functions
IED Intelligent Electronic Device
I/O Input/Output
ISaGRAF IEC 61131-3 compliant application
providing a programming and runtime
environment.
JRE Java Runtime Environment
JVM Java Virtual Machine
MB Megabyte
Mhz Megahertz

2005663 - Rev. 1.3
TERM DEFINITION
PostgreSQL A UNIX database program.

RAM Random Access Memory
RTU Remote Terminal Unit
RTU50 Foxboro Australia’s Remote Terminal Unit
Product, formerly known as the C50.
RTUCFG The previous RTU Configurator
SALL State And Logic Language
SCD Station Computing Device
SCD5200 Foxboro Australia’s Station Computing
Device product.
TCP/IP Transmission Control Protocol/Internet
Protocol
TDO Twelve Digital Output module

2005663 - Rev. 1.3
Appendix B Referenced Documents
[1] DNP3 Slave User Manual for the RTU50, RTU10 and SCD5200
Foxboro Australia
Document No. 2005554
[2] DNP3 Master User Manual for the RTU50 and SCD5200
Foxboro Australia
[3] TCP/IP User Manual for the RTU50, SCD5200 and CLS
Foxboro Australia
[4] Intrinsic Database Functions User Manual for the SCD5200, RTU50 and
RTU10
Foxboro Australia
[5] RTU Programming User Manual – State and Logic Language Reference
(SALL) for the RTU50 and RTU10
Foxboro Australia
[6] IEC 61131-3 Programming and Runtime Environment User Manual for the
RTU50 and SCD5200
Foxboro Australia
[7] OptoNet Software User Manual for the RTU50 and SCD5200
Foxboro Australia
[8] SALL High Level Serial Interface User Manual for the RTU50, RTU10,
SCD5200 and CLS
Foxboro Australia
[9] C50 Configuration User Manual

Foxboro Australia

System Configurator User Manual

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

System Configurator User Manual

Uploaded by

Copyright:

Available Formats

`

for the: RTU50

Document ID: 2005663

Document Revision History:

Rev. Date Comments Prepared By

I/A Series Intelligent SCADA System Page 3 of 70

1.3 Definitions and Abbreviations.....................................................................................10

1.4 Referenced Documents ................................................................................................10

2. Installation of System Configurator ................................................................... 11

2.1 System Requirements...................................................................................................11

2.2 Installing System Configurator ....................................................................................12

3. Getting Started with System Configurator......................................................... 13

3.1 Starting up....................................................................................................................13

3.2 Menus and dialog boxes ..............................................................................................14

3.3 Navigating the configuration tree ................................................................................14

3.4 Managing configuration items .....................................................................................15

3.5 Getting help..................................................................................................................18

4. The Configuration Tree........................................................................................ 20

4.1 RTU Configuration node .............................................................................................20

4.2 Sites node.....................................................................................................................20

4.3 Equipment node ...........................................................................................................21

4.4 Calc Sources node........................................................................................................22

6. Configuring Sites ................................................................................................. 24

I/A Series Intelligent SCADA System Page 4 of 70

7. Configuring OptoNet Networks .......................................................................... 25

8. Configuring I/A SCADA Remote Devices ........................................................... 27

8.1 Creating the Remote Device ........................................................................................27

8.2 Creating a card file.......................................................................................................27

8.3 Configuring slots..........................................................................................................28

8.4 Moving cards and ports................................................................................................31

9. Importing Existing Configurations ..................................................................... 32

9.1 Importing a configuration ............................................................................................32

9.2 Notes on Configuration Import....................................................................................32

10. Configuring Electrobus ....................................................................................... 33

11. Configuring Optobus Master .............................................................................. 36

12. Configuring I/O modules ..................................................................................... 39

13. Configuring DCBs (Dual Communications Boards) .......................................... 40

13.1 Configure the board .....................................................................................................40

13.2 Configure the port........................................................................................................40

13.3 Configure the protocol .................................................................................................41

14. Configuring OptoNet modules ............................................................................ 43

15. Configuring serial ports ...................................................................................... 44

15.1 Configure the serial card..............................................................................................44

15.2 Configure the serial port ..............................................................................................45

15.3 Configure the protocol .................................................................................................45

16. Configuring Ethernet ........................................................................................... 46

17. Configuring Protocols ......................................................................................... 48

17.1 Configuring master protocols ......................................................................................48

I/A Series Intelligent SCADA System Page 5 of 70

17.3 Configuring slave protocols for IEDs ..........................................................................51

17.4 Configuring SALL HLSI .............................................................................................51

18. Configuring calculations ..................................................................................... 53

18.1 IDF – Intrinsic Database Functions .............................................................................53

18.2 SALL – State And Logic Language.............................................................................54

19. Predefined points................................................................................................. 57

20. Generating and Browsing Configuration Files .................................................. 59

20.1 Generating configuration files .....................................................................................59

20.2 Browsing configuration files .......................................................................................60

21. Database Maintenance Utilities........................................................................... 61

21.1 Backup the configuration database ..............................................................................61

21.2 Restore the configuration database..............................................................................61

21.3 Compressing the configuration database .....................................................................62

22.1 The required services are not running. ........................................................................63

22.3 Check permissions on PostgreSQL files......................................................................65