SCADAPack E Remote I/O
Technical Reference
2
SCADAPack E Remote I/O Technical Reference
Table of Contents
Part I SCADAPack ES Remote I/O Technical
3
1 Technical
...................................................................................................................................
Support
3
2 Safety ...................................................................................................................................
Information
4
3 Introduction
...................................................................................................................................
& General Information
6
3.1 Description & Indication
..........................................................................................................................................................
LEDs
8
3.2 Rem ote I/O Sw itch
..........................................................................................................................................................
Settings & Ethernet Rem ote I/O and TCP/IP
9
3.3 Tim e Synchronization
..........................................................................................................................................................
& Rem ote I/O Firm w are Updates
10
4 RTU I/O
...................................................................................................................................
Operation
11
4.1 Creation of Rem
..........................................................................................................................................................
ote I/O Points
12
.........................................................................................................................................................
Specific Point Assignment
13
4.1.1 Automatic &
4.2 Rem ote I/O Data
..........................................................................................................................................................
Transfer
14
4.3 RTU Inputs .......................................................................................................................................................... 15
.........................................................................................................................................................
Point Attributes
16
4.3.1 Remote Input
.........................................................................................................................................................
Point Properties
17
4.3.2 Remote Input
4.4 SCADAPack E..........................................................................................................................................................
Output Controls
18
.........................................................................................................................................................
Point Properties
19
4.4.1 Remote Output
4.5 Rem ote I/O Status
.......................................................................................................................................................... 20
Failure
22
4.5.1 Remote I/O.........................................................................................................................................................
5 Port Assignments
................................................................................................................................... 23
5.1 Serial Rem ote..........................................................................................................................................................
I/O
24
5.1.1 Main RTU ......................................................................................................................................................... 25
Unit
26
5.1.2 Remote I/O.........................................................................................................................................................
5.2 Multiple Serial..........................................................................................................................................................
Rem ote I/O Ports
27
5.3 Ethernet Rem..........................................................................................................................................................
ote I/O
29
5.4 Mixed Serial and
..........................................................................................................................................................
Ethernet Rem ote I/O
31
6 Diagnostics
................................................................................................................................... 32
6.1 Main RTU
.......................................................................................................................................................... 33
6.2 Rem ote I/O Unit
.......................................................................................................................................................... 34
7 Additional
...................................................................................................................................
Diagnostics
35
7.1 Diagnostic Display
..........................................................................................................................................................
Session & Start-Up Diagnostics
36
7.2 Rem ote I/O Com
..........................................................................................................................................................
m unication Exchanges
38
SCADAPack ES Remote I/O Technical
I
3
SCADAPack ES Remote I/O Technical
©2013 Control Microsystems Inc.
All rights reserved.
Printed in Canada.
Version: 8.05.4
The information provided in this documentation contains general descriptions and/or technical
characteristics of the performance of the products contained herein. This documentation is
not intended as a substitute for and is not to be used for determining suitability or reliability of
these products for specific user applications. It is the duty of any such user or integrator to
perform the appropriate and complete risk analysis, evaluation and testing of the products
with respect to the relevant specific application or use thereof. Neither Schneider Electric nor
any of its affiliates or subsidiaries shall be responsible or liable for misuse of the information
contained herein. If you have any suggestions for improvements or amendments or have
found errors in this publication, please notify us.
No part of this document may be reproduced in any form or by any means, electronic or
mechanical, including photocopying, without express written permission of Schneider
Electric.
All pertinent state, regional, and local safety regulations must be observed when installing and
using this product. For reasons of safety and to help ensure compliance with documented
system data, only the manufacturer should perform repairs to components.
When devices are used for applications with technical safety requirements, the relevant
instructions must be followed. Failure to use Schneider Electric software or approved
software with our hardware products may result in injury, harm, or improper operating results.
Failure to observe this information can result in injury or equipment damage.
1
Technical Support
Support related to any part of this documentation can be directed to one of the following
support centers.
4
SCADAPack E Remote I/O Technical Reference
Technical Support: The Americas
Available Monday to Friday 8:00am – 6:30pm Eastern Time
Toll free within North America
1-888-226-6876
Direct Worldwide
+1-613-591-1943
Email
TechnicalSupport@controlmicrosystems.com
Technical Support: Europe
Available Monday to Friday 8:30am – 5:30pm Central European Time
Direct Worldwide
+31 (71) 597-1655
Email
euro-support@controlmicrosystems.com
Technical Support: Asia
Available Monday to Friday 8:00am – 6:30pm Eastern Time (North America)
Direct Worldwide
+1-613-591-1943
Email
TechnicalSupport@controlmicrosystems.com
Technical Support: Australia
2
Inside Australia
1300 369 233
Email
au.help@schneider-electric.com
Safety Information
Read these instructions carefully, and look at the equipment to become familiar with the
device before trying to install, operate, or maintain it. The following special messages may
appear throughout this documentation or on the equipment to warn of potential hazards or to
call attention to information that clarifies or simplifies a procedure.
The addition of this symbol to a Danger or Warning safety label
indicates that an electrical hazard exists, which will result in personal
injury if the instructions are not followed.
This is the safety alert symbol. It is used to alert you to potential
personal injury hazards. Obey all safety messages that follow this
symbol to avoid possible injury or death.
SCADAPack ES Remote I/O Technical
5
DANGER
DANGER indicates an imminently hazardous situation which, if not avoided, will
result in death or serious injury.
WARNING
WARNING indicates a potentially hazardous situation which, if not avoided, can
result in death or serious injury.
CAUTION
CAUTION indicates a potentially hazardous situation which, if not avoided, can
result in minor or moderate injury.
CAUTION
CAUTION used without the safety alert symbol, indicates a potentially hazardous
situation which, if not avoided, can result in equipment damage..
PLEASE NOTE
Electrical equipment should be installed, operated, serviced, and maintained only by qualified
personnel. No responsibility is assumed by Schneider Electric for any consequences arising
out of the use of this material.
A qualified person is one who has skills and knowledge related to the construction and
operation of electrical equipment and the installation, and has received safety training to
recognize and avoid the hazards involved.
BEFORE YOU BEGIN
Do not use this product on machinery lacking effective point-of-operation guarding. Lack of
effective point-of-operation guarding on a machine can result in serious injury to the operator
of that machine.
CAUTION
EQUIPMENT OPERATION HAZARD
Verify that all installation and set up procedures have been completed.
Before operational tests are performed, remove all blocks or other temporary
holding means used for shipment from all component devices.
6
SCADAPack E Remote I/O Technical Reference
Remove tools, meters, and debris from equipment.
Failure to follow these instructions can result in injury or equipment
damage.
Follow all start-up tests recommended in the equipment documentation. Store all equipment
documentation for future references.
Software testing must be done in both simulated and real environments.
Verify that the completed system is free from all short circuits and grounds, except those
grounds installed according to local regulations (according to the National Electrical Code in
the U.S.A, for instance). If high-potential voltage testing is necessary, follow
recommendations in equipment documentation to prevent accidental equipment damage.
Before energizing equipment:
Remove tools, meters, and debris from equipment.
Close the equipment enclosure door.
Remove ground from incoming power lines.
Perform all start-up tests recommended by the manufacturer.
OPERATION AND ADJUSTMENTS
The following precautions are from the NEMA Standards Publication ICS 7.1-1995 (English
version prevails):
Regardless of the care exercised in the design and manufacture of equipment or in the
selection and ratings of components, there are hazards that can be encountered if such
equipment is improperly operated.
It is sometimes possible to misadjust the equipment and thus produce unsatisfactory or
unsafe operation. Always use the manufacturer’s instructions as a guide for functional
adjustments. Personnel who have access to these adjustments should be familiar with the
equipment manufacturer’s instructions and the machinery used with the electrical
equipment.
Only those operational adjustments actually required by the operator should be accessible
to the operator. Access to other controls should be restricted to prevent unauthorized
changes in operating characteristics.
3
Introduction & General Information
This manual describes details of the SCADAPack E RTU Remote I/O facilities (known as SCADAPack
ES Remote I/O) that are available for SCADAPack ES and SCADAPack ER RTU's.
It describes operation of Remote I/O using Serial and Ethernet RTU interfaces.
SCADAPack ES Remote I/O Technical
Description & Indication LEDs
8
Remote I/O Switch Settings & Ethernet Remote I/O and TCP/IP
Time Synchronization & Remote I/O Firmware Updates 10
9
7
8
3.1
SCADAPack E Remote I/O Technical Reference
Description & Indication LEDs
Description
Remote I/O is the mechanism provided by a Main SCADAPack ES or SCADAPack ER RTU that
expands its I/O capacity.
SCADAPack ER and SCADAPack 300E RTUs are not supported as Remote I/O units.
When used in Remote I/O configurations, a SCADAPack ER may only be a Main RTU.
A SCADAPack ES may be either a Main RTU, or an Remote I/O Unit. The Main RTU behaves as a
normal RTU, providing the complete range of RTU services. Remote I/O Units provide facilities for
monitoring and controlling I/O on behalf of the Main RTU. Normal RTU facilities, such as ISaGRAF user
applications, data manipulation, Profiling and Trend Sampling are NOT provided by the Remote I/O
units.
Main and Remote I/O units are differentiated by the RTU’s Hex switch settings. See Section Remote I/
O Switch Settings 9 for further information.
Remote I/O systems use SCADAPack ES RTU to RTU communications to provide I/O monitoring and
control facilities. Remote I/O communication is transparent to the user and requires no programming.
The following RTU communication interface types support Remote I/O:
RS-232 Serial Communication
Ethernet Communication
Each Remote I/O system comprises one Main RTU and one or more Remote I/O Units. A Main RTU
can communicate with up to 15 Remote I/O units.
The SCADAPack ES allows multiple Groups of Main RTU / Remote I/O systems to use the same
communication medium (e.g. Ethernet). Up to 15 Main RTUs, each with 15 Remote I/O units may be
connected to the same communication channel. There is no interaction between Remote I/O units in
different groups. Each Remote I/O unit is controlled only by its Main RTU. In addition, there is no
transparent interaction between Main RTUs in different groups. It is possible, however, to use other Main
RTU facilities, such as DNP3 Peer communications, to exchange data between Main RTUs.
Indication LEDs (SCADAPack ES and SCADAPack ER only)
Onboard LEDs are used indicate the presence of Remote I/O communication activity:
Main RTU:
Serial Remote I/O:
Ethernet Remote I/O:
None
Green LED1 indicates Ethernet received data (only when
TCP/IP disabled)
Remote Unit:
Serial Remote I/O:
Red RX LED indicates received data
Yellow TX LED indicates transmitted remote I/O data
Red and Yellow LEDs active as for Remote Unit Serial
Remote I/O.
Green LED1 indicates received Ethernet remote I/O data
Ethernet Remote I/O:
SCADAPack ES Remote I/O Technical
3.2
9
Remote I/O Switch Settings & Ethernet Remote I/O and TCP/IP
Remote I/O Switch Settings
The SCADAPack ES RTU uses the hardware HEX switches to set MAIN and REMOTE I/O Group and
Unit addresses for remote I/O. The HEX switch settings apply for both Serial and Ethernet remote I/O
systems.
Remote I/O is operational on a SCADAPack E RTU when the HEX switch settings are in the range 00 EF. The first switch setting (first hex digit) indicates the Remote I/O Group number. Up to 15 different
Remote I/O groups are supported on the same physical link. The group number is selected by switch
settings 0 – 9, A – E. Each Remote I/O Group needs to have one Main unit and may have multiple
Remote I/O units.
The second switch setting (second hex digit) indicates the Remote I/O Unit number. One MAIN unit is
permitted per Remote I/O group (unit address 0), and up to 15 Remote I/O units may be connected to
the same Main unit, being selected by switch settings 1 – 9, A – F. Each Main and Remote I/O unit in
the same group needs to have a unique unit HEX address switch setting. When multiple
communications interfaces are used for Remote I/O on the same Main RTU unit, Remote I/O units need
to be in the same group in order to communicate with the Main RTU unit. In addition, Remote I/O units
need to have unique unit addresses regardless of which Main RTU unit communications interface they
are connected to.
For normal RTU operation as a Single RTU (ie. A Main RTU unit with no Remote I/O units), it is
recommended that the SCADAPack E HEX Switches be set to “00”.
Switch settings F0-FF are reserved for special SCADAPack E facilities. Remote I/O does not operate in
these modes. For more information see the SCADAPack E Operational Reference manual.
Ethernet Remote I/O and TCP/IP
For SCADAPack E RTU’s, when the’ “Ethernet Function” parameter is set for “TCP/P + RemIO” on the
Main RTU, both Remote I/O and TCP/IP protocols are supported simultaneously on the RTU’s Ethernet
interface. The SCADAPack ER RTU is not supported as an Remote I/O unit.
The RTU’s Remote I/O sub-system uses Ethernet IEEE 802.3 framing with IEEE 802.2 LLC SNAP for
communicating frames between the Main RTU unit and Remote I/O units. TCP/IP communications uses
Ethernet II frames. The SCADAPack E RTU’s Ethernet driver simultaneously supports both frame
formats.
Both Ethernet interfaces on the SCADAPack ES can simultaneously support both TCP/IP and Remote I/
O.
TCP/IP communications are not supported on Remote I/O units and as such cannot be accessed via a
WAN.
10
3.3
SCADAPack E Remote I/O Technical Reference
Time Synchronization & Remote I/O Firmware Updates
Time Synchronization
The Remote I/O units periodically request time synchronization from the Main RTU unit. This occurs to
maintain accuracy of Remote I/O event time-stamps. Remote I/O units request time updates when they
start-up, and every 60 minutes thereafter.
Accuracy of time synchronization between Remote I/O units and the Main RTU units for SCADAPack E
RTU’s is approximately 10mS.
Remote I/O Firmware Updates
The SCADAPack E RTU allows for remote updates of both Boot Monitor and main Operating System
firmware in Remote I/O units. This is done in an automatic manner, so that initiating a firmware update
to the Main RTU, by default will cause attached Remote I/O units to be updated as well. See the
SCADAPack E Firmware Update Technical Reference for details.
SCADAPack ES Remote I/O Technical
4
RTU I/O Operation
The following sections describe the operation of Remote I/O units on the SCADAPack E RTU:
Creation of Remote I/O Points
Remote I/O Data Transfer
RTU Inputs
12
14
15
SCADAPack E Output Controls
Remote I/O Status
20
18
11
12
4.1
SCADAPack E Remote I/O Technical Reference
Creation of Remote I/O Points
Remote I/O unit points are created in the Main RTU under the following conditions:
The Main RTU’s user configuration defines the Remote unit I/O points. This is done via the Data
Concentrator configuration interface on the main RTU. Refer to the SCADAPack E Data
Concentrator Technical Reference for more details.
A Remote I/O unit reports to the Main RTU unit.
Rremote I/O Units provide expansion to the I/O capacity of an RTU Main Unit.
Once Remote I/O points are created in the Main RTU, they are not deleted. If a Remote I/O unit is
removed, or its unit address is changed, the original points remain in the Main RTU point database.
Upon a subsequent Main RTU restart, the I/O points mapped to the remote I/O database are not deleted
if the points are determined to be off-line, as any non-default configurations for these points would be
lost. A complete re-configuration of the Main RTU unit is necessary to remove off-line Remote I/O points.
The point numbering in the main RTU for the Remote I/O points can be assigned in one of two ways:
The point mapping information (i.e. point number, type and quantity) is specifically defined in the
Remote Point Configuration table (see the Data Concentrator page in the SCADAPack E
Configurator).
No point mapping is defined, whereby the main RTU automatically creates a range of points for each
of the physical I/O in the detected Remote I/O Unit.
Refer to the SCADAPack E Configuration Technical Reference manual for more detailed information
regarding the SCADAPack E point numbering methodology.
SCADAPack ES Remote I/O Technical
4.1.1
13
Automatic & Specific Point Assignment
Automatic Point Assignment
Where points in the main are automatically assigned and created (because of absence of Remote
Points Configuration table in the RTU), the points that map to the remote I/O points are located
according to the hex switch offset of the remote I/O unit from that of the main RTU hex switches.
For example, consider that the main RTU has the hex switches set to 20, and consider that there are
two Remote I/O Units grouped with this Main RTU, with hex switches set to 21 and 22 respectively.
Remote I/O Unit 1 (hex switches 21) is fitted with an I/O board having the following I/O capacity:
32 Digital Inputs
16 Digital (Relay) Outputs
12 Analog Inputs
4 Analog Outputs
The main point numbering for Remote I/O Unit “1” is as follows:
DIGITAL IN
DIGITAL OUT
ANALOG IN
ANALOG OUT
COUNTER
101..132
101..116
101..112
101..104
101..132
Remote I/O Unit 2 (hex switches 22) is fitted with an I/O board having the following I/O capacity:
8 Digital Inputs
2 Digital (Relay) Outputs
4 Analog Inputs
0 Analog Outputs
DIGITAL IN
DIGITAL OUT
ANALOG IN
ANALOG OUT
COUNTER
201..208
201..202
201..204
N/A
201..208
Specific Point Assignment
The alternative to the automatic point assignment is to specifically assign the exact point mapping
required. This allows the user to configure the mapped points on the main RTU to be located anywhere
between the maximum local physical point number and point number 50000, i.e. system point boundary.
This approach also allows the user to configure only the points that are being utilised on the remote I/O
unit as opposed to every I/O point, which allows optimisation of main / remote I/O communications. The
RTU data concentrator interface is used to specifically assign mapped remote I/O points on the main
RTU. Refer to the SCADAPack E Data Concentrator Technical Reference for details on how to configure
remote I/O points in this way.
14
4.2
SCADAPack E Remote I/O Technical Reference
Remote I/O Data Transfer
Input and Output remote I/O data is kept synchronized, and the status of the communication link
between Main and Remote I/O units is monitored by way of data polling. When the Main RTU hasn’t
received an unsolicited report from an Remote I/O unit, the Main RTU issues a background poll request
to verify correct operation of the Remote I/O unit.
If a Remote I/O unit is reporting unsolicited data, the Main RTU does not send the background poll
request. After a must poll period, the Main RTU issues a must poll request to a correctly functioning
Remote I/O unit for the purposes of keeping remote I/O data synchronized.
Upon detection of missing communications with its Main RTU, a Remote I/O unit detects
communications inactivity and clears its output data. The following occurs:
Digital Outputs are de-energized
Analog Outputs are set to Minimum Value
The time-outs for the previous conditions are adjustable via RTU System Points. The following table
indicates the system points for each parameter, including the default value.
The System Analog Point values are set in the Main RTU unit, even though some of the operations relate
to operation of Remote I/O units. Any changes to these system point values take effect immediately,
are retained in the SCADAPack E NV memory, and affect operation of Remote I/O on all interfaces
(serial, multiple serial, and/or Ethernet configurations).
System Analog Point
Description
Units
Default Value
50349
Remote I/O “Must” poll time period
Secs
60
50350
Remote I/O “Background” poll time period
Secs
15
50352
Remote I/O Inactivity Timeout
Secs
60
A further type of Main RTU unit poll request is known as a location poll. Where multiple Remote I/O
interfaces are present, the location poll is used to determine which interface the remote I/O device is
connected to. A Delay Measurement request is issued as a location poll to determine the
communication port connected to a remote I/O unit. The location is determined by which port the
remote I/O responds on. The port on which a Remote I/O unit is found is used to communicate with the
Remote I/O in the future. If the Remote I/O unit then reports on a different communication port, the Main
RTU automatically detects and switches operation to the new port. If the Remote I/O unit does not
respond to the location poll request, the next REMOTE IO communication interface is attempted.
If the Remote I/O unit does not respond on any configured Remote I/O interface, the Main RTU does not
attempt to find it again. Rather, the Main RTU puts the relevant Remote I/O unit on-line when it receives
a start-up or operational Unsolicited response from the Remote I/O unit. At this time, the Remote I/O is
assigned to the relevant remote I/O communication port.
In the time between Main RTU unit poll requests, changes in data on Remote I/O units are transferred to
the Main RTU as events, using unsolicited responses. The event data is manipulated at the Main RTU in
the same way as local input events on the Main RTU.
SCADAPack ES Remote I/O Technical
4.3
15
RTU Inputs
SCADAPack E physical input channels on Remote I/O units are managed by the SCADAPack E RTU I/
O interface on the Remote I/O unit. Changes in physical input data on remote I/O units are timestamped by the I/O interface on the remote units.
In the case of digital input remote I/O points, a history of the state and time-stamp of input changes are
forwarded via serial or Ethernet link to the Main RTU unit. The event data is manipulated at the Main RTU
in the same way as local input events.
In the case of analog input remote I/O points, the current value and time-stamp of the recent input
change is forward to the Main RTU unit. The event change deviation point attribute for the remote I/O
analog inputs is set from a global system point in the main unit (firmware versions 7.4-2 and later). The
main units Remote I/O Analog Change Deviation system point is a floating-point number between 0.0
and 100.0%. This system point will be used globally for the analog input Change Deviation for EVERY
remote I/O unit (and their associated analog inputs). To reduce the number of analog input changes that
are reported to the main unit the set this system point to be an appropriate value.
System Analog Point
Description
Units
Default Value
63202
Remote I/O Analog Change Deviation
%
0.0
16
4.3.1
SCADAPack E Remote I/O Technical Reference
Remote Input Point Attributes
The following Attributes are transferred from the point configuration on the Main RTU unit, to the Remote
I/O unit. Changes to the Main RTU configurations for these attributes are sent to the remote I/O
dynamically and take effect immediately.
The Main RTU unit manages any other point attributes for Remote I/O data, as it does for local RTU I/O.
For Digital Input Points:
Invert Point State
De-bounce Time
Events disabled if corresponding COUNTER defined in the database
For Analog Input Points:
The change deviation is loaded into remotes from the single (global) Analogue Change Deviation
system point (see RTU Inputs 15 )
The most recent of multiple analog point changes are reported from the Remote I/O unit to the Main
RTU unit
For Counter Points:
Events enabled if COUNTER defined in Main RTU unit database
Remote I/O unit Counters may be cleared using DNP3 Initialize Data (see SCADAPack E DNP3
Technical Reference manual)
Remote I/O unit Counters may be preset using ISaGRAF “Operate” function (see the SCADAPack E
ISaGRAF Technical Reference manual)
Remote I/O unit Counters cannot be preset to any value other than 0 when using DNP3 Write
commands to Counter objects. A write to a counter object on a remote I/O unit with a non-zero value
will result in the counter value being preset to 0
SCADAPack ES Remote I/O Technical
4.3.2
Remote Input Point Properties
The following point Properties are managed by the Main RTU unit from Remote unit Inputs.
The Main RTU unit manages any other point properties, as for local I/O.
For Digital Input Points & Counter Points:
Off-line / On-line
Point Failed
I/O not Responding [including activation of I/O “Module Bad” system point]
Point state
For Analog Input Points:
Off-line / On-line
Point Failed
I/O not Responding [including activation of I/O “Module Bad” system point]
A/D Reference Check
Point value
17
18
4.4
SCADAPack E Remote I/O Technical Reference
SCADAPack E Output Controls
Requests to control remote output points, whether from ISaGRAF, DNP3, Profiler, etc. are forwarded to
the appropriate Remote I/O unit via serial link or Ethernet interface.
Controls are sent to remote I/O asynchronously to other SCADAPack E operational facilities.
Remote Control Interlock facilities provided by the Main RTU unit operate for Remote I/O in the same
way as Local I/O. For more information see SCADAPack E Operational Reference manual.
No point attributes are transferred from output point configurations on the Main RTU unit, to the Remote
I/O unit. The Main RTU unit manages all point attributes for remote output points.
The Main RTU unit, to stop communications link over-loads if rapid Main RTU unit changes are occurring
for the same remote I/O point, provides output saturation handling. This results in only the most recent
control for each point being sent to the remote I/O. The user should be aware that this may cause
missing intermediate control states or values. In this case, Outputs are updated with the most recent
state or value.
Remote I/O controls are sent under any conditions other than the missing of the communication link
between the Main and Remote I/O units.
SCADAPack ES Remote I/O Technical
4.4.1
Remote Output Point Properties
The following point Properties are managed by the Main RTU unit for remote outputs.
The Main RTU unit manages any other point properties, as for local I/O.
For Digital Output Points:
Off-line / On-line
Point Failed
I/O not Responding [including I/O Module Bad & relay feed-back failure]
Point state
For Analog Output Points:
Off-line / On-line
Point Failed
I/O not Responding [including I/O Module Bad]
Point value
19
20
4.5
SCADAPack E Remote I/O Technical Reference
Remote I/O Status
The following SCADAPack E system points are provided for operational status indication on the Main
RTU Unit for Remote I/O Units.
Where indicated "Config", these system points may be added to RTU point database with complete
point configuration attributes.
Table 4.1: Remote I/O Status System Binary Points
Point
Type
System
Binary
Points
Point
Number
Description
Access
50209
Remote ‘1’ I/O Module Failure
Rd Only / Config
50210
Remote ‘1’ Input Power Supply Low
Rd Only / Config
50211
Remote ‘1’ On-Board Battery Low
Rd Only / Config
50212
Remote ‘1’ Calibration Parameters Invalid
Rd Only / Config
50213
Remote ‘2’ I/O Module Failure
Rd Only / Config
50214
Remote ‘2’ Input Power Supply Low
Rd Only / Config
50215
Remote ‘2’ On-Board Battery Low
Rd Only / Config
50216
Remote ‘2’ Calibration Parameters Invalid
Rd Only / Config
…
50265
Remote ‘F’ I/O Module Failure
Rd Only / Config
50266
Remote ‘F’ Input Power Supply Low
Rd Only / Config
50267
Remote ‘F’ On-Board Battery Low
Rd Only / Config
50268
Remote ‘F’ Calibration Parameters Invalid
Rd Only / Config
50500
Remote I/O Clear Outputs (Remote I/O Mode only:
Internal use)
Write Only
Table 4.2: Remote I/O Status System Analog Points
Point
Type
Point
Number
54600
System
Description
Remote ‘1’ SCADAPack E Type
Access
Read / Write
SCADAPack ES Remote I/O Technical
Analog
Points
54601
Remote ‘1’ SCADAPack E Firmware revision
Read / Write
54602
Remote ‘1’ SCADAPack E Switch Setting
Read / Write
54603
Remote ‘1’ SCADAPack E Processor Board PAL
revision
Read / Write
54604
Remote ‘1’ SCADAPack E Processor Board Boot
Monitor revision
Read / Write
54605
Remote ‘1’ I/O Board 1 Firmware revision
Read / Write
54606
Reserved
…
54698
Remote ‘F’ SCADAPack E Type
Read / Write
54699
Remote ‘F’ SCADAPack E Firmware revision
Read / Write
54700
Remote ‘F’ SCADAPack E Switch Setting
Read / Write
54701
Remote ‘F’ SCADAPack E Processor Board PAL
revision
Read / Write
54702
Remote ‘F’ SCADAPack E Processor Board Boot
Monitor revision
Read / Write
54703
Remote ‘F’ I/O Board 1 Firmware revision
Read / Write
54704
Reserved
21
22
4.5.1
SCADAPack E Remote I/O Technical Reference
Remote I/O Failure
On initial connection with a Remote I/O Unit, the main RTU will issue a “location poll”. This is a short
message (DNP3 Delay Measurement) used to determine the communications latencies between the
main RTU and the remote unit. There will be two attempts to deliver this message each with a timeout of
5 seconds before the remote I/O until is deemed OFFLINE (i.e. communications failed). Once the
Remote I/O unit has been configured (and therefore ONLINE), integrity polls are scheduled at intervals
specified by the “Must poll time” and “Back ground poll time” system points (see Remote I/O Data
Transfer 14 ). There are three attempts for any scheduled integrity poll, each with a timeout of 5 seconds
before the Remote I/O is deemed OFFLINE (i.e. communications failed).
Where a Main RTU communications with an REmote I/O unit fails, the Main RTU unit activates the
Remote I/O Module Failure system point and marks relevant I/O points as I/O Not Responding in the
Main RTU unit point database.
Where an Remote I/O unit’s I/O board fails, the Main RTU point database indicates I/O Not Responding
for each relevant I/O point, but the Remote I/O Module Failure system point is not activated.
When a Remote I/O unit detects loss of communication with the Main RTU unit, it clears its physical
outputs. This results in digital output channels being de-energized, and analog output channels being
minimized. Detection of missing communications occurs according to the settings of the Remote I/O
Inactive Timeout - System Analog Point. See Section Remote I/O Data Transfer 14 .
If there is a failure of any given point on a Remote I/O unit, the failed status will be reported to the main
RTU in the next poll response. Exceptions to this behaviour are noted as follows:
A/D reference failures (for analog inputs) will be reported immediately
Control responses for failed output points will report a failed status to the main RTU.
SCADAPack ES Remote I/O Technical
5
23
Port Assignments
SCADAPack E RTU serial and the optional Ethernet ports can provide connection to Remote I/O
SCADAPack E RTU devices, for the purposes of expanding the I/O capacity of the Main RTU unit.
Using the Remote I/O RTU facility, multiple SCADAPack E RTU units may be arranged such that one
unit is the Main RTU, and the remaining units are Remote I/O units. Remote I/O units appear as I/O
points to the Main unit. The Main unit appears as a large logical RTU made up of its own local I/O, and
I/O from remote units. The Main unit maintains RTU functionality, where as from the user’s perspective,
the Remote unit is a simple I/O device, only. Main and Remote units are determined from the
SCADAPack E Hex Switch settings. For more information see Section Remote I/O Switch Settings
9 .
Serial Remote I/O
24
Multiple Serial Remote I/O Ports
Ethernet Remote I/O
27
29
Mixed Serial and Ethernet Remote I/O
31
24
5.1
SCADAPack E Remote I/O Technical Reference
Serial Remote I/O
The following sections described the use of serial ports on the SCADAPack E for Remote I/O operation:
Main RTU
25
Remote I/O Unit
26
SCADAPack ES Remote I/O Technical
5.1.1
25
Main RTU
A Main RTU unit used in a serial Remote I/O system is characterized by the following:
Unit Address (2nd Hex Switch) needs to be “0”
At least one serial port set as Remote I/O and one or more
Remote I/O Unit(s) connected to the serial port, OR
A Main RTU unit may be configured with multiple Remote I/O serial ports. See Section Multiple
Serial Remote I/O Ports 27
Remote IO ports may be assigned for serial Remote I/O operation to any of the following ports on an
SCADAPack E Main RTU unit:
PORT 0
PORT 1
PORT 2
PORT 3
Daisy chaining serial remote I/O units requires the use of PORT 0 and PORT 1
(see Table 5.1: Remote I/O Unit Communication Port Modes
26
).
26
5.1.2
SCADAPack E Remote I/O Technical Reference
Remote I/O Unit
An Remote I/O unit used in a Serial Remote I/O system is characterized by the following:
Unit Address (2nd Hex Switch) needs to be non-zero, ie. “1”-“9”, “A”- “F”
Port 1 is connected to a communications link to the Main RTU.
Many Remote I/O Unit configurations are fixed. The following table details the serial communication port
usage on an Remote I/O Unit.
Table 5.1: SCADAPack ES Remote I/O Unit Communication Port Modes
PORT 0
PORT 1
PORT 4
DNP3
DNP3
CmdLine
Connect to Port 1
on daisy chained
Remote I/O unit
Connect to Main
RTU unit’s
“Remote IO” port
Connect to ASCII
terminal for
Diagnostics
RS232 (Rts On)
RS232 (Rts On)
RS232 (Rts On)
57600 bps
57600 bps
9600 bps
The Port Format for each serial port is:
Port Format:
8-bit, No-parity, 1-stop-bit
Remote I/O port settings operate with fixed configurations and cannot be altered.
Figure 5.1: Main RTU and Remote I/O Unit (Remote I/O Serial Port)
SCADAPack ES Remote I/O Technical
5.2
27
Multiple Serial Remote I/O Ports
Where multiple Remote I/O serial ports are configured on the same Main RTU, Remote I/O units can be
connected to any serial Remote I/O port. Any port may be used for any mixture of Remote I/O unit
communications. Remote I/O units may be connected in any order. The Main RTU unit automatically
detects communications from a Remote I/O unit on any of the Main RTU’s communication interfaces.
During the start-up process of the Main RTU, it may be required to locate the serial port that the various
Remote I/O units are connected to. This may add some delays to the time required to start-up the Main
RTU while attempts to locate each Remote I/O unit.
It is permitted to change the Remote I/O units to communicate on alternate Main RTU ports, including
when the Main and Remote I/O units are operational. This change s detected automatically by the Main
RTU unit.
EXPANSION I/O Unit #22 hex
Port 1
RS232
Local IO
“Remote IO” Port 0
“Remote IO” Port 2
MAIN RTU Unit #20 hex
RS232
EXPANSION I/O Unit #21 hex
Port 1
Figure 5.2: Main RTU and Remote I/O Units (2 Remote I/O Serial Ports)
Chaining of remote I/O units via serial links is also possible. This provides the ability to connect multiple
Remote I/O units via the same serial connection on a single main RTU unit. In this case, the Main RTU
unit should connect to a REMOTE I/O unit’s Port 1. Port 0 of this Remote I/O unit should be connected
to Port 1 of another Remote I/O unit. Port 0 of the second Remote I/O unit should be connected to Port
1 of the next Remote I/O unit, and so on. Remote I/O units may be interconnected in any order in the
communication chain.
Chaining Remote I/O units may result in increasing the latency of updating I/O changes between Main
RTU unit and Remote I/O unit(s). The impact of this increased latency should be taken into account in
the Remote I/O system design.
28
SCADAPack E Remote I/O Technical Reference
Figure 5.3: Remote I/O Main RTU and Remote I/O Units (1 Remote I/O Serial Port)
SCADAPack ES Remote I/O Technical
5.3
29
Ethernet Remote I/O
Remote I/O facilities may utilize the Ethernet ports on the SCADAPack E rather than serial port(s).
When the Main RTU is connected to a DNP3 Secure Authentication network it is recommended that
Remote I/O not use this same connection. For example:
The Main RTU uses the ETH 1 port for connection with the DNP3 Secure Authentication network
and the Remote I/O uses the ETH 2 port.
The Main RTU uses a serial for connection with the DNP3 Secure Authentication network and the
Remote I/O uses the ETH 1 port.
Correct operation of the Remote I/O Ethernet interface requires the SCADAPack E RTU’s serial
number to be configured as part of the RTU Factory Calibration Procedure. For more information
on the hardware aspects of the Ethernet interface see the relevant SCADAPack E RTU Hardware
Manual.
Apart from this there are no user configurations required at Main RTU or Remote I/O units in order to
utilize the Ethernet interface for Remote I/O. Based upon configurations in the Main RTU unit point
database, the Remote I/O facility will search for Remote I/O units, and can locate them on the Ethernet
interface. Similarly, when Remote I/O units start-up, they will attempt to communicate with a Main RTU
unit on the Ethernet ports.
A Main RTU unit used in an Ethernet Remote I/O system is characterized by the following:
Unit Address (2nd Hex Switch) needs to be “0”
Main RTU with Ethernet option, and one or more:
Remote I/O Unit(s) connected to the Ethernet interface
A Remote I/O unit used in an Ethernet Remote I/O system is characterized by the following:
Unit Address (2nd Hex Switch) needs to be non-zero, ie. “1”-“9”, “A”- “F”
Remote I/O unit connected to Ethernet LAN for communication with Main RTU unit in the same
Group.
30
SCADAPack E Remote I/O Technical Reference
Figure 5.4: Remote I/O Main and Remote I/O Units (Ethernet)
Remote I/O communication is not authenticated. When the Main RTU is connected to a DNP3 Secure
Authentication network it is recommended that Remote I/O not use this same connection. For example:
The Main RTU uses the ETH 1 port for connection with the DNP3 Secure Authentication network
and the Remote I/O uses the ETH 2 port.
The Main RTU uses a serial for connection with the DNP3 Secure Authentication network and the
Remote I/O uses the ETH 1 port.
SCADAPack ES Remote I/O Technical
5.4
31
Mixed Serial and Ethernet Remote I/O
It is possible to mix Remote I/O operation using both Ethernet and Serial interfaces for communication
with different Remote I/O units.
There are no Main RTU unit configurations required in order to utilize the Ethernet interface for Remote I/
O. For the SCADAPack ES RTU, either or both Ethernet interfaces may be used for Remote I/O. A
serial port on the Main RTU unit requires configuration as a “REMOTE IO” port in order to support mixed
communications, i.e. both Ethernet and serial.
During the start-up process of the Main RTU, it will attempt to locate the interface that the various
Remote I/O units are connected to. This may add some delays to the time required to start-up the Main
RTU while attempts are made to locate each Remote I/O unit.
Remote I/O units are searched in order to determine their location. (If a serial interface is not configured
for “REMOTE IO” then the Main RTU unit does not attempt to locate Remote I/O units on that port). The
port search order is as follows:
PORT 0
PORT 1
PORT 2
PORT 3
Ethernet 1
Ethernet 2
It is permitted to change the Remote I/O units to communicate on alternate Main RTU interfaces,
including when the Main and Remote I/O units are operational. This change is detected automatically
by the Main RTU unit.
Figure 5.5: Remote I/O Main and Remote I/O Units (Mixed Serial & Ethernet)
32
6
SCADAPack E Remote I/O Technical Reference
Diagnostics
Remote I/O Diagnostics
Main Unit
33
Remote I/O Unit
34
SCADAPack ES Remote I/O Technical
6.1
33
Main RTU
By default, diagnostic messages relevant to Remote I/O communications are disabled on the Main RTU.
Remote I/O communication diagnostics can be enabled on the Remote I/O port(s) using DNPDIAG
command, but generally will not remain active following DNP3 Warm Restart, RTU Initialization or powerup.
At start-up, the Remote I/O diagnostic modes are disabled, so it is necessary to re-enter the diagnostic
filter command to enable for a Remote I/O channel diagnostics each time the RTU starts in order to view
Remote I/O diagnostics.
HINT: This does not apply if the RTU is in SYSDIAG OVERRIDE mode. I.e. the previous Remote I/O
diagnostics state is preserved only if system diagnostic override mode is enabled at the time of an RTU
sub-system or system-wide restart.
To maximize the effectiveness of LED indication for the Main RTU, Remote I/O communications are NOT
indicated on the Main unit’s TX and RX LED’s. Remote I/O communications received on the Ethernet
interface only activate the Green LED1 if TCP/IP is disabled for the Ethernet interface.
For further information on using Main Unit diagnostics see SCADAPack E Operational Reference
manual.
As SCADAPack ES Remote I/O uses DNP3 communications, the DNPDIAG command can be useful
for diagnostic purposes
The DNPDIAG command is used to filter DNP3 diagnostics displays when in Diagnostic Session display
mode (use DIAG to return to diagnostic mode).
The format of DNPDIAG command is described in the SCADAPack E Operational Reference manual.
34
6.2
SCADAPack E Remote I/O Technical Reference
Remote I/O Unit
LED indication is provided on Remote I/O units for serial and Ethernet communication links. The
Remote I/O unit’s TX and RX LED’s indicate Remote I/O communication traffic for both serial and
Ethernet Remote I/O links. In addition, Ethernet Remote I/O communications indicate received Ethernet
frames from a Main RTU unit using Green LED1.
As SCADAPack ES Remote I/O uses DNP3 communications, the DNPDIAG command can be useful
for diagnostic purposes
As the automatic configuration of Remote I/O units includes a command line interface on PORT 4,
Remote I/O diagnostics can be viewed using the Diagnostic Display session (use the DIAG command)
from the command line on the Remote I/O unit(s).
The DNPDIAG command is used to filter DNP3 diagnostics displays when in Diagnostic Session display
mode (use DIAG to return to diagnostic mode).
The format of DNPDIAG command is described in the SCADAPack E Operational Reference manual.
By default, diagnostic messages relevant to Remote I/O communications are disabled, but these can be
enabled using the following command prior to entering the Diagnostic Display session.
DNPDIAG ENABLE 1 APPL
DNPDIAG ENABLE REM_ETH APPL
for Serial Remote I/O
for Ethernet Remote I/O Interface 1
DNPDIAG ENABLE REM_ETH_2 APPL for Ethernet Remote I/O Interface 2
This enables application layer diagnostics on the Remote I/O port(s) to the Main RTU unit.
SCADAPack ES Remote I/O Technical
7
35
Additional Diagnostics
A range of additional diagnostic information is provided by the SCADAPack E RTU in order to facilitate
trouble-shooting of Remote I/O.
Diagnostic Display Session & Start-Up Diagnostic
Remote I/O Communication Exchanges
38
36
36
7.1
SCADAPack E Remote I/O Technical Reference
Diagnostic Display Session & Start-Up Diagnostics
Diagnostic Display Session
A Remote I/O Unit, through the Diagnostic Display session, may indicate exceptional RTU operating
conditions. This is available through the Cmd Line port on the RTU and using the “DIAG” command from
an ASCII terminal plugged into that port.
RTU diagnostics use the following format to assist in identifying messages from various SCADAPack E
tasks:
Task-name>>diagnostic text
Start-Up Diagnostics
At start-up the SCADAPack E can display information about its start-up sequence and configuration.
For information on Main RTU unit diagnostics see SCADAPack E Operational Reference Manual. The
following section indicates typical start-up diagnostics for a REMOTE I/O unit.
SCADAPack E Fi r mwar e 8. 05. 3
Bui l d 5. 3. 146
Copyr i ght ( C) Cont r ol Mi cr osyst ems I nc. and l i censor s
Cont r ol l er
CPU speed
Fi r mwar e ver si on
I SaGRAF 3 ver si on
I SaGRAF 5 ver si on
RTOS
TCP/ I P ver si on
BOOT MONI TOR ver si on
RTU PAL ver si on
Ser i al Number
Et her net MAC Addr
Et her net MAC Addr 2
:
:
:
:
:
:
:
:
:
:
:
:
SCADAPack ES Model ( 586)
100 MHz
8. 05. 3. 146
3. 55
2010. 5. 23. 710_( 100908)
G1. 13
4. 1
2. 15
2. 0
65535
00- 03- 74- 01- FF- FF
00- 03- 74- 02- FF- FF
St ar t up at : 13/ 11/ 2012 14: 45: 11. 169
Reset Reason mask
: 0x0006
Task Wat chdog mask
: 0x0000
I O_PROCESSOR>>Task St ar t i ng
CMDLI NE>>Task st ar t ed
DNP3>>Task St ar t ed
<+++ [ 176]
Bui l d DNP3 Message: NULL Response
<+++ [ 176]
I nser t r equest i n queue: NULL Response
<=== [ 176]
Appl i cat i on Header , Unsol i ci t ed
FI R( 1) FI N( 1) CON( 1) UNS( 1) SEQ# 0 I I N( 0x0090)
<=== [ 176]
I I N Bi t s:
I I N1. 7 Devi ce Rest ar t
I I N1. 4 Ti me Synchr oni zat i on Requi r ed
DNP>>Bui l di ng Event l i st s. . .
DNP>>Fr ee Event Pool si ze: 5000
I O_PROCESSOR>>Task St ar t ed
C: \ >
SCADAPack ES Remote I/O Technical
37
38
7.2
SCADAPack E Remote I/O Technical Reference
Remote I/O Communication Exchanges
The following are typical exchanges between a single MAIN RTU and REMOTE I/O unit:
START-UP INDICATION RECEIVED FROM REMOTE I/O UNIT
~~~> ch01 00001~>00000 APPLICATION HEADER - UNSOLICITED RESPONSE
First:1 Final:1 Confirm:1 Sequence:17 IIN:0x9200
IIN: Device Restart
IIN: Time synchronization required from the master
IIN: Class 1 report by exception data available
<~~~ ch01 00001<~00000 APPLICATION HEADER - CONFIRM
First:1 Final:1 Confirm:0 Sequence:17
MAIN RTU INITIALIZING COMMUNICATION WITH REMOTE I/O UNIT
<~~~ ch01 00001<~00000 APPLICATION HEADER - WRITE for user request:
CLEAR RESTART IIN (CAUSED BY RESTART IIN)
First:1 Final:1 Confirm:0 Sequence:12
~~~> ch01 00001~>00000 APPLICATION HEADER - RESPONSE TO REQUEST
First:1 Final:1 Confirm:0 Sequence:12 IIN:0x1200
IIN: Time synchronization required from the master
IIN: Class 1 report by exception data available
<~~~ ch01 00001<~00000 APPLICATION HEADER - DELAY MEASUREMENT
First:1 Final:1 Confirm:0 Sequence:13
~~~> ch01 00001~>00000 APPLICATION HEADER - RESPONSE TO REQUEST
First:1 Final:1 Confirm:0 Sequence:13 IIN:0x1200
IIN: Time synchronization required from the master
IIN: Class 1 report by exception data available
<~~~ ch01 00001<~00000 APPLICATION HEADER - WRITE for user request:
CLEAR RESTART IIN (CAUSED BY RESTART IIN)
First:1 Final:1 Confirm:0 Sequence:14
~~~> ch01 00001~>00000 APPLICATION HEADER - RESPONSE TO REQUEST
First:1 Final:1 Confirm:0 Sequence:14 IIN:0x1200
IIN: Time synchronization required from the master
IIN: Class 1 report by exception data available
<~~~ ch01 00001<~00000 APPLICATION HEADER - WRITE for user request:
WRITE INITIAL SYSTEM TIME
First:1 Final:1 Confirm:0 Sequence:15
~~~> ch01 00001~>00000 APPLICATION HEADER - RESPONSE TO REQUEST
First:1 Final:1 Confirm:0 Sequence:15 IIN:0x0200
IIN: Class 1 report by exception data available
<~~~ ch01 00001<~00000 APPLICATION HEADER - DELAY MEASUREMENT
First:1 Final:1 Confirm:0 Sequence:00
SCADAPack ES Remote I/O Technical
~~~> ch01 00001~>00000 APPLICATION HEADER - RESPONSE TO REQUEST
First:1 Final:1 Confirm:0 Sequence:00 IIN:0x0200
IIN: Class 1 report by exception data available
<~~~ ch01 00001<~00000 APPLICATION HEADER - WRITE for user request:
WRITE SYSTEM TIME(CAUSED BY DLY MEASUREMENT CALLBACK)
First:1 Final:1 Confirm:0 Sequence:01
~~~> ch01 00001~>00000 APPLICATION HEADER - RESPONSE TO REQUEST
First:1 Final:1 Confirm:0 Sequence:01 IIN:0x0200
IIN: Class 1 report by exception data available
MAIN RTU SENDING CONFIGURATION TO REMOTE I/O UNIT
<~~~ ch01 00001<~00000 APPLICATION HEADER - WRITE for user request:
FILE DOWNLOAD
First:1 Final:1 Confirm:0 Sequence:02
~~~> ch01 00001~>00000 APPLICATION HEADER - RESPONSE TO REQUEST
First:1 Final:1 Confirm:0 Sequence:02 IIN:0x0200
IIN: Class 1 report by exception data available
<~~~ ch01 00001<~00000 APPLICATION HEADER - WRITE for user request:
FILE DOWNLOAD
First:1 Final:1 Confirm:0 Sequence:03
~~~> ch01 00001~>00000 APPLICATION HEADER - RESPONSE TO REQUEST
First:1 Final:1 Confirm:0 Sequence:03 IIN:0x0200
IIN: Class 1 report by exception data available
<~~~ ch01 00001<~00000 APPLICATION HEADER - WRITE for user request:
EXEC COMMAND
First:1 Final:1 Confirm:0 Sequence:04
~~~> ch01 00001~>00000 APPLICATION HEADER - RESPONSE TO REQUEST
First:1 Final:1 Confirm:0 Sequence:04 IIN:0x0200
IIN: Class 1 report by exception data available
MAIN RTU POLLING REMOTE I/O UNIT INPUT DATA
<~~~ ch01 00001<~00000 APPLICATION HEADER - READ for user request:
INTEGRITY DATA POLL (CAUSED BY PERIODIC POLL)
First:1 Final:1 Confirm:0 Sequence:05
~~~> ch01 00001~>00000 APPLICATION HEADER - RESPONSE TO REQUEST
First:1 Final:1 Confirm:1 Sequence:05 IIN:0x0000
<~~~ ch01 00001<~00000 APPLICATION HEADER - CONFIRM
First:1 Final:1 Confirm:0 Sequence:05
MAIN RTU SENDING OUTPUT CONTROL DATA TO REMOTE I/O UNIT
<~~~ ch01 00001<~00000 APPLICATION HEADER - DIRECT OPERATE
39
40
SCADAPack E Remote I/O Technical Reference
First:1 Final:1 Confirm:0 Sequence:06
~~~> ch01 00001~>00000 APPLICATION HEADER - RESPONSE TO REQUEST
First:1 Final:1 Confirm:0 Sequence:06 IIN:0x0200
IIN: Class 1 report by exception data available
<~~~ ch01 00001<~00000 APPLICATION HEADER - DIRECT OPERATE
First:1 Final:1 Confirm:0 Sequence:07
~~~> ch01 00001~>00000 APPLICATION HEADER - RESPONSE TO REQUEST
First:1 Final:1 Confirm:0 Sequence:07 IIN:0x0200
IIN: Class 1 report by exception data available
REMOTE I/O UNIT SENDING CHANGE DATA TO MAIN RTU
~~~> ch01 00001~>00000 APPLICATION HEADER - UNSOLICITED RESPONSE
First:1 Final:1 Confirm:1 Sequence:18 IIN:0x0000
<~~~ ch01 00001<~00000 APPLICATION HEADER - CONFIRM
First:1 Final:1 Confirm:0 Sequence:18
SCADAPack ES Remote I/O Technical
41