Cannot connect to Kamstrup Omnipower meter

36 posts / 0 new
Last post
flok
Cannot connect to Kamstrup Omnipower meter

Hello!

I try to connect Gurux GXDLMSDirector with a Kamstrup Omnipower Three-Phase meter. But I always get the error message "not enough data".

Here is the log:
GXDLMSDirector 8.0.1708.1801
Log created 22:00:54
22:00:55 Initializing serial connection.
22:00:55 Send SNRM request.
7E A0 14 03 21 93 63 E7 81 80 08 05 02 00 80 06 02 00 80 F8 85 7E
22:00:55 Received data
7E A0 14 03 21 93 63 E7 81 80 08 05 02 00 80 06 02 00 80 F8 85 7E 7E A0 20 21 03 73 73 98 81 80 14 05 02 00 80 06 02 00 80 07 04 00 00 00 01 08 04 00 00 00 01 CE 6A 7E
22:00:55 Parsing UA reply.<CR><LF>81 80 14 05 02 00 80 06 02 00 80 07 04 00 00 00 01 08 04 00 00 00 01
22:00:55 Parsing UA reply succeeded.
22:00:55
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 18 1E FF FF 3B 40 7E
22:00:55 Received data
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 18 1E FF FF 3B 40 7E 7E A0 39 21 03 30 2E D2 E6 E7 00 61 82 00 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 10 1C 03 EF 00 07 00 3D 7E
22:00:55 Disconnect request
System.Exception: Not enough data.
at GXDLMSDirector.GXDLMSDevice.InitializeConnection()
at GXDLMSDirector.MainForm.Connect(Control sender, Object[] parameters)

I also tested with your java demo app with the following log:
Authentication: None
ClientAddress: 0x10
ServerAddress: 0x1
<- 21:51:17.598 7E A0 07 03 21 93 0F 01 7E
-> 21:51:17.659 7E A0 07 03 21 93 0F 01 7E 7E A0 20 21 03 73 73 98 81 80 14 05 02 00 80 06 02 00 80 07 04 00 00 00 01 08 04 00 00 00 01 CE 6A 7E
<- 21:51:17.662 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
-> 21:51:17.786 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 7E A0 39 21 03 30 2E D2 E6 E7 00 61 82 00 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 10 1D 03 EF 00 07 44 36 7E
Not enough data.

If I use another application I get the following log. Readout (Association LN) works here:
Source: CLIENT
7E A0 20 03 21 93 7D D9 81 80 14 05 02 07 EE 06 02 07 EE 07 04 00 00 00 01 08 04 00 00 00 01 B5 D4 7E

Source: SERVER
7E A0 20 21 03 73 73 98 81 80 14 05 02 03 F2 06 02 03 F2 07 04 00 00 00 01 08 04 00 00 00 01 0A 75 7E

Source: CLIENT
7E A0 34 03 21 10 A3 DE E6 E6 00 60 26 A1 09 06 07 60 85 74 05 08 01 01 8B 07 60 85 74 05 08 02 00 BE 10 04 0E 01 00 00 00 06 5F 1F 04 00 00 18 1D FF FF 13 ED 7E

Source: SERVER
7E A0 39 21 03 30 2E D2 E6 E7 00 61 82 00 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 10 1D 03 EF 00 07 44 36 7E

Source: CLIENT
7E A0 19 03 21 32 6F D8 E6 E6 00 C0 01 41 00 0F 00 00 28 00 00 FF 02 00 8A C1 7E

Do you have an idea why I get this error?

Kind regards
Florian

kurumi
kurumi's picture
Omnipower

Hi,

Ask from the manufacturer If there is new firmware available. Your meter is returning wrong size. Reason why you can read with another application is that it don't check received data size.
Meter should send this data: (I manually modified reply of the meter).
http://www.gurux.fi/GuruxDLMSTranslator?pdu=6128A109060760857405080101A2...

BR,

Mikko

________________________________________
Mikko Kurunsaari
Gurux Ltd
Hermiankatu 6-8 H 33720 TAMPERE, FINLAND
Phone: +358 3 265 1244
Home page: http://www.gurux.org

flok
Thank you for your fast reply

Thank you for your fast reply!

kurumi
kurumi's picture
Omnipower

Hi,

If that is not fixed, let me know what programming language you want to use and I show what line you must comment out to read your meter.

BR,

Mikko

________________________________________
Mikko Kurunsaari
Gurux Ltd
Hermiankatu 6-8 H 33720 TAMPERE, FINLAND
Phone: +358 3 265 1244
Home page: http://www.gurux.org

flok
Hello!

Hello!
I wanted to ask if I can get "workaround" for java so I can do further testing?
Kind regards
Florian

flok
Hello!

Hello!

I contacted Kamstrup. Can you give me your "workaraound" anyway so I can proceed testing till I get an answer from Kamstrup? I'm using Java.

Kind regards
Florian

kurumi
kurumi's picture
Omnipower

Hi,
Open

GXAPDU.java go to parseUserInformation
Comment lines 317 and 329

Let me know if you have more problems.

BR,

Mikko

________________________________________
Mikko Kurunsaari
Gurux Ltd
Hermiankatu 6-8 H 33720 TAMPERE, FINLAND
Phone: +358 3 265 1244
Home page: http://www.gurux.org

flok
Hello!

Hello!
Thank you four your answer but unfortunately your fix doesn't work because the exception that causes the fault is still thrown. But meanwhile I got an answer from kamstrup:
"This is a valid BER encoding of number of bytes to come, when it can be expected that nob can’t be represented in 7 bits available.
82 nob is represented 2 bytes
00 high byte of nob
29 low byte of nob"

So I modified GXAPDU.java that it takes the right two bytes for the data length and now it works.

But now I have a new problem:
After establishing a secure connection Gurux uses a glo-get-request but the meter only supports general-glo-ciphering. Is there a possibility to tell gurux to use general-glo-ciphering?

Kind regards
Florian

kurumi
kurumi's picture
Omnipower

Hi,

This is PDU what meter reply. You are right. I miss this when I check this. All other meters are sending data size with one byte.
I don't understand why they want to send it like this and add extra bytes. Every byte counts. :-)
You can replace your issue if you modify
ParsePDU
Change
int len = buff.GetUInt8();
to
int len = GXCommon.GetObjectCount(buff);

But there is a another issue in InitiateResponse and this is what I was talking about:

60 85 74 05 08 01 01 BE 10 04 0E 01 00 00 00 06 5F 1F 04 00 00 18 1E FF FF 3B 40 7E 7E A0 39 21 03 30 2E D2 E6 E7 00 61 82 00 29 A1 09 06 07 60 85 74 05 08 01 01 A2 03 02 01 00 A3 05 A1 03 02 01 00

InitiateResponse
BE
10 LEN: 16
04 TAG
0E LEN 15
08 00 06 5F 1F 04 00 00 10 1C 03 EF 00 07 //DATA

