SC V500 Operation Rev 500

Document Number: 74000-SCO
STATION CONTROLLER OPERATION

User’s Manual
____________________________________________
September 22, 2009
This manual describes the operation of the Station controllers (Scout and Hunter).
Revision/Update Information
Revision 1.00 Initial release for software 74000-01 version 4.02

Revision 2.00 February 26, 2008. For software 74000-01 rev 4.03
Added option for Fault Detection with Loss of Voltage on Hunter
Added information for Unit Issue 2 of Hunter (Voltage dc analog Inputs)
Revision 2.01 Document update
Revision 3.00 May 16, 2008. For software 74000-01 rev 4.04 and up
Added time delay for fault indicators
Added Min Hold time for fault indicators
Revision 3.01 November 01, 2008. For software 74000-01 rev. 4.04.03 and up.
Added Simple Time Network Protocol
Added pseudo-controls for clearing and erasing waveform events
Revision 4.00 April 16, 2009. For software 74000-01 rev. 4.05.02 and up.
Added Fast Meter Messages Protocol for SEL devices
Revision 5.00 September 21, 2010. For software 74000-01 rev. 5.00.00 and up.
Added IEC 61850 Master configuration
Survalent Technology Corporation

Mississauga, Ontario
Copyright (c) 2007-2009 Survalent Technology Corporation
Station Controller Operation User’s Manual
All rights reserved
Survalent Technology Corporation

2600 Argentia Road
Mississauga, Ontario
Canada
L5N 5V4
TEL (905) 826 5000
FAX (905) 826 7144
www.survalent.com
The software described in this document is furnished under license, and may only
be used or copied in accordance with the terms of such license.
Information furnished by Survalent Technology Corporation has been checked carefully

and is believed to be accurate and reliable. However, Survalent Technology Corporation
does not assume any responsibility for inaccuracies. Survalent Technology Corporation
reserves the right to make changes without notice to improve reliability, function or
design.
Table of Contents
Table of Contents..........................................................................................i
1. Station Controller Operation ....................................................................1

1.1 System Overview.............................................................................................1
1.2 System Options................................................................................................3
1.3 Main Hardware Sub-system Operation...........................................................4
1.3.1 Main Processor Module.................................................................................4
1.3.2 Control, Analog, Status and Communication Board........................................5
1.4 Status Hardware Sub-system Operation........................................................7
1.4.1 Hardware Operation......................................................................................7
1.4.2 Normal Status...............................................................................................9
1.4.3 SOE Software Operation ...........................................................................10
1.4.4 SOE Configuration......................................................................................12
1.4.5 Status Accumulator Inputs...........................................................................12
1.4.6 Status Accumulator Configuration................................................................13
1.5 Analog Hardware Sub-system Operation.....................................................16
1.5.1 Scout Analog Hardware Sub-system Operation............................................16
1.5.2 Hunter Analog Hardware Sub-system Operation..........................................22
1.6 Control Hardware Sub-System Operation....................................................28
1.6.1 Scout Control Operation..............................................................................28
1.6.2 Hunter Control Operation.............................................................................30
1.6.3 Control Configuration...................................................................................31
1.7 Setpoint Operation.........................................................................................33
1.7.1 Hardware Operation....................................................................................33
1.7.2 Setpoint Software Operation........................................................................33
1.8 ADAM4021 Analog Output Operation ..........................................................33
1.8.1 Hardware Operation....................................................................................33
1.8.2 Rescale of ADAM Values ............................................................................35
1.8.3 ADAM4021 Configuration............................................................................36
1.9 Master Communication..................................................................................36
1.9.1 Overview.....................................................................................................36
1.9.2 Supported Protocols....................................................................................37
1.9.3 Master Communication Configuration..........................................................37
1.9.4 QUICS IV/ QUIN - Master Communication Configuration............................37
1.9.5 DNP 3.0 - Master Communication Configuration ........................................39
1.9.6 IEC 870-5-101 - Master Communication Configuration ..............................41
i
1.9.7 TeleGyr 8979 - Master Communication Configuration ................................44
1.9.8 IEC 870-5-104 - Master Communication Configuration ..............................44
1.9.9 Modbus - Master Communication Configuration ........................................46
1.9.10 IEC 61850 - Master Communication Configuration ....................................47
1.9.11 Master Points Mapping (applies to all protocols)..........................................48
1.10 IED Communication.....................................................................................49
1.10.1 Overview...................................................................................................49
1.10.2 Mapping File Generation............................................................................49
1.10.3 SOE Time Tag...........................................................................................50
1.10.4 Supported IED Protocols...........................................................................51
1.10.5 IED with DNP 3.0.....................................................................................51
1.10.6 IED with MODBUS..................................................................................54
1.10.7 IED with Cooper 2179..............................................................................54
1.10.8 IED with IEC 870-5-101 Protocol..............................................................55
1.10.9 IED with IEC 870-5-103 Protocol..............................................................55
1.10.10 IED with SPA BUS Protocol.....................................................................55
1.10.11 IED with SEL-Fast Meter Messages Protocol............................................56
1.10.12 IED with IEC 61850 Protocol....................................................................56
1.11 Network Communication Operation............................................................56
1.11.1 Network Configuration...............................................................................57
1.11.2 Com Port Configuration..............................................................................58
1.11.3 Server Only Parameters.............................................................................58
1.11.4 Client Only Parameters..............................................................................59
1.12 Terminal Server Configuration Editor.........................................................60
1.13 Web Server...................................................................................................60
1.14 Programmable Logic Controller..................................................................61
1.15 Station Controller Time Sub-System..........................................................61
1.15.1 Time Operation..........................................................................................61
1.15.2 Time Configuration....................................................................................61
1.15.3 IRIG-B......................................................................................................62
1.15.4 Default Date Editor....................................................................................62
1.15.5 IRIG B Configuration Editor........................................................................62
1.15.6 SNTP – Simple Network Time Protocol......................................................62
1.16 Load Profile Configuration..........................................................................63
1.16.1 Load Profile Configuration Editor................................................................64
1.17 System Errors...............................................................................................64
1.17.1 General.....................................................................................................64
1.17.2 Specific System Errors "Momentary Errors"................................................64
1.17.3 Specific System Errors "Continuous Errors"................................................65
1.18 Maintenance Port Operation........................................................................65
2. Start up Configuration...............................................................................1
2.1 Download Maps................................................................................................1
2.1.1 Hardware Mapping........................................................................................1
2.1.2 IED Mapping.................................................................................................1
ii
2.2 cf command......................................................................................................1
2.2.1 System Options Editor...................................................................................1
2.2.2 Masters Editor...............................................................................................2
2.2.3 Com Port Configuration Editor.......................................................................2
2.2.4 Network Configuration Editor.........................................................................2
3. Station Controller Program Updating........................................................1

3.1 Using Ethernet (tftp).........................................................................................1
3.1.1 Preparation...................................................................................................1
3.1.2 On PC..........................................................................................................1
3.1.3 On Station Controller.....................................................................................1
3.2 Using Xmodem.................................................................................................2
4. Station Controller Database Configuration...............................................1

4.1 Scout Database ...............................................................................................1
4.1.1 Status Points Definition..................................................................................1
4.1.2 Analog Points Definition.................................................................................4
4.1.3 Counter Points Definition...............................................................................5
4.1.4 Control Points Definition ...............................................................................7
4.1.5 Set Points Definition .....................................................................................7
4.2 Hunter Database new.......................................................................................8
4.2.1 6 Voltage and 6 Current configuration............................................................8
4.2.2 3 Voltage and 9 Current configuration..........................................................16
4.2.3 Hunter Scaling Values.................................................................................26
5. APPENDICES............................................................................................1
5.1 Appendix A: MPM LED and Jumper Designations.........................................1
5.2 Appendix B: CASCO LED and Jumper Designations....................................3
5.3 Appendix C: Hunter LED and Jumper Designations......................................5
5.4 Appendix D: MPM Jumper Settings................................................................7
5.5 Appendix E: CASCO Jumper Settings............................................................8
5.6 Appendix F: HUNTER Jumper Settings........................................................10
5.7 Appendix G: Communication Cable Connections.......................................13
5.7.1 RS232 Connections....................................................................................13
5.7.2 RS485 Connections....................................................................................14
iii
1. Station Controller Operation
This manual describes the operation of both the Scout and the Hunter Controllers. Most of the operations
are the same for both, but where there are differences the operation is described separately for each. The
Scout is a scalable Station Controller where the Hunter is a fixed point count Controller. The Hunter has
direct ac analog inputs (transducerless) and provides power quality features.
The Station Controller is comprised of the 51464 MPM board and the 51459 CASCO board. Input and
output boards can be added as required. The MPM contain processor, memory, serial and Ethernet ports.
The Station Controller application program resides here and is the same for both Hunter and Scout. The
CASCO board provides interfaces for inputs and outputs for analog, status and controls as well as
additional serial ports.
The Hunter Controller is comprised of 51462 MPM board and 51481 Hunter board. The MPM contain
processor, memory, serial and Ethernet ports. The application program resides here and is the same for
both Hunter and Scout Station Controller. The Hunter board provides inputs and outputs for analog, status
and controls as well as additional serial ports.
The Station Explorer II is a support application program for both Controllers
1.1 System Overview

The Station Controller provides full data gathering and device control via status and analog input points,
control output relays, and external Intelligent End Devices (IED).
The Station Controller can be broken down into the following subsystems.
Database: The database is the heart of the system. All the system tasks transfer data with each other via
the database. The database contains status, analog, accumulator (or counter), Sequence Of Events (SOE),
control and setpoint information. These points may be from Controller hardware points, Controller’s
internal status, references, PLC points etc, or from IED points. No point in the database is accessible from
a master station until it is mapped, and not all points in the database are interesting to any particular
master station. The selective accessibility of the database points to a master is made possible through
point maps. One mapping file is required for each master to map to the master the Station Controller’s
hardware points, internal status, references and/or PLC points; and one mapping file for each master is
needed for each communication port to map IED points to the master. Up to 4 independent master
stations are supported by the Station Controller. IED points are directly mapped to the master station’s
database points to simplify the mapping process. The storing locations of these IED points in the database
are dynamically determined by the Controller, based upon the maps downloaded. These point maps are
downloaded through either the master’s IED wizard or Station Explorer (refer to the corresponding user’s
manuals for more details).
1
A point of any type in the database may be referenced by up to five different methods. It can be
referenced through the database point number, or may be referenced through a point number in any
master database (up to four master database are possible) if it is mapped to the master.
File System: The file system provides storage for large blocks of data that are used to configure and
control the operation of the system. The file system may contain files that configure the basic system and
the serial port parameters. Other files are used to define the operation of the IED system that includes the
transfer of blocks of data to and from the IED.
Status Hardware: The hardware status input subsystem monitors the input hardware for status changes
and then updates the database with these changes. Status points can also be configured to act as SOE or
accumulator points.
Analog Hardware: The hardware analog input subsystem monitors the input hardware for changes in
the analog points and then updates the database with these changes. The analog input subsystem also has
reference values that can be monitored to determine the stability of the analog to digital converter.
Control Output: The control output subsystem provides hardware relay output points for system
control. A select, checkback, operate scheme are used to prevent illegal control operation from occurring.
IED Communication: The IED communication subsystem gathers data from the connected IEDs,
processes the data and writes the results into the database. It also takes the control and setpoint
commands, interprets them, and then sends out the resultant control to the desired IED. The IED
communications is determined by the IED mapping file.
Master Communications: The master communication subsystem is the main communication link to
the master computer. Multiple master stations with separate event data reporting are supported. The data
base point assignment per master connection is determined by the mapping files received for that master
from either the master’s IED Wizard or from the Station Explorer.
Network Communication: Two Ethernet connections are available on the Station Controller. They
both support a suite of TCP/IP functions/protocols and can be used as communication media to masters
and IEDs.
Maintenance and Configuration tools: The maintenance tools can monitor and control the
operation of the Station Controller through various system functions. The configuration tools can change
parameters in the Station Controller. Three tools are available and perform slightly different functions as
indicated in the table below. Throughout this document only references are made to the console
commands. In most cases similar functions can be performed using the web server and the Station
Explorer II.
Console
The console is using port 0 to access the commands available in the Station Controller. The same
commands can also be accessed using the Telnet protocol on either of the two Ethernet ports. A terminal
emulator (e.g. Hyperterm) is used on the pc and connected via serial or network communication. Refer to
document 74000-SCC for details of the console.
Web Server
2
The web server is accessed via either of the two Ethernet ports. A web browser (e.g. Internet Explorer) is
used on the pc and connected via network communication. Refer to document 74000-SCW for details of
the web server functions.
Station Explorer II
The Station Explorer II is a pc application program for a pc and can connect to the Station Controller via
serial communication to port 1 or network communication to either of the two Ethernet ports. Refer to
document 74100-SEC for detail of the Station Explorer II functions.
NETWORK COMMUNICATION
VIEW OPERATIONAL DATA
SERIAL COMMUNICATION
POWER QUALITY DATA
PROGRAM UPGRADE
CONFIGURATION
MAP DATA
SCANMON
TELNET
CONSOLE √ √ √ √ √ √ √
WEB SERVER √ √ √ √
STATION
√ (√) √ √ (√) √ (√) √ √
EXPLORER II
Table 1.1-1 (√) = Available via Telnet Console only
1.2 System Options

The Station Controller software is configured for the purchased options through the password
configuration editor. This manual describes the operation of all the possible options. Your particular
Station Controller may not support all the options described.
The different options available are as follows:
• Sequence of Events
• KYZ Accumulators
• Cooper 2179 to IED
• Modbus to IED
• QUICS IV to IED
3
• ADAM4000 Protocol
• DNP 3.0 to IED
• IEC 870-5-103 to IED
• SPA-BUS to IED
• IEC 870-5-101 to IED
• Fast Meter Messages (SEL) to IED
• Multiple Master
• DNP 3.0 to Master
• IEC 870-5-101 to Master
• IEC 870-5-104 to Master
• GYR to Master
• Modbus to Master
• Fast Ethernet
• Second Ethernet
• Terminal Server
• Web Server
• Irig B Input
• PLC
• Load Profile
Only the password given to the customer by Survalent Technology Corporation will cause the Station
Controller to operate correctly. Use of other passwords may cause to system not to operate correctly. If a
new option is required, contact Survalent for a new password.
In the event that the non-volatile memory in which the password is stored is erased, the software reverts
to the default password of: DN6E-NG2B-IKT6-K232-OELG-PKQW. This password allows the basic
status, analog, accumulator and control operations to work with QUIN/QUICS4 master protocols, but the
above options will not be available. To restore you password, simply enter it the System Options Editor.
Maintenance Terminal Tip:

To check which options are enabled, use the process report command (pr) on the console or the Process
Report page on the web server. To enter/view the password, use the System Options Editor in the menu
command (cf option 5) or on the web server
1.3 Main Hardware Sub-system Operation

The main hardware subsystem consists of the Main Processor Module (MPM) 51462 and the Hunter
input/output boards 51481 or the 51459 CASCO board for the Scout.
1.3.1 Main Processor Module

The Main Processor Module contains the microprocessor, memory and RS232 serial and Ethernet ports. It
sits on the Input/Output board (Hunter or CASCO) as a daughter board and connects to it by 2 connectors.
The processor is a Freescale MPC860T, which has an integrated serial communication controllers (SCC)
and a Fast Ethernet controller. Two SCCs are used for serial RS232 communication (ports 2 and 3), one is
used for 10 BaseT Ethernet controller and the last is reserved for future RS485 communication between
4
distributed modules (Port 4). Two simple UARTS are used for console and configuration communication
(Ports 0 and 1).
The memory consists of FLASH non-volatile for program and custom web page storage, static RAM for
data storage, NV RAM for system log and for other bigger files that require retention during power down
and EEPROM for smaller configuration parameter storage.
Time of Day clock is available in Unit Issue 5 and up.
LEDs indicate the activities on ports 1 to 4 as well as the two Ethernet ports. Four LEDs are designated to
diagnostic including the RUN indication. Three LED marked Diagnostic #1, Diagnostic #2 and
Diagnostic #3 can be assigned functions as set in LED Editor under Station Controller System
Configuration Menu. Diagnostic LED #1 is used as default to indicate control action, flashing during
control select and on solid during control execute. The LEDs can be on the MPM directly or on a separate
board depending on packaging option. For designation of LEDs on the MPM see Appendix A
The MPM has the jumper settings outlined in Appendix C
1.3.2 Control, Analog, Status and Communication Board

Scout
The CASCO board provides interface to modular input and output boards. These boards are connected via
3 bus cables and can be added in modules of 16 points per board to a maximum of 256 of each type. As
well it has 8 communication ports (Ports 8 to 15) for RS232 or 485 connections
Hunter
The Hunter board provides direct I/O for 32 status inputs, 16 analog inputs (12 ac inputs and 4 dc inputs)
and 8 control outputs. As well it has 4 communication ports (Ports 8 to 11) for RS232 or 485 connections.
1.3.2.1 Control Interface

Scout
The control interface on the Scout provides 16 relay drivers and 16 panel drivers and 1 execute switch to
activate 1 of 256 final interposing relays. Checkback information is retrieved from these 32 drivers. A
current sensing circuit monitors the current supplied to the interposing relays and will deactivate the
control if current draw is higher than what is expected for one relay.
Hunter
The control interface provides 8 select relays and 1 execute relay to activate 1 of 8 final interposing
relays. Checkback information is retrieved from these select relays. An “execute lock” is provided in
hardware which requires the software to write 4 consecutive and specific data bytes to unlock and activate
the execute relay. The control outputs can be expanded with an additional 8 relays by installing the
DOMEXP 51435 on J15 expansion connector. These 16 control outputs can also be used with multiplex
output boards to provide up to 64 outputs. The type of control to be used is determined by hardware
installed and on what database point range used.
5
1.3.2.2 Analog Interface
Scout
The analog interface provides two banks of connections to the analog input boards. Each bank has select
lines to select 1 of 128 inputs. The analog signal from the selected point is converted to digital format and
presented to the processor. Precision reference signal on the CASCO board are also converted and used as
-90 and +90 of full scale values.
Hunter
The analog interface provides 3 different input types. Four inputs are available for dc mA (=/- 1 mA or 0
to 20 mA), 3 or 6 direct ac voltage inputs (120 Vac nominal) and 6 or 9 direct ac current inputs (5 Aac
nominal). The sampled and converted data from these inputs is used in calculations by the DSP to give
rms values for voltage, current, power, energy and power quality values. Precision reference signals are
also converted and used as 0 %, 10 % and +90 % of full scale values.
1.3.2.3 Status Interface

Scout
The status interface provides select lines to select 16 groups of 16 status inputs. Each group can be
configured for internal or external wetting. The data of the selected group is presented to the processor.
Hunter
The status interface provides 32 status inputs in two groups of 16. Each group can be configured for
internal or external contact wetting. The data is sampled and processed by the DSP on the Hunter board
before being passed on the processor.
1.3.2.4 Communication Interface

The communication interface provides a number of asynchronous communication ports. The CASCO
board has 8 ports and the Hunter board has 4 ports.
Each port can be individually configured as RS232 or 485 by jumper settings (see appendices E and F) or
via any of the 3 configuration tools. The Baud rate and RTS and CTS control lines can also be configured
via any of the 3 configuration tools.
Two LEDs are provided per port for Tx, and Rx activity. Refer to Appendices B and C for designation of
LEDs.
The CASCO and Hunter board have jumper settings as outlined in Appendices E and F.
6
1.4 Status Hardware Sub-system Operation
1.4.1 Hardware Operation.

The Scout and Hunter have different input circuits and scanning which are described separately below.
1.4.1.1 Scout Hardware Operation

