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

Device Properties

Using device properties you can configure GXDLMSDirector to read your meter. Meter settings are depending from manufacture and meter model. Depending from the meter and given settings, if settings are not correct meter is not answer anything or sends error. Usually if meter is not answer anything meter address is wrong. If manufacturer of the meter is not shown on Manufacturer list you can add it as described on add new manufacturer.

By default the settings given in Manufacturer Settings are used to communicate with a device. However, when adding a new Device in the system, the Device Properties dialog includes text fields and drop-down lists to change the editable settings of a device.

Device Settings


Device name describes meter.


Manufacturer of the meter. This must be correct or usually meter is not answer anything.

Start protocol

If meter is read using optical probe (head) IEC 62056-21 is usually selected. Otherwise DLMS is selected.

Logical Name Referencing

Is meter using Logical Name Referencing or Short Name Referencing. Most of the meters are using Logical Name Referencing.


Used authentication level. Supported authentication levels depend from the used meter. Authentication levels describes how user can access the meter. Using Authentication level None only read operations are allowed. List of available objects might vary from used Authentication level.

Client Address

Used client address in hex format. Usually different authentication levels have different client address. Default is 16 (0x10).


Used password. Note! Password might be different for each authentication level.

Wait time

How long reply is wait from the meter. Value is given as a seconds.

Resend count

How many times data is try to resend to the meter.

Address type

Used Meter address. Meter address is divided for Physical and Logical part. Also serial number of the meter cab be used as meter address.

Interface type

Interface type depends from the used communication channel.

Logical Server

Logical Server address in hex format.

Physical Server

Physical Server address in hex format.


Used media type. Supported media types are Serial port, TCP/IP, UDP, Terminal and own custom medias.

Verbose Mode

If verbose mode is used media as rend more information from received bytes, etc. This can be used to solve communication problems.

Media specific settings

Device Properties dialog asks for media specific settings, according to the selected connection media.


  • Enter the Host name (IP Address of the physical device).
  • Enter the number of the Port to use.
  • Check the check box if using Serial port through ethernet.


  • Select the Serial Port to use.
  • To set more accurate settings (BitRate, DataBits, Parity, StopBits, ParityCheck, and Flow Control), click the Advanced... button.


  • Enter the Phone Number.
  • Select the Serial Port to use.
  • To set more accurate settings (BitRate, DataBits, Parity, StopBits, and Flow Control), click the Advanced... button.


Max payload size in transmit

Maximum payload size in transmit.

Max payload size in receive

Maximum payload size in receive.

Window size in transmit

Window size in transmit.

Window size in receive

Window size in receive.

Server address size

Some meters can handle only specific HDLC address size. Usually this is not needed.

Inactivity timeout

Meter will close connection if keep alive message is not send during this time.


Used priority.

Service Class

Service class.

Use UTC time zone, not standard

DLMS standard defines that time zone is from normal time to UTC time. UTC time is used in some country standards like Italian UNI/TS 11291-11-2 and Saudi Electricity Company DLMS standard. Set this value to True, if you want to use UTC time.
Read more from Clock object.

Ignore Time Zone

Some meters can't handle time zones and writing time zone is causing an exception. When Ignore Time Zone is selected time zone is not send as part of the date time.

Ignore Time Status

Some meters can't handle time status (usually DST) and writing time zone is causing an exception. When Ignore Time Status is selected time status is not send as part of the date time.

Max PDU size

Client can propose maximum PDU size that server uses.

User ID

User ID is used when connection established.


Select country specific standard if meter uses it.

Use Protected Release

Protected release can be used with ciphered connection to make sure that real client is closing the connection. This is security feature.

Security change check

Security level can't change during the communication if Security change check is selected. This is normal behavior and it will increase the security, but there are some meters that are changing the security level during the communication.

Challenge Size

DLMS standard defines challenge size from 8 bytes to 64 bytes, but some meters can accept only exact size of challenges. The default challenge size is 16 bytes.

Send Public Key certificate in initialize

Its possible that client sends Public Key certificate in AARQ when connection is made and it's not needed to import to the meter. All the meters doesn't support this.

Supported services

Supported services defines what kind of services client wants to use. Read more from Conformance settings.

Secured connection settings

Secured connection settings are used when data between client and meter is encrypted.


Security level that client wants to use.

System title

Client system title. Size of system title is 8 bytes,

Block Cipher Key

Block Cipher Key is used to encrypt every data block. Size of block cipher key is 16 bytes,

Authentication Key

Authentication Key is used to sign every data block. Size of authentication key is 16 bytes,

Dedicated Key

Dedicated Key is used to encrypt every data block. Size of dedicated key is 16 bytes. This can be empty if dedicated key is not used.


Invocation Counter is increased for each message. This is initial value. Usually value is read fro the meter before secured connection is established. In that case Logical Name of "Frame Counter" is set. It might depend from the authentication level, etc. Example


Custom challenge can be used for developing purposes.

Pre-established Application Associations

When Pre-established Application Associations are used client can read data without establish the connection to the meter (AARQ and AARE is messages are not sent). This makes reading faster.