Count how many bytes there are on the data. Length is 1 too high.
I forget that we have remove check from here because there is other meter manufacturer who is counting this wrong, so it don't throw error anymore, but this is a issue.

BR,

Mikko

________________________________________
Mikko Kurunsaari
Gurux Ltd
Hermiankatu 6-8 H 33720 TAMPERE, FINLAND
Phone: +358 3 265 1244
Home page: http://www.gurux.org

flok
Hello!

Hello!

Again thank you four your detailed answer. Can you also say something to my other problem where gurux uses a glo-get-request and the meter only supports general-glo-ciphering? (see my last post above)

Kind regards
Florian

kurumi
kurumi's picture
Omnipower

Hi,

Are you from Italy? Is your meter supporting Italian Standard UNI 11291?

BR,

Mikko

________________________________________
Mikko Kurunsaari
Gurux Ltd
Hermiankatu 6-8 H 33720 TAMPERE, FINLAND
Phone: +358 3 265 1244
Home page: http://www.gurux.org

flok
Hello!

Hello!
The meter is used in austria. I don't know if it supports the italian standard. I only got the information from kamstrup that I have to use general-glo-ciphering instead of glo-get-request.
Kind regards
Florian

kurumi
kurumi's picture
Omnipower

Hi,

Can you read your meter with GXDLMSDirector. There is a new version available that can read your meter.
Restart GXDLMSDirector and you get announce that there is a new version available. Install that.
Then send byte trace to me. We'll check this.

BR,
Mikko

________________________________________
Mikko Kurunsaari
Gurux Ltd
Hermiankatu 6-8 H 33720 TAMPERE, FINLAND
Phone: +358 3 265 1244
Home page: http://www.gurux.org

flok
Hello!

Hello!

Reading the meter with the new GXDLMSDirecotor also fails:
GXDLMSDirector 8.0.1710.1101
Log created 13:05:12
13:05:14 Initializing serial connection.
13:05:14 Send SNRM request.
7E A0 07 21 25 93 EC D0 7E
13:05:15 Received data
7E A0 07 21 25 93 EC D0 7E 7E A0 20 25 21 73 91 EB 81 80 14 05 02 00 80 06 02 00 80 07 04 00 00 00 01 08 04 00 00 00 01 CE 6A 7E
13:05:15 Parsing UA reply.<CR><LF>81 80 14 05 02 00 80 06 02 00 80 07 04 00 00 00 01 08 04 00 00 00 01
13:05:15 Parsing UA reply succeeded.
13:05:15
7E A0 68 21 25 10 62 4D 60 5D A1 09 06 07 60 85 74 05 08 01 03 A6 0A 04 08 31 32 33 34 35 36 37 38 8A 02 07 80 8B 07 60 85 74 05 08 02 02 AC 12 80 10 2A 67 77 1F 77 5F 30 16 2E 50 06 70 3D 49 3A 37 BE 23 04 21 21 1F 30 00 00 01 9F FB E4 1E 46 5D D7 D5 D3 C3 F8 CA 90 C5 86 CC 7A F1 70 E6 D1 97 4B 0C 2E 58 6B FD B5 7E
Data send failed. Try to resend 1/3
Data send failed. Try to resend 2/3
13:05:57 Failed to receive reply from the device in given time.
7E A0 68 21 25 10 62 4D 60 5D A1 09 06 07 60 85 74 05 08 01 03 A6 0A 04 08 31 32 33 34 35 36 37 38 8A 02 07 80 8B 07 60 85 74 05 08 02 02 AC 12 80 10 2A 67 77 1F 77 5F 30 16 2E 50 06 70 3D 49 3A 37 BE 23 04 21 21 1F 30 00 00 01 9F FB E4 1E 46 5D D7 D5 D3 C3 F8 CA 90 C5 86 CC 7A F1 70 E6 D1 97 4B 0C 2E 58 6B FD B5 7E
13:05:57 Received data
7E A0 68 21 25 10 62 4D 60 5D A1 09 06 07 60 85 74 05 08 01 03 A6 0A 04 08 31 32 33 34 35 36 37 38 8A 02 07 80 8B 07 60 85 74 05 08 02 02 AC 12 80 10 2A 67 77 1F 77 5F 30 16 2E 50 06 70 3D 49 3A 37 BE 23 04 21 21 1F 30 00 00 01 9F FB E4 1E 46 5D D7 D5 D3 C3 F8 CA 90 C5 86 CC 7A F1 70 E6 D1 97 4B 0C 2E 58 6B FD B5 7E
System.Exception: Failed to receive reply from the device in given time.
at GXDLMSDirector.GXDLMSDevice.InitializeConnection()
at GXDLMSDirector.MainForm.Connect(Control sender, Object[] parameters)

But If I use your Java sample client and modify it I get the following trace:

