...
- The originator ASDU address is not present.
- ASDU address is 1 byte, it is defined as the station address. ASDU addresses of all stations on one line must be different.
- The cause of transmission is 1 byte (does not contain the Originator ASDU address).
- The information object address is 2 bytes, it is defined as an I/O tag address.
...
- Communication protocol "IEC 870-5-101 balanced", "IEC 870-5-101 unbalanced primary (Master)" or "IEC 870-5-101 unbalanced secondary (Slave)".
- The station address is a decimal number in the range 0 - 255 and is used in the protocol as the ASDU address. It can be specified as a decimal number or as a hexadecimal number with a hash at the beginning (e.g. #0A).
- The synchronization of the station real-time may be enabled also for the protocols "master" and "balanced - station A (controlling)". Set the synchronization period to a nonzero value. The synchronization is executed by ASDU 103 "Clock synchronization command" in the local time according to settings of the D2000 System.
The Browse button opens a browsing dialog for the station address. If the communication is functional, a dialog with the ASDU addresses received so far is displayed. The Refresh button can be used to clear the list of received ASDU addresses.
...
Note: in the case of the "slave" and "balanced" protocols, if an Interrogation (ASDU 100) or Counter Interrogation (ASDU 101) command arrives for the "broadcast" address (hexadecimal FF or FFFF according to the Link Address parameter), data from all stations will be sent.
| Kotva | ||||
|---|---|---|---|---|
|
...
Configuration dialog box - tab Protocol parameters.
They influence some optional parameters of the protocol. The following station protocol parameters can be set:
Table 1
Configuration dialog box - tab Protocol parameters.
They influence some optional parameters of the protocol. The following station protocol parameters can be set:
Table 1
| Parameter | Meaning |
|---|
| ParameterMeaningUnit | Default value | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Common link address. | - | 1 | ||||||||||||||||||
| Length of ASDU address. | 1/2 byte(s) | 1 | ||||||||||||||||||
| Length of common link address. | 1/2 byte(s) | 1 | ||||||||||||||||||
| Length of info object address. | 1/2/3 byte(s) | 2 | ||||||||||||||||||
| Length of "Cause Of Transmission". | 1/2 byte(s) | 1 | ||||||||||||||||||
| The delay between request retry in case of a communication failure. | - | 2 | ||||||||||||||||||
| The delay between retry of call in case of a communication error. | ms | 100 millisecond | ||||||||||||||||||
| Delay after sending the request before reading the response. | ms | 100 millisecond | ||||||||||||||||||
| Delay between response readings until it is completed. | ms | 500 millisecond | ||||||||||||||||||
| Retry count of response reading until it is completed. | - | 6 | ||||||||||||||||||
| Delay of next call "Request user data class 1/2" if no data have been received (only master). | ms | 300 millisecond | ||||||||||||||||||
| Interval of connection monitoring. If no valid data have not been received, station status will go to a communication error. Switching of redundant devices in case of SerialOverUDP Device Redundant line (only slave). | ms | 5 sec. | ||||||||||||||||||
| The switching interval of the redundant devices MOXA NPort in case of communication error (only master, balanced). | sec. | 10 | ||||||||||||||||||
| Set flags FI..FL according to the source of line. If SerialOverUDP System+Line Redundant is used, the values will have these flags:
Note: Flag was used in communication with redundant systems to distinguish the wrong values that were sent by a partner system, which was supposed to be passive and not to send nothing. | - | NO | ||||||||||||||||||
| Activation of parameter results in ignoring flags FA..FH for output I/O tags. If this parameter is turned off, flags FA..FH are mapped to individual bits of a quality byte. | - | NO | ||||||||||||||||||
| Interval of request sending "Test function for link" if timeout elapsed and no data telegrams were transferred (balanced only). | sec. | 10 | ||||||||||||||||||
| Kotva | sv | sv | Single Value In Spontaneous AnswerWhen sending spontaneous changes, these will be sent one-per-ASDU and they will not be cumulated into longer packets. The parameter was implemented to handle a bug in a particular TM1703mic. | - | NO | ||||||||||||||||
| Kotva | dc | dc | Data Classelapsed and no data telegrams were transferred (balanced only). | sec. | 10 | ||||||||||||||||
| When sending spontaneous changes, these will be sent one-per-ASDU and they will not be cumulated into longer packets. The parameter was implemented to handle a bug in a particular TM1703mic. | - | NO | ||||||||||||||||||
| The class used for sending data (slave only). IEC 101 Master sends Class1 (high priority) and Class2 (normal) read data requests. Slave responds to them with data or a message that it has no data. In both Class1 and Class2 responses there is an ACD flag that the slave has Class1 data available. If set, the IEC 101 Master will then request Class1 data. The parameter affects behavior as follows:
The default value of the parameter is Class1. | - | Class1&2 Class1 Class2 Prio reply | ||||||||||||||||||
| Discard received data before sending a response (only slave). If a correct request is received and the IEC 101 Slave wants to send a response, it will clear the incoming queue before sending, if the queue has data in it. This parameter serves as a protection against various data duplications due to communication partner errors (e.g. OSI Monarch with RtuPing running during switching of active communication line). | - | NO | ||||||||||||||||||
| Filtering multiple spontaneous values of the same I/O tag when sending (only slave, balanced). If some I/O tags change so fast that there would be multiple values of the same I/O tag in one response to a data request, activating this parameter causes only one (latest) spontaneous value to be sent. See also the description of the Filter Minimum parameter. | NO | |||||||||||||||||||
| The number of requests in the output queue at which value filtering is activated, if enabled by the Filter Spontaneous Values parameter. This parameter allows value filtering to be activated only in error conditions (e.g. excessive value generation in the D2000 CALC process) and not during normal operation. | - | 0 | The class used for sending data (slave only). IEC 101 Master sends Class1 (high priority) and Class2 (normal) read data requests. Slave responds to them with data or a message that it has no data. In both Class1 and Class2 responses there is an ACD flag that the slave has Class1 data available. If set, the IEC 101 Master will then request Class1 data. The parameter affects behavior as follows:
The default value of the parameter is Class1. | - | Class1&2 Class1 Class2 Prio reply | |||||||||||||||
| Kotva | sr | sr | Single RequestDiscard received data before sending a response (only slave). If a correct request is received and the IEC 101 Slave wants to send a response, it will clear the incoming queue before sending, if the queue has data in it. This parameter serves as a protection against various data duplications due to communication partner errors (e.g. OSI Monarch with RtuPing running during switching of active communication line). | - | NO|||||||||||||||||
| Type of sent confirmation to write value (only slave, balanced). | - 7(CONF) 10(TERM) 7(CONF) and 10(TERM) | 7(CONF) | ||||||||||||||||||
| Type of record confirmation to be accepted successfully (only master, balanced). | - 7(CONF) 10(TERM) 7(CONF) or 10(TERM) | 7(CONF) or 10(TERM) | ||||||||||||||||||
| Limitation of data packet size (only slave, balanced). | bytes | 220 | ||||||||||||||||||
| Setting a bit DIR in balance mode (only balanced). | Station A(Controlling) Station B(Controlled) | Station A(Controlling) | ||||||||||||||||||
| Send single-byte ACK preferentially (0xE5-byte ACK preferentially (0xE5). | YES/NO | NO | ||||||||||||||||||
| Send the call 100 and counter values on general interrogation (only slave, balanced). | YES/NO | YES | ||||||||||||||||||
| Send "end of interrogation command" to all ASDU (only slave). | YES/NONO | YES | ||||||||||||||||||
| icci | Interrog. Covers CountersSend the call 100 and counter values on general interrogation (only slave, balanced). | YES/NO | YES | |||||||||||||||||
| Kotva | seoi |
| If the value of the parameter is "1 - IC/CIC after EOI", then after receiving ASDU 70 (End of initialisation) the Interrogation Command will be sent again. The default value "0 - no IC/CIC after EOI" will cause ASDU 70 to be ignored. | - | 0 | seoi | Send EOISend "end of interrogation command" to all ASDU (only slave). | YES/NO | YES | ||||||||||||
| Send general interrogation command in case of slave or balanced controlled station B (only slave, balanced). | YES/NO | NO | ||||||||||||||||||
| Communication for system the Sinaut Spectrum system, which requires non-standard behavior on redundant lines (different from the Norwegian convention). | YES/NO | NO | ||||||||||||||||||
| Address of station and output I/O tag with the status of system redundancy. The format of the address is Station Address, I/O tag address, for example. "1,1003". The parameter is useful for SerialOverUDP System&Line Redundant lines, which enable communication with two independent control systems (e.g. main dispatching SED in Žilina and backup dispatching SED in Bratislava). The parameter enables one to ignore values that are received from the control system, which is inactive just now, providing that the application knows which one is active or inactive. It can know it e.g. based on the value of the input I/O tag with the defined value. This feature (information about active control system) will work | providing provided that the station with the output I/O tag of Dout type | existexists with the same addresses as is defined in this parameter and the application must write True into it if "System A" is active, or False if "System B" ( | configured on the system redundant line) is active.configured on the system redundant line) is active. | - | ||||||||||||||||
| If Ignore Unknown Addresses=TRUE, the D2000 KOM process will not show an error on its console or write it into log files in case the incoming value has the address not matching any of the addresses of I/O tags defined in the D2000 system. | - | False | -||||||||||||||||||
| A high level of communication tracking, the received values of I/O tags, and other debug information is shown. | YES/NO | NO | ||||||||||||||||||
...
I/O tag address is a numerical address of data object IOA (in the range 0 - 65535). It can be specified as a decimal number or as a hexadecimal number with a hash at the beginning (e.g. #0A).
The I/O tag with an address starting with %IGNORE will be ignored.
In the case of command direction in master or balanced mode, it is necessary to configure a proper ASDU type:
...
Note 1: Individual bits of bytes which determines a quality byte (SIQ for ASDU 1,2,30; DIQ for ASDU 3,4,31; QDS for 5-14,20,32-36) set the attributes FLA (0.bit), FLB (1.bit) ..FLH (7.bit).Kotva poz1 poz1
Example:
for ASDU 4: FLA=DPI bit 0, FLB=DPI bit 1, FLC=0, FLD=0, FLE=BL bit, FLF=SB bit, FLG=NT bit, FLH=IV bit.
for ASDU 16: FLA..FLE Sequence number bity bits 0..4, FLF=CY bit, FLG=CA bit, FLH=IV bit
And
Moreover:
- if bit IV (Invalid) is set, the status of value will be Invalid
- if one of the NT (Not topical), SB (Substituted), BL (Blocked), OV (Overflow), CA (Counter adjusted), or CY (Counter overflow) bits are set for in their respective ASDU types, the status of value will be Weak.
...
| Kotva | ||||
|---|---|---|---|---|
|
| Kotva | ||||
|---|---|---|---|---|
|
Note 2: When using the system and line redundant categories of lines, the status of line and station is formed by a logical sum of all used lines. It means, that if the redundant system consists of four lines and just one line is working, the status of the station and line is all right. The status of lines is presented with the help of special input or output I/O tag (of integer and real type, i.e. Ai/Ao/Ci/Co). The name of this I/O tag has this format: [line_name]_SystemStatus (e.g. for line L.Test it is M.Test_SystemStatus). The value of the I/O tag represents the binary format of the status of N-tuple lines. If the first three lines are okay but the last one does not work (SystemB/SecondaryLine) i.e. [FALSE, TRUE, TRUE, TRUE], I/O tag has the value 0b0111, i.e. 7.
The order of lines mapped to individual bits is [SystemB/SecondaryLine, SystemB/PrimaryLine, SystemA/SecondaryLine, SystemA/PrimaryLine].
...
Double-clicking on a particular line will cause the Address parameter to be inserted into the configuration of the I/O tag from which the IEC870-5-101 Item Browser window was opened.
...
The Value column contains the received value.
The Value column contains the received value, and the Time column contains the received timestamp. The Point column contains the name of the I/O tag that has this address (if there is one).
| Kotva | ||||
|---|---|---|---|---|
|
...
- Telecontrol equipment and systems Part 5-101: Transmission protocols – Companion standard for basic telecontrol tasks (IEC 60870-5-101:2003), http://www.iec.ch.
- Telecontrol equipment and systems Part 5-2: Link transmissions procedures (IEC 60870-5-2:1992), http://www.iec.ch.
- Norwegian IEC 870-5-101 User Conventions, Approved version Revision no. 2.0, http://www.statnett.no.
| Info | ||
|---|---|---|
| ||
You can read blogs about about the IEC 870-5-101 protocol (for now, in Slovak language only): |
...