Changes

DLMS client configuration example (view source)

Revision as of 15:57, 10 November 2023

28 bytes added , 15:57, 10 November 2023

no edit summary

Line 29: Line 29:

** 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 operating manual;

−

The final configuration could look like so:

+

The final configuration could look like so:

[[File:DLMS_client_configuration_example_serial_connection_v1.png|border|class=tlt-border|900x900px]]

===Physical device configuration===

----

−

Once we have configured the basic connection parameters, we can move onto configuring the DLMS physical devices. Back in the Main tab, we can create a new DLMS physical device interface with a recognizable name. Once the instance is created, and the configuration window opens up, there are a few parameters we need to specify:

+

Once we have configured the basic connection parameters, we can move onto configuring the DLMS physical devices. Back in the Main tab, we can create a new DLMS physical device interface with a recognizable name. Once the instance is created, and the configuration window opens up, there are a few parameters we need to specify:

[[File:DLMS_client_configuration_example_physical_device_window_v1.png|border|class=tlt-border|700x700px]]

* Select the '''connection instance''' created earlier;

Line 55: Line 55:

===Testing physical device reachability===

----

−

Finally, once we have configured the physical DLMS device, we can test if our configuration up until this point was correct by enabling the DLMS Client package, the created physical device instance, saving the settings, and pressing the TEST button:

+

Finally, once we have configured the physical DLMS device, we can test if our configuration up until this point was correct by enabling the DLMS Client package, the created physical device instance, saving the settings, and pressing the TEST button:

[[File:DLMS_client_configuration_example_physical_device_v1.png|border|class=tlt-border|800x800px]]

If you're receiving an error, open physical device instance, and press the TEST button at the bottom. It will provide a more specific error message:

Line 63: Line 63:

Now that the physical devices are configured and working, let's move onto COSEM group configuration. COSEM groups are a convenient way to organize the OBIS codes that you want to send to the remote data collection server. You can add OIDs from different physical devices to the same COSEM group.

−

The first thing to do is to choose how frequently you want to read the data from the devices. For TCP/IP devices, one second is a good interval. For serial devices, you may need to use a longer interval, depending on the baud rate. This is to avoid reading the data too fast and causing errors.

+

The first thing to do is to choose how frequently you want to read the data from the devices. For TCP/IP devices, one second is a good interval. For serial devices, you may need to use a longer interval, depending on the baud rate. This is to avoid reading the data too fast and causing errors.

[[File:DLMS_client_configuration_example_cosem_group_v1.png|border|class=tlt-border|800x800px]]

====COSEM value configuration====

Line 74: Line 74:

** 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.

−

Here is an example of a configured COSEM value:

+

Here is an example of a configured COSEM value:

[[File:DLMS_client_configuration_example_cosem_value_v1.png|border|class=tlt-border|800x800px]]

==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:

+

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:

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

−

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:

+

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:

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

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.

DaumantasG

Administrators

157

edits