...
Configuration line dialog box - tab Protocol parameters.
They influence some of the optional protocol parameters. The following line parameters can be set:
Table 1
| Keyword | Full name | Description | Unit | Default value | ||||||
|---|---|---|---|---|---|---|---|---|---|---|
| TCP Server | Activates server mode on the TCP/IP-TCP line. In this mode, the D2000 KOM process listens to the client connection. After the client is connected, the D2000 KOM process communicates with it (i.e., it is a single-server implementation handling a single client). After the client is disconnected, the D2000 KOM process listens again. | - | False | ||||||
| Read Wait Timeout | Waiting between individual data readouts from the communication. If no data was received during this period and previously some data was read, it will be published as a value of input I/O tag IN. If some data was received during this period, it will be appended to a buffer, until a timeout occurs or the buffer becomes full (see a parameter Read Size). If a parameter Log Each Read is set to True, data will be published immediately regardless of the value of parameter Read Wait Timeout. | sec.mss | 1.000 | ||||||
| Character encoding | The method for text encoding/decoding for writing/reading. Implemented are:
Note: ISO_8859_1 mode is suitable for transmission of 8-bit ASCII characters and implementation of binary protocols. | - | ISO_8859_1 | ||||||
| Read Size | Maximum size (in bytes) of input data. Longer data will be published in several chunks. | - | 1024 | ||||||
| Log Each Read | If this parameter is set to True, data will be published immediately regardless of the value of the parameter Read Wait Timeout. | - | False | ||||||
| Log Format | Format of data traces in log files: "0 - Hexa log" or "1 - Text log". Setting the correct format helps to make a communication log file more readable depending on whether the specific protocol is text-oriented or binary by dumping the data in text or hexadecimal format. | - | 0 - Hexa log | ||||||
| Single Log | Setting this parameter to True will make all logs to go be written to a single file on redundant lines. Setting this parameter to False means that two log files will be created for the primary/secondary line (Serial Line Redundant, SerialOverUDP Line Redundant, TCP/IP-TCP Redundant), or four log files will be created for the primary/secondary line of the A/B system (Serial System&Line Redundant, SerialOverUDP System&Line Redundant). | - | False |
...
| Kotva | ||||
|---|---|---|---|---|
|
- The output I/O tag has an address OUT.
Note: on redundant lines values written to an I/O tag with address OUT are written to both lines (primary/secondary), eventually to both systems (A/B). - on line-redundant lines (Serial Line Redundant, SerialOverUDP Line Redundant, TCP/IP-TCP Redundant) it is possible to configure I/O tags with addresses OUT_A and OUT_B to write data to primary/secondary line only
- on system-redundant lines (Serial System&Line Redundant, SerialOverUDP System&Line Redundant) it is possible to configure I/O tags with addresses OUT_A, OUT_B, OUT_C, OUT_D to write data to primary/secondary line of system A/B only
...