Connecting to the MT880 with CM-e-3 card.

By davidzidar_INEA , 29 August, 2023
Forums
DLMSDirector

Hello,

I am trying to connect to the power meter ISKRA MT880 (with card CM-e-3) with GXDLMSDirector (i have the lastest version, downloaded from https://github.com/gurux). I added the device to the program (device properties are visible in attachment: properties.png). When I press connect button, a new pop up window appear ("You need to read Association view to see all objects what the meter can offer. Do you want to do it now?"). After pressing yes (or no), I get new alert "GetObjects failed. Failed to receive reply from device in given time". I have also tried different Client addresses (0x01, 0x11, 0x16, 0x24, 0x36, 0x64;| 0x36 because last two digits from serial are 20 + 16 = 36), but there is no success with reading DLMS data.
After the alert pop up (GetObject failed...) the connection remains successful, but with no data. If I press "read " button, the same pop up appears.
What do you suggest?

For more info: I am running the program in visual studio environment on Windows 10. I can also access meter MT880 easily with MeterConfigurator tool (with "consereth" connection)

Kurumi

2 years 9 months ago

Hi,

Can you add the hex log from the MeterConfigurator messages? The first two messages are enough. I can check the correct settings for you from the messages.

BR,
Mikko

davidzidar_INEA

2 years 9 months ago

Hi,

Thank you for fast answer.

Here is hex log (from MC - if i read multiple actual values):

1. Request: 13:55:16.102
--------------------
Size 169 B (37,98%)
--------------------

03 00 A6 7E A8 A4 02 23 03 76 31 78 E6 E6 00 C0 ...~...#.v1x....
03 42 14 00 03 01 00 55 07 00 FF 02 00 00 03 01 .B.....U........
00 55 07 00 FF 03 00 00 03 01 00 56 07 00 FF 02 .U.........V....
00 00 03 01 00 56 07 00 FF 03 00 00 03 01 00 57 .....V.........W
07 00 FF 02 00 00 03 01 00 57 07 00 FF 03 00 00 .........W......
03 01 00 5A 07 00 FF 02 00 00 03 01 00 5A 07 00 ...Z.........Z..
FF 03 00 00 03 01 00 5B 07 00 FF 02 00 00 03 01 .......[........
00 5B 07 00 FF 03 00 00 03 01 00 7C 07 00 FF 02 .[.........|....
00 00 03 01 00 7C 07 00 FF 03 00 00 03 01 00 7D .....|.........}
07 00 FF 02 00 00 03 01 00 7D 07 00 FF 03 00 00 .........}......
03 01 00 7E 07 00 11 9E 7E ...~....~

2. Answer: 13:55:16.132
--------------------
Size 13 B (2,92%)
--------------------

03 00 0A 7E A0 08 03 02 23 91 43 31 7E ...~....#.C1~

3. Request: 13:55:16.132
--------------------
Size 68 B (15,28%)
--------------------

03 00 41 7E A0 3F 02 23 03 78 EE C9 FF 02 00 00 ..A~.?.#.x......
03 01 00 7E 07 00 FF 03 00 00 03 01 00 82 07 00 ...~............
FF 02 00 00 03 01 00 82 07 00 FF 03 00 00 03 01 ................
00 83 07 00 FF 02 00 00 03 01 00 83 07 00 FF 03 ................
00 3D 42 7E .=B~

4. Answer: 13:55:16.177
--------------------
Size 146 B (32,81%)
--------------------

03 00 8F 7E A0 8D 03 02 23 B6 FF C8 E6 E7 00 C4 ...~....#.......
03 42 14 00 12 00 00 00 02 02 0F FD 16 FF 00 12 .B..............
00 00 00 02 02 0F FD 16 FF 00 12 00 00 00 02 02 ................
0F FD 16 FF 00 06 00 00 00 01 00 02 02 0F FD 16 ................
21 00 06 00 00 00 05 00 02 02 0F FD 16 21 00 06 !............!..
00 00 00 4E 00 02 02 0F FD 16 23 00 06 00 00 00 ...N......#.....
34 00 02 02 0F FD 16 23 00 06 00 00 00 82 00 02 4......#........
02 0F FD 16 23 00 06 00 00 00 01 00 02 02 0F FF ....#...........
16 1D 00 06 00 00 00 03 00 02 02 0F FF 16 1C D2 ................
01 7E .~

5. Request: 13:55:16.177
--------------------
Size 13 B (2,92%)
--------------------

03 00 0A 7E A0 08 02 23 03 53 32 B2 7E ...~...#.S2.~

6. Answer: 13:55:16.197
--------------------
Size 36 B (8,09%)
--------------------

03 00 21 7E A0 1F 03 02 23 73 C3 71 81 80 12 05 ..!~....#s.q....
01 9A 06 01 9A 07 04 00 00 00 01 08 04 00 00 00 ................
01 CC A2 7E

Here is hex log (from MC - if i read one actual value - current - instantaneous current):

1. Request: 13:57:24.695
--------------------
Size 13 B (4,19%)
--------------------

03 00 0A 7E A0 08 02 23 03 93 3E 74 7E ...~...#..>t~

2. Answer: 13:57:24.729
--------------------
Size 36 B (11,61%)
--------------------

03 00 21 7E A0 1F 03 02 23 73 C3 71 81 80 12 05 ..!~....#s.q....
01 9A 06 01 9A 07 04 00 00 00 01 08 04 00 00 00 ................
01 CC A2 7E ...~

3. Request: 13:57:24.729
--------------------
Size 74 B (23,87%)
--------------------

03 00 47 7E A0 45 02 23 03 10 FB 7F E6 E6 00 60 ..G~.E.#.......`
36 A1 09 06 07 60 85 74 05 08 01 01 8A 02 07 80 6....`.t........
8B 07 60 85 74 05 08 02 01 AC 0A 80 08 31 32 33 ..`.t........123
34 35 36 37 38 BE 10 04 0E 01 00 00 00 06 5F 1F 45678........._.
04 00 00 7E 1F FF FF 83 D7 7E ...~.....~

4. Answer: 13:57:24.761
--------------------
Size 61 B (19,68%)
--------------------

03 00 3A 7E A0 38 03 02 23 30 11 51 E6 E7 00 61 ..:~.8..#0.Q...a
29 A1 09 06 07 60 85 74 05 08 01 01 A2 03 02 01 )....`.t........
00 A3 05 A1 03 02 01 00 BE 10 04 0E 08 00 06 5F ..............._
1F 04 00 00 7E 1F 05 00 00 07 62 2B 7E ....~.....b+~

5. Request: 13:57:24.761
--------------------
Size 42 B (13,55%)
--------------------

03 00 27 7E A0 25 02 23 03 32 58 DC E6 E6 00 C0 ..'~.%.#.2X.....
03 41 02 00 03 01 00 0B 07 00 FF 02 00 00 03 01 .A..............
00 0B 07 00 FF 03 00 FB F1 7E .........~

6. Answer: 13:57:24.794
--------------------
Size 35 B (11,29%)
--------------------

03 00 20 7E A0 1E 03 02 23 52 0C 4A E6 E7 00 C4 .. ~....#R.J....
03 41 02 00 06 00 00 00 00 00 02 02 0F FD 16 21 .A.............!
E7 38 7E .8~

7. Request: 13:57:24.794
--------------------
Size 13 B (4,19%)
--------------------

03 00 0A 7E A0 08 02 23 03 53 32 B2 7E ...~...#.S2.~

8. Answer: 13:57:24.826
--------------------
Size 36 B (11,61%)
--------------------

03 00 21 7E A0 1F 03 02 23 73 C3 71 81 80 12 05 ..!~....#s.q....
01 9A 06 01 9A 07 04 00 00 00 01 08 04 00 00 00 ................
01 CC A2 7E ...~

Best regards,
David

Kurumi

2 years 9 months ago

Hi,

Are you reading your meter with MeterConfigurator using TCP/IP connection?
The reason why I ask this is that it's using HDLC framing and not WRAPPER.

Try to change the interface from WRAPPER to HDLC.
Client address is 1.
Logical address is 1.
Physical address is 0x17.

Now your settings are the same.

BR,
Mikko

davidzidar_INEA

2 years 9 months ago

Hi,

Thank you for your answer.

MC: I am using Consereth connection to read my meter with MeterConfiguration.

GXDLMSDirector: I forgot to tell you something. I get the pop up window( "You need to read Association view to see all objects what the meter can offer. Do you want to do it now?"), if I check the "Pre-established system title" and leave the input text box empty (you can see that in attachment) and WRAPPER selected. If "Pre-established system title" is unchecked, I get error window with "Failed to receive reply from the device in given time". I get the same message if I am using HDLC connection (if the "pre-established sy.." is checked or not - the message is the same).

My parameters (writing from the pop up window "Device properties", HEX near "initial settings" is checked):
Interface: Wrapper (also tried HDLC, but so far with no success)
Client address: 1
Logical server: 1
Physical server: 0x17
Authentication: Low (12345678)
Logical Name Referencing and ASCII is also checked.
Use Serial port through ethernet is UNchecked.

When I press connect, the pop up window appears (with the association view info). When i press cancel or no, and right click on the device, the "read object" option is locked, and only "read" is availible to click. When I press read, I get the error "GetObjects failed".

Best regards,
David

Image

Kurumi

2 years 9 months ago

Hi,

All meters don't implement an association view for pre-established connections.
So you must add all objects manually. You can do this if you select "Edit" and "Add Object". Then select object type and set the correct logical name.
Try to add a clock object and read it. All objects that you can read with a pre-established connection are in the meter manual.

BR,
Mikko

davidzidar_INEA

2 years 9 months ago

Hi,

Thank you for your answer.

I added one object manually (Clock - in MT880 documentation, OBIS code for the clock is 0-0:1.0.0*255 - so the logical name (0.0.1.0.0.255) for the clock should be correct, I think.

When I connect to the meter (WRAPPER or HDLC or HDLCwithmodeE - I tried all three; Also tried with and without authentication), add an object manually (clock - picture in attachment), and then press read, I get an error window with "Failed to receive a reply from the device in the given time" info.

This is the log (using WRAPPER):
GXDLMSDirector 0.0.0.0
Log created 08:26:32
08:26:33 Initializing Network connection.
08:26:36 Read object type Clock index: 2
00 01 00 01 00 17 00 0D C0 01 C1 00 08 00 00 01 00 00 FF 02 00
08:26:41 Data send failed. Try to resend 1/3
08:26:46 Data send failed. Try to resend 2/3
08:26:51 Failed to receive reply from the device in given time.
System.TimeoutException: Failed to receive reply from the device in given time.
at GXDLMSDirector.GXDLMSCommunicator.ReadDLMSPacket(Byte[] data, Int32 tryCount, GXReplyData reply) in C:\Users\dzidar\Documents\2023\ISKRA_STEVCI\30082023NEWTRY\GXDLMSDirector-master\GXDLMSDirector-master\Development\GXDLMSCommunicator.cs:line 461
at GXDLMSDirector.GXDLMSCommunicator.ReadDataBlock(Byte[] data, String text, Int32 multiplier, Int32 tryCount, GXReplyData reply) in C:\Users\dzidar\Documents\2023\ISKRA_STEVCI\30082023NEWTRY\GXDLMSDirector-master\GXDLMSDirector-master\Development\GXDLMSCommunicator.cs:line 1595
at GXDLMSDirector.GXDLMSCommunicator.ReadDataBlock(Byte[] data, String text, Int32 multiplier, GXReplyData reply) in C:\Users\dzidar\Documents\2023\ISKRA_STEVCI\30082023NEWTRY\GXDLMSDirector-master\GXDLMSDirector-master\Development\GXDLMSCommunicator.cs:line 1573
at GXDLMSDirector.GXDLMSCommunicator.ReadDataBlock(Byte[] data, String text, GXReplyData reply) in C:\Users\dzidar\Documents\2023\ISKRA_STEVCI\30082023NEWTRY\GXDLMSDirector-master\GXDLMSDirector-master\Development\GXDLMSCommunicator.cs:line 1485
at GXDLMSDirector.GXDLMSCommunicator.ReadDataBlock(Byte[][] data, String text, GXReplyData reply) in C:\Users\dzidar\Documents\2023\ISKRA_STEVCI\30082023NEWTRY\GXDLMSDirector-master\GXDLMSDirector-master\Development\GXDLMSCommunicator.cs:line 1478
at GXDLMSDirector.GXDLMSCommunicator.Read(Object sender, GXDLMSObject obj, Boolean forceRead) in C:\Users\dzidar\Documents\2023\ISKRA_STEVCI\30082023NEWTRY\GXDLMSDirector-master\GXDLMSDirector-master\Development\GXDLMSCommunicator.cs:line 1925
at GXDLMSDirector.MainForm.Read(Object sender, GXAsyncWork work, Object[] parameters) in C:\Users\dzidar\Documents\2023\ISKRA_STEVCI\30082023NEWTRY\GXDLMSDirector-master\GXDLMSDirector-master\Development\MainForm.cs:line 2827

Best regards,
David

Image

davidzidar_INEA

2 years 9 months ago

Hi,
I can provide some more info. When looking at the trace at GXDLMSDirector, it it interesting that the disconnect request:

Example from GXDLMSDir: 13:22:04 Send Disconnect request.
TX: 7E A0 08 02 23 03 53 32 B2 7E

Example from MC: 7. Request: 13:04:52.644
--------------------
Size 13 B (3,11%)
--------------------

03 00 0A 7E A0 08 02 23 03 53 32 B2 7E

are the same.
But the connect request is different:
Example from GXDLMSDir: 13:28:29 Send SNRM request.
TX: 7E A0 1F 02 23 03 93 A2 F0 81 80 12 05 01 9A 06 01 9A 07 04 00 00 00 01 08 04 00 00 00 01 CC A2 7E

Example from MC: 1. Request: 13:04:52.548
--------------------
Size 13 B (3,11%)
--------------------

03 00 0A 7E A0 08 02 23 03 93 3E 74 7E

Is there any option to modify connect request to be the same as MC conn req?

Best regards,
David

Kurumi

2 years 9 months ago

Hi,

You have modified frame settings. Select the Frame tab and change the max payload size from 154 to 128.

BR,
Mikko

davidzidar_INEA

2 years 9 months ago

Hi,

Thank you for your answer. Now the conn req is the same as in MC.

(08:07:56 Send SNRM request.
TX: 7E A0 08 02 23 03 93 3E 74 7E
08:08:01 Data send failed. Try to resend 1/3
08:08:06 Data send failed. Try to resend 2/3 ).

When looking at the packets with Wireshark, I see consereth overhead missing (the 03 00 part)

So I added this in code - in GXDLMSCommunicator (found on previous forum from 2015 - /*ivan consereth header*/ :

byte[] length = BitConverter.GetBytes((short)data.Length);
byte[] conserethHead = { 0x03, length[1], length[0] };
IEnumerable<byte> conserethData = conserethHead.Concat(data);
media.Send(conserethData.ToArray(), null);

Now connection is successful. I added clock object, when I tried to read it - i received some error (so i unchecked Pre-established system title).

It works now (reading objects is also succesful).... So happy. Very thankful for your help. Thank you.

Association view also works - just tried, it was successful!

Best regards,
David

Kurumi

2 years 9 months ago

Hi David,

I didn't remember the consereth extension because it's Iskraemeco's own custom solution and it's not in DLMS standard.

If you can read the meter now. I don't want to add this for the library because it's a custom solution and we are doomed if all custom ideas are added for the library.

BR,
Mikko