Can we Read Zhejiang Chint DLMS meter using GXDlms Director.

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 ayush , 1 March, 2021
Forums
DLMSDirector

Hi Kurumi,
Hope you are doing well.

I have a Chint DLMS meter and I want to read it using GXDLMS director tool. But, I am not able to find this meter name under Manufacturer option. Can I use other manufacturer name or there is some other alternative method.

Also, Can we use the same C stack(We have purchased from your company long back ago) in Micro Processors(Linux) to read DLMS meter. We are successfully able to read using Micro Controllers.

Pls help.

Thankyou,
AyushK

Kurumi

5 years 3 months ago

Hi,

If Zhejiang Chint is supporting DLMS you can read it with GXDLMSDirector. You can try to select Gurux as manufacturer and read ZHEJIANG CHINT INSTRUMENT & METER CO meter.

Please, let me know if you succeeded to read the meter and send device file to me. We can then add support for ZHEJIANG CHINT INSTRUMENT & METER CO.

You can also use C stack to read the meter.
BR,
Mikko

ayush

5 years 3 months ago

Hi,
Thanks for your reply. I am still waiting for their reply to get the server and address details. Once I will get that I can try to read it and will share the same.

Kurumi

5 years 3 months ago

Hi,

It's great if you can do share the client and server address so it's easier to use.

BR,
Mikko

ayush

5 years 3 months ago

Hi, Do you get any info in the attached image. I received this info from chint team. I tried to read using GXdlms director but it's not communicating.

Image

ayush

5 years 3 months ago

Hi,
I have one more query I am not able to understand below frame. when I am reading via tool its responding. but with c library its not responding. Below is the frame mentioned.

Meter Name : Elster AS3500
Client Add: 16
Logical Add: 1
Physical Add : 80
Authentication :Low

With Tool:
7E A0 21 02 A1 21 93 1C EC 81 80 14 05 02 03 E7 06 02 03 E6 07 04 00 00 00 01 08 04 00 00 00 01 BC 61 7E

With C stack :
7e a0 14 03 21 93 63 e7 81 80 08 05 02 03 f2 06 02 03 f2 03 f0 7e

ayush

5 years 3 months ago

Hi,
Can you pls check and update me.

Hi,

Set client address to 17 (0x11) and the server's Logical address is 100 (0x64) and Physical address: 37 (0x25). If the address is wrong the meter doesn't reply anything.

BR,
Mikko

Kurumi

5 years 3 months ago

Hi,

Your addresses are different from the meter expects and the meter is not replying for that reason. Use those values:
Server address: 0xD0 and client address: 0x10.

BR,
Mikko

ayush

5 years 3 months ago

Hi,
Thanks for your reply. Can you tell me how you have calculated the addresses. Also, is these addresses dependent on meter serial number, means if serial number is different will this addresses change accordingly?

ayush

5 years 3 months ago

I am still checking this one. I will let you know if there is any problem in reading.
Also can you tell me.
In the tool we are providing physical address, but in C stack we are not providing why?

ayush

5 years 3 months ago

Hi Kurumi,
I am successfully able to read the meter via Tool. Logical and Physical add. will depend on meter serial number.
For Eg :
Chint meter serial no. - XXXX00050068
Physical server : 16 + 68 = 84 (decimal)
Logical Server : 16 + 5 = 21(decimal)
Client address: 11(hex)
Low authentication Password: Low level security, 12345678
RX TX frame size used = 1010

Now I will check with the C stack and I will let you know.

ayush

5 years 3 months ago

Hi,
I am able to read chint meter via tool, but not able to read via c stack. below is the frames.
Via Tool:
13:03:27 Initializing serial connection.
1:03:28 PM Send SNRM request.
7E A0 21 2A A9 23 93 E5 73 81 80 14 05 02 03 E7 06 02 03 E6 07 04 00 00 00 01 08 04 00 00 00 01 BC 61 7E
1:03:28 PM
7E A0 1F 23 2A A9 73 D5 4A 81 80 12 05 01 80 06 01 80 07 04 00 00 00 01 08 04 00 00 00 01 53 3B 7E
Duration: 87
13:03:28 Parsing UA reply succeeded.
1:03:28 PM Send AARQ request.
7E A0 45 2A A9 23 10 D5 49 E6 E6 00 60 36 A1 09 06 07 60 85 74 05 08 01 01 8A 02 07 80 8B 07 60 85 74 05 08 02 01 AC 0A 80 08 31 32 33 34 35 36 37 38 BE 10 04 0E 01 00 00 00 06 5F 1F 04 00 00 1E 5D FF FF A9 FD 7E
1:03:28 PM
7E A0 38 23 2A A9 30 07 6A E6 E7 00 61 29 A1 09 06 07 60 85 74 05 08 01 01 A2 03 02 01 00 A3 05 A1 03 02 01 00 BE 10 04 0E 08 00 06 5F 1F 04 00 00 1A 1D 00 F3 00 07 F0 A7 7E
1:03:39 PM Read object type Register index: 2
7E A0 1A 2A A9 23 BA 1B 5C E6 E6 00 C0 01 C1 00 03 01 00 20 07 00 FF 02 00 85 83 7E
1:03:39 PM
7E A0 16 23 2A A9 DA 7A 23 E6 E7 00 C4 01 C1 00 06 00 03 79 71 CB B2 7E
Duration: 77

