9,567
edits
Changes
Template:Networking rutos manual rs485 (view source)
Revision as of 12:46, 24 October 2023
, 12:46, 24 October 2023Text replacement - "Template: Networking_rutos_manual_latest_fw" to "Template: Networking_device_manual_latest_fw"
{{Template:Networking_rutos_manual_fw_disclosure
{{Template: Networking_device_manual_fw_disclosure
| fw_version = {{{series}}}_R_00.02.04.1
| series = {{{series}}}
| series = {{{series}}}
| name = {{{name}}}
| fw_version ={{Template: Networking_device_manual_latest_fw
| series = {{{series}}}
| name = {{{name}}}
}}
}}
}}
<b>[[{{{name}}} RS485|RS485]] service was moved to [[{{{name}}} Serial Utilities|Serial Utilities]] page from FW version <i>{{{series}}}_R_00.07.03</i>.
{{#ifeq: {{{series}}} | RUT9 |<br><i><b>Note</b>: <b>[[{{{name}}} RS232/RS485 (legacy WebUI)#RS485|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==
This manual page provides an overview of the RS485 page in {{{name}}} devices.
This manual page provides an overview of the RS485 page in {{{name}}} devices.
==General information==
{{#switch: {{{name}}}
| TRB145|RUT955|RUT956=
===RS485 connector pinout===
----
Below is a depiction of the RS485 connector pins:
<table class="wikitable" style="border: 1px solid black; background: white;">
<tr>
<th style="border: 1px solid black; width: 250px" colspan="3"><span style=color:#104996><b>RS485 connector pinout</b></span></th>
<th style="border: 1px solid white; border-left: 1px solid black; background: white;" rowspan="7">[[File:Trb145_rs485_pinout_v1.png|130px|right|bottom]]</th>
</tr>
<tr>
<td style="border: 1px solid black;">Pin</td>
<td style="border: 1px solid black;">Name</td>
<td style="border: 1px solid black;">Description</td>
</tr>
<tr>
<td style="border: 1px solid black;">1</td>
<td style="border: 1px solid black;">D_N</td>
<td style="border: 1px solid black;">Driver negative signal</td>
</tr>
<tr>
<td style="border: 1px solid black;">2</td>
<td style="border: 1px solid black;">R_N</td>
<td style="border: 1px solid black;">Receiver negative signal</td>
</tr>
<tr>
<td style="border: 1px solid black;">3</td>
<td style="border: 1px solid black;">GND</td>
<td style="border: 1px solid black;">Device ground</td>
</tr>
<tr>
<td style="border: 1px solid black;">4</td>
<td style="border: 1px solid black;">D_P</td>
<td style="border: 1px solid black;">Driver positive signal</td>
</tr>
<tr>
<td style="border: 1px solid black;">5</td>
<td style="border: 1px solid black;">R_P</td>
<td style="border: 1px solid black;">Receiver positive signal</td>
</tr>
<tr>
<td style="border: 1px solid black;">6</td>
<td style="border: 1px solid black;">NC</td>
<td style="border: 1px solid black;">Power input 9-30 VDC</td>
<td style="border: 1px solid white; border-left: 1px solid black; width: 250px" colspan="1"><span style=color:white>filler text</span></td>
</tr>
</table>
===Cable Type===
----
Recommended cable parameters:
<table class="nd-othertables">
<tr>
<th style="width: 300px">PARAMETER</th>
<th style="width: 850px">VALUE</th>
</tr>
<tr>
<td>Cable Type</td>
<td>22-24 AWG, 2 – pair (used for full-duplex networks ) or 1-pair (used for half duplex networks). One addtitional wire for ground connection is needed</td>
</tr>
<tr>
<td>Characteristic cable Impedance</td>
<td>120 Ω @ 1MHz</td>
</tr>
<tr>
<td>Capacitance (conductor to conductor)</td>
<td>36 pF/m</td>
</tr>
<tr>
<td>Propagation Velocity</td>
<td>78% (1.3 ns/ft)</td>
</tr>
</table>}}
===Maximum data rate vs. transmission line length===
===Maximum data rate vs. transmission line length===
----
----
===2-Wire and 4-Wire Networks===
===2-Wire and 4-Wire Networks===
----
----
Below is an example of a 4-wire network electrical connection. There are 3 devices shown in the example. One of the devices is the "master" and other two are "slaves". Termination resistors are placed at each cable end. Four-wire networks consists of one master with its transmitter connected to each of the slaves' receivers on one twisted pair. The slave transmitters are all connected to the master receiver on a second twisted pair:
Below is an example of a 4-wire network electrical connection. There are 3 devices shown in the example. One of the devices is the "master" and other two are "slaves". Termination resistors (120 Ω each) are placed at each cable end. Four-wire networks consists of one master with its transmitter connected to each of the slaves' receivers on one twisted pair. The slave transmitters are all connected to the master receiver on a second twisted pair:
[[File:Services rs485 4wire.PNG]]
[[File:Services rs485 4wire_v2.PNG]]
Example 2-wire network electrical connection: to enable a 2-wire RS485 configuration you need to connect D_P to R_P and D_N to R_N on the device’s RS485 socket. Termination resistors are placed at each cable end:
Example 2-wire network electrical connection: to enable a 2-wire RS485 configuration you need to connect D_P to R_P and D_N to R_N on the device’s RS485 socket. Termination resistors are placed at each cable end (120 Ω each):
[[File:Services rs485 2wire.PNG]]
[[File:Services rs485 2wire_v2.PNG]]
==RS485 Configuration==
==RS485 Configuration==
The <b>RS485 Configuration</b> section is used to set up the main operating parameters and the serial type of the RS485 connector.
The <b>RS485 Configuration</b> section is used to set up the main operating parameters and the serial type of the RS485 connector.
[[File:Networking_rutos_manual_rs485_rs485_configuration.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_rs485_rs485_configuration_data_bits_{{{data_bit}}}.png|border|class=tlt-border]]
<table class="nd-mantable">
<table class="nd-mantable">
</tr>
</tr>
<tr>
<tr>
<td>Baud rate</td>
<td>300 | 1200 | 2400 | 4800 | 9600 | 19200 | 38400 | 57600 | 115200 | 230400 | 460800 | 921600 | 1000000 | 3000000 ; default: <b>300</b></td>
<td>{{{baud_rates}}}; default: <b>{{{baud_rate}}}</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 (bps)).</td>
</tr>
</tr>
<tr>
<tr>
<tr>
<tr>
<td>Serial type</td>
<td>Serial type</td>
<td>[[#Console|Console]] | [[#Over IP|Over IP]] | [[#Modbus gateway|Modbus gateway]]; default: <b>Console</b></td>
<td>[[#Console|Console]] | [[#Over IP|Over IP]] | [[#Modem|Modem]] | [[#Modbus gateway|Modbus gateway]]; default: <b>Console</b></td>
<td>Specifies the serial connection type.<br><b>Look to the sections below for information on different RS485 serial type options.</b></td>
<td>Specifies the serial connection type.<br><b>Look to the sections below for information on different RS485 serial type options.</b></td>
</tr>
</tr>
<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.
[[File:Networking_rutos_manual_usb_tools_usb_to_serial_console_v1.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_usb_tools_printer_server_usb_to_serial_console.png|border|class=tlt-border]]
===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.
[[File:Networking_rutos_manual_usb_tools_usb_to_serial_over_ip_v1.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_rs485_over_ip_v1.png|border|class=tlt-border]]
<table class="nd-mantable">
<table class="nd-mantable">
<tr>
<tr>
<th>Field</th>
<th style="width: 360px>Field</th>
<th>Value</th>
<th>Value</th>
<th>Description</th>
<th>Description</th>
<tr>
<tr>
<td>Protocol</td>
<td>Protocol</td>
<td>TCP | UDP; default: <b>TCP</b></td>
<td><span style="color: blue;">TCP</span> | <span style="color: green;">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>
<td>Raw mode</td>
<td>off {{!}} on; default; default: <b>off</b></td>
<td>When enabled, all data will be transmitted transparently.</td>
</tr>
</tr>
<tr>
<tr>
<td>Mode</td>
<td>Mode</td>
<td><span style="color: red;">Server</span> | <span style="color: purple;">Client</span> | Bidirect; default: <b>Server</b></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>This device's role in the connection:
<td>This device's role in the connection:
<ul>
<ul>
</tr>
</tr>
<tr>
<tr>
<td><span style="color: red;">Server settings</span>: Timeout (s)</td>
<td><span style="color: red;">Server settings</span> | <span style="color: blue;">TCP</span>: Timeout (s)</td>
<td>integer; default: <b>none</b></td>
<td>integer [0..32767]; default: <b>300</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 seconds) after which an inactive clients is disconnected.</td>
</tr>
<tr>
<td><span style="color: orange;">Bidirect</span>: Output</td>{{#switch:{{{series}}}
| TRB2=<td>Configurable Input/Output (2) {{!}} Configurable Input/Output (3) {{!}} Configurable Input/Output (4); default: <b>Configurable Input/Output (2)</b></td>
| TRB1=<td>Configurable Input/Output (3) {{!}} Configurable Input/Output (4); default: <b>Configurable Input/Output (3)</b></td>
| RUT9=<td>Output (4) {{!}} Isolated Output (3,4,8) {{!}} Relay (5,10); default: <b>Output (4)</b></td>}}
<td>Specifies which output to manage.</td>
</tr>
<tr>
<td><span style="color: orange;">Bidirect</span>: Output state</td>
<td>0 {{!}} 1; default: <b>0</b></td>
<td>Default output state value, when the application is started.</td>
</tr>
<tr>
<td><span style="color: red;">Server settings</span> | <span style="color: green;">UDP</span>: Number of clients</td>
<td>1-10; default: <b>1</b></td>
<td>Specifies how many UDP clients will be supported simultaneously (predefined clients does not count towards this limit).</td>
</tr>
<tr>
<td><span style="color: red;">Server settings</span> | <span style="color: green;">UDP</span>: Predefined client 1 address</td>
<td>ip4; default: <b>none</b></td>
<td>Specifies IP address for predefined connection 1.</td>
</tr>
<tr>
<td><span style="color: red;">Server settings</span> | <span style="color: green;">UDP</span>: Predefined port 1</td>
<td>port; default: <b>none</b></td>
<td>Specifies port number for predefined connection 1.</td>
</tr>
<tr>
<td><span style="color: red;">Server settings</span> | <span style="color: green;">UDP</span>: Predefined client 2 address</td>
<td>ip4; default: <b>none</b></td>
<td>Specifies IP address for predefined connection 2.</td>
</tr>
</tr>
<tr>
<tr>
<td><span style="color: red;">Server settings</span>: Open port automatically</td>
<td><span style="color: red;">Server settings</span> | <span style="color: green;">UDP</span>: Predefined port 2</td>
<td>off | on; default: <b>on</b></td>
<td>port; default: <b>none</b></td>
<td>Automatically adds a traffic rule in the firewall configuration to open the required port for NTRIP communication.</td>
<td>Specifies port number for predefined connection 2.</td>
</tr>
</tr>
<tr>
<tr>
</tr>
</tr>
<tr>
<tr>
<td><span style="color: red;">Client settings</span>: Port</td>
<td><span style="color: purple;">Client settings</span>: Port</td>
<td>integer [0..65535]; default: <b>none</b></td>
<td>integer [0..65535]; default: <b>none</b></td>
<td>Server's listening port number.</td>
<td>Server's listening port number.</td>
</tr>
</tr>
<tr>
<tr>
<td><span style="color: red;">Client settings</span>: Reconnect interval (s)</td>
<td><span style="color: purple;">Client settings</span>: Reconnect interval (s)</td>
<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>
<tr>
<tr>
<td>Echo</td>
<td>Serial device read time</td>
<td>integer [0..1000]; default: <b>none</b></td>
<td>Specifies custom read time for the serial device.</td>
</tr>
<tr>
<td>Full Duplex</td>
<td>0 {{!}} 1; default: <b>0</b></td>
<td>Enables RS485 Full-Duplex.</td>
</tr>
<tr>
<td><span style="color: red;">Server settings</span> | <span style="color: blue;">TCP</span>: Max clients</td>
<td>integer [1..32]; default: <b>32</b></td>
<td>Specifies how many clients are allowed to connect simultaneously.</td>
</tr>
<tr>
<td><span style="color: blue;">TCP</span>: Always reconnect</td>
<td>off | on; default: <b>off</b></td>
<td>off | on; default: <b>off</b></td>
<td>Turn RS485 echo on or off.</td>
<td>When enabled, a new TCP connection will be made after sending every data package.</td>
</tr>
</table>
{{#ifeq: {{{modem}}} | 1 |
===Modem===
----
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 such applications with 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_usb_tools_printer_server_usb_to_serial_modem.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Mode</td>
<td>Partial control {{!}} Full control; default: <b>Partial control</b></td>
<td>Specifies modem control mode.
<ul>
<li><b>Partial control</b> - enables modem control with AT commands, mobile connection will be controlled by RUTOS.
<li><b>Full control</b> - enables modem control with AT commands, mobile connection will be controlled by user.
</ul>
</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 an RTU specified by the Slave ID. The Slave ID can be specified by the user or be obtained directly from the Modbus header.
The <b>Modbus gateway</b> serial type allows redirecting TCP data coming to a specified port to an 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|border|class=tlt-border]]
[[File:Networking_rutos_manual_rs485_rs485_configuration_modbus_gateway.png|border|class=tlt-border]]
<table class="nd-mantable">
<table class="nd-mantable">
</tr>
</tr>
<tr>
<tr>
<td>Echo</td>
<td>Full duplex</td>
<td>off | on; default: <b>off</b></td>
<td>off | on; default: <b>off</b></td>
<td>Turn RS485 echo on or off.</td>
<td>Turns RS485 full duplex on or off.</td>
</tr>
</tr>
</table>
</table>
==IP Filter==
The <b>IP Filter</b> 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.
[[File:Networking_rutos_manual_console_ip_filter.png|border|class=tlt-border]]
Then enter the IP address and save.
[[File:Networking_rutos_manual_console_ip_filter_instance.png|border|class=tlt-border]]
[[Category:{{{name}}} Services section]]
[[Category:{{{name}}} Services section]]
