7,851
edits
Changes
Template:Networking rutos manual dlms (view source)
Revision as of 14:31, 2 October 2023
, 14:31, 2 October 2023no edit summary
<tr>
<tr>
<td><span style="color:red">Serial device</span></td>
<td><span style="color:red">Serial device</span></td>
<td>{{#switch: {{{rs232}}}{{{rs485}}} | 1 0 = rs232 | 0 1 = rs485 | 1 1 = rs232 {{!}} rs485}} ; default: <b></b></td>
<td>{{Template: Networking rutos manual serial ports| rs232={{{rs232}}}| rs485={{{rs485}}}| usb = {{{usb}}}}}; default: <b>{{Template: Networking rutos manual default serial port| rs232={{{rs232}}}| rs485={{{rs485}}}| usb = {{{usb}}}}}</b></td>
<td>DLMS serial device.</td>
<td>DLMS serial device.</td>
</tr>
</tr>
<tr>
<tr>
<td><span style="color:red">Baud rate</span></td>
<td>Baud rate</td>
<td>string; default: <b>none</b></td>
<td>300 {{!}} 1200 {{!}} 2400 {{!}} 4800 {{!}} 9600 {{!}} 19200 {{!}} 38400 {{!}} 57600 {{!}} 115200{{#ifeq: {{{rs485}}} | 1 | {{!}} 230400 {{!}} 460800 {{!}} 921600 {{!}} 1000000 {{!}} 3000000|}}; default: <b>9600</b></td>
<td>OBIS code value, actions are not executed, only properties are read.</td>
<td>Serial data transmission rate (in bits per second).</td>
</tr>
</tr>
<tr>
<tr>
<td><span style="color:red">Data bits</span></td>
<td>Data bits</td>
<td>string; default: <b>none</b></td>
<td>{{#ifeq:{{#expr: {{{rs232}}} or {{{usb}}}}} |1|{{#ifeq:{{{series}}}|TRB2||5 {{!}} 6 {{!}}}} 7 {{!}} |}}8; default: <b>8</b></td>
<td>OBIS code value, actions are not executed, only properties are read.</td>
<td>Number of data bits for each character.</td>
</tr>
</tr>
<tr>
<tr>
<td><span style="color:red">Stop bits</span></td>
<td>Stop bits</td>
<td>string; default: <b>none</b></td>
<td>1{{#ifeq:{{#expr: {{{rs232}}} or {{{usb}}}}} |1| {{!}} 2|}}; default: <b>1</b></td>
<td>OBIS code value, actions are not executed, only properties are read.</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><span style="color:red">Parity</span></td>
<td>Parity</td>
<td>string; default: <b>none</b></td>
<td>Even {{!}} Odd{{#ifeq:{{#expr: {{{rs232}}} or {{{usb}}}}} |1| {{!}} Mark {{!}} Space|}} {{!}} None; default: <b>None</b></td>
<td>OBIS code value, actions are not executed, only properties are read.</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>{{#ifeq:{{#expr: {{{rs232}}} or {{{usb}}}}} |1|<li><b>Space</b> (<b>s</b>) - the parity bit will always be a binary 0.</li>
<li><b>Mark</b> (<b>M</b>) - the parity bit will always be a binary 1.</li>|}}
</ul>
</td>
</tr>
</tr>
<tr>
<tr>
<td><span style="color:red">Flow control</span></td>
<td>Flow control</td>
<td>string; default: <b>none</b></td>
<td>None {{#ifeq:{{#expr: {{{rs232}}} or {{{usb}}}}} |1| {{!}} RTS/CTS {{!}} Xon/Xoff|}}; default: <b>None</b></td>
<td>OBIS code value, actions are not executed, only properties are read.</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.
</tr>|}}
{{#ifeq:{{#expr: {{{rs232}}} or {{{usb}}}}} |1|<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.</li>
</ul>|}}
</td>
</tr>{{#ifeq: {{{rs485}}} | 1 |
<tr>
<td><span style="color:blue">RS485:</span> Full Duplex</td>
<td>off {{!}} on; default: <b>off</b></td>
<td>Enables RS485 full duplex.</td>
</tr>|}}}}
<tr>
<tr>
<td>IP address</td>
<td>IP address</td>
