SSE Training Module 1

SSE
Module 1 Training
1
Contents of Training
Session…
• Overview
• Communication Terminology
• RTU Hardware
• Supporting Hardware
• RTU Software (/Firmware/Middle-ware)
• SSE OPC (different file)
• Comms Orchestrator (different file)
2
Overview
SSE not only pride themselves, in producing excellent products to

highest standards, but also a long term and good after sales service
combined with a help desk and proper client training.
Specialist System Engineering (SSE) started in 1994 specialising in

the design and manufacturing of high speed and other telemetry
products for the military, aerospace and industrial industries.
With our experienced team of hardware and software engineers, who

has been designing high-tech Tele-Control and Process-Control
systems for more than 15 years. SSE prides itself in developing
reliable high-tech Tele-Control, Process Control, Computerised test
systems as well as systems and sub-systems for the military and
aerospace industry.
3
Overview.....
•Water treatment, purification and distribution plants and
networks.
•Electrical generation, distribution, sub-station and mini-sub-
stations.
•Gas distribution networks
•Sewage treatment, purification and distribution plants and
networks
•Irrigation systems
•Metrological systems
•Pollution acquisition and control systems
•Traffic control systems
•Building management systems
•Flood Warning Systems
With Telemetry you can monitor and control anything you can
think off.
4
Overview....
What is Telemetry
Telemetry is the monitoring and or control of remote equipment via a
communication medium.
▪Types of telemetry equipment.

➢RTU ( Remote Terminal Unit )
➢PLC ( Programmable Logic Controller)
➢Remote Alarm Units
➢ETC
5
SCADA
Supervisory Control and Data Acquisition:
Scada software are used to display and manipulate the data from
the RTU, to a level where the data will make sense, to the persons
using the system.
– Mimics - HMI ( Human machine interface )

– Trending
– Alarming
– Reporting
– Archiving
Different types of SCADA

– Adroit
– Factory Link
– Fix De-Max
– In Touch
– Cytec
– Etc. 6
OPC
• OLE (Object Link & Embedding) for Process Control
The reason for OPC and not dedicated drivers at the SCADA is :
• The SCADA developers don’t write drivers for all

the different devices
• Different types of SCADA software can link to one
OPC Server
• The OPC server can run on a different computer
on the network
• From the OPC you can access different types of
databases without going through the SCADA.
7
Protocols
A protocol is the “ language “ used between RTU’s to exchange data . The
package is normally called a word and contain a certain amount of data.
A software driver is the “ Translator “ between two different protocols.

Sample of a protocol word
Address System Data Sign Bit Check Sum
Different types protocol:

– SSE
– Modbus
– Profibus
– IP
– Dnp-3
8
Driver located at OPC
Communicating from OPC
direct to RTU devices
Network Network
SCADA 01 with SCADA 02 with

OPC Server
OPC Client OPC Client
Driver
RTU
Protocol
Protocol
Protocol Protocol
9
Communication
Typical Types
➢RS 232
➢RS 485
➢Radio
➢Dial Up Modem
➢Satellite Phone
➢Fibre Optic
➢Cell Phone
•Dial Up
•SMS ( Short Message Service)
•GPRS ( General Packed Radio System)
•HSCSD ( High Speed Circuit Switch Data )
10
Communication
Serial Interfacing Basics
Major points of serial interfacing
o Three kinds of signals:
➢ Data (RXD, TXD)
➢ Control (RTS, CTS, DCD, DTR, DSR)
➢ Clocks (or timing), is used in synchronous applications (TC, RC, ETC)
oAsynchronous versus synchronous
➢ Async uses start and stop bits to frame every character
Disadvantage: Wastes 20% or more of the available bandwidth,

typically
Advantage: Requires minimal wiring connections between devices
➢ Async is deployed only for low-speed interfaces
➢ Sync uses clock signals so the line receiver knows when to sample the
incoming data
Clock signals are usually implemented as separate wires in a serial
interface, but line coding schemes can be used to encode data and clocks on
the same wires
11
Communication
Serial Interfacing Basics
With few exceptions, serial interfaces are unidirectional
oInputs must connect to outputs; outputs must connect to inputs
DTE and DCE were created to enhance standards so that manufacturers would
implement them in directly compatible ways
oDTE-Data Terminal Equipment
➢ TXD, RTS, DTR, are outputs
➢ RXD, CTS, DCD, DSR are inputs
➢ Usually implemented in a male connector
oDCE-Data Circuit-terminating Equipment
➢ RXD, CTS, DCD, DSR are outputs
➢ TXD, RTS, DTR are inputs
➢ Usually implemented in a female connector
oConnecting DCE to DTE requires a straight cable
➢ “Straight” refers to signals, not necessarily pins
oConnecting DCE to DCE or DTE to DTE requires crossover (or null) cable
12
Communication
Electrical Standards Basics
Electrical interface standards specify the following:
oSignal types and their exact names
➢ Data lines
➢ Control lines
➢ Timing lines
oElectrical specifics
➢ Standards specify voltages, voltage ranges, and thresholds for signal
detection
➢ Standards specify balanced or unbalanced signalling
oMaximum data rate-often, but not always, specified
oMaximum distance-often, but not always, specified
oPinouts
oOther requirements
13
Communication
RS-232
The most common electrical interface for low-speed data
oITU designation V.24, EIA standard 232
oUnbalanced electrical interface-referenced to signal ground lead
➢ Short-range
➢ Low bit rates
oPoor noise immunity, cable capacitance limits distance, unbalanced interface limits
distance
➢ EIA-232 does not specify maximum distance
oPractical for speeds up to 115.2 kbps over very short cables (2m)
➢ Typical application is 19.2 kbps or less over cables up to 15m
oOpen-circuit limits: +3 to 25V, -3 to -25V
➢ The zone between 3V and -3V is defined as undefined in the EIA-232
standard-that is, it is neither zero nor one

oDefined on DB-25, DB-9, and RJ-45 connectors
➢ Often implemented on other connector types and connector blocks as well

14
Communication
EIA-232 EIA-561
DTE
DTE
DB-9 Male Socket 1 2 3 4 5 6 7 8
1 2 3 4 5
DCD
Rx
Tx
DTR
DTE DSR DCE
CTS 6 7 8 9
RTS
RI
GND 8 7 6 5 4 3 2 1
1: Data Carrier Detect (DCD)

2: Receive (Rx)
3: Transmit (Tx)
4: Data Terminal Ready (DTR)
5: Ground/Common (GND)
6: Data Set Ready (DSR)
7: Request To Send (RTS)
8: Clear To Send (CTS)
9: Ring Indicator (RI) 1: Ring Indicator (RI)/Data Set Ready (DSR) Blue
2: Data Carrier Detect (DCD) Orange
3: Data Terminal Ready (DTR) Black
4: Ground/Common (GND) Red
5: Receive (Rx) Green
6: Transmit (Tx) Yellow
7: Clear To Send (CTS) Brown
8: Request To Send (RTS) White
15
Communication
RS-232
TX RX
RX TX
Gnd Gnd
TX RX
RX TX
Gnd Gnd
16
Communication
ADVANTAGES DISADVANTAGES
•Easy to implement /install •Distance max +/- 30 meters

•Versatile communication medium •Point to Point communication
•Global standard ( Not Multi drop )
•Speed Medium •Lightning Damage
17
Communication
RS-485
RS232 RS232 RS 485 RS232

TO
TO
RS485
RS485 RS232
Converter
Converter
RS232 RS232
TO
RS485
Converter
RS232 RS232
TO
RS485
Converter
18
Communication
RS-485
•Easy to implement /install •Distance max 2 Km

•Multi Drop •Speed ( compared to LAN )
•Versatile communication medium •Lightning Damage
•Global standard
•Speed ( compared to Radio )
•Distance ( 0-2 Km )
19
Communication
Optic Fiber
RS232 RS232 Optic RS232

TO
Optic Fiber Fibre TO
Optic Fiber
Converter RS232
Converter
RS232 RS232
TO
Optic Fiber
Converter
RS232 RS232
TO
Optic Fiber
Converter
20
Communication
Optic Fiber
•Multi Drop •Expensive

•Versatile communication medium •Expensive to install
•Global standard
•Speed
•Distance
•Lightning
•Theft
21
Communication
Analog Radio Network
22
Communication
Analog Radio Network
The analog radio will be connected to the FSK Modem port on the RTU
•Distance •Speed ( 1200-2400 Bd)

•Price •PTT Time ( Warm up Time )
•Repair Outlets •Antenna Theft
•Lightning
23
Communication
Digital Radio Network
Digital
Radio RS232
RS232
Digital
Radio
RS232
Digital
Radio
RS232
Digital
Radio
24
Communication
Digital Radio Network
•Distance ( Compared to Wire ) •Speed ( Lower speed with longer

•Speed ( Compared to Analog Radio) distance 1200-19K6 Bd)
•PTT Time •Expensive
•Multi drop •Antenna Theft
•Lightning
25
Communication
Dial Up Land Line Modem Network
RS232
Modem
Modem
RS232
RS232
Modem
Telephone
Network
RS232
Modem
26
Communication
Dial Up Land Line Modem Network
ADVANTAGES
•Distance
DISADVANTAGES
•Speed ( 56K )
•Point to Point communication
•Connection Time
•Expensive
Steps of communication •Cable Theft
•Lightning
•Dial number – ATD 0126634331 •Network ( Telkom)
•Incoming call at RTU – RTU pick line up
•Modems Negotiate baud rate ( +/- 30 sec)
•Switch off FSK and connect
•Go into transport mode
•When finish disconnect ( +/- 15 Sec)
27
Communication
Cell Phone Modem Network
RS232
Cell
Phone Cell
Phone RS232
RS232
Cell Phone Cell
Network Phone
•Vodacom
•Cell C
•MTN
RS232
Cell
Phone
28
Communication
•Distance •Point to Point communication

•Theft •Connection Time
•Versatile •Expensive
•Easy to install •Network Bound
•Multi Function
•Lightning
29
Communication
Dial Up
Exactly the same as the normal dial up modem. ( Max speed 9600 baud)
SMS ( Short Message Service)
Send Protocol message to OPC via service center
Send Read Text message to private persons to indicate alarms.
HSCSD ( High Speed Circuit Switch Data )
With this mode you have a maximum of 4 Channels to upload data and 4
Channels to Download data .
Therefore it is faster than dial up and SMS ( 14K2 baud rate )
GPRS (General Packed Radio System)
Computer is permanently connected to the service provider via a ISDN Line.
You have 4 Download Link and 2 Upload links. ( 500-800 ms @ 14000b /link)
You don’t pay for the time of calls , but for the amount of data transferred.
30
Inside Computer
GPRS Site
SCADA (Highsite)
Adroit OPUS GPRS
OPC-Server
RF
Radio Site
Database
GPRS GPRS Site

(Highsite)
GPRS NETWORK
NOC
SPOORNET
APN
GPRS
SPOORNET NETWORK
Mobile
Workstation
SCADA SCADA SCADA 31

SYSTEM OVERVIEW
View Node 1 View Node 2 View Node 3
Advantages
• No separate-hex-file-scenario for different comms
mediums or protocols. All is in one hex file.
• Processor speed of the RTU is in excess of 10x faster (
Infineon C161 JR).
• Faster IO-bus servicing.
• Add 2 additional RS232 ports or Only FSK
• FSK port input-output is gain and attenuation adjustable.
• Higher current capabilities on the DOT port.
• Multi-configuration inputs on DIN port.
• Multi-configuration connectors on RTU.
• Future Expandability on protocols and software.
• Program memory is stored in FLASH and not NVRAM
(non-volatile). This ensures retaining of program code.
32
RTU Hardware Bus Port
Note- Do not remove
Ribbon Cable when
RTU12 (Top) Power is On
8 x LED display For digital inputs
8 x LED display for digital Outputs

when Switch is pushed in
CD- Carrier Detect – will switch off if Data is

detected. - Red
PTT- Press To Talk- Light will switch on when

