31,703
edits
Changes
no edit summary
<table class="nd-mantable">
<table class="nd-mantable">
<tr>
<tr>
<th>field name</th>
<th>Field</th>
<th>value</th>
<th>Value</th>
<th>description</th>
<th>Description</th>
</tr>
</tr>
<tr>
<tr>
<td>Enabled</td>
<td>Enabled</td>
<td>yes | no; default: <b>no</b></td>
<td>yes | no; default: <b>no</b></td>
<td>When checked, enables the RS232 service</td>
<td>Turns the RS232 service on or off.</td>
</tr>
</tr>
<tr>
<tr>
<td>Baud rate</td>
<td>Baud rate</td>
<td>300 | 1200 | 2400 | 4800 | 9600 | 19200 | 38400 | 57600 | 115200; default: '''115200'''</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 (bps)).</td>
</tr>
</tr>
<tr>
<tr>
<td>Data bits</td>
<td>Data bits</td>
<td>5 | 6 | 7 | 8; default: '''8'''</td>
<td>5 | 6 | 7 | 8; default: <b>8</b></td>
<td>The 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 | Odd | Even; default: '''None'''</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. <br> '''None''' ('''N''') - no parity method is used <br> '''Odd''' ('''O''') - the parity bit is set so that the number of "logical ones (1s)" has to be odd <br> '''Even''' ('''E''') - the parity bit is set so that the number of "logical ones (1s)" has to be even</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>
<tr>
<tr>
<td>Stop bits</td>
<td>Stop bits</td>
<td>1 | 2; default: '''1'''</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>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>
<tr>
<tr>
<td>Serial type</td>
<td>Serial type</td>
<td>[[RUT955_RS232/RS485#Console|Console]] | [[RUT955_RS232/RS485#Over_IP|Over IP]] | [[RUT955_RS232/RS485#Modem|Modem]] | [[RUT955_RS232/RS485#Modbus_gateway|Modbus gateway]] | [[RUT955_RS232/RS485#NTRIP_client|NTRIP client]]; default: <b>Console</b></td>
<td>[[#Console|Console]] | [[#Over_IP|Over IP]] | [[#Modem|Modem]] | [[#Modbus_gateway|Modbus gateway]] | [[#NTRIP_client|NTRIP client]]; default: <b>Console</b></td>
<td>Specifies the serial connection type.</td>
<td>Specifies the serial connection type. More information on serial types can be found in each of their respective sections of this manual page.</td>
</tr>
</tr>
<tr>
<tr>
<td>Echo</td>
<td>Echo</td>
<td>yes | no; default: <b>no</b></td>
<td>yes | no; default: <b>no</b></td>
<td>Toggles RS232 echo ON or OFF. RS232 echo is a loopback test usually used to check whether the RS232 cable is working properly</td>
<td>Turns RS232 echo on or off. RS232 echo is a loopback test usually used to check whether the RS232 cable is working properly.</td>
</tr>
</tr>
</table>
</table>
RS232 connector type on this device is DCE female. DCE stands for Data Communication Equipment.
RS232 connector type on this device is DCE female. DCE stands for Data Communication Equipment.
[[Image:Services rs232 connector.PNG]]
[[File:Services rs232 connector.PNG]]
<table class="nd-othertables">
<table class="nd-othertables">
==RS485==
==RS485==
<b>RS-485</b> is a serial data transmission standard for use in long ranges or noisy environments.
[[Image:Services rs485.PNG|border|class=tlt-border ]]
[[File:Services rs485.PNG|border|class=tlt-border ]]
<table class="nd-mantable">
<table class="nd-mantable">
<tr>
<tr>
<th>field name</th>
<th>Field</th>
<th>value</th>
<th>Value</th>
<th>description</th>
<th>Description</th>
</tr>
</tr>
<tr>
<tr>
<td>Enabled</td>
<td>Enabled</td>
<td>yes | no; default: <b>no</b></td>
<td>yes | no; default: <b>no</b></td>
<td>Toggles the RS485 serial port function ON or OFF</td>
<td>Turns the RS485 service on or off.</td>
</tr>
</tr>
<tr>
<tr>
<td>Baud rate</td>
<td>Baud rate</td>
<td>300 | 1200 | 2400 | 4800 | 9600 | 19200 | 38400 | 57600 | 115200; default: '''115200'''</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 (bps)).</td>
</tr>
</tr>
<tr>
<tr>
<td>Parity</td>
<td>Parity</td>
<td>None | Odd | Even; default: '''None'''</td>
<td>None | Odd | Even; default: <b>None</b></td>
<td>The parity bit setting used for error detection during data transfer</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>
<tr>
<tr>
<td>Flow control</td>
<td>Flow control</td>
<td>None | RTS- CTS | Xon-Xoff; default: '''None'''</td>
<td>None | RTS/CTS | Xon/Xoff; default: <b>None</b></td>
<td>Specifies how many stop bits will be used to detect the end of character</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>
<tr>
<tr>
<td>Serial type</td>
<td>[[#Console|Console]] | [[#Over_IP|Over IP]] | [[#Modem|Modem]] | [[#Modbus_gateway|Modbus gateway]] | [[#NTRIP_client|NTRIP client]]; default: <b>Console</b></td>
<td>Specifies the serial connection type. More information on serial types can be found in each of their respective sections of this manual page.</td>
<td>Allows IP to connect to server</td>
</tr>
</tr>
</table>
</table>
===Maximum data rate vs. transmission line length===
===Maximum data rate vs. transmission line length===
----
----
RS-485 standart can be used for network lengths up to 1200 meters, but the maximum usable data rate decreases as the transmission length increases. A device operating at the maximum data transfer rate (10Mbps) is limited to a transmission length of about 12 meters, while the 100kbps data rate can achieve a distance up to 1200 meters. A rough relation between maximum transmission length and data rate can be calculated using this approximation:
The RS-485 standard can be used for network lengths up to 1200 meters, but the maximum usable data rate decreases as the transmission length increases. A device operating at the maximum data transfer rate (10 Mbps) is limited to a transmission length of about 12 meters, while the 100 kbps data rate can achieve a distance up to 1200 meters. A rough relation between maximum transmission length and data rate can be calculated using this approximation:
[[Image:Services rs485 formula.PNG]]
[[File:Services rs485 formula.PNG]]
Where Lmax is the maximum transmission length in meters and DR is maximum data rate in bits per second.
Where Lmax is the maximum transmission length in meters and DR is maximum data rate in bits per second.
Twisted pair is the prefered cable type for RS-485 networks. Twisted pair cables pick up noise and other electromagnetically induced voltages as common mode signals, which are rejected by the differential receivers.
Twisted pair is the preferred cable type for RS-485 networks. Twisted pair cables pick up noise and other electromagnetically induced voltages as common mode signals, which are rejected by the differential receivers.
===Cable Type===
===Cable Type===
===RS485 connector pin-out===
===RS485 connector pin-out===
----
----
[[Image:Services rs485 port.PNG|border|class=tlt-border ]]
[[File:Services rs485 port.PNG|border|class=tlt-border ]]
<table class="nd-othertables">
<table class="nd-othertables">
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 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.
[[Image:Services rs485 4wire.PNG|border|class=tlt-border ]]
[[File:Services rs485 4wire.PNG|border|class=tlt-border ]]
Example 2-wire network electrical connection: to enable a 2-wire RS-485 configuration on a Teltonika router, you need to connect D_P to R_P and D_N to R_N on the device’s RS-485 socket. Termination resistors are placed at each
Example 2-wire network electrical connection: to enable a 2-wire RS-485 configuration on a Teltonika router, you need to connect D_P to R_P and D_N to R_N on the device’s RS-485 socket. Termination resistors are placed at each
cable end.
cable end.
[[Image:Services rs485 2wire.PNG|border|class=tlt-border]]
[[File:Services rs485 2wire.PNG|border|class=tlt-border]]
===Termination===
===Termination===
120 Ω termination resistor is included on the RUT955 PCB and can be enabled by shorting contacts (shown in the picture below), placing 2.54mm pitch jumper:
120 Ω termination resistor is included on the RUT955 PCB and can be enabled by shorting contacts (shown in the picture below), placing 2.54mm pitch jumper:
[[Image:Services rs485 jumper.PNG|border|class=tlt-border ]]
[[File:Services rs485 jumper.PNG|border|class=tlt-border ]]
But on the [[RUT955_Product_Change_Notifications#2019.01.22:_visual_design_changes|RUT955 improved housing design ]] PCB the terminator connections are missing. Since the housing of the RUT955 improved model is not disassembled, the termination resistor must be connected to the outside of the device by connecting a through-hole 100 ohm resistor to the terminal contacts.
But on the [[RUT955_Product_Change_Notifications#2019.01.22:_visual_design_changes|RUT955 improved housing design ]] PCB the terminator connections are missing. Since the housing of the RUT955 improved model is not disassembled, the termination resistor must be connected to the outside of the device by connecting a through-hole 100 ohm resistor to the terminal contacts.
The connection of the external resistor is shown in the figure:
The connection of the external resistor is shown in the figure:
[[Image:Networking rut manual services rs485 termination v1.png|border|class=tlt-border]]
[[File:Networking rut manual services rs485 termination v1.png|border|class=tlt-border]]
===Number of devices in an RS-485 Network===
===Number of devices in an RS-485 Network===
====Mode: Server====
====Mode: Server====
----
----
[[Image:Services rs232 rs485 overip server.PNG|border|class=tlt-border ]]
[[File:Services rs232 rs485 overip server.PNG|border|class=tlt-border ]]
<table class="nd-mantable">
<table class="nd-mantable">
<tr>
<tr>
<th>field name</th>
<th>Field</th>
<th>value</th>
<th>Value</th>
<th>description</th>
<th>Description</th>
</tr>
</tr>
<tr>
<tr>
====Mode: Client====
====Mode: Client====
----
----
[[Image:Services rs232 rs485 overip client.PNG|border|class=tlt-border ]]
[[File:Services rs232 rs485 overip client.PNG|border|class=tlt-border ]]
<table class="nd-mantable">
<table class="nd-mantable">
<tr>
<tr>
<th>field name</th>
<th>Field</th>
<th>value</th>
<th>Value</th>
<th>description</th>
<th>Description</th>
</tr>
</tr>
<tr>
<tr>
====Mode: Bidirect====
====Mode: Bidirect====
----
----
[[Image:Networking_rut955_manual_rs232_rs485_over_ip_bidirect.png|border|class=tlt-border ]]
[[File:Networking_rut955_manual_rs232_rs485_over_ip_bidirect.png|border|class=tlt-border ]]
<table class="nd-mantable">
<table class="nd-mantable">
<table class="nd-mantable">
<table class="nd-mantable">
<tr>
<tr>
<th>field name</th>
<th>Field</th>
<th>value</th>
<th>Value</th>
<th>description</th>
<th>Description</th>
</tr>
</tr>
<tr>
<tr>
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.
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.
[[Image:Services_rs232_rs485_modbus_gateway.PNG|border|class=tlt-border ]]
[[File:Services_rs232_rs485_modbus_gateway.PNG|border|class=tlt-border ]]
<table class="nd-mantable">
<table class="nd-mantable">
<tr>
<tr>
<th>field name</th>
<th>Field</th>
<th>value</th>
<th>Value</th>
<th>description</th>
<th>Description</th>
</tr>
</tr>
<tr>
<tr>
