Changes

no edit summary
Line 30: Line 30:  
----
 
----
 
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, enter an new configuration name and click the 'Add' button.
+
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:Networking_rutos_manual_dlms_dlms_physical_devices_add_button_v2.png|border|class=tlt-border]]
+
[[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 40: Line 40:  
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:Networking_rutos_manual_dlms_dlms_physical_devices_configuration_v2.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_dlms_dlms_physical_devices_configuration_v3.png|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 60: Line 60:  
     <tr>
 
     <tr>
 
         <td>Name</td>
 
         <td>Name</td>
         <td>string; default: <b>previously added device name</b></td>
+
         <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:lime">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:lime">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 99: Line 109:  
     </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 120: Line 130:  
     <tr>
 
     <tr>
 
         <td>Logical name referencing</td>
 
         <td>Logical name referencing</td>
         <td>on | off; default: <b>on</b></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>
 
         <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>

Navigation menu