The field status points are connected to either the 56719 or the 51484 status input boards. Both of these
boards contain a noise filter to filter out transient noise. Optical isolation is also provided to protect the
Station Controller hardware from damaging field transient and faults.
The status input boards are linked together via a daisy-chained ribbon cable bus. This bus contains 5
address lines, 16 data lines, and other miscellaneous control lines. The bus uses 12 Vdc logic levels.
Each board (and therefore range of points) has its own unique address. The boards are position
independent on the bus, so care has to be taken to ensure that each status input board is strapped correctly
for the required address.
The LED on the status input board indicates that the status cards are being scanned. The LED remains on
for approximately 30 ms after the board is accessed. Therefore the LED may remain solidly on or flicker
on and off depending on the status scan rate.
The power connector on the status input board supplies power for the status wetting current. This current
is used to sense a contact closure, which then turns on the opto-coupler.
The inputs can accept external wetting of use the voltage supplied on the power connector depending on
jumper settings. Refer to the appropriate input board’s Jumper hand header information.
The status interface circuits on the 51459 Control, Analog, Status and Communication (CASCO) Board
provides an interface between the 51462 Main Processor Module (MPM) and the status input cards.
It is very important that the address strapping be done correctly for proper operation. For the 56719 status
board address 0 is not used on any boards. If strapped to address 0 the Scout will assume that a combo
board is connected and enable only a few status and analog points. Refer to the table 1-1below.
The newer 51484 board must start at address 0. The two types of boards can not be mixed on the same
bus.
7
Status W1 Jumper Position
Panel A16 A8 A4 A2 A1
Address
0 WARNING: Do not strap for address No boards selected.
0. Combo board will be detected and
only limited points will be available.
1 0 0 0 0 1 Status Points 1 to 16
8 0 1 0 0 0 Status Points 113 to 128
9 0 1 0 0 1 Status Points 129 to 144
10 0 1 0 1 0 Status Points 145 to 160
11 0 1 0 1 1 Status Points 161 to 176
12 0 1 1 0 0 Status Points 177 to 192
13 0 1 1 0 1 Status Points 193 to 208
14 0 1 1 1 0 Status Points 209 to 224
15 0 1 1 1 1 Status Points 225 to 240
16 1 0 0 0 0 Status Points 241 to 256
17 to 31 Not used
Table 1.4.1.1-1: Status Board Strap Address and Point Range for 56719 boards
Table 1.4.1.1-2: Status Board Strap Address and Point Range for 51484 boards.
Status W1 Jumper Position

Panel A8 A4 A2 A1
Address
0 0 0 0 0 Status Points 1 to 16
16 to 31 For future use
8
1.4.1.2 Scout Status Software Operation
The scan software accesses each board in the following manner:
Put the address of the next board to be scanned on the bus.

Verify the “board installed” bit is returned.
If not: set the pseudo status bit indicating that the board is failed. Increment the board error
counter.
If so: read in the board data and processes the data.
Deselect the board.
Wait until the board is deselected.
Repeat the above steps until all the boards have been scanned.
On power-up, the number of status boards is determined by scanning from the last possible board in the
system to the first board until a board responds. The board that responds is considered to be the last
equipped board. Thereafter the scanning software only processes the equipped boards. No processing is
performed if no boards were found.
The scan rate for all equipped input points is 1 millisecond. Three subsystems use this information to
process data for their own function. These are regular status, SOE and accumulator.
1.4.1.3 Hunter Hardware Operation

The field status points are connected directly to the Hunter board on the J13 removable terminal block.
These inputs contain noise filters to filter out transient noise. Optical isolation is also provided to protect
the Station Controller hardware from damaging field transient and faults. LEDs are provided for each
status input and are ON when the field contacts are closed. The internal contact wetting is 24 Vdc and a
closed contact will draw ~ 5 mA. The wetting voltage can be selected to be internal or external by jumper
on W1 and 2.
1.4.1.4 Hunter Status Software Operation

The DSP on the Hunter board scans all 32 inputs every 1 msec. The DSP further processes the samples
for change detection, de-bouncing and time stamping. It also make a copy of the current state of all 32
points available to the main processor for processing of normal status.
1.4.2 Normal Status

The following applies to both the Scout and the Hunter.
The normal status input points sample the fast scanned 1 millisecond input data every 10 millisecond,
typically. The debouncing is using the double scan method. For a status point to be detected as a valid
change of state, the status must remain in the same state for 2 successive samples.
Status points are placed in the database starting from point 0 in the database and up to the last detected
board for the Scout or to point 31 for the Hunter. These points must be mapped to one or more master
9
station ports in order to be reported. The default is no points are mapped to any master. See section on
mapping for further details.
Changes of state are latched in the Controller until reported to the master. The number of changes held in
the Controller varies depending on the selected protocol. This can range from one change per point
(QUICS4) to several hundreds per Controller (DNP).

To check the current state of the status input, use the status read command (sr).
1.4.3 SOE Software Operation

The Sequence Of Events (SOE) option monitors status points for change of states. Each change of state is
time tagged and stored in a SOE event buffer. The input to the SOE is the fast scan (1 ms) of the hardware
as well as status points brought in from IEDs. The details of the operation are described by the following
features:
• SOE Point Reference
The point that the Station Controller scans as a SOE point can be referenced through either the master
station database point if it is mapped or directly to Station Controller database point. Up to four
master stations with independent database each can be referenced. If referenced from a master
database point, the point will be treated as a SOE point by that master. It may not be treated as a SOE
point by any other masters although it could be same Station Controller database point, unless the
point also is configured as a SOE point for those other masters. However, if referenced from Station
Controller database point, the point will be treated as a SOE point by all masters which are activated
and have the Station Controller point in their maps.
• Multiple SOE Point Ranges
The Station Controller supports multiple ranges of SOE points, no matter what database the points
may be referenced to. Each SOE point range starts from "First Status Point to be used for SOEs" and
have "total number of SOE Points" in the range. The First Status Point to be used for SOE, can be
any valid status point. The total number of SOE Points is the number of status points that will be
treated as SOEs. If this is set to 0, no SOE points are defined in the range. The SOE points may
include both hardware and IED status points.
• SOE Time Tag and Debounce
o Hardware Status Points
The frequency at which the SOE points are scanned is fixed at 1 msec. SOE points are
debounced over a selectable period in the Scout and over a fixed period of 3 msec in the
Hunter. When a change of state of SOE point is detected, the change of state is time tagged
and stored. However, if the Station Controller time is not valid (i.e. it is not synchronized by
command from master station or maintenance port or internal Real Time Clock), the change
of state will not be time-tagged.
10
o IED Status Points
For information about IED SOE status point time tags, please refer to “IED Communication”
section of this Manual.
One Event Reported:
No Event Reported:
Debounce Time
• Initial Status
The very first reading of status points after a restart will be used as the initial status, and will not be
reported as events even if they may be 1.
• Normal Status Point vs SOE Point
When a point is configured as a SOE point, normal status operation on the points continues
undisturbed. (i.e. SOE and normal status operation continue in parallel.)
• Reporting of SOE Data to Master
The reporting of SOE data to the master varies depending of protocol selected.
o For QUICS/QUIN the following applies:
When an SOE point is placed in the internal Station Controller buffers, the flag “Data in SOE
Queue” is set in the protocol. When this bit is set, the master initiates an SOE event upload
sequence. When all current SOE data has been sent to the master and acknowledged, the flag
is cleared. If the SOE data queue is filled, oldest SOE events are discarded to make room for
the newest SOE events. The SOE buffer can store over 1000 events before any events are
lost.
o For DNP the following applies:
SOE data is transmitted to the master on Class polls (typically Class 1) as event data with
timestamp. The buffer will hold up to 500 events of all types between polls.
SOE data can also be examined with the maintenance port command, se. Past events can be
examined and current events can be monitored. The last 1000 events are kept in the Station
Controller for examination until the Controller is restarted.
Before SOEs can time stamp changes with a valid time, the Station Controller 's clock must be set by the
master, the console or by the Real Time Clock (RTC). The Controller will normally have it time set by
11
the internal RTC after each restart and will be ready to time stamp events. However, if the RTC is not
available, then the Default data and time will be used and the Controller must be synchronized before
time stamps will be applied to events.
1.4.4 SOE Configuration

SOE configuration configures the method to be used for referencing SOE points, SOE point ranges, SOE
points in a range and the de-bounce time for each range. It can be done by using any of the 3
configuration methods described in the beginning of this manual
When adding a SOE point range, the following items must be configured in the SOE configuration editor:
Master Map for SOE Range: This will select which database map to reference. 1 to 4 will select master
1 to 4, and 0 will select direct access to the Station Controller database.
First Status Point of SOE range: This is the first valid status point that will be processed as a SOE
point in the range. The points reserved are sequential, starting at this point number.
Total number of SOE Points in range: This determines the quantity of status points that will be
treated as SOE points in the range. If no SOE points are required, set the quantity to zero.
Default SOE Debounce Time (ms units): The minimum length of time a transition must be stable
before it will be counted as an event. It applies to this range only. This parameter is only active on the
Scout. On the Hunter the debounce time used is always 3 msec regardless of this parameter
Example:
Master Map for SOE Range : 1

First Status Point of SOE range: 25
Total number of SOE Points in range: 6
Default SOE Debounce Time (ms units): 15 (always 3 msec on the Hunter)
With the above settings, transitions on status points 25 through to 30 of master 1 will be processed as
SOE points. Status point 31 will not be processed a SOE point. State transitions of less than 15
milliseconds will not be logged.

To check the current state of the status input, use the status read command (sr or srmp). To monitor SOE
events or to view past SOE events, use the SOE command (se). To edit the SOE configuration, use the
menu command (cf) and select the soe configuration editor.
1.4.5 Status Accumulator Inputs

The status accumulator (or pulse counter) option counts the number of transitions on selected status points
using the status input hardware. The details of the operation are as follows.
An off (open or 0) to on (closed or 1) transition causes the associated accumulator point to increment by
1. When a point is configured as an accumulator point, status transitions are not transmitted to the master.
However, the current state of the status point can be monitored via the test terminal's sr command. The
12
accumulator debounces the data in the same manner that the SOE system debounces the data. The
debounce time must be selected to be longer that the longest expected contact bounce, but shorter that the
shortest pulse. If the contact bounce is not more than 10 msec and the fasted pulse rate is 10 pulses per
second (or 100 msec per period and 50 msec per half period if symmetrical), select a debounce time
between 20 and 40 msec.
If "First Status Point to be used for Accumulators" is set to 10, "Total number of Accumulator Points" is
set to 5 and "First Accumulator Point Number to use" is set to 112, an off-on change on status point 14
will cause accumulator point 116 to increment by 1.
The method of collecting Accumulator/Counter data by the master depends largely on the protocol used.
In general, the following requests can be handled by the Station Controller, if supported by the selected
protocol.
Read Running Counter: Station Controller responds with present counter value.
Read Frozen Counter: Station Controller responds with frozen counter value.
Freeze Counter: Station Controller will copy present counter value to frozen counter
value.
Freeze and Reset Counter: Station Controller will copy present counter value to frozen counter
value and reset present counter value to zero.
When the master transmits a Counter Freeze command to the Station Controller, the present counter value
is copied to an internal frozen counter buffer. The present counter value continues to count upward and
rolls over to zero when the full count is reached. When the master sends out a frozen counter read
command, only the frozen values are transmitted to the master. The master then calculates the delta
between the new data and the last transmitted data to determine how many counts have occurred in the
last interval. The present counter value can be monitored via the maintenance terminal's cr command.
When the master transmits a Counter Freeze and Reset command to the Station Controller, the present
counter value is copied to an internal frozen counter buffer. The present counter value is reset to zero and
will then start to count upward again until the next Freeze and Reset. When the master sends out a frozen
counter read command, only the frozen values are transmitted to the master. The master now gets directly
how many counts have occurred in the last interval. The present counter value can be monitored via the
maintenance terminal's cr command.
1.4.6 Status Accumulator Configuration

The configuration of Accumulator point is a two step process where accumulator points first are
configured from status points and secondly, the configured accumulator points are map to one or more
masters.
The following items must be configured in the Station Controller configuration editor. It can be done by
using any of the 3 configuration methods described in the beginning of this manual.
13
Default Accumulator Upset Threshold: This parameter is currently only used for the IEC 60870-5-
101 protocol communication to a master. It defines the number of counts an accumulator value must
change before it is transmitted as an event.
Enable Accumulator Events: This parameter is currently only used for the IEC 60870-5-101 protocol
communication to a master and should only be enabled for this protocol. It will enable event reporting to
a master as described above.
First Status Point to be used for H/W Accumulators: This is the first valid hardware status point
that will be processed as an accumulator point. The points reserved are sequential, starting at this point.
Total number of H/W Accumulator Points: This determines the quantity of status points that will
be treated as accumulator points. If no accumulator points are required set the quantity to zero.
First H/W Accumulator Point Number to use: The accumulator point number that is associated
with the first status point marked as an accumulator.
Offset Accumulators for QUICS4 (recommended 0 or 112): This parameter can be disregarded
on all protocols including QUICS4. The selection of Accumulator points are performed in the mapping
process.
H/W Accumulator Debounce Time (ms units): The minimum length of time a transition must be
stable before it will be counted as a transition.
Example:
First Status Point to be used for H/W Accumulators: 21

Total number of H/W Accumulator Points: 3
First H/W Accumulator Point Number to use: 112
H/W Accumulator Debounce Time (ms units): 30
With the above settings, transitions on status points 21, 22 and 23 will be counted in accumulator points
112, 113 and 114 respectively. Status point 24 will not increment an accumulator point. State transitions
of less than 30 milliseconds will not cause the accumulator to increment.

To check the current accumulator value, use the counter read command (cr or crmp). To check the
current state of the status input, use the status read command (sr or srmp). To edit the accumulator
configuration, use the menu command (cf) and select the system configuration editor.
1.4.6.1 KYZ Accumulator Inputs

The status accumulator (or pulse counter) option counts the number of transitions on selected status points
using the status input hardware. Unlike the standard accumulator points, the KYZ accumulator points use
2 status points per accumulator and require a Form-C contact as an input. The details of the operation are
as follows.
To cause an accumulator to increment, the basic sequence must be followed: 1. point A on (closed or 1),
point B off (open or 0); 2. both points off; 3. point A off and point B on. The reverse sequence will also
14
cause the accumulator to increment: 1. point A off, point B on; 2. both points off; 3. point A on and point
B off. Any other transitions are ignored. When a point is configured as a KYZ accumulator point, status
transitions are not transmitted to the master. However, the current state of the status point can be
monitored via the maintenance terminal's sr command. Each status input point is debounced individually
in the same manner that the SOE system debounces the data before the transition is processed as a KYZ
accumulator point.
Status Pt. A Status Pt. B Action

1 0 Initial state
0 0
0 1 Accumulator increments
0 0
0 0
1 0 Reject transition
1 1 Reject illegal transition
1 0 Reject transition
0 0
Table 1.4.6.2-1: KYZ Accumulator Transitions
The reporting of values behaves in the same manner as described under regular Accumulators above.
1.4.6.2 KYZ Accumulator Configuration

The configuration of Accumulator point is a two step process where accumulator points first are
configured from status points and secondly, the configured accumulator points are map to one or more
masters.
First Status Point to be used for KYZ Accumulators: This is the first valid hardware status point
that will be processed as an accumulator point. The points reserved are sequential, starting at this point,
and 2 status points are used per accumulator point.
Total number of KYZ Accumulator Points (1 accumulator pt uses 2 status pts): This
determines the quantity of status points that will be treated as accumulator points. Two status points are
required per accumulator point. If no accumulator points are required, set the quantity to zero.
First KYZ Accumulator Point Number to use: The accumulator point number that is associated
with the first and second status point marked as an accumulator.
KYZ Accumulator Debounce Time (ms units): The minimum length of time a transition must be
stable before it will be counted as a transition.
15
Example:
First Status Point to be used for KYZ Accumulators: 12

Total number of KYZ Accumulator Points (1 accum pt uses 2 status pts): 5
First KYZ Accumulator Point Number to use:112
KYZ Accumulator Debounce Time (ms units): 25
With the above settings, transitions on status points 12/13, 14/15, 16/17, 18/19 and 20/21 will be counted
in accumulator points 112, 113, 114, 115 and 116 respectively. Status point 22 will not increment an
accumulator point. State transitions of less than 25 milliseconds will not cause the accumulator to
increment.

To check the current accumulator value, use the counter read command (cr or crmp). To check the
current state of the status input, use the status read command (sr or srmp). To edit the accumulator
configuration, use the menu command (cf) and select the system configuration editor.
1.5 Analog Hardware Sub-system Operation

The Scout and Hunter have different input circuits and scanning which are described separately below.
1.5.1 Scout Analog Hardware Sub-system Operation
1.5.1.1 Scout Analog Hardware Operation

The analog input boards are the boards to which the field transducer inputs are connected. These boards
contain a filter network to filter out transient noise, common mode noise, and differential ac noise. Each
analog point has an analog switch that connects the selected point to the analog bus.
Two types of boards are currently used on the Scout. These are the original 56718 and the new 51483
analog input boards. Both have the same functions and characteristics, but the 51483 has a smaller
physical size and is available in an enclosure. The two types of boards can be used on the same Scout.
The analog input boards are linked together via a daisy chained ribbon cable bus. This bus contains 3
address lines, 4 point select lines, 1 pair for the analog signal, and other miscellaneous control lines. The
bus uses 15 Vdc logic levels and carries +/- 15 Vdc power. The 51459 CASCO Board supplies this
voltage. Each board and therefore range of points has it's own unique address. The boards are position
independent on the bus, so care has to be taken to ensure that each input board is strapped correctly.
The CASCO Board has an additional interface connector. This allows connections on two banks or busses
of analog inputs for 256 total inputs.
16
Strap W1 Jumper
Address Position Function
A4 A2 A1
0 0 0 0 Analog Points 1 to 16 (129 to 144)
Table 1.5.1.1-1: Analog Board Jumper Configuration
Point numbers in ( ) are for the optional bank 2
The LED on the analog input board indicates that the analog cards are being scanned. The LED remains
on for approximately 30 ms after the board is accessed. Each board is scanned every two seconds and the
LED remains on for approximately 30 ms after the board is accessed
The analog interface circuits on the 51459 CASCO Board provides an interface between 51462 Main
Processor Module (MPM) and the analog input cards. This circuit provides analog to digital conversion
and address drive. Two analog reference points are also provided: +90% and -90% of the full scale.
These values are accessible as analog points at address 256 and 257 in the database.
The 51459 I/O Board can also be configured to enable a 60/50 Hz filter. The hardware will generate 2
analog to digital conversions one half cycle apart for each analog point. The analog scanning software
will take these 2 readings and store the average of the 2 values into the analog database. This will provide
additional line frequency noise immunity at the expense of a slower analog scan rate. To enable the filter,
the configuration parameter, Analog Filter (None, 60/50 Hz), will need to be set to a 5 or a 6.
The values produced by the analog to digital converter are in 12 bit format and stored as such in the
database. When these database values are transferred to the master station protocol and this protocol
caters to more than 12 bit values an option is available to report the 12 bit values as +2047/-2048 (no shift
of value) or 16 times higher at +32752/-32768 (shift of value) maximum.
1.5.1.2 Scout Analog Software Operation

The analog scan software accesses each board in the following manner:
Select first point on current board

Check if board responds
If not: set the pseudo status bit indicating that the board is failed.
Increment the board error counter.
If so: Convert the point
17
If the 60/50Hz filter is enabled wait for 1/2 cycle, convert the point again and store the
average value point in database, deselect the current point, and wait for point to be
deselected.
Select the next point on board.
Repeat the above 3 steps for each point on the current board.
Repeat the above steps for each board in the system.
Select and convert the low analog reference point.
If reference point is out of limits, raise an alarm.
Select and convert the high analog reference point.
If reference point is out of range, raise an alarm.
On power-up, the number of analog boards is determined by scanning all the possible boards in the
system. The board with the highest address that responds is considered to be the last equipped board.
Thereafter the scanning software only processes the equipped boards. If no boards were found, there is no
scanning and no reference points are reported.
Analog points are placed in the database starting from point 0 in the database and up to the last detected
board. These points must be mapped to one or more master station ports in order to be reported. The
default is that no points are mapped to any master. See section on mapping for further details.
1.5.1.3 Scout Analog Reporting

