Changes

** 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 can be found 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 server 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>

==Testing the configuration==

==Testing the configuration==

Once all of the configuration is enabled and saved, we can re-open the COSEM group we have created, and press the TEST button. If the configuration was successful, we should see the information returned in JSON format, as well as a green checkmark by the COSEM value:<br>

Once all of the configuration is enabled and saved, we can re-open the COSEM group we have created, and press the TEST button. If the configuration is correct, we should see the information returned in JSON format, as well as a green checkmark next to each COSEM value:<br>

[[File:DLMS_client_configuration_example_testing_cosem_group_v1.png|border|class=tlt-border|800x800px]]<br>

[[File:DLMS_client_configuration_example_testing_cosem_group_v1.png|border|class=tlt-border|800x800px]]<br>

If one or more COSEM values fails to read, you'll get an error within the JSON string, as well when hovering over the exclamation mark by the COSEM value in question:<br>

If the service fails to obtain one or more COSEM values, you'll get an error within the JSON string, as well as when hovering over the exclamation mark next to each COSEM value in question:<br>

[[File:DLMS_client_configuration_example_testing_cosem_group_error_v2.png|border|class=tlt-border|800x800px]]<br>

[[File:DLMS_client_configuration_example_testing_cosem_group_error_v2.png|border|class=tlt-border|800x800px]]<br>

The JSON string will then be sent to the Data to Server module, to be sent to a remote data collection server. In the Data to server module, it is possible to filter the values by the COSEM Group name.

The JSON string will then be sent to the Data to Server module, to be sent to a remote data collection server. In the Data to server module, it is possible to filter the values by the COSEM Group name.