Skip to main content
Home
for DLMS smart meters
Open source solutions for DLMS smart metering

Main navigation

  • Home
  • Products
  • About us
  • Open Source
  • Community
  • Forum
  • Downloads
User account menu
  • Log in

Breadcrumb

  1. Home
  2. Forums
  3. Problems Reading ME383

Problems reading ME383

Forum Rules

Before commenting read Forum rules

Don't comment the topic if you have a new question.

You can create a new topic selecting correct category from Gurux Forum and then create a new topic selecting "New Topic" from the top left.

By Zappa , 4 November, 2021
Forums
DLMSDirector

Hi,
I´m trying to read meter ME383 with Iskraemeco default configuration through serial port but I´m getting "Failed to receive reply from the device in given time." message from GuruxDirector.(9600 8N1).

I tried with HDLCwithModeE and optical probe, with same result:"Failed to receive reply from the device in given time."Bitrate 300, 7E1.

So I suspect Client or Server IDs are wrong, so I tried to get this values from meter with optical probe .
I´m following IEC62056-21 and I´m trying to read first parameter value with this command sequence:

[TX] - /?72034762!<CR><LF>

[RX] - /ISK5\2ME383-1008<CR><LF>

[TX] - <ACK>001<CR><LF>

[RX] - <SOH>P0<STX>(73707997)<ETX>c
[TX] - <SOH>R10000(93)

with no reply to the last command.

I tried to reset meter configuration through Reset button and following meter manual, but I couldn´t get to reset menu.

What am I doing wrong?
Is it posible to get Client ID or Server ID from optical probe?
How could I communicate with meter?

Thank you.

Image
Profile picture for user Kurumi

Kurumi

4 years 7 months ago

Hi,

Hi,

If you are reading your meter with an optical probe the Interface must change from HDLC to HdlcWithModeE. I don't know if you have done it, but in the picture it's HDLC.

Try to establish the connection using an optical probe first. The baud rate can be anything and if it's wrong the meter doesn't reply.

You should receive a reply if you are using an optical probe. Connection is started with IEC 62056-21 mode E and the meter should reply if the baud rate is correct.

BR,
Mikko

Zappa

4 years 7 months ago

Thank you.

Thank you.
Yes, I tried. First I tried with serial and HDLC(9600 8N1).) and it didn´t work. Then with usb optical probe and HDLC with E.(300, 7E1) and didn´t work. I get "Failed to receive reply from the device in given time." message in both cases.
I´m able to connect with my optical probe and it answers to IEC62056-21 identification command.(I communicate with the probe without using GuruxDirector, I use Docklight to send commands)
The problem is that, as I suspect that I can connect through serial HDLC because of wrong Client or Server IDs, I´m using optical probe to read those addresses but I don´t know how to do it or if is it possible.
With Docklight serial debuging tool I send this command to the optical probe to read a register: [TX] - <SOH>R10000(93)
but the meter didn´t answer to this command.

So, how could I get Client and Server addresses from the meter? I suppose the problem is wrong addresses, maybe wrong password, I´m not sure.

Thank you

Profile picture for user Kurumi

Kurumi

4 years 7 months ago

Hi,

Hi,

The default serial port settings with IEC 62056-21 are 300 7E1, but this can be configured to something else for the meter. Is the meter returning anything when you are connecting with GXDLMSDirector using an optical probe? You can see this if you select "View" | "Log" and | "View Log". or press Crtl+R.
There should be something like "/?!<CR><LF>" and meter should reply like this:
"/ISK5\2ME383-1008<CR><LF>"

BR,
Mikko

Zappa

4 years 7 months ago

Thank you.

Thank you.

This is the log with HDLC with mode E and optical probe:

GXDLMSDirector 8.2.2110.0602
Log created 8:15:47
08:16:33 Initializing serial connection.
08:16:34 IEC Sending:/?!<CR><LF>
08:16:35 HDLC received: /ISK5\2ME383-1008<CR><LF>
08:16:35 BaudRate is : 9600
8:16:35 Moving to mode E.
06 32 35 32 0D 0A
8:16:38 Send SNRM request.
7E A0 08 02 23 C9 93 E4 43 7E
08:16:43 Data send failed. Try to resend 1/3
08:16:48 Data send failed. Try to resend 2/3
8:16:53 Failed to receive reply from the device in given time.
08:16:53 Disconnect request
8:16:53 Send Disconnect request.
7E A0 08 02 23 C9 53 E8 85 7E
08:16:59 Data send failed. Try to resend 1/3
08:17:04 Data send failed. Try to resend 2/3
8:17:09 Failed to receive reply from the device in given time.
System.TimeoutException: Failed to receive reply from the device in given time.
en GXDLMSDirector.GXDLMSCommunicator.ReadDLMSPacket(Byte[] data, Int32 tryCount, GXReplyData reply)
en GXDLMSDirector.GXDLMSCommunicator.ReadDataBlock(Byte[] data, String text, Int32 multiplier, Int32 tryCount, GXReplyData reply)
en GXDLMSDirector.GXDLMSCommunicator.InitializeConnection(Boolean force)
en GXDLMSDirector.GXDLMSDevice.InitializeConnection()
en GXDLMSDirector.MainForm.Connect(Object sender, GXAsyncWork work, Object[] parameters)

Zappa

4 years 7 months ago

Hello,

Hello,
I made some progress trying to read ME383 meter with optical probe following IEC62056-21 protocol, using Docklight serial tool.

This is the command sequence in Docklight:

[TX] - /?72034762!<CR><LF>
[RX] - /ISK5\2ME383-1008<CR><LF>
[TX] - <ACK>001<CR><LF>
[RX] - <SOH>P0<STX>(79772560)<ETX>o
[TX] - <SOH>R1<STX>D0000000(1)<ETX>&
[RX] - <STX>(ER11)<ETX><NAK>