Authentication: HighGMac
ClientAddress: 0x12
ServerAddress: 0x10
<- 12:47:35.627 7E A0 07 21 25 93 EC D0 7E
-> 12:47:35.782 7E A0 07 21 25 93 EC D0 7E 7E A0 20 25 21 73 91 EB 81 80 14 05 02 00 80 06 02 00 80 07 04 00 00 00 01 08 04 00 00 00 01 CE 6A 7E
Okt 12, 2017 12:47:35 PM gurux.dlms.secure.GXDLMSChippering encryptAesGcm
INFO: Encrypt settings: Security: AUTHENTICATION_ENCRYPTION InvocationCounter: 407 SystemTitle: 31 32 33 34 35 36 37 38 AuthenticationKey: *********************************************** BlockCipherKey: ***********************************************
Okt 12, 2017 12:47:35 PM gurux.dlms.secure.GXDLMSChippering encryptAesGcm
INFO: Crypted: 211F300000019751C2C42B0191B4FB59A4D8D409321F20CA297C3B0C2DE84563CE
<- 12:47:35.801 7E A0 6B 21 25 10 AF 68 E6 E6 00 60 5D A1 09 06 07 60 85 74 05 08 01 03 A6 0A 04 08 31 32 33 34 35 36 37 38 8A 02 07 80 8B 07 60 85 74 05 08 02 05 AC 12 80 10 1F 21 4D 5A 6D 75 72 22 75 6E 51 78 18 1B 29 4C BE 23 04 21 21 1F 30 00 00 01 97 51 C2 C4 2B 01 91 B4 FB 59 A4 D8 D4 09 32 1F 20 CA 29 7C 3B 0C 2D E8 45 63 CE DF 6A 7E
-> 12:47:36.195 7E A0 6B 21 25 10 AF 68 E6 E6 00 60 5D A1 09 06 07 60 85 74 05 08 01 03 A6 0A 04 08 31 32 33 34 35 36 37 38 8A 02 07 80 8B 07 60 85 74 05 08 02 05 AC 12 80 10 1F 21 4D 5A 6D 75 72 22 75 6E 51 78 18 1B 29 4C BE 23 04 21 21 1F 30 00 00 01 97 51 C2 C4 2B 01 91 B4 FB 59 A4 D8 D4 09 32 1F 20 CA 29 7C 3B 0C 2D E8 45 63 CE DF 6A 7E 7E A0 89 25 21 30 50 C0 E6 E7 00 61 82 00 79 A1 09 06 07 60 85 74 05 08 01 03 A2 03 02 01 00 A3 05 A1 03 02 01 0E A4 0A 04 08 4B 41 4D 45 01 AE DD 42 88 02 07 80 89 07 60 85 74 05 08 02 05 AA 22 80 20 9E E9 57 A4 79 02 70 4A D6 66 31 C6 AF 89 39 DD A8 F8 8C D8 9C 55 23 F3 D5 5B 45 A5 82 C4 D3 41 BE 23 04 21 28 1F 30 00 00 01 34 BD 17 D6 BD 61 2F A3 F8 B4 E3 38 7B C1 1A E9 79 E6 73 94 FA EA 11 00 B0 CD AA B3 76 7E
Okt 12, 2017 12:47:36 PM gurux.dlms.secure.GXDLMSChippering decryptAesGcm
INFO: Decrypt settings: Security: AUTHENTICATION_ENCRYPTION InvocationCounter: 308 SystemTitle: 4B 41 4D 45 01 AE DD 42 AuthenticationKey: *********************************************** BlockCipherKey: ***********************************************
SharedSecret:
Okt 12, 2017 12:47:36 PM gurux.dlms.secure.GXDLMSChippering decryptAesGcm
INFO: Encrypted: BD17D6BD612FA3F8B4E3387BC11AE979E67394FAEA1100B0CDAA
Okt 12, 2017 12:47:36 PM gurux.dlms.secure.GXDLMSChippering encryptAesGcm
INFO: Encrypt settings: Security: AUTHENTICATION InvocationCounter: 408 SystemTitle: 31 32 33 34 35 36 37 38 AuthenticationKey: *********************************************** BlockCipherKey: ***********************************************
Okt 12, 2017 12:47:36 PM gurux.dlms.secure.GXDLMSChippering encryptAesGcm
INFO: Crypted: 04A054FA8165E9CA21A1B3C7
Okt 12, 2017 12:47:36 PM gurux.dlms.secure.GXDLMSChippering encryptAesGcm
INFO: Encrypt settings: Security: AUTHENTICATION_ENCRYPTION InvocationCounter: 408 SystemTitle: 31 32 33 34 35 36 37 38 AuthenticationKey: *********************************************** BlockCipherKey: ***********************************************
Okt 12, 2017 12:47:36 PM gurux.dlms.secure.GXDLMSChippering encryptAesGcm
INFO: Crypted: CB31300000019898E6A18052205CF4CD5F9080AEA1125F8F4A57F97A6CDA9F46F39624FD3A7AACAB7218839A598059A4DB8AAD
<- 12:47:36.215 7E A0 3F 21 25 32 45 CD E6 E6 00 CB 31 30 00 00 01 98 98 E6 A1 80 52 20 5C F4 CD 5F 90 80 AE A1 12 5F 8F 4A 57 F9 7A 6C DA 9F 46 F3 96 24 FD 3A 7A AC AB 72 18 83 9A 59 80 59 A4 DB 8A AD 05 EF 7E
SharedSecret:
-> 12:47:36.399 7E A0 3F 21 25 32 45 CD E6 E6 00 CB 31 30 00 00 01 98 98 E6 A1 80 52 20 5C F4 CD 5F 90 80 AE A1 12 5F 8F 4A 57 F9 7A 6C DA 9F 46 F3 96 24 FD 3A 7A AC AB 72 18 83 9A 59 80 59 A4 DB 8A AD 05 EF 7E 7E A0 38 25 21 52 63 FD E6 E7 00 CF 2A 30 00 00 01 36 D5 6B DF AE A7 CA 13 F2 4A 59 DB 18 2B CE C8 61 EC 94 E4 64 C9 4F 62 5D BF 86 B2 78 8A 72 CD 20 36 05 E7 E2 48 92 A5 7E
Okt 12, 2017 12:47:36 PM gurux.dlms.secure.GXDLMSChippering decryptAesGcm
INFO: Decrypt settings: Security: AUTHENTICATION_ENCRYPTION InvocationCounter: 310 SystemTitle: 4B 41 4D 45 01 AE DD 42 AuthenticationKey: *********************************************** BlockCipherKey: ***********************************************
Okt 12, 2017 12:47:36 PM gurux.dlms.secure.GXDLMSChippering decryptAesGcm
INFO: Encrypted: D56BDFAEA7CA13F24A59DB182BCEC861EC94E464C94F625DBF86B2788A72CD203605E7E248
Okt 12, 2017 12:47:36 PM gurux.dlms.secure.GXDLMSChippering encryptAesGcm
INFO: Encrypt settings: Security: AUTHENTICATION InvocationCounter: 309 SystemTitle: 4B 41 4D 45 01 AE DD 42 AuthenticationKey: *********************************************** BlockCipherKey: ***********************************************
Okt 12, 2017 12:47:36 PM gurux.dlms.secure.GXDLMSChippering encryptAesGcm
INFO: Crypted: C69FE81582FB593D7BEF37E2
Okt 12, 2017 12:47:36 PM gurux.dlms.secure.GXDLMSChippering encryptAesGcm
INFO: Encrypt settings: Security: AUTHENTICATION_ENCRYPTION InvocationCounter: 409 SystemTitle: 31 32 33 34 35 36 37 38 AuthenticationKey: *********************************************** BlockCipherKey: ***********************************************
Okt 12, 2017 12:47:36 PM gurux.dlms.secure.GXDLMSChippering encryptAesGcm
INFO: Crypted: C81E30000001992B0EE2567905EAD5D6221AED92252CCC9128640267C5E53EE3
<- 12:47:36.408 7E A0 2C 21 25 54 19 2D E6 E6 00 C8 1E 30 00 00 01 99 2B 0E E2 56 79 05 EA D5 D6 22 1A ED 92 25 2C CC 91 28 64 02 67 C5 E5 3E E3 BC 04 7E
-> 12:47:36.603 7E A0 2C 21 25 54 19 2D E6 E6 00 C8 1E 30 00 00 01 99 2B 0E E2 56 79 05 EA D5 D6 22 1A ED 92 25 2C CC 91 28 64 02 67 C5 E5 3E E3 BC 04 7E 7E A0 0F 25 21 74 84 A2 E6 E7 00 D8 02 02 CF 5B 7E
Meter returns Service unknown exception. Service not supported

Hope that helps!

Kind regards
Florian

kurumi
kurumi's picture
Omnipower

Hi,

You are right. There was one issue on Gurux.DLMS.Net component that was causing this.
We have released new version from GXDLMSDirector and gurux.dlms.java.

Now parsing this is working also with GuruxDLMSTranslator.
http://www.gurux.fi/GuruxDLMSTranslator?pdu=61820029A1090607608574050801...

