Changes

DLMS client configuration example (view source)

Revision as of 15:45, 17 November 2023

8 bytes removed ,  15:45, 17 November 2023
no edit summary
Line 3: Line 3:  
DLMS (''Device Language Message Specification'') is a set of standards used for communication between various meters, monitoring equipment, and the respective controllers. It uses '''TCP/IP or serial communication''' and utilizes '''Client and Server topology''', where the client polls the data from the server (''usually gas/electricity/water meter''). It should be noted, that there often is confusion between IEC 62056-21 and DLMS. '''IEC 62056-21 is not DLMS''' and is not currently supported by our devices.
 
DLMS (''Device Language Message Specification'') is a set of standards used for communication between various meters, monitoring equipment, and the respective controllers. It uses '''TCP/IP or serial communication''' and utilizes '''Client and Server topology''', where the client polls the data from the server (''usually gas/electricity/water meter''). It should be noted, that there often is confusion between IEC 62056-21 and DLMS. '''IEC 62056-21 is not DLMS''' and is not currently supported by our devices.
 
    
 
    
−
COSEM (''Companion Specification for Energy Metering'') is a protocol that falls under the DLMS standard. It provides application and transport layers for the protocol. COSEM defines a set of '''objects''' that represent the data and functions of the meter, and a set of '''services''' that allow the client to access the objects. COSEM also specifies the '''security''' mechanisms for authentication and encryption of the messages. It should be noted, that for now our implementation of COSEM only allows us to perform read operations on DLMS servers, with write operations not currently being supported.
+
COSEM (''Companion Specification for Energy Metering'') is a protocol that falls under the DLMS standard. It provides application and transport layers for the protocol. COSEM defines a set of '''objects''' that represent the data and functions of the meter, and a set of '''services''' that allow the client to access the objects. COSEM also specifies the '''security''' mechanisms for authentication and encryption of the messages. It should be noted, that for now our implementation of COSEM only allows us to perform read operations on DLMS meters, with write operations not currently being supported.
 
   
 
   
 
==What problems can our DLMS implementation solve?==
 
==What problems can our DLMS implementation solve?==
Line 22: Line 22:  
* When the configuration window opens up, specify:
 
* When the configuration window opens up, specify:
 
** '''Connection type''' as '''TCP''';
 
** '''Connection type''' as '''TCP''';
−
** '''IP address''' of the DLMS server. It can be assigned statically or dynamically using DHCP;
+
** '''IP address''' of the DLMS meter. It can be assigned statically or dynamically using DHCP;
 
** '''Port number''' of the DLMS access. ''Usually'', the port used for DLMS/COSEM is anywhere from 4059 to 4063. Please refer to a manual of your device to check which port is used by your device;
 
** '''Port number''' of the DLMS access. ''Usually'', the port used for DLMS/COSEM is anywhere from 4059 to 4063. Please refer to a manual of your device to check which port is used by your device;
 
After the connection parameters are entered, do not forget to '''enable the instance'''! The configuration could look similar to this:<br>
 
After the connection parameters are entered, do not forget to '''enable the instance'''! The configuration could look similar to this:<br>
Line 32: Line 32:  
** '''Connection type''' as '''Serial''';
 
** '''Connection type''' as '''Serial''';
 
** Under the '''Serial device''' field, specify whether you're using RS485 or RS232;
 
** Under the '''Serial device''' field, specify whether you're using RS485 or RS232;
−
** Specify the remaining serial parameters. They can either be configured in the DLMS server itself, or the default ones should be specified within the user manual;
+
** Specify the remaining serial parameters. They can either be configured in the DLMS meter itself, or the default ones should be specified within the user manual;
 
The final configuration could look like so:<br>
 
The final configuration could look like so:<br>
 
[[File:DLMS_client_configuration_example_serial_connection_v1.png|border|class=tlt-border|900x900px]]<br>
 
[[File:DLMS_client_configuration_example_serial_connection_v1.png|border|class=tlt-border|900x900px]]<br>
Line 49: Line 49:  
*** Client address '''17''' - '''Low''';
 
*** Client address '''17''' - '''Low''';
 
*** Client address '''18''' - '''High''';
 
