One of the problems solved, at least in the Old version of Gurux, this meter uses GXDLMSRegister for 1.1.1.8.1.255, and NOT the GXDLMSExtendedRegister.
With Java older versions I get connected at least, and I can read some codes, the biggest problem I've got with new versions (Java, also python version!) is that it reads no answer, even though the meter do answer..
I've recorded the behavior for you to see, with a byte counter (attached gif)
Sorry I haven't got the number of "old" version, because it's a mix of source codes, but I can tell you it uses GXCommunicate instead of GXDLMSReader
Backing to the github version, here is the full log: (please look for the TIME of waiting, it's about ONE MINUTE waiting for an answer that the meter already sent)
WITH LATEST VERSION
============================================
Authentication: None
ClientAddress: 0x10
ServerAddress: 0x1
TX: 13:51:02.002 7E A0 07 03 21 93 0F 01 7E
RX: 13:51:02.065 7E A0 1E 21 03 73 C3 7A 81 80 12 05 01 80 06 01 3E 07 04 00 00 00 01 08 04 00 00 00 01 07 22 7E
TX: 13:51:02.065 7E A0 2B 03 21 10 FB AF E6 E6 00 60 1D A1 09 06 07 60 85 74 05 08 01 01 BE 10 04 0E 01 00 00 00 06 5F 1F 04 00 00 1E 1D FF FF C5 E4 7E
Data send failed. Try to resend 1/3
TX: 13:52:02.195 7E A0 2B 03 21 10 FB AF E6 E6 00 60 1D A1 09 06 07 60 85 74 05 08 01 01 BE 10 04 0E 01 00 00 00 06 5F 1F 04 00 00 1E 1D FF FF C5 E4 7E
RX: 13:52:02.242 7E A0 37 21 03 30 6C 7C E6 E7 00 61 28 A1 09 06 07 60 85 74 05 08 01 01 A2 03 02 01 00 A3 05 A1 03 02 01 00 BE 0F 04 0D 08 00 06 5F 1F 04 00 00 02 18 13 88 00 07 38 2F 7E
13:52:02.273 [main] DEBUG guruxclient.LandisGyr - READING TIME
TX: 13:52:02.273 7E A0 19 03 21 32 6F D8 E6 E6 00 C0 01 C1 00 08 00 00 01 00 00 FF 02 00 60 1A 7E
RX: 13:52:02.320 7E A0 0C 21 03 97 3E 21 10 22 08 29 D6 7E
13:52:02.320 [main] ERROR guruxclient.LandisGyr - ex::
gurux.dlms.GXDLMSException: Access Error : Unknown error.
at gurux.dlms.client.GXDLMSReader.readDLMSPacket(GXDLMSReader.java:297) ~[guruxGithubMaven-1.0-SNAPSHOT-jar-with-dependencies.jar:na]
at gurux.dlms.client.GXDLMSReader.readDataBlock(GXDLMSReader.java:320) ~[guruxGithubMaven-1.0-SNAPSHOT-jar-with-dependencies.jar:na]
at gurux.dlms.client.GXDLMSReader.read(GXDLMSReader.java:493) ~[guruxGithubMaven-1.0-SNAPSHOT-jar-with-dependencies.jar:na]
WITH OLD VERSION
============================================
============================================
PD: About python version, it it only gives this answer (note 15 seconds between send and reply, even though meter responds immediately)
============================================
Gurux.DLMS.Client.Example.python>python main.py -t Verbose -r sn -c 16 -s 1 -S COM99
Authentication: Authentication.NONE
ClientAddress: 0x10
ServerAddress: 0x1
TX: 15:28:08 7E A0 07 03 21 93 0F 01 7E
RX: 15:28:23 7E A0 1E 21 03 73 C3 7A 81 80 12 05 01 80 06 01 3E 07 04 00 00 00 01 08 04 00 00 00 01 07 22 7E
DisconnectRequest
We'll check python. You need to decrease the wait time. The message is lost and I believe it's causing the problem. Change wait time example to 10 seconds and try again.
Data is correct. GeneralProtection flag is set on a new version, but otherwise generated data is same.
One of the problems solved,
One of the problems solved, at least in the Old version of Gurux, this meter uses GXDLMSRegister for 1.1.1.8.1.255, and NOT the GXDLMSExtendedRegister.
Hi,
Hi,
I can't say anything without a full trace, but the frame counter is wrong for some reason.
Are you calling read withour sending it?
BR,
Mikko
With Java older versions I
With Java older versions I get connected at least, and I can read some codes, the biggest problem I've got with new versions (Java, also python version!) is that it reads no answer, even though the meter do answer..
I've recorded the behavior for you to see, with a byte counter (attached gif)
To see animated
To see animated
https://media.giphy.com/media/UqFpBwgrlnnirPgG4Y/giphy.gif
To see animated
.
Hi hernan,
Hi hernan,
What is the version number of the old version? Can you send a textual log from received data?
BR,
Mikko
Sorry I haven't got the
Sorry I haven't got the number of "old" version, because it's a mix of source codes, but I can tell you it uses GXCommunicate instead of GXDLMSReader
Backing to the github version, here is the full log: (please look for the TIME of waiting, it's about ONE MINUTE waiting for an answer that the meter already sent)
WITH LATEST VERSION
============================================
Authentication: None
ClientAddress: 0x10
ServerAddress: 0x1
TX: 13:51:02.002 7E A0 07 03 21 93 0F 01 7E
RX: 13:51:02.065 7E A0 1E 21 03 73 C3 7A 81 80 12 05 01 80 06 01 3E 07 04 00 00 00 01 08 04 00 00 00 01 07 22 7E
TX: 13:51:02.065 7E A0 2B 03 21 10 FB AF E6 E6 00 60 1D A1 09 06 07 60 85 74 05 08 01 01 BE 10 04 0E 01 00 00 00 06 5F 1F 04 00 00 1E 1D FF FF C5 E4 7E
Data send failed. Try to resend 1/3
TX: 13:52:02.195 7E A0 2B 03 21 10 FB AF E6 E6 00 60 1D A1 09 06 07 60 85 74 05 08 01 01 BE 10 04 0E 01 00 00 00 06 5F 1F 04 00 00 1E 1D FF FF C5 E4 7E
RX: 13:52:02.242 7E A0 37 21 03 30 6C 7C E6 E7 00 61 28 A1 09 06 07 60 85 74 05 08 01 01 A2 03 02 01 00 A3 05 A1 03 02 01 00 BE 0F 04 0D 08 00 06 5F 1F 04 00 00 02 18 13 88 00 07 38 2F 7E
13:52:02.273 [main] DEBUG guruxclient.LandisGyr - READING TIME
TX: 13:52:02.273 7E A0 19 03 21 32 6F D8 E6 E6 00 C0 01 C1 00 08 00 00 01 00 00 FF 02 00 60 1A 7E
RX: 13:52:02.320 7E A0 0C 21 03 97 3E 21 10 22 08 29 D6 7E
13:52:02.320 [main] ERROR guruxclient.LandisGyr - ex::
gurux.dlms.GXDLMSException: Access Error : Unknown error.
at gurux.dlms.client.GXDLMSReader.readDLMSPacket(GXDLMSReader.java:297) ~[guruxGithubMaven-1.0-SNAPSHOT-jar-with-dependencies.jar:na]
at gurux.dlms.client.GXDLMSReader.readDataBlock(GXDLMSReader.java:320) ~[guruxGithubMaven-1.0-SNAPSHOT-jar-with-dependencies.jar:na]
at gurux.dlms.client.GXDLMSReader.read(GXDLMSReader.java:493) ~[guruxGithubMaven-1.0-SNAPSHOT-jar-with-dependencies.jar:na]
WITH OLD VERSION
============================================
Authentication: None
ClientAddress: 0x10
ServerAddress: 0x1
<- 14:20:32.954 7E A0 07 03 21 93 0F 01 7E
-> 14:20:33.032 7E A0 1E 21 03 73 C3 7A 81 80 12 05 01 80 06 01 3E 07 04 00 00 00 01 08 04 00 00 00 01 07 22 7E
<- 14:20:33.267 7E A0 2B 03 21 10 FB AF E6 E6 00 60 1D A1 09 06 07 60 85 74 05 08 01 01 BE 10 04 0E 01 00 00 00 06 5F 1F 04 00 40 1E 1D FF FF E7 25 7E
-> 14:20:33.376 7E A0 37 21 03 30 6C 7C E6 E7 00 61 28 A1 09 06 07 60 85 74 05 08 01 01 A2 03 02 01 00 A3 05 A1 03 02 01 00 BE 0F 04 0D 08 00 06 5F 1F 04 00 00 02 18 13 88 00 07 38 2F 7E
14:20:33.391 [main] DEBUG guruxclient.Common - man.getName():Landis+Gyr
14:20:33.407 [main] DEBUG guruxclient.LandisGyr - READING TIME
<- 14:20:33.626 7E A0 19 03 21 32 6F D8 E6 E6 00 C0 01 C1 00 08 00 00 01 00 00 FF 02 00 60 1A 7E
-> 14:20:33.704 7E A0 1E 21 03 52 48 4A E6 E7 00 C4 01 C1 00 09 0C 07 E3 09 10 01 0E 10 11 FF 80 00 00 36 C8 7E
============================================
PD: About python version, it it only gives this answer (note 15 seconds between send and reply, even though meter responds immediately)
============================================
Gurux.DLMS.Client.Example.python>python main.py -t Verbose -r sn -c 16 -s 1 -S COM99
Authentication: Authentication.NONE
ClientAddress: 0x10
ServerAddress: 0x1
TX: 15:28:08 7E A0 07 03 21 93 0F 01 7E
RX: 15:28:23 7E A0 1E 21 03 73 C3 7A 81 80 12 05 01 80 06 01 3E 07 04 00 00 00 01 08 04 00 00 00 01 07 22 7E
DisconnectRequest
Hi,
Hi,
We'll check python. You need to decrease the wait time. The message is lost and I believe it's causing the problem. Change wait time example to 10 seconds and try again.
Data is correct. GeneralProtection flag is set on a new version, but otherwise generated data is same.
BR,
Mikko
Hi,
Hi,
There is a new version from Python (1.0.26) where are fixed few Short Name referencing issues.
You can now read your LGZ using Python.
BR,
Mikko