It's sad that your meter is not support glo-get-request. We have make some changes and try to release general-glo-ciphering for client side as soon as possible.

BR,

Mikko

________________________________________
Mikko Kurunsaari
Gurux Ltd
Hermiankatu 6-8 H 33720 TAMPERE, FINLAND
Phone: +358 3 265 1244
Home page: http://www.gurux.org

kurumi
kurumi's picture
Omnipower

Hi,

We have added support for general-glo-ciphering.
Data is correct, but because we do not have your meter you have to test this with your meter.

What you need to do:

1. Start GXDLMSDirector. It says that there is new version available.
2. Download latest version from GXDLMSDirector.
3. Make sure that "Security" is set on "Secured Connections" tab . In default that is None
4. Check "General protection" from "Supported Services" tab.

Let me know what happened.

BR,

Mikko

________________________________________
Mikko Kurunsaari
Gurux Ltd
Hermiankatu 6-8 H 33720 TAMPERE, FINLAND
Phone: +358 3 265 1244
Home page: http://www.gurux.org

flok
Hello!

Hello!

Here is the trace:
GXDLMSDirector 8.0.1710.1302
Log created 15:59:34
15:59:36 Initializing serial connection.
15:59:36 Send SNRM request.
7E A0 07 21 25 93 EC D0 7E
15:59:36 Received data
7E A0 07 21 25 93 EC D0 7E 7E A0 20 25 21 73 91 EB 81 80 14 05 02 00 80 06 02 00 80 07 04 00 00 00 01 08 04 00 00 00 01 CE 6A 7E
15:59:36 Parsing UA reply.<CR><LF>81 80 14 05 02 00 80 06 02 00 80 07 04 00 00 00 01 08 04 00 00 00 01
15:59:36 Parsing UA reply succeeded.
15:59:36
7E A0 6B 21 25 10 AF 68 E6 E6 00 60 5D A1 09 06 07 60 85 74 05 08 01 03 A6 0A 04 08 31 32 33 34 35 36 37 38 8A 02 07 80 8B 07 60 85 74 05 08 02 02 AC 12 80 10 0B 19 76 49 2A 5D 14 55 5D 42 41 4B 4F 15 2D 68 BE 23 04 21 21 1F 30 00 00 01 F9 1D B3 B5 BF 2A FE B0 6E E0 D2 2B C4 E9 CE 8F 7C 6B D3 1C 3F 00 45 EE B1 9D 6E F0 C8 7E
15:59:36 Received data
7E A0 6B 21 25 10 AF 68 E6 E6 00 60 5D A1 09 06 07 60 85 74 05 08 01 03 A6 0A 04 08 31 32 33 34 35 36 37 38 8A 02 07 80 8B 07 60 85 74 05 08 02 02 AC 12 80 10 0B 19 76 49 2A 5D 14 55 5D 42 41 4B 4F 15 2D 68 BE 23 04 21 21 1F 30 00 00 01 F9 1D B3 B5 BF 2A FE B0 6E E0 D2 2B C4 E9 CE 8F 7C 6B D3 1C 3F 00 45 EE B1 9D 6E F0 C8 7E 7E A0 2F 25 21 30 F7 29 E6 E7 00 61 82 00 1F A1 09 06 07 60 85 74 05 08 01 03 A2 03 02 01 01 A3 05 A1 03 02 01 0B BE 06 04 04 0E 01 06 00 D0 1C 7E
15:59:36 Disconnect request
Gurux.DLMS.GXDLMSException: Connection is permanently rejected. The authentication mechanism name is not recognized.
at GXDLMSDirector.GXDLMSDevice.InitializeConnection()
at GXDLMSDirector.MainForm.Connect(Control sender, Object[] parameters)

It seems that GXDLMSDirector sends 02 instead of 05 for the auth mechanism name.

Kind regards
Florian

kurumi
kurumi's picture
Omnipower

Hi,

Authentication level is now High. Change it to HighGMac. I update new settings for Kamstrup.
When you start GXDLMSDirector it will say that there are new settings available. Download them.

BR,

Mikko

________________________________________
Mikko Kurunsaari
Gurux Ltd
Hermiankatu 6-8 H 33720 TAMPERE, FINLAND
Phone: +358 3 265 1244
Home page: http://www.gurux.org

flok
Hello!

Hello!