the data transmission is in progress - Green
Test –Will pulse every 2 Sec when normal.
33
RTU Hardware
RTU12 (Top)
Battery for RTC and NVM
Processor
SRAM
(Data/Descriptor Memory)
34
RTU Hardware
RTU12 (Top)
Real Time Clock and Battery
X-Bus or Telemetry Bus
Descriptor Save EEPROMs
Analog Circuitry
35
RTU Hardware
RTU12 (Bottom)
RTC Crystal and NVM Switch
Descriptor Save EEPROMs
FLASH
(Program/OS Memory)
X-Bus or Telemetry Bus
36
RTU Hardware RTU12 - Comms
Ports ASC0 and ASC1
ASC0 and ASC1 Fitted
• All serial ports on the RTU are DTE ports,
NO exceptions!
• ASC0 and -1 are EIA-561 compatible
(NOT compliant)
RTU12
ASC0 & ASC1
1 2 3 4 5 6 7 8
1: ASCx_CTRL_IN_1
2: ASCx_CTRL_IN_1
3: ASCx_CTRL_OUT_1
5: ASCx_Rx
6: ASCx_Tx
7: Bootload (ASC0 ONLY, ASC1 Not Used)
8: ASCx_CTRL_OUT_2
37
Communication
EIA-232 EIA-561
DTE
DTE
DB-9 Male Socket 1 2 3 4 5 6 7 8
1 2 3 4 5
DCD
Rx
Tx
DTR
DTE DSR DCE
CTS 6 7 8 9
RTS
RI
8 7 6 5 4 3 2 1
GND
1: Data Carrier Detect (DCD)
2: Receive (Rx)
3: Transmit (Tx)
4: Data Terminal Ready (DTR)
6: Data Set Ready (DSR)
7: Request To Send (RTS)
8: Clear To Send (CTS)
9: Ring Indicator (RI) 1: Ring Indicator (RI)/Data Set Ready (DSR) Blue
2: Data Carrier Detect (DCD) Orange
3: Data Terminal Ready (DTR) Black
4: Ground/Common (GND) Red
5: Receive (Rx) Green
6: Transmit (Tx) Yellow
38
RTU Hardware
RTU12 - Comms Ports ASC0 and ASC1
DCD
EIA-561
Rx
Tx DTE
DTR
DTE DSR DCE 1 2 3 4 5 6 7 8
CTS
RTS
RI
GND
RTU12
ASC0 & ASC1
1 2 3 4 5 6 7 8
8 7 6 5 4 3 2 1
1: ASCx_CTRL_IN_1
2: ASCx_CTRL_IN_1 1: Ring Indicator (RI)/Data Set Ready (DSR) Blue
3: ASCx_CTRL_OUT_1 2: Data Carrier Detect (DCD) Orange
4: Ground/Common (GND) 3: Data Terminal Ready (DTR) Black
5: ASCx_Rx 4: Ground/Common (GND) Red
6: ASCx_Tx 5: Receive (Rx) Green
7: Bootload (ASC0 ONLY, ASC1 Not Used) 6: Transmit (Tx) Yellow
8: ASCx_CTRL_OUT_2
39
RTU Hardware
Flow Control Selections
40
RTU Hardware
JP20: ASCx_CTRL_IN_1
JP21: ASCx_CTRL_OUT_1
JP22: ASCx_CTRL_IN_2
JP23: ASCx_CTRL_OUT_2
• Jumper position connects the relevant control line

(input/output) to a specific serial port (ASC0/-1)
• 2 and 3 Linked: ASC0
• 1 and 2 Linked: ASC1
• Either ASC0 or ASC1, cannot share the pins!
• Supported Flow Control:
• CTRL_IN_1: CTS (DNP3.0 Tshwane Electrical)
• CTRL_OUT_2: RTS (DNP3.0 Tshwane Electrical)
• CTRL_OUT_1: Hart® Protocol/Mitsubishi (CO)
• CTRL_IN_2: CD for MDS Radio
• CTRL_IN_1: CD for GPRS (cannot be CTRL_IN_2 as
MDS will be used in conjunction with GPRS)
41
RTU Hardware
• When RS232 Module fitted, ASC2/-3 have
proprietary pin-outs on the DB-9
42
RTU12 RS232 Module
• This module may NOT be removed

from, or inserted into the RTU
while power is applied to the
RTU!!!
• This module expands the serial
ports on the RTU12 to two
additional independent serial ports
(ASC2 and -3)
• Shared pins in the DB9 on the
RTU12 base board is used for the
relevant Tx, Rx and GND signals
ONLY
• NO FLOW CONTROL SIGNALS
ARE AVAILABLE!!!
43
RTU Hardware
RTU12 - Comms Connections
DTE - DTE DTE - DCE DTE – DCE (Full Flow Control)
DB-9 Male or Female DB-9 Male or Female DB-9 Male or Female

1 2 3 4 5 1 2 3 4 5 1 2 3 4 5
6 7 8 9 6 7 8 9 6 7 8 9
1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8
RJ45 Socket RJ45 Socket RJ45 Socket
44
RTU Hardware
RTU12 - Comms Ports FSK
• When FSK Module fitted, pin-outs are the
same as for the RTU3, -10 and -11
RTU12
FSK
DB-9 Male Socket
1 2 3 4 5
6 7 8 9
1: V+ Supply
2: V+ Supply
3: Squelch
4: Press-To-Talk/Transmit (PTT)
5: Tx to Radio
8: Band Pass Test
9: Rx from Radio
45
RTU12 FSK Module
• This module may NOT be removed from, or

inserted into the RTU while power is applied
to the RTU!!!
• Data rate of ONLY 1K2 is supported
• ERROR on the silk legend, DCD and CD is
swapped!
• The same setup for the RTU10/11 matching to
the relevant radio is still prevalent here, the
FSK Module MUST be matched/paired with a
specific radio
46
RTU12 FSK Module
Radio Gain
Pots set audio Gain and
attenuate
Top - Transmit
Bottom – Receive
Setting are sensitive with

radio types.
CD/DCD
2&3 (Default) Data
Carrier Detect
1&2 Carrier Detect
47
RTU Hardware
RTU12 - IO Connections
General
The RTU12 is available in two connector types for field interfacing:

• 10-Way screw terminal, for direct interfacing to the field wiring; and
• 14-Way ribbon cable interface that connects to field wiring interface modules for the field wiring. This saves a
huge amount of space in the cabinet due to the physical size of the ribbon cables.
For clarity sake all IO wiring interface connections discussed here are with reference to the 10 -Way screw terminal
connectors, although the 14-Way connectors are shown.
48
RTU Hardware
Ethernet (EIA-T-568)
•As mentioned earlier, a variant of the RTU12 allows Ethernet connectivity.
•The RTU12 with Ethernet is used to allow the RTU12 to communicate on an Ethernet network via the ASC1 port. This will
allow the RTU12 to be installed onto existing or new Ethernet backbones/networks and communicate its data to the SSE
OPC.
•In order to provide extra communications ability to the RTU12, it is possible to add a communication Module to the RTU12.
•This will allow the user even more communication flexibility.
•For the RTU12 Ethernet (X-Port) connections (via cable), ensure that a twisted cable is used for direct PC connection and a
straight cable is used when connected to a hub/switch
•Connection to a wireless hub/switch is via a straight cable
49
RTU Hardware
T-568A Straight T-568B Straight
50
RTU Hardware
T-568 Crossover
51
RTU Hardware
RTU12 - IO Connections Layout
AIN - Analogue Inputs
DIN – Digital/Binary Inputs
DOT – Digital/Binary Outputs
52
RTU Hardware
DOT
DOT – Digital/Binary Outputs
• Open-Drain outputs (no drive capability,

current sinking)
53
RTU Hardware
DOT Connections (indicative only)
54
RTU Hardware
DIN
DIN – Digital/Binary Inputs
• Optically isolated inputs, active low (0V)

inputs
• Active high (field voltage) inputs can be
supplied on special request
• Can be software configured to Counter
Inputs
55
RTU Hardware
DIN – Active Low/High
Opto-Isolator type determine if the RTU can
be only active low or both
Active Low/High Selection Jumpers

• JP11 Lower DIN selection (DIN1 - DIN4)
• JP12 Upper DIN selection (DIN5 – DIN8)
• 1-2 Linked: Active Low (0V)

• 2-3 Linked: Active High (field voltage)
56
RTU Hardware
DIN – Active Low/High
Opto-Isolator type determine if the RTU can
be only active low or both
Active Low/High Selection Jumpers

• JP11 Lower DIN selection (DIN1 - DIN4)
• JP12 Upper DIN selection (DIN5 – DIN8)
• 1-2 Linked: Active Low (0V)

• 2-3 Linked: Active High (field voltage)
RTUs are shipped by default as Active Low

inputs!
DO NOT CHANGE THIS JUMPER SETTING

UNLESS RTU IS ORDERED AS ACTIVE
HIGH!!!
57
RTU Hardware
DIN Connections (Indicative Only)
Active Low
RTU12
V-MINUS
DIN8
DIN7
DIN6
JMP- LINKS
3 DIN5
2 1 Supply PSU
V-PLUS
DIN4
IK
DIN3
DIN2
DIN1
58
RTU Hardware
DIN Connections (Indicative Only)
Active High
59
RTU Hardware
Layout
AIN - Analogue Inputs
• All AINs are 4-20mA inputs
• NO VOLTAGE INPUTS!
Scaling
4mA = 0m = 0%
20mA = 10m =100%
V = I*R
Vmin = 0.004 * 120 = 0.48v
Vmax = 0.020 * 120 = 2.40v
12 Bit A/D = 4095
( 0.48 * 4095) / 2.5 = 786

( 2.40 * 4095) / 2.5 = 3932
4mA = 786
20mA = 3932
60
RTU Hardware
AIN Connections (Indicative Only)
GND
120 R V2 = 2.4V
A/D AIN8 Loop Powered Instrument
Converter R2
4- 20 mA
120 R AIN7
12 Bit
AIN6
0.0 - 2.5 Volt

AIN5 12 / 24V
GND
AIN4 Self Powered Instrument
+
AIN3 Galvanic External
4- 20 mA
Voltage Input Isolator - Supply
AIN2
V1 = I * R1
R1= V1 / I R1
AIN1
R1 = 13.8 V / 20mA 690 R V1 = 13.8V
DC Voltage Input (13.8 v)
R1 = 690 Ohm
61
RTU Hardware
RTU12 - Decimal Values
10000 1000 100 10 1 0.1 0.01 0.001
0 4 2 3 1 4 0 0 4231.4
7 0 5 0 0 0 7 0 70500.07
0 0 0 0 0 0 0 4 0.004
62
RTU Hardwar
RTU12 – Binary Values
Representation
A binary number can be represented by any sequence of bits (binary digits), which in turn may be
represented by any mechanism capable of being in two mutually exclusive states.
12 bits
Byte
2048 1024 512 256 128 64 32 16 8 4 2 1
0 0 0 0 0 0 0 0 0 0 0 1 1
0 0 0 0 0 0 0 0 0 0 1 0 2
0 0 0 0 0 0 0 0 0 0 1 1 3
0 0 0 0 0 0 0 0 0 1 0 0 4
0 0 0 0 0 0 0 0 0 1 0 1 5
0 0 0 0 0 0 0 0 0 1 1 0 6
0 0 0 0 0 0 0 0 0 1 1 1 7
0 0 0 0 0 0 0 0 1 0 0 0 8
0 0 0 0 1 1 1 1 1 1 1 1 255
1 0 1 0 1 0 1 0 1 0 1 0 2730
1 1 1 1 1 1 1 1 1 1 1 1 4095
63
Supporting Hardware
Hardware complementing the IO of the RTU except CO devices:
• Multi-IO Card
• 24-Channel DIN Card
• 24-Channel DOT Card
• AOT Card
• MUX232 Card
• 2MXP Memory Expansion Card
• RS232 Isolator
• EEPROM Memory Module
• FFSK Modem
• Jordan Modem
• BBR08
• BBDI8
• BBSI8
• BBCV8
64
Supporting Hardware:
Card Addressing
Device Card Start Address IO Start Address DIP Switch Indication
RTU 0 0 None
Multi-IO 1 9
24-Ch DOT 0 (9)
24-Ch DIN 0 (9)
AOT 1 9
MUX232 0 NA
(MXP2M) 2MXP 0 NA
65
Multi-IO Card
• Configuration “111” shown, all IO types

populated, this is now the defacto
standard
• Note address on the DIP switch
• Connectors either 10-way or 14-way
• All relevant connections are the same
as that of the RTU12
• DOTs are open Drain outputs (needs
pull-up, sink to ground)
• By default DINs are active low input
• All DINs are selected as either active
low/high (same hardware rules as
RTU12)
66
24-Channel DIN Card

• All DIN connections are the same as
that of the RTU12
• By default DINs are active low input
• DINs are selected in groups of 8 as
either active low/high (same hardware
rules as RTU12)
67
24-Channel DOT Card

