Template:Networking rutos manual dlms: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 15: | Line 15: | ||
<b>Note:</b> DLMS is additional software that can be installed from the <b>System → [[{{{name}}} Package Manager|Package Manager]]</b> page. | <b>Note:</b> DLMS is additional software that can be installed from the <b>System → [[{{{name}}} Package Manager|Package Manager]]</b> page. | ||
<b>Note:</b> The count of DLMS connections is limited to 30, physical devices - up to 30, space groups - up to 10, cosem objects - up to 20 in each group. | |||
==Main== | ==Main== | ||
The <b>Main</b> page is used to configure DLMS physical devices and Cosem Groups. | The <b>Main</b> page is used to configure DLMS physical devices and Cosem Groups. | ||
Notice the Global section config. It is used to outright turn the service off or on if any active configurations are present. | |||
[[File:Networking rutos manual dlms dlms physical devices global button v1.png|border|class=tlt-border]] | |||
Clicking the Cog icon opens a modal window. The global configuration slider can be set and it's state saved. | |||
[[File:Networking rutos manual modbus modbus tcp client modbus tcp server devices global config modal v1.png|border|class=tlt-border]] | |||
===DLMS Physical devices=== | ===DLMS Physical devices=== | ||
---- | ---- | ||
Interoperable devices in DLMS categorize as server (physical device) and client. Data collection device act as a client that supports system | 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, | 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, click the 'Add' button. | ||
[[File: | [[File:Networking_rutos_manual_dlms_dlms_physical_devices_add_button_v3.png|border|class=tlt-border]] | ||
After clicking 'Add' you will be redirected to the newly added physical device's configuration page. | After clicking 'Add' you will be redirected to the newly added physical device's configuration page. | ||
| Line 32: | Line 41: | ||
The <b>DLMS Physical device configuration</b> section is used to configure the parameters of server (physical device). | The <b>DLMS Physical device configuration</b> section is used to configure the parameters of server (physical device). | ||
[[File: | [[File:Networking_rutos_manual_dlms_dlms_physical_devices_configuration_v3.png|border|class=tlt-border]] | ||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
| Line 52: | Line 61: | ||
<tr> | <tr> | ||
<td>Name</td> | <td>Name</td> | ||
<td>string; default: <b> | <td>string; default: <b>none</b></td> | ||
<td>Physical device name.</td> | <td>Physical device name.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Server address</td> | <td>Server address type</td> | ||
<td><span style="color:maroon">Default</span> {{!}} <span style="color:olive">Serial number</span>; default: <b>Default</b></td> | |||
<td>Select 'Default' for server address or 'Serial Number' for addressing by a specific serial number.</td> | |||
</tr> | |||
<tr> | |||
<td><span style="color:maroon">Server address</span></td> | |||
<td>integer [0..255]; default: <b>1</b></td> | <td>integer [0..255]; default: <b>1</b></td> | ||
<td>DLMS device server address.</td> | <td>DLMS device server address.</td> | ||
</tr> | |||
<tr> | |||
<td><span style="color:olive">Serial number</span></td> | |||
<td>unsigned integer; default: <b>1</b></td> | |||
<td>DLMS device serial number. Uses formula 'SN % 10000 + 1000'.</td> | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
| Line 91: | Line 110: | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td><span style="color:brown">Invocation counter OBIS code</span></td> | <td>Authentication/Encryption/Authentication encryption: <span style="color:brown">Invocation counter OBIS code</span></td> | ||
<td>string; default: <b>none</b></td> | <td>string; default: <b>none</b></td> | ||
<td>DLMS device invocation counter OBIS code.</td> | <td>DLMS device invocation counter OBIS code.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td><span style="color:blue">Authentication key</span></td> | <td>Authentication/Authentication encryption: <span style="color:blue">Authentication key</span></td> | ||
<td>string (Length of the value must be 32); default: <b>none</b></td> | <td>string (Length of the value must be 32); default: <b>none</b></td> | ||
<td>DLMS device authentication key.</td> | <td>DLMS device authentication key.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td><span style="color:blue">Block cipher key</span></td> | <td>Encryption/Authentication encryption: <span style="color:blue">Block cipher key</span></td> | ||
<td>string (Length of the value must be 32); default: <b>none</b></td> | <td>string (Length of the value must be 32); default: <b>none</b></td> | ||
<td>DLMS device block cipher key.</td> | <td>DLMS device block cipher key.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td><span style="color:green">Dedicated key</span></td> | <td>Encryption/Authentication encryption: <span style="color:green">Dedicated key</span></td> | ||
<td>string (Length of the value must be 32); default: <b>none</b></td> | <td>string (Length of the value must be 32); default: <b>none</b></td> | ||
<td>DLMS device dedicated key.</td> | <td>DLMS device dedicated key.</td> | ||
| Line 112: | Line 131: | ||
<tr> | <tr> | ||
<td>Logical name referencing</td> | <td>Logical name referencing</td> | ||
<td>on | <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> | <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> | ||
| Line 124: | Line 143: | ||
===DLMS Cosem groups=== | ===DLMS Cosem groups=== | ||
---- | ---- | ||
To add a new cosem group, | To add a new cosem group, click the 'Add' button. | ||
[[File: | [[File:Networking_rutos_manual_dlms_dlms_cosem_groups_add_button_v1.png|border|class=tlt-border]] | ||
After clicking 'Add' you will be redirected to the newly added cosem group's configuration page. | After clicking 'Add' you will be redirected to the newly added cosem group's configuration page. | ||
| Line 149: | Line 168: | ||
<tr> | <tr> | ||
<td>Name</td> | <td>Name</td> | ||
<td>string; default: <b> | <td>string; default: <b>none</b></td> | ||
<td>OBIS code group name.</td> | <td>OBIS code group name.</td> | ||
</tr> | </tr> | ||
| Line 166: | Line 185: | ||
====DLMS Cosem value==== | ====DLMS Cosem value==== | ||
---- | ---- | ||
<b>Cosem value</b> is a specific value retrieved from a defined server (physical device). To add a new cosem value, | <b>Cosem value</b> is a specific value retrieved from a defined server (physical device). To add a new cosem value, click the 'Add' button. | ||
[[File: | [[File:Networking_rutos_manual_dlms_dlms_cosem_value_add_button_v3.png|border|class=tlt-border]] | ||
After clicking 'Add' you will be redirected to the newly added cosem value's configuration page. | After clicking 'Add' you will be redirected to the newly added cosem value's configuration page. | ||
[[File: | [[File:Networking_rutos_manual_dlms_dlms_cosem_value_configuration_v1.png|border|class=tlt-border]] | ||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
| Line 187: | Line 206: | ||
<tr> | <tr> | ||
<td>Name</td> | <td>Name</td> | ||
<td>string; default: <b> | <td>string; default: <b>none</b></td> | ||
<td>COSEM option name.</td> | <td>COSEM option name.</td> | ||
</tr> | </tr> | ||
| Line 202: | Line 221: | ||
<tr> | <tr> | ||
<td>COSEM class id</td> | <td>COSEM class id</td> | ||
<td>DATA (ID: 1) {{!}} REGISTER (ID: 3) {{!}} REGISTER (ID: | <td>DATA (ID: 1) {{!}} REGISTER (ID: 3) {{!}} EXTENDED REGISTER (ID: 4) {{!}} DEMAND REGISTER (ID: 5) {{!}} REGISTER ACTIVATION (ID: 6) {{!}} <span style="color:red">PROFILE GENERIC (ID: 7)</span> {{!}} CLOCK (ID: 8) {{!}} SCRIPT TABLE (ID: 9) {{!}} SPECIAL DAYS TABLE (ID: 11) {{!}} ASSOCIATION LOGICAL NAME (ID: 15) {{!}} SAP ASSIGNMENT (ID: 17) {{!}} IMAGE TRANSFER (ID: 18) {{!}} IEC LOCAL PORT SETUP (ID: 19) {{!}} ACTIVITY CALENDAR (ID: 20) {{!}} REGISTER MONITOR (ID: 21) {{!}} ACTION SCHEDULE (ID: 22) {{!}} IEC HDLC SETUP (ID: 23) {{!}} IEC TWISTED PAIR SETUP (ID: 24) {{!}} UTILITY TABLES (ID: 26) {{!}} MODEM CONFIGURATION (ID: 27) {{!}} AUTO ANSWER (ID: 28) {{!}} AUTO CONNECT (ID: 29) {{!}} PUSH SETUP (ID: 40) {{!}} TCP UDP SETUP (ID: 41) {{!}} IP4 SETUP (ID: 42) {{!}} MAC ADDRESS SETUP (ID: 43) {{!}} GPRS SETUP (ID: 45) {{!}} GSM DIAGNOSTIC (ID: 47) {{!}} IP6 SETUP (ID: 48) {{!}} COMPACT DATA (ID: 62) {{!}} SECURITY SETUP (ID: 64) {{!}} ARBITRATOR (ID: 68) {{!}} DISCONNECT CONTROL (ID: 70) {{!}} LIMITER (ID: 71); default: <b>DATA (ID: 1)</b></td> | ||
<td>Object type for OBIS code.</td> | <td>Object type for OBIS code.</td> | ||
</tr> | </tr> | ||
| Line 217: | Line 236: | ||
===DLMS Connections=== | ===DLMS Connections=== | ||
---- | ---- | ||
To add a new connection, | To add a new connection, click the 'Add' button. | ||
[[File: | [[File:Networking_rutos_manual_dlms_dlms_connections_add_button_v1.png|border|class=tlt-border]] | ||
After clicking 'Add' you will be redirected to the newly added connection's configuration page. | After clicking 'Add' you will be redirected to the newly added connection's configuration page. | ||