Hello!
I try to establish a HLS6 connection to a meter. At the moment pass 1 and 2 are working but pass 3 (call method reply_to_HLS_authentication) is not working because the meter seems to require a "glo action request" (0xCB) instead of an "action request" (0xC3).
Is it possible to use a glo action request for this step?
I have a working trace for this meter. Below is the part of the method call and its response:
request: 7E A0 4F 02 23 0B 32 83 FF E6 E6 00 CB 40 31 00 00 00 A4 03 D9 06 FF 18 62 F0 48 BB 88 B7 5C 50 69 E3 12 2D 17 23 92 E3 95 F6 3E 68 BD 0B 4B 37 F5 DB 1F 2E E1 C1 DF E4 03 F8 57 61 A1 0F 14 14 6E 5F 02 9D 01 F0 03 E4 AC 2E 64 2B 46 A8 2E 9A 7E
response: 7E A0 48 0B 02 23 52 2E E1 E6 E7 00 CF 39 31 00 00 00 56 B3 07 96 7F 2A 5F 54 37 C0 C6 86 A0 11 9B 43 34 5C E1 5A 9C 4B 81 7A 4E FE 58 89 C7 0F 3C 93 BA 83 F0 34 F8 F2 CA 03 2E B1 00 F2 37 B1 AB DF 1E 28 7D 04 DF D3 54 7E
I set up GXDLMSDirector for my meter. I changed some properties (security setup, max payload) and the trace now looks similar to the trace manufacturer's software trace (see above):
One difference is the security control byte. In the manufacturer's trace it is 31 (Authentication + Encryption + Security Suite 1). GXDLMSDirector used 30.
I'm not sure where to put my keys in GXDLMSDirector. Authentication and encryption key are clear, but where to put HLS secret?
Is it possible to configure security suite in GXDLMSDirector? In my own app i set security suite to security 1 but the security control byte is still 0x30.
Can I repeat the question?
Can I repeat the question?
kind regards
Florian
Establishing a HLS6 connection
Hi,
I'm sorry. For some reason, I did not notice this email.
Your message is glo_action. Is data encrypted correctly? Are you sure that authentication is HLS6 (HighSHA256)?
http://www.gurux.fi/GuruxDLMSTranslator?translate=7EA04F02230B3283FFE6E…
BR,
Mikko
Hello!
Hello!
Yes, authentication should be HLS6. I have a trace of a manufacturer's software: https://gist.github.com/knogi/d64dec10f26930620952d6247d7521bd
In the third send-step (which should be the reply_to_hls_authentication method call) it seems that a glo action request is sent. My gurux program seems to use an action request: https://gist.github.com/knogi/6e641bc3564da4695541e3f071da08f2
I'm not sure if that is the problem, but maybe you have an idea?
Kind regards
Florian
Establishing a HLS6 connection
Hi,
We'll check this. Are you using GXDLMSDirector?
BR,
Mikko
Hello!
Hello!
Not at the moment, but if it helps I'll try to configure my meter in GXDLMSDirector.
Kind regards
Florian
Establishing a HLS6 connection
Hi,
Use GXDLMSDirector first. It's easier to see what parameters you are using, etc.
BR,
Mikko
Hello!
Hello!
I set up GXDLMSDirector for my meter. I changed some properties (security setup, max payload) and the trace now looks similar to the trace manufacturer's software trace (see above):
https://gist.github.com/knogi/63440022f78bf415e14f8b717ddcae54
One difference is the security control byte. In the manufacturer's trace it is 31 (Authentication + Encryption + Security Suite 1). GXDLMSDirector used 30.
I'm not sure where to put my keys in GXDLMSDirector. Authentication and encryption key are clear, but where to put HLS secret?
Kind regards
Florian
Establishing a HLS6 connection
Hi,
0x31 is Security Suite 1. 0x30 is Security Suite 0. HLS secret is password.
BR,
Mikko
Hallo!
Hallo!
Can this be a problem?
Is it possible to configure security suite in GXDLMSDirector? In my own app i set security suite to security 1 but the security control byte is still 0x30.
Kind regards
Florian