*** Client address '''18''' - '''High''';
−
** The client address should be specified in the '''user manual''' of the DLMS Server. However, if you are not able to find this information, the most commonly used address is 16 with no authentication. Keep in mind, that some manufacturers may not follow the standard and use Client addresses that do not follow the scheme mentioned above.
+
** The client address should be specified in the '''user manual''' of the DLMS meter. However, if you are not able to find this information, the most commonly used address is 16 with no authentication. Keep in mind, that some manufacturers may not follow the standard and use Client addresses that do not follow the scheme mentioned above.
 
* '''Interface type'''
 
* '''Interface type'''
 
** We currently support two DLMS interface types:
 
** We currently support two DLMS interface types:
Line 55: Line 55:  
*** '''HDLC''' - can be used with both '''serial''' and '''TCP/IP connections'''. We currently support direct serial connections, as well as IEC 62056-21 protocol '''mode E''' / HDLC with mode E interfaces, which contain an optical probe on one end, and RS interface on the other.
 
*** '''HDLC''' - can be used with both '''serial''' and '''TCP/IP connections'''. We currently support direct serial connections, as well as IEC 62056-21 protocol '''mode E''' / HDLC with mode E interfaces, which contain an optical probe on one end, and RS interface on the other.
 
* '''Transport security'''
 
* '''Transport security'''
−
** Transport security, unlike access security, specifies on how the data should be encrypted when being transferred via the TCP/IP or Serial communication lines. This parameter can also be found in the user manual of the DLMS Server. It has 4 possible levels of security.
+
** Transport security, unlike access security, specifies on how the data should be encrypted when being transferred via the TCP/IP or Serial communication lines. This parameter can also be found in the user manual of the DLMS meter. It has 4 possible levels of security.
    
===Testing physical device reachability===
 
===Testing physical device reachability===
Line 71: Line 71:  
====COSEM value configuration====
 
====COSEM value configuration====
 
----
 
----
−
Each COSEM value needs to be created for every OBIS code that needs to be read from the DLMS Server. In this window we will need to specify:
+
Each COSEM value needs to be created for every OBIS code that needs to be read from the DLMS meter. In this window we will need to specify:
 
* '''Physical device''' that we will be reading the value from;
 
* '''Physical device''' that we will be reading the value from;
 
* '''OBIS code''' of the value that we would like to read;
 
* '''OBIS code''' of the value that we would like to read;
−
** OBIS codes specify the location of the data on the DLMS server, and they can be found in the user manual of your device.  
+
** OBIS codes specify the location of the data on the DLMS meter, and they can be found in the user manual of your device.  
 
** It should be in the following format: '''A.B.C.D.E.F''' (''for example, 1.0.1.4.6.255''). OBIS codes are comprised of 6 groups, and each group represents a different piece of information about the OID in question. More information about it can be found in the sources linked at the end of the article.
 
** It should be in the following format: '''A.B.C.D.E.F''' (''for example, 1.0.1.4.6.255''). OBIS codes are comprised of 6 groups, and each group represents a different piece of information about the OID in question. More information about it can be found in the sources linked at the end of the article.
 
** The same OBIS code can be read from multiple devices/logical devices at the same time;
 
** The same OBIS code can be read from multiple devices/logical devices at the same time;
−
* '''COSEM class ID''' (''also known as COSEM object'') specifies the format in which the data will be returned. The most commonly used ones are '''DATA (ID: 1)''' and '''REGISTER (ID: 3)''', however, this information should be available in the user manual of your DLMS server along with each OBIS code.<br>
+
* '''COSEM class ID''' (''also known as COSEM object'') specifies the format in which the data will be returned. The most commonly used ones are '''DATA (ID: 1)''' and '''REGISTER (ID: 3)''', however, this information should be available in the user manual of your DLMS meter along with each OBIS code.<br>
 
Here is an example of a configured COSEM value:<br>
 
Here is an example of a configured COSEM value:<br>
 
[[File:DLMS_client_configuration_example_cosem_value_v1.png|border|class=tlt-border|800x800px]]<br>
 
[[File:DLMS_client_configuration_example_cosem_value_v1.png|border|class=tlt-border|800x800px]]<br>
Retrieved from "https://wiki.teltonika-networks.com/view/Special:MobileDiff/116279"

Navigation menu