Template:Networking rutos manual usb tools: Difference between revisions
No edit summary |
No edit summary |
||
Line 71: | Line 71: | ||
<td>Baud rate</td> | <td>Baud rate</td> | ||
<td>300 | 1200 | 2400 | 4800 | 9600 | 19200 | 38400 | 57600 | 115200; default: <b>115200</b></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> | <td>Data rate for serial data transmission (in bits per second).</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 84: | Line 84: | ||
<ul> | <ul> | ||
<li><b>None</b> (<b>N</b>) - no parity method is used</li> | <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>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> | <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> | </ul> | ||
</td> | </td> | ||
Line 92: | Line 92: | ||
<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> | ||
Line 99: | Line 99: | ||
<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. | <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> | <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. | ||
</ul> | </ul> | ||
</td> | </td> |
Revision as of 07:32, 3 July 2020
Template:Networking rutos manual fw disclosure
Summary
The USB Tools page is used to manage services related to the device's USB connector.
This manual page provides an overview of the USB Tools page in {{{name}}} devices.
Printer Server
The Printer Server feature provides the possibility to configure access to a printer that is connected to the USB port of the device. After the printer is connected to the device's USB port and configured, it can be utilized by users in the local network (LAN, WiFi) or remotely.
The 'Add' button lets you add and manage additional printers. To configure a printer instance, click the Edit button located next to it:
File:Networking rutx manual printer server printer server v1.png
Field | Value | Description |
---|---|---|
Enable | off | on; default: off | Turns printer support on or off. |
Device | file path; default: /dev/usb/lp0 | Printer's device file. |
Port | integer [9100..9109]; default: 9100 | Printer's TCP port. |
Bidirectional mode | off | on; default: on | Turns bidirectional mode on or off. |
PC and printer setup
For step-by-step instructions on how to set up a printer for use with the {{{name}}} device, [[How to set up a USB printer (Windows, {{{name}}})|click here]]
USB to Serial
The device's USB connector can also be used as a serial port.
File:Networking rutos manual usb tools usb to serial v1.png
Field | Value | Description |
---|---|---|
Enabled | off | on; default: off | Turns the USB to Serial service on or off. |
Baud rate | 300 | 1200 | 2400 | 4800 | 9600 | 19200 | 38400 | 57600 | 115200; default: 115200 | Data rate for serial data transmission (in bits per second). |
Data bits | 5 | 6 | 7 | 8; default: 8 | Number of data bits for each character |
Parity | None | Odd | Even; 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.
|
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. |
Flow control | None | RTS/CTS | Xon/Xoff; 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.
|
Serial type | Console | Over IP | Modbus gateway | NTRIP client; default: Console | Specifies the serial connection type. Look to the sections below for information on different USB to Serial type options. |
Console
Console 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 use such applications as PuTTY on Windows and microcom, minicom, picocom or similar applications on Linux.
File:Networking rutos manual usb tools usb to serial console v1.png
Over IP
The Over IP serial type is used to manage serial connections over a TCP/IP network.
File:Networking rutos manual usb tools usb to serial over ip v1.png
Field | Value | Description |
---|---|---|
Protocol | TCP | UDP; default: TCP | Protocol used in the communication process. |
Mode | Server | Client | Bidirect; default: Server | Device's role in the connection:
|
No leading zeros | off | on; default: off | When checked, indicates that the first hex zeros should be skipped. |
Server settings: Port | integer [0..65535]; default: none | Internal port number used to listen for incoming connections. |
Server settings: Timeout (s) | integer; default: none | Specifies an inactivity time limit (in second) after which an inactive clients is disconnected. |
Client settings: Server Address | ip | host; default: none | IP address or hostname of the server that the client will connect to. |
Client settings: Port | integer [0..65535]; default: none | Server's listening port number. |
Client settings: Reconnect interval (s) | integer; default: none | Time period (in seconds) between reconnection attempts in case a connection fails. |
Open port automatically | off | on; default: on | Automatically adds a traffic rule in the firewall configuration to open the required port for serial communication. |
Echo | off | on; default: off | Turn USB to serial echo on or off. |
Modbus gateway
The Modbus gateway serial type allows redirecting TCP data coming to a specified port to RTU specified by the Slave ID. The Slave ID can be specified by the user or be obtained directly from the Modbus header.
File:Networking rutos manual usb tools usb to serial modbus gateway v1.png
Field | Value | Description |
---|---|---|
Listening IP | ip; default: 0.0.0.0 | IP address to listen for incoming connections. |
Port | integer [0..65535]; default: none | Port number to listen for incoming connections. |
Slave ID configuration type | User defined | Obtained from TCP; default: User defined |
Specifies whether slave IDs are user defined or automatically obtained from TCP. |
Slave ID | Permitted slave IDs | integer | range of integers; default: 1 or 1-247 |
Specifies the slave ID of range of permitted slave IDs. The way this field is named and its function depends on the value of the Slave ID configuration field. A range of IDs can be specified by placing a hyphen (-) between two integer numbers. For example, if you permit slave IDs in the range of 10 to 20, you would specify it as: 10-20 You can also specify multiple values that are not connected in a range using commas (,). For example, to specify 6, 50 and 100 as permitted slave IDs, you would have to use: 6,50,100 |
Open port automatically | off | on; default: on | Automatically adds a traffic rule in the firewall configuration to open the required port for serial communication. |
Echo | off | on; default: off | Turn USB to serial echo on or off. |
NTRIP client
Networked Transport of RTCM via Internet Protocol (NTRIP) is a protocol for streaming differential GPS (DGPS) data over the Internet in accordance with specification published by RTCM.
File:Networking rutos manual usb tools usb to serial ntrip client v1.png
Field | Value | Description |
---|---|---|
IP address | ip; default: 0.0.0.0 | IP address of an NTRIP server. |
Port | integer [0..65535]; default: none | TCP/UDP port used for NTRIP communication. |
Mount point | file path | string; default: none | NTRIP mount point. |
Data format | NTRIP V2.0 TCP/IP | NTRIP V2.0 RSTP/RTP | NTRIP V1.0 | Automatic detection | NTRIP V2.0 UDP; default: NTRIP V1.0 | Version of NTRIP protocol. |
Username | string; default: none | User name for authentication to NTRIP server. |
Password | string; default: none | Password for authentication to NTRIP server. |
Default NMEA string | string; default: none | Optional NMEA string that will be used as the default value when initiating the connection to the NTRIP server (this value is only sent to the server if there is no NMEA from router's GPS device). |
Use device GPS | off | on; default: off | Allows to obtain default NMEA string from the router's GPS device. Only works if GPS service is enabled and location fix is obtained at the time of NTRIP service start. |
Open port automatically | off | on; default: on | Automatically adds a traffic rule in the firewall configuration to open the required port for serial communication. |
Echo | off | on; default: off | Turn USB to serial echo on or off. |
[[Category:{{{name}}} Services section]]