Difference between revisions of "Template:Networking rutos manual serial utilities"
(20 intermediate revisions by 4 users not shown) | |||
Line 7: | Line 7: | ||
}} | }} | ||
}} | }} | ||
− | + | <br><i><b>Note</b>: {{#ifeq:{{{rs232}}}|1| | |
− | {{#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>|}} | + | <b>[[{{{name}}} RS232|RS232]]</b>|}}{{#ifeq:{{{rs232}}}|1|{{#ifeq:{{{rs485}}}|1| and |}}|}}{{#ifeq:{{{rs485}}}|1|<b>[[{{{name}}} RS485|RS485]]</b>|}} services were merged and moved to <b>Serial Utilities</b> page from FW version {{{series}}}_R_00.07.03</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_device_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. | ||
+ | |||
+ | To make a <b>new serial configuration</b> instance select a serial type from the left-hand navigation menu. In the next page enter a custom name for the new config, select a serial device and click the Add button. | ||
+ | |||
+ | Example from the Modem Configuration page: | ||
+ | |||
+ | [[File:Networking_rutos_manual_serial_utilities_add_new_instance_default_{{{default}}}_v1.png|border|class=tlt-border]] | ||
+ | |||
+ | Then, click the Edit button next to the instance: | ||
+ | |||
+ | [[File:Networking_rutos_manual_serial_utilities_edit_config_default_{{{default}}}_v1.png|border|class=tlt-border]] | ||
+ | |||
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| |
===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.| |
{{#ifeq: {{{rs232}}} | 1 | | {{#ifeq: {{{rs232}}} | 1 | | ||
===RS232=== | ===RS232=== | ||
Line 227: | Line 240: | ||
}} | }} | ||
− | + | ==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. | ||
Line 257: | Line 270: | ||
<td>{{Template: Networking_rutos_manual_serial_ports | rs232={{{rs232}}} | rs485={{{rs485}}} | usb={{{usb}}} }}; default: <b>{{Template: Networking_rutos_manual_default_serial_port | rs232={{{rs232}}} | rs485={{{rs485}}} | usb={{{usb}}} }}</b></td> | <td>{{Template: Networking_rutos_manual_serial_ports | rs232={{{rs232}}} | rs485={{{rs485}}} | usb={{{usb}}} }}; default: <b>{{Template: Networking_rutos_manual_default_serial_port | rs232={{{rs232}}} | rs485={{{rs485}}} | usb={{{usb}}} }}</b></td> | ||
<td>Specifies which serial port will be used for serial communication.</td> | <td>Specifies which serial port will be used for serial communication.</td> | ||
− | </tr> | + | </tr> |
<tr> | <tr> | ||
− | <td>Baud rate | + | <td>Baud rate</td> |
− | <td>integer [300.. | + | <td>integer [300..3000000]; default: <b>9600</b></td> |
<td>Data rate for serial data transmission (in bits per second (bps)).</td> | <td>Data rate for serial data transmission (in bits per second (bps)).</td> | ||
− | </tr> | + | </tr> |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
<tr> | <tr> | ||
<td>Data bits</td> | <td>Data bits</td> | ||
− | <td> | + | <td>7 {{!}} 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> | ||
Line 335: | Line 338: | ||
<td>Message to print to serial device when modem control is ready.</td> | <td>Message to print to serial device when modem control is ready.</td> | ||
</tr> | </tr> | ||
− | </table> | + | </table> |
− | + | ==Console== | |
<b>Console</b> mode requires no further configuration than the settings above and is used as a direct-access method to the device's shell interface. For this purpose you may want use such applications as PuTTY on Windows and microcom, minicom, picocom or similar applications on Linux. | <b>Console</b> mode requires no further configuration than the settings above and is used as a direct-access method to the device's shell interface. For this purpose you may want use such applications as PuTTY on Windows and microcom, minicom, picocom or similar applications on Linux. | ||
Line 363: | Line 366: | ||
<td>{{Template: Networking_rutos_manual_serial_ports | rs232={{{rs232}}} | rs485={{{rs485}}} | usb={{{usb}}} }}; default: <b>{{Template: Networking_rutos_manual_default_serial_port | rs232={{{rs232}}} | rs485={{{rs485}}} | usb={{{usb}}} }}</b></td> | <td>{{Template: Networking_rutos_manual_serial_ports | rs232={{{rs232}}} | rs485={{{rs485}}} | usb={{{usb}}} }}; default: <b>{{Template: Networking_rutos_manual_default_serial_port | rs232={{{rs232}}} | rs485={{{rs485}}} | usb={{{usb}}} }}</b></td> | ||
<td>Specifies which serial port will be used for serial communication.</td> | <td>Specifies which serial port will be used for serial communication.</td> | ||
− | </tr> | + | </tr> |
<tr> | <tr> | ||
− | <td>Baud rate | + | <td>Baud rate</td> |
− | <td>integer [300.. | + | <td>integer [300..3000000]; default: <b>9600</b></td> |
<td>Data rate for serial data transmission (in bits per second (bps)).</td> | <td>Data rate for serial data transmission (in bits per second (bps)).</td> | ||
− | </tr> | + | </tr> |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
<tr> | <tr> | ||
<td>Data bits</td> | <td>Data bits</td> | ||
− | <td> | + | <td>7 {{!}} 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> | ||
Line 415: | Line 408: | ||
<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> | + | </table> |
==Over IP== | ==Over IP== | ||
The <b>Over IP</b> serial type is used to manage serial connections over a TCP/IP network. | The <b>Over IP</b> serial type is used to manage serial connections over a TCP/IP network. | ||
− | |||
− | |||
− | |||
− | |||
− | |||
===Serial Device Configuration=== | ===Serial Device Configuration=== | ||
Line 450: | Line 438: | ||
<tr> | <tr> | ||
<td>Device</td> | <td>Device</td> | ||
− | <td> | + | <td>{{Template: Networking_rutos_manual_serial_ports | rs232={{{rs232}}} | rs485={{{rs485}}} | usb={{{usb}}} }}; default: <b>{{Template: Networking_rutos_manual_default_serial_port | rs232={{{rs232}}} | rs485={{{rs485}}} | usb={{{usb}}} }}</b></td> |
<td>Specifies which serial port will be used for serial communication.</td> | <td>Specifies which serial port will be used for serial communication.</td> | ||
− | </tr> | + | </tr> |
<tr> | <tr> | ||
− | <td>Baud rate | + | <td>Baud rate</td> |
− | <td>integer [300.. | + | <td>integer [300..3000000]; default: <b>9600</b></td> |
<td>Data rate for serial data transmission (in bits per second (bps)).</td> | <td>Data rate for serial data transmission (in bits per second (bps)).</td> | ||
− | </tr> | + | </tr> |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
<tr> | <tr> | ||
<td>Data bits</td> | <td>Data bits</td> | ||
− | <td> | + | <td>5 {{!}} 6 {{!}} 7 {{!}} 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> | + | <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> | + | <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> | ||
Line 557: | Line 535: | ||
</table> | </table> | ||
− | [[File:Networking rutos manual serial utilities over ip mbus configuration | + | [[File:Networking rutos manual serial utilities over ip mbus configuration security.png|border|class=tlt-border]] |
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
Line 568: | Line 546: | ||
<td>Use TLS/SSL</td> | <td>Use TLS/SSL</td> | ||
<td>off {{!}} on; default: <b>off</b></td> | <td>off {{!}} on; default: <b>off</b></td> | ||
− | <td> | + | <td></td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>TLS version</td> | <td>TLS version</td> | ||
<td>Support all {{!}} tlsv1.0 {{!}} tlsv1.1 {{!}} tlsv1.2 {{!}} tlsv1.3; default: <b>Support all</b></td> | <td>Support all {{!}} tlsv1.0 {{!}} tlsv1.1 {{!}} tlsv1.2 {{!}} tlsv1.3; default: <b>Support all</b></td> | ||
− | <td> | + | <td></td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>TLS type</td> | <td>TLS type</td> | ||
<td>Certificate based {{!}} <span style="color: blue;">Pre-Shared-Key based</span>; default: <b>Certificate based</b></td> | <td>Certificate based {{!}} <span style="color: blue;">Pre-Shared-Key based</span>; default: <b>Certificate based</b></td> | ||
− | <td> | + | <td></td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Require certificate</td> | <td>Require certificate</td> | ||
<td>off {{!}} on; default: <b>on</b></td> | <td>off {{!}} on; default: <b>on</b></td> | ||
− | <td> | + | <td></td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td> | + | <td><span style="color: brown;">Require certificate</span></td> |
− | <td>off {{!}} on; default: <b> | + | <td>off {{!}} on; default: <b>on</b></td> |
− | <td> | + | <td></td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Certificate files from device</td> | <td>Certificate files from device</td> | ||
<td>off {{!}} on; default: <b>off</b></td> | <td>off {{!}} on; default: <b>off</b></td> | ||
− | <td> | + | <td>Turn on this option if you want to select generated certificate files from device.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Certificate file</td> | <td>Certificate file</td> | ||
<td>.crt file; default: <b>none</b></td> | <td>.crt file; default: <b>none</b></td> | ||
− | <td> | + | <td>TLS certificate file.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Key file</td> | <td>Key file</td> | ||
<td>.key file; default: <b>none</b></td> | <td>.key file; default: <b>none</b></td> | ||
− | <td> | + | <td>TLS key file.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>CA file</td> | <td>CA file</td> | ||
<td>.ca file; default: <b>none</b></td> | <td>.ca file; default: <b>none</b></td> | ||
− | <td> | + | <td>A certificate authority file.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td><span style="color: blue;">Pre-Shared-Key</span></td> | <td><span style="color: blue;">Pre-Shared-Key</span></td> | ||
<td>string; default: <b>none</b></td> | <td>string; default: <b>none</b></td> | ||
− | <td> | + | <td></td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td><span style="color: blue;">Identify</span></td> | <td><span style="color: blue;">Identify</span></td> | ||
<td>string; default: <b>none</b></td> | <td>string; default: <b>none</b></td> | ||
− | <td> | + | <td></td> |
</tr> | </tr> | ||
</table> | </table> | ||
− | [[File:Networking rutos manual serial utilities over ip mbus configuration | + | [[File:Networking rutos manual serial utilities over ip mbus configuration advanced_v1.png|border|class=tlt-border]] |
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
Line 664: | Line 642: | ||
<td>on {{!}} off; 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> | <td>Close TCP connections everytime data is sent or received (might result in serial data loss).</td> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td | + | <td>Keep alive time</td> |
<td>integer [0..32000]; default: <b>0</b></td> | <td>integer [0..32000]; default: <b>0</b></td> | ||
<td>Close TCP connections everytime data is sent or received (might result in serial data loss).</td> | <td>Close TCP connections everytime data is sent or received (might result in serial data loss).</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td | + | <td>Keep alive interval</td> |
<td>integer [0..32000]; default: <b>0</b></td> | <td>integer [0..32000]; default: <b>0</b></td> | ||
<td>The interval between subsequential keepalive probes.</td> | <td>The interval between subsequential keepalive probes.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td | + | <td>Keep alive probes</td> |
<td>integer [0..32000]; default: <b>0</b></td> | <td>integer [0..32000]; default: <b>0</b></td> | ||
<td>The number of unacknowledged probes.</td> | <td>The number of unacknowledged probes.</td> |
Revision as of 09:44, 20 December 2023
The information in this page is updated in accordance with firmware version .
Note: services were merged and moved to Serial Utilities page from FW version {{{series}}}_R_00.07.03.
Summary
The Serial Utilities page is used to make serial communication configurations of different types.
To make a new serial configuration instance select a serial type from the left-hand navigation menu. In the next page enter a custom name for the new config, select a serial device and click the Add button.
Example from the Modem Configuration page:
[[File:Networking_rutos_manual_serial_utilities_add_new_instance_default_{{{default}}}_v1.png|border|class=tlt-border]]
Then, click the Edit button next to the instance:
[[File:Networking_rutos_manual_serial_utilities_edit_config_default_{{{default}}}_v1.png|border|class=tlt-border]]
This manual page provides an overview of the Serial Utilities page in {{{name}}} devices.
Modem Control
The Modem 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}}}_v2.png|border|class=tlt-border]]
Field | Value | Description |
---|---|---|
Enable | off | on; default: off | Turns the instance on or off. |
Name | string; default: none | Instance name, generated by the user when first creating the configuration. |
Device | ; default: | Specifies which serial port will be used for serial communication. |
Baud rate | integer [300..3000000]; default: 9600 | Data rate for serial data transmission (in bits per second (bps)). |
Data bits | 7 | 8; default: 8 | Number of data bits for each character. |
Stop bits | 1 | 2; default: 1 | 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. |
Parity | None | Odd | Even | Mark | Space; default: None | 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.
|
Flow control | None; default: None | In many circumstances a transmitter might be able to send data faster than the receiver is able to process it. To cope with this, serial lines often incorporate a "handshaking" method, usually distinguished between hardware and software handshaking. |
Mode | Partial control | Full control; default: Partial control | Specifies modem control mode.
|
Start up message | string; default: none | Message to print to serial device when modem control is ready. |
Console
Console mode requires no further configuration than the settings above and is used as a direct-access method to the device's shell interface. For this purpose you may want use such applications as PuTTY on Windows and microcom, minicom, picocom or similar applications on Linux.
[[File:Networking_rutos_manual_serial_utilities_console_default_{{{default}}}_v1.png|border|class=tlt-border]]
Field | Value | Description |
---|---|---|
Enable | off | on; default: off | Turns the instance on or off. |
Name | string; default: none | Instance name, generated by the user when first creating the configuration. |
Device | ; default: | Specifies which serial port will be used for serial communication. |
Baud rate | integer [300..3000000]; default: 9600 | Data rate for serial data transmission (in bits per second (bps)). |
Data bits | 7 | 8; default: 8 | Number of data bits for each character. |
Stop bits | 1 | 2; default: 1 | 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. |
Parity | None | Odd | Even | Mark | Space; default: None | 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.
|
Flow control | None; default: None | In many circumstances a transmitter might be able to send data faster than the receiver is able to process it. To cope with this, serial lines often incorporate a "handshaking" method, usually distinguished between hardware and software handshaking. |
Over IP
The Over IP serial type is used to manage serial connections over a TCP/IP network.
Serial Device Configuration
Configure serial port communication parameters in the Serial Device Configuration section.
[[File:Networking_rutos_manual_serial_utilities_over_ip_serial_default_{{{default}}}_v2.png|border|class=tlt-border]]
Field | Value | Description |
---|---|---|
Enable | off | on; default: off | Turns the instance on or off. |
Name | string; default: none | Instance name, generated by the user when first creating the configuration. |
Device | ; default: | Specifies which serial port will be used for serial communication. |
Baud rate | integer [300..3000000]; default: 9600 | Data rate for serial data transmission (in bits per second (bps)). |
Data bits | 5 | 6 | 7 | 8; default: 8 | Number of data bits for each character. |
Stop bits | 1 | 2; default: 1 | 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. |
Parity | None | Odd | Even | Mark | Space; default: None | 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.
|
Flow control | None; default: None | In many circumstances a transmitter might be able to send data faster than the receiver is able to process it. To cope with this, serial lines often incorporate a "handshaking" method, usually distinguished between hardware and software handshaking. |
Over IP Configuration Settings
You can configure network related parameters of the serial connection in the Over IP Configuration secion.
Field | Value | Description |
---|---|---|
Mode | Server | Client | Client + server | Bidirect; default: Server | This device's role in the connection:
|
Protocol | TCP | UDP; default: TCP | Protocol used in the communication process. |
Client: Destination address | IP | Port; default: empty | Specify server address and port for client to connect to. E.g first field for address second for port. 16 destination addresses are allowed. |
Server: UDP: Predefined addresses | IP | Port; default: empty | Set predefined IP and port for UDP connection. E.g first field for address second for port. |
Listening port | [1..65535]; default: empty | When enabled, all data will be transmitted transparently. |
Field | Value | Description |
---|---|---|
Use TLS/SSL | off | on; default: off | |
TLS version | Support all | tlsv1.0 | tlsv1.1 | tlsv1.2 | tlsv1.3; default: Support all | |
TLS type | Certificate based | Pre-Shared-Key based; default: Certificate based | |
Require certificate | off | on; default: on | |
Require certificate | off | on; default: on | |
Certificate files from device | off | on; default: off | Turn on this option if you want to select generated certificate files from device. |
Certificate file | .crt file; default: none | TLS certificate file. |
Key file | .key file; default: none | TLS key file. |
CA file | .ca file; default: none | A certificate authority file. |
Pre-Shared-Key | string; default: none | |
Identify | string; default: none |
File:Networking rutos manual serial utilities over ip mbus configuration advanced v1.png
Field | Value | Description |
---|---|---|
Raw mode | off | on; default: on | When enabled, all data will be transmitted transparently. |
Remove all zeros | off | on; default: off | When checked, indicates that the first hex zeros should be skipped. |
Inactivity timeout | integer [0..36000]; default: 300 | Specifies period of time in seconds, where server connection must be inactive, to disconnect client. To disable timeout input 0. |
Serial timeout | integer [0..1000]; default: none | Specifies the maximum milliseconds to wait for serial data. |
Max clients | integer [1..32]; default: 4 | Specify how many clients are allowed to connect simultaneously. |
TCP echo | on | off; default: off | Enable software TCP echo. |
Close connections | on | off; default: off | Close TCP connections everytime data is sent or received (might result in serial data loss). |
Keep alive time | integer [0..32000]; default: 0 | Close TCP connections everytime data is sent or received (might result in serial data loss). |
Keep alive interval | integer [0..32000]; default: 0 | The interval between subsequential keepalive probes. |
Keep alive probes | integer [0..32000]; default: 0 | The number of unacknowledged probes. |
IP Filter
The IP Filter section is used for configuring which network is allowed to communicate with the device. You may add a new instance by selecting the Interface and pressing Add.
Then enter the IP address and save.
[[Category:{{{name}}} Services section]]