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

Start protocol is used if default protocol of the meter is IEC 62056-21. If meter is supporting only DLMS (IEC 62056-53) then DLMS is selected.


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

Physical Server

Physical Server address.

Logical Server

Logical Server address.


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 frame size in transmit

Maximum frame size in transmit.

Max frame size in receive

Maximum frame size in receive.

Window size in transmit

Window size in transmit.

Window size in receive

Window size in receive.


HDLC priority.

Service Class

HDLC service class.

Use Wrapper

Is WRAPPER used when communicated using TCP/IP or UDP protocol.

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.

Max PDU size

Client can propose maximum PDU size that server uses.

User ID

User ID is used when connection established.

Server address size

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


Select country specific standard if meter uses it.

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.

Block Cipher Key

Block Cipher Key is used to encrypt every data block.

Authentication Key

Authentication Key is used to encrypt every data block..


Invocation Counter is increased for each message. This is initial value.


Custom challenge can be used for developing purposes.

Pre-established Application Associations

When Pre-established Application Associations are used AARQ and AARE is messages are not sent.