Authentication now seems to work. But GetObjects fails:
07:55:56 Initializing serial connection.
07:55:56 Send SNRM request.
7E A0 07 21 25 93 EC D0 7E
07:55:56 Received data
7E A0 07 21 25 93 EC D0 7E 7E A0 20 25 21 73 91 EB 81 80 14 05 02 00 80 06 02 00 80 07 04 00 00 00 01 08 04 00 00 00 01 CE 6A 7E
07:55:56 Parsing UA reply.<CR><LF>81 80 14 05 02 00 80 06 02 00 80 07 04 00 00 00 01 08 04 00 00 00 01
07:55:56 Parsing UA reply succeeded.
07:55:56
7E A0 6B 21 25 10 AF 68 E6 E6 00 60 5D A1 09 06 07 60 85 74 05 08 01 03 A6 0A 04 08 31 32 33 34 35 36 37 38 8A 02 07 80 8B 07 60 85 74 05 08 02 05 AC 12 80 10 34 2C 1D 72 33 46 6E 15 2A 5B 50 55 54 1D 37 57 BE 23 04 21 21 1F 30 00 00 02 67 BB 2A CF E0 48 16 C7 E6 6B DA 5F 49 9A 5C CD C6 57 CE D7 B1 54 2A 54 53 95 E2 5F 35 7E
07:55:56 Received data
7E A0 6B 21 25 10 AF 68 E6 E6 00 60 5D A1 09 06 07 60 85 74 05 08 01 03 A6 0A 04 08 31 32 33 34 35 36 37 38 8A 02 07 80 8B 07 60 85 74 05 08 02 05 AC 12 80 10 34 2C 1D 72 33 46 6E 15 2A 5B 50 55 54 1D 37 57 BE 23 04 21 21 1F 30 00 00 02 67 BB 2A CF E0 48 16 C7 E6 6B DA 5F 49 9A 5C CD C6 57 CE D7 B1 54 2A 54 53 95 E2 5F 35 7E 7E A0 89 25 21 30 50 C0 E6 E7 00 61 82 00 79 A1 09 06 07 60 85 74 05 08 01 03 A2 03 02 01 00 A3 05 A1 03 02 01 0E A4 0A 04 08 4B 41 4D 45 01 AE DD 42 88 02 07 80 89 07 60 85 74 05 08 02 05 AA 22 80 20 CB E1 C3 8F 51 A7 C9 2D E9 9F 4A 8F 5E 4D 48 B3 99 EA CB B7 57 CA AF 67 B9 96 02 3D 2A 39 CF 5F BE 23 04 21 28 1F 30 00 00 01 A1 DB B5 5D 6D 0D DB 58 BF 22 E6 1F CB 01 B7 6C 47 85 CF 19 19 D9 39 1F 68 A6 43 AE DF 7E
07:55:56 Authenticating
7E A0 48 21 25 32 21 C0 E6 E6 00 DB 08 31 32 33 34 35 36 37 38 31 30 00 00 02 68 55 96 AC C4 FC 5C 5D C3 16 E7 C5 59 59 25 69 C3 4B C6 4C 48 0D 04 1B B8 7C D0 72 28 8B 7C 16 1A 11 F0 4E 94 1B FE 71 FE BC 29 97 5F 2E 92 7E
07:55:56 Received data
7E A0 48 21 25 32 21 C0 E6 E6 00 DB 08 31 32 33 34 35 36 37 38 31 30 00 00 02 68 55 96 AC C4 FC 5C 5D C3 16 E7 C5 59 59 25 69 C3 4B C6 4C 48 0D 04 1B B8 7C D0 72 28 8B 7C 16 1A 11 F0 4E 94 1B FE 71 FE BC 29 97 5F 2E 92 7E 7E A0 43 25 21 52 33 67 E6 E7 00 DB 08 4B 41 4D 45 01 AE DD 42 82 00 2A 30 00 00 01 A3 13 2F 18 A6 D3 FF F2 7C 50 21 E7 7E 6B D5 42 7B 2A 9C 75 11 78 01 6B AF E0 59 B3 1B 6E B1 74 B9 D7 52 49 B1 76 BD D6 7E
07:55:56 Parsing AARE reply succeeded.
07:55:58 --- Collecting objects. ---
07:55:58 Collecting objects
7E A0 35 21 25 54 DB 17 E6 E6 00 DB 08 31 32 33 34 35 36 37 38 1E 30 00 00 02 69 97 F4 79 21 EC AD E0 D3 28 19 0B E4 87 3C BF E5 10 8E 47 15 49 2C 8E 40 C6 51 ED 7E
Data send failed. Try to resend 1/3
Data send failed. Try to resend 2/3
08:00:28 Failed to receive reply from the device in given time.
7E A0 35 21 25 54 DB 17 E6 E6 00 DB 08 31 32 33 34 35 36 37 38 1E 30 00 00 02 69 97 F4 79 21 EC AD E0 D3 28 19 0B E4 87 3C BF E5 10 8E 47 15 49 2C 8E 40 C6 51 ED 7E 7E A8 89 25 21 64 D1 8E E6 E7 00 DB 08 4B 41 4D 45 01 AE DD 42 82 03 C5 30 00 00 01 A4 CD BA C6 D0 65 2D 7B 91 85 E2 7B 51 44 65 77 6B F5 8A C3 20 33 80 37 C0 B3 D1 DC E8 2D 6C 62 53 79 D8 99 F4 0E 65 B8 CE 2F 65 51 8B E2 FA 10 18 CE B3 7A AB C0 5D 11 D4 03 BB 2B A1 FA B5 B7 A0 41 4A EC A5 2C 30 4C B2 77 AD F2 A2 9B A6 BF A3 16 A7 6E 27 16 73 DB 0D 0F E4 F1 CF EB 28 16 B1 3D E0 5F 14 A8 3C 57 2C 65 C6 2C FC 3A 7E
08:00:28 Received data
7E A0 35 21 25 54 DB 17 E6 E6 00 DB 08 31 32 33 34 35 36 37 38 1E 30 00 00 02 69 97 F4 79 21 EC AD E0 D3 28 19 0B E4 87 3C BF E5 10 8E 47 15 49 2C 8E 40 C6 51 ED 7E 7E A8 89 25 21 64 D1 8E E6 E7 00 DB 08 4B 41 4D 45 01 AE DD 42 82 03 C5 30 00 00 01 A4 CD BA C6 D0 65 2D 7B 91 85 E2 7B 51 44 65 77 6B F5 8A C3 20 33 80 37 C0 B3 D1 DC E8 2D 6C 62 53 79 D8 99 F4 0E 65 B8 CE 2F 65 51 8B E2 FA 10 18 CE B3 7A AB C0 5D 11 D4 03 BB 2B A1 FA B5 B7 A0 41 4A EC A5 2C 30 4C B2 77 AD F2 A2 9B A6 BF A3 16 A7 6E 27 16 73 DB 0D 0F E4 F1 CF EB 28 16 B1 3D E0 5F 14 A8 3C 57 2C 65 C6 2C FC 3A 7E
System.Exception: GetObjects failed. Failed to receive reply from the device in given time.
at GXDLMSDirector.MainForm.ReadDevice(GXDLMSDevice dev)
at GXDLMSDirector.MainForm.Read(Control sender, Object[] parameters)
08:01:08 Send Keep Alive

08:01:48 Send Keep Alive

08:02:28 Send Keep Alive

Data send failed. Try to resend 1/3
08:03:08 Send Keep Alive

08:03:49 Send Keep Alive

Data send failed. Try to resend 2/3
08:04:28 Send Keep Alive

08:05:08 Send Keep Alive

08:05:38 Failed to receive reply from the device in given time.
08:05:38 Disconnect request
7E A0 07 21 25 53 E0 16 7E
08:06:37 Disconnect request

Kind regards
Florian

kurumi
kurumi's picture
Omnipower

Hi,

If you connect without ciphering and read association view, can you find Data object with Logical Name:
0.0.43.1.0.255?

BR,

Mikko

________________________________________
Mikko Kurunsaari
Gurux Ltd
Hermiankatu 6-8 H 33720 TAMPERE, FINLAND
Phone: +358 3 265 1244
Home page: http://www.gurux.org

flok
Hello!

Hello!

