Gurux DLMSDirector is an easy-to-use application to communicate with DLMS/COSEM smart meters.

The OBIS (Object Identification System) determines the identification of data objects in DLMS/COSEM communication. The OBIS codes are used as Logical names of data objects. The DLMS User Association defines and allocates OBIS codes, and maintains list of valid OBIS codes. All the device manufacturers, however, have not abided by the recommendations. This is why the OBIS codes are made editable, to some degree, in GXDLMSDirector.

Though it is made possible, it is not recommended to add OBIS codes manually in the GXDLMSDirector, but to get them directly from the physical device itself. This is done by adding a device in the Devices Collection, and retrieving the register objects from the physical device, as guided in GXDLMSDirector Help. Once you have retrieved the register objects from the device, you can view their OBIS codes.

The OBIS codes of devices of the supported device manufacturers are automatically available in the OBIS codes dialog.

To view the OBIS codes

  1. In the Tools menu, select OBIS codes...

  2. In the opening OBIS codes dialog, on the left, you get a list of the supported device manufacturers.

  3. In the OBIS codes dialog, select the manufacturer, whose OBIS codes to view.

  4. A list of OBIS codes of the selected manufacturer is displayed on the right.

  5. Double-click an OBIS code in the list, to open it in the OBIScode form:



           
 



In the OBIS Code Form you can edit
  • The LogicalName
  • Description of the OBIS code
  • ValueType, if available
  • ValueUIType, if available, and
  • the Interface, which the selected OBIS code belongs to.
  • you can also add / edit / remove enumerated values in the Value Editor.

To edit the OBIS codes

  1. To edit the LogicalName or Description, just replace the text in the text field.
  2. To edit ValueType, or ValueUIType
    • Click on the row to edit,
    • open the drop-down list of available options by clicking on the arrow down, in the end of the row, and
    • select the required option in the drop down list.
  3. To change the Interface, select the correct one in the drop-down list (top left in OBIS Code Form).
  4. To add / edit / remove enumerated values, see section Value Editor below.
  5. When all required properties of the OBIS code are edited, click OK to save the changes.



Value Editor

In the Value Editor, the top most drop-down list shows the items available to edit. The enumerated device values, and the corresponding UI values, are shown in the list.

In the example picture, on the right Status of the Clock register is selected.

Below the list are buttons for creating a new, editing and removing a device value / UI value pair.

This way you can easily remove the value pairs that your device does not support, from the list, or edit which UI Value is to represent which Device Value. You can also add new value pairs, if they are not all listed.

The purpose of using device values and UI values as pairs, is to make interpretation of the read data easier for the user. With value pairs, the user gets information in human language, and does not have to know, or to remember, which device language value means which.

An example of using a value pair:
Let us assume that value one means that the device is turned on. When the value, retrieved from the device, equals one, the application displays "ON", instead of "1".

 



If you have any questions, suggestions or problems concerning GXDLMSDirector,
kindly present your questions and comments at our Forum.