Porovnávané verzie

Kľúč

  • Tento riadok sa pridal
  • Riadok je odstránený.
  • Formátovanie sa zmenilo.

...

Implementation is, according to the IEC870-5-101 standard, as follows:

  • Originator 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.
  • Cause The cause of transmission is 1 byte (does not contain Originator ASDU address).
  • Information 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)".
  • Station The station address is a decimal number in range 0 - 255 and is used in the protocol as the ASDU address.
  • 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 D2000 System.

...

Configuration dialog box - tab Protocol parameters.
They influence some optional parameters of the protocol. Following The following station protocol parameters can be set:

...

Parameter


Meaning


Unit


Default value


Kotva
la
la
Link Address
Common link address.-1
Kotva
lasdu
lasdu
Length of ASDU Address
Length of ASDU address.1/2 byte(s)1
Kotva
lla
lla
Length of Link Address
Length of common link address.1/2 byte(s)1
Kotva
lioa
lioa
Length of Info Object Address
Length of info object address.1/2/3 byte(s)2
Kotva
lcot
lcot
Length of Cause Of Transmission
Length of "Cause Of Transmission".1/2 byte(s)1
Kotva
rc
rc
Retry Count
Delay The delay between request retry in case of a communication failure.-2
Kotva
rt
rt
Retry Timeout
Delay The delay between retry of call in case of a communication error.ms100 millisecond
Kotva
wft
wft
Wait First Timeout
Delay after sending the request before reading the response.ms100 millisecond
Kotva
wt
wt
Wait Timeout
Delay between response readings till its completing.ms500 millisecond
Kotva
mwr
mwr
Max. Wait Retry
Retry count of response reading till its completing.-6
Kotva
ndt
ndt
No Data Timeout
Delay of next call "Request user data class 1/2" if no data have been received (only master).ms300 millisecond
Kotva
it
it
Inactivity Timeout
Interval of connection monitoring. If no valid data have not been received, station status will pass go to a communication error. Switching of redundant devices in case of SerialOverUDP Device Redundant line (only slave).ms5 sec.
Kotva
mt
mt
Moxa Timeout
Interval of The switching interval of the redundant devices MOXA NPort in case of communication error (only master, balanced).sec.10
Kotva
sf
sf
Source Flags
Set flags FI..FL according to the source of line. If SerialOverUDP System+Line Redundant is used, the values will have these flags:
  • System A, primary line: FI
  • System A, secondary line: FJ
  • System B, primary line: FK
  • System B, secondary line: FL

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
Kotva
nf
nf
No Output Flags
Activation of parameter results in ignoring of flags FA..FH for output I/O tags. If this parameter is turned off, flags FA..FH are mapped to individual bits of quality byte.-NO
Kotva
ltt
ltt
Link Test Timeout
Interval of request sending "Test function for link" if timeout elapsed and no data telegrams was were transferred (only balancedbalanced only).sec.10

Kotva
sv
sv
Single Value In Spontaneous Answer

When sending spontaneous changes, these will be sent one-per-ASDU and they will not be cumulated into longer packets. Parameter The parameter was implemented to handle a bug in a particular TM1703mic.-NO

Kotva
dc
dc
Data Class

The class used for sending data (slave only slave). 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 response  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:

  • Class1&2 - IEC 101 Slave responds to Class1 and Class2 requests with data. The ACD flag sets if it has additional data.
  • Class1 - IEC 101 Slave sends all data as Class1 and responds to the Class2 requests that it has no data. The ACD flag sets if it has additional data.
  • Class2 - IEC 101 Slave sends all data as Class2 and responds to the Class1 requests that it has no data. The ACD flag sets to 0 (it does not have Class1 data).
  • Prio reply - IEC 101 Slave sends responses to command ASDUs as Class1 data and other ASDUs (value changes, responses to Interrogation) as Class2ASDUs as Class1 data and other ASDUs (value changes, responses to Interrogation) as Class2.
    Note: The responses to Interrogation (ASDU 100) and Counter Interrogation (ASDU 101) commands and all the values sent as a part of the response are also sent as Class1 data.

The default value of the parameter is Class1.

-Class1&2
Class1
Class2
Prio reply

Kotva
sr
sr
Single Request

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 partners partner errors (e.g. OSI Monarch with RtuPing running during switching of active communication line).-NO
Kotva
cmdc
cmdc
Send Confirmation Command
Type of sent confirmation to write value (only slave, balanced).-
7(CONF)
10(TERM)
7(CONF) and 10(TERM)
7(CONF)
Kotva
acc
acc
Accept Confirmation Command
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)
Kotva
mtu
mtu
Max. MTU
Limitation of data packet size (only slave, balanced).bytes220
Kotva
dirab
dirab
Phys. Trans. Direction
Setting a bit DIR in balance mode (only balanced).Station A(Controlling)
Station B(Controlled)
Station A(Controlling)
Kotva
sback
sback
Single Byte Ack
Send single-byte ACK preferentially (0xE5).YES/NONO
Kotva
icci
icci
Interrog. Covers Counters
Send the call 100 and counter values on general interrogation (only slave, balanced).YES/NOYES
Kotva
seoi
seoi
Send EOI
Send "end of interrogation command" to all ASDU (only slave).YES/NOYES
Kotva
sisd
sisd
Send Interrog. in Sec. Direct.
Send general interrogation command in case of slave or balanced controlled station B (only slave, balanced).YES/NONO

Kotva
sm
sm
Sinaut Mode

Communication for system Sinaut Spectrum, which requires non-standard behavior on redundant lines (different from the Norwegian convention).YES/NONO

Kotva
srmast
srmast
System Redundancy: Manages A Status Address

-
Kotva
fd
fd
Full Debug
High level of communication tracking, the loaded received values of I/O tags and other debug information are is shown.YES/NONO

Kotva
merany_bod
merany_bod
I/O tag configuration

...

Kotva
pozn3
pozn3
*** - ASDU 18, 39 and 40: value of byte SPE(ASDU 18,39) or OCI (ASDU 40) sets the attributes FLI (0.bit), FLJ (1.bit) up-to FLP (7.bit).  Value The value of byte QDP sets the attributes FLA (0.bit), FLB (1.bit) up-to FLH (7.bit), following 2 bytes (CP16Time2a) are interpreted as a positive number (0-60 000) into the value of I/O tag with value type Ci/Ai or as a relative time (0-60 seconds) into the value of I/O tag with value type TiR.

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 elementslines. It means, that if the redundant system consists of four lines and just one line is working, the status of 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). Name The name of this I/O tag has this format: [line_name of line]_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 bites bits is [SystemB/SecondaryLine,  SystemB/PrimaryLine, SystemA/SecondaryLine, SystemA/PrimaryLine].

...