Via C Stack:
SNRM:
7e a0 14 2b 23 93 2a 11 81 80 08 05 02 03 f2 06 02 03 f2 03 f0 7e
received buffer: 32
7e a0 1e 23 2b 73 88 22 81 80 12 05 01 80 06 01 80 07 04 00 00 00 01 08 04 00 00 00 01 53 3b 7e
AARQ:
sending Command:
7e a0 44 2b 23 10 af 72 e6 e6 00 60 36 a1 09 06 07 60 85 74 05 08 01 01 8a 02 07 80 8b 07 60 85 74 05 08 02 01 ac 0a 80 08 31 32 33 34 35 36 37 38 be 10 04 0e 01 00 00 00 06 5f 1f 04 00 40 1e 1d ff ff fd 3a 7e
received buffer: 57
7e a0 37 23 2b 30 27 24 e6 e7 00 61 29 a1 09 06 07 60 85 74 05 08 01 01 a2 03 02 01 00 a3 05 a1 03 02 01 00 be 10 04 0e 08 00 06 5f 1f 04 00 00 1a 1d 00 f3 00 07 f0 a7 7e

Querying obis : 1.1.32.7.0.255,0,3
sending Command:
7e a0 19 2b 23 32 26 2e e6 e6 00 c0 01 81 00 03 01 01 20 07 00 ff 02 00 55 d1 7e
received buffer: 19
7e a0 11 23 2b 52 fa a0 e6 e7 00 c4 01 81 01 04 ba f0 7e

And I don't know why this logical address is changing in the frame if queried via tool, even though I am giving 21 its showing 2772 in the frame.

Also can you tell me.
In the tool we are providing physical address, but in C stack we are not providing why?

Kurumi

5 years 3 months ago

Hi,

You can read more about how to count HDLC address from here:
https://www.gurux.fi/dlmsAddress

You can usually use the serial number to count the meter address.

BR,
Mikko

Kurumi

5 years 3 months ago

Hi,

You can use the device address 0xAD4. You can use cl_getServerAddress-method to count server address from the logical and physical address.
Something like:
Logical address:21, Physical address:84
cl_getServerAddress(21, 84, 0);

BR,
Mikko

Kurumi

5 years 3 months ago

Hi,

Another application is proposing different frame sizes (1010). If your meter is not answering the problem is that your client and server sizes are different.

BR,
Mikko

ayush

5 years 3 months ago

Hi, Thanks for your reply

I don't have this method in my stack. Can you pls provide.

ayush

5 years 3 months ago

Hi,
I am able to read Chint meter from stack also.
I did a mistake in OBIS query. Instead of querying 1.0.32.7.0.255, I was querying 1.1.32.7.0.255. That's why it was not responding. I used the same settings as mentioned below.

Logical Server : 21
Client address: 17

ayush

5 years 3 months ago

Hi, I have sent you the logs in your email id.
Note : Manufacturer used KAMSTRUP in the tool.

ayush

5 years 3 months ago

Hi,
I am about to receive Elster meter in a couple of days, If I face issue in reading it I will contact you in separate subject in this forum. Earlier I was checking remotely.

Kurumi

5 years 3 months ago

Hi,

I really know what you mean by that the OBIS code is wrong. Sometimes it's so hard to see that OBIS code is invalid.

BR,
Mikko

ayush

5 years 3 months ago

Hi, I have a query.
Let suppose multiple DLMS meters are connected in same RS485 port. Then how will i differentiate the meters of same manufacturers as addressess will be same.

Hi,

You can count the meter address from the meter serial number. All meter manufacturers are not using the same formula and for this reason, you must know how to count the meter address from the serial number.

BR,
Mikko