Points of interest must be mapped to one or more master station ports in order to be reported. The default
is that no points are mapped to any master. See section on mapping for further details.
Analog upsets/events are determined when the count changes by the analog point upset
threshold/deadband. If an analog is flagged as an upset, the analog will be transmitted to the master
station on the next data poll. Only the most current analog data is transmitted to the master. On a Station
Controller reset, the individual upset thresholds are set to the global default upset threshold. This will be
modified if deadband ranges are set in the controller or if deadbands are set in any downloaded mapping
files from the Station Explorer. Individual upset thresholds can be downloaded from the master depending
on protocol used.
Previous Current Upset Flagged

Value Value Threshold As Upset
1286 1290 4 Yes
1286 1289 4 No
1 -1 2 Yes
Table 1.5.1.3-1: Upset Detection Examples
Two analog reference inputs on the 51459 CASCO Board are set to -90% (-1800 counts) and 90% (1800
counts) of full scale. The -90% input will be stored as pseudo analog point # 256 and the 90% input will
be stored as pseudo analog point # 257. The reference points are treated as normal analog inputs except
for the analog reference out of range detection. When one or both of the analog reference points pass out
of range, the analog reference out of range status bit that is returned in line 0 of the QUICS4 protocol will
be set. The analog upset threshold value is used to provide hysteresis of the reference points. (i.e. the
acceptable limits are constrained by the value of the analog upset threshold.)
18
Minimum Maximum
Reference Nominal Value Acceptable Acceptable
Point (counts) Value (counts) Value (counts)
-90 % -1800 -1820 -1780
+90% 1800 1780 1820
Table 1.5.1.3-2: Reference Inputs Acceptable Range
If an analog conversion failure is detected, the analog conversion failure status bit that is returned in line 0
of the QUICS4 protocol is set. Last converted data will then be used until the failure is cleared.
If an analog board is addressed and does not respond, an error counter pertaining to that board is
incremented each time that board is addressed. Also a pseudo status point indicating a board failure is set
to a 1. The value last read in from the board is used for the current data in this case. The database points
for all 16 points of a failed board will be marked Failed. This will appear when any failed points are
displayed by the console or the web server. This information can also be transmitted to a master
depending on protocol used together with the last converted value.
The values originating from analog hardware input boards are in 12 bit format and stored as such in the
database. When these database values are transferred to the master station protocol and this protocol
allows for 16 bit values an option is available to have the database value be reported in the least
significant 12 bits (no shift/align of value) or as the most significant bits (shift/align of value) in which
case the values reported to the master will be 16 times larger.

To check the current state of the analog input or the reference points, use the analog read command (ar).
1.5.1.4 Scout Analog Configuration

Default Analog Upset Threshold (0 = Always upset): This is the upset threshold/deadband that
will be used to determine if the analog point data has changed enough to be declared an upset or event.
Analog Filter (None, 60/50 Hz): This selects the optional analog filter. A 'N' disables the filter
whereas a '5' or '6' enables the filter.
Use Shift for hardware AI points: This selects the alignment of analog database point values
originating from the hardware analog boards into the master station protocol. Refer to the section above
on Analog Reporting for details.
1.5.1.5 Scout Analog Deadband Configuration

The Analog Deadband Editor allows the set up of deadbands for one or more ranges of points. These
deadband ranges are applied in order. This means that if a point appears in more than one range its
deadband will be the deadband in the last range that contains the point. The deadbands configured in this
19
editor will overwrite the default deadband set for all point. These deadbands can also be overwritten by
deadbands defined in and downloaded by the Station Explorer. The deadband changes made to the default
setting by the editor and the Station Explorer will be retained in memory at power down. Finally, the
deadbands can also be changes by the master using the assigned object in DNP. However, these changes
are not retained during restart or power down and will have to be reloaded.
List Setup Ranges: This option displays the current list of ranges.
Change Setup Range: This option can be used to change one or more of the parameters of an existing
range.
Add Setup Range: This option can be used to add a new range to the list before or after any of the
existing ranges.
Delete Setup Range: This option can be used to delete any one of the current ranges.

To check the current deadband of an analog input use the analog read command (ar 0) or the analog
deadband command (ad 0 0 15).
1.5.1.6 Scout Analog Calibration

The software performs the analog calibration using an input on any point of any input board. The
references will be calibrated first to -1800 and +1800 for -90 and +90% of full scale. Then the actual
inputs will be calibrated to zero offset. Finally the gain will be calibrated for the inputs using an input
signal on a selected point set at 90 % of full scale value. The analog circuits on all inputs are using
precision components to eliminate the need to calibrate each input. With 90 % input the calibration will
set the full scale value to 2000. The full scale value can also be adjusted to 2047 by applying 88% input
during calibration.
When the calibration is complete the calibration values are normally stored in EEPROM on the CASCO
board. However, for those early released CASCO boards on which EEPROM is not available, the
calibration values will be automatically saved on the MPM board.
The Scout has to be restarted for these values to take effect. When Scout is started, it will try to read and
use the calibration data from CASCO board. However if the calibration data is not available from
CASCO board, it will automatically try to read and use it from the MPM board; if still not available from
MPM board, it will use the default calibration data with a gain and offset adjustments of 1 and 0
respectably.
NOTE 1: For CASCO boards on which EEPROM is not available, calibration is recommended if either
the MPM or the CASCO board has been replaced. The calibration file may also be loaded to a PC for
storage and then reloaded to the Station Controller if only the MPM has been replaced.
NOTE 2: To know if a CASCO has its EEPROM available, use fs command to check where
AI_CALIBRATION file is saved. If it is not saved in CASCO EEPROM device, the board does not have
EEPROM.
20
The calibration function can only be invoked by the maintenance console. Follow the instructions given
by the console to perform the calibration.
Error messages will be displayed if any calibration section can not be completed. In general the value to
be calibrated must be within a set range and be stable for the calibration to be completed. The reason for
the failed calibration will be displayed.
Error messages for references:

• “Zero reference calibration failed. Values read, NNN to NNN, are not within NNN of NNN or
stable within +/-NNN.” Where the NNN’s are numbers.
• “Ten reference calibration failed. Values read, NNN to NNN, are not within NNN of NNN or
• “Ninety reference calibration failed. Values read, NNN to NNN, are not within NNN of NNN or
• “Negative ninety reference calibration failed. Values read, NNN to NNN, are not within NNN of
NNN or stable within +/-NNN.” Where the NNN’s are numbers.
Error messages for zero calibration:

• “Zero calibration failed. Values read, NNN to NNN, are not within NNN of NNN or stable within
+/-NNN.” Where the NNN’s are numbers.
• "Board read error, calibration failed."
• "Conversion error, calibration failed."
Error messages for positive scale calibration:

• “Positive full scale calibration failed. Values read, NNN to NNN, are not within NNN of NNN or
Error messages for negative scale calibration:

• “Negative full scale calibration failed. Values read, NNN to NNN, are not within NNN of NNN
or stable within +/-NNN.” Where the NNN’s are numbers.
21
To check the current state of the analog input and the reference points, use the analog read command
(ar 0 256 257 will display the first hardware point and the two reference points). For calibration only one
point needs to be connected to a reference source. All other points can be left connected to the field
wiring.
1.5.2 Hunter Analog Hardware Sub-system Operation
1.5.2.1 Hunter Analog Hardware Operation

The field wiring is connected to the Hunter board directly on removable terminal blocks. Three types of
inputs are available. Four inputs allows for dc mA or voltage input from transducers, 3 or 6 inputs accept
ac voltage from potential transformers and 9 or 6 inputs accept ac current from current transformers.
The dc inputs are differential and have +/- 1 mA as defaultrange and 0 – 20 mA as a jumper option. The
input current is converted to 1 Volt by input scaling resistor (1.00 kOhm for 1 mA and 50 Ohm for 20
mA). Voltage inputs of 1 V, 5 V, 10 V, 30 V and 60 V are selectable by jumpers on a per channel basic.
Refer to Jumper settings section of this document for details. The selectable input ranges is only available
on unit issue 2 and up.
The ac inputs are transformer coupled and the signals are filtered against high frequency noise before
being multiplexed and converted to digital values. The voltage inputs have 150 Volts as full scale. The
current inputs have two input ranges of 10 Amps used for measurement values and 20 Amps used for
fault indications.
Internal reference signals of 0, 10 and 90 % of full scale are available to validate the analog subsystem.
All inputs and references are converted 32 times per ac cycle.
The frequency of the power system (60/50 Hz), will need to be set to a 5 or a 6. This is done with the
maintenance terminal using cf command.
1.5.2.2 Hunter Analog Software Operation

The converted values are processed by the Digital Signal Processor (DSP) on the Hunter board and the
resulting values are placed in the database starting at point 0. The resulting values from the ac inputs are
instantaneous rms values for voltage, current and power as well as energy and power quality data.
The ac inputs are available in two configurations: 3 voltage and 9 current inputs and 6 voltage and 6
current inputs. The 3 and 9 configuration is ideal for obtaining measurements from 3 feeders with the
same voltage bus. The 6 and 6 configuration will provide measurement for 2 feeders with separate voltage
busses. The calculations of power and energy values are based on these configurations. The calculations
for both configurations are based on WYE power system configuration with voltage and current inputs
from all three phases.
22
1.5.2.3 Fault Indicators
Fault Indicators are available for capturing fault current, voltage sag and swell events. Indication of an
event consists of status bit time stamped with start and end times as well as analog values with voltage
and current captured during the event. The analog event values can be reported with time stamp (end of
event) if DNP is used for master station communication. Fault indicator event is triggered when the
associated threshold is exceeded. The thresholds are shared with the waveform capture and can be set
from the master, via the web server in the Hunter or from the Power Quality Display pc application. Time
delay can be set and which has to be exceeded before fault is detected. The time delay is shared with the
fault indication followed by loss of voltage function described later and can be set from the master or via
the web server in the Hunter. A Minimum Hold time can be set to ensure that the fault indication duration
is never less than the set hold time. This time can be set from the master or via the web server in the
Hunter.
All current and voltage inputs (phases) have individual status input and analog input points assigned for
event capturing as indicated in Database Configuration section in this manual. Analog outputs (setpoints)
are used to set the thresholds and control outputs can be used to reset the last captured analog values.
Multiple events on the same phase or multiple phases can be captured when DNP is used for master
station communication. Each event creates two status changes (ON at the start and OFF at the end of the
event). Both are transferred to the DNP event buffer with time stamp. Depending on the type of event one
or two analog values will also be captured and transferred to the DNP event buffer. Time stamping can be
configured to be included on all analog event values. The analog values will remain frozen until the next
event occurs on that phase or until it is reset by the control action on that phase.
Fault current event generates status events and analog event values for both maximum current and
minimum voltage detected during the event for the phase.
Voltage sag event generates status events and analog event value for minimum voltage detected during
the event for the phase.
Voltage swell event generates status events and analog event value for maximum voltage detected during
the event for the phase.
The status indications for fault current, sag and swell are set and reset automatically as the conditions
starts and ends. The analog values will remain frozen until either a new events are detected or when they
are reset by controls. The control points to be used can be found in the Database Configuration section in
this manual.
The thresholds control when events will be captured. These can be set from the master station using AO
objects in DNP or via the Hunter’s web server using Setpoint values. The third option is the Power
Quality Display (PQD) application. The PQD can also adjust the threshold hysterises. The hysterises
prevents multiple event capturing if the phase value is close to the threshold. The hysterises is set to
default values until adjusted by the PQD. The default threshold and hysterises values are listed at the end
of Database Configuration section in this manual. All threshold and hysterises settings are stored in non
volatile memory and retained during power down. The AO or Setpoint points to be used can be found in
the Database Configuration section in this manual.
23
1.5.2.4 Waveform Capture
Waveform capture can be activated by an overcurrent condition, harmonic distortion, voltage swell or sag
or on demand. When triggered, 36 cycles on data are captured for all 12 input channels, 4 cycles before
the trigger and 32 after. Up to 8 such events can be stored in the Hunter before the oldest event will be
overwritten. Status bit, 32-39, will be set for each activated event and reset when the data has been
uploaded to the Power Quality Display application. Sending a trip/ open command to the pseudo–control
322-329 from the Master Station, can reset the event bits. Pseudo-control 321 mark as read all events and
will clear status points 32-39. The buffer can be completely erased by tripping point 330. The Power
Quality Display application is used to set the trigger values, upload, display and save event data. The
communication to the Hunter can be selected to be serial via dial in modem or RS232 directly to port 1 on
the Hunter or via network to either of the two Ethernet ports on the Hunter. A separate manual is
available for the Power Quality Display application.
1.5.2.5 Fault Detection with Loss of Voltage

This function is in parallel to the regular Fault Indicators. The fault detection is the same as describe in
previous section except this function has added parameter for time delay which has to be exceed before
the fault is detected. The threshold is the same used for both functions. After the fault has been detected
the function will wait for the fault to return below the threshold. At that time the voltage on all 3 phases
on the associated voltage inputs are monitored. If any of the 3 voltages goes below a settable parameter
for longer that a settable parameter, then a status bit is set to indicate that the upstream breaker has
opened and interrupted the fault. The status indication can be used as a “sectionalizer count” in PLC
sectionalizer logic. The status indication will be cleared when the voltage again exceeds the threshold and
a new sequence is ready to be detected.
This function is enabled as an option by installing jumper in W15 position 1. Enabling this function will
disable harmonic calculations on all inputs.
For information of the point values described in this section and their location in the database refer to the
section for Database Configuration in this manual.
1.5.2.6 Hunter Analog Reporting

Points of interest must be mapped to one or more master station ports in order to be reported. The default
is that no points are mapped to any master. See section on mapping for further details.
Analog upsets/events are determined when the count changes by the analog point upset
threshold/deadband. If an analog is flagged as an upset, the analog will be transmitted to the master
station on the next data poll. On a Station Controller reset, the individual deadbands are set to the global
deadband that is set via the Station Configuration Editor. Individual deadbands can be set in the Hunter
by the maintenance terminal or the web server and/or downloaded from the Station Explorer or from the
master depending on protocol used.
24
Previous Current Upset Flagged
Value Value Threshold As Upset
1286 1290 4 Yes
1286 1289 4 No
1 -1 2 Yes
Table 1.5.2.3-1: Upset Detection Examples
The values produced by DSP are in 12 bit format and stored as such in the database. When these database
values are transferred to the master station protocol and this protocol allows for 16 bit values an option is
available to have the database value be reported in the least significant 12 bits (no shift/align of value) or
as the most significant bits (shift/align of value) in which case the values reported to the master will be 16
times larger.

