ipRouteDialup

As one serial interface is reserved for the uplink modem connection, three interfaces are available for connecting substations. These can be operated either in point-to-point or party-line communication (unbalanced).

• The dialup adapter has received an ASDU from the substation - for instance a spontaneous indication - the type of which qualifies for setting up a connection, as defined in the configuration. In addition to the ASDU type, a cause of transmission may be configured, which then initiates the dial-up.
• The telegram buffer (as configured in the size parameter) has been filled to a specified limit.
• In predefined cyclic intervals (configurable).

A configurable character string can be sent to support identification of the substation by the control station.

Connection takedown is initiated if either the maximum idle time (i.e. no ASDUs are sent) or the maximum connection time is exceeded. If the reason for connection setup persists after the disconnection, ipRouteDialup automatically calls again after a configurable timeout.

Special measures are taken to prevent buffer overload by the inflow of measured values. Measured values without a time stamp are entered in a separate impulse buffer where each new value overwrites the older so that only the most recent value for each information object is waiting for transmission. When a measured value with time stamp is received, the relevant entry is deleted from the impulse buffer and the new value is entered directly in the normal buffer. But, if configured, a measured value can still trigger dial-up to the control station.

Accurate monitoring of the ASDUs ensures that a temporary connection break-off or other communication interference does not result in data loss. Unacknowledged ASDUs are repeated after the next connection setup, even if they had been sent before.

• 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)

As ipRouteDialup simply passes through ASDUs, information objects need not be configured directly.

ASDU types that initiate dial-up to the control station are configured in a list.

Eligible modem types can be configured here. All modem types shown in the dropdown list have been tested on the system.

The character string for dial-up to the control station is configured here, too. The dial number is taken from a separate list.

The relevant information is shown for each connection separately. In addition to information on the communication state of the link and transport layers, statistical data is given. This includes the number of ASDUs transmitted per minute on a specified connection. For uplink connections, the buffer state is displayed to facilitate fast detection of communication bottlenecks.

Connection setup with ipRouteDialup can be initiated from here, or if a connection is up and running, connection takedown which significantly facilitates the commissioning phase.

The current modem state is also displayed.

• All data to/from ipRoute sent and received via the relevant communication module
• 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 each 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 volume).

(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 [1] 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