• All DOT connections are the same as
that of the RTU12
• DOTs are open Drain outputs (needs
pull-up, sink to ground)
68
AOT Card

• AOTs are NOT current sourcing, but
current SINKING!!!!!!!!!!!!!
• Can be ordered with or without
lightning protection
• 8 x LED display to indicate the status of
the outputs on the module
• Note that the LED will only light up if
the output value is bigger than half
scale or 12 mA
• Minimum supply voltage 18V DC
69
AOT Card
IO Connections
AIN Output Connections
D/A 4-20 mA
Anl Out 011 LCD
Converter
DISPLAY
12 Bit Anl Out 022
+
Anl Out 033 Galvanic
Loop 4-20 mA Valve
0.0 - 2.5 Volt Isolator -
Anl Out 044
Grnd 0V 5
Grnd 0V 6
+ 24 V 7
Grnd 0 V 8 24V 0V
Grnd 0V 9
Grnd 0V 10
70
2MXP Memory
Expansion Card
• A total of 2MB of Non-Volatile Memory
per card
• RTU supports up to 6-cards (12MB)
• LEDs indicate Read and Write status per
bank of 512KB
• Note the address on the DIP switch
71
RS232 Isolator
• Establishes a galvanic
isolation between two devices
connected via RS232
WITHOUT any flow control
(Tx, Rx and GND ONLY)
• The data directions shown on
the module is with respect to
the module, ie Tx is out of the
module, Rx is into the
module, for both ports
• Maximum baud rate of
115200bps
• This is NOT a repeater
72
RS232 Isolator
Connections
• The MUX232 card is neither a DTE nor a

DCE device
• The legend on the PCB indicates the
actual data direction with respect to the
card
Gnd
Rxa Txa
Data Out From Device
Txb
Data In To Device
Gnd
Rxb
Common (GND) Device
-
System Power Supply -
1 2 3 4 5 6 7 8
+
System Power Supply +
3000V Galvanic
Isolation
RTU12
73
FFSK Modem
• DCE device
• This is a transparent modem that can
be setup/configured via a terminal
interface
• Connection to radio is the same as
that for the RTU10/11/12 FSK port to
radio connection, maximum data rate
is 1K2
• As with the FSK Module and
RTU10/11/12, the FSK Modem MUST
be matched/paired with a specific
radio
• The FSK Modem handles zero
insertion and deletion of data
• Controls the radio without the
attached device needing to perform
any of these functions
• The tactile switch on the side of the
modem serves absolutely no
function!
74
MUX232 Card
• Used ONLY in Comms Orchestrator

applications
• Although 9-ports are present on the
card, only 7-ports (maximum per card)
can be used as additional ports
• The first port connects to the relevant
RTU port (ASC0-3)
• The last port (port 8) is reserved for
possible future expansion to additional
MUX232 cards
• Note the address on the DIP switch
75
MUX232 Card
Connections
• The MUX232 card is neither a DTE nor a

DCE device
• The legend on the PCB indicates the
actual data direction with respect to the
TX1
TX2
RX1
RX2
G1
G2
TX
RX
G
card
1 2 3 4 5 6 7 8
Data Out Device1
Data In Device1
Common (GND) Device1

RJ45 Socket
Data Out Device2
Data In Device2
Common (GND) Device2

76
Jordan Modem
(V2)
• Based on the microRTU V2 mother board

• DCE device
• Note: Retaining screws for fixing the
modem to the carrier board MUST be fitted
as the screws add to the ground plane of
the modem and is essential for the modem
to operate correctly (present here)
77
Jordan Modem
Modem Modules
GR64 (V1 shown, V2 Green PCB) GR47 Telit GE864-QUAD
78
Jordan Modem
GPRS
General:
• Network reset and connection must be done by the RTU via the configuration strings
• Only the “new driver (Advanced)” can be used
• Physical connection between the RTU and the modem can be found in the RTU Firmware Release Notes
• All SIM cards used in system MUST have fixed static IP addresses
• The SSE GPRS Driver for the RTU is for the SSE Jordan GR47/64 modems and modules ONLY!
• GPRS connections can ONLY be made from either ASC0 or ASC1, NOT ASC2 nor ASC3 (flow control)
79
BBR08
Relay Output Interface Card
8 Channel
• Ribbon cable interface
to the RTU
• Relay contact rating is
10A
• Voltage free contact
• NC (Normally Closed)
connection is used for
JORDAN GPRS power
• Connector P1 is used to
supply power to the
relay card
• Pin A 12V dc
• Pin B GND
• LED Indicate the relay
that is active
80
BBDI8
Analog and Digital Input
Module 8 Channel
Digital Input
• Ribbon cable interface to the RTU

• Connector P1 is used to supply power to the module
depending on the application used
• Digital Inputs with common also surge protected
• Pin A 12V dc
• Pin B GND
• Pin C GND
• Pin D Not Connected
• Digital Input without surge protection
• Pin A 12V DC
• Pin B GND
• Pin C Not Connected
• Pin D GND
• The above example is for negative switch on the RTU
• Refer to the input wiring of the RTU as it will be the
same
81
BBDI4
Analog and Digital Input
Module 4 Channel
Analog Input

• Connector P1 is used to supply power to the module
depending on the application used
• Analog Inputs with common 12V on surge protected
• Pin A GND
• Pin B GND
• Pin C 12V
• This is used to make the wiring easier for field
wiring to instruments
• Analog Input with common 24V on surge protection
• Pin A GND
• Pin B GND
• Pin C 24V
• Refer to the input wiring of the RTU as it will be the
same
82
BBSI8
Analog Input Module 8
Channel
Analog Input

• Connector P1 is used to supply power to the module depending on the application used
• Analog Inputs with common 12V on surge protected
• Pin A 12V
• Pin B GND
• Refer to the input wiring of the RTU as it will be the same
83
BBSI8
Analog Input Module 8 Channel
Base Board
Analog Input

• Connector P1 is used to supply power to
the module depending on the
application used
• Analog Inputs with common 12V on
surge protected
• Pin A 12V
• Pin B GND
• Refer to the input wiring of the RTU as it
will be the same
84
GPRS Network
GPRS B-MON
Modem VSWR
High Site Audio

LCD
RTU
K-Pad Repeater E&M
LBU
Audio
Site Temp Site Link
PSU Sensor Battery Radio E&M
85
BBSI
Audio Board
• The module is designed to measure Audio
signals.
• And Convert it to signal that the RTU can
read on the Analog Inputs
86
BBSI
Audio Board
• The module is designed to measure Audio
signals between the LBU and the radio
equipment
• Convert Audio signals into logarithmic
scale in dBm for measurement
87
BBSI
Audio Board
88
BBSI
0 to 10 Volt Input Module
This board is mounted in the BBSI base Board
• It is possible to adjust the gain of the modules when the DIP switches is
populated with the different resistor values
• Typical jumper settings
• J1 Pin 2,3
• J2 Pin 2,3
• J3 Pin 2,3
• J4 Pin 2,3
• Fixed amplification on the board in the system used
89
BBSI
0 to 10 Volt Input Module
90
BBCV8
Analog, Digital Input Output
Module 8 Channel

• Connector P1 is used to supply power to the
module depending on the application used
• Digital Inputs
• Pin A 12V dc
• Pin B GND
• Refer to the input wiring of the RTU as it will be
the same
• Inputs 1 to 8 will be wired directly on the 8
terminals of the module
91
12 TO 24 Volt Converter
Step up converter
• The converter is used to step up the

voltage for the use in loop powered
instrumentation loops
• The output mili Amps is limited to
100mA
• The unit is supplied with surge
protection
92
Instrument Single
Channel Surge Module
• The converter is used to protect instrumentation loops at

the Instrument in the field
• The top part of the unit is the side the Instrument will be
connected
• The bottom part of the unit is the side that will be
connected to the field wiring or cabling
• Make sure that the centre pin is connected to a good
earth
93
LOOK @ Display
• The display is a intelligent unit

• The interface to the RTU is via a RS 232 serial
communication
• The unit is used to display analog or digital information
connected to the RTU
• Can display 4 different values in its own line
94
SAM
• The SAM display hardware comprises a 4-line by 20-
character alpha-numeric ASCII liquid crystal display (LCD)
which is controlled by a dedicated key panel
• SAM is used to interrogate the RTU for all the relevant IO
connected to the RTU
• Physical and other intelligent device information
The System Analysing Mechanism or SAM Menu lets you

build your own hierarchical menu structure. The SAM menu
system can display complete menu structures containing data
and output control information and execution. In addition to this
a configuration management feature by means of embedded
documentation is implemented to ensure the user can add
complete build-states of the station/system or any other
documentation related data.
95
Antenna Installation
X- Meters
X- Meters
10mm Copper
70mm Copper
RTU
Earth Spike
Earth Bar
2 Meters 2 Meters 96
RTU Software
• Operating System (OS)

• RTU Data Tables (Database)
97
RTU Software
Important Notes:
• THE CORRECT FIRMWARE MUST BE LOADED ON THE CORRECT TYPE OF RTU!

• Firmware identification:
• RTU12: RTU12-x.x.x
• When released all versions are zipped into a single file marked RTUx-x.x.x
• Version identification: RTU12-4.1.0
• 4: Major version – happens seldom, extremely big change or new technology
• 1: Minor version – new features or major bug fixes, will also happen when Build number
exceeds 63
• 0: Build – this will be seen most, any bug fixes, improvements or new features
• A Watchdog Timer (WDT) will recover the CPU when an endless loop is entered
• Undefined memory jumps are NOT catered for by the CPU
• ALL hardware CPU peripherals are interrupt driven
98
Operating System (OS)
Initialisation
The most important step in the RTU firmware
• Detect RTU Type
• Check firmware version between Firmware (FLASH) and EEPROM (previous firmware version)
• Initialise all descriptor tables (internal database) from either SRAM or EEPROM
• Reset task lists (possible pending tasks)
• Detect all communications ports baud rates
• Upon successful initialisation, print “welcome” message on screen containing RTU address, System
address, RTU type and firmware version and all ports configured baud rates and the relevant
communications modules fitted ( RS232 or FSK Modules)
Timer (Concurrent Process)

All IO processes are kicked-off here
• 50ms Resolution on Descriptor processing (DIN, AIN and FIN)
• 10ms Resolution on On-Change Logger Descriptor processing (DIN and CIN)
• SAM IO status updating
• Rx/Tx Time-outs/Dead Times
• Complete FFSK Engine control
• Descriptor Saving control Engine
• Comms Orchestrator Control/Time-outs
• 1 Second Process Loop Time-out control
99
Communications Orchestrator
All CO Protocols and general receiving is handled here
• CO Slave Protocol Detection
1. Modbus RTU Slave
2. Modbus ASCII Slave
3. Special DNP (SSE Expansion Implementation)
4. DNP 3.0 Slave
5. IEC60870-101 Slave
6. Hex Driver
7. Tait Driver
• SSE Protocol
• CO Master Protocol Handling
• ASCII Protocol Handling (Modem Responses – Dial and SMS mostly)
IO Scanning
All hardware (physical IOs) and software (Descriptor) IOs are maintained here
• Hardware IOs:
• Hardware IOs are scanned “live”
• All DINs and CPU AINs are updated on every main loop iteration
• All CINs are updated when the DINs are updated
• Expansion AINs are updated consecutively, starting from AIN1 in the first main loop iteration. The next loop
will update AIN2 and so on.
• DIN/DOT LED status updates
• Software IOs:
• FIN-, AIN- and DIN-descriptors are scanned according to the settings in the OPC and via the triggers from
the Timer loop
• IO Eventing, Alarming etc. are maintained from here
• The Task List is accessed from here
• On-Change CIN/DIN Logging
• Rx IO Mapping
100
1 Second
All state machines and iterative engines are maintained here
• AIN Alarms
• FIN Alarms
• CIN Descriptor Processing
• Local IO Mapping
• P-Code
• Dial Modem Drivers
• SMS Modem Drivers
• GPRS Drivers
• Periodic Logging (1 second resolution)
• AIN/FIN On-Change Logging (1 second resolution)
• Descriptor Saving and Refreshing
• Task List
• Test LED
Comms TX Special
All Flow control Txing maintained here
NOTE: THIS IS ONLY APPLICABLE ON FSK, ASC0 AND ASC1 PORTS!
• CD (FFSK and MDS)