Without ciphering reading association view fails also:
GXDLMSDirector 8.0.1710.1302
Log created 09:57:32
09:57:34 Initializing serial connection.
09:57:34 Send SNRM request.
7E A0 07 03 21 93 0F 01 7E
09:57:34 Received data
7E A0 07 03 21 93 0F 01 7E 7E A0 20 21 03 73 73 98 81 80 14 05 02 00 80 06 02 00 80 07 04 00 00 00 01 08 04 00 00 00 01 CE 6A 7E
09:57:34 Parsing UA reply.<CR><LF>81 80 14 05 02 00 80 06 02 00 80 07 04 00 00 00 01 08 04 00 00 00 01
09:57:34 Parsing UA reply succeeded.
09:57:34
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
09:57:34 Received data
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 7E A0 39 21 03 30 2E D2 E6 E7 00 61 82 00 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 10 1D 03 EF 00 07 44 36 7E
09:57:34 Parsing AARE reply succeeded.
09:57:37 --- Collecting objects. ---
09:57:37 Collecting objects
7E A0 19 03 21 32 6F D8 E6 E6 00 C0 01 C1 00 0F 00 00 28 00 00 FF 02 00 91 53 7E
Data send failed. Try to resend 1/3
Data send failed. Try to resend 2/3
09:57:58 Failed to receive reply from the device in given time.
7E A0 19 03 21 32 6F D8 E6 E6 00 C0 01 C1 00 0F 00 00 28 00 00 FF 02 00 91 53 7E 7E A8 89 21 03 42 07 B9 E6 E7 00 C4 02 C1 00 00 00 00 01 00 82 00 88 01 19 02 04 12 00 0F 11 02 09 06 00 00 28 00 00 FF 02 02 01 0B 02 03 0F 01 16 01 00 02 03 0F 02 16 01 00 02 03 0F 03 16 01 00 02 03 0F 04 16 01 00 02 03 0F 05 16 01 00 02 03 0F 06 16 01 00 02 03 0F 07 16 00 00 02 03 0F 08 16 01 00 02 03 0F 09 16 01 00 02 03 0F 0A 16 01 00 02 03 0F 0B 16 01 00 01 06 02 02 0F 01 16 00 02 02 0F 02 16 00 02 62 6E 7E
09:57:58 Received data
7E A0 19 03 21 32 6F D8 E6 E6 00 C0 01 C1 00 0F 00 00 28 00 00 FF 02 00 91 53 7E 7E A8 89 21 03 42 07 B9 E6 E7 00 C4 02 C1 00 00 00 00 01 00 82 00 88 01 19 02 04 12 00 0F 11 02 09 06 00 00 28 00 00 FF 02 02 01 0B 02 03 0F 01 16 01 00 02 03 0F 02 16 01 00 02 03 0F 03 16 01 00 02 03 0F 04 16 01 00 02 03 0F 05 16 01 00 02 03 0F 06 16 01 00 02 03 0F 07 16 00 00 02 03 0F 08 16 01 00 02 03 0F 09 16 01 00 02 03 0F 0A 16 01 00 02 03 0F 0B 16 01 00 01 06 02 02 0F 01 16 00 02 02 0F 02 16 00 02 62 6E 7E
System.Exception: GetObjects failed. Failed to receive reply from the device in given time.
at GXDLMSDirector.MainForm.ReadDevice(GXDLMSDevice dev)
at GXDLMSDirector.MainForm.Read(Control sender, Object[] parameters)
09:58:26 Disconnect request
7E A0 07 03 21 53 03 C7 7E
09:58:26 Received data
7E A0 07 03 21 53 03 C7 7E 7E A0 07 21 03 1F 6B E9 7E
09:58:26 Unknown Error.

If it hepls: If I read the association view with another program I get following result:

Scanned addresses:
Address Description Access Mode Access Selector
ABSTRACT ASSOCIATION_LN
Attributes:
15/0.0.40.0.0.255/1 LOGICAL_NAME(1) READ_ONLY -
15/0.0.40.0.0.255/2 OBJECT_LIST(2) READ_ONLY -
15/0.0.40.0.0.255/3 ASSOCIATED_PARTNERS_ID(3) READ_ONLY -
15/0.0.40.0.0.255/4 APPLICATION_CONTEXT_NAME(4) READ_ONLY -
15/0.0.40.0.0.255/5 XDLMS_CONTEXT_INFO(5) READ_ONLY -
15/0.0.40.0.0.255/6 AUTHENTICATION_MECHANISM_NAME(6) READ_ONLY -
15/0.0.40.0.0.255/7 LLS_SECRET(7) NO_ACCESS -
15/0.0.40.0.0.255/8 ASSOCIATION_STATUS(8) READ_ONLY -
15/0.0.40.0.0.255/9 SECURITY_SETUP_REFERENCE(9) READ_ONLY -
15/0.0.40.0.0.255/10 10 READ_ONLY -
15/0.0.40.0.0.255/11 11 READ_ONLY -
Methods:
15/0.0.40.0.0.255/1 REPLY_TO_HLS_AUTHENTICATION NO_ACCESS
15/0.0.40.0.0.255/2 CHANGE_HLS_SECRET NO_ACCESS
15/0.0.40.0.0.255/3 ADD_OBJECT NO_ACCESS
15/0.0.40.0.0.255/4 REMOVE_OBJECT NO_ACCESS
15/0.0.40.0.0.255/5 NO_ACCESS
15/0.0.40.0.0.255/6 NO_ACCESS

ELECTRICITY DATA
Attributes:
1/1.1.0.0.1.255/1 LOGICAL_NAME(1) READ_ONLY -
1/1.1.0.0.1.255/2 VALUE(2) READ_ONLY -

ELECTRICITY DATA
Attributes:
1/1.1.0.0.2.255/1 LOGICAL_NAME(1) READ_ONLY -
1/1.1.0.0.2.255/2 VALUE(2) READ_ONLY -

ELECTRICITY DATA
Attributes:
1/1.1.0.0.3.255/1 LOGICAL_NAME(1) READ_ONLY -
1/1.1.0.0.3.255/2 VALUE(2) READ_ONLY -

ELECTRICITY DATA
Attributes:
1/1.1.96.1.0.255/1 LOGICAL_NAME(1) READ_ONLY -
1/1.1.96.1.0.255/2 VALUE(2) READ_ONLY -

ELECTRICITY DATA
Attributes:
1/1.1.0.0.0.255/1 LOGICAL_NAME(1) READ_ONLY -
1/1.1.0.0.0.255/2 VALUE(2) READ_ONLY -

ELECTRICITY DATA
Attributes:
1/1.1.96.54.1.255/1 LOGICAL_NAME(1) READ_ONLY -
1/1.1.96.54.1.255/2 VALUE(2) READ_ONLY -

ELECTRICITY DATA
Attributes:
1/1.1.96.1.1.255/1 LOGICAL_NAME(1) READ_ONLY -
1/1.1.96.1.1.255/2 VALUE(2) READ_ONLY -

ELECTRICITY DATA
Attributes:
1/1.1.0.0.5.255/1 LOGICAL_NAME(1) READ_ONLY -
1/1.1.0.0.5.255/2 VALUE(2) READ_ONLY -

ELECTRICITY DATA
Attributes:
1/1.1.0.2.0.255/1 LOGICAL_NAME(1) READ_ONLY -
1/1.1.0.2.0.255/2 VALUE(2) READ_ONLY -

ELECTRICITY DATA
Attributes:
1/1.1.96.58.15.255/1 LOGICAL_NAME(1) READ_ONLY -
1/1.1.96.58.15.255/2 VALUE(2) READ_ONLY -

ELECTRICITY DATA
Attributes:
1/1.1.96.58.19.255/1 LOGICAL_NAME(1) READ_ONLY -
1/1.1.96.58.19.255/2 VALUE(2) READ_ONLY -

ELECTRICITY DATA
Attributes:
1/1.1.0.0.4.255/1 LOGICAL_NAME(1) READ_ONLY -
1/1.1.0.0.4.255/2 VALUE(2) READ_ONLY -

ELECTRICITY DATA
Attributes:
1/1.1.96.58.20.255/1 LOGICAL_NAME(1) READ_ONLY -
1/1.1.96.58.20.255/2 VALUE(2) READ_ONLY -