To check the current state of the analog input or the reference points, use the analog read command (ar or
armp
1.5.2.7 Hunter Analog Configuration

Default Analog Upset Threshold (0 = Always upset): This is the upset threshold/deadband that
will be used to determine if the analog point data has changed enough to be declared an upset or event.
AC Frequency (60/50 Hz): This selects the operation frequency of the power system.
Use Shift for hardware AI points: This selects the alignment of analog database point values
originating from the DSP to points in the master station protocol. Refer to section above on Analog
Reporting for details.
1.5.2.8 Hunter Analog Deadband Configuration

The Analog Deadband Editor allows the set up of deadbands for one or more ranges of points. These
deadband ranges are applied in order. This means that if a point appears in more than one range its
deadband will be the deadband in the last range that contains the point. The deadbands configured in this
editor will overwrite the default deadband set for all point. These deadbands can also be overwritten by
deadbands defined in and downloaded by the Station Explorer. The deadband changes made to the default
setting by this editor and the Station Explorer will be retained in memory at power down. Finally, the
deadbands can also be changes by the master using the assigned object in DNP. However, these changes
are not retained during restart or power down and will have to be reloaded.
List Setup Ranges: This option displays the current list of ranges.
25
Change Setup Range: This option can be used to change one or more of the parameters of an existing
range.
Add Setup Range: This option can be used to add a new range to the list before or after any of the
existing ranges.
Delete Setup Range: This option can be used to delete any one of the current ranges.

To check the current deadband of an analog input use the analog read command (ar 0) or the analog
deadband command (ad 0 0 15).
1.5.2.9 Hunter Analog Input Adjustment

Each of the 12 direct ac (transducerless) inputs can be adjusted separately for both magnitude and phase.
The magnitude adjustment has a range of +/- 10.0 percent or 100 per mille and the phase can be adjusted
+/- 90 degrees. The adjustment is primarily used to compensate for external sensor or transformer
deviations. If a current transformer connected to channel 6 produces 5.4 % less in magnitude and a phase
lag of 7 degrees from the ideal values, then channel 6 can be adjusted to compensate by entering -54 for
magnitude and -7 for the phase. This will adjust the magnitude up by 5.4% and place a 7 degree lead on
the phase.
The Channel numbers corresponds with the database designations as listed in the table and depends of
input configuration.
Ch1 Ch2 Ch3 Ch4 Ch5 Ch6 Ch7 Ch8 Ch9 Ch10 Ch11 Ch12
Bus Bus Bus Bus Bus Bus

6V F1 F1 F1 F2 F2 F2
1 1 1 2 2 2
6C Ph A Ph B Ph C Ph A Ph B Ph C
Ph A Ph B Ph C Ph A Ph B Ph C
Bus Bus Bus

3V F3 F3 F3 F1 F1 F1 F2 F2 F2
1 1 1
9C Ph A Ph B Ph C Ph A Ph B Ph C Ph A Ph B Ph C
Ph A Ph B Ph C
Table 1.5.2.6-1: Channel to database designation
1.5.2.10 Hunter Analog Calibration

The software perform the analog calibration by sampling predefined and stable sources applied to all ac
voltage, ac current and dc mA inputs. The calibration can only be initiated from the console.
The references will be calibrated first. Then the actual inputs will be calibrated to zero offset. Finally the
gain will be calibrated for the inputs using the connected input signals first the ac values then the dc
values.
26
Tip: When the dc input are calibrated and only one source is available the calibration time can be reduced
if the source is moved to the following channel as soon as the present one is accepted.
When the calibration is complete the calibration values are stored in EEPROM on the Hunter board.
The Station Controller has to be restarted for these values to take effect. When the Station Controller is
started, it will read and use the calibration data from Hunter board. However if the calibration data is not
available, it will use the default calibration data.
Equipment required.
Accurate and stable ac voltage and current source to generate the required full scale ac values. Typically
150 Vac and 10 Aac. Voltage and current outputs must be in perfect phase to each other.
Accurate and stable current source to generate required full scale dc mA. Typically 1 mAdc.
Maintenance terminal.
Set Up.
Power up the Station Controller and allow it to stabilize for 5 minutes.
Analog values can be viewed on the maintenance terminal (ar command)
Adjust the dc mA source to full scale (typically 1 mA) as it is connected to one dc mA input. Then
disconnect the source.
Start with dc mA inputs open.
Connect the ac voltage source to all voltage inputs in parallel and the ac current scource to all current
inputs in series. All must be in phase.
Set the sources to half of full sacle (half scale is typically 75 Vac and 5 Aac)
Procedure.
When ready to calibrate the Station Controller use the ac command on the maintenance console and
follow the instructions.
A calibration session would look like this
Maint (on-line): ac
Calibrate Hunter Analog Inputs (y/n)?
12:39:12:711 Calibration Starting
12:39:12:904 Step 0x10: Calibrating Reference 0
12:39:32:911 Step 0x20: Calibrating DC Channel 0 zero
12:40:35:261 Step 0x30: Calibrating AC Channel 0
27
12:41:15:275 Step 0x3A: Calibrating AC Channel 10
12:41:19:276 Step 0x3B: Calibrating AC Channel 11
12:41:37:702 Step 0x80: Ready for Channel 0 full scale
12:42:29:722 Step 0x40: Calibrating DC Channel 0 positive (neg not done)
12:42:31:720 Step 0x90: Accepted
12:43:06:151 Step 0x88: Ready for Channel 0 negative
12:43:58:171 Step 0x70: Calibrating DC Channel 0 negative (pos done)
Maint (on-line):

To check the current state of the reference points, use the analog read command (ar 0 2 3 will display 0,
10 and 90 % references).
1.6 Control Hardware Sub-System Operation

The Scout and Hunter have different control output circuits which are described separately below.
1.6.1 Scout Control Operation
1.6.1.1 Scout Hardware Operation

The 56720 control output boards are the boards to which the field control output points are connected.
These boards contain the final output relays of the Station Controller.
The control output boards are linked together via a daisy-chained ribbon cable bus. This bus contains 16
relay select lines and 16 board select lines to give a total capacity of 256 points or 128 open/close pairs.
Each board (and therefore range of points) has its own unique address. The boards are position
28
independent on the bus, so care has to be taken to ensure that each control output board is strapped
correctly for the required address.
There are no special control circuits on the control output board. The X and Y relay drivers, current
limiter, etc. exist on the 51459 CASCO Board.
Strap
Configuration Function
X1: 1-2 Control Output Points 1 to 8
Table 1.6.1.1-1: Control Board Strap Configuration and Point Range
The control output hardware enforces a Select-Check-Operate command sequence. A Select command
causes the X and Y output drivers corresponding to the chosen point to be energised, and the output
drivers are read back. This checkback is verified against the point number and is also returned to the
Master for verification, if applicable. An Open or Close command can then be received, to energise the
desired control relay. This must occur within the Control Select Timeout (typically set to 15 seconds) of
the selection.
The length of time the control is operated for is contained in the Execute (Open or Close) message
depending on protocol used. If it is not specified or if the time appears as 0, the default Control Operate
Duration (typically set to 1 second) is used.
There are 2 types of hardware protection to ensure false controls are not executed.
1. Select-Check-Operate - as described above.
2. Relay Current Limiter - the relay current limiter supplies enough current to pick-up
one relay, but not 2. In the event that 2 relays attempt to energize at the same time,
no relays will be operated. An error is reported on the maintenance console: "Control
Overcurrent Detected".
29
1.6.1.2 Scout Control Software Operation
When a select command is received, the requested point is selected. The point is de-select by the
software after a timeout of typically 15 seconds. If a control operate command is received and no point is
currently selected, no operation is attempted and a checkback error is return. Therefore, a control operate
command must be received within the Control Select Timeout (typically set to 15 seconds) after the initial
select command.
If a selection is in progress and a new selection is received, the new selection overrides the previous
selection.
If a control command is received, and a different point is selected, a checkback error is returned.
If a control is in progress (either an open or close) and a second control command is received, a
checkback error is returned and the original control is not interrupted.
Control points in the database are linked linearly to control outputs starting from point 0 in the database
and up to the last possible board. These points must be mapped to one or more master station ports in
order to be controlled. The default is that no points are mapped to any master. See section on mapping for
further details.
1.6.2 Hunter Control Operation
1.6.2.1 Hunter Hardware Operation

The field wiring for controls are typically connected to the final interposing relay board of various
variations each with different contact ratings. The interposing board is connected to the Hunter board via
a ribbon cable.
The typical output configuration is using the DOM 8 relay board that provides 8 relays. This arrangement
can be expanded with an additional DOM 8 if the DOMEXP board is added to the Hunter’s J15
expansion connector. The DOF 16 relay board comes in configurations for 16 individual control outputs
or in 8 x 8 matrix for a total of 64 control outputs. This configuration requires 4 DOF 16 boards and the
DOMEXP board.
The control output hardware enforces a Select-Check-Operate command sequence. A Select command
causes a select relay corresponding to the chosen point to be energised, and the checkback contacts on all
the select relays are read back. This checkback is verified against the point number and is also returned to
the Master for verification, if applicable. An Open or Close command can then be received, to energise
the desired control relay. This must occur within the Control Select Timeout (typically set to 15 seconds)
of the selection.
The length of time the control is operated for is contained in the Execute (Open or Close) message
depending on protocol used. If it is not specified or if the time appears as 0, the default Control Operate
Duration (typically set to 1 second) is used.
30
1.6.2.2 Hunter Control Software Operation
When a select command is received, the requested point is selected. The point is de-select by the
software after a timeout of typically 15 seconds. If a control operate command is received and no point is
currently selected, no operation is attempted and a checkback error is return. Therefore, a control operate
command must be received within the Control Select Timeout (typically set to 15 seconds) after the initial
select command.
selection.
If a control command is received, and a different point is selected, a checkback error is returned.
If a control is in progress (either an open or close) and a second control command is received, a
checkback error is returned and the original control is not interrupted.
Control points in the database are linked linearly to control outputs starting from point 0 in the database.
These points must be mapped to one or more master station ports in order to be controlled. The default is
no points mapped to any master. See section on mapping for further details.
1.6.2.3 Hunter Control Database

The internal database for direct hardware controls has 3 sections where controls can be mapped to the
master points. The maximum limit for relays is 16 for individual configuration and 64 for matrixed
configuration and the two configurations are mutually exclusive.
Database points 0 to 7 are used for individual control outputs for up to 16 relays. The sequence is such
that the first relay is assigned to OPEN command for the first point and the second relay is assigned to
CLOSE command for the first point.
Database points 20 to 27 are used for individual control outputs for up to 16 relays. These relays are the
same as described above. However, the sequence is such that the first relay is assigned to CLOSE
command for the first point and the second relay is assigned to OPEN command for the first point.
Database points 28 to 59 are used for matrixed control outputs for up to 64 relays. The sequence is such
that the first relay is assigned to CLOSE command for the first point and the second relay is assigned to
OPEN command for the first point.
1.6.3 Control Configuration

using any of the 3 configuration methods described in the beginning of this manual. The description
applies both to the Scout and the Hunter.
Control Select Timeout (ms units): This is the maximum time allowed between control select and
control execute command. If no control command is reached before this time, the selected point is
deselected and the following control operation will be blocked.
31
Control Operate Duration (ms units): This is the default time that a momentary control relay is
activated on a control command, if no time or zero time is specified in the protocol.
Hardware Control Lockout Enabled: This will enable all hardware control to locked out if the
conditions in the following parameters are met. This is a software lockout which is in addition to the
hardware lockout of the Local/Remote switch.
Hardware Control Lockout Status Point Map: This selects which master map will be used to
reference the status point in the next parameter (0 for direct mapping into database and 1 to 4 for master 1
to 4 maps).
Hardware Control Lockout Status Point Point: This selects the status input point to be used for
hardware control lockout if enabled in the parameter above. The status input can be either a hardware
point or one of the internal pseudo points.
Hardware Control Lockout Point Polarity (Block when Status reads): This defines the state of
the selected status input that will lock out the hardware controls.
IED Control Lockout Enabled: This will enable all IED control to locked out if the conditions in the
following parameters are met. This is a software lockout.
IED Control Lockout Status Point Map: This selects which master map will be used to reference
the status point in the next parameter (0 for direct mapping into database and 1 to 4 for master 1 to 4
maps).
IED Control Lockout Status Point Point: This selects the status input point to be used for IED
control lockout if enabled in the parameter above. The status input can be either a hardware point or one
of the internal pseudo points. The Local/Remote switch is typically also connected to a status input to
signal its state to the master. This status point can be used here to also control the lockout of IED controls.
IED Control Lockout Point Polarity (Block when Status reads): This defines the state of the
selected status input that will lock out the hardware controls.
32
To select a control point, use the control select command (cs). To select and operate (open/close), use the
control open (co) or the control close (cc) command.
1.7 Setpoint Operation
1.7.1 Hardware Operation

The Station Controller does not have proprietary hardware to operate setpoints, but rather uses IEDs for
setpoint hardware.
1.7.2 Setpoint Software Operation

When a setpoint select command is received, the requested point is selected. The point is de-select by the
software after a timeout of typically 15 seconds. If a setpoint execute command is received and no point
is currently selected, no operation is attempted and a checkback error is return. Therefore, a setpoint
execute command must be received within the select timeout after the initial select command.
selection.
If a setpoint execute command is received and a different point is selected, a checkback error is returned.

To write a value to a setpoint, use the database command: db sp w xx yy, where xx is the point number
and y is the value to set the setpoint to.
1.8 ADAM4021 Analog Output Operation
1.8.1 Hardware Operation

The ADAM4021 analog output module is connected to the Station Controller as an IED. It receives the
digital input through an RS-485 interface from the Station Controller. It then uses its processor-controlled
Digital to Analog converter to convert the digital data into signals. You get a true read back of the analog
output signal from the unit's Analog to Digital Converter, which independently monitors the output.
Each analog output is isolated from the rest of the system by a transformer based isolation that provides
isolation up to 3000 Vdc.
33
Figure 1.8.1-1: ADAM 4021 Block Diagram
34
Analog Output Range 0 - 10V
0 – 20 mA
4 – 20 mA
Serial Input RS-485 (2 wire)
Baud rate: 1200, 2400, 4800, 9600, 19.2k, 38.4k
Maximum distance: 4000 ft. (1200m)
Accuracy +/- 0.1% of FSR for current output
+/- 0.2% of FSR for voltage output
Read back accuracy +/- 0.1% of FSR
Zero drift voltage output: +30 µV/ °C
current output: +0.2µA/ °C
Span temperature coefficient +/-25 ppm/ °C
Isolation rated voltage 3000 Vdc
Programmable output slope Voltage Output Current Output
(slew rate) Immediate change Immediate change
0.0625 V/sec 0.125 mA/sec
0.125 V/sec 0.250 mA/sec
0.250 V/sec 0.500 mA/sec
0.500 V/sec 1.000 mA/sec
1.000 V/sec 2.000 mA/sec
2.000 V/sec 4.000 mA/sec
4.000 V/sec 8.000 mA/sec
8.000 V/sec 16.00 mA/sec
16.00 V/sec 32.00 mA/sec
32.00 V/sec 64.00 mA/sec
64.00 V/sec 128.0 mA/sec
Current load resistor 0 to 500 Ω (source)
Bandwidth 100 samples per second
Output impedance 0.5 Ω
Watchdog timer Yes
Power supply +10 to +30 VDC (non-regulated)
Power consumption 1.4 W
Table 1.8.2-2: ADAM 4021 Specifications
1.8.2 Rescale of ADAM Values

The ADAM4021 analog output module has a scale of 0 to 4095 (unsigned 12 bits value) for both its
analog output and its analog input. However, in QUICS protocol data are transmitted between master and
Station Controller in signed 12-bit format (i.e. the data has a scale of 0 to 2047 in the positive value
range). To match the scale of the ADAM4021 and that of QUICS master, and to use the full resolution
available from ADAM4021, the following rules are applied:
35
1) In the master stations, both AO and AI of ADAM4021 use a scale of 0 to 2047.
2) In the Station Controller, a) when outputting to ADAM4021, the output value from
master is multiplied by 2 so that the full resolution of ADAM4021 can be used; b) When
inputting from ADAM4021, the input value to master is divided by 2 so that the scale of
ADAM4021 points in master station can be matched.
3) The data in the Station Controller database for Adam points is expected to have a scale of
0 to 2047.
4) The scale of 0 to 2047 applies to all master protocols.
1.8.3 ADAM4021 Configuration

Before an ADAM4021 can be connected to the Station Controller, it has to be correctly configured. Refer
to the maintenance section for configuration information.
The following items must be configured in the Station Controller configuration editor:
COM port ADAM4021 units connected to (8 = COM8): This is the communication port number
that is used to communicate with the ADAM4021 units. Ports 8 to 11 can be used.
Number of ADAM4021 units: This is the number of ADAM4021 units that are connected to the serial
port. Set this number to 0 to disable the ADAM4021 units.
First Setpoint Point Number to use: The first ADAM4021 unit (address 1) analog output
corresponds to this setpoint point number. The remaining units follow sequentially.
First Analog Point Number to use: The first ADAM4021 unit (address 1) analog input corresponds
to this analog point number. The remaining units follow sequentially.

To write a value to a setpoint, use the database command: db sp w xx yy, where xx is the point number
and y is the value to set the setpoint to. To read the current value of the setpoint, use the analog read
command (ar) and read the value of the corresponding output.
1.9 Master Communication
1.9.1 Overview
The master communication port is the data link between the master station and the Station Controller. The
Station Controller typically operates on a poll-response method, where the master sends a command to
get data or to execute a command, and then the Station Controller sends a response back to the master. If
there were errors in the message exchange, it is up to the master to restart the message exchange. If
communication is not received from the master for the configured time, the Station Controller will raise a
scanfail error (for QUICS IV/QUIN and Modbus only).
Quiescent operation or unsolicited mode is also supported depending on protocol. This mode of operation
relieves the master from having to continually poll the Station Controller for upsets/events. In this mode,
the Station Controller will send unsolicited status, analog and SOE upsets/events to the master as they
36
occur and as defined in the selected protocol. The master then will acknowledge the received data. This
mode of operation reduces the amount of traffic on the communication lines and is useful when there are
a large number of small Station Controllers sharing the same communication channel.
Up to four master communication links can be supported at the same time. Each master link has a
separate database so that upsets/events are sent to all selected masters. Each channel is independent of the
other and can run different protocols, baud rates and modes of operation. Each master link is mapped
independently to its database.
The communication link supports a direct connection (RS232) or the use of modems on a serial port. The
link can also be connected to a port on one of the Ethernet ports. The baud rate, handshaking and network
parameters are configured via the Com Port Configuration Editor.

To monitor communication between the master and the Station Controller, use the scan monitor command
(sm). To change the serial port settings or change the Station Controller number, use the system editors
via the menu command (cf).
1.9.2 Supported Protocols

The following protocols are supported. Not all protocols are licensed in each Station Controller. New
protocols are regularly added, so contact Survalent for the latest protocols that are supported.
QUICS IV
QUIN
DNP 3.0
IEC 870-5-101
IEC 870-5-104
TeleGyr 8979
Modbus RTU
Modbus TCP
Only one protocol can be supported on a given master communications port at a time.
1.9.3 Master Communication Configuration

Protocol (0=Disable, 1=QUIN, 2=QUICSIV, 3=DNP, 4=IEC, 5=GYR, 6=IEC104, 7=MODBUS):
This selects the master protocol to be used. A 0 indicates that no communication to the master is to take
place. Depending on protocol selected the Station Controller will present different questions.
1.9.4 QUICS IV/ QUIN - Master Communication Configuration

Comm Port to Use (2 = com2) :
37
This is the communication port that is used to communicate with the master station. Ports 0 to 15 are
assigned to serial ports and ports 16 to 31 are assigned to network ports. Presently ports 2 to 4, 8 to 11 or
15 and 16 to 31 can be used. The Controllers have the following physical serial ports:
Port 0: Maintenance port
Port 1: Configuration port
Ports 2 & 3: RS232 port with control signals
Port 4: RS485 port 2 or 4 wire.
Ports 5 to 7: not used
Ports 8 to 11: RS232 with control signals or RS485 2 wire.
Ports 12 to 15: RS232 with control signals or RS485 2 wire. Available only on the Scout.
Set Time Disable:
Setting this to true will disable the master to set the Station Controller 's clock.
Enable only one master to set the Station Controller’s clock.
Note: To enable the master to set Station Controller’s clock, this field has to be set to false and Respond
to Master Time Sync Commands field has to be set to true.
RTU Address:
This is the address of the Station Controller. The master must poll the Station Controller with this address
for the Station Controller to respond. For QUICSIV/QUIN protocol Station Controller accepts addresses
in the range between 0 and 127.
Respond to Master Time Sync Commands:
Setting this to false will disable the master to set the Station Controller 's clock .
Note: To enable the master to set Station Controller’s clock, this field has to be set to true and Set Time
Disable field has to be set to false.
Master Scanfail Timeout (sec units):
If a valid command from the master is not received by the Station Controller in this amount of time, the
Station Controller will raise a scanfail alarm.
Maximum Number of Reply Lines (QUIN protocol):
This limits the number of lines of data that the Station Controller will send to the master at one time.
Setting this to a lower number can reduce the control latency and improve communication in noisy
environments. This option is only valid if the QUIN protocol is enabled.
Enable Quiescent Mode:
Setting this to true enables the quiescent mode of communication.
Quiescent Wait For ACK Timeout (sec units):
38
When quiescent mode is selected, this is the amount of time that the Station Controller will wait for a
reply from the master before re-transmitting the original command.
Reset RTU on No Communication Timeout (min units):
If this parameter is set to non-zero value, then the Station Controller will reset after this timeout. If this
parameter equals 0, then the Station Controller will not reset after timeout.
Freeze (0) or Freeze & Reset (1) for Accumulators?:
When the Station Controller receives Freeze command from the Master it freezes its Running counters.
The counters may or may not be cleared after the freeze depending on this configuration of the Station
Controller. If 0 is specified (Freeze), then the counters will not be cleared. If 1 is specified (Freeze and
Reset), then the counters will be cleared. The Station Controller keeps separate database of running
counters for each master. The counters from a database of another master will not be affected by Freeze
command.
Accumulator Offset for QUIN / QUICSIV

First H/W Accumulator Point Number usually starts with 112 in the Station Controller (counters 0-111
are reserved for calculated energy values as well as internal Station Controller purposes). QUICSIV can
report only 16 counters to the Master. In previous software versions this offset was required to select
which 16 consecutive accumulator points were to be included in the protocol. However, this task is now
included in the point mapping function and this Offset parameter is no longer applicable.
1.9.5 DNP 3.0 - Master Communication Configuration

The following are DNP specific settings. More detailed description can be found in the DNP 3.0
documentation from the DNP Users Group and in the DNP Profile Document for the Station Controller.
Comm Port to Use (2 = com2):
RTU Address (default = 1):
for the Station Controller to respond. For DNP protocol Station Controller accepts addresses in the range
between 0 and 65535. Address 65335 is the DNP broadcast address, which all Station Controller s will
receive at in addition to their individual addresses.
39
Master Address (Default = 1024):
This sets the master address to which the Station Controller will send unsolicited messages. The Station
Controller will reply to a request from a master with this address only if the master address is less than
32000. The Station Controller will reply to a request from any master if the master address is equal to or
more than 32000
Data Link Retries (default = 0):
Maximum number of Data Link retries if data link Confirm is enabled (0 to 256).
Data Link Timeout (default is 1 and in 0.1 seconds):
Time between Data Link reties (1 to 300, 300 = 30 seconds)
Data Link Confirmation ? (default = Never):
This will enable or disable Data Link Confirm requests. If set to Never, then confirm request is disabled.
If set to Always, then confirm is requested on each DNP frame message. If set to Sometimes, then
confirm will only be requested on multi frame messages being transmitted. It is normally recommended
not to have Data Link confirm enabled since it adds considerable complexity and bandwidth requirement.
Application Timeout (default = 4 s = 4000 ms):
The Station Controller accepts values in the range between 0 ms and 1 hour (3600000 ms). Application
Confirm must be received before the timeout for the event to be removed from the transmit buffer.
Umode Enabled ? (default = No):
Setting this to 1 enables unsolicited mode of DNP protocol. (In unsolicited mode the Station Controller
may report significant events to the master station on its own without waiting for master to poll data.)
Umode Poll Frequency (default = 1 seconds):
The Station Controller accepts values in the range between 1 s and 1 hour (3600 s). The Station Controller
will repeat unconfirmed messages to the Master at this interval if Umode is enabled and Application
Confirm has not been received. Messages will be repeated at this rate until the set Application Retry value
has expired after which the massage will be repeated at the Degraded timer interval. New event data will
wait for this interval to expire before being transmitted.
Umode Degraded Poll Frequency (default = 5 min = 300 seconds):
The Station Controller accepts values in the range between 1 s and 1 hour (3600 s). The Station Controller
will repeat unconfirmed messages to the Master at this interval if Umode is enabled and all retries have
expired. This will continue until Application Confirm is received.
Umode Application Retry (default = 5 times):
40
The Station Controller accepts values in the range between 0 and 100. This limits the number of retries
the Station Controller does send events to the master station before it switches from Umode Poll
Frequency into Umode Degraded Poll Frequency.
Umode Reporting of Classes 1 – 3 enabled? (default = No):
Class 1 to 3 event data will automatically be reported if both Umode and this parameters are enabled. The
reporting can also be enabled or disabled by the appropriate DNP function code.
Umode Fixed Delay (default is 20 and in 0.1 seconds):
This parameter determines the minimum delay the controller with Umode enabled will wait after a
channel becomes free before starting to transmit. The DCD input signal on the RS232 port will indicate a
free or busy channel. Only ports 2 and 3 can be used for channel detection. The range is 0 to 256 and is in
0.1 second measure.
Umode Random Delay (default = 40 and in 0.1 seconds):
This parameter determines the maximum delay the controller with Umode enabled will wait after the
fixed delay has expired before starting to transmit. The time will be random between 0 and the set
parameter value. The range is 0 to 256 and is in 0.1 second measure.
AI Confirm ? (default = No) :
This enables Confirm request when AI object 30 is transmitted.
AI events with time? (default = No):
This selects AI events to be reported with or without time
AI/DI/CI Variation ? (default = without flag):
This selects if AI, DI and CI static objects will be reported without flags, with flags or dynamically. If
dynamically, then flags will be added when any abnormal flag is set on a point, otherwise the objects will
be reported without flags. A mix of variations may be included in same message.
Disable Master Time Set (default = Yes):
Setting this to true will disable the master to set the Station Controller 's clock. Enable only one master to
set the Station Controller’s clock.
1.9.6 IEC 870-5-101 - Master Communication Configuration

