31,703
edits
Changes
→USB to serial
[[File:Rut955 webui services usb tools usb tools configuration serial type over ip v1.png]]
[[File:Rut955 webui services usb tools usb tools configuration serial type over ip v1.png]]
<table class="nd-mantable">
<tr>
<th>field name</th>
<th>value</th>
<th>description</th>
</tr>
<tr>
<td>Enabled</td>
<td>yes | no; Default: <b>no</b></td>
<td>Enables the RS232 service</td>
</tr>
<tr>
<td>Baud rate</td>
<td>300 | 1200 | 2400 | 4800 | 9600 | 19200 | 38400 | 57600 | 115200; Default: <b>115200</b></td>
<td>Data rate for serial data transmission (in bits per second)</td>
</tr>
<tr>
<td>Data bits</td>
<td>5 | 6 | 7 | 8; Default: <b>8</b></td>
<td>Number of data bits for each character</td>
</tr>
<tr>
<td>Parity</td>
<td>None | Odd | Even; 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.
<ul>
<li><b>None</b> (<b>N</b>) - no parity method is used</li>
<li><b>Odd</b> (<b>O</b>) - the parity bit is set so that the number of "logical ones (1s)" has to be odd</li>
<li><b>Even</b> (<b>E</b>) - the parity bit is set so that the number of "logical ones (1s)" has to be even</li>
</ul>
</td>
</tr>
<tr>
<td>Stop bits</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>
</tr>
<tr>
<td>Flow control</td>
<td>None | RTS/CTS | Xon/Xoff; Default: <b>None</b></td>
<td>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.
<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>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
</ul>
</td>
</tr>
<tr>
<td>Serial type</td>
<td>Over IP; Default: <b>Over IP</b></td>
<td>Specifies the serial connection type.</td>
</tr>
<tr>
<td>Protocol</td>
<td>TCP; Default: <b>TCP</b></td>
<td>Protocol used in the communication process</td>
</tr>
<tr>
<td>Mode</td>
<td>Server | Client | Bidirect; Default: <b>Server</b></td>
<td>Device's role in the connection:
<ul>
<li><b>Server</b> - the device waits for incoming connections</li>
<li><b>Client</b> - the device initiates the connection</li>
<li><b>Bidirect</b> - acts as client by default but waits for incoming connections at the same time</li>
</ul>
</td>
</tr>
<tr>
<td>No leading zeros</td>
<td>yes | no; Default: <b>no</b></td>
<td>When checked, indicates that the first hex zeros should be skipped</td>
</tr>
<tr>
<td><span style="color: red;">Client settings</span>: Server address</td>
<td>ip | host; Default: <b>none</b></td>
<td>IP address or hostname of the server that the client will connect to</td>
</tr>
<tr>
<td><span style="color: red;">Client settings</span>: TCP port</td>
<td>integer [0..65535]; Default: <b>none</b></td>
<td>Server's port number</td>
</tr>
<tr>
<td><span style="color: red;">Client settings</span>: Reconnect interval (s)</td>
<td>integer; Default: <b>none</b></td>
<td>Time period (in seconds) between reconnection attempts in case a connection fails</td>
</tr>
<tr>
<td><span style="color: purple;">Server settings</span>: TCP port</td>
<td>integer [0..65535]; Default: <b>none</b></td>
<td>Internal TCP port number used to listen for incoming connections </td>
</tr>
<tr>
<td><span style="color: purple;">Server settings</span>: Timeout (s)</td>
<td>integer; Default: <b>none</b></td>
<td>Disconnects clients after they remain inactive for an amount time (in seconds) specified in this field</td>
</tr>
<tr>
<td>Output</td>
<td>OC Output | Relay Output; Default: <b>OC Output</b></td>
<td>Output to indicate that the application switched from client (default) to server state (this field becomes visible only in Bidirect mode)</td>
</tr>
<tr>
<td>Output state</td>
<td>1 | 0; Default: <b>0</b></td>
<td>Output state value during which the application reverts to server mode (this field becomes visible only in Bidirect mode)</td>
</tr>
</table>
==Supported USB modems==
==Supported USB modems==
