RUT955 RS232: Difference between revisions

==Summary==

RS232 and RS485 functions are designed to utilize available serial interfaces of the router. Serial interfaces provide a possibility for legacy devices to gain access to IP networks. This chapter is an overview of the RS232/RS485 functions in RUT routers.

==RS232==

     <tr>

       <td>Enabled</td>

       <td>When checked, enables the RS232 service</td>

     </tr>

     <tr>

       <td>Baud rate</td>

       <td>Sets the data rate for serial data transmission (in bits per second)</td>

     </tr>

     <tr>

     <td>Data bits</td>

         <td>The number of data bits for each character</td>

     </tr>

     <tr>

     <td>Parity</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>

     </tr>

     <tr>

       <td>Stop bits</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>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. <br> '''RTS/CTS''' - 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 <br> '''Xon/Xoff''' - 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</td>

     </tr>

     <tr>

     <td>Serial type</td>

         <td>Specifies the serial connection type.</td>

     </tr>

     <tr>

     <td>Echo</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>

     </tr>

     <tr>

       <td>Enabled</td>

       <td>Toggles the RS485 serial port function ON or OFF</td>

     </tr>

     <tr>

       <td>Baud rate</td>

       <td>The communication speed of the serial interface</td>

     </tr>

     <tr>

     <td>Parity</td>

         <td>The parity bit setting used for error detection during data transfer</td>

     </tr>

     <tr>

     <td>Flow control</td>

         <td>Specifies how many stop bits will be used to detect the end of character</td>

     </tr>

     <tr>

       <td>Serial type</td>

       <td>Specifies the function of the serial interface</td>

     </tr>

     <tr>

     <td>Interface</td>

         <td>Interface used for connection</td>

     </tr>

     <tr>

     <td>Allow IP</td>

         <td>Allows IP to connect to server</td>

     </tr>

     <tr>

       <td>Protocol</td>

       <td>Specifies the protocol used in the communication process</td>

     </tr>

     <tr>

       <td>Mode</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>Specifies that the first hex zeros should be skipped</td>

     </tr>

     <tr>

     <td>TCP port</td>

         <td>The port number used to connect to the server</td>

     </tr>

     <tr>

     <td>Timeout (s)</td>

         <td>Disconnects clients after the amount of inactivity time (in seconds) specified in this field</td>

     </tr>

     <tr>

       <td>Protocol</td>

       <td>The protocol used for data transmission</td>

     </tr>

     <tr>

       <td>Mode</td>

       <td>'''Server''' - waits for incoming connection

     <tr>

     <td>No leading zeros</td>

         <td>Skips first hex zeros</td>

     </tr>

     <tr>

     <td>Server address</td>

         <td>Server address to which the client will connect to</td>

     </tr>

     <tr>

     <td>TCP port</td>

         <td>The port number used to listen for incoming connections</td>

     </tr>

     <tr>

     <td>Reconnect intervals (s)</td>

         <td>Indicates the time period between reconnection attempts</td>

     </tr>

====Mode: Bidirect====

----

<table class="nd-mantable">

     <tr>

       <td>Mode</td>

     </tr>

     <tr>

       <td>No leading zeros </td>

       <td>Skips first hex zeros</td>

     </tr>

     <tr>

     <td>Server address</td>

         <td>Server address to which the client will connect to</td>

     </tr>

     <tr>

     <td>TCP port</td>

         <td>The port number used to listen for incoming connections</td>

     </tr>

     <tr>

       <td>Reconnect intervals (s)</td>

       <td>Indicates the time period between reconnection attempts</td>

     </tr>

     <tr>

       <td>TCP port</td>

       <td>The port number used to listen for incoming connections</td>

     </tr>

     <tr>

     <td>Timeout (s)</td>

         <td>Disconnects client after the specified timeout of inactivity</td>

     </tr>

     <tr>

     <td>Output</td>

         <td>Output to indicate that application switched from client (default) to server state</td>

     </tr>

     <tr>

     <td>Output state</td>

         <td>Output state value after the application reverts to server mode</td>

     </tr>

     <tr>

       <td>Direct connect</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>The port number used to listen for incoming connections. Leave it empty to disable incoming connections</td>

     </tr>

     <tr>

     <td>Initiation string</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>Removes extra CR LF before and LF after response code</td>

     </tr>

     <tr>

       <td>Listening IP</td>

       <td>IP address on which the Modbus gateway will wait for incoming connections</td>

     </tr>

     <tr>

       <td>Port</td>

       <td>The port number used to listen for incoming connections</td>

     </tr>

     <tr>

     <td>Slave ID configuration type</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>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>

     <tr>

       <td>IP address</td>

       <td>IP address of the NTRIP server </td>

     </tr>

     <tr>

       <td>Port</td>

       <td>TCP/UDP port used for NTRIP communication</td>

     </tr>

     <tr>

     <td>Mount point</td>

         <td>NTRIP mount point</td>

     </tr>

     <tr>

     <td>Data format</td>

         <td>Specifies the used version of NTRIP </td>

     </tr>

     <tr>

       <td>Username</td>

       <td>User name for NTRIP authentication</td>

     </tr>

     <tr>

       <td>Password</td>

       <td>Password for NTRIP authentication</td>

     </tr>

     <tr>

     <td>Default NMEA string</td>

         <td>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) </td>

     </tr>

     <tr>

     <td>Use device GPS</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>