Router for IEC 870-5-101 and IEC 870-5-104 protocols
start price 970,- €
ipRoute Use Cases
ipRoute enables fast and cost-efficient coupling of control stations and
RTUs using the IEC 60870-5-101 and IEC 60870-5-104 communication standards, profiting
from the fact that these protocols are highly compatible at the application level.
Please go to ipRoute Use Cases for examples of the various applications of
|ipRoute is a router-based system. The ASDU (Application Service Data
Unit) data packet exchange between the communication components is
transparent. The IEC 60870-5-101 link layer functions and the IEC 60870-5-104
transport layer functions are however directly executed by ipRoute, as
shown in the diagram.
The data packets sent by a control station are switched through to either all
or only a specified substation depending on the configuration. Conversely, the
data packets received by a substation are transmitted to all or specified
The decision where to transmit a packet is made by using the corresponding
common address of ASDU.
This transparent operation of ipRoute makes system integration fast and simple.
System configuration is reduced to a few parameters such as the baud rate or
information object address length. Configuration of the individual information
objects is not required.
ipRoute supports nearly all the link and transport layer functions defined by
the IEC 60870-5-101 and IEC 60870-5-104 protocols. It also allows dial-up connections to
The various protocols can be combined as required, enabling even complex
network to be implemented.
IEC 870-5-101 balanced, slave
|For connecting control stations via a conventional serial leased line. The "balanced" transport procedure is used.
Several V.24 interfaces for connecting a DCE (Data Communication
Equipment) are provided.
IEC 870-5-101 unbalanced, slave
|For connecting control stations via a conventional serial leased
line, using the "unbalanced" mode on the transport layer.
Several V.24 interfaces for connecting a DCE are provided.
IEC 870-5-104 server
|For connecting one or more IEC 870-5-104 control stations via
Ethernet TCP/IP. Data can be fed to the control connection lines
individually (1 of n) or simultaneously to all. ipRoute supports the
configuration of several IP addresses and different port settings. The
physical link is implemented with a 100BaseT port.
IEC 870-5-101 balanced, master
|For connecting substations via a conventional serial leased line
using balanced transmission mode.
IEC 870-5-101 unbalanced, slave
|For connecting substations via conventional serial leased line using
the unbalanced transmission mode. Supports the simultaneous connection
of several substations.
IEC 870-5-101, dialup, master
|For connecting substations via dialup lines. Although not supported
by the IEC 870-5-101 standard, this communication mode is gaining in
popularity. The protocol can manage several dialup modems and several
dialup slaves. The transmission mode can either be balanced or
IEC 870-5-104, client
|For connecting IEC 870-5-104 based substations via TCP/IP. It
supports both the connection of redundant devices and redundant
ipRoute is a very powerful tool offering a complete range of
functionalities that support its integration in specialized environments.
|ipRoute transmits ASDUs transparently without interpreting them.
This enables ASDUs from the private part of the standard to be
exchanged, without the necessity of prior configuration.
|Configuration of different
|The lengths of the common ASDU (CA = Common Address of ASDU), the cause of transmission and the information object address (IOA) can be configured
differently and may not be the same.
IEC 104 and IEC 101
|ipRoute supports conversion between monitoring direction ASDU types
with long time stamp (M_SP_TB_1, M_DP_TB_1, etc.) and ASDU types with
short time stamp (M_SP_TA_1, M_DP_TA_1, etc.) and vice versa. It
also supports conversion between control direction ASDU types with long
time stamp (C_SC_TA_1, C_DC_TA_1, etc.) and ASDU types without timestamp
(C_SC_NA_1, C_DC_NA_1, etc.) and vice versa. Additionally an individual
size of originator address can be specified for each communication
module. By means of this functionality the most of the differences
between IEC 60870-5-104 and IEC 60870-5-101 devices can be eliminated.
|Intelligent data flow
and bandwidth adjustment
|ipRoute offers intelligent data flow control to prevent
unnecessary data buffering. Should the connection to the control station
fail or the data flow be interrupted by the master, ipRoute
automatically stops the data transmission to all downlink connections.
This shifts buffering to the substation as much as possible.
If master connections are slower than slave connections, ipRoute
data flow control automatically slows down the slave connections to
prevent buffer overflow.
The ASDU TTL (time to live) monitoring which can be configured flexibly
ensures that no data is needlessly transmitted to the master and - this is
of particular importance with respect to commands - to the slave or
Accurate monitoring of acknowledged ASDUs prevents loss of data units in
case of temporary connection failures or communication interferences.
Unacknowledged ASDUs are repeated after the next connection set-up, even
if they had already been transmitted.
||ipRoute allows ASDU filtering in control and monitoring
directions based on the ASDU address (Common ASDU address). In control
direction (downlink), ASDUs may either be sent to all or only to
specified ASDU addresses. Broadcast ASDUs are dispatched to all
connected devices. In monitoring direction, the ASDUs are generally sent
to all superordinate systems. A filter may also be configured for each
uplink connection, so that only certain ASDUs are passed on.
||As the master does not directly register a substation connection
failure, ipRoute allows the automatic triggering of a general poll
to the substations after the next connection setup.
||In addition, the slave connection status can be signaled to the
master using a virtual RTU. In this case
ipRoute behaves like a full IEC-101/104 slave.
||ipRoute allows clock synchronization of substations. The ipRoute
internal clock can be synchronized via NTP or IEC. Following its own synchronization,
any connected substations
||In order to meet higher data reliability requirements, ipRoute can be
used with a second device and provide the necessary redundancy (see also ipRoute Use Cases
for references). Redundancy coupling is either implemented via a
serial connection or the Ethernet. Our proprietary channel switch CS
can be used for connecting serial communication lines.
System configuration is executed completely in a web browser.
No other special configuration tools are required, a normal notebook with a
network interface card and web browser are all that is needed.
||The first page provides access to all the relevant ipRoute
functions and shows the general system state at a glance. These functions
- Backup and restore the complete configuration
- Software upgrade
- Edit configuration parameters
- Start up and stop the system
- Access diagnostic data (see also diagnostics)
- Access current log files (see also logging)
|System configuration involves only a few parameters.
In addition to some general system parameters, the link and transport modules need to be
configured for each transmission direction.
simply switches through ASDUs, information objects need not be
||This is the configuration page of the IEC104Server module.
In addition to general IEC 870-5-104 parameters, the client IP addresses can
be configured here enabling the clients to communicate with ipRoute.
|This is the configuration page for the
The diagnostic display offers a quick and detailed overview of
the communication state on all configured connections.
||The "Diagnostics" button on the first page
provides access to
diagnostic information. The most important information is displayed in plain
text format with the time in a clear easy to read way. Colored highlights
indicate an ok / not ok status.
The relevant information is shown for each
connection separately. In addition to the information on the communication state of the
link and transport layers, statistical data is given, including the
number of ASDUs transmitted per minute on a specified connection. For uplink
connections, the buffer state is displayed to facilitate fast detection of
With all communication applications, it is always essential
to know which data is transmitted via a protocol and how the data is
converted from one protocol to another. And it is even more important when
problems occur with transmission. ipRoute features logging and archiving
functions for all data traffic.
||ipRoute allows you to keep track of the system state and
information flow inside the converter by recording and archiving all
information passing through a module for a given time period. The following data
can be recorded:
- All data to/from ipRoute sent and received via the relevant
- System messages, i.e. connection break-off,
communication error messages etc.
- Configuration and software error messages
The range of data recorded is defined by the logging level. This can be
changed dynamically (at runtime) or statically (in the configuration) for
The logging level defines the
representation format for the sent or received information. Data can be
represented either in hexadecimal code or in decoded, symbolic form or both.
This example shows the content of a logfile generated from the
IEC104 server module.
Data is stored directly in the easy to read ASCII
format. Logfiles can be
downloaded via a web interface for offline diagnosis. Or you can keep
track of the communication online via the TCP/IP "telnet" service.
All recorded data is archived cyclically, enabling you to keep track of
communication over a period of days or even weeks (depending on the data
(2): << [1/1] I-FRAME NS=8377 NR=4 DATA=<01 02 03 00 01 00 0
(2): << [1/1] I-FRAME NS=8378 NR=4 DATA=<01 02 03 00 01 00 0
08.03.05 14:55:11 up1 [1/1] path disconnected !
08.03.05 14:55:11 up1  connection aborted !
08.03.05 14:57:39 up1 [1/1] path connected !
08.03.05 14:57:39 up1 [1/1] connection established with 192.
(2): >> [1/1] LEN=4 STARTDT ACT
(2): >> [1/1] LEN=20 I-FRAME NS=0 NR=0 DATA=<67 01 06 00 FF
(2): >> [1/1] LEN=14 I-FRAME NS=1 NR=0 DATA=<64 01 06 00 FF
(2): << [1/1] STARTDT CON
(2): << [1/1] I-FRAME NS=0 NR=2 DATA=<67 01 07 00 FF FF 00 0
(2): << [1/1] I-FRAME NS=1 NR=2 DATA=<01 02 03 00 01 00 02 0
(2): << [1/1] I-FRAME NS=2 NR=2 DATA=<64 01 07 00 01 00 00 0
(2): << [1/1] I-FRAME NS=3 NR=2 DATA=<01 3B 03 00 01 00 02 0
(2): << [1/1] I-FRAME NS=4 NR=2 DATA=<01 3B 03 00 01 00 01 0
(2): << [1/1] I-FRAME NS=5 NR=2 DATA=<01 3B 03 00 01 00 02 0
(2): << [1/1] I-FRAME NS=6 NR=2 DATA=<01 3B 03 00 01 00 02 0
(2): << [1/1] I-FRAME NS=7 NR=2 DATA=<01 3B 03 00 01 00 01 0
(2): >> [1/1] LEN=4 S-FRAME NR=8
(2): << [1/1] I-FRAME NS=8 NR=2 DATA=<01 01 03 00 01 00 02 0
(2): << [1/1] I-FRAME NS=9 NR=2 DATA=<01 02 03 00 01 00 01 0
These requirements ensure successful integration of IEC 870-5-101/104
If these requirements cannot be met, ipConvLite or ipConv are
- ASDU addresses used must be unambiguous and unique for all connections,
multiple assignations are not allowed.
- ASDU types used for the control station or substations must be compatible.
This can be ensured by matching interoperability lists. ipRoute supports
the conversion of following ASDU types (the behaviour is configurable):
- monitoring direction ASDU types with long time stamp (M_SP_TB_1,
M_DP_TB_1, etc.) into ASDU types with short time stamp (M_SP_TA_1,
M_DP_TA_1, etc.) and vice versa
- control direction ASDU types with long time stamp (C_SC_TA_1, C_DC_TA_1,
etc.) into ASDU types without timestamp (C_SC_NA_1, C_DC_NA_1, etc.) and vice
- test command ASDU with long time stamp C_TS_TA_1 into test command ASDU
without timestamp C_TS_NA_1 and vice versa
We would be more than pleased to offer our support to assist you in checking these requirements.
|SEC2||Compact controller mountable on a DIN-rail with a very attractive price|
|MEC2||Powerful midrange embedded controller with a GPRS/UMTS cellular modem module (optional)|
|CS||Channel switch for coupling of two redundant devices to one communication line|
|Iran Gas Project|
|BLS Lötschbergtunnel II, Switzerland|
|Switzerland||ipConv ipRoute ||IEC 60870-5-104, Master / IEC 60870-5-104, Slave / SNMP, Client / |
|BLS AlpTransit - Lötschbergtunnel|
|Switzerland||ipConv ipRoute ||OPC DA 3.0, Server / IEC 60870-5-104, Slave / IEC 60870-5-101, Master / IEC 60870-5-104, Master / SNMP, Client / |
|E.ON Interconnection Karlsfeld/Lehrte|
|RWE Mosel Hydro Power Stations|
|Germany||ipConvOPC ipRoute ||OPC DA 3.0, Server / IEC 60870-5-104, Master / |
|Germany||ipConv ipRoute ||ANSI X3.28, Master / IEC 60870-5-104, Slave / |