Difference between revisions of "Template:Networking rutos manual usb tools"
(Created page with "{{Template:Networking_rutos_manual_fw_disclosure | fw_version = {{{series}}}_R_00.02.04.1 | series = {{{series}}} }} __TOC__ ==Summary== The <b>USB Tools</b> page is use...") |
|||
(46 intermediate revisions by 6 users not shown) | |||
Line 1: | Line 1: | ||
− | {{Template: | + | {{Template:Networking_rutos_manual_fw_disclosure |
− | | | + | | fw_version = {{{series}}}_R_00.02.04.1 |
− | + | | series = {{{series}}} | |
− | |||
− | |||
− | |||
− | |||
}} | }} | ||
− | + | __TOC__ | |
+ | |||
==Summary== | ==Summary== | ||
− | The <b>USB Tools</b> page is used to | + | The <b>USB Tools</b> page is used to set up USB printer settings. After the printer is connected to the router's USB port and configured, it can be utilized by users in the local network (LAN, WiFi) or remotely. |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | This manual page provides an overview of the Printer Server page in {{{name}}} devices. | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
==Printer Server== | ==Printer Server== | ||
− | The <b>Printer Server</b> feature provides the possibility to configure access to a printer that is connected to the USB port of the device. | + | The <b>Printer Server</b> feature provides the possibility to configure access to a printer that is connected to the USB port of the device. The 'Add' button lets you add and manage additional printers. To configure a printer instance, click the Edit button located next to it: |
− | |||
− | The 'Add' button lets you add and manage additional printers. To configure a printer instance, click the Edit button located next to it: | ||
− | [[File: | + | [[File:Networking_rutx_manual_printer_server_printer_server_v1.png| border | class=tlt-border]] |
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
Line 94: | Line 25: | ||
<tr> | <tr> | ||
<td>Enable</td> | <td>Enable</td> | ||
− | <td>off | + | <td>off | on; default: <b>off</b></td> |
− | <td>Turns | + | <td>Turns printer support on or off.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Device</td> | <td>Device</td> | ||
− | <td> | + | <td>file path; default: <b>/dev/usb/lp0</b></td> |
<td>Printer's device file.</td> | <td>Printer's device file.</td> | ||
</tr> | </tr> | ||
Line 109: | Line 40: | ||
<tr> | <tr> | ||
<td>Bidirectional mode</td> | <td>Bidirectional mode</td> | ||
− | <td>off | + | <td>off | on; default: <b>on</b></td> |
<td>Turns bidirectional mode on or off.</td> | <td>Turns bidirectional mode on or off.</td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
− | |||
− | |||
− | |||
− | ==USB to | + | ===PC and printer setup=== |
+ | ---- | ||
+ | For step-by-step instructions on how to set up a printer for use with the {{{name}}} device, <b>[[How to set up a USB printer (Windows, {{{name}}})|click here]]</b> | ||
+ | |||
+ | ==USB to serial== | ||
− | The device's USB connector can also be used as a <b>serial port</b>. | + | The device's USB connector can also be used as a <b>serial port</b>. |
− | [[File: | + | [[File:Networking_rutos_manual_usb_tools_usb_to_serial_v1.png|border|class=tlt-border]] |
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
Line 131: | Line 63: | ||
<tr> | <tr> | ||
<td>Enabled</td> | <td>Enabled</td> | ||
− | <td>off | + | <td>off | on; default: <b>off</b></td> |
− | <td> | + | <td>Enables the RS232 service</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Baud rate</td> | <td>Baud rate</td> | ||
− | <td>300 | + | <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>Data rate for serial data transmission (in bits per second)</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Data bits</td> | <td>Data bits</td> | ||
− | <td>5 | + | <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>Parity</td> | <td>Parity</td> | ||
− | <td>None | + | <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. | <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> | ||
<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><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><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 157: | Line 89: | ||
<tr> | <tr> | ||
<td>Stop bits</td> | <td>Stop bits</td> | ||
− | <td>1 | + | <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>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>Flow control</td> | <td>Flow control</td> | ||
− | <td>None | + | <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. | <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><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> | ||
Line 172: | Line 104: | ||
<tr> | <tr> | ||
<td>Serial type</td> | <td>Serial type</td> | ||
− | <td>[[#Console|Console]] | + | <td>[[#Console|Console]] | [[#Over IP|Over IP]] | [[#Modbus gateway|Modbus gateway]] | [[#NTRIP client|NTRIP client]]; default: <b>Console</b></td> |
− | <td>Specifies the serial connection type.<br><b>Look to the sections below for information on different USB to Serial type options.</b></td> | + | <td>Specifies the serial connection type.<br><b>Look to the sections below for information on how different USB to Serial type options.</b></td> |
</tr> | </tr> | ||
</table> | </table> | ||
Line 179: | Line 111: | ||
===Console=== | ===Console=== | ||
---- | ---- | ||
− | <b>Console</b> | + | <b>Console</b> 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: | + | [[File:Networking_rutos_manual_usb_tools_usb_to_serial_console_v1.png|border|class=tlt-border]] |
===Over IP=== | ===Over IP=== | ||
Line 187: | Line 119: | ||
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. | ||
− | [[File: | + | [[File:Networking_rutos_manual_usb_tools_usb_to_serial_over_ip_v1.png|border|class=tlt-border]] |
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
Line 197: | Line 129: | ||
<tr> | <tr> | ||
<td>Protocol</td> | <td>Protocol</td> | ||
− | <td>TCP | + | <td>TCP | UDP; 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>Mode</td> | <td>Mode</td> | ||
− | <td><span style="color: | + | <td><span style="color: red;">Server</span> | <span style="color: purple;">Client</span> | Bidirect; default: <b>Server</b></td> |
− | <td> | + | <td>Device's role in the connection: |
<ul> | <ul> | ||
− | <li><b | + | <li><b>Server</b> - the device waits for incoming connections.</li> |
− | <li><b | + | <li><b>Client</b> - the device initiates the connection.</li> |
− | <li><b | + | <li><b>Bidirect</b> - acts as client by default but waits for incoming connections at the same time.</li> |
</ul> | </ul> | ||
</td> | </td> | ||
Line 213: | Line 145: | ||
<tr> | <tr> | ||
<td>No leading zeros</td> | <td>No leading zeros</td> | ||
− | <td>off | + | <td>off | on; default: <b>off</b></td> |
<td>When checked, indicates that the first hex zeros should be skipped.</td> | <td>When checked, indicates that the first hex zeros should be skipped.</td> | ||
</tr> | </tr> | ||
Line 225: | Line 157: | ||
<td>integer; default: <b>none</b></td> | <td>integer; default: <b>none</b></td> | ||
<td>Specifies an inactivity time limit (in second) after which an inactive clients is disconnected.</td> | <td>Specifies an inactivity time limit (in second) after which an inactive clients is disconnected.</td> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td><span style="color: purple;">Client settings</span>: Server Address</td> | <td><span style="color: purple;">Client settings</span>: Server Address</td> | ||
− | <td>ip | + | <td>ip | host; default: <b>none</b></td> |
− | <td>IP address or hostname of the server that | + | <td>IP address or hostname of the server that the client will connect to.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 245: | Line 172: | ||
<td>integer; default: <b>none</b></td> | <td>integer; default: <b>none</b></td> | ||
<td>Time period (in seconds) between reconnection attempts in case a connection fails.</td> | <td>Time period (in seconds) between reconnection attempts in case a connection fails.</td> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>Open port automatically</td> | ||
+ | <td>off | on; default: <b>on</b></td> | ||
+ | <td>Automatically adds a traffic rule in the firewall configuration to open the required port for NTRIP communication.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Echo</td> | <td>Echo</td> | ||
− | <td>off | + | <td>off | on; default: <b>off</b></td> |
<td>Turn USB to serial echo on or off.</td> | <td>Turn USB to serial echo on or off.</td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
+ | |||
===Modbus gateway=== | ===Modbus gateway=== | ||
---- | ---- | ||
− | The <b>Modbus gateway</b> serial type allows redirecting TCP data coming to a specified port to | + | The <b>Modbus gateway</b> 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: | + | [[File:Networking_rutos_manual_usb_tools_usb_to_serial_modbus_gateway_v1.png|border|class=tlt-border]] |
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
Line 268: | Line 201: | ||
<td>Listening IP</td> | <td>Listening IP</td> | ||
<td>ip; default: <b>0.0.0.0</b></td> | <td>ip; default: <b>0.0.0.0</b></td> | ||
− | <td>IP address to listen for incoming connections | + | <td>IP address to listen for incoming connections.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Port</td> | <td>Port</td> | ||
− | <td>integer [0..65535]; default: <b> | + | <td>integer [0..65535]; default: <b>none</b></td> |
<td>Port number to listen for incoming connections.</td> | <td>Port number to listen for incoming connections.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Slave ID configuration type</td> | <td>Slave ID configuration type</td> | ||
− | <td><span style="color: red;">User defined</span> | + | <td><span style="color: red;">User defined</span> | <span style="color: purple;">Obtained from TCP</span>;<br>default: <b><span style="color: red;">User defined</span></b></td> |
<td>Specifies whether slave IDs are user defined or automatically obtained from TCP.</td> | <td>Specifies whether slave IDs are user defined or automatically obtained from TCP.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td><span style="color: red;">Slave ID</span> | + | <td><span style="color: red;">Slave ID</span> | <span style="color: purple;">Permitted slave IDs</span></td> |
− | <td><span style="color: red;">integer </span> | + | <td><span style="color: red;">integer </span> | <span style="color: purple;">range of integers</span>;<br>default: <b><span style="color: red;">1</span> or <span style="color: purple;">1-247</span></b></td> |
<td>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. <br> A range of IDs can be specified by placing a hyphen (<i>-</i>) between two integer numbers. For example, if you permit slave IDs in the range of 10 to 20, you would specify it as: <i>10-20</i><br>You can also specify multiple values that are not connected in a range using commas (<i>,</i>). For example, to specify 6, 50 and 100 as permitted slave IDs, you would have to use: <i>6,50,100</i></td> | <td>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. <br> A range of IDs can be specified by placing a hyphen (<i>-</i>) between two integer numbers. For example, if you permit slave IDs in the range of 10 to 20, you would specify it as: <i>10-20</i><br>You can also specify multiple values that are not connected in a range using commas (<i>,</i>). For example, to specify 6, 50 and 100 as permitted slave IDs, you would have to use: <i>6,50,100</i></td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Open port automatically</td> | <td>Open port automatically</td> | ||
− | <td>off | + | <td>off | on; default: <b>on</b></td> |
− | <td>Automatically adds a traffic rule in the firewall configuration to open the required port for | + | <td>Automatically adds a traffic rule in the firewall configuration to open the required port for NTRIP communication.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Echo</td> | <td>Echo</td> | ||
− | <td>off | + | <td>off | on; default: <b>off</b></td> |
<td>Turn USB to serial echo on or off.</td> | <td>Turn USB to serial echo on or off.</td> | ||
</tr> | </tr> | ||
Line 301: | Line 234: | ||
<b>Networked Transport of RTCM via Internet Protocol (NTRIP)</b> is a protocol for streaming differential GPS (DGPS) data over the Internet in accordance with specification published by RTCM. | <b>Networked Transport of RTCM via Internet Protocol (NTRIP)</b> is a protocol for streaming differential GPS (DGPS) data over the Internet in accordance with specification published by RTCM. | ||
− | [[File: | + | [[File:Networking_rutos_manual_usb_tools_usb_to_serial_ntrip_client_v1.png|border|class=tlt-border]] |
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
Line 321: | Line 254: | ||
<tr> | <tr> | ||
<td>Mount point</td> | <td>Mount point</td> | ||
− | <td> | + | <td>file path | string; default: <b>none</b></td> |
<td>NTRIP mount point.</td> | <td>NTRIP mount point.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Data format</td> | <td>Data format</td> | ||
− | <td>NTRIP V2.0 TCP/IP | + | <td>NTRIP V2.0 TCP/IP | NTRIP V2.0 RSTP/RTP | NTRIP V1.0 | Automatic detection | NTRIP V2.0 UDP; default: <b>NTRIP V1.0</b></td> |
<td>Version of NTRIP protocol.</td> | <td>Version of NTRIP protocol.</td> | ||
</tr> | </tr> | ||
Line 332: | Line 265: | ||
<td>Username</td> | <td>Username</td> | ||
<td>string; default: <b>none</b></td> | <td>string; default: <b>none</b></td> | ||
− | <td> | + | <td>User name for authentication to NTRIP server.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Password</td> | <td>Password</td> | ||
<td>string; default: <b>none</b></td> | <td>string; default: <b>none</b></td> | ||
− | <td>Password for authentication to | + | <td>Password for authentication to NTRIP server.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 346: | Line 279: | ||
<tr> | <tr> | ||
<td>Use device GPS</td> | <td>Use device GPS</td> | ||
− | <td>off | + | <td>off | on; default: <b>off</b></td> |
<td>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.</td> | <td>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.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Open port automatically</td> | <td>Open port automatically</td> | ||
− | <td>off | + | <td>off | on; default: <b>on</b></td> |
− | <td>Automatically adds a traffic rule in the firewall configuration to open the required port for | + | <td>Automatically adds a traffic rule in the firewall configuration to open the required port for NTRIP communication.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Echo</td> | <td>Echo</td> | ||
− | <td>off | + | <td>off | on; default: <b>off</b></td> |
<td>Turn USB to serial echo on or off.</td> | <td>Turn USB to serial echo on or off.</td> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
</tr> | </tr> | ||
</table> | </table> | ||
[[Category:{{{name}}} Services section]] | [[Category:{{{name}}} Services section]] |
Revision as of 14:15, 1 July 2020
Template:Networking rutos manual fw disclosure
Summary
The USB Tools page is used to set up USB printer settings. After the printer is connected to the router's USB port and configured, it can be utilized by users in the local network (LAN, WiFi) or remotely.
This manual page provides an overview of the Printer Server 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. 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 | Enables the RS232 service |
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 how 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 NTRIP 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 NTRIP 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 NTRIP communication. |
Echo | off | on; default: off | Turn USB to serial echo on or off. |
[[Category:{{{name}}} Services section]]