• Soft CD
• RTS/CTS
101
Descriptor Save
All Descriptor saving done from here
• Periodic Descriptor update (read from EEPROM)
• Continuous monitoring of Descriptor change for saving
• State machine maintained from the Timer Loop
102
103
RTU Data Tables
(Database)
Things to remember…
• All registers in the RTU low level tables are only registers in memory unless they are coupled to actual
hardware IOs from the OPC configuration
• All registers/data types/register types can be used in P-Code EXCEPT FINs!
• Low level tables are updated faster than Descriptor-coupled IOs
104
RTU Data Tables (Database)
AIN FIN DIN CIN AOT DOT DREG AREG
1 1 1 1 1 1 1 1
2 2 2 2 2 2 2 2
3 3 3 3 3 3 3 3
4 4 4 4 4 4 4 4
5 5 5 5 5 5 5 5
6 6 6 6 6 6 6 6
7 7 7 7 7 7 7 7
8 8 8 8 8 8 8 8
9 9 9 9 9 9 9 9
10 10 10 10 10 10 10 10
… … … … … … … …
… … … … … … … …
254 64 254 254 254 254 254 254
105
RTU Data Tables
(Database)
106
1 1 1 1 1 1 1 1
2 2 2 2 2 2 2 2
3 3 3 3 3 3 3 3
4 4 4 4 4 4 4 4
5 5 5 5 5 5 5 5
6 6 6 6 6 6 6 6
7 7 7 7 7 7 7 7
8 8 8 8 8 8 8 8
9 9 9 9 9 9 9 9
10 10 10 10 10 10 10 10
… … … … … … … …
… … … … … … … …
254 64 254 254 254 254 254 254
107
RTU Data Tables
(Database)
108
1 1 1 1 1 1 1 1
2 2 2 2 2 2 2 2
3 3 3 3 3 3 3 3
4 4 4 4 4 4 4 4
5 5 5 5 5 5 5 5
6 6 6 6 6 6 6 6
7 7 7 7 7 7 7 7
8 8 8 8 8 8 8 8
9 9 9 9 9 9 9 9
10 10 10 10 10 10 10 10
… … … … … … … …
… … … … … … … …
254 64 254 254 254 254 254 254
109
RTU Descriptor Tables
General:
• All Input Data Types have Descriptors (AINs, DINs, FINs, CINs)
• NO Output Data Types have Descriptors (DOTs, AOTs)
• NO Register Data Types have Descriptors (AREGs, DREGs)
• All Input Data Types are Event enabled EXCEPT CINs
• ONLY AINs and DINs have SMS Messaging capabilities (AINs x16, DINs x64)
• CINs are ONLY updated from the physically declared DIN cards (hardware)
110
SSE OPC
111
NOC Computer
ADROIT SCADA
OPC-Client Opus
Reporting
Config Toolbox & Comms Server
OPC-Server
Config Data-
Toolbox Data Centre Base
Handler Historical
Database
Protocol Drivers
GPRS Network.
112
SSE OPC
Overall…
• This course does not cover the link of tags or other data objects to SCADA etc. etc…
• This is purely a OPC focused course
• The SSE OPC is LICENCED software!
113
SSE OPC
Channels
• Communication settings in a channel is persistent to ALL devices configured in that specific channel
• The more devices you have per channel, the slower the OPC becomes
• It is considered good practice in SSE to start the OPC address from 254 downwards (not set in stone)
• Addresses 0 and 255 are reserved and MAY NOT BE USED! AT ALL!!!!!
• The Enabled tick-box in the Addresses and Port Settings and the Modem Timers & Settings tabs
work in unison
• There is a maximum of 10 channels ONLY, this cannot be expanded due to the impact on processing speed
and the complexity of the system
114
SSE OPC
Channels: Addresses & Port Settings
• OPC always generates a new Channel with default values to ensure DIRECT communication to a NEW (fresh)
RTU, the user must change the configuration according to the required system
• Mediums
• None: No use at all
• RTU: When RTU is used as a FSK modem
• FSK Modem: The physical communication to the modem differs to that of the RTU
• Modem: Yes, a dial-up modem
• SMS: Note, this is SSE Protocol via SMS
• Trunk: Never been used
• TCP/IP Server: The OPC is the connection server
• TCP/IP Client: The OPC is the client that connects to (a) server(s)
• Be sure that the communication settings are correct for the relevant communication mediums shown above
• Ack Enabled should be UNTICKED if an RTU is used as a FSK modem, failure to do this will result in double
acknowledges (one from the RTU and one from the OPC)
115
SSE OPC
Channels: Addresses & Port Settings
• Comms Service Interval is the rate at which the OPC service the PC comm port receiver buffer to monitor if
new data is received or not
• Base RTU Comms Interval is the rate at which the OPC polls a RTU utilised as a FSK modem to monitor if
data is received via the FSK port on that RTU (Medium: RTU)
• TCP-IP Port No, actually TCP Port No, used only in TCP/IP Server medium, this is the port the clients
connect to (Ethernet and GPRS) as the OPC is then the server
• Server TCP-IP Address is the address of the server the OPC as a client (multiple OPCs) must connect to.
• STFU Time and STFU Auto Tx are STFU (Silent Time For Unit - Radio Data Silence) periodic activation
(automatic) settings, inhibits all data communications to/from the RTU/device to enable voice communications
• Update RTU Time on Poll (and date) tick enables the time/date update of ALL the RTUs (devices) in this
channel (unless specifically disabled per device, later) when CONFIGURED data is polled. This should be un -
ticked where more than one OPC server connects to a single RTU as this can cause a time advance to the one
OPC and create invalid time stamps. This setting should only be active on one OPC at a time
116
SSE OPC
Channels: Modem Timers & Settings
• Modem Initialization Str are sent to the modem periodically at the rate set in Modem Initialize
Timer. This will only happen when there is no active connection or when an SMS transmission is complete
• Dial Timeout is the maximum time allowed for the OPC modem to dial a destination RTU
• Incoming Ring Timeout is the amount of seconds the OPC will wait for the modem to answer the dial-up
call before it (the OPC) will answer the call
• Comms Activity Timeout (Inactivity), no PROTOCOL comms between the OPC and the destination RTU
while a line (dial) is active in this period will cause the OPC to drop (hang -up) the line – saves costs and time
• Cell-Modem Type indicates to the OPC which of the GCOM modems (GSM) are connected to it as SMS/Dial-
up for the correct string and modem handling
• Modem Esc Sequence is the string the specific modem will use to exit data mode and enter command mode,
each modem is unique
117
SSE OPC
Channels: Modem Timers & Settings
• ModemHangUp is the string used for the modem to hang-up an active dial-up connection, again, each modem
hang-up string is unique and can even be incorporated into the modem escape string
• SMS Rx- and -Tx Count is an indication tool to the user/technician to gather how many SMSes were sent and
received by the modem connected to the OPC
• The above counters can be cleared automatically by the SMS Counter Reset either Daily, Weekly, Monthly,
Yearly or Never
118
SSE OPC
Channels: Client/Server Setup
• The most confusing of them all, Client/Server connections

• The left side is the Server configuration side. Port Number is the port the server must listen on for connecting
clients
• The right side is the list of client IP addresses (Client IP Address) that the server must allow to connect to
it
119
SSE OPC
Channels: Ethernet / TCP/IP Connections
• This is the most confusing communications medium as all rules pertaining to Ethernet and TCP/IP MUST be
adhered to
• Ensure that the Server and Clients’ IP addresses are in the same IP category (A, B or C)
• Ensure correct Subnet Masks for the IP categories
• Ensure that only TCP is used and NOT UDP!
• Special care is needed when DNS is used, for this the relevant network IT specialist is needed in establishing
the connection
120
SSE OPC
Devices
• Each device declared in a channel represents a RTU

