Supported device types and versions
Communication line configuration
Communication station configuration
Station protocol parameters
I/O tag configuration
Changes and modifications
Document revisions
The ASCII Client/Server protocol is intended for parsing serial communication containing simple text-oriented data (data sentences) that conform to a template
StartMark Data1 Separator Data2 Separator .... DataN EndMark
Parameters StartMark, Separator and EndMark can be configured within the station address.
It is also possible to periodically send text-oriented data with an identical template. The StartMark, Separator and EndMark parameters for transmitting can be different from those for receiving.
Example of received data:
Sending<CR><LF>11.8<CR><LF>-17.519723239035<CR><LF>12.2<CR><LF>0.3312<CR><LF>1.465<CR><LF>0.01<CR><LF> 11.384611976362<CR><LF>
Setting individual parameters:
StartMark = ding<CR><LF>
Separator = <CR><LF>
EndMark = Sen
Note: this communication protocol is simpler than the Generic User Protocol and only offers simple value parsing. On the other hand, parsing does not need to be implemented in the ESL script, but is performed directly by the KOM process.
Category of communication line:
Communication protocol ASCII Client/Server.
Data Input section
Receiving enabled - the protocol processes input data.
Startup - text sequence indicating the start of data (StartMark). The end of the sequence must be followed by data.
Value delimiter - text sequence separating individual values (Separator).
End mark - text sequence indicating the end of data (EndMark).
Data output section
Transmitting enabled - the protocol writes data with the period Data output period.
Startup - text sequence written at the beginning of the data (StartMark).
Value delimiter - text sequence separating individual recorded values (Separator).
End mark - text sequence written at the end of the data (EndMark).
Note: StartMark, Separator and EndMark parameters can also contain special (control) characters in symbolic form, e.g. <CR> or <LF>. The following table lists the supported characters:
Table 1
| Symbolic form | Character | ASCII value |
|---|---|---|
<NUL> | NUL | 0 |
<SOH> | SOH | 1 |
<STX> | STX | 2 |
<ETX> | ETX | 3 |
<EOT> | EOT | 4 |
<ENQ> | ENQ | 5 |
<ACK> | ACK | 6 |
<BEL> | BEL | 7 |
<BS> | BS | 8 |
<HT> | HT | 9 |
<LF> | LF | 10 |
<VT> | VT | 11 |
<FF> | FF | 12 |
<CR> | CR | 13 |
<SO> | SO | 14 |
<SI> | SI | 15 |
<DLE> | DLE | 16 |
<DC1> | DC1 | 17 |
<DC2> | DC2 | 18 |
<DC3> | DC3 | 19 |
<DC4> | DC4 | 20 |
<NAK> | NAK | 21 |
<SYN> | SYN | 22 |
<ETB> | ETB | 23 |
<CAN> | CAN | 24 |
<EM> | EM | 25 |
<SUB> | SUB | 26 |
<ESC> | ESC | 27 |
<FS> | FS | 28 |
<GS> | GS | 29 |
<RS> | RS | 30 |
<US> | US | 31 |
<SPACE> | SPACE | 32 |
The following station parameters can be set:
Table 2
| Full name | Description | Unit | Default value |
|---|---|---|---|
| Waiting after writing data. If writes and reads are related to each other (it is a request and a response), it is possible to set this parameter to send a request, wait, and then process the response. | sec | 00:00.000 |
| Waiting between data readings. | sec | 00:00.200 |
| Maximum reading time of one data sentence (if data input is enabled in the station configuration). | sec | 00:05.000 |
| Data transmission period (if transmitting is enabled in the station configuration). | sec | 01:00.000 |
| 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 |
The attached ZIP contains the configuration of the line (Serial over UDP - communication took place via the Moxa NPort serial server), station, and I/O tags with ASCII Client/Server protocol. |
Possible value types of I/O tag: Ai, Ci, Ao, Co, Di, Dout.
Input I/O tags:
Output I/O tags:
-