41
for the Station Controller to respond. For IEC protocol Station Controller accepts addresses in the range
between 0 and 255.
Long Pulse Duration in ms (default=10000 ms) :
The long pulse duration (0 to 30000) for controls (see 7.2.6.26 in 870-5-101 IEC document).
Short Pulse Duration in ms (default=1000 ms) :
The short pulse duration (0 to 30000) for controls (see 7.2.6.26 in 870-5-101 IEC document).
Setpoint Command (default = SBO) :
Setpoint commands may be configured as a “Direct” commands or as “Select Before Operate” (SBO)
commands. (There is a special Setpoint # 0xFFFF which always accepts both “Direct” and “SBO”
commands. This point is used to set Control Duration when qualifier <0> is used for controls, see 7.2.6.26
of 870-5-101 IEC document.)
Single Command (default = SBO) :
The Single command (type 45) in IEC protocol may be configured as a “Direct” command or as “Select
Before Operate” (SBO) command.
Double Command (default = SBO) :
The Double command (type 46) in IEC protocol may be configured as a “Direct” command or as “Select
Analog Input (AI) offset (default=0 ):
This offset (0 to 32767) will be added to the internal point addresses for analog inputs when used in the
IEC protocol
Digital Input (DI) offset (default=0 ):
This offset (0 to 32767) will be added to the internal point addresses for digital inputs when used in the
IEC protocol.
Double Digital Input (DI) offset (default=0 ):

42
This offset (0 to 32767) will be added to the internal point addresses for double digital inputs when used
in the IEC protocol
Analog Output (AO) offset (default=0
This offset (0 to 32767) will be added to the internal point addresses for analog outputs when used in the
IEC protocol
Digital Output (DO) offset (default=0 ):
This offset (0 to 32767) will be added to the internal point addresses for digital outputs when used in the
IEC protocol
Counter Input (CI) offset (default=0 ):
This offset (0 to 32767) will be added to the internal point addresses for counter inputs when used in the
IEC protocol
Balanced mode (default = No):
This parameter selects balanced mode (unsolicited reporting) or normal polling mode
set the Station Controller’s clock
Data link address size (default = 1 octet):
This parameter sets the number of octets to use (1 or 2).
Common address size (default = 1 octet):
This parameter sets the number of octets to use (1 or 2).
Object address size (default = 2):
This parameter sets the number of octets to use (1 to 3)
Normalized or Scaled analog values (default = Scaled):
This parameter selects which ASDU to use (Normalized – ASDU 9 or Scaled – ASDU 11).
Full time or Short time (default = Short):
This parameter selects which time format to use in the time stamp.
43
Refer to System Editors (cf) for additional set up options for Double Status Points and Step Position
Points
1.9.7 TeleGyr 8979 - Master Communication Configuration

The following are TeleGyr 8979 specific settings.
RTU Address:
for the Station Controller to respond. For GYR protocol Station Controller accepts addresses in the range
between 0 and 255.
Setting this to true will disable the master to set the Station Controller 's clock.
1.9.8 IEC 870-5-104 - Master Communication Configuration

The following are IEC 870-5-104 specific settings.
assigned to serial ports and should not be used for this protocol. Ports 16 to 31 are assigned to network
ports.
This is the address (0 to 255) of the Station Controller. The master must poll the Station Controller with
this address for the Station Controller to respond.
Long Pulse Duration in ms (default=10000 ms):
44
The long pulse duration (0 to 30000) for controls (see 7.2.6.26 in 870-5-101 IEC document).
Short Pulse Duration in ms (default=1000 ms):
The short pulse duration (0 to 30000) for controls (see 7.2.6.26 in 870-5-101 IEC document).
Setpoint Command (default = SBO):
Setpoint commands may be configured as a “Direct” commands or as “Select Before Operate” (SBO)
commands. (There is a special Setpoint # 0xFFFF which always accepts both “Direct” and “SBO”
commands. This point is used to set Control Duration when qualifier <0> is used for controls, see 7.2.6.26
of 870-5-101 IEC document.)
Single Command (default = SBO) :
The Single command (type 45) in IEC protocol may be configured as a “Direct” command or as “Select
Double Command (default = SBO) :
The Double command (type 46) in IEC protocol may be configured as a “Direct” command or as “Select
Analog Input (AI) offset (default=0 ):
This offset (0 to 32767) will be added to the internal point addresses for analog inputs when used in the
IEC protocol
Digital Input (DI) offset (default=0 ):
This offset (0 to 32767) will be added to the internal point addresses for digital inputs when used in the
IEC protocol
Double Digital Input (DI) offset (default=0 ):
This offset (0 to 32767) will be added to the internal point addresses for double digital inputs when used
in the IEC protocol
Analog Output (AO) offset (default=0 ):
This offset (0 to 32767) will be added to the internal point addresses for analog outputs when used in the
IEC protocol
Digital Output (DO) offset (default=0 ):
This offset will be added to the internal point addresses for digital outputs when used in the IEC protocol
Counter Input (CI) offset (default=0 ):
45
This offset (0 to 32767) will be added to the internal point addresses for counter inputs when used in the
IEC protocol
Single Input Frequency:
This parameter defines the frequency (in seconds between 0 and 65535) that all single input points will be
spontaneously reported.
Double Input Frequency:
This parameter defines the frequency (in seconds between 0 and 65535) that all double input points will
be spontaneously reported.
Step Position Frequency:
This parameter defines the frequency (in seconds between 0 and 65535) that all step position points will
Analog Input Frequency:
This parameter defines the frequency (in seconds between 0 and 65535) that all analog input points will
Frozen Counter Frequency:
This parameter defines the frequency (in seconds between 0 and 65535) that all frozen counter points will
set the Station Controller’s clock.
Refer to System Editors (cf) for additional set up options for Double Status Points and Step Position
Points
1.9.9 Modbus - Master Communication Configuration

The following are Modbus RTU and TCP specific settings. Modbus RTU can be used with either serial or
network ports. Modbus TCP should only be used with network ports
46
TCP Mode (default = No):
Setting this to true selects Modbus TCP mode. Otherwise Modbus RTU is used.
RTU Address:
This is the address (0 to 255) of the Station Controller. The master must poll the Station Controller with
this address for the Station Controller to respond.
Master Scanfail Timeout (default = 15 in seconds):
If a valid command from the master is not received by the Station Controller in this amount of time, the
Station Controller will raise a scanfail alarm.
1.9.10 IEC 61850 - Master Communication Configuration
The master communication port is the data link between Master Stations and the Station Controller. Up
to four master communication links can be supported at the same time, each can be set to different
communication protocols. The Station Controller supports the IEC61850 communications protocol
between the Station Controller and the Master Station. Only one of the four communication links can be
set to the IEC61850 protocol at a time, but up to 4 master stations can connect to one communication port
set as IEC61850.
The IEC61850 logical device in the Station Controller is configurable to suit the needs of the substation.
Changes to the logical device are made by editing the “RTU61850MODEL.CID” file. The
“RTU61850MODEL.CID” file is a “Configured IED Description” file written in SCL (Substation
Configuration Language) as defined by the IEC61850 standard. Data Objects within the IEC61850 model
are mapped to master points within the RTU Database configuration using the DATAMAPn.CFG file.
RTU Master points are mapped to RTU internal points using Master Map files.
The following are IEC61850 specific settings.
assigned to serial ports and ports 16 to 31 are assigned to network ports. IEC61850 can only be used with
network ports 16 to 31.
IED Name:
Identification name of the IED within the RTU61850MODEL.CID file. A model generation error will
occur if not set.
Access Point:
47
Access Point identification as set within the RTU61850MODEL.CID file. A model generation error will
occur if not set.
AP Title: (default = 1 3 9999 33)
Application Title. Application layer network addressing, clients must have matching AP title to connect.
AE Qualifier: (default = 33)
Application Entity Qualifier. Application layer network addressing, connecting clients should have
matching AE qualifier.
P Selector: (default = 0001)
Presentation Selector also abbreviated PSEL. Presentation layer network addressing, clients must have
matching settings to connect.
S Selector: (default = 01)
Session Selector also abbreviated SSEL. Session layer network addressing, clients must have matching
settings to connect.
T Selector: (default = 01)
Transport Selector also abbreviated TSEL. Transport layer network addressing, clients must have
matching settings to connect.
Report Scan Rate (default = 20 in 100mS) :
Sets how often the RTU will check conditions to see if a report is to be generated to be sent to the master
station. The default scan rate is 2 seconds; units are in 100mS. Valid entries are from 0 to 10000. 0 sets
the scan rate to as often as possible, which is approximately 50mS.
1.9.11 Master Points Mapping (applies to all protocols)

Station Controller internal database contains thousands of points. There are points corresponding to
hardware boards connected to the Station Controller (status, analog, control) as well as points for IEDs,
points reflecting internal Station Controller status, references etc. Not all data from the database may be
of interest to all master stations. The data base points can be mapped to each master individually using
either the Survalent master’s IED Wizard or the Station Explorer. The Station Explorer will allow points
mapping from hardware inputs and outputs to any of 4 masters. The Station Explorer will also map IED
points directly to any of 4 masters.
Note: Mapping files must be loaded to the Station Controller before database points can be accessed by a
master.
Maintenance Console Tip:
48
To see the date and time of the currently used mapping files, use the file system command (fs) and select
list files. The map file names are MxHDWPTMAP for the hardware points map and MxPyyIEDMAP for
the IED points map, where x is the master station connection number being used and yy is the IED port
number. In the file system command (fs) is also an option for displaying the content of a mapping file.
The commands <im x> and <mp x> will display the point assignments for master x
To monitor communication between the master and the Station Controller, use the scan monitor command
(sm).
1.10 IED Communication
1.10.1 Overview
The Intelligent End Device (IED) communications option allows the Station Controller to act as a master
to one or more devices. These are connected to an auxiliary communications line and the received
information is placed into the Station Controller 's own database for transmission to the master station.
To configure the IED subsystem, an IED mapping file is downloaded to the Station Controller. The
mapping file defines the IED port number, the protocol, the units and the data that will be accessed from
each IED.
1.10.2 Mapping File Generation

The mapping file can be generated on Survalent Master Station using the IED Wizard application and
down loaded to the Station Controller over the regular communication media if DNP protocol is used
between master and Station Controller. Alternatively, the mapping file can be generated on the Station
Explorer, which is a PC application program. The download can occur serially on port 1 on the Station
Controller or over either of the two Ethernet ports.
Refer to mapping section for detailed description of the Station Controller mapping as well as Station
Explorer User’s Guide.
49
1.10.2.1 Mapped Points Organization
The Station Explorer will define hardware points and IED points to be mapped to one or more master
station connections. The Station Controller will map hardware and IED points directly to the desired
points on each master station communication port. The database is still used as a holding place where all
data between hardware, IEDs and masters passes through. The hardware points will map to the database
in a fixed way such that hardware point 0 for either Status, Analog or Control maps to database point 0
and hardware point1 to database 1 and so on. The IED points are dynamically assigned points in the
database starting from point 1000 based on the maps loaded for IEDs.
Refer to Station Explorer document 74100-SEC
1.10.2.2 Mapped Points Access

Points inside the Station Controller can now be viewed and controlled by using reference to the database
or to points within any of the 4 master station protocols.
The standard 2 character command (e.g. ar 0) will access points in the database. The ar and cr commands
will also show what points in each of the master protocols this point is mapped to.
The 4 character command (e.g. armp 1 0) will access points in specified master number. It will also show
what database location is used to hold the specified point.

To see the date and time of the currently used mapping files, use the file system command (fs) and select
list files. The map file names are MxHDWPTMAP and MxPppIEDMAP, where x is the master number
and pp is the communication port number being used for IEDs. In the file system command (fs) is also an
option for displaying the content of a mapping file. This will show which points are available.
To monitor communication between the IED and the Station Controller, use the scan monitor command
(sm).
To view the received data, use the status read (sr or srmp), analog read (ar or armp), and counter read (cr
or crmp) commands. To control points in the IED use the control open (co or comp) or the control close
(cc or ccmp) command. To write setpoints in the IED, use the database command (db) with point type
SP.
1.10.3 SOE Time Tag

The rules for time tagging Status Events (SOE) are different for IED points from those for hardware
points. For IED SOE points, the following rules apply:
1) The IED status points must be included in the SOE configuration for the full rules to be
applied. Status points not included in the SOE configuration will only use rules 3a and
3b.
2) If status events are reported to the Station Controller from IED with time tags, these time
tags will be used as the valid SOE time tags and will be together with the status be
reported to master stations.
50
3) If status events are reported to the Station Controller without time tags, then
a) if the Station Controller time is valid, then events will be time tagged and
reported to masters by the Station Controller with the time they are received by
the Station Controller.
b) if the Station Controller time is not valid, then events will not be time tagged and
will be reported to masters without time tags.
1.10.4 Supported IED Protocols

The following protocols are supported. Not all protocols are licensed in each Station Controller. New
protocols are regularly added, so contact Survalent for the latest protocols that are supported.
Serial Communication:
ModbusRTU
DNP3.0
Cooper 2179
IEC870-5-101
IEC870-5-103
SPA BUS
Fast Meter Messages/ SEL
Network Communication:
ModbusTCP
DNP TCP
IEC 61850
Only one protocol can be supported on a given IED serial or network port at one time. However, the
Station Controller can support different IED protocols on different IED serial or network ports. Note that
multiple network ports can be carried on the same Ethernet port.
1.10.5 IED with DNP 3.0

The Station Controller supports IEDs with DNP3.0 connected through RS-232/ RS-485 serial or TCP/IP
network connections. Use available communication ports between 2 to 15 for serial and 16 to 31 for
network connections.
Normal operation
For each port the Station Controller will run independent task. This means that delays occurring in one
port (e.g., the IED is not connected) will not create any delays on another port.
The Station Controller will poll all IEDs (units) connected to a port for events (class 1,2, & 3). All units
will be polled in sequence with “Exception Poll Interval” milliseconds between each the poll on a
continuous basis. The Exception Poll Interval is defined in the Station Explorer under DNP Protocol
Parameters (default value = 2000 ms).
51
After events have be polled a period of times as defined by the All Data Poll Interval in the Station
Explorer under DNP protocol parameters, the Station Controller will interject one poll for events and all
data (classes 1,2,3 & 0) to all units on this port.
The Station Controller will interpret the responses from the IED and will put the values received from the
IED into the Station Controller database according to the mapping file.
If the RESTART bit in DNP IIN field is set in response message from the IED, the Station Controller will
send the message to clear this bit in the IED.
If Time Synchronization is enabled in the Station Explorer under DNP Protocol Parameters and if NEED
TIME bit in DNP IIN field is set in the response message from the IED, the Station Controller will
perform time synchronization by sending the time sync message.
Controls may be issued to the IED as Select Before Operate (SBO) (default) and as Direct Operate
commands as defined in the Station Explorer under DNP DO Work Sheet, Operate field
Controls may be issued as TRIP, CLOSE pair with PULSE ON or as LATCH ON, LATCH OFF pair as
defined in the Station Explorer under DNP DO Work Sheet, Trip and Close fields. When a trip action is
pending the type of control as defined in the Trip field will be executed. Likewise a pending close action
will execute the type defined in the Close field. The most common type of control for both Trip and Close
fields is Pulse On. This selection will use the Trip/Pulse On and Close/Pulse On messages. Some
combinations are not included in the pull down menu on the Work Sheet in the Station Explorer, but can
be configured by using the Overwrite selection and placing the correct code in the actual overwrite field.
The codes are listed in the table below.
Note: It is very important to understand exactly what control codes are used for the IED. Some IEDs use
different control codes for different types of points.
Function Control Code Operation
Direct Operate Bit 7 (128) If set, Direct Operate will be used
NUL Trip/Close Bit 6 (64) If set, Trip/Close will not be included in control
Not used Bit 5 (32) Must be 0
Not used Bit 4 (16) Must be 0
Latch Off Bit 3 (8) Un-latches a relay
Latch On Bit 2 (4) Latches a relay
Pulse Off Bit 1 (2) Momentarily opens a normally closed relay
Pulse On Bit 0 (1) Momentarily closes a normally open relay
Table 1.10.4.1-1: Control Codes for DNP
The control code is arrived at by adding the desired functions together.

52
Examples: A Pulse On with Trip and Close designations and Direct Operate would be 1 + 128 = 129.
A Pulse On with no Trip and Close designations would be 1 + 64 = 65.
The default setting in the Station Explorer for the control codes is Trip/Close Pulse On (code 1). This
code will either issue a Trip, Pulse On or Close, Pulse On control depending on the control issued by the
master or the console. Some IEDs require only Pulse On or Pulse Off to be issued and the codes for these
will be 65 and 66.
Processing of Analog Inputs

Two types of Analog Inputs may be defined in the Station Explorer under DNP AI Work Sheet, Align
field. These types are Aligned (or Shifted) and not Aligned (or Normal). The value received from an IED
is stored in the database as it is received and marked as either S or N.
For values marked N the value placed in the master protocol will be altered to fit as many Least
Significant Bits as possible. For example, if a 16 bit value in the database has to be transmitted as a 12 bit
value in the protocol used for master communication, then only the least significant 12 bits will be used.
If the value is larger than 2047 then 2047 will be used and the overflow bit set if applicable. Alternatively,
if a 12 bit value has to be transmitted in a 16 bit message then the maximum value transmitted can only be
2047.
For values marked S the value placed in the master protocol will be altered to fit as many Most
Significant Bits as possible. For example, if a 16 bit value in the database has to be transmitted as a 12 bit
value in the protocol used for master communication, then only the most significant 12 bits will be used
and therefore the value being transmitted will be 16 times smaller than it appears in the database.
Alternatively, if a 12 bit value has to be transmitted in a 16 bit message then the 12 bit value will be
multiplied with 16 for a maximum value of 32752.
Implementation of controls
Controls issued to an IED by a master station will be handled in two stages. A full control sequence must
be received by the Station Controller before the control is passed on to the IED. This will allow for
protocols with different select, execute format to be used for master and IED communication
When receiving a Select command from the master the Station Controller only returns an internally
generated checkback to the Master. No messages are sent to the IED. As the Operate command is
received, the Station Controller will issue a control to the IED. This could be a SBO sequence or a direct
operate command as defined in the mapping table. For SBO sequence commands a Select is sent to the
IED. A valid checkback is expected from the IED before the Operate is sent. The reply of the Operate to
the IED is used as response to the master’s operate command as appropriate for the protocol. If Direct
Operate is defined them this command is issued when the Operate command is received from the master.
Again the reply from the IED is used as a response to the master.
If communication is not available between Station Controller and IED, then the master will be notified in
the response to the Operate command as appropriate for the protocol.
If the IED is processing a previous control and rejects the new control, then the master will be notified in
the response to the Operate command as appropriate for the protocol.
Note that it is not always possible to transfer exact failure information from IED protocol to master
protocol.
53
Control commands from the master with zero operate time duration or no duration defined, will be re-
issued to the IED with a duration defined in parameter “Control Operate Duration” set with “cf”
command (default value = 1 sec).
TRIP and CLOSE will be sent to the same IED point if the master specifies so in its control. If the IED
only supports TRIP and CLOSE on different points then the master must also issue its controls to
different points.
1.10.6 IED with MODBUS