• The Devices window configures the GLOBAL operation method/requirements of the RTU
121
SSE OPC
Devices: OPC Primary Connections
• System Address is NOT linked to any of the channels, but ONLY to the relevant device
• Digi-1, Digi-2 and Digi-3 is the digi-peater communication path used by the OPC/Base Station (even if it is
a RTU) to communicate with the specific device (Device Address). To be discussed in greater detail in
Network Maps
• TCP/IP Address is a view-only field that displays the IP address of the relevant device when connected to the
OPC (Medium: TCP/IP Server)
• This address is only populated once the RTU is connected to the OPC AND a successful link between
the Device Address and IP address is established in the OPC
• This happens automatically when using the SSE GPRS solution and/or the complete RTU12 Ethernet
solution via a special protocol message that links the two addresses. The link is NOT established
automatically when using a Ethernet to Serial converter as the message is not sent
• Protocol and RTU Type fields indicate the implemented features and type of RTU (device) for correct
operation and configuration in the OPC
• DNP Master and -Slave fields are shared with the IEC60870. The master and device address respectively,
refer to the DNP/IEC protocols for valid address ranges
122
SSE OPC
• Ports configures all the communication ports for the relevant device and, including the various addresses
(System, Device and DNP/IEC) is downloaded as Basic Configuration from the Datascope and is now
SAVED in the configuration database
• The number of ports shown is automatically loaded from the RTU Type field
• Note that the FSK port and ASC2/3 will ALWAYS be present when a RTU12 is selected even if the relevant
modules are NOT present
123
SSE OPC
• SMS in Route must only be used when there is a device in the digi-peat path, as digi-peater, that utilises SMS
- the message from the OPC is then physically shortened to accommodate the limitation of SMS
• Tries is the actual tries from the OPC to reach the device and NOT retries!
• Event Counter is (supposed to be) a read-only field to indicate the number of events the relevant device
reported to date, this counter can be reset via the selection in Reset Event Counter as Daily, Weekly,
Monthly, Yearly and Never
• Comms Fail Timeout is the amount of seconds the OPC must wait before flagging a Comms Fail, indicated
in Device Status, when NO data were received from the RTU. The status becomes Normal when ANY type of
Protocol communication from/to the relevant device address is established (originally implemented for the
microRTU when No Ack feature is used)
• Descr. Auto Downl. Delay is an hourly setting to download the descriptors to the RTU/device. Used when
descriptors are changed but cannot be downloaded via operator – Dangerous wrt. logging data and descriptor
tables
• Update Timestamp on POLL is the device specific control for time/date update from the OPC
124
SSE OPC
Devices: Device Hardware Profile / IO
Scan Rates
• Multi IO Modules MUST be selected in order for the local RTU IOs to be active, along with actual Multi IO
Cards
• Values shown in each of the IO type fields are the number of cards for each type connected to the device
(RTU) EXCEPT for the Multi IO Card, which has 8-channels each of AINs, DINs and DOTs – from above
• 2x Multi IO Cards, one without AINs or just not used (the other AINs, DINs and DOTs are populated on
the RTU)
• 3x 24-Chan DIN Cards, and
• 3x 24-Chan DOT Cards
• A value of 0 (zero) indicates that it is disabled/not used
• 2MB Memory Exp. Cards are limited to a maximum of 6 cards (remember, logger data ONLY)
• Scan Rate (AIN, DIN and CIN/FIN) is the rate at which the DECSRIPTOR tables are scanned in the RTU, NOT
the physical (low level) IOs
• In the RTU12, the CIN/FIN Scan Rate is relevant ONLY to the FIN data type, CINs are scanned every second
as they are not event enabled and is therefore not critical
125
SSE OPC
Devices: Alarms / Events / PTT Settings
• Events Enabled is enabled by default! To disable events be sure to tick this box (state as shown)!!!
126
SSE OPC
Devices: Logger Settings
• Logger Enabled does exactly that, it enables the logging of the relevant IOs globally when ticked
• Logger Overwrite Delay is the time period the RTU must wait before it will discard all logged data after the
data logger is full. In this time NO new data will be logged. The RTU will send the OPC an event to indicate the
logger is full according to the setting in TX Log Perc field (conditions apply)
127
SSE OPC
Devices: Telephone Settings (DIAL-UP
+ SMS)
• Primary Tel No is the telephone number the OPC must dial to reach the RTU, thus the RTU’s telephone
number; no ATD need to be added as a prefix
• The modem initialisation strings are entered in the Modem Init Str 1 - 3 fields. These strings are output
from the RTU to the Dial-up modem every 5 minutes if no connection is active or if the RTU is NOT busy
sending or reading an SMS
• Device SMS Header field contains the name of the RTU should the RTU be configured for SMS messaging
• Modem Esc Sequence is the string needed by the modem to get the modem out of on -line or data made and
into command mode. Modem HangUp string is then used to disconnect the modem from the line (hang-up the
call)
• SMS Rx Counter and SMS Tx Counter are view only fields to display to the user the total amount of SMS
messages received and sent respectively from/to the specific RTU/device
• The telephone strings part of the Telephone Settings are downloaded from the Datascope under Tel Str,
the Device SMS Header part is downloaded when either DIN Msgs or AIN Msgs are selected for download
128
SSE OPC
Devices: RTU Program
• RTU Program Name is a field in which you enter the specific program name for the RTU/device. Double -
clicking in this field then enters the program editor in which the RTU Program is written
• Only 1 program is allowed for each RTU/device
• The RTU Program is downloaded from the Datascope as RTU Program descriptors
• Note, the RTU Program is meant for download purposes only as the OPC compiles the program at download
time. The RTU does support upload (from RTUx-4.1.0), but this is only for storage debugging and is useless
otherwise due to the compilation of the program
129
SSE OPC
Devices: GPRS Settings
General:
• You MUST know how the relevant GPRS network and connection operate to setup the GPRS modem
• The service provider flush the GPRS system periodically between ever 1 to 6 minutes. For this purpose the
RTU must maintain in constant communication with the server via Heart Beat (to follow)
• The service provider does NOT disconnect the SIM attachment from the network every time a modem’s power
is cycled, this must be catered for in the modem via the configuration strings
• The following must be known for the required connection for correct modem setup:
1. Base station/Master IP address
2. Base station/Master TCP Port number
3. APN (Access Point Name) address
4. Username and Password for the PPP (Point-to-Point Protocol) connection
• Establishing a connection (even controlled) takes time, especially when there is a problem with the first
connection
• Have an up to date “AT Command Manual”, corresponding to the modem firmware version, at hand when
configuring the modem
130
SSE OPC
GPRS Limitations:
• No connection can be made between two RTUs, thus no remote IO mapping can be done
• All TCP/IP rules apply in GPRS
• All connections are Server/Client based
• All data transfers depend on a connection, no data can be transferred without a valid connection
• Establishing a connection can be timeous (hours), depending on factors such as overall network
traffic/availability, signal strength, APN availability, any Ethernet problem in the whole system
• At all costs, avoid a dial-up connection from the Base station/Master, use a fixed line connection
• No connection across APN can be established, unless arranged through service provider
131
SSE OPC
• Modem Type informs the OPC of what type of modem will be connected to the RTU/device. This aids the OPC
automatically populating the needed GPRS strings and string time-outs. Selections currently are:
• JORDAN-Sony Ericsson: Driver fully implemented
• JORDAN-Telit: No driver yet developed and should thus not be used
• The GPPRS Settings are downloaded in the Datascope under GPRS Settings
• Advanced GPRS field requires the push of the Setup… Button to run the string editor for the GPRS modem…
132
SSE OPC
Devices: GPRS Settings – Advanced
• SSE Advanced GPRS driver can be divided into two main operations:
• The main GPRS connectivity driver establishing and maintaining (to follow) the Server/Client
connection,
• And the GPRS signal strength driver which actually disconnects the modem to get the signal strength
and then reconnects the modem
133
SSE OPC
Connectivity Driver
• The GPRS driver of the RTU can accommodate a connection to two APNs, although NOT simultaneously! The
APN No field is for indication to the user as to what settings are entered for the specific APN
• Modem Cmd 1 to 6 are populated automatically by the modem type selection in the previous table. The
various connection strings required by the modem to establish the actual Server/Client connection are entered
here (Note: only 6 fields are available for this)
• Each modem command (Modem Cmd from above) has its own time-out field named Timeout. This time-out is
the maximum time the RTU will spend the relevant command ONLY! When the one command is issued and
that command’s specific time-out has expired, the RTU will issue the following command
• At the end of Timeout 6 the RTU checks if a “CONNECT” message was received from the modem
• If it has, the RTU is connected successfully to the Server and the RTU then issues the protocol
message to the OPC to link the RTU/device address to the modem/SIM card’s IP address
• If not, the RTU simply switches the modem off (through the BBR08 board), switches it on after 3
seconds and retry, but this time with the next APN entry
• If the second APN entry (APN 2) is empty (as above), the RTU will retry with APN 1 after the power cycle
sequence on the modem expired
• The RTU will do the above FOREVER if it cannot connect to the Server, so be sure that the settings are correct!
134
SSE OPC
Signal Strength Driver
• A global timer (to follow) indicates to the RTU if the GPRS signal strength is required. If so…
• The RTU exits the modem from online data mode and puts the modem into command mode with Modem Cmd 7
(the modem is still connected to the Server during the whole operation)
• Upon expiry (time-out) the RTU requests the signal strength through Modem Cmd 8. The modem then
responds with a value to the RTU which maps this value through a local IO Map (to follow)
• When Timeout 8 expires, the RTU attempts to re-open the connection (from command mode back to on-line
data mode). If at the end of Timeout 9 the modem does not respond with “CONNECT”, the RTU restarts the
whole sequence from the previous slide
135
SSE OPC
• GPRS DOT Power Switch is the DOT on the RTU that must be used to control the modem power supply. The
RTU driver will utilise this DOT to do the hardware switching on and off of the modem
• Heart Beat Rate maintains the connection to the Server. The RTU will send a specific protocol message,
periodically according to the rate, to the OPC to keep the connection open to the RTU and will prevent the
service provider from closing the connection. This string can contain data for the various descriptors (to
follow)
• Signal Strength Rate is the global timer that enables the signal rate driver if not zero, and runs the
processes explained in the previous slide
• Session Open String, Connect String, Disconnect String and Session Close String fields are
only used in older version firmware (pre RTUx-4.1.0 and microRTU) and are considered OBSOLETE!
• The OPC still accommodates these strings by sending the “old” (these) strings first. If the RTU does not
support the old driver, the RTU will respond with a No Acknowledge (NACK) and the OPC will then send the
Advanced GPRS strings
136
SSE OPC
Establishing a Connection:
• After all settings are correctly defined in the configuration, the descriptors MUST be downloaded in the
following order to ensure that the RTU will connect to the Master/Base Station:
• Basic Configuration – Configuring the required port for GPRS modem type
• HW Setup – Configures the DOT for modem switch control, added to this the rates for the Heart Beat
Rate and Signal Strength Rate fields
• GPRS Settings – The actual strings and timeouts for the connection
137
SSE OPC
Devices: RTU Status
• Batt Faulty is used ONLY in the RTU12. A signature compare algorithm is implemented to verify if the
battery is healthy. Should this not be the case, this tick-box will be enabled when the RTU transmits the event
to the OPC indicating the problem. This field CANNOT be enabled by the user!
138
SSE OPC
Data Points: Data Types and Descriptors
• RTU have the following Data Types:

• Inputs
AINs, DINs, FINs, and CINs – These type have descriptors
• Outputs
AOTs and DOTs – No descriptors
• Registers
AREGs and DREGs – No descriptors
• Descriptors inform the RTU’s individual IOs how to interpret to actual connected entities (describe to the
processor of the RTU how to process the various inputs)
• Descriptor commonalities:
• Configuration of relevant operating limits
• Enables Event (Change Of State – COS) reporting (SMS Messaging and Protocol) – Remember to enable
events GLOBALLY!
• Enables Logging – Remember to enable the logger GLOBALLY!
139
SSE OPC
Data Points: Events
• The following descriptors are needed BEFORE eventing can operate correctly (in no particular order):
• HW Setup – Globally enables events
• Input Descriptors – Enables the event processor for each individual input – Note that AINs also
need AIN Scaling descriptors to operate
• Network Maps – Enables the Task List to transmit the events to the required address (to follow)
140
SSE OPC
Data Points: Analogue Inputs (AIN) - Events
• Samples filed is the amount of samples to take of the input value at the predefined AIN Scan Rate field
BEFORE processing the AIN value
• Event Enabled tick-box enables the relevant IOs to report a change of state condition. This is on condition of
the correct Network Map configuration (to follow)
• Delta Change (Unit) indicates the Engineering Unit (to follow) value quantity change BEFORE an event
will be generated, -(Raw) is the same change quantity but as a raw value (there is a calculation bug here)
• Downloaded as part of the AIN descriptors from the Datascope
• Event Example
141
SSE OPC
Data Points: Floating-Point Inputs (FIN) - Events
• AIN Port IO No is when a FIN’s descriptor data is processed directly from an AIN value (low-level tables,
not descriptor tables)
• Samples filed is the amount of samples to take of the input value at the predefined FIN Scan Rate field
BEFORE processing the FIN value
• Delta Change indicates the value quantity change BEFORE an event will be generated
• Downloaded as part of the FIN descriptors from the Datascope
• Event Example
142
SSE OPC
Data Points: Digital Inputs (DIN) - Events
• Dead Time operates the same as Samples in AINs and FINs, but from the DIN Scan Rate field
• Downloaded as part of the DIN descriptors fro the Datascope
• Event Example
143
SSE OPC
Data Points: Logger - RTU
• The RTU data logger operates in two modes:

• Periodic Log – The inputs are monitored continuously, according to the relevant setup, and when a
configured amount of time has elapsed the input is logged. NO limit/window is checked
for this logging mode as the actual average must be logged periodically
• On-Change Log – The input are logged in the same manner as the input events COS are checked, when
an input change above/below a certain threshold or changes state the input is logged, a limit/window
change is implemented the same as for events (AIN/FIN)
• The logging modes can be used either individually or in unison
• The data logger is TOTALLY independent from the input descriptors
• No input descriptors need to be downloaded for the logger to operate, only logger descriptors need to be
downloaded
• Thus, only the low-level input values are logged and NOT processed values!!!!!!!!!!!!!
144
SSE OPC
Data Points: Logger - RTU
• By activating the Logger Enabled tick-box of any input data type , the general Logging editor is run where
ALL input data types’ logging configuration must be defined
145
SSE OPC
Data Points: Analogue Input Logger (AIL)
• Periodic Log tick-box enables/disables the input’s periodic logger engine

• Periodic Sample Min and -Sec define how often (periodic) the AIN must be sampled
• Periodic Log Min and –Sec is the rate at which the AIN must be logged, when this time is reached the
average of the AIN, for the amount of samples taken, is calculated and is then logged
• On Change Log tick-box enables/disables the input’s on-change logger engine
• Samples are the amount of samples of the AIN to take to calculate the average for value comparison
• Delta Change is the amount of change limit before the AIN is logged (calculated from the AIN scaling fields,
to follow)
• Sample On Change Min and –Sec is the rate at which the AIN must be sampled, in the same manner as the
AIN Scan Rate in the Devices window for eventing
• Downloaded as AIN Logging from the Datascope
146
SSE OPC
Data Points: Floating-Point Input Logger (FIL)

• Periodic Sample Min and -Sec define how often (periodic) the FIN must be sampled
• Periodic Log Min and –Sec is the rate at which the FIN must be logged, when this time is reached the
average of the FIN, for the amount of samples taken, is calculated and is then logged
• Samples are the amount of samples of the FIN to take to calculate the average for value comparison
• Delta Change is the amount of change limit before the FIN is logged (calculated from the FIN scaling fields,
to follow)
• Sample On Change Min and –Sec is the rate at which the FIN must be sampled, in the same manner as the
AIN Scan Rate in the Devices window for eventing
• Downloaded as AIN Logging from the Datascope
147
SSE OPC
Data Points: Digital Input Logger (DIL)

• Periodic Log Min and –Sec is the rate at which the DIN must be logged, the actual value of the DIN at that
instant will be logged
• Downloaded as DIN Logging from the Datascope
148
SSE OPC
Data Points: Counter Input Logger (CIL)

• Periodic Log Min and –Sec is the rate at which the CIN must be logged, the actual count value of the CIN at
that instant will be logged
• Downloaded as CIN Logging from the Datascope
149
SSE OPC
Data Points: AIN Alarms
• Alarm Enabled enables/disables the input’s alarming process

• Dead Band is the window in which the value can fluctuate without generating an alarm
• HiHi, Hi, Lo and LoLo are the various generated alarm levels at the required engineering value
• EU Max, EU Min, Raw Max and Raw Min fields are the scaling parameters for eventing and alarming
• Downloaded as AIN Scaling from the Datascope
150
SSE OPC
Data Points: AIN SMS Messaging (Alarms)
• Alarm Enabled MUST be ticked for the following to operate

