8,408
edits
Changes
Template:Networking rutos manual dlms rut2 rut9 (view source)
Revision as of 10:47, 9 April 2024
, 9 AprilCreated page with "{{Template: Networking_device_manual_fw_disclosure | series = {{{series}}} | name = {{{name}}} | fw_version ={{Template: Networking_device_manual_latest_fw | series = {{{se..."
{{Template: Networking_device_manual_fw_disclosure
| series = {{{series}}}
| name = {{{name}}}
| fw_version ={{Template: Networking_device_manual_latest_fw
| series = {{{series}}}
| name = {{{name}}}
}}
}}
==Summary==
The <b>DLMS / COSEM</b> standard suite (IEC 62056 / EN 13757- 1) is the most widely accepted international utility meter data exchange standard. DLMS is the application layer protocol that transforms the data into messages and COSEM describes the general object model and can be used for all kinds of presentations.
----
This manual page provides an overview of the DLMS functionality in {{{name}}} devices.
<b>Note:</b> DLMS is additional software that can be installed from the <b>System → [[{{{name}}} Package Manager|Package Manager]]</b> page.
==Main==
The <b>Main</b> page is used to configure DLMS physical devices and Cosem Groups.
===DLMS Physical devices===
----
Interoperable devices in DLMS categorize as server (physical device) and client. Data collection device act as a client that supports system
dependent features, parameters, functions and classes requesting data from the server (physical device). In this structure, communication protocol stack is independent of application layer so both devices may communicate different media. To add a new physical device, enter an new configuration name and click the 'Add' button.
[[File:Networking_rutos_manual_dlms_dlms_physical_devices_add_button_v2.png|border|class=tlt-border]]
After clicking 'Add' you will be redirected to the newly added physical device's configuration page.
====DLMS Physical device configuration====
----
The <b>DLMS Physical device configuration</b> section is used to configure the parameters of server (physical device).
[[File:Networking_rutos_manual_dlms_dlms_physical_devices_configuration_v2.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>off {{!}} on; default: <b>off</b></td>
<td>Enables specific physical device configuration.</td>
</tr>
<tr>
<td>Connection</td>
<td>empty ; default: <b>none</b></td>
<td>DLMS connection.</td>
</tr>
<tr>
<td>Name</td>
<td>string; default: <b>previously added device name</b></td>
<td>Physical device name.</td>
</tr>
<tr>
<td>Server address</td>
<td>integer [0..255]; default: <b>1</b></td>
<td>DLMS device server address.</td>
</tr>
<tr>
<td>Logic server address</td>
<td>integer [0..255]; default: <b>0</b></td>
<td>DLMS device logical server address.</td>
</tr>
<tr>
<td>Client address</td>
<td>integer [0..255]; default: <b>16</b></td>
<td>DLMS device client address.</td>
</tr>
<tr>
<td>Access security</td>
<td>none {{!}} <span style="color:red">Low</span> {{!}} <span style="color:red">High</span> {{!}} <span style="color:red">High MD5</span> {{!}} <span style="color:red">High SHA1</span> {{!}} <span style="color:blue">High GMAC</span>; default: <b>none</b></td>
<td>DLMS device authentication type.</td>
</tr>
<tr>
<td><span style="color:red">Password</span></td>
<td>string; default: <b>none</b></td>
<td>DLMS device password if authentication is used.</td>
</tr>
<tr>
<td>Interface type</td>
<td>HDLC {{!}} WRAPPER; default: <b>HDLC</b></td>
<td>DLMS device interface type.</td>
</tr>
<tr>
<td>Transport security</td>
<td>none {{!}} <span style="color:brown">Authentication</span> {{!}} <span style="color:green">Encryption</span> {{!}} <span style="color:green">Authentication encryption</span>; default: <b>none</b></td>
<td>DLMS device message encryption.</td>
</tr>
<tr>
<td><span style="color:brown">Invocation counter OBIS code</span></td>
<td>string; default: <b>none</b></td>
<td>DLMS device invocation counter OBIS code.</td>
</tr>
<tr>
<td><span style="color:blue">Authentication key</span></td>
<td>string (Length of the value must be 32); default: <b>none</b></td>
<td>DLMS device authentication key.</td>
</tr>
<tr>
<td><span style="color:blue">Block cipher key</span></td>
<td>string (Length of the value must be 32); default: <b>none</b></td>
<td>DLMS device block cipher key.</td>
</tr>
<tr>
<td><span style="color:green">Dedicated key</span></td>
<td>string (Length of the value must be 32); default: <b>none</b></td>
<td>DLMS device dedicated key.</td>
</tr>
<tr>
<td>Logical name referencing</td>
<td>on | off; default: <b>on</b></td>
<td>DLMS devices use Logical Names to reference and access specific data objects or attributes during communication. For example, when requesting data from a device, you might reference a specific Logical Name to retrieve the information.</td>
</tr>
<tr>
<td>Test</td>
<td>-(interactive button)</td>
<td>Test device configuration.</td>
</tr>
</table>
===DLMS Cosem groups===
----
To add a new cosem group, enter an new configuration name and click the 'Add' button.
[[File:Networking_rutos_manual_dlms_dlms_cosem_groups_add_button.png|border|class=tlt-border]]
After clicking 'Add' you will be redirected to the newly added cosem group's configuration page.
====DLMS Cosem group configuration====
----
The <b>DLMS Cosem group configuration</b> section is used to configure the parameters of cosem groups.
[[File:Networking_rutos_manual_dlms_dlms_cosem_groups_configuration v2.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>off {{!}} on; default: <b>off</b></td>
<td>Enables Cosem group.</td>
</tr>
<tr>
<td>Name</td>
<td>string; default: <b>previously added cosem group name</b></td>
<td>OBIS code group name.</td>
</tr>
<tr>
<td>Interval</td>
<td>integer [1..4294967295]; default: <b>1</b></td>
<td>Interval for OBIS code reading (in seconds).</td>
</tr>
<tr>
<td>Test</td>
<td>-(interactive button)</td>
<td>Test cosem group.</td>
</tr>
</table>
====DLMS Cosem value====
----
<b>Cosem value</b> is a specific value retrieved from a defined server (physical device). To add a new cosem value, enter an new configuration name and click the 'Add' button.
[[File:Networking_rutos_manual_dlms_dlms_cosem_value_add_button_v2.png|border|class=tlt-border]]
After clicking 'Add' you will be redirected to the newly added cosem value's configuration page.
[[File:Networking_rutos_manual_dlms_dlms_cosem_value_configuration.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>off {{!}} on; default: <b>off</b></td>
<td>Enables Cosem state.</td>
</tr>
<tr>
<td>Name</td>
<td>string; default: <b>previously added cosem value name</b></td>
<td>COSEM option name.</td>
</tr>
<tr>
<td>Physical device</td>
<td>selection; default: <b>none</b></td>
<td>Physical device to read from.</td>
</tr>
<tr>
<td>OBIS code</td>
<td>string; default: <b>none</b></td>
<td>OBIS code value, actions are not executed, only properties are read.</td>
</tr>
<tr>
<td>COSEM class id</td>
<td>DATA (ID: 1) {{!}} REGISTER (ID: 3) {{!}} REGISTER (ID: 3) {{!}} DEMAND REGISTER (ID: 5) {{!}} REGISTER ACTIVATION (ID: 6) {{!}} <span style="color:red">PROFILE GENERIC (ID: 7)</span> {{!}} CLOCK (ID: 8) {{!}} SCRIPT TABLE (ID: 9); default: <b>DATA (ID: 1)</b></td>
<td>Object type for OBIS code.</td>
</tr>
<tr>
<td><span style="color:red">Entries</span></td>
<td>interger [1..32767]; default: <b>none</b></td>
<td>How many data objects to read.</td>
</tr>
</table>
==Connections==
The <b>Connections</b> page is used to configure DLMS connections. You can use either TCP or serial (depending on the router) connection to establish a connection between the physical device and the router.
===DLMS Connections===
----
To add a new connection, enter an new connection name and click the 'Add' button.
[[File:Networking_rutos_manual_dlms_dlms_connections_add_button.png|border|class=tlt-border]]
After clicking 'Add' you will be redirected to the newly added connection's configuration page.
====DLMS Connection configuration====
----
The <b>DLMS Connection configuration</b> section is used to configure the parameters of connections.
[[File:Networking_rutos_manual_dlms_dlms_connections_configuration.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>off {{!}} on; default: <b>off</b></td>
<td>Enables Cosem state.</td>
</tr>
<tr>
<td>Name</td>
<td>string; default: <b>previously added connection name</b></td>
<td>Name of DLMS connection configuration.</td>
</tr>
<tr>
<td>Connection type</td>
<td>TCP {{#ifeq: {{{serial}}} | 1 | {{!}} <span style="color:red">Serial</span> |}}; default: <b>TCP</b></td>
<td>DLMS connection type.</td>
</tr>{{#ifeq: {{{serial}}} | 1 |
<tr>
<td><span style="color:red">Serial device</span></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>
</tr>
<tr>
<td>Baud rate</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>Serial data transmission rate (in bits per second).</td>
</tr>
<tr>
<td>Data bits</td>
<td>{{#ifeq:{{#expr: {{{rs232}}} or {{{usb}}}}} |1|{{#ifeq:{{{series}}}|TRB2||5 {{!}} 6 {{!}}}} 7 {{!}} |}}8; default: <b>8</b></td>
<td>Number of data bits for each character.</td>
</tr>
<tr>
<td>Stop bits</td>
<td>1{{#ifeq:{{#expr: {{{rs232}}} or {{{usb}}}}} |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>Parity</td>
<td>Even {{!}} Odd{{#ifeq:{{#expr: {{{rs232}}} or {{{usb}}}}} |1| {{!}} Mark {{!}} Space|}} {{!}} None; 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>{{#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>
<td>Flow control</td>
<td>None {{#ifeq:{{#expr: {{{rs232}}} or {{{usb}}}}} |1| {{!}} 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.
{{#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>
<td>IP address</td>
<td>ip; default: <b>none</b></td>
<td>DLMS device IP address for TCP connection.</td>
</tr>
<tr>
<td>Port</td>
<td>integer [1..65535]; default: <b>none</b></td>
<td>DLMS device IP port for TCP connection.</td>
</tr>
</table>
[[Category:{{{name}}} Services section]]
| series = {{{series}}}
| name = {{{name}}}
| fw_version ={{Template: Networking_device_manual_latest_fw
| series = {{{series}}}
| name = {{{name}}}
}}
}}
==Summary==
The <b>DLMS / COSEM</b> standard suite (IEC 62056 / EN 13757- 1) is the most widely accepted international utility meter data exchange standard. DLMS is the application layer protocol that transforms the data into messages and COSEM describes the general object model and can be used for all kinds of presentations.
----
This manual page provides an overview of the DLMS functionality in {{{name}}} devices.
<b>Note:</b> DLMS is additional software that can be installed from the <b>System → [[{{{name}}} Package Manager|Package Manager]]</b> page.
==Main==
The <b>Main</b> page is used to configure DLMS physical devices and Cosem Groups.
===DLMS Physical devices===
----
Interoperable devices in DLMS categorize as server (physical device) and client. Data collection device act as a client that supports system
dependent features, parameters, functions and classes requesting data from the server (physical device). In this structure, communication protocol stack is independent of application layer so both devices may communicate different media. To add a new physical device, enter an new configuration name and click the 'Add' button.
[[File:Networking_rutos_manual_dlms_dlms_physical_devices_add_button_v2.png|border|class=tlt-border]]
After clicking 'Add' you will be redirected to the newly added physical device's configuration page.
====DLMS Physical device configuration====
----
The <b>DLMS Physical device configuration</b> section is used to configure the parameters of server (physical device).
[[File:Networking_rutos_manual_dlms_dlms_physical_devices_configuration_v2.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>off {{!}} on; default: <b>off</b></td>
<td>Enables specific physical device configuration.</td>
</tr>
<tr>
<td>Connection</td>
<td>empty ; default: <b>none</b></td>
<td>DLMS connection.</td>
</tr>
<tr>
<td>Name</td>
<td>string; default: <b>previously added device name</b></td>
<td>Physical device name.</td>
</tr>
<tr>
<td>Server address</td>
<td>integer [0..255]; default: <b>1</b></td>
<td>DLMS device server address.</td>
</tr>
<tr>
<td>Logic server address</td>
<td>integer [0..255]; default: <b>0</b></td>
<td>DLMS device logical server address.</td>
</tr>
<tr>
<td>Client address</td>
<td>integer [0..255]; default: <b>16</b></td>
<td>DLMS device client address.</td>
</tr>
<tr>
<td>Access security</td>
<td>none {{!}} <span style="color:red">Low</span> {{!}} <span style="color:red">High</span> {{!}} <span style="color:red">High MD5</span> {{!}} <span style="color:red">High SHA1</span> {{!}} <span style="color:blue">High GMAC</span>; default: <b>none</b></td>
<td>DLMS device authentication type.</td>
</tr>
<tr>
<td><span style="color:red">Password</span></td>
<td>string; default: <b>none</b></td>
<td>DLMS device password if authentication is used.</td>
</tr>
<tr>
<td>Interface type</td>
<td>HDLC {{!}} WRAPPER; default: <b>HDLC</b></td>
<td>DLMS device interface type.</td>
</tr>
<tr>
<td>Transport security</td>
<td>none {{!}} <span style="color:brown">Authentication</span> {{!}} <span style="color:green">Encryption</span> {{!}} <span style="color:green">Authentication encryption</span>; default: <b>none</b></td>
<td>DLMS device message encryption.</td>
</tr>
<tr>
<td><span style="color:brown">Invocation counter OBIS code</span></td>
<td>string; default: <b>none</b></td>
<td>DLMS device invocation counter OBIS code.</td>
</tr>
<tr>
<td><span style="color:blue">Authentication key</span></td>
<td>string (Length of the value must be 32); default: <b>none</b></td>
<td>DLMS device authentication key.</td>
</tr>
<tr>
<td><span style="color:blue">Block cipher key</span></td>
<td>string (Length of the value must be 32); default: <b>none</b></td>
<td>DLMS device block cipher key.</td>
</tr>
<tr>
<td><span style="color:green">Dedicated key</span></td>
<td>string (Length of the value must be 32); default: <b>none</b></td>
<td>DLMS device dedicated key.</td>
</tr>
<tr>
<td>Logical name referencing</td>
<td>on | off; default: <b>on</b></td>
<td>DLMS devices use Logical Names to reference and access specific data objects or attributes during communication. For example, when requesting data from a device, you might reference a specific Logical Name to retrieve the information.</td>
</tr>
<tr>
<td>Test</td>
<td>-(interactive button)</td>
<td>Test device configuration.</td>
</tr>
</table>
===DLMS Cosem groups===
----
To add a new cosem group, enter an new configuration name and click the 'Add' button.
[[File:Networking_rutos_manual_dlms_dlms_cosem_groups_add_button.png|border|class=tlt-border]]
After clicking 'Add' you will be redirected to the newly added cosem group's configuration page.
====DLMS Cosem group configuration====
----
The <b>DLMS Cosem group configuration</b> section is used to configure the parameters of cosem groups.
[[File:Networking_rutos_manual_dlms_dlms_cosem_groups_configuration v2.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>off {{!}} on; default: <b>off</b></td>
<td>Enables Cosem group.</td>
</tr>
<tr>
<td>Name</td>
<td>string; default: <b>previously added cosem group name</b></td>
<td>OBIS code group name.</td>
</tr>
<tr>
<td>Interval</td>
<td>integer [1..4294967295]; default: <b>1</b></td>
<td>Interval for OBIS code reading (in seconds).</td>
</tr>
<tr>
<td>Test</td>
<td>-(interactive button)</td>
<td>Test cosem group.</td>
</tr>
</table>
====DLMS Cosem value====
----
<b>Cosem value</b> is a specific value retrieved from a defined server (physical device). To add a new cosem value, enter an new configuration name and click the 'Add' button.
[[File:Networking_rutos_manual_dlms_dlms_cosem_value_add_button_v2.png|border|class=tlt-border]]
After clicking 'Add' you will be redirected to the newly added cosem value's configuration page.
[[File:Networking_rutos_manual_dlms_dlms_cosem_value_configuration.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>off {{!}} on; default: <b>off</b></td>
<td>Enables Cosem state.</td>
</tr>
<tr>
<td>Name</td>
<td>string; default: <b>previously added cosem value name</b></td>
<td>COSEM option name.</td>
</tr>
<tr>
<td>Physical device</td>
<td>selection; default: <b>none</b></td>
<td>Physical device to read from.</td>
</tr>
<tr>
<td>OBIS code</td>
<td>string; default: <b>none</b></td>
<td>OBIS code value, actions are not executed, only properties are read.</td>
</tr>
<tr>
<td>COSEM class id</td>
<td>DATA (ID: 1) {{!}} REGISTER (ID: 3) {{!}} REGISTER (ID: 3) {{!}} DEMAND REGISTER (ID: 5) {{!}} REGISTER ACTIVATION (ID: 6) {{!}} <span style="color:red">PROFILE GENERIC (ID: 7)</span> {{!}} CLOCK (ID: 8) {{!}} SCRIPT TABLE (ID: 9); default: <b>DATA (ID: 1)</b></td>
<td>Object type for OBIS code.</td>
</tr>
<tr>
<td><span style="color:red">Entries</span></td>
<td>interger [1..32767]; default: <b>none</b></td>
<td>How many data objects to read.</td>
</tr>
</table>
==Connections==
The <b>Connections</b> page is used to configure DLMS connections. You can use either TCP or serial (depending on the router) connection to establish a connection between the physical device and the router.
===DLMS Connections===
----
To add a new connection, enter an new connection name and click the 'Add' button.
[[File:Networking_rutos_manual_dlms_dlms_connections_add_button.png|border|class=tlt-border]]
After clicking 'Add' you will be redirected to the newly added connection's configuration page.
====DLMS Connection configuration====
----
The <b>DLMS Connection configuration</b> section is used to configure the parameters of connections.
[[File:Networking_rutos_manual_dlms_dlms_connections_configuration.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>off {{!}} on; default: <b>off</b></td>
<td>Enables Cosem state.</td>
</tr>
<tr>
<td>Name</td>
<td>string; default: <b>previously added connection name</b></td>
<td>Name of DLMS connection configuration.</td>
</tr>
<tr>
<td>Connection type</td>
<td>TCP {{#ifeq: {{{serial}}} | 1 | {{!}} <span style="color:red">Serial</span> |}}; default: <b>TCP</b></td>
<td>DLMS connection type.</td>
</tr>{{#ifeq: {{{serial}}} | 1 |
<tr>
<td><span style="color:red">Serial device</span></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>
</tr>
<tr>
<td>Baud rate</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>Serial data transmission rate (in bits per second).</td>
</tr>
<tr>
<td>Data bits</td>
<td>{{#ifeq:{{#expr: {{{rs232}}} or {{{usb}}}}} |1|{{#ifeq:{{{series}}}|TRB2||5 {{!}} 6 {{!}}}} 7 {{!}} |}}8; default: <b>8</b></td>
<td>Number of data bits for each character.</td>
</tr>
<tr>
<td>Stop bits</td>
<td>1{{#ifeq:{{#expr: {{{rs232}}} or {{{usb}}}}} |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>Parity</td>
<td>Even {{!}} Odd{{#ifeq:{{#expr: {{{rs232}}} or {{{usb}}}}} |1| {{!}} Mark {{!}} Space|}} {{!}} None; 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>{{#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>
<td>Flow control</td>
<td>None {{#ifeq:{{#expr: {{{rs232}}} or {{{usb}}}}} |1| {{!}} 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.
{{#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>
<td>IP address</td>
<td>ip; default: <b>none</b></td>
<td>DLMS device IP address for TCP connection.</td>
</tr>
<tr>
<td>Port</td>
<td>integer [1..65535]; default: <b>none</b></td>
<td>DLMS device IP port for TCP connection.</td>
</tr>
</table>
[[Category:{{{name}}} Services section]]