ELECTRICITY DATA
Attributes:
1/1.1.96.58.4.255/1 LOGICAL_NAME(1) READ_ONLY -
1/1.1.96.58.4.255/2 VALUE(2) READ_ONLY -

ELECTRICITY DATA
Attributes:
1/1.1.96.58.16.255/1 LOGICAL_NAME(1) READ_ONLY -
1/1.1.96.58.16.255/2 VALUE(2) READ_ONLY -

ELECTRICITY DATA
Attributes:
1/1.1.134.0.30.255/1 LOGICAL_NAME(1) READ_ONLY -
1/1.1.134.0.30.255/2 VALUE(2) READ_AND_WRITE -

ELECTRICITY DATA
Attributes:
1/1.1.97.97.0.255/1 LOGICAL_NAME(1) READ_ONLY -
1/1.1.97.97.0.255/2 VALUE(2) READ_ONLY -

ABSTRACT DATA
Attributes:
1/0.2.43.1.1.255/1 LOGICAL_NAME(1) READ_ONLY -
1/0.2.43.1.1.255/2 VALUE(2) READ_ONLY -

ABSTRACT DATA
Attributes:
1/0.1.43.1.1.255/1 LOGICAL_NAME(1) READ_ONLY -
1/0.1.43.1.1.255/2 VALUE(2) READ_AND_WRITE -

ABSTRACT CLOCK
Attributes:
8/0.1.1.0.0.255/1 LOGICAL_NAME(1) READ_ONLY -
8/0.1.1.0.0.255/2 TIME(2) READ_ONLY -
8/0.1.1.0.0.255/3 TIME_ZONE(3) NO_ACCESS -
8/0.1.1.0.0.255/4 STATUS(4) READ_ONLY -
8/0.1.1.0.0.255/5 DAYLIGHT_SAVINGS_BEGIN(5) READ_ONLY -
8/0.1.1.0.0.255/6 DAYLIGHT_SAVINGS_END(6) READ_ONLY -
8/0.1.1.0.0.255/7 DAYLIGHT_SAVINGS_DEVIATION(7) READ_ONLY -
8/0.1.1.0.0.255/8 DAYLIGHT_SAVINGS_ENABLED(8) READ_ONLY -
8/0.1.1.0.0.255/9 CLOCK_BASE(9) READ_ONLY -

ABSTRACT SAP_ASSIGNMENT
Attributes:
17/0.0.41.0.0.255/1 LOGICAL_NAME(1) READ_ONLY -
17/0.0.41.0.0.255/2 SAP_ASSIGNMENT_LIST(2) READ_ONLY -

ABSTRACT IEC_HDLC_SETUP_CLASS
Attributes:
23/0.0.22.0.0.255/1 LOGICAL_NAME(1) READ_ONLY -
23/0.0.22.0.0.255/2 COMM_SPEED(2) READ_ONLY -
23/0.0.22.0.0.255/3 WINDOW_SIZE_TRANSMIT(3) READ_ONLY -
23/0.0.22.0.0.255/4 WINDOW_SIZE_RECEIVE(4) READ_ONLY -
23/0.0.22.0.0.255/5 MAX_INFO_FIELD_LENGTH_TRANSMIT(5) READ_ONLY -
23/0.0.22.0.0.255/6 MAX_INFO_FIELD_LENGTH_RECEIVE(6) READ_ONLY -
23/0.0.22.0.0.255/7 INTER_OCTET_TIME_OUT(7) READ_ONLY -
23/0.0.22.0.0.255/8 INACTIVITY_TIME_OUT(8) READ_ONLY -
23/0.0.22.0.0.255/9 DEVICE_ADDRESS(9) READ_ONLY -

ABSTRACT SECURITY_SETUP
Attributes:
64/0.0.43.0.1.255/1 LOGICAL_NAME(1) READ_ONLY -
64/0.0.43.0.1.255/2 SECURITY_POLICY(2) READ_ONLY -
64/0.0.43.0.1.255/3 SECURITY_SUITE(3) READ_ONLY -
64/0.0.43.0.1.255/4 CLIENT_SYSTEM_TITLE(4) NO_ACCESS -
64/0.0.43.0.1.255/5 SERVER_SYSTEM_TITLE(5) READ_ONLY -
Methods:
64/0.0.43.0.1.255/1 SECURITY_ACTIVATE NO_ACCESS
64/0.0.43.0.1.255/2 GLOBALE_KEY_TRANSFER NO_ACCESS

ABSTRACT SECURITY_SETUP
Attributes:
64/0.0.43.0.0.255/1 LOGICAL_NAME(1) READ_ONLY -
64/0.0.43.0.0.255/2 SECURITY_POLICY(2) READ_ONLY -
64/0.0.43.0.0.255/3 SECURITY_SUITE(3) READ_ONLY -
64/0.0.43.0.0.255/4 CLIENT_SYSTEM_TITLE(4) NO_ACCESS -
64/0.0.43.0.0.255/5 SERVER_SYSTEM_TITLE(5) READ_ONLY -
Methods:
64/0.0.43.0.0.255/1 SECURITY_ACTIVATE NO_ACCESS
64/0.0.43.0.0.255/2 GLOBALE_KEY_TRANSFER NO_ACCESS

The request for the association view in this program is the following:
7E A0 19 03 21 32 6F D8 E6 E6 00 C0 01 41 00 0F 00 00 28 00 00 FF 02 00 8A C1 7E

Hope that helps,
Florian

kurumi
kurumi's picture
Omnipower

Hi,

Contact to meter manufacturer. HDLC frame ID is wrong when you connect without authentication.
Data to send:
7E A0 19 03 21 32 6F D8 E6 E6 00 C0 01 C1 00 0F 00 00 28 00 00 FF 02 00 91 53 7E
Reply:

7E A8 89 21 03
42 //HDLC Frame ID is wrong! It should be 52.

This frame is skipped. You can fix this if you you find CheckFrame from settings.java and don't check frame id. Just return true in first line.

BR,

Mikko

________________________________________
Mikko Kurunsaari
Gurux Ltd
Hermiankatu 6-8 H 33720 TAMPERE, FINLAND
Phone: +358 3 265 1244
Home page: http://www.gurux.org

flok
Hello!

Hello!

My other program sends the following to read association view:
7E A0 19 03 21 32 6F D8 E6 E6 00 C0 01 41 00 0F 00 00 28 00 00 FF 02 00 8A C1 7E

And then the meter returns:
7E A0 A0 21 03 52 96 85 E6 E7 00 C4 02 41 00 00 00 00 01 00 82 00 88 01 19 02 04 12 00 0F 11 02 09 06 00 00 28 00 00 FF 02 02 01 0B 02 03 0F 01 16 01 00 02 03 0F 02 16 01 00 02 03 0F 03 16 01 00 02 03 0F 04 16 01 00 02 03 0F 05 16 01 00 02 03 0F 06 16 01 00 02 03 0F 07 16 00 00 02 03 0F 08 16 01 00 02 03 0F 09 16 01 00 02 03 0F 0A 16 01 00 02 03 0F 0B 16 01 00 01 06 02 02 0F 01 16 00 02 02 0F 02 16 00 02 02 0F 03 16 00 02 02 0F 04 16 00 02 02 0F 05 16 00 02 02 0F 06 16 00 26 3F 7E

