Supported device types and versions
Communication line configuration
Communication station configuration
Station protocol parameters
I/O tag configuration
Changes and modifications
Document revisions
...
It is also possible to periodically transmit textsend text-oriented data with an identical template. The StartMark, Separator and EndMark parameters for transmission transmitting can be different from those for receptionreceiving.
Example of received data:
...
| Full name | Description | Unit | Default value | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Waiting between data readings. | sec | 0.2 | ||||||
| Maximum reading time of one data sentence (if data input is enabled in the station configuration). | sec | 5 | ||||||
| Data transmission period (if transmission transmitting is enabled in the station configuration). | sec | 60 | ||||||
| If the SerialOverUDP Device Redundant communication line is used, on which two serial servers are configured (e.g. Moxa NPort), the parameter specifies a timeout after which the redundant serial servers will be switched in the event of a communication error (if no data is received within this time limit). | sec | 120 |
...
Possible value types of I/O tag: Ai, Ci, Ao, Co, Di, Dout.
| Kotva | ||||
|---|---|---|---|---|
|
...
- The output I/O tag has a numerical address (1 ... 999) indicating the position of the value (Data1, Data2 ... Data N) in the sent data sentence.
An I/O tag of type Dout is written as 0/1, an I/O tag of type Ao as a floating point with 2 digits after the decimal point (e.g. -123.45).
Note: if there are no I/O tags for some addresses, then these values will not be sent (nor the separators between them).
Example: Output I/O tags with addresses 1 and 5 are configured, the following data sentence will be sent:
StartMark Data1 Separator Data5 EndMark
...