• Global Alarm MUST be enabled for the following to operate (Alarms / Events / PTT Settings)
• SMS Enabled ensures that the alarm notification can be sent as a normal SMS Message for display on a cell
phone handset (not a SSE SMS protocol message)
• SMS AIN Desc. is the actual name/description given to the current AIN as it will appear on the cell phone
handset
• SMS HiHi, SMS Hi, SMS Normal, SMS Lo and SMS LoLo are messages for the various levels to be displayed
on the cell phone handset
• Note, if no text is present in these fields (as the default shows) the actual value of the current AIN will be
sent to the handset, if text is present in the fields, the actual text will be sent to the handset
• Downloaded as AIN Msgs from the Datascope. AIN descriptors (AIN) MUST be downloaded first when AIN
Messaging is used!
151
SSE OPC
Data Points: AIN Data scope Formatting and
Values
• EU Value displays the last value received from the RTU’s relevant AIN as an engineering value
• EUVal Dec Format formats the floating point component of the AIN scaled (engineering value) to the desired
decimal point for display on the OPC Datascope
• Raw Value is the actual ADC (Analogue-To-Digital converter) value used to compute the EU Value from the
RTU’s relevant AIN above
• Eng Units is a string field downloaded to the RTU to define the entity type as text used for Datascope
display and SMS Messaging
• Logarithmic dBm Enabled forces the OPC to convert the enabled AIN value to be converted to a dBm
logarithmic unit for display in the Datascope (used in the audio level modules)
• Logarithmic dBm Enabled is downloaded as part of the AIN descriptors from the Datascope
152
SSE OPC
Data Points: AIN Triggers
• Triggers ensures that an AIN event processing is executed when the required trigger is active
• Trigger Digital Enable enables AIN eventing ONLY if the configured digital data type from Digital IO
Type and Digital IO Addr is active
• Trigger On sets the level for the relevant digital data type to enable AIN event to be sent
• Trigger Analog Enable enables AIN eventing ONLY when a predefined threshold from an analogue data
type, defined in Analog IO Type and Analog IO Addr, is exceeded from the limit set in Analog
Threshold
• Digital/Analog Delay(mSec) defines a dead time for the analogue threshold or digital level to settle before
the trigger is processed
• Triggers are downloaded as part of the AIN descriptors, as a separate entity if defined, from the Datascope
153
SSE OPC
Data Points: AIN Add To Heartbeat Message
• Add to GPRS Heartbeat enables the specific AIN value to be added to every GPRS Heartbeat message
(medium GPRS) – very useful for ensuring up-to-date data without the need for a poll message
• The amount of values to add to a Heartbeat message is limited to 30 AINs ONLY!!!
• Downloaded as part of the AIN descriptors from the Datascope
154
SSE OPC
Data Points: FIN Add To Heartbeat Message
• Add to GPRS Heartbeat enables the specific FIN value to be added to every GPRS Heartbeat message
(medium GPRS) – very useful for ensuring up-to-date data without the need for a poll message
• The amount of values to add to a Heartbeat message is limited to 15 FINs ONLY!!!
• Downloaded as part of the FIN descriptors from the Datascope
155
SSE OPC
Data Points: DIN SMS Messaging (Alarm/Event)
• As with the AINs, but NOT as alarming, but as eventing

• SMS Enabled ensures that the notification can be sent as a normal SMS Message for display on a cell phone
handset (not a SSE SMS protocol message)
• SMS DIN Desc. is the actual name/description given to the current DIN as it will appear on the cell phone
handset
• SMS Hi and SMS Lo are messages for the relevant levels to be displayed on the cell phone handset
• Note, if no text is present in either of these fields (as the default shows) NO SMS will be sent to the
handset. A message will only be sent if a field contains text and only the field that contains the text’s
level will be sent!
• Downloaded as DIN SMS Msgs from the Datascope
156
SSE OPC
Data Points: CIN Data scope Formatting and
Values
• NONE of the above fields are downloaded to the RTU! All these fields are for correct value scaling for
Datascope display in the OPC ONLY!
157
SSE OPC
Data Points: CIN Set point
• CIN Setpoint enables the relevant CIN descriptor to start counting at a preset value
• Useful when implementing a new RTU with a flow meter that already has a count, then this filed is used to
synchronised the two entities
• Value is downloaded to the RTU as soon as the cursor/focus is moved from this field to another
• Add to Heartbeat is NOT implemented for CINs yet!!!
158
SSE OPC
Data Points: Outputs and Registers
• Output and Register data/IO types do not have descriptors

• Output and Register data/IO types cannot report change of state (events)
• Output and Register data/IO types cannot be logged
• Register types were originally implemented only for P-Code/RTU Program
159
SSE OPC
Data Points: Analogue Output (AOT)
• EU Max, EU Min, Raw Max, Raw Min and Eng Units are not downloaded to the RTU, but is used by the OPC
for the Datascope display of the values
• EU Value is the editing field to change the actual AOT output in the RTU by the EU entity entered here. The
value is written to the RTU as soon as the field scope/focus is changed
• Raw Value is the editing field to change the actual AOT output in the RTU by the actual raw amount entered
here. The value is written to the RTU as soon as the field scope/focus is changed
• AOT is a 16-bit register and can accept values from “0 – 65535” UNSIGNED!
• Confirm Enabled tick box enables a “confirm of state change” process in the OPC. If a value is written to the
relevant AOT the RTU must acknowledge the state change to the OPC. If this box is ticked and the RTU does
not respond with an acknowledge, the OPC will resend the value when the time in Confirm Time has expired
160
SSE OPC
Data Points: Digital Output (DOT)
• EU Value is the editing field to change the actual DOT output in the RTU by the EU entity entered here. The
• Raw Value is the editing field to change the actual DOT output in the RTU by the actual raw amount entered
• DOT is a binary register and can ONLY accept a value of ‘0’ or ‘1’
relevant DOT the RTU must acknowledge the state change to the OPC. If this box is ticked and the RTU does
161
SSE OPC
Data Points: Analogue Register (AREG)
• EU Max, EU Min, Raw Max, Raw Min and Eng Units are not downloaded to the RTU, but is used by the OPC
for the Datascope display of the values
• EU Value is the editing field to change the actual AREG output in the RTU by the EU entity entered here. The
• Raw Value is the editing field to change the actual AREG output in the RTU by the actual raw amount entered
• AREG is a 16-bit register and can accept values from “0 – 65535” UNSIGNED!
relevant AREG the RTU must acknowledge the state change to the OPC. If this box is ticked and the RTU does
162
SSE OPC
Data Points: Digital Register (DREG)
• EU Value is the editing field to change the actual DREG output in the RTU by the EU entity entered here. The
• Raw Value is the editing field to change the actual DREG output in the RTU by the actual raw amount entered
• DREG is a binary register and can ONLY accept a value of ‘0’ or ‘1’
relevant DREG the RTU must acknowledge the state change to the OPC. If this box is ticked and the RTU does
163
SSE OPC
Data Points: IO Maps
• By definition: IO Maps map IOs

• There are 3 implementations of IO Maps
• LOCAL – Maps virtually ANY onboard input or output to another input or output. No rule for mapping an
input to an output of the same data type size (AIN-AREG-AOT-CIN and DIN-DOT-DREG), but rules do
apply when mapping IOs between the different data type sizes (AIN -DIN-CIN-DREG-AOT-DOT-AREG-CIN).
There are local IO types that are NOT physical IOs, but the implementation of it in the RTU makes them
operate as virtual IOs (GPRS SIGNAL, PASSWORD, RESET PASSWORD)
• TX – Inputs that must be transmitted (events, but as IO Mapped inputs) from the RTU by means of a
combination of an IO Map and Network Map (to follow)
• RX – Inputs received as events that are IO Mapped at the receiving station/RTU
164
SSE OPC
Data Points: IO Maps - Local
• For a local IO Map to operate as such the only requirement is that the Remote/Destination Station
Address is the same as that RTU the IO Map is configured for (System Address obviously too), for this
example, RTU Address = 1
• For local IO Maps the Destination- and Source-Data Types are used:
• If DOT1 must be mapped to DIN1 locally, the Source Data Type is the DOT. That is the data to be
mapped. The DIN will then be the Destination Data Type as that is where the data must end up. Only
1 IO must be mapped, so the corresponding Remote-Start and –Stop and the Local-Start and –Stop
must be set to 1 and only IO must be mapped
165
SSE OPC
Data Points: IO Maps - RX
• For a RX IO Map the Remote/Destination Station Address (and System Address) is the RTU’s address
from where the data will be received, for this example, RTU Address = 1 and the data will be received from
Address = 100
• For RX IO Maps the Remote- and Local-Data Types are used:
• If AIN9-10 from the remote RTU must be mapped to AREG4-5 locally, the Remote Data Type is the
remote AIN. That is the data to be mapped. The AREG will then be the Local Data Type as that is
where the data must end up. 2 IOs must be mapped, so the corresponding Remote-Start and –Stop
must be set to 9 and 10 respectively, and the Local-Start and –Stop must be set to 4 and 5
respectively, which gives you the 2 IOs
• Remember, RX IO Maps are plain events received from the remote station and then mapped in the local station
166
SSE OPC
Data Points: IO Maps - TX
• For a TX IO Map the Remote/Destination Station Address (and System Address) is the RTU’s address
to where the data must be transmitted, for this example, RTU Address = 1 and the data will be transmitted to
Address = 100
• For TX IO Maps the Remote- and Local-Data Types are used:
• If DIN1-8 locally must be mapped to DOT8-15 remotely, the Remote Data Type is the remote DOT. That
is where the data is to be mapped. The DIN will then be the Local Data Type as that is where the data
is transmitted from. 8 IOs must be mapped, so the corresponding Remote-Start and –Stop must be set
to 8 and 15 respectively, and the Local-Start and –Stop must be set to 1 and 8 respectively, which
gives you the 8 IOs
• Remember, TX IO Maps are special IO Map events transmitted from the local station and then mapped in the
remote station
167
SSE OPC
Data Points: Network Maps
• Network Maps form the basis of the Task List and is the core of any RTU initiated communications to the
OPC/Base-station and other RTUs
• Network Map serves 4 purposes:
• Manages the change of physical comms mediums/change of comms ports
• To define any digi-peating paths
• Service all Poll/Response types (Task Types!)
• Enables the RTU to report various unsolicited responses (Event Reporting, Alarm Reporting etc)
168
SSE OPC
• Comms Medium defines what medium to use for communication, these include:
• FSK – radio medium
• Direct Connection – direct interfacing without any comms establishing engine
• Dial-up – dial connection must first be established before connection (incoming and outgoing)
• SMS – handles all messages as either protocol via SMS or SMS Messaging
• GPRS – GPRS connection initialisation with support services
• Comms Ports are the actual physical ports that a medium connects to for communication
• FSK – FSK port on RTU (if module fitted)
• ASC0 – ASC3 – actual serial ports (if ASC2/3 fitted)
• DCD Select is not used anymore as this is now implemented in Basic Configuration flow control
• Station Address is the DESTINATION address referenced in the Network Map, operates in conjunction with
System Address
169
SSE OPC
Data Points: Network Maps Digi-peating
• Defining digi-peat addresses in the Network Maps serves NO purpose if there are no digipeat addresses are
defined in the Devices window
• The digi-peat addresses defined in the Devices window indicates the comms path from the origin, with
reference to the OPC/Base-station, to the end destination – RTU
• The Network Maps digi-peat addresses indicates the comms path from the origin, the RTU, to the destination –
OPC/Base-station
• When using an RTU as a FSK modem, the RTU address MUST be the same as that of the OPC! This ensures
that the FSK modem RTU does not need to be defined as a digi-peater
• Complex Example
• IO Mapping can be processed in digi-peat paths
• Digi-peating diagnostic via protocol and Datascope
170
SSE OPC
• Event Reporting is actually Reporting Type. Here RTU is instructed what to do with input descriptors:
• All Event Reporting – all events must be reported (Protocol messages)
• All Alarm Reporting – all input alarms must be reported (Protocol messages)
• All SMS Messaging – All IO reporting (SMS Messaging to handset)
• IO Map Event Reporting – same as event reporting, but Tx type in IO Maps (to follow)
• IO Map Alarm Reporting – same as alarm reporting, but Tx type in IO Maps (to follow)
• IO Map SMS Messaging – input-block SMS Messaging transmission to handset
• Poll Minute, Poll Second and TX/Poll Type form the RTU initiated Reporting/Requesting of configured
data to the OPC/Base station or other RTUs. Poll Minute and –Second is the rate for the required task
• Phone Number is the telephone number of the destination device/station – OPC/Base-station or other RTUs –
if SMS or Dial-up is used. ATD MUST be present for dial-up stations, but is optional in an SMS system as the
medium caters for this
171
SSE OPC
Devices Device Port Routing
• Device Port Routing is for SSE Protocol messages ONLY!!!!