Which seems to have the right frame ID. Could it be that the association view read request from DlmsDirector has to be modified?

Kind regards
Florian

kurumi
kurumi's picture
Omnipower

Hi,

In that reply HDLC frame is correct. What you have modified?

BR,

Mikko

________________________________________
Mikko Kurunsaari
Gurux Ltd
Hermiankatu 6-8 H 33720 TAMPERE, FINLAND
Phone: +358 3 265 1244
Home page: http://www.gurux.org

flok
Hello!

Hello!

I didn't modify anything. This is from my other test-program. You can see the result of the association view in post #21.

Here is the complete trace:
Source: CLIENT
Message: 7E A0 20 03 21 93 7D D9 81 80 14 05 02 07 EE 06 02 07 EE 07 04 00 00 00 01 08 04 00 00 00 01 B5 D4 7E

Source: SERVER
Message: 7E A0 20 21 03 73 73 98 81 80 14 05 02 03 F2 06 02 03 F2 07 04 00 00 00 01 08 04 00 00 00 01 0A 75 7E

Source: CLIENT
Message: 7E A0 34 03 21 10 A3 DE E6 E6 00 60 26 A1 09 06 07 60 85 74 05 08 01 01 8B 07 60 85 74 05 08 02 00 BE 10 04 0E 01 00 00 00 06 5F 1F 04 00 00 18 1D FF FF 13 ED 7E

Source: SERVER
Message: 7E A0 39 21 03 30 2E D2 E6 E7 00 61 82 00 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 10 1D 03 EF 00 07 44 36 7E

Source: CLIENT
Message: 7E A0 19 03 21 32 6F D8 E6 E6 00 C0 01 41 00 0F 00 00 28 00 00 FF 02 00 8A C1 7E

Source: SERVER
Message: 7E A0 A0 21 03 52 96 85 E6 E7 00 C4 02 41 00 00 00 00 01 00 82 00 88 01 19 02 04 12 00 0F 11 02 09 06 00 00 28 00 00 FF 02 02 01 0B 02 03 0F 01 16 01 00 02 03 0F 02 16 01 00 02 03 0F 03 16 01 00 02 03 0F 04 16 01 00 02 03 0F 05 16 01 00 02 03 0F 06 16 01 00 02 03 0F 07 16 00 00 02 03 0F 08 16 01 00 02 03 0F 09 16 01 00 02 03 0F 0A 16 01 00 02 03 0F 0B 16 01 00 01 06 02 02 0F 01 16 00 02 02 0F 02 16 00 02 02 0F 03 16 00 02 02 0F 04 16 00 02 02 0F 05 16 00 02 02 0F 06 16 00 26 3F 7E

[...]

Kind regards
Florian

kurumi
kurumi's picture
Omnipower

Hi,

Try to change
cl.Limits.MaxInfoRX = cl.Limits.MaxInfoTX = 1010;

Send data is same with both apps.

BR,

Mikko

________________________________________
Mikko Kurunsaari
Gurux Ltd
Hermiankatu 6-8 H 33720 TAMPERE, FINLAND
Phone: +358 3 265 1244
Home page: http://www.gurux.org

flok
Hello!

Hello!
My last message got blocked. The new limits fixed the issue but I still get an invalid response. I can't include the trace so I created a github gist where you can see it: https://gist.github.com/anonymous/ad149859bb223697aced12c6390c868b
Kind regards
Florian

kurumi
kurumi's picture
Omnipower

Hi,

We added support for IEC HDLC setup Versio 1.
Currrent implementation is for Version 0.

http://www.gurux.fi/node/6339

This caused that we can't use so large HDLC frame size what your meter wants and it seems that
your meter can't operate with smaller HDLC frame size.

We release new version from C# code today and for Java for next week.

BR,

Mikko

________________________________________
Mikko Kurunsaari
Gurux Ltd
Hermiankatu 6-8 H 33720 TAMPERE, FINLAND
Phone: +358 3 265 1244
Home page: http://www.gurux.org

flok
Hello!

Hello!

Thank you for your great support. So in this new version will my association view problem be fixed? Will this also fix my HLS5 problem?

Thank you
Florian

kurumi
kurumi's picture
Omnipower

Hi,

We are fixing Omnipower issues here, so I don't know. Can you get latest version from C# and try with that and let me know. We do not have Omnipower on the office so I can't test it. We must go step by step until it works.

BR,

Mikko

________________________________________
Mikko Kurunsaari
Gurux Ltd
Hermiankatu 6-8 H 33720 TAMPERE, FINLAND
Phone: +358 3 265 1244
Home page: http://www.gurux.org

kurumi
kurumi's picture
Omnipower

Note!
It seems that this is critical.
cl.Limits.MaxInfoRX = cl.Limits.MaxInfoTX = 1010;

BR,

Mikko

________________________________________
Mikko Kurunsaari
Gurux Ltd
Hermiankatu 6-8 H 33720 TAMPERE, FINLAND
Phone: +358 3 265 1244
Home page: http://www.gurux.org

flok
Hello!

Hello!
I tried with the latest C# version from https://github.com/Gurux/Gurux.DLMS.Net

It also failed with "invalid response":
https://gist.github.com/knogi/f3d4853b936164882e5ed653498e7b61

Kind regards
Florian

flok
Hello!

Hello!
I saw that you released a new .net version this morning. With this version I can read the association view without any error. But I have to set MaxInfoRX and MaxInfoTX to 1010.
Kind regards
Florian

kurumi
kurumi's picture
Omnipower

Hi,

Your meter is very special case. We have made changes to cpp and java codes so you can also read your meter with them. We are releasing new versions today.

BR,

Mikko

________________________________________
Mikko Kurunsaari
Gurux Ltd
Hermiankatu 6-8 H 33720 TAMPERE, FINLAND
Phone: +358 3 265 1244
Home page: http://www.gurux.org

flok
Hello!

Hello!

I tested the secured connection with the .net example application. I had to modify GXDLMSClient.GetInitialConformance to add support for Conformance.GeneralProtection but now I can read registers and read/write date using a secured connection.

Thank you very much!
Florian

kurumi
kurumi's picture
Omnipower

Hi,

Do it like this:

client.ProposedConformance |= Conformance.GeneralProtection;

and for Java like this:

client.getProposedConformance().add(Conformance.GENERAL_PROTECTION);

We can't add that to the default because some meters can't handle GeneralProtection flag.

BR,

Mikko

________________________________________
Mikko Kurunsaari
Gurux Ltd
Hermiankatu 6-8 H 33720 TAMPERE, FINLAND
Phone: +358 3 265 1244
Home page: http://www.gurux.org