RUT955 RS232: Difference between revisions

From Teltonika Networks Wiki
VisualWikitext
No edit summary
(Replaced content with "{{Template: Networking_rut_manual_ntp_rs232_rs485 <!------------------------DEVICE-----------------------> | name = RUT955 | series = RUT9XX }}")
Tag: Replaced
Line 1: Line 1:
{{Template: Networking_rutos_manual_fw_disclosure
{{Template: Networking_rut_manual_ntp_rs232_rs485
| fw_version = RUT9XX_R_00.06.07
<!------------------------DEVICE----------------------->
| name  = RUT955
| series = RUT9XX
}}
}}
==Summary==
<b>RS232</b> and <b>RS485</b> serial interfaces provide a possibility for legacy devices to gain access to IP networks.
This chapter of the user manual provides an overview of the RS232/RS485 page for {{{name}}} devices.
==RS232==
[[File:Networking_rut_manual_rs232.png|border|class=tlt-border]]
<table class="nd-mantable">
    <tr>
        <th>Field</th>
      <th>Value</th>
      <th>Description</th>
    </tr>
    <tr>
      <td>Enabled</td>
      <td>yes | no; default: <b>no</b></td>
      <td>Turns the RS232 service on or off.</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 (bps)).</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>[[#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>
    </tr>
    <tr>
    <td>Echo</td>
        <td>yes | no; default: <b>no</b></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>
</table>
===RS232 Connector Pinout===
----
RS232 connector type on this device is DCE female. DCE stands for Data Communication Equipment.
[[File:Services rs232 connector.PNG]]
<table class="nd-othertables">
    <tr>
        <th style="width: 30px">PIN</th>
      <th style="width: 60px">NAME*</th>
      <th style="width: 170px">DESCRIPTION*</th>
        <th style="width: 400px">DIRECTION ON THIS DEVICE</th>
    </tr>
    <tr>
      <td>1</td>
      <td>DCD</td>
      <td>Data Carrier Detect</td>
      <td>Output</td>
    </tr>
    <tr>
      <td>2</td>
      <td>RXD</td>
      <td>Receive Data</td>
      <td>Output</td>
    </tr>
    <tr>
    <td>3</td>
        <td>TXD</td>
        <td>Transmit Data</td>
      <td>Input</td>
    </tr>
    <tr>
    <td>4</td>
        <td>DTR</td>
        <td>Data Terminal Ready</td>
      <td>Input</td>
    </tr>
    <tr>
      <td>5</td>
      <td>GND</td>
      <td>Signal Ground</td>
      <td>-</td>
    </tr>
    <tr>
      <td>6</td>
      <td>DSR</td>
      <td>Data Set Ready</td>
      <td>Output</td>
    </tr>
    <tr>
    <td>7</td>
        <td>RTS</td>
        <td>Ready To Send</td>
      <td>Input</td>
    </tr>
    <tr>
    <td>8</td>
        <td>CTS</td>
        <td>Clear To Send</td>
      <td>Output</td>
    </tr>
    <tr>
    <td>9</td>
        <td>RI</td>
        <td>Ring Indicator</td>
      <td>Output (connected to +5V permanently via a 4.7k resistor) </td>
    </tr>
</table>
'''*''' The names and descriptions that indicate signal direction (such as TXD, RXD, RTS, CTS, DTR, and DSR) are named from the point of view of the DTE device.
===Cables===
----
{{Template: webui_services_rs232_cables}}
==RS485==
<b>RS-485</b> is a serial data transmission standard for use in long ranges or noisy environments.
[[File:Services rs485.PNG|border|class=tlt-border ]]
<table class="nd-mantable">
    <tr>
        <th>Field</th>
      <th>Value</th>
      <th>Description</th>
    </tr>
    <tr>
      <td>Enabled</td>
      <td>yes | no; default: <b>no</b></td>
      <td>Turns the RS485 service on or off.</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 (bps)).</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>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>[[#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>
    </tr>
</table>
===Maximum data rate vs. transmission line length===
----
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:
[[File:Services rs485 formula.PNG]]
Where Lmax is the maximum transmission length in meters and DR is maximum data rate in bits per second.
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===
----
Recommended cable parameters:
<table class="nd-othertables">
    <tr>
        <th style="width: 300px">PARAMETER</th>
      <th style="width: 350px">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>
===RS485 connector pin-out===
----
[[File:Services rs485 port.PNG|border|class=tlt-border ]]
<table class="nd-othertables">
    <tr>
        <th style="width: 65px">NAME</th>
      <th style="width: 200px">DESCRIPTION</th>
      <th style="width: 170px">TYPE</th>
    </tr>
    <tr>
      <td>D_P</td>
      <td>Driver positive signal</td>
      <td>Differential Output</td>
    </tr>
    <tr>
      <td>D_N</td>
      <td>Driver negative signal</td>
      <td>Differential Output</td>
    </tr>
    <tr>
    <td>R_P</td>
        <td>Receiver positive signal</td>
        <td>Differential Input</td>
    </tr>
    <tr>
    <td>R_N</td>
        <td>Receiver negative signal</td>
        <td>Differential Input</td>
    </tr>
    <tr>
    <td>Ground</td>
        <td>Device ground</td>
        <td>Differential Output</td>
    </tr>
</table>
===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.
[[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
cable end.
[[File:Services rs485 2wire.PNG|border|class=tlt-border]]
===Termination===
----
'''When to use (place jumper)'''
Termination resistor, equal in resistance to cable characteristic impedance, must be connected at each end of the cable to reduce reflection and ringing of the signals when the cable lengths get relatively long. Rise time of the RUT955 RS-485 driver is about 5 ns, so the maximum unterminated cable length is about 12 cm. As transmission line cables will always be longer than 12 cm, termination is mandatory all the time if RUT955 is located at the end of the cable.
'''When not to use (remove jumper)'''
If your RS-485 consists of more than two devices and the RUT955 router is located not on the end of the line but, for example, in the middle, RUT955 termination resistor needs to be disabled. In this case, place termination at other devices which are situated at the ends of the line.
'''How to enable 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:
[[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.
The connection of the external resistor is shown in the figure:
[[File:Networking rut manual services rs485 termination v1.png|border|class=tlt-border]]
===Number of devices in an RS-485 Network===
----
One RUT955 RS-485 driver is capable of driving a maximum of 32 receivers, provided that the receiver input impedance is 12 kΩ. If receiver impedances are higher, the maximum number of receivers in the network increases. Any combination of receiver types can be connected together, provided their parallel impedance does not exceed RLoad > 375 Ω.
==Modes of different serial types in RS232 and RS485==
===Console===
----
In this mode the serial interface set up as a Linux console of the device. It can be used for debugging purposes, to get the status of the device or to control it.
===Over IP===
----
In '''Over IP Serial''' type the router provides a connection to a TCP/IP network for the devices connected via serial interfaces.
====Mode: Server====
----
[[File:Services rs232 rs485 overip server.PNG|border|class=tlt-border ]]
<table class="nd-mantable">
    <tr>
        <th>Field</th>
      <th>Value</th>
      <th>Description</th>
    </tr>
    <tr>
      <td>Protocol</td>
      <td>TCP; default: '''TCP'''</td>
      <td>Specifies the protocol used in the communication process</td>
    </tr>
    <tr>
      <td>Mode</td>
      <td>Server | Client | Bidirect; default: '''Server'''</td>
      <td>Specifies the device's role in the connection: <br> '''Server''' - the device waits for incoming connections <br> '''Client''' - the device initiates the connection <br> '''Bidirect''' - acts as client by default but waits for incoming connections at the same time</td>
    </tr>
    <tr>
    <td>No leading zeros</td>
        <td>yes | no; default: <b>no</b></td>
        <td>Specifies that the first hex zeros should be skipped</td>
    </tr>
    <tr>
    <td>TCP port</td>
        <td>integer [0..65535]; default: <b>none</b></td>
        <td>The port number used to connect to the server</td>
    </tr>
    <tr>
    <td>Timeout (s)</td>
        <td>integer; default: <b>none</b> </td>
        <td>Disconnects clients after the amount of inactivity time (in seconds) specified in this field</td>
    </tr>
</table>
====Mode: Client====
----
[[File:Services rs232 rs485 overip client.PNG|border|class=tlt-border ]]
<table class="nd-mantable">
    <tr>
        <th>Field</th>
      <th>Value</th>
      <th>Description</th>
    </tr>
    <tr>
      <td>Protocol</td>
      <td>TCP; default: '''TCP'''</td>
      <td>The protocol used for data transmission</td>
    </tr>
    <tr>
      <td>Mode</td>
      <td>Server | Client | Bidirect; default: '''Server'''</td>
      <td>'''Server''' - waits for incoming connection
'''Client''' - initiates the connection
'''Bidirect''' – acts as a client by default, but at the same time waits for incoming connections</td>
    </tr>
    <tr>
    <td>No leading zeros</td>
        <td>yes | no; default: <b>no</b></td>
        <td>Skips first hex zeros</td>
    </tr>
    <tr>
    <td>Server address</td>
        <td>host | ip; default: <b>no</b></td>
        <td>Server address to which the client will connect to</td>
    </tr>
    <tr>
    <td>TCP port</td>
        <td>integer [0..65535]; default: <b>none</b></td>
        <td>The port number used to listen for incoming connections</td>
    </tr>
    <tr>
    <td>Reconnect intervals (s)</td>
        <td>integer; default: <b>none</b></td>
        <td>Indicates the time period between reconnection attempts</td>
    </tr>
</table>
====Mode: Bidirect====
----
[[File:Networking_rut955_manual_rs232_rs485_over_ip_bidirect.png|border|class=tlt-border ]]
<table class="nd-mantable">
    <tr>
        <th>Field</th>
      <th>Value</th>
      <th>Description</th>
    </tr>
    <tr>
      <td>Always reconnect</td>
      <td>yes | no; default: <b>no</b></td>
      <td>When checked, established a new TCP connection aftereach message.</td>
    </tr>
    <tr>
      <td>Mode</td>
      <td>Server | Client | Bidirect; default: <b>Server</b></td>
      <td>Serial connection operating mode.
            <ul>
                <li><b>Server</b> - this device wait for incoming connection.</li>
                <li><b>Client</b> - this device initiates the connection</li>
                <li><b>Bidirect</b> – acts as a client by default, but at the same time waits for incoming connections</li>
            </ul>
        </td>
    </tr>
    <tr>
    <td>Server address</td>
        <td>host | ip; default: <b>no</b></td>
        <td>IP address or hostname of the server that this client will connect to.</td>
    </tr>
    <tr>
    <td>TCP port</td>
        <td>integer [0..65535]; default: <b>none</b></td>
        <td>Internal port number used to listen for incoming connections.</td>
    </tr>
    <tr>
      <td>Reconnect intervals (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>Port</td>
      <td>integer [0..65535]; default: <b>none</b></td>
      <td>Server's listening port number.</td>
    </tr>
    <tr>
    <td>Timeout (s)</td>
        <td>integer; default: <b>none</b></td>
        <td>Disconnects client after the specified timeout of inactivity</td>
    </tr>
    <tr>
    <td>Output</td>
        <td>OC Output | Relay Output; default: <b>OC Output</b></td>
        <td>Output to indicate that application switched from client (default) to server state.</td>
    </tr>
    <tr>
    <td>Output state</td>
        <td>integer [0..1]; default: <b>0</b></td>
        <td>Output state value after the application reverts to server mode.</td>
    </tr>
</table>
===Modem===
----
With Modem Serial type, the router imitates a dial-up modem. Connections to TCP/IP networks can be established using AT commands. The connection can be initiated by the device connected via serial interface with an ATD command: ATD <host>:<port>. If Direct connect settings are specified, the connection to the server is always active. Data mode can be entered by issuing the ATD command. Incoming connections are indicated by sending a RING to the serial interface.
[[File:Services rs232 rs485 modem v 2.png|border|class=tlt-border ]]
<table class="nd-mantable">
    <tr>
        <th>Field</th>
      <th>Value</th>
      <th>Description</th>
    </tr>
    <tr>
      <td>Direct connect</td>
      <td>host:port | ip:port; default: <b>none</b></td>
      <td>Maintains a constant connection to specified host. Leave empty to use an ATD command to initiate the connection</td>
    </tr>
    <tr>
      <td>TCP port</td>
      <td>integer [0..65535]; default: <b>none</b></td>
      <td>The port number used to listen for incoming connections. Leave it empty to disable incoming connections</td>
    </tr>
    <tr>
    <td>Initiation string</td>
        <td>string; default: <b>none</b></td>
        <td>A command string that will be sent to the modem to initiate it in some special way</td>
    </tr>
    <tr>
    <td>No extra CR LF in response</td>
        <td>yes | no; default: '''yes'''</td>
        <td>Removes extra CR LF before and LF after response code</td>
    </tr>
</table>
This is the AT command set<span class="asterisk">*</span> used in Modem mode of the serial interfaces:
<table class="nd-othertables">
    <tr>
        <th style="width: 85px">COMMAND</th>
      <th style="width: 210px">DESCRIPTION</th>
      <th style="width: 360px">USAGE</th>
    </tr>
    <tr>
      <td>A</td>
      <td>Answers incoming call</td>
      <td>To answer incoming connection: ATA</td>
    </tr>
    <tr>
      <td>D</td>
      <td>Dial a number</td>
      <td>To initiate data connection: ATD <host>:<port> <br>
To enter data mode with Direct connect settings: ATD</td>
    </tr>
    <tr>
    <td>E</td>
        <td>Local echo</td>
        <td>Turn local echo on: ATE1<br>
Turn local echo off: ATE0</td>
    </tr>
    <tr>
    <td>H</td>
        <td>Hang up current call</td>
        <td>To end data connection: ATH</td>
    </tr>
    <tr>
    <td>O</td>
        <td>Return to data mode</td>
        <td>To return to data mode from command mode: ATO</td>
    </tr>
    <tr>
    <td>Z</td>
        <td>Reset to default configuration</td>
        <td>To reset the modem to default configuration: ATZ</td>
    </tr>
</table>
<font size="-1"><span class="asterisk">*</span> Only these commands are supported in Modem mode.</font>
===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:Services_rs232_rs485_modbus_gateway.PNG|border|class=tlt-border ]]
<table class="nd-mantable">
    <tr>
        <th>Field</th>
      <th>Value</th>
      <th>Description</th>
    </tr>
    <tr>
      <td>Listening IP</td>
      <td>ip; default: '''0.0.0.0'''</td>
      <td>IP address on which the Modbus gateway will wait for incoming connections</td>
    </tr>
    <tr>
      <td>Port</td>
      <td>integer [0..65535]; default: <b>none</b></td>
      <td>The port number used to listen for incoming connections</td>
    </tr>
    <tr>
    <td>Slave ID configuration type</td>
        <td>User defined | Obtained from TCP; default: '''User defined'''</td>
        <td>Specifies whether slave IDs are user defined or automatically obtained from TCP</td>
    </tr>
    <tr>
    <td>Slave ID | Permitted slave IDs</td>
        <td>integer | range of integers; default: '''1'''</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''' ('''-''') between two integer numbers. For example, if you permitt slave IDs in the range of 10 to 20, you would specify it as: '''10-20''' <br> 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'''</td>
    </tr>
</table>
===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_rut955_manual_rs232_rs485_ntrip_client.png|border|class=tlt-border]]
<table class="nd-mantable">
    <tr>
        <th>Field</th>
      <th>Value</th>
      <th>Description</th>
    </tr>
    <tr>
      <td>IP address</td>
      <td>ip; default: <b>0.0.0.0</b></td>
      <td>IP address of an NTRIP server.</td>
    </tr>
    <tr>
      <td>Port</td>
      <td>integer [0..65535]; default: <b>none</b></td>
      <td>Port number of the NTRIP server.</td>
    </tr>
    <tr>
    <td>Mount point</td>
        <td>string; default: <b>none</b></td>
        <td>NTRIP mount point.</td>
    </tr>
    <tr>
    <td>Data format</td>
        <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>Specifies the version of NTRIP.</td>
    </tr>
    <tr>
      <td>User name</td>
      <td>string; default: <b>none</b></td>
      <td>Username for authentication to NTRIP server.</td>
    </tr>
    <tr>
      <td>Password</td>
      <td>string; default: <b>none</b></td>
      <td>Password for authentication to NTRIP server.</td>
    </tr>
    <tr>
    <td>Initial NMEA-GGA</td>
        <td>string; default: <b>none</b></td>
        <td>Optional NMEA string that will be used as the default value when initiating a connection to an NTRIP server (this value is only sent to the server if there is no NMEA from router's GPS device).</td>
    </tr>
    <tr>
    <td>Acquire NMEA-GGA</td>
        <td>yes | no; default: <b>no</b></td>
        <td>Obtains initial NMEA-GGA string from GPS module of this device. Only works if GPS service is enabled and location fix is obtained at the time of NTRIP service start.</td>
    </tr>
</table>
[[Category:RUT955 Services section]]

Revision as of 12:59, 19 November 2020

Main Page > EOL Products > RUT955 > RUT955 Manual > RUT955 WebUI > RUT955 Services section > RUT955 RS232

Template:Networking rut manual ntp rs232 rs485

Retrieved from "https://wiki.teltonika-networks.com/index.php?title=RUT955_RS232&oldid=75333"