The Station Controller supports IEDs with MODBUS RTU protocol connected through RS-232/ RS-485
serial or MODBUS TCP/IP connected through TCP/IP network connections. Use available
communication ports from 2 to 15 for serial and 16 to 31 for network connections. The assignment of the
communication port defines which of the two types of protocol is used.
The mapping file will specify which registers in the IED are to be polled and the polling rate. It will also
specify which received register will be stored in the Station Controller and where.
For detailed description of the Station Explorer refer to document 74100-SEC
1.10.7 IED with Cooper 2179

The Station Controller supports IEDs with Cooper 2179 protocol connected through RS-232/ RS-485
serial ports. Use available communication ports from 2 to 15 for serial connections.
The mapping file will specify which sequence numbers in the IED are to be polled and the polling rate. It
will also specify where the polled sequence numbers will be stored in the Station Controller.
Event log upload from Cooper Form4C recloser

The Station Controller can be set to monitor the “event data available” status bit from the F4C and inform
the master via status bit. The master is expected to issue a control to initiate a transfer of the data from
F4C to the Station Controller and have it placed in a file. Subsequent request from the master will upload
it to the master via DNP object 70. The format of the file will be according to the information received
from the F4C.
The points mapping for the 2179 protocol allows for mapping the “Event Data Available” status bit from
the F4C (sequence 30 hex bit 5) to a status point being reported to the master. It also allows for mapping
of a control point from the master (SOE Upload Request) to initiate a transfer from the F4C to the Station
Controller as well as a second status bit to the master (SOE Available) to indicate that a file is ready in the
Station controller.
Sequence of actions are as follows:

1) Event(s) has been generated in F4C which sets “Event Data Available” bit.
2) The Station Controller receives the “Event Data Available” bit and transfers it to the master as
mapped.
3) When the master sees the “Event Data Available” status, it will issue a control command to the
associated “SOE Upload Request” DO point.
4) The Station Controller will issue “Retrieve Time-Tagged Information” command to F4C via the
2179 protocol using Function Code 4 and Command 6 “Dump all event records”. All records
54
received will be attached to “TT000” file with no data conversion. “Time-Tagged Record
Format” will be used (Refer to Cooper document R280-90-12). “Event Data Available” bit will
be reset by the F4C after it uploads events.
5) Event data uploading may take a couple seconds. After the data have been appended to the
“TT000” file, the Station Controller will set “SOE Available” bit, indicating to the master that the
file is ready for the next upload step.
6) The master must initiate a request for file transfer of the “TT000” file. When the file “TT000” has
been successfully uploaded to the master, the Station Controller will then erase the file and clear
“SOE Available” bit.
The Station Controller may be connected to multiple F4C reclosers in which case multiple sets of status
and control points must be assigned, each set unique for its F4C. This allows the master to select and
control which F4C to retrieve the file from. However only one file is created in the Station Controller and
only data from the F4C that originally caused the file to be generated can be appended to this file.
Requests for uploads from other F4Cs will be ignored until the file in the Station Controller has been
successfully uploaded to the master and then automatically erased.
For detailed description of the Station Explorer refer to document 74100-SEC.
1.10.8 IED with IEC 870-5-101 Protocol

The Station Controller supports IEDs with IEC 870-5-101 protocol connected through RS-232/ RS-485
serial ports. Use available communication ports between 2 and 15 for serial connections.
The mapping file will specify which IED points (identified by Function, Information and Position) are to
be polled and the polling rate. It will also specify where the polled IED points will be stored in the Station
Controller.
1.10.9 IED with IEC 870-5-103 Protocol

The Station Controller supports IEDs with IEC 870-5-103 protocol connected through RS-232/ RS-485
serial ports. Use available communication ports between 2 and 15 for serial connections.
The mapping file will specify which IED points (identified by Function, Information and Position) are to
be polled and the polling rate. It will also specify where the polled IED points will be stored in the Station
Controller.
1.10.10 IED with SPA BUS Protocol

The Station Controller supports IEDs with SPA-BUS protocol connected through RS-232/ RS-485 serial
ports. Use available communication ports 2 to 15 for serial connections.
The mapping file will specify which IED points (identified by Channel, Data Category and Data Number)
are to be polled and the polling rate. It will also specify where the polled IED points will be stored in the
Station Controller.
55
SPA-BUS protocol is not supported by the Station Explorer. Mapping must be performed by Survalent’s
master station using the IED Wizard.
1.10.11 IED with SEL-Fast Meter Messages Protocol

The Station Controller supports IEDs with SEL-Fast Merter Messages Protocol. The connection is RS-
232 point to point.
In addition when using this protocol the QuickSet Accecelerator could be used.
1.10.12 IED with IEC 61850 Protocol

The Station Controller supports IEDs with IEC 61850 protocol. One of the Ethernet interfaces is used and
the associated port must be configured as client.
1.11 Network Communication Operation

The Station Controller has two Ethernet controllers. The first supports 10/100 BASE TX/FX and is
referred to as the Fast Ethernet controller (FEC). The second supports only 10 BASE T and is referred to
as the Standard Ethernet controller (SEC). The Ethernet controllers have Ethernet addresses assigned at
the factory from the block of addresses allocated to Survalent by IEEE. Each controller has its own
selectable IP address and mask.
The Station Controller application software uses both Ethernet controller and they can be configured
individually. The Monitor is only using the Standard Ethernet controller (10BaseT). Its IP address is set to
the same as the Standard Ethernet controller address in the Station Controller application when it is set.
However, it can be set to its on independent IP address in monsetup command in the Monitor. This
address will be effective until the controller address is again set or changed by the user in the Station
Controller’s application.
The IP address of either controller can be left as 0.0.0.0 if the controller will not be used.
The subnets of the two controllers must not overlap. The subnet for a controller is the range of IP
addresses covered when the 0 bits in the mask are used as do not care bits in the address. For example an
IP address of 192.168.100.1 with a mask of 255.255.255.0 gives a subnet of 192.168.100.0 to
192.168.100.255. Messages with addresses outside this range will not be acted on.
Example: The FEC is set to IP Address “10.0.1.124” and IP Mask “255.255.255.0”. The SEC is then set
to IP Address “10.0.2.124” and IP Mask “255.255.255.0”. All messages to addresses that start with 10.0.1
can be received and will be sent out the FEC port and all messages with addresses that start with 10.0.2
can be received and will be sent out the SEC port.
Gateway address should be set if gateway or router is used in the network. Multiple gateways can be set.
If multiple gateways are specified, the selection of which gateway to be used will start with the
destination address with the tightest mask (255.255.255.255). A destination address and mask entered as
0.0.0.0 and 0.0.0.0 will act as a default address that will be used if no other addresses matches. The
Ethernet port used for the connection to a gateway is determined by the gateway IP address. This address
56
should be on the same subnet as the desired Ethernet port. Continuing with the example above the first 3
numbers of the gateway IP address should be 10.0.1 if the FEC is to be used.
Logical or virtual communication ports (16 to 31) in the Station Controller can be assigned to either
controller. Within this, communication port assignments are made for IP port number and whether it must
act as a client or as a server.
Links between logical communication ports may be set up to create a terminal server function where one
communication port is assigned to the network and the second communication port is assigned to a serial
communication port.
Telnet session can be used to access the maintenance port via the network. The IP address assigned to the
connected Ethernet controller and the port number of 23 must be set up in the remote computer. Various
application programs for Telnet are available for a PC with Windows Operating system including
HyperTerm. Only one Telnet session can be active at any time. Access to the maintenance port is
protected by password. The default name is “RTU” and password is “Scout”. Network Communication
Configuration
The following parameters must be configured.
1.11.1 Network Configuration

First set the IP addresses for both the Ethernet controllers in Network Configuration Editor in mu
command. If the Station Controller is to be connected to a corporate or other multi user network the
address and mask should be assigned by the network administrator
IP Address first byte:
Enter the four address segments in the IP address (0 to 255 each segment).
IP Mask first byte:
Enter the four address segments for the IP mask (0 to 255 each segment).
Gateway address should be set if gateway or router is used in the network. Multiple gateways can be set.
Destination IP Address first byte:
Enter the four address segments in the destination IP address (0 to 255 each segment).
Destination IP Mask first byte:
Enter the four address segments in the destination IP mask (0 to 255 each segment).
Gateway IP Address first byte
Enter the four address segments in the gateway IP address (0 to 255 each segment).
57
1.11.2 Com Port Configuration
The communications port that have been assigned to network in System Configuration Editor or in
Terminal Server Configuration Editor must be set up for protocol, function, port number, Ethernet
controller and various function specific parameters.
Network port set up is done in two parts. The first (general) part includes the parameters that apply to all
ports. The second part includes the parameters that are specific to servers or to clients, selected based on
the configuration in the first part.
General Parameters
IP Protocol (TCP, UDP): (default = TCP)
Select Transmission Control Protocol (TCP) or User Datagram Protocol (UDP). Typically TCP would be
used.
IP Function (Server, Client): (default = Server)
Select server or client function.
If the port is to be used for communication to a master or as the network port in a terminal server
configuration then select server. This setting waits for a client on another computer to talk to it. The
Station Controller is passive; it waits for the connection request.
If the port is to be used as an IED interface then select client. This setting is used to talk to a server on
another computer. The Station Controller initiates the connection.
Local IP Port: (default = 0 = disabled)
Enter the desired port number. Some applications have pre assigned port numbers, such as DNP that
normally is 20000. Entering this number creates a link between the externally used IP port and the
internally used virtual com port. The port number must always be different than 0 for both server and
client function. If client function, use an arbitrary number other than 0.
Local IP Address (Either, Fast, Second): (default = Fast)
Select Either, Fast or Second.
This setting is only applicable if the com port is set as a server. Selecting “Fast” or “Second” will restrict
the com port to one Ethernet controller. Selecting “Either” will allow a TCP connection to be established
through either Ethernet controller as long the message has the proper IP port number.
If set as client the network to be used, FEC or SEC, will be determined by which subnet contains
the destination IP address.
1.11.3 Server Only Parameters

First Remote IP Address 1st byte (0 if not used): 0
58
Enter the four segments of the IP address of the remote device. This is one of three remote (source)
addresses that the Station Controller will receive from, filtering out all other source addresses. If this
address is set to 0 then no filtering of source address will be done and the following two remote addresses
are not checked. This will allow a specific master station to be connected to a specific com port.
Second Remote IP Address 1st byte (0 if not used): 0

Enter value (0 to 255):
Enter the four segments of the IP address of the remote device. This will only be used if the first remote
address is not 0. It is one of three remote (source) addresses that the Station Controller will receive from,
filtering out all other source addresses. If the address is set to 0 then it is not used and the following
remote address is not checked. Entering an address here will allow the two specified master stations to be
connected to one specific com port, typically used with dual redundant masters.
Third Remote IP Address 1st byte: 0

Enter value (0 to 255):
Enter the four segments of the IP address of the remote device. This will only be used if the first and
second remote addresses are not 0. It is one of three remote (source) addresses that the Station Controller
will receive from, filtering out all other source addresses. If the address is set to 0 then it is not used.
Entering an address here will allow three specific master stations to be connected to one specific com
port.
1.11.4 Client Only Parameters

In order to emulate a multi-drop serial connection to a series of IED-s this set up can be used to map a
series of unit addresses (the addresses inside of the messages used to determine the message destination)
to a series of IP addresses. For example if the remote address was set to 192.168.10.15 and the minimum
and maximum destination (Unit) addresses were 1 and 10 then a message with a destination of 5 would be
sent to IP address 192.168.10.19. In addition the unit address inside the message can be replaced by a
fixed value for network devices that use a fixed unit address (Modbus only).
Remote IP Address 1st byte (0 if not used):
Enter the four segments of the IP address of the remote device. This is the IP address of the remote
computer (IED). If there is more than one computer on this port then this is the address of the first
computer (lowest IP address)
Remote IP Port:
Enter the IP port of the remote device. This is the port number on the remote computer (IED) that the
Station Controller wishes to connect to. For MODBUS TCP this port is in most cases 502. For DNP IP
Port 20000 is typically used.
Minimum message destination address: (default = 0)
If there is only one computer (IED) on this port then set this parameter to 0. If there is more than one
computer then set this to the unit address of the first computer (lowest unit address).
Maximum message destination address: (default = 0)
59
If there is only one computer (IED) then set this parameter to 0. If there is more than one computer then
set this to the unit address of the last computer (highest unit address).
Replace destination: (default = No)

Enter value (Y,N):
This determines whether the unit address inside the message will be replaced by a fixed value.
Destination replacement (if required):
If the “Replace destination” option is set to yes then this will be the fixed value that is used to replace the
unit address. Some PML meters require a unit address of 100.
1.12 Terminal Server Configuration Editor

This menu will allow for listing connected ports, adding new connections between ports and deleting a
connection. Only adding connections are described here. Listing and deleting commands are self-
explanatory. Once the link has been set up between two com ports go to Com Port Configuration Editor to
configure each of the selected ports.
Port A Number:
Enter number of first communication port to be connected. Use available communication ports in the 2 to
15 range.
Port B Number:
Enter number of second communication port to be connected. Use ports 16 to 31 for network ports.
Telnet Filter:
Select No for transfer of raw binary data and Yes if Telnet protocol is used for data transfer.
1.13 Web Server

The Station Controller Web Interface duplicates most of the functionality of the Console maintenance
functions.
The Station Controller must have the Ethernet port being used and the web server system options enabled.
The Station Controller supports Internet Explorer 5.5 or above and Netscape 7.0 or above.
All pages except the “Home” page require a log in before they can be viewed. The default password set
up includes only one user with the name “RTU” and password “Scout”. It gives full access to all
functions in the web server and should be changed before the Station Controller is placed in service.
A separate manual exists for the web server with document number 74000-SCW
60
1.14 Programmable Logic Controller
The Programmable Logic Controller (PLC) will accept and execute operation instructions. The
instructions are generated on the IEC 61131 compliant editors found in the OpenPcs application program
and downloaded to the Station Controller either over a serial or network link. The instructions will have
use of the Station Controller’s database points for its inputs and outputs.
Separate manuals exist for OpenPcs and its use with the Station Controller.
1.15 Station Controller Time Sub-System
1.15.1 Time Operation

The Station Controller maintains a real time clock. Upon power-up, the clock is set to 1990-01-01
00:00:00 or to the default date. At this point the time is considered to be invalid. SOE events logged in the
SOE buffer will be tagged with an invalid time flag.
In Station Controllers with 51462 (MPM) hardware issue 5 or higher a battery backed Time of Day clock
will maintain day and time during power down. The date and time from this clock will be used on start up
and the time will be considered for valid.
The time can be adjusted via a time sync from a connected IRIG-B source, from a SNTP server, from the
master station or by setting the time via the console or the web server.
In supporting time sync commands from the master station, the Station Controller maintains a time sync
alarm. After receiving a time sync command from the master, the Station Controller starts a count down
timer. If a new time sync command is not received by the Station Controller, the Station Controller raises
the time sync alarm. The alarm is cleared on the next time sync command. The maximum duration
between time sync commands is specified by the Time Sync Failure Timeout parameter found in the
system configuration editor (cf command). The Timeout will also set the Time Sync Request flag in DNP.
The different sources of setting the time are organised with priority. Top priority is given to the IRIG-B
input, next to the master station time sync and last to the maintenance console/Web server. A lower
priority source will be blocked from setting the time as long as a higher priority source is active and for a
configurable time after it goes inactive. The time source is displayed on the web server or on the console
using the td command.
1.15.2 Time Configuration

Time Sync Correction Factor (ms units): (default = 0)
This number is added to the time received from the master before the clock is updated. This number can
be positive or negative.
Time Sync Failure Timeout (sec units): This is the length of time after a Time Sync command has
been received that a time sync failure alarm will be raised if another time sync command is not received.
61
To monitor the current time, use the time display command (td). To edit the time configuration, use the
menu command (cf) and select the system configuration editor.
1.15.3 IRIG-B
IRIG-B input will be accepted in a demodulated RS485 format on Port 8. Ensure that Port 8 is set for
RS485 and selected to be IRIG in the IRIG-B Configuration Editor. The original IRIG-B protocol does
not supply data on the year. This can be set in the Default Date Editor. An option to use IEEE 1344
allows clock sources with this added feature to set the year as well.
1.15.4 Default Date Editor