• From the RTU3 days, when a message was received at an RTU and the message was not intended for that
RTU, then the RTU would forward the message automatically through the FSK port. This was the days when
FSK was the defacto comms medium
• Times change, MDSs are fast becoming the standard and this feature to automatically forward the data is lost
over the serial ports (ASC0 – ASC3)
• Device Port Routing caters for “automatic” digi-peating where no Network Maps are/can be downloaded
due to the comms medium and the comms port
• To ensure that the Device Port Routing operates as required, the digi-peat addresses MUST still be entered
in the Devices -> OPC Primary Connections window. These addresses are used in the RTU to get a path
back to the source or to send it forward to the eventual destination
172
SSE OPC
Devices Device Port Routing
• All settings are configured in the right side of the window

• All ports are represented as a matrix, indicating the Incoming and the outgoing ports
• By ticking a box in the Port Routing Options, the Incoming Port is then forwarded, with the correct digi-
peating shifting of addresses, to the outgoing port represented by the tick-box
173
SSE OPC
Data Points: AIN/FIN Event Processing
• AIN/FIN Scan Rate = 1000 ms

• Samples = 7
• Delta Change (Unit) = 10
174
SSE OPC
Data Points: Events - AIN/FIN Event Processing
Signal Magnitude
Time
175
SSE OPC
Signal Magnitude
Time
176
SSE OPC
Signal Magnitude
Time
177
SSE OPC
Signal Magnitude
Time
178
SSE OPC
Data Points: AIN/FIN Event Processing – SCADA
View
Signal Magnitude
Time
179
SSE OPC
Data Points: DIN Event Processing
• DIN Scan Rate = 1000 ms

• Dead Time = 1
180
SSE OPC
Digital Input
Time
181
SSE OPC
Digital Input
Time
182
SSE OPC
Digital Input
Time
183
SSE OPC
Data Points:DIN Event Processing - NOTE!
Digital Input
Time
184
SSE OPC
Data Points: AIN/FIN Log Processing
Periodic
• Periodic Sample Min = 1

• Periodic Sample Sec = 0
• Periodic Log Min = 5
• Periodic Log Sec = 0
185
SSE OPC
Periodic
Signal Magnitude
Time
186
SSE OPC
Periodic
Signal Magnitude
Time
187
SSE OPC
Periodic
Signal Magnitude
Time
188
SSE OPC
On-Change
• Samples = 5
• Delta Change = 10
• Sample On-Change Min = 2
• Sample On-Change Sec = 0
189
SSE OPC
On-Change
Signal Magnitude
Time
190
SSE OPC
On-Change
Signal Magnitude
Time
191
SSE OPC
On-Change
Signal Magnitude
Time
192
SSE OPC
On-Change
Signal Magnitude
Time
193
SSE OPC
On-Change
Signal Magnitude
Time
194
Comms Orchestrator
• Apart from the already-known input and output types of the RTU (AINs, DINs etc) the Comms Orchestrator
(CO) utilises ALL data types (registers included), and the CO device itself becomes a IO device
• Data from all supported device types can be mapped into ANY of the SSE data types, as long as the data type
size matches that of the device
• CO devices/protocols are MASTER protocols. The device must be a slave-type device (RTU requests data,
Device responds – no “event-type” data can be supported)
• Additional devices can be added to the CO driver in the RTU and the OPC, at a minimal cost implication…
195
Comms Orchestrator
• The CO configuration window is split into 2 entities

• Left side (Communications Orchestrator) represents the actual device connected to the RTU as a
whole, including all communications settings, timings and in certain cases the handling of the data type
order
• Right side (SSE Protocol) represents all the actual commands/requests to the device and the IOs in
the device, and how it is mapped into the RTU data tables
196
Comms Orchestrator
Left Side
• RTU Port is the physical comms port used on the RTU to connect the external device to
• Mux Ports is the physical port on the MUX card where the device is connected to. If no MUX card is present,
leave the setting to 1
• Protocol selects the actual protocol used to communicate with the device
197
Comms Orchestrator
Left Side
• Baud rate, Data bits, Parity and Stop Bits are the comms settings for the device. These are the settings
needed to communicate to the device and MUST therefore match that of the device
• Byte Time is the time the RTU must wait before the received message is seen/processed as a complete
message
198
Comms Orchestrator
Left Side
• Time Slot (ms) is the time limit of the RTU from the time the RTU sends the request command until the
RTU processed the response, for ALL commands. If there are 6 commands defined for a device, the above
settings will allow ONLY 2 seconds for ALL commands AND responses to be processed (the BIGGEST point of
error)
• Func Time Aloc is a view field to inform the configurator/user how much time the RTU gives each command
(Function)
199
Comms Orchestrator
Left Side – Time Slot
• Time Slot (ms) is the time limit of the RTU from the time the RTU sends the request command until the
RTU processed the response, for ALL commands. If there are 6 commands defined for a device, the above
settings will allow ONLY 2 seconds for ALL commands AND responses to be processed (the BIGGEST point of
error)
• Func Time Aloc is a view field to inform the configurator/user how much time the RTU gives each command
(Function)
200
Comms Orchestrator
Left Side
• To ensure proper comms to the device, a comms fail mechanism is implemented

• No of Tries is the total amount of tries per command the RTU sends for a valid response from the device. If
no valid response is received within 3 tries (as shown here), the RTU will set a IO state from Destination IO
Address, for the specific data type in Destination IO Type. AINs, DINs and DOTs are supported
201
Comms Orchestrator
Left Side
• Floating Point Arrangement corrects the order of device representation of a single floating point data
type to be mapped into the SSE FINs
• FP Translate enables the Floating Point Arrangement setting
202
SAM
The System Analysing Mechanism or SAM Menu lets you build your own hierarchical menu
structure for the SAM display. The SAM menu system can display complete menu structures
containing data and output control information and execution. In addition to this a configuration
management feature by means of embedded documentation is implemented to ensure the user can
add complete build-states of the station/system or any other documentation related data.
The SAM menu features are accessed from the Device Window->SAM Menu tab. Before the actual
menu structure can be used, a menu unique name must first be supplied, as shown below,
then double click to take you to the next screen. You can also click on the navigation icon next to the
'RTU Program' icon.
For a more in-depth explanation of the menu system, an introduction to and operation of the SAM
must be covered first. The menu system configuration is covered in the SAM Menu Structure
Maintenance Screen.
Additional functionality for the SAM are available from SAM Messaging.
203
SAM
Introduction
The SAM display hardware comprises a 4-line by 20-character alpha-numeric ASCII liquid crystal
display (LCD) which is controlled by a dedicated key panel, as can be seen below:
SAM Power Key

A momentarily press of this key will either switch the
SAM on (if already off) or off (if already on).
Numeric Keys
Numeric 0 through to 9 values. This is mostly used
for the menu hierarchy selection via the index.
Menu
Reverts to the first Level1 menu screen if no Start-
up Screen is present.
Clear
Currently unused
Sign Change
Decimal Point
204
SAM
Introduction
Escape
Currently unused
Special Functions
Special Function 1 - 3 keys for user dedicated implementation.
Currently unused.
Each key-press on the key panel is actively sampled when a
buzzer sound is heard from the SAM,
except on the power button.
Enter
The Enter/Accept key. when-ever a change is made or a selection
is made, the change/selection will
become active on the pressing of the ENT key.
Remaining Arrows
Currently unused
Left Arrow
A back-key for moving back up into the hierarchy of
the menu structure.
205
Decimal Point
SAM
Operation
Screen and Levels fields, along with the IO Type field types. The hierarchy is established by means of
a numbering system for each entry in the various fields mentioned.
Each entry in Level1 will have a unique index starting from 1. The next entry in Level1 will have an
index of 2 and so forth. Now a first entry in Level2 will now also have an index of 1, the next
consecutive entry in Level 2 will have an index of 2 and so on. This is repeated for all levels.
This can be shown as follow:
This ensures that each index is linked to a level of a specific magnitude. Level1 has the highest
ranking, followed by Level2 etc. A lower level, eg Level5 cannot exist without a higher level, Level4,
entry. This ensures the linking process to operate.
206
SAM
Operation
Because of this link between the levels and the indexes, there is one more link to sustain the
hierarchy, namely the level link. This means that if more sub-levels are added to their respective main
levels a full hierarchy can be formed. This is shown below:
Each level and sub-level within its own ranking is linked

and the unique index is compiled accordingly.
This unique index is now used by the SAM display and
the key-panel to select and show the desired
menu structure according to the indexes.
Refer to the SAM Menu Screen. The above diagram is
from the example. All text and variables
substituted, the diagram will look like the following
(without the Start-up Screen):
207
SAM
Operation
208
SAM
Configuration Rules
Refer to the IO Type field for more clarity.
Due to the nature of the operation of the SAM display and the index linking of the various levels, a
number of configuration rules MUST be adhered to to ensure the stable and predictive operation of the
SAM display.
The following rules apply:
1. A Start-up Screen is optional.
2. Within a Start-up Screen the PASSWORD type is optional.
3. IO Registers (selected from IO Type) can be displayed in the Start-up Screen.
4. Documentation (DOC) CANNOT be displayed or accessed from the Start-up Screen.
5. An AUTO LOGOUT type cannot be used without the presence of a PASSWORD type
6. A lower ranking sub-level MUST have a higher ranking level as a reference point for correct
indexing.
7. Within the Levels, any IO Type can be referenced and all are optional.
8. To display a MENU, DOC and IO register within a level, the following order MUST be adhered to:
· First a MENU type,
· then a IO type (DIN, DOT, AIN, CIN, FIN, DREG, AREG, CTRL DOT and CTRL DREG)
· then the DOC type
9. External referenced documentation MUST be plain text file(s). NO pictures and/or graphics must be
present.
10. The SAM settings MUST be downloaded to the connected RTU in order for the SAM to operate.
See below for SAM descriptor downloads
209
SAM
Configuration Rules
Do NOT upload (request) the SAM descriptor configuration from the RTU.
210
SAM
Menu Screen
The SAM Menu Structure Maintenance Screen, shown below, is a simple example of a menu
configuration
211
SAM
Menu Screen
The screen consists of 11 columns where ALL configuration for the required menu is done. Each
column represents a specific field in the actual menu structure that the user will see from the SAM
display, and therefore simplifies the configuration for the user.
Columns 1 - 6 controls/configures the actual menu/sub-menu text on the SAM display. Column 7
configures the actual data type of the menu levels, and the remaining columns (8 - 11) control the
value display of the various data types from column 7.
Each field for columns 1 - 6 is further configured by column 7, the IO Type field. Refer to
this field for each of the first 5 fields of configuration.
The SAM display consists of a 4-line, 20-character display. This MUST be kept in mind when
configuring the menu structures and the actual documentation.
For simplicity's sake, the IO Type field will be explained first:
IO Type
Start-up Screen
IO Type
Levels
IO Address/Auto Logout Timeout
Format
On State/File Path
Off State/File Name
212
SAM
Start-up Screen
The Start-up Screen field is the first actual screen displayed by the SAM display after the SAM is
connected to the RTU. Various parameters can be displayed in this field such as the Time/Date,
Station name/text etc. This field is completely optional.
Refer to the SAM Menu Screen for this discussion. With reference to the IO Type field, all text in the
Start-up Screen field is displayed, with the exception of TIME/DATE and AUTO LOGOUT. As the IO
Type field works in conjunction with this and the Levels fields, the below discussion will comprise both
parameters for clarity.
Start-up Screen: STATIONX

IO Type: TEXT
STATIONX in this case is a TEXT type and represents the station ID/name. This is the first text
displayed on the SAM display.
Start-up Screen: GPRS

IO Type: AIN
The GPRS text will be displayed on the next line followed by a value from an AIN (in this case AIN
1 from the IO Address/Auto Logout Timeout field).
Start-up Screen: None

IO Type: TIME/DATE
Only the time and date will be displayed in the following line as there are no text in the Start-up
Screen field. The time and date is periodically updated from the connected RTU.
213
SAM
Start-up Screen
Start-up Screen: None
IO Type: AUTO LOGOUT
No text is displayed, or should be entered, for this parameter as this is an operational parameter
only. No line on the SAM display is consumed or reserved for this parameter either. The auto
logout timeout for this configuration is 120 seconds from the IO Address/Auto Logout Timeout
field. Refer to PASSWORD and AUTO LOGOUT for more information.
Start-up Screen: PASSWORD