I´m trying to read Parameter data Identification number one as per IEC62056-21(D0000000(1), but I´m getting ERR11 message. I can´t find the meaning of this, I suppose, error message in ME383 manual. What does it mean ERR11? How could I get the value of these registers?

Thank you.

Profile picture for user Kurumi

Kurumi

4 years 7 months ago

Hi,

Hi,

You can connect with Docklight using IEC 62056-21 (old IEC 1107), but DLMS communication fails when you connect with GXDLMSDirector and I don't know the reason for that.

I'm sorry, but I can't help you with IEC 62056-21. THere are too many variations with IEC 62056-21 and it causes that meters from different manufacturers are behaving differently.

Everything is easier if you can connect with DLMS. What is the manufacturing year of the meter? You should see it on the top of the meter.

BR,
Mikko

Zappa

4 years 7 months ago

On the top of the meter I can

On the top of the meter I can see "2018". Serial number of the device:I11D18D000471. ME383 from Iskra.

Thank you.

Profile picture for user Kurumi

Kurumi

4 years 7 months ago

Hi,

Hi,

Try to change authentication to None and Logical Meter address to zero and Physical Address to One.

BR,
Mikko

Zappa

4 years 7 months ago

Thank you.

Thank you.

I tried new configuration with no success. This is the log:

GXDLMSDirector 8.2.2110.0602
Log created 16:36:01
16:38:20 Initializing serial connection.
System.UnauthorizedAccessException: Se ha denegado el acceso al puerto 'COM5'.
en GXDLMSDirector.GXDLMSCommunicator.InitSerial()
en GXDLMSDirector.GXDLMSCommunicator.InitializeConnection(Boolean force)
en GXDLMSDirector.GXDLMSDevice.InitializeConnection()
en GXDLMSDirector.MainForm.Connect(Object sender, GXAsyncWork work, Object[] parameters)
16:38:32 Initializing serial connection.
16:38:33 IEC Sending:/?!<CR><LF>
16:38:34 HDLC received: /ISK5\2ME383-1008<CR><LF>
16:38:34 BaudRate is : 9600
16:38:34 Moving to mode E.
06 32 35 32 0D 0A
16:38:37 Send SNRM request.
7E A0 07 03 C9 93 56 26 7E
16:38:42 Data send failed. Try to resend 1/3
16:38:47 Data send failed. Try to resend 2/3
16:38:52 Failed to receive reply from the device in given time.
16:38:52 Disconnect request
16:38:52 Send Disconnect request.
7E A0 07 03 C9 53 5A E0 7E
16:38:57 Data send failed. Try to resend 1/3
16:39:02 Data send failed. Try to resend 2/3
16:39:07 Failed to receive reply from the device in given time.
System.TimeoutException: Failed to receive reply from the device in given time.
en GXDLMSDirector.GXDLMSCommunicator.ReadDLMSPacket(Byte[] data, Int32 tryCount, GXReplyData reply)
en GXDLMSDirector.GXDLMSCommunicator.ReadDataBlock(Byte[] data, String text, Int32 multiplier, Int32 tryCount, GXReplyData reply)
en GXDLMSDirector.GXDLMSCommunicator.InitializeConnection(Boolean force)
en GXDLMSDirector.GXDLMSDevice.InitializeConnection()
en GXDLMSDirector.MainForm.Connect(Object sender, GXAsyncWork work, Object[] parameters)

Image
Profile picture for user Kurumi

Kurumi

4 years 7 months ago

Hi,

Hi,

Try to change the client address from 0x64 to 0x10. If it still fails change the logical address to 1 and the physical address to 0x21.

Is this your own meter or is it an electricity company meter? If it's electricity company meter, it might be that the server address is changed or the DLMS part is disabled for the optical probe.

BR,
Mikko

Zappa

4 years 7 months ago

Hi, thank you for your reply.

Hi, thank you for your reply.

Reading is still unsuccessful with last changes.

The meter is from an electricity company. I was suspecting a change of address and I was trying to read the address with an optical probe and IEC 62056-21 with no success.

Is it posible to enable DLMS with optical probe and IEC 62056-21? with <ACK>202<CR><LF> command?

Best regards.

Profile picture for user Kurumi

Kurumi

4 years 6 months ago

Hi,

Hi,

There is now a tutorial available that shows how to find HDLC server and client addresses using brute force with GXDLMSDirector.

https://youtu.be/BeaWKmyMwuE

I hope it helps you to find the correct parameters.

BR,
Mikko

  • Create new account
  • Reset your password

Hire Us!

Latest Releases

  • Tue, 06/09/2026 - 11:16
    gurux.dlms.java 4.0.95
  • Tue, 06/09/2026 - 10:03
    Gurux.DLMS.Python 1.0.199
  • Mon, 06/08/2026 - 13:39
    gurux.dlms.cpp 9.0.2606.0801
  • Mon, 06/01/2026 - 10:15
    gurux.dlms.cpp 9.0.2606.0101
  • Thu, 05/28/2026 - 16:06
    gurux.dlms.java 4.0.94

New forum topics

  • Error reading L&G Meter
  • Pass a TCP Client to GXNet
  • Australian EDMI Mk10D (Essential Energy area)
  • Strange mix of data notificiation vs get response
  • DLMS Connection
More

Who's new

  • Tuanhgg
  • Adel
  • charnon
  • Paddles
  • Miguel Ángel
RSS feed
Privacy FAQ GXDN Issues Contact
Follow Gurux on Twitter Follow Gurux on Linkedin