The menu is part of the Date and Time editor under the cf console command and will allow for setting a
date to be used when the Station Controller starts up and until a time sync or setting is received. This is
important for getting the correct year when the battery backed time of day clock is not available and the
standard IRIG-B time sync is used. The default date will be updated every midnight.
Year: 2007
Enter the year in full.
Month (1="January", 2="February", 3="March", 4="April", 5="May", 6="June", 7="Ju

ly", 8="August", 9="September", O="October", N="November", D="December"): 4
Enter the month as: 1,2,3,4,5,6,7,8,9,O,N,D
Day: 03
This sets the default date.
1.15.5 IRIG B Configuration Editor

This menu is part of the Date and Time editor under the cf console command and will allow for setting an
offset time to adjust from UTC to local time. The IRIG-B function is enabled using settings for port 8.
IRIG B offset (minute units): This value adjusts the time in minutes from UTC to local time. For
Eastern Standard Time use -300 (-5 Hours).
Enable IEEE 1344: This enables or disables the enhanced features of IEEE 1344 including
information on Year. Do not enable this parameter if the clock does not support IEEE 1344 since it may
produce erroneous results.
1.15.6 SNTP – Simple Network Time Protocol

The time and date of the Station Control can be set using a Simple Network Time –SNTP Server.
SNTP Enabled (Y="Yes", N="No"): Select yes in order to enable this function
62
SNTP Server Address: Enter the I.P address of the server. Gateway must be properly set in order to use
SNTP Backup Server Address (0 = disabled): Enter the I.P address of the backup server or 0.
GMT Offset for Timezone: This value does the time zone correction. The value is in the (-1440 to
1440) range (+24 hours –24 hours).
Time between Syncs: instructs the RTU how often to updated the time.
1.16 Load Profile Configuration

The Load Profile sub-system provides a mechanism to record in a file the values of up to any 12 analog
points with up to 32 bit resolution taken at regular intervals. The recording is restarted if the configuration
is changed and is then continuous from that point on. When the maximum number of configured data sets
is reached the oldest values will be over written. The file can be uploaded at any time and does not affect
the recording.
The duration and “base time” of the interval can be configured. The “base time” is the offset into the
interval that the recordings will be taken. For example an interval of 60 minutes with a base time of 5
minutes will take recordings at 5 minutes past the hour. The base time is only applied to the first
recording. To maintain the base time, intervals can only be either 15, 20 or 30 minutes. If the “base time”
is disabled then the first recording will occur immediately after the configuration has been changed.
The captured values will be recorded with timestamp. If a value is not available at the time of capture a
“blank” indication will be recorded. Recordings that were to happen while the Station Controller was
powered down will also have “blank” indications.
The maximum data sets that can be recorded are 3360 before the oldest data set is over written. This
allows for 35 days of recordings at 15 minutes interval. (60 / 15 * 24 * 35 = 3360). At other intervals the
maximum number of days can be calculated by
days = 3360 / 24 / 60 * N where N is the interval in minutes.
It is recommended only to use the number of data sets required in order to reduce the file size and
therefore the upload time from the Station Controller to the master. The number of data sets required for a
given interval and days of recording can be calculated by
Data sets = 60 / N * 24 * D where N is interval in minutes and D is days.
NOTE: Changing the configuration will restart the recording and previous data will be lost. Ensure that
the file is uploaded before changing the configuration if old data has to be preserved.
Load Profile files can be transferred out of the Station Controller using any of the existing file transfer
methods except xmodem, but including DNP file transfer Object. The Survalent master can upload the
file via DNP, convert and save it into a “.csv” file readable by spreadsheet programs.
63
1.16.1 Load Profile Configuration Editor
This menu will allow for selecting the Load Profile file name, how often to record and which analog point
in the Station Controller to include.
File name: This is the base name of the file in which the values will be recorded; the extension “.SLP”
will be added to this name.
Recording interval: This is the time, in minutes, between recording values. (Min 15, Max 30000)
Enable base time: This turns on and off the base time feature.
Base time: This is the base time in minutes.
Maximum number of data sets: This is the number of recordings that will be taken before the file
”wraps” around and starts to throw away the oldest data. Maximum is 3360 which will hold 35
days of 15 minutes intervals.
Number of points in a data set: This is the number of points that will be recorded. It determines
how many of the following master and point numbers will be used. (0 to 12)
Point n in set, master number: This is the master number (1 to 4) to be used to access the database
or it can be set to 0 to indicate a direct access of the database.
Point n in set, point number: This is the point number in the specified master map or in the
database directly.
1.17 System Errors
1.17.1 General
The software tests and monitors the hardware and software for errors. Error checking is done at power
up, during system operation, and in the background.
Errors are recorded as follows:
1. Incrementing error counters

2. Maintaining the error state of specific devices
3. Displaying error messages on the maintenance terminal
4. Reporting errors to the master station.
1.17.2 Specific System Errors "Momentary Errors"

These errors are typically one-state errors. They happen and then are gone but do not cause a device fail.
(i.e. a parity error.) This type of error will cause an error counter to be incremented each time the error
occurs.
64
Error counters implemented internally in the Station Controller are listed in Table 1.16.2-1: Error Counter
Descriptions.
Error Counter Description

TimeSync Fail The number of times the master did not synchronise the Controller.
Control H/W Err The number of times control failures were detected. The H/W refers to the
Control IED Err hardware control relay system and IED refers to control points associated
with the IEDs connected to the Station Controller .
SetPt IED Err The number of times setpoint control failures were detected with the IEDs
connected to the Station Controller .
Table 1.16.2-1: Error Counter Descriptions
1.17.3 Specific System Errors "Continuous Errors"

These errors are two-state errors. They have a failed state and an operational state. i.e. analog subsystem
failure. The state may be set by the number of momentary errors that happen within a time period, or
other detected error conditions as applicable.
When the device goes into the failed state, a failed message will be printed on the maintenance port, the
current state flag will be set to failed, and a latch type flag will be set to latch the alarm as failed.
The implemented error states are listed in the table below.
Error State Description

MasN SOEBufFull If set to failed, the SOE buffer is over 90% full. N refers to master number.
TimeSync Fail Indicates whether the Controller time is synchronised to the master.
Table 1.16.3-1: Error State Descriptions
1.18 Maintenance Port Operation

The maintenance port (Port 0) allows local terminal access to the Station Controller system and
maintenance functions. The maintenance terminal can be any terminal or terminal emulation that supports
an 80 column or greater display and a communication port setting of:
Baud Rate: 9600

Data Bits: 8
Parity: None
Stop Bits: 1
The optional factory supplied terminal is a laptop PC, configured as above, and supplied with an
appropriate cable.
65
Upon connecting the maintenance terminal with the Station Controller, it will display the maintenance
terminal prompt when the Enter key is pressed.
Port 1 is used for loading mapping files from the Station Explorer and has the same parameter settings as
port 0.
Note that setting the Baud rate on either port 0 or port 1 will change it for both port.
66
2. Start up Configuration
The Station Controller may be shipped with either a default or a custom configuration. The configuration
is contained in various files in the Station Controller. Not all features may be enabled. This depends on
the option password, and therefore not all settings may be possible or be applicable.
When configuring the Station Controller for the first time the following set up sequence is recommended.
Use HyperTerm or similar on a computer and connect to the maintenance port (Port 0) at 9600 Bd, No
parity, 8 data bits using a null modem cable.
Verify proper connection by pressing Enter key. This will produce the prompt: Maint (on-line):
The current configuration can be view by using the pr command. Note that some settings require a reboot
to take effect.
2.1 Download Maps

Mapping files have to be loaded for both hardware and for IED points. These are generated in the Station
Explorer or Survalent’s master and loaded into the Station Controller.
2.1.1 Hardware Mapping

One mapping file is required for each master station connection. If the file is not available then no
hardware data points will be accessible.
2.1.2 IED Mapping

One mapping file is required for each port to make a connection to IEDs. If the file is not available the
IED or IEDs will not be polled for data.
2.2 cf command
This is the System Configuration Editor which has submenus. Not all editors are important when the
Station Controller is first started. Only the critical or mandatory editors are listed here.
2.2.1 System Options Editor

Enter or verify the options password. The list of enabled options can be seen in the process report (pr
command)
1
2.2.2 Masters Editor.
Configure the protocol, com port number, protocol specific parameters per master station.
2.2.3 Com Port Configuration Editor

For serial ports (com 0 to 15) set Baud rate, data bits, parity and control signals and timing.
Suggested settings. These are typical and the actual settings may depend on connected device.
For RS232 connections with modem device enable RTS and CTS and set both timing parameters to 0.
For RS232 with no control signals connected disable RTS and CTS.
For RS485 enable RTS and disable CTS. Set RTS On delay to 50 and RTS Off delay to 0.
For network ports (com 16 to 31) set the IP parameters.
Set the protocol to UDP or TCP. TCP is more common
Set as server or client. Server must be set if the port is connected to a master or is used in a terminal
server link. Client must be set if the port is connected to an IED.
Set the port number. Some functions have pre assigned port numbers. DNP over TCP/IP generally uses
port 20000. This applies to server only.
Local IP Address. Select which Ethernet port to use. Use Fast as first choice. This is applicable to server
setting only. For client setting, the port will be selected depending on the IP address mask setting in
Network Configuration.
Remote IP port. If server, set to 0. If client, set to the port number to be accessed on the connected other
device.
First Remote IP address. If server, set to 0 to allow any other connected device within the subnet to access
this port. Setting an IP address other than 0 will allow only that address to have access to this port. The
second and third remote address can be set similar. Typically all 3 addresses can be set to 0. If client, set
the IP address of the connected other device. The 2 other addresses have no meaning.
2.2.4 Network Configuration Editor.

Set the IP address and mask for both Fast and Second Ethernet controllers. Set the gateway addresses if
required. Obtain addresses from system administrator if on a shared network.
2
3. Station Controller Program Updating
The application program for the Station Controller resides in FLASH memory. This memory is non
volatile and will retain its data without power. It can also be updated by loading new program via either
the serial maintenance port or the second Ethernet port.
The following describes the procedures. A Monitor program in the Station Controller is used for loading
the program and storing it in FLASH memory. The Monitor runs before the Station Controller application
program starts and has the option of not starting the application. The monitor commands are different
from those in the application program
Note: If updating the Station Controller program from version 3.04 or earlier versions, refer to section for
rescaling of Adam data values.
3.1 Using Ethernet (tftp)

The Station Controller will request a file (the application program) to be retrieved from a tftp server.
3.1.1 Preparation
Connect the PC and the Station Controller to the same network. Use an Ethernet crossover cable to
connect the PC directly to the Station Controller or connect both to a hub or switch. Make sure to connect
to the second Ethernet port. Note that the IP address of the second Ethernet port when the Monitor is
active is typically the same as what was set for the same port in the Station Controller application.
However, the IP address used by the Monitor can be set by using the monsetup command at the uMon
prompt. This address will stay in effect until the address of the second Ethernet port is changes in the
Station Controller application at which time they again both will be the same. Connect Station Controller
maintenance port (Port 0) to a terminal emulator (e.g. PC running Hyperterm).
3.1.2 On PC
1. Determine IP address of the PC. Look in the network setup or try “arp –a” on the command line.
2. Start a tftp server (for example Solarwinds’, available at www.solarwinds.net. Ensure that
Transmit and Receive files button is selected in File, Configure, Security).
3. Put Station Controller program binary file in tftp root directory (default for Solarwinds is
c:\TFTP-Root. Files in directory can be verified in Files, Configure, TFTP Root directory).
3.1.3 On Station Controller

1. If monitor has a build date prior to 2003, then include the steps marked with *. The build date is
displayed in the banner of the monitor when the Station Controller restarts. No harm is done if
these extra steps are also performed in monitors built in 2003 or later.
2. *Install a jumper in W2 position 1 on the MPM 51462
1
3. Restart Station Controller.
4. Stop in monitor by hitting s key when given the option.
5. Check that monitor IP address is on the same subnet as the PC. The monitor address is given in
the start up banner. To change the IP address used by the monitor edit the monrc file in the
monitor and restart the Station Controller.
6. *Enter “flash erase 0-11” into the monitor.
7. Enter “loadrtu [IP address of PC] [name of Station Controller binary]” into monitor. For example
“loadrtu 10.0.1.20 74000V402_00.bin”.
8. Wait for program to be downloaded and written.
9. *Remove jumper on W2 position 1.
In version 3.05 or later, an automated reload/programming can be performed by using rl command.

This is useful when the connection to the maintenance port is via a telnet. Please refer to rl command
for more details.
3.2 Using Xmodem

The application program is loaded into the Station Controller on serial communication port. This is not
the recommend method since the transfer of the application file will take very long time. Use tftp option if
at all possible.
Preparation
Connect Station Controller maintenance port to a terminal emulator running on the PC (e.g. Hyperterm).
On Terminal Emulator
2. Stop in monitor by hitting the ‘s’ key when given the option.
3. Enter “mdmldrtu” into monitor.
4. Select “Transfer”, ”Send file” in terminal emulator (using Xmodem)
5. Send program binary file to the Station Controller.
6. Wait for program to be downloaded and written.
Note
The baud rate of the monitor can be increased by using the “mstat –b [rate]” command. For example enter
“mstat –b 57600” into the monitor then increase the rate in the terminal emulator (in hyperterm, go
offline, select properties, hit configure, change the rate, hit ok, hit ok and go back online).
2
4. Station Controller Database Configuration
The Scout and the Hunter controllers each has a different database configuration as describes here in
separate sections
4.1 Scout Database

This section describes the point assignment inside the Scouts database.
4.1.1 Status Points Definition
Scout Status Points Definition

From To Description
0 4127 Complete database (4128 points)
0 255 Status hardware input points (16 boards, 256 points)
256 511 Extended Status hardware input points (16 boards, 256 points)
512 543 Status board status (1 = board is failed)
512 Board #1 - status points 0 to 15
1
From To Description
544 559 Analog board status (1 = board is failed)
544 Board #1 - analog points 0 to 15
560 560 -90% analog reference status for analog points 0 to 127 (1 = point is
failed)
561 561 +90% analog reference status for analog points 0 to 127 (1 = point is
failed)
562 562 -90% analog reference status for analog points 128 to 255 (1 = point is
failed)
563 563 +90% analog reference status for analog points 128 to 255 (1 = point
is failed)
564 564 Reserved for future use (do not use)
567 567 SOE Master #1 queue overflow (1 = queue has overflowed)
571 571 Time sync fail status (1 = point is failed)
572 572 Reserved
573 573 PLC running status
574 604 Reserved
605 605 PLC program loaded
606 636 Reserved
2
From To Description
637 637 PLC run on restart status
638 733 Non-volatile status of controls 129 to 224
734 797 Status of controls 225 to 288
798 861 Dual Momentary Status of controls 289 to 320 (Close/Open Seq)
1000 4095 IED status points
3
4.1.2 Analog Points Definition
Scout Analog Points Definition

From To Description
0 127 Analog hardware input points (8 boards, 128 points)
128 255 Extended Analog hardware input points (8 boards, 128 points)
256 256 -90% analog reference point for analog points 0 to 127 (nom counts:
-1800)
257 257 +90% analog reference point for analog points 0 to 127 (nom counts:
+1800)
258 258 -90% analog reference point for analog points 128 to 255 (nom counts:
-1800)
259 259 +90% analog reference point for analog points 128 to 255 (nom
counts: +1800)
356 371 Adam AO feedback points
372 599 PLC Analog points
600 999 Reserved
1000 4095 IED points
4
4.1.3 Counter Points Definition
Scout Counter Points Definition

From To Description
0 31 Status board error counters
0 Board # 1 - status points 0 to 15
32 47 Analog board error counters
32 Board # 1 - analog points 0 to 15
5
Scout Counter Points Definition
From To Description
48 48 -90% analog reference error counter for analog points 0 to 127
49 49 +90% analog reference error counter for analog points 0 to 127
50 50 -90% analog reference error counter for analog points 128 to 255
51 51 +90% analog reference error counter for analog points 128 to 255
56 56 SOE Master #1 queue overflow error counter
58 58 Master #1 Scanfail error counter
61 61 Time sync fail error counter
63 63 Hardware control failure error counter
64 64 IED control failure error counter
65 65 IED setpoint failure error counter
112 191 Counter points for Accumulators
192 999 Reserved for future use
1000 4095 IED Counter points
6
4.1.4 Control Points Definition
Scout Control Points Definition

From To Description
0 127 Control hardware output points (16 boards, 128 points)
128 128 PLC run on restart (feedback in status point 637)
129 224 Non-volatile controls, feedback in status points 638-733
225 288 Volatile controls, feedback in status points 734-797
289 320 Dual momentary controls, feedback in status points 798-861
(Close/Open sequence)
1000 2047 IED control points
4.1.5 Set Points Definition
Scout Set Points Definition

From To Description
0 99 Non-volatile setpoints
100 399 Volatile setpoints
400 415 Setpoints for Adam AOs
1000 2047 IED setpoints
7
4.2 Hunter Database new
This section describes the point assignment inside the Hunter’s database. Scaling values for analog points
are listed at the end of this section.
Two configurations are available:
 6 Voltage inputs and 6 Current inputs
 3 Voltage inputs and 9Current inputs
4.2.1 6 Voltage and 6 Current configuration
4.2.1.1 Status Points Definition
Hunter Status Points Definition

6 V and 6 C configuration
From To Description
0 31 Status hardware input points (32 points)
32 47 Waveform Capture Events
32 39 Waveform Capture Events (8 points)
40 47 Waveform Capture Events Future (8 points)
48 53 Fault Indicators on F1
48 48 Fault Indicator phase A on F1
49 49 Reserved
50 50 Fault Indicator phase B on F1
51 51 Reserved
52 52 Fault Indicator phase C on F1
53 53 Reserved
54 59 Fault Indicators on F2 (same sequence as F1)
86 91 Voltage Sag and Swell Indicators Bus 1
86 86 Voltage Sag Indicator phase A
87 87 Voltage Swell Indicator phase A
88 88 Voltage Sag Indicator phase B
89 89 Voltage Swell Indicator phase B
90 90 Voltage Sag Indicator phase C
91 91 Voltage Swell Indicator phase C
92 97 Voltage Sag and Swell Indicators Bus 2(same sequence as Bus 1)
98 101 Fault/Loss of Voltage on F1
98 98 Fault/Loss of Voltage phase A on F1
99 99 Fault/Loss of Voltage phase B on F1
100 100 Fault/Loss of Voltage phase C on F1
101 101 Fault/Loss of Voltage neutral on F1
8
From To Description
102 105 Fault/Loss of Voltage on F2 (same sequence as F1)
106 109 Reserved (do not use)
110 111 Fault Indicators for neutral
110 110 Fault Indicator neutral on F1
112 112 Reserved (do not use)
567 999 Miscellaneous internal status
572 572 Reserved
573 573 PLC running status (Undefined if program not loaded)
574 604 Reserved
605 605 PLC program loaded (Undefined if program not loaded)
606 636 Reserved
637 637 PLC run on restart status (Non-volatile point)
864 999 Reserved for PLC
9
4.2.1.2 Analog Points Definition new
Hunter Analog Points Definition

From To Description
0 3 Reference values
0 0 0 % analog reference point for analog points (nom counts: 0)
1 1 Always 0
2 2 10 % analog reference point for analog points (nom counts: +200)
3 3 +90% analog reference point for analog points (nom counts: +1800)
4 7 dc mA inputs (4 points)
8 43 Feeder 1 (F1) values
8 10 Current phases A,B and C on J9 (F1) (Ch 7, 8 and 9)
11 11 Neutral Current of F1
12 14 Voltage phases A, B, C on J11 (F1) (Ch 1, 2 and 3)
15 17 Watt phases A, B and C of F1
18 18 Total Watt of F1
19 21 Var phases A, B and C of F1
22 22 Total Var of F1
23 25 VA phases A, B and C of F1
26 26 Total VA of F1
27 29 Power Factor phases A, B and C of F1
30 30 Average Power Factor of F1
35 35 Frequency phase A on J9 (F1) (Ch 1)
36 38 Max Fault Current phases A, B and on J9 (F1)
40 42 Sag/Swell Voltage phases A, B and C on J11 (Ch 1, 2 and 3)
44 46 Current phases A, B and C on J8 (F2) (Ch 10, 11 and 12)
48 50 Voltage phases A, B, C on J10 (F2) (Ch 4, 5 and 6)
10
From To Description
80 283 Harmonic Distortion Values for 12 channels
80 85 Total Even Harmonic Distortion Channels 1, 7, 2, 8, 3, 9
92 97 Total Odd Harmonic Distortion Channels 1, 7, 2, 8, 3, 9
104 109 2nd Harmonic Distortion Channels 1, 7, 2, 8, 3, 9
116 121 3rd Harmonic Distortion Channels 1, 7, 2, 8, 3, 9
128 133 4th Harmonic Distortion Channels 1, 7, 2, 8, 3, 9
272 277 Total Harmonic Distortion Channels 1, 7, 2, 8, 3, 9
11
4.2.1.3 Counter Points Definition new
Hunter Counter Points Definition

From To Description
0 8 Feeder 1 (F 1) Energy
0 KWHR Import (F1 Total) (Future)
1 KWHR Export (F1 Total) (Future)
2 KWHR Net (F1 Total) (Future)
3 KWHR Total (F1 Total)
4 KVarHR Import (F1 Total) (Future)
5 KVarHR Export (F1 Total) (Future)
6 KVarHR Net (F1 Total) (Future)
7 KvarHR Total (F1 Total)
8 KVAHR Total (F1 Total)
9 KWHR Import (F2 Total) (Future)
10 KWHR Export (F2 Total) (Future)
11 KWHR Net (F2 Total) (Future)
12 KWHR Total (F2 Total)
13 KVarHR Import (F2 Total) (Future)
14 KVarHR Export (F2 Total) (Future)
15 KVarHR Net (F2 Total) (Future)
16 KvarHR Total (F2 Total)
17 KVAHR Total (F2 Total)
56 111 Miscellaneous internal counters
12
4.2.1.4 Control Points Definition new
Hunter Control Points Definition

From To Description
0 7 Control hardware output points (Open/Close sequence)
0 0 Control hardware output point 1 (outputs 1 (OP) and 2 (CL))
4 4 Control hardware output point 5 (outputs 9 (OP) and 10 (CL)) (Exp)
8 19 Reset of fault Indicator points
8 8 Reset phase A on F1 (trip only)
9 9 Reset phase B on F1 (trip only)
10 10 Reset phase C on F1 (trip only)
11 11 Reset all phases on F1 (trip only)
12 15 Reset phases on F2 (same sequence as F1)
16 19 Reserved
20 27 Control hardware output points (Close/Open sequence)
20 20 Control hardware output point 1 (outputs 1 (CL) and 2 (OP))
22 22 Control hardware output point 3 (outputs 5 (CL and 6 (OP))
24 24 Control hardware output point 5 (outputs 9 (CL) and 10 (OP)) (Exp)
28 59 Control hardware output points Matrix’ed 32 points (Close/Open)
13
From To Description
128 287 PLC Controls
321 330 Clear & Erase Waveform Captured Events status points 32-39
321 321 Clear all Waveform Captured Event flags. Command: Trip only. Status
points 32-39 are cleared ‘0’. Event is marked as ‘Read’.
322 329 Clear Waveform Capture Event 1-8. Event is marked as ‘Read’.
330 330 Erase all Waveform Capture Events.
14
4.2.1.5 Set Points Definition
Hunter Set Points Definition

From To Description
0 5 Fault Indicator Thresholds (Non Volatile)
0 2 Fault Indicator Threshold on F1
0 0 Fault Indicator Threshold phase A on F1
1 1 Fault Indicator Threshold phase B on F1
2 2 Fault Indicator Threshold phase C on F1
3 5 Fault Indicator Threshold on F2 (same sequence as F1)
9 9 Fault Indicator Threshold Neutral on F1
12 23 Voltage Sag and Swell Thresholds (Non Volatile)
12 17 Sag and Swell Thresholds on Bus 1
12 12 Sag Threshold phase A on Bus 1
13 13 Sag Threshold phase B on Bus 1
14 14 Sag Threshold phase C on Bus 1
15 15 Swell Threshold phase A on Bus 1
16 16 Swell Threshold phase B on Bus 1
17 17 Swell Threshold phase C on Bus 1
18 23 Sag and Swell Thresholds on Bus 2 (same sequence as Bus 1)
24 25 Loss of Voltage Threshold
24 24 Loss of Voltage Threshold on Bus 1
26 27 Fault Detection time delay for fault indicator & fault/loss of
voltage
26 26 Fault Detection time delay for all phases on F1
28 28 Reserved (Do not use)
29 29 Fault Detection time delay for neutral on F1
32 32 Loss of Voltage time delay on Bus 1
34 34 Minimum Hold time for all fault indicators
35 59 Non-volatile setpoints Reserved for future applications
60 99 Non-volatile setpoints Reserved for PLC
15
4.2.2 3 Voltage and 9 Current configuration
4.2.2.1 Status Points Definition

From To Description
0 31 Status hardware input points (32 points)
32 47 Waveform Capture Events
32 39 Waveform Capture Events (8 points)
40 47 Waveform Capture Events Future (8 points)
48 53 Fault Indicators on F1
48 48 Fault Indicator phase A on F1
49 49 Reserved
50 50 Fault Indicator phase B on F1
51 51 Reserved
52 52 Fault Indicator phase C on F1
53 53 Reserved
66 85 Reserved for future use (fault direction indicators)
86 91 Voltage Sag and Swell Indicators Bus 1
86 86 Voltage Sag Indicator phase A
87 87 Voltage Swell Indicator phase A
88 88 Voltage Sag Indicator phase B
89 89 Voltage Swell Indicator phase B
90 90 Voltage Sag Indicator phase C
91 91 Voltage Swell Indicator phase C
98 101 Fault/Loss of Voltage on F1
98 98 Fault/Loss of Voltage phase A on F1
99 99 Fault/Loss of Voltage phase B on F1
100 100 Fault/Loss of Voltage phase C on F1
101 101 Fault/Loss of Voltage neutral on F1
110 112 Fault Indicators for neutral
567 999 Miscellaneous internal status
16
From To Description
572 572 Reserved
573 573 PLC running status
574 604 Reserved
605 605 PLC program loaded
606 636 Reserved
637 637 PLC run on restart status
863 999 Reserved for PLC
17
4.2.2.2 Analog Points Definition

From To Description
0 3 Reference values
0 0 0 % analog reference point for analog points (nom counts: 0)
1 1 Always 0
2 2 10 % analog reference point for analog points (nom counts: +200)
3 3 +90% analog reference point for analog points (nom counts: +1800)
4 7 dc mA inputs (4 points)
12 14 Voltage phases A, B and C on J11 (F1) (Ch 1, 2 and 3)
36 38 Max Fault Current phases A, B and C on J9 (F1)
48 50 Voltage phases A, B and C on J11 (F2) (Ch 1, 2 and 3) (Same as F1)
71 71 Frequency phase A on J11 (F2) (Ch 1) (same as F1)
18
From To Description
84 86 Voltage phases A, B, C on J11 (F3) (Ch 1, 2 and 3) (Same as F1)
107 107 Frequency phase A on J11 (F3) (Ch 1) (same as F1)
108 110 Max Fault Current phases A, B and C on J9 (F3)
116 319 Harmonic Distortion Values for 12 channels
19
From To Description
20
4.2.2.3 Counter Points Definition new

From To Description
0 0 KWHR Import (F1 Total) (Future)
1 1 KWHR Export (F1 Total) (Future)
2 2 KWHR Net (F1 Total) (Future)
3 3 KWHR Total (F1 Total)
4 4 KVarHR Import (F1 Total) (Future)
5 5 KVarHR Export (F1 Total) (Future)
6 6 KVarHR Net (F1 Total) (Future)
7 7 KvarHR Total (F1 Total)
8 8 KVAHR Total (F1 Total)
56 65 Miscellaneous internal counters
21
From To Description
22
4.2.2.4 Control Points Definition new

From To Description
0 7 Control hardware output points (Open/Close sequence)
8 19 Reset of fault Indicator points
8 8 Reset phase A on F1 (trip only)
9 9 Reset phase B on F1 (trip only)
10 10 Reset phase C on F1 (trip only)
11 11 Reset all phases on F1 (trip only)
20 27 Control hardware output points (Close/Open sequence)
28 59 Control hardware output points Matrix’ed 32 points (Close/Open)
23
From To Description
128 287 PLC Controls
321 330 Clear & Erase Waveform Captured Events status points 32-39
321 321 Clear all Waveform Captured Event flags. Command: Trip only. Status
points 32-39 are cleared ‘0’. Event is marked as ‘Read’.
322 329 Clear Waveform Capture Event 1-8. Event is marked as ‘Read’.
330 330 Erase all Waveform Capture Events.
24
4.2.2.5 Set Points Definition
Hunter Set Points Definition

From To Description
0 8 Fault Indicator Thresholds (Non Volatile)
0 0 Fault Indicator Threshold phase A on F1
1 1 Fault Indicator Threshold phase B on F1
2 2 Fault Indicator Threshold phase C on F1
12 17 Voltage Sag and Swell Thresholds (Non Volatile)
12 12 Sag Threshold phase A
13 13 Sag Threshold phase B
14 14 Sag Threshold phase C
15 15 Swell Threshold phase A
16 16 Swell Threshold phase B
17 17 Swell Threshold phase C
24 25 Loss of Voltage Threshold
26 27 Fault Detection time delay for fault indicator & fault/loss of
voltage
34 34 Minimum Hold time for all fault indicators
35 69 Non-volatile setpoints Reserved for future applications
70 99 Non-volatile setpoints Reserved for PLC
25
4.2.3 Hunter Scaling Values
Point Input Input Range Value Range Notes
Analog DC Current -1mA – +1mA -2000 – +2000
Analog Internal Reference 10% 200
Analog Internal Reference 90% 1800
Analog AC Voltage 0 – 150V rms* 0 – 2000
Analog AC Voltage Sag/Swell 0 – 150V rms* 0 – 2000
Analog AC Current 0 – 10A rms 0 – 2000
Analog AC Fault Current 0 – 20A rms 0 – 2000
Analog Frequency 50 – 60 – 70Hz -2000 – 0 – +2000 60 Hz setting
Analog Frequency 40 – 50 – 60Hz -2000 – 0 – +2000 50 Hz setting
Analog Harmonic distortions 0 – 100% 0 – 1000
Analog Watt – True power -1500 – +1500 W -2000 – +2000 150[V] X 10[A]
Phases @ pf of 1
Analog Watt – True power -4500 – +4500 W -2000 – +2000 150[V] X 10[A] X 3
Total @ pf of 1
Analog VA – Apparent power 0 – 1500 VA 0 –2000 150[V] X 10[A]
Phases
Analog VA – Apparent power 0 – 4500 VA 0 –2000 150[V] X 10[A] X 3
Total
Analog VAR – Reactive power -1500 – 0 -2000 – 0 150[V] X 10[A]
Phases 0 – +1500 VAR 0 – +2000 @ pf of 0
Analog VAR – Reactive power -4500 – 0 -2000 – 0 150[V] X 10[A] X 3
Total 0 – +4500 VAR 0 – +2000 @ pf of 0
Analog Power factor 0 – +1 – 0 0 – +2000 – 0 Indication is valid if
0 – -1 – 0 0 – -2000 – 0 feeder is energized
Analog Temperature 0 – 100 degrees C 500 - 1500 C= Counts*0.1-50
F= Counts*0.18-58
Counter Energy kWh 0.1kWh = 1 count 0 – 4294967295
Counter Energy kVAh 0.1kWh = 1 count 0 – 4294967295
Counter Energy kVARh 0.1kWh = 1 count 0 – 4294967295
Set point AC Fault Current 0 – 20A 0 – 4000 Default threshold 3000
300% of 5A = 15A
Default hysteresis 2A
Set point AC Voltage Sag 0 – 150V* 0 – 1250 Default threshold 800
80% of 120V = 96V
Default hysteresis 5V
Set point AC Voltage Swell 0 – 150V* 0 – 1250 Default threshold 1200
120% of 120V = 144V
Default hysteresis 5V
Set point Loss of Voltage (LOV) 0 – 150V* 0 – 1250 Default threshold 0
Set point Pick up Time Delays 0 – 32000 msec 0 - 32000 Default time delay 0
Set point LOV Time Delay 0 – 32000 msec 0 - 32000 Default time delay 0
Set point FI Min Hold time 0 – 2000 msec 0 - 2000 Default time delay 0
Status Status input 1 = energized
Status Internal status point 1 = condition true
* 150 V for option xx4x; 10 V for option xx6x.
26
5. APPENDICES
5.1 Appendix A: MPM LED and Jumper Designations
MPM LED DESIGNATIONS

DS4 DS1
Port #4 Rx Port #1 Rx
DS4 DS1
Port #4 Tx Port #1 Tx
DS5 DS2 Diagnostic #3 Port #2 Rx
DS6 DS3
DS10 DS7
Diagnostic #2 Port #2 Tx
DS11 DS8 Diagnostic #1 Port #3 Rx
DS12 DS9
DS16 DS13
Run Port #3 Tx
DS17 DS14 SE Link FE Link
DS18 DS15
SE Rx FE Rx
SE Tx FE Tx
DS18 DS15
SE = Second Ethernet Port

FE = Fast Ethernet Port
Port #0 Port #2
10/100
Base TX/FX 10 Base T Port #4
J8 J7
J6 J5 J4
Port #1 Port #3
1
Unit Issues 1 to 3
Unit Issue 4 and up
2
5.2 Appendix B: CASCO LED and Jumper Designations
Unit issues 1 to 3
3
Unit Issue 4 and up
4
5.3 Appendix C: Hunter LED and Jumper Designations
Unit Issue 1 Only

5
6
Unit Issue 2 and Up
5.4 Appendix D: MPM Jumper Settings

The function described for the jumper is true when the jumper is installed
W1: 5 Volt input selector
A-C (J1) 5 Volt supply from J1 connector

B-C (P1) 5 Volt supply from P1 connector (Default)
W2: Software options
1 A-B Watch Dog disabled (Default out)

2 A-B Clear NV RAM (Default out)
3 A-B Clear EEPROM (Default out)
4 A-B Future use (Default out)
W3: Fast Ethernet Controller Filter (issue 4 and up)
A-C Filter to Chassis Gnd (Default)

B-C Filter to Logic Gnd
W4: 10BaseT setup
1 A-B Full Duplex enabled (Default out)

(not used in issue 4 and up)
2 A-B Internal Loopback disabled (Default in)
3 A-B Link Integrity test disabled (Default out)
4 A-B SQE enabled (Default in)
W5: Port 4 half/full duplex mode
A-B Half duplex mode (Default in)
W6: Port 4 2/4 wire mode
A-B 4 wire mode (Default in)
W7: Port 4 2 wire & 4 wire Rx termination (issue 4 and up)
A-B Termination Active (Default out)
W8: Port 4 4 wire Tx termination (issue 4 and up)
A-B Termination Active (Default out)
7
5.5 Appendix E: CASCO Jumper Settings
No. Jumper Number Position Description Default Comments
1 W1 A-B EEPROM write protect. N.E.
2 W2 A-B EEPROM ADDRESS: A0 N.E., Hardwired on PCB
5 W5 A-B USE INTERNAL -15V IN W11 must be out, if IN
6 W6 A-B USE INTERNAL +5V IN W20 must be out, if IN
7 W7 A-C IRQ4 on P1 N.E.
B-C IRQ4 on P2 N.E.
B-C IRQ3 on P2 N.E.
B-C IRQ6 on P2 (Hardwired on PCB) N.E.
B-C IRQ5 on P2 N.E.
11 W11 A-B USE EXTERNAL -15V OUT W5 must be out, if IN
12 W12 A-C RS232/485 Software Configurable IN Port 8 configuration
B-C RS485
NONE RS232
B-C RS485
NONE RS232
B-C RS485
NONE RS232
B-C RS485
NONE RS232
B-C RS485
NONE RS232
B-C RS485
NONE RS232
B-C RS485
NONE RS232
B-C RS485
NONE RS232
20 W20 A-B USE EXTERNAL +5V OUT W6 must be out, if IN
21 W21 NOT USED
22 W22 NOT USED
23 W23 A-B (future) OUT
24 W24 A-B 120 Ohm termination for 485 lines OUT Port 8
8
28 W28 A-B 120 Ohm termination for 485 lines OUT Port12
32 W32 A-C RS485 Line protection to Logic Gnd IN
B-C RS485 Line protection to Chassis Gnd
33 W33 A-C (future) IN
B-C (future)
34 W34 A-B Logic Gnd to Chassis Gnd connection OUT
9
5.6 Appendix F: HUNTER Jumper Settings

1 W1 1-2 Internally supplied Wetting Voltage IN
3-4 Points 0 – 15 (dry contacts) IN
2-3 Externally supplied Wetting Voltage
Points 0 – 15 (wetted contacts)
3-4 Points 16 -31 (dry contacts) IN
Points 16 - 31 (wetted contacts)
4 W4 A-C RS232/485 software configurable IN Port 11 configuration
B-C RS485
NONE RS232
B-C RS485
NONE RS232
B-C RS485
NONE RS232
B-C RS485
NONE RS232
11 W11 A-B (future – not used) OUT
15 W15 1 A-B (future – not used)
2 A-B 6 V & 6 C configuration Out (DS 42) Factory wired
3 V & 9 C configuration In (DS 41)
16 W16 (future – not used)
17 W17 A-C dc input filters to logic Gnd IN
B-C dc input filters to chassis Gnd
Unit Issue 1 Only
10
3-4 Points 0 – 15 (dry contacts) IN
Points 0 – 15 (wetted contacts)
3-4 Points 16 -31 (dry contacts) IN
Points 16 - 31 (wetted contacts)
B-C RS485
NONE RS232
B-C RS485
NONE RS232
B-C RS485
NONE RS232
B-C RS485
NONE RS232
11 W11 A-B (future – not used) OUT
13 W12Ax1 A-C 1 mAmp dc input IN CH 1 to 4
B-C W12A1y for CH1
W12Ax2 A-C IN W12A2y for CH2
B-C W12A3y for CH3
W12Ax3 A-C OUT W12A4y for CH4
B_C OUT Refer to dc analog input
W12Ax4 A-C OUT configuration table for
B-C OUT other input settings
19 W15 1 A-B Fault/Loss of Voltage Option -In Factory wired as
2 A-B 6 V & 6 C configuration- Out (DS 42) required
3 V & 9 C configuration- In (DS 41)
20 W16 (future – not used. All OUT)
21 W17 A-C Temperature sensor IN
B-C Vcc sensor
Unit Issue 2 and Up
11
DC Analog Input Configuration Table
INPUT W12Ax1 W12Ax2 W12Ax3 W12Ax4
* 1 mA A-C A-C OUT OUT
20 mA B-C A-C OUT OUT
1V OUT A-C OUT OUT
5V OUT B-C A-C OUT
10 V OUT OUT B-C OUT
30 V OUT OUT B-C B-C
60 V OUT OUT B-C A-C
x – Denotes Channel Number (1 to 4)
* – Denotes default setting
This table applies to Unit Issue 2 and up.
12
5.7 Appendix G: Communication Cable Connections
5.7.1 RS232 Connections
DTE on DB9 DB25 DCE on

Controller Male Male Modem
RxD 2 3
TxD 3 2
Gnd 5 7
RTS 7 4
CTS 8 5
DCD
1 8
Modem RS232 cable
DTE on DB9 DB9 DB25 DTE on

Controller Male (Female*) (Female*) PC/IED
RxD 2 2 3
TxD 3 3 2
Gnd 5 5 7
RTS 7 7 4
CTS 8 8 5
DCD
1 1 8
Null Modem RS232 cable

DCD is used on ports 2 and 3 only
*Check gender of connector for IED
13
5.7.2 RS485 Connections
DB9 IED
Controller
Male Connector
2 Wire (4 Wire)
+ 4 + Tx/Rx + (Rx + )
- 9 - Tx/Rx - (Rx -)
(Tx +)
(Tx -)
IED 2 wire RS485 cable on ports 8 to 11 or 15
Port 4 IED
Controller
RJ 12 (6) Connector
2 Wire (4 Wire)
+ 4 + Tx/Rx + (Rx + )
- 5 - Tx/Rx - (Rx -)
(Tx +)
(Tx -)
IED 2 wire RS485 cable on port 4
14
Port 4 IED
Controller
RJ 12 (6) Connector
4 Wire
+ Tx 2 Rx +
- Tx 3 Rx -
+ Rx 4 Tx +
- Rx 5 Tx -
IED 4 wire RS485 cable on port 4
15

SC V500 Operation Rev 500

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SC V500 Operation Rev 500

Uploaded by

Copyright:

Available Formats

Document Number: 74000-SCO

STATION CONTROLLER OPERATION

September 22, 2009

Revision 1.00 Initial release for software 74000-01 version 4.02

Survalent Technology Corporation

Station Controller Operation User’s Manual

All rights reserved

Survalent Technology Corporation

TEL (905) 826 5000

FAX (905) 826 7144

Information furnished by Survalent Technology Corporation has been checked carefully

1. Station Controller Operation ....................................................................1

3. Station Controller Program Updating........................................................1

4. Station Controller Database Configuration...............................................1

The Station Explorer II is a support application program for both Controllers

1.1 System Overview

Table 1.1-1 (√) = Available via Telnet Console only

1.2 System Options

The different options available are as follows:

Maintenance Terminal Tip:

1.3 Main Hardware Sub-system Operation

1.3.1 Main Processor Module

Time of Day clock is available in Unit Issue 5 and up.

The MPM has the jumper settings outlined in Appendix C

1.3.2 Control, Analog, Status and Communication Board

1.3.2.1 Control Interface

1.3.2.3 Status Interface

1.3.2.4 Communication Interface

1.4.1 Hardware Operation.

1.4.1.1 Scout Hardware Operation

Status W1 Jumper Position

Put the address of the next board to be scanned on the bus.

1.4.1.3 Hunter Hardware Operation

1.4.1.4 Hunter Status Software Operation

1.4.2 Normal Status

Maintenance Terminal Tip:

1.4.3 SOE Software Operation

• SOE Point Reference

• Multiple SOE Point Ranges

• SOE Time Tag and Debounce

o Hardware Status Points

One Event Reported:

• Normal Status Point vs SOE Point

• Reporting of SOE Data to Master

o For QUICS/QUIN the following applies:

o For DNP the following applies:

1.4.4 SOE Configuration

Master Map for SOE Range : 1

Maintenance Terminal Tip:

1.4.5 Status Accumulator Inputs

1.4.6 Status Accumulator Configuration

First Status Point to be used for H/W Accumulators: 21

Maintenance Terminal Tip:

1.4.6.1 KYZ Accumulator Inputs

Status Pt. A Status Pt. B Action

1.4.6.2 KYZ Accumulator Configuration

First Status Point to be used for KYZ Accumulators: 12

Maintenance Terminal Tip:

1.5 Analog Hardware Sub-system Operation

1.5.1 Scout Analog Hardware Sub-system Operation

1.5.1.1 Scout Analog Hardware Operation

Point numbers in ( ) are for the optional bank 2

1.5.1.2 Scout Analog Software Operation