IO Type: PASSWORD
The text PASSWORD is displayed on the SAM display, and the SAM is basically waiting for input
from the key-panel to proceed to the Levels structure.
214
SAM
IO Type
The IO Type field basically informs the preceding fields of how the data is to be presented and/or
handled.
The various selections for this field are as follow:
MENU
TEXT
PASSWORD
DOC
TIME/DATE
AUTO LOGOUT
DIN
DOT
CTRL DOT
DREG
CTRL DREG
AIN
AOT
AREG
CIN32
FIN
215
SAM
IO Type
MENU
Text in the levels as this type is displayed as a menu item on the SAM display. This field is directly
coupled in operation to the Level1, Level2, Level3, Level4 and Level5 fields in the configuration
window. Each entry in the levels of this type (MENU) creates a unique index for reference.
See the configuration of these fields for more detail.
TEXT
A TEXT type entry is only used in the Start-up Screen. This will typically be a station name or an ID
number for the station.
PASSWORD
This type indicates that a password must be entered by the user before the SAM can be used further
to display the rest of the menu structure (Levels1-5). This is a security feature maintained from the
RTU to ensure a specific user must first log into the SAM (RTU) before any actions can be taken from
the SAM to the RTU.
See Password List for more information.
216
SAM
IO Type
DOC
This type will point the user by means of the relevant text entry in the levels to a specific document to
be displayed on the SAM.
A document can either be imported from an external text file by typing the file path and name in the
File Path and File Name fields, or a local document file can be created by double-clicking on the DOC
type. another window will open (see below) where the document can be entered and saved for
download to the RTU.
217
SAM
IO Type
TIME/DATE
This type is used in conjunction with the Start-up Screen. No text need to be entered in the Start-up
Screen for this type, the Time/Date will automatically be displayed in the Start-up Screen for this type.
AUTO LOGOUT
With the selection of this type a PASSWORD type MUST be present. This type is defined in the
Start-up Screen of the menu structure, with the auto-logoff time limit defined in the I/O Address/Auto
Logout Timeout field in seconds. This is a security feature maintained from the RTU. When a key press
on the key-panel from the SAM did not occur in the timeout period, then the SAM will logout
automatically and therefore prevent any user access to the SAM until the user log into the SAM again .
This IO Type is an operational IO Type only.
DIN
This type pertains to the Start-up Screen and to the Levels. Text entered into any of these fields with
this type will display the status of a DIN. The specific DIN IO Number is selected from the I/O Address/
Auto Logout Timeout field.
The DIN status can be either a 1 or 0, thus the status text for display on the SAM can be entered in
the On State/File Path and the Off State/File Name fields.
218
SAM
IO Type
DOT
this type will display the status of a DOT (monitor only, no control). The specific DOT IO Number is
selected from the I/O Address/Auto Logout Timeout field.
The DOT status can be either a 1 or 0, thus the status text for display on the SAM can be entered in
CTRL DOT
this type will control the status of a DOT (monitor and control). The specific DOT IO Number is
The DOT status can be either a 1 or 0, thus the status text for display on the SAM can be entered in
the On State/File Path and the Off State/File Name fields. The status of the relevant DOT works on a
toggle operation linked to the index of the DOT.
Should there be 40 CTRL DOTs be configured in a menu, each DOT will have an index in front of the
display text on the SAM. By entering this index number from the key-panel and pressing ENT, the DOT
status will toggle from the previous status (from on to off if it was on and vice versa).
The maximum number of DOTs catered for in a consecutive menu structure of CTRL
DOTs only, is 99!
219
SAM
IO Type
DREG
This type pertains to the Startup Screen and to the Levels. Text entered into any of these fields with
this type will display the status of a DREG (monitor only, no control). The specific DREG IO Number is
The DREG status can be either a 1 or 0, thus the status text for display on the SAM can be entered in
CTRL_DREG
This type pertains to the Startup Screen and to the Levels. Text entered into any of these fields with
this type will control the status of a DREG (monitor and control). The specific DREG IO Number is
The DREG status can be either a 1 or 0, thus the status text for display on the SAM can be entered in
the On State/File Path and the Off State/File Name fields. The status of the relevant DREG works on a
toggle operation linked to the index of the DREG.
Should there be 40 CTRL DREGs be configured in a menu, each DREG will have an index in front of
the display text on the SAM. By entering this index number from the key-panel and pressing ENT, the
DREG status will toggle from the previous status (from on to off if it was on and vice versa).
The maximum number of DREGs catered for in a consecutive menu structure of CTRL
DREGs only, is 99!
220
SAM
IO Type
AIN
this type will display the value of an AIN. The specific AIN IO Number is selected from the I/O Address/
The AIN status can be any number value. To cater for the wide input range/format, the Format field is
used to customise the user required format for each AIN.
AIN Units can be displayed on the SAM ONLY when the AIN descriptors are downloaded to the RTU.
The AIN Units defined in the AIN descriptors are used or the display of the SAM units.
AOT
this type will display the value of an AOT. The specific AIN IO Number is selected from the I/O
Address/Auto Logout Timeout field.
The AOT status can be any number value. To cater for the wide input range/format, the Format field is
used to customise the user required format for each AOT.
AREG
this type will display the value of an AREG. The specific AREG IO Number is selected from the I/O
Address/Auto Logout Timeout field.
The AREG status can be any number value. To cater for the wide input range/format, the Format field
is used to customise the user required format for each AREG.
221
SAM
IO Type
CIN32
this type will display the value of an CIN. The specific CIN IO Number is selected from the I/O Address/
The CIN status can be any number value. To cater for the wide input range/format, the Format field is
used to customise the user required format for each CIN.
FIN
this type will display the value of an FIN. The specific FIN IO Number is selected from the I/O Address/
The FIN status can be any number value. To cater for the wide input range/format, the Format field is used
to customise the user required format for each FIN.
222
SAM
Levels
The Levels fields (1 - 5) contain the actual menu structure of the SAM. Not all level
fields must be used
or need to be used, as long as each index is on a line of its own. Each level represent
a hierarchal
index and a position within the menu level structure.
Referring to the MENU IO type, each entry in the levels of type MENU will create a
unique index
number. This is explained in more detail in Operation.
A level with a lower ranking may not exist without its own upper ranking level!
223
SAM
IO Address/Auto Logout Timeout
This filed serves two purposes.
IO Address
This functionality comes into play when an IO Type of either DIN, DOT, AIN, CIN, FIN, DREG, AREG,
CTRL DOT or CTRL DREG is selected. This field then indicates the corresponding IO number of the
appropriate IO type.
eg. If the IO Type selected was DIN, then an entry in this field of 5 will mean DIN 5.
Range:
One Byte, 1 – 254
Auto Logout Timeout

This functionality is active when an IO Type of AUTO LOGOUT is selected. The value entered in this
field will represent the timeout before the SAM automatically logs out the current user from the RTU if
no key is pressed on the key-panel in seconds.
Range:
One Byte, 1 - 255
Unit:
Seconds
224
SAM
Format
This field is only in effect when an IO Type of AIN is selected. This field selects the format of the value
for readable display of the SAM.
To display any AIN scaled values the relevant AIN Scaling descriptors MUST be
downloaded to the RTU as this is used for the scaling calculations.
Raw Value
This selection type displays the current value of the relevant AIN without any scaling applied to the
result.
Range:
0 – 65535
Positive and Negative Whole Numbers

This selection type displays the positive and negative scaled values of the relevant AIN.
Positive Whole Numbers

This selection type displays only the positive scaled values of the relevant AIN.
0.#
This selection type displays the scaled values of the relevant AIN to a resolution of 1 decimal point.
225
SAM
Format
0.##
This selection type displays the scaled values of the relevant AIN to a resolution of 2 decimal points.
0.###
0.####
0.#####
This selection type displays the scaled values of the relevant AIN to a resolution of 5 decimal points..
226
SAM
On State/File Path
On State
This functionality comes into play when an IO Type of DIN, DOT, DREG, CTRL DOT or CTRL DREG
is selected. This field then indicates the corresponding status of the IO type in readable/explanatory
text when the IO type is active or on.
File Path
This functionality is active when an IO Type of DOC is selected. The value entered in this field will
represent the physical path of an external document to be used in the menu structure.
227
SAM
Off State/File Name
Off State
This functionality comes into play when an IO Type of DIN, DOT, DREG, CTRL DOT or CTRL DREG
is selected. This field then indicates the corresponding status of the IO type in readable/explanatory text
when the IO type is inactive or off.
File Name
This functionality is active when an IO Type of DOC is selected. The value entered in this field will
represent the physical file name and extension (text file) to be used in the menu structure.
228
Test Your Skills
Configure the following:
•Station 250 Connected to the PC
•Create the following IO on the station
•AIN 1 to 3
•DIN 1 to 8
•DOT 1 to 8
•CIN 10
•Create the following IO Map between the Stations
•From Station 10
•DIN 1 to 3 map to DOT 1 to 3 on station 250
•DIN 5 to 6 map to DOT 7 to 8 on station 250
•DIN 8 map to DOT 5 and 6 on station 250
•Station 10 will be communicating via FSK to station 250
•Create the following IO on the station
•AIN 1 to 8
•DIN 1 to 8
•DOT 1 to 8
•Create the following IO Map between the Stations
•From Station 250
•DIN 1 to 8 DOT 8 to 1 on station 10
•AIN 1 map to AOT 12 on station 10
229

SSE Training Module 1

Uploaded by

Document Information

Original Description:

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

SSE Training Module 1

Uploaded by

Copyright:

Available Formats

SSE

SSE not only pride themselves, in producing excellent products to

Specialist System Engineering (SSE) started in 1994 specialising in

With our experienced team of hardware and software engineers, who

▪Types of telemetry equipment.

– Mimics - HMI ( Human machine interface )

Different types of SCADA

• The SCADA developers don’t write drivers for all

A software driver is the “ Translator “ between two different protocols.

Address System Data Sign Bit Check Sum

Different types protocol:

SCADA 01 with SCADA 02 with

➢ Data (RXD, TXD)

➢ Control (RTS, CTS, DCD, DTR, DSR)

➢ Clocks (or timing), is used in synchronous applications (TC, RC, ETC)

oAsynchronous versus synchronous

➢ Async uses start and stop bits to frame every character

Disadvantage: Wastes 20% or more of the available bandwidth,

➢ TXD, RTS, DTR, are outputs

➢ RXD, CTS, DCD, DSR are inputs

➢ Usually implemented in a male connector

oDCE-Data Circuit-terminating Equipment

➢ RXD, CTS, DCD, DSR are outputs

➢ TXD, RTS, DTR are inputs

➢ Usually implemented in a female connector

oConnecting DCE to DTE requires a straight cable

➢ “Straight” refers to signals, not necessarily pins

➢ Standards specify voltages, voltage ranges, and thresholds for signal

oMaximum data rate-often, but not always, specified

oMaximum distance-often, but not always, specified

oUnbalanced electrical interface-referenced to signal ground lead

➢ Low bit rates

➢ Typical application is 19.2 kbps or less over cables up to 15m

oOpen-circuit limits: +3 to 25V, -3 to -25V

➢ The zone between 3V and -3V is defined as undefined in the EIA-232

standard-that is, it is neither zero nor one

➢ Often implemented on other connector types and connector blocks as well

1: Data Carrier Detect (DCD)

•Easy to implement /install •Distance max +/- 30 meters

RS232 RS232 RS 485 RS232

•Easy to implement /install •Distance max 2 Km

RS232 RS232 Optic RS232

•Multi Drop •Expensive

•Distance •Speed ( 1200-2400 Bd)

•Distance ( Compared to Wire ) •Speed ( Lower speed with longer

•Distance •Point to Point communication

GPRS GPRS Site

SCADA SCADA SCADA 31

8 x LED display For digital inputs

8 x LED display for digital Outputs

CD- Carrier Detect – will switch off if Data is

PTT- Press To Talk- Light will switch on when

Test –Will pulse every 2 Sec when normal.

Battery for RTC and NVM

Real Time Clock and Battery

X-Bus or Telemetry Bus

Descriptor Save EEPROMs

RTC Crystal and NVM Switch

Descriptor Save EEPROMs

X-Bus or Telemetry Bus

Flow Control Selections

• Jumper position connects the relevant control line

• This module may NOT be removed