31,703
edits
Changes
no edit summary
<tr>
<tr>
<td>Enabled</td>
<td>Enabled</td>
<td>yes {{!}} no; Default: '''no'''</td>
<td>yes | no; Default: '''no'''</td>
<td>When checked, enables the RS232 service</td>
<td>When checked, enables the RS232 service</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: '''115200'''</td>
<td>Sets the data rate for serial data transmission (in bits per second)</td>
<td>Sets the 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 {{!}} 6 {{!}} 7 {{!}} 8; Default: '''8'''</td>
<td>5 | 6 | 7 | 8; Default: '''8'''</td>
<td>The number of data bits for each character</td>
<td>The 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: '''None'''</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. <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>
<tr>
<tr>
<td>Stop bits</td>
<td>Stop bits</td>
<td>1 {{!}} 2; Default: '''1'''</td>
<td>1 | 2; Default: '''1'''</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>Flow control</td>
<td>None {{!}} RTS/CTS {{!}} Xon/Xoff; Default: '''None'''</td>
<td>None | RTS/CTS | Xon/Xoff; Default: '''None'''</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>
<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>
<tr>
<tr>
<td>Echo</td>
<td>Echo</td>
<td>yes {{!}} no; Default: '''no'''</td>
<td>yes | no; Default: '''no'''</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>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>
<tr>
<tr>
<td>Enabled</td>
<td>Enabled</td>
<td>yes {{!}} no; Default: '''no'''</td>
<td>yes | no; Default: '''no'''</td>
<td>Toggles the RS485 serial port function ON or OFF</td>
<td>Toggles the RS485 serial port function 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: '''115200'''</td>
<td>The communication speed of the serial interface</td>
<td>The communication speed of the serial interface</td>
</tr>
</tr>
<tr>
<tr>
<td>Parity</td>
<td>Parity</td>
<td>None {{!}} Odd {{!}} Even; Default: '''None'''</td>
<td>None | Odd | Even; Default: '''None'''</td>
<td>The parity bit setting used for error detection during data transfer</td>
<td>The parity bit setting used for error detection during data transfer</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: '''None'''</td>
<td>Specifies how many stop bits will be used to detect the end of character</td>
<td>Specifies how many stop bits will be used to detect the end of character</td>
</tr>
</tr>
<tr>
<tr>
<td>Serial type</td>
<td>Serial type</td>
<td>Console {{!}} Over IP {{!}} Modem {{!}} Modbus Gateway {{!}} NTRIP Client; Default: '''Console'''</td>
<td>Console | Over IP | Modem | Modbus Gateway | NTRIP Client; Default: '''Console'''</td>
<td>Specifies the function of the serial interface</td>
<td>Specifies the function of the serial interface</td>
</tr>
</tr>
<tr>
<tr>
<td>Interface</td>
<td>Interface</td>
<td>LAN {{!}} WAN {{!}} VPN {{!}} L2TP {{!}} PPTP {{!}} GRE {{!}} HOTSPOT; Default: '''LAN'''</td>
<td>LAN | WAN | VPN | L2TP | PPTP | GRE | HOTSPOT; Default: '''LAN'''</td>
<td>Interface used for connection</td>
<td>Interface used for connection</td>
</tr>
</tr>
<tr>
<tr>
<td>Mode</td>
<td>Mode</td>
<td>Server {{!}} Client {{!}} Bidirect; Default: '''Server'''</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>
<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>
<tr>
<tr>
<td>No leading zeros</td>
<td>No leading zeros</td>
<td>yes {{!}} no; Default: '''no'''</td>
<td>yes | no; Default: '''no'''</td>
<td>Specifies that the first hex zeros should be skipped</td>
<td>Specifies that the first hex zeros should be skipped</td>
</tr>
</tr>
<tr>
<tr>
<td>Mode</td>
<td>Mode</td>
<td>Server {{!}} Client {{!}} Bidirect; Default: '''Server'''</td>
<td>Server | Client | Bidirect; Default: '''Server'''</td>
<td>'''Server''' - waits for incoming connection
<td>'''Server''' - waits for incoming connection
<tr>
<tr>
<td>No leading zeros</td>
<td>No leading zeros</td>
<td>yes {{!}} no; Default: '''no'''</td>
<td>yes | no; Default: '''no'''</td>
<td>Skips first hex zeros</td>
<td>Skips first hex zeros</td>
</tr>
</tr>
<tr>
<tr>
<td>Server address</td>
<td>Server address</td>
<td>host {{!}} ip; Default: '''no'''</td>
<td>host | ip; Default: '''no'''</td>
<td>Server address to which the client will connect to</td>
<td>Server address to which the client will connect to</td>
</tr>
</tr>
<tr>
<tr>
<td>Mode</td>
<td>Mode</td>
<td>Server {{!}} Client {{!}} Bidirect; Default: '''Server'''</td>
<td>Server | Client | Bidirect; Default: '''Server'''</td>
<td>'''Server''' - waits for incoming connection
<td>'''Server''' - waits for incoming connection
<tr>
<tr>
<td>No leading zeros </td>
<td>No leading zeros </td>
<td>yes {{!}} no; Default: '''no'''</td>
<td>yes | no; Default: '''no'''</td>
<td>Skips first hex zeros</td>
<td>Skips first hex zeros</td>
</tr>
</tr>
<tr>
<tr>
<td>Server address</td>
<td>Server address</td>
<td>host {{!}} ip; Default: '''no'''</td>
<td>host | ip; Default: '''no'''</td>
<td>Server address to which the client will connect to</td>
<td>Server address to which the client will connect to</td>
</tr>
</tr>
<tr>
<tr>
<td>Output</td>
<td>Output</td>
<td>OC Output {{!}} Relay Output; Default: '''OC Output'''</td>
<td>OC Output | Relay Output; Default: '''OC Output'''</td>
<td>Output to indicate that application switched from client (default) to server state</td>
<td>Output to indicate that application switched from client (default) to server state</td>
</tr>
</tr>
<tr>
<tr>
<td>Direct connect</td>
<td>Direct connect</td>
<td>host:port {{!}} ip:port; Default: " "</td>
<td>host:port | ip:port; Default: " "</td>
<td>Maintains a constant connection to specified host. Leave empty to use an ATD command to initiate the connection</td>
<td>Maintains a constant connection to specified host. Leave empty to use an ATD command to initiate the connection</td>
</tr>
</tr>
<tr>
<tr>
<td>No extra CR LF in response</td>
<td>No extra CR LF in response</td>
<td>yes {{!}} no; Default: '''yes'''</td>
<td>yes | no; Default: '''yes'''</td>
<td>Removes extra CR LF before and LF after response code</td>
<td>Removes extra CR LF before and LF after response code</td>
</tr>
</tr>
<tr>
<tr>
<td>Slave ID configuration type</td>
<td>Slave ID configuration type</td>
<td>User defined {{!}} Obtained from TCP; Default: '''User defined'''</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>
<td>Specifies whether slave IDs are user defined or automatically obtained from TCP</td>
</tr>
</tr>
<tr>
<tr>
<td>Slave ID {{!}} Permitted slave IDs</td>
<td>Slave ID | Permitted slave IDs</td>
<td>integer {{!}} range of integers; Default: '''1'''</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>
<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>
<tr>
<tr>
<td>Data format</td>
<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: '''NTRIP V1.0'''</td>
<td>NTRIP V2.0 TCP/IP | NTRIP V2.0 RSTP/RTP | NTRIP V1.0 | Automatic detection | NTRIP V2.0 UDP; Default: '''NTRIP V1.0'''</td>
<td>Specifies the used version of NTRIP </td>
<td>Specifies the used version of NTRIP </td>
</tr>
</tr>
<tr>
<tr>
<td>Use device GPS</td>
<td>Use device GPS</td>
<td>yes {{!}} no; Default: '''no'''</td>
<td>yes | no; Default: '''no'''</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>
</table>
</table>
[[Category:RUT955 WebUI]]
