219
edits
Changes
Template:Networking rutos manual serial utilities (view source)
Revision as of 09:24, 15 April 2024
, 15 Aprilno edit summary
{{Template: Networking_rutos_manual_fw_disclosure
{{Template: Networking_device_manual_fw_disclosure
| fw_version ={{Template: Networking_rutos_manual_latest_fw
| series = {{{series}}}
| name = {{{name}}}
| fw_version ={{Template: Networking_device_manual_latest_fw
| series = {{{series}}}
| series = {{{series}}}
| name = {{{name}}}
| name = {{{name}}}
}}
}}
}}
}}
{{#ifeq: {{{series}}} | RUT9 |<i><b>Note</b>: <b>[[{{{name}}} RS232/RS485 (legacy WebUI)#RS232|click here]]</b> for the old style WebUI (FW version {{Template: Networking_device_manual_latest_fw | series = RUT9XX}} and earlier) user manual page.</i>|}}
{{#ifeq: {{{series}}} | RUT9 |<i><b>Note</b>: <b>[[{{{name}}} RS232/RS485 (legacy WebUI)#RS232|click here]]</b> for the old style WebUI (FW version {{Template: Networking_rutos_manual_latest_fw | series = RUT9XX}} and earlier) user manual page.</i>|}}
==Summary==
==Summary==
The <b>Serial Utilities</b> page is used to make serial communication configurations of different types.
The <b>Serial Utilities</b> page is used to make serial communication configurations of different types.
This manual page provides an overview of the Serial Utilities page in {{{name}}} devices.
This manual page provides an overview of the Serial Utilities page in {{{name}}} devices.
{{#ifeq: {{#expr: {{{rs232}}} or {{{rs485}}}}}| 1 |==General information==|}}
{{#ifeq: {{#expr: {{{rs232}}} or {{{rs485}}}}}| 1 |==General information==|}}
{{#ifeq:{{{series}}}|TRB2|
{{#switch:{{{series}}}|TRB2| TRB2M =
===RS232/RS485===
===RS232/RS485===
----
----
====Connector pinout====
====Connector pinout====
----
----
For {{{name}}} pinout, please refer to <b>[[{{{name}}} Input/Output#16_pin_Connector_Pinout|Input/Output]]</b> page.|
For {{{name}}} pinout, please refer to <b>[[{{{name}}} Input/Output#16_pin_Connector_Pinout|Input/Output]]</b> page.| #default =
{{#ifeq: {{{rs232}}} | 1 |
{{#ifeq: {{{rs232}}} | 1 |
===RS232===
===RS232===
----
----
To connect another DCE device to RUT955, a Null-modem (crossed) Male/Male cable should be used:
To connect another DCE device to RUT/TRB, a Null-modem (crossed) Male/Male cable should be used:
[[File:Male male rs232 cable.jpg]]
[[File:Male male rs232 cable.jpg]]
}}
}}
==Modem Control==
{{#ifeq:{{{modem}}}|1|==Modem Control==
The <b>Modem</b> serial type is used to manage modem functionality which could be accessed using shell interface. For this purpose you may want use CR/LF (Carriage Return, Line Feed) capable applications like PuTTY on Windows and microcom, minicom, cutecom or similar applications on Linux.
The <b>Modem</b> serial type is used to manage modem functionality which could be accessed using shell interface. For this purpose you may want use CR/LF (Carriage Return, Line Feed) capable applications like PuTTY on Windows and microcom, minicom, cutecom or similar applications on Linux.
[[File:Networking_rutos_manual_serial_utilities_modem_control_default_{{{default}}}_v1.png|border|class=tlt-border]]
{{#ifeq:{{{dual_modem}}} | 1 |
[[File:Networking_rutos_manual_serial_utilities_modem_control_default_{{{default}}}_dual_modem_v1.png|border|class=tlt-border]]|
[[File:Networking_rutos_manual_serial_utilities_modem_control_default_{{{default}}}_v2.png|border|class=tlt-border]]
}}
<table class="nd-mantable">
<table class="nd-mantable">
<tr>
<tr>
<td>Enable</td>
<td>Enable</td>
<td>off | on; default: <b>off</b></td>
<td>off {{!}} on; default: <b>off</b></td>
<td>Turns the instance on or off.</td>
<td>Turns the instance on or off.</td>
</tr>
</tr>
<tr>
<tr>
<td>Data bits</td>
<td>Data bits</td>
<td>7 | 8; default: <b>8</b></td>
<td>{{#ifeq: {{{rs232}}} | 1 | 5 {{!}} 6 {{!}} 7 {{!}} 8 | 8}}; default: <b>8</b></td>
<td>Number of data bits for each character.</td>
<td>Number of data bits for each character.</td>
</tr>
</tr>
<tr>
<tr>
<td>Stop bits</td>
<td>Stop bits</td>
<td>1 | 2; default: <b>1</b></td>
<td>1 {{!}} 2; default: <b>1</b></td>
<td>Stop bits sent at the end of every character allow the receiving signal hardware to detect the end of a character and to resynchronise with the character stream. Electronic devices usually use one stop bit. Two stop bits are required if slow electromechanical devices are used.</td>
<td>Stop bits sent at the end of every character allow the receiving signal hardware to detect the end of a character and to resynchronise with the character stream. Electronic devices usually use one stop bit. Two stop bits are required if slow electromechanical devices are used.</td>
</tr>
</tr>
<tr>
<tr>
<td>Parity</td>
<td>Parity</td>
<td>None | Odd | Even | Mark | Space; default: <b>None</b></td>
<td>None {{!}} Odd {{!}} Even {{!}} Mark {{!}} Space; default: <b>None</b></td>
<td>In serial transmission, parity is a method of detecting errors. An extra data bit is sent with each data character, arranged so that the number of 1 bits in each character, including the parity bit, is always odd or always even. If a byte is received with the wrong number of 1s, then it must have been corrupted. However, an even number of errors can pass the parity check.
<td>In serial transmission, parity is a method of detecting errors. An extra data bit is sent with each data character, arranged so that the number of 1 bits in each character, including the parity bit, is always odd or always even. If a byte is received with the wrong number of 1s, then it must have been corrupted. However, an even number of errors can pass the parity check.
<ul>
<ul>
<ul>
<ul>
<li><b>RTS/CTS</b> - hardware handshaking. RTS and CTS are turned OFF and ON from alternate ends to control data flow, for instance when a buffer is almost full.</li>
<li><b>RTS/CTS</b> - hardware handshaking. RTS and CTS are turned OFF and ON from alternate ends to control data flow, for instance when a buffer is almost full.</li>
<li><b>Xon/Xoff</b> - software handshaking. The Xon and Xoff characters are sent by the receiver to the sender to control when the sender will send data, i.e., these characters go in the opposite direction to the data being sent. The circuit starts in the "sending allowed" state. When the receiver's buffers approach capacity, the receiver sends the Xoff character to tell the sender to stop sending data. Later, after the receiver has emptied its buffers, it sends an Xon character to tell the sender to resume transmission.
<li><b>Xon/Xoff</b> - software handshaking. The Xon and Xoff characters are sent by the receiver to the sender to control when the sender will send data, i.e., these characters go in the opposite direction to the data being sent. The circuit starts in the "sending allowed" state. When the receiver's buffers approach capacity, the receiver sends the Xoff character to tell the sender to stop sending data. Later, after the receiver has emptied its buffers, it sends an Xon character to tell the sender to resume transmission.</li>
</ul>|}}
</ul>|}}
</td>
</td>
</tr>
</tr>
{{#ifeq: {{{dual_modem}}} | 1 |
<tr>
<td>Modem</td>
<td>Primary modem{{!}} Secondary modem; default: <b>Primary modem</b></td>
<td>Specifies modem, which will be used for modem control.
<ul>
<li><b>Primary modem</b>- enables modem control for Primary modem.</li>
<li><b>Secondary modem</b>- enables modem control for Secondary modem.</li>
</ul>
</td>
</tr> |}}
<tr>
<tr>
<td>Mode</td>
<td>Mode</td>
<td>Specifies modem control mode.
<td>Specifies modem control mode.
<ul>
<ul>
<li><b>Partial control</b>- enables modem control with AT commands, mobile connection will be controlled by RUTOS.
<li><b>Partial control</b>- enables modem control with AT commands, mobile connection will be controlled by RUTOS.</li>
<li><b>Full control</b>- enables modem control with AT commands, mobile connection will be controlled by user.
<li><b>Full control</b>- enables modem control with AT commands, mobile connection will be controlled by user. </li>
</ul>
</ul>
</td>
</td>
<td>Turns Full Duplex mode on or off. This option is available only on the RS485 device.</td>
<td>Turns Full Duplex mode on or off. This option is available only on the RS485 device.</td>
</tr>|}}
</tr>|}}
</table>
<tr>
<td>Start up message</td>
<td>string; default: <b>none</b></td>
<td>Message to print to serial device when modem control is ready.</td>
</tr>
</table>|}}
==Console==
==Console==
<tr>
<tr>
<td>Enable</td>
<td>Enable</td>
<td>off | on; default: <b>off</b></td>
<td>off {{!}} on; default: <b>off</b></td>
<td>Turns the instance on or off.</td>
<td>Turns the instance on or off.</td>
</tr>
</tr>
<tr>
<tr>
<td>Data bits</td>
<td>Data bits</td>
<td>7 | 8; default: <b>8</b></td>
<td>{{#ifeq: {{{rs232}}} | 1 | 5 {{!}} 6 {{!}} 7 {{!}} 8 | 8}}; default: <b>8</b></td>
<td>Number of data bits for each character.</td>
<td>Number of data bits for each character.</td>
</tr>
</tr>
<tr>
<tr>
<td>Stop bits</td>
<td>Stop bits</td>
<td>1 | 2; default: <b>1</b></td>
<td>1 {{!}} 2; default: <b>1</b></td>
<td>Stop bits sent at the end of every character allow the receiving signal hardware to detect the end of a character and to resynchronize with the character stream. Electronic devices usually use one stop bit. Two stop bits are required if slow electromechanical devices are used.</td>
<td>Stop bits sent at the end of every character allow the receiving signal hardware to detect the end of a character and to resynchronize with the character stream. Electronic devices usually use one stop bit. Two stop bits are required if slow electromechanical devices are used.</td>
</tr>
</tr>
<tr>
<tr>
<td>Parity</td>
<td>Parity</td>
<td>None | Odd | Even | Mark | Space; default: <b>None</b></td>
<td>None {{!}} Odd {{!}} Even {{!}} Mark {{!}} Space; default: <b>None</b></td>
<td>In serial transmission, parity is a method of detecting errors. An extra data bit is sent with each data character, arranged so that the number of 1 bits in each character, including the parity bit, is always odd or always even. If a byte is received with the wrong number of 1s, then it must have been corrupted. However, an even number of errors can pass the parity check.
<td>In serial transmission, parity is a method of detecting errors. An extra data bit is sent with each data character, arranged so that the number of 1 bits in each character, including the parity bit, is always odd or always even. If a byte is received with the wrong number of 1s, then it must have been corrupted. However, an even number of errors can pass the parity check.
<ul>
<ul>
<ul>
<ul>
<li><b>RTS/CTS</b> - hardware handshaking. RTS and CTS are turned OFF and ON from alternate ends to control data flow, for instance when a buffer is almost full.</li>
<li><b>RTS/CTS</b> - hardware handshaking. RTS and CTS are turned OFF and ON from alternate ends to control data flow, for instance when a buffer is almost full.</li>
<li><b>Xon/Xoff</b> - software handshaking. The Xon and Xoff characters are sent by the receiver to the sender to control when the sender will send data, i.e., these characters go in the opposite direction to the data being sent. The circuit starts in the "sending allowed" state. When the receiver's buffers approach capacity, the receiver sends the Xoff character to tell the sender to stop sending data. Later, after the receiver has emptied its buffers, it sends an Xon character to tell the sender to resume transmission.
<li><b>Xon/Xoff</b> - software handshaking. The Xon and Xoff characters are sent by the receiver to the sender to control when the sender will send data, i.e., these characters go in the opposite direction to the data being sent. The circuit starts in the "sending allowed" state. When the receiver's buffers approach capacity, the receiver sends the Xoff character to tell the sender to stop sending data. Later, after the receiver has emptied its buffers, it sends an Xon character to tell the sender to resume transmission.</li>
</ul>|}}
</ul>|}}
</td>
</td>
Configure serial port communication parameters in the <b>Serial Device Configuration</b> section.
Configure serial port communication parameters in the <b>Serial Device Configuration</b> section.
[[File:Networking_rutos_manual_serial_utilities_over_ip_serial_default_{{{default}}}_v1.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_serial_utilities_over_ip_serial_default_{{{default}}}_v2.png|border|class=tlt-border]]
<table class="nd-mantable">
<table class="nd-mantable">
<tr>
<tr>
<td>Enable</td>
<td>Enable</td>
<td>off | on; default: <b>off</b></td>
<td>off {{!}} on; default: <b>off</b></td>
<td>Turns the instance on or off.</td>
<td>Turns the instance on or off.</td>
</tr>
</tr>
<tr>
<tr>
<td>Data bits</td>
<td>Data bits</td>
<td>7 | 8; default: <b>8</b></td>
<td>{{#ifeq: {{{rs232}}} | 1 | 5 {{!}} 6 {{!}} 7 {{!}} 8 | 8}}; default: <b>8</b></td>
<td>Number of data bits for each character.</td>
<td>Number of data bits for each character.</td>
</tr>
</tr>
<tr>
<tr>
<td>Stop bits</td>
<td>Stop bits</td>
<td>1 | 2; default: <b>1</b></td>
<td>1 {{!}} 2; default: <b>1</b></td>
<td>Stop bits sent at the end of every character allow the receiving signal hardware to detect the end of a character and to resynchronise with the character stream. Electronic devices usually use one stop bit. Two stop bits are required if slow electromechanical devices are used.</td>
<td>Stop bits sent at the end of every character allow the receiving signal hardware to detect the end of a character and to resynchronise with the character stream. Electronic devices usually use one stop bit. Two stop bits are required if slow electromechanical devices are used.</td>
</tr>
</tr>
<tr>
<tr>
<td>Parity</td>
<td>Parity</td>
<td>None | Odd | Even | Mark | Space; default: <b>None</b></td>
<td>None {{!}} Odd {{!}} Even {{!}} Mark {{!}} Space; default: <b>None</b></td>
<td>In serial transmission, parity is a method of detecting errors. An extra data bit is sent with each data character, arranged so that the number of 1 bits in each character, including the parity bit, is always odd or always even. If a byte is received with the wrong number of 1s, then it must have been corrupted. However, an even number of errors can pass the parity check.
<td>In serial transmission, parity is a method of detecting errors. An extra data bit is sent with each data character, arranged so that the number of 1 bits in each character, including the parity bit, is always odd or always even. If a byte is received with the wrong number of 1s, then it must have been corrupted. However, an even number of errors can pass the parity check.
<ul>
<ul>
<ul>
<ul>
<li><b>RTS/CTS</b> - hardware handshaking. RTS and CTS are turned OFF and ON from alternate ends to control data flow, for instance when a buffer is almost full.</li>
<li><b>RTS/CTS</b> - hardware handshaking. RTS and CTS are turned OFF and ON from alternate ends to control data flow, for instance when a buffer is almost full.</li>
<li><b>Xon/Xoff</b> - software handshaking. The Xon and Xoff characters are sent by the receiver to the sender to control when the sender will send data, i.e., these characters go in the opposite direction to the data being sent. The circuit starts in the "sending allowed" state. When the receiver's buffers approach capacity, the receiver sends the Xoff character to tell the sender to stop sending data. Later, after the receiver has emptied its buffers, it sends an Xon character to tell the sender to resume transmission.
<li><b>Xon/Xoff</b> - software handshaking. The Xon and Xoff characters are sent by the receiver to the sender to control when the sender will send data, i.e., these characters go in the opposite direction to the data being sent. The circuit starts in the "sending allowed" state. When the receiver's buffers approach capacity, the receiver sends the Xoff character to tell the sender to stop sending data. Later, after the receiver has emptied its buffers, it sends an Xon character to tell the sender to resume transmission.</li>
</ul>|}}
</ul>|}}
</td>
</td>
<td>off {{!}} on; default: <b>off</b></td>
<td>off {{!}} on; default: <b>off</b></td>
<td>Turns Full Duplex mode on or off. This option is available only on the RS485 device.</td>
<td>Turns Full Duplex mode on or off. This option is available only on the RS485 device.</td>
</tr>|}}{{#ifeq: {{{rs232}}} | 1 |
<tr>
<td><span style="color: green;">RS232:</span> Echo</td>
<td>off {{!}} on; default: <b>off</b></td>
<td> Enable serial device echo. This option is available only on the RS232 device.</td>
</tr>|}}
</tr>|}}
</table>
</table>
You can configure network related parameters of the serial connection in the <b>Over IP Configuration</b> secion.
You can configure network related parameters of the serial connection in the <b>Over IP Configuration</b> secion.
[[File:Networking_rutos_manual_serial_utilities_over_ip_configuration_v1.png|border|class=tlt-border]]
[[File:Networking rutos manual serial utilities over ip mbus configuration general_v1.png|border|class=tlt-border]]
<table class="nd-mantable">
<table class="nd-mantable">
<tr>
<tr>
<td>Mode</td>
<td>Mode</td>
<td><span style="color: red;">Server</span> | <span style="color: purple;">Client</span> | <span style="color: orange;">Bidirect</span>; default: <b>Server</b></td>
<td><span style="color: red;">Server</span> {{!}} <span style="color: purple;">Client</span> {{!}} <span style="color: green;">Client + server</span> {{!}} <span style="color: orange;">Bidirect</span>; default: <b>Server</b></td>
<td>This device's role in the connection:
<td>This device's role in the connection:
<ul>
<ul>
<li><b>Server</b> - the device waits for incoming connections.</li>
<li><b>Server</b> - the device waits for incoming connections.</li>
<li><b>Client</b> - the device initiates the connection.</li>
<li><b>Client</b> - the device initiates the connection.</li>
<li><b>Client + server</b> - launches service in server and client(s) mode simultaneously.</li>
<li><b>Bidirect</b> - acts as client by default but waits for incoming connections at the same time.</li>
<li><b>Bidirect</b> - acts as client by default but waits for incoming connections at the same time.</li>
</ul>
</ul>
<tr>
<tr>
<td>Protocol</td>
<td>Protocol</td>
<td><span style="color: blue;">TCP</span> | <span style="color: green;">UDP</span>; default: <b>TCP</b></td>
<td><span style="color: blue;">TCP</span> {{!}} <span style="color: brown;">UDP</span>; default: <b>TCP</b></td>
<td>Protocol used in the communication process.</td>
<td>Protocol used in the communication process.</td>
</tr>
</tr>
<tr>
<tr>
<td>Raw mode</td>
<td><span style="color: purple;">Client: </span>Destination address</td>
<td>off {{!}} on; default; default: <b>off</b></td>
<td>IP {{!}} Port; default: <b>empty</b></td>
<td>Specify server address and port for client to connect to. E.g first field for address second for port. 16 destination addresses are allowed. </td>
</tr>
<tr>
<td><span style="color: red;">Server: </span><span style="color: brown;">UDP: </span> Predefined addresses</td>
<td>IP {{!}} Port; default: <b>empty</b></td>
<td>Set predefined IP and port for UDP connection. E.g first field for address second for port.</td>
</tr>
<tr>
<td>Listening port</td>
<td>[1..65535]; default: <b>empty</b></td>
<td>When enabled, all data will be transmitted transparently.</td>
<td>When enabled, all data will be transmitted transparently.</td>
</tr>
</tr>
</table>
[[File:Networking rutos manual serial utilities over ip mbus configuration security_v1.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<tr>
<th style="width: 360px>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
</tr>
<tr>
<tr>
<td>Use TLS/SSL</td>
<td>off {{!}} on; default: <b>off</b></td>
<td>Mark to use TLS/SSL for connection.</td>
</tr>
</tr>
<tr>
<tr>
<td>TLS version</td>
<td>Support all {{!}} tlsv1.0 {{!}} tlsv1.1 {{!}} tlsv1.2 {{!}} tlsv1.3; default: <b>Support all</b></td>
<td>Minimum TLS version allowed to be used.</td>
</tr>
</tr>
<tr>
<tr>
<td>TLS type</td>
<td>Certificate based {{!}} <span style="color: blue;">Pre-Shared-Key based</span>; default: <b>Certificate based</b></td>
<td>Select the type of TLS encryption.</td>
</tr>
</tr>
<tr>
<tr>
<td>Require certificate</td>
<td>off {{!}} on; default: <b>on</b></td>
<td>Demand certificate and key from peer and verify them against certificate authority.</td>
</tr>
</tr>
<tr>
<tr>
<td>Verify host</td>
<td>off {{!}} on; default: <b>off</b></td>
<td>Check if the server certificates Common Name (CN) matches hostname to which client is connecting.</td>
</tr>
</tr>
<tr>
<tr>
<td>Certificate files from device</td>
<td>off {{!}} on; default: <b>off</b></td>
<td>Choose this option if you want to select certificate files from device.<br> Certificate files can be generated <a class=link href="/system/admin/certificates/generation">here</a>.</td>
</tr>
<tr>
<td>Certificate file</td>
<td>.crt file; default: <b>none</b></td>
<td>Upload certificate file.</td>
</tr>
<tr>
<td>Key file</td>
<td>.key file; default: <b>none</b></td>
<td>Upload key file.</td>
</tr>
<tr>
<td>CA file</td>
<td>.ca file; default: <b>none</b></td>
<td>Upload CA file.</td>
</tr>
<tr>
<td><span style="color: blue;">Pre-Shared-Key</span></td>
<td>string; default: <b>none</b></td>
<td>The pre-shared-key in hex format with no leading “0x”.</td>
</tr>
<tr>
<td><span style="color: blue;">Identify</span></td>
<td>string; default: <b>none</b></td>
<td>Specify the identity.</td>
</tr>
</table>
[[File:Networking rutos manual serial utilities over ip mbus configuration advanced_v3.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th style="width: 360px>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
</tr>
<tr>
<tr>
<td><span style="color: purple;">Client settings</span>: Server Address</td>
<td>Raw mode</td>
<td>ip | host; default: <b>none</b></td>
<td>off {{!}} on; default: <b>on</b></td>
<td>IP address or hostname of the server that this client will connect to.</td>
<td>When enabled, all data will be transmitted transparently.</td>
</tr>
</tr>
<tr>
<tr>
<td>Remove all zeros</td>
<td>off {{!}} on; default: <b>off</b></td>
<td>When checked, indicates that the first hex zeros should be skipped.</td>
</tr>
</tr>
<tr>
<tr>
<td><span style="color: purple;">Client settings</span>: Reconnect interval (s)</td>
<td>Inactivity timeout</td>
<td>integer; default: <b>none</b></td>
<td>integer [0..36000]; default: <b>300</b></td>
<td>Time period (in seconds) between reconnection attempts in case a connection fails.</td>
<td>Specifies period of time in seconds, where server connection must be inactive, to disconnect client. To disable timeout input 0.</td>
</tr>
</tr>
<tr>
<tr>
<td>Serial device read time</td>
<td>Serial timeout</td>
<td>integer [0..1000]; default: <b>none</b></td>
<td>integer [0..1000]; default: <b>none</b></td>
<td>Specifies custom read time for the serial device.</td>
<td>Specifies the maximum milliseconds to wait for serial data.</td>
</tr>{{#ifeq: {{{rs485}}} | 1 |
</tr>
<tr>
<td>Max clients</td>
<td>integer [1..32]; default: <b>4</b></td>
<td>Specify how many clients are allowed to connect simultaneously.</td>
</tr>
<tr>
<td>TCP echo</td>
<td>on {{!}} off; default: <b>off</b></td>
<td>Enable software TCP echo.</td>
</tr>
<tr>
<tr>
<td><span style="color: purple;">RS485:</span> Full Duplex</td>
<td>Close connections</td>
<td>off {{!}} on; default: <b>off</b></td>
<td>on {{!}} off; default: <b>off</b></td>
<td>Close TCP connections everytime data is sent or received (might result in serial data loss).</td>
</tr>|}}
</tr>
<tr>
<td>Keep alive</td>
<td><span style="color: blue;">on</span> {{!}} off; default: <b>off</b></td>
<td>Enable keep alive.</td>
</tr>
<tr>
<tr>
<td><span style="color: red;">Server settings</span> | <span style="color: blue;">TCP</span>: Max clients</td>
<td><span style="color: blue;">Keep alive time</span></td>
<td>integer [1..32]; default: <b>32</b></td>
<td>integer [0..32000]; default: <b>0</b></td>
<td>Specifies how many clients are allowed to connect simultaneously.</td>
<td>Close TCP connections everytime data is sent or received (might result in serial data loss).</td>
</tr>
</tr>
<tr>
<tr>
<td><span style="color: blue;">TCP</span>: TCP echo</td>
<td><span style="color: blue;">Keep alive interval</span></td>
<td>off | on; default: <b>off</b></td>
<td>integer [0..32000]; default: <b>0</b></td>
<td>Enables software TCP echo.</td>
<td>The interval between subsequential keepalive probes.</td>
</tr>
</tr>
<tr>
<tr>
<td><span style="color: blue;">TCP</span>: Always reconnect</td>
<td><span style="color: blue;">Keep alive probes</span></td>
<td>off | on; default: <b>off</b></td>
<td>integer [0..32000]; default: <b>0</b></td>
<td>When enabled, a new TCP connection will be made after sending every data package.</td>
<td>The number of unacknowledged probes.</td>
</tr>
</tr>
</table>
</table>
