Invalid password: Server to Client challenge do not match

By zeus8497st , 27 December, 2022

Forums

Hi, hope you are doing well.I use Dlms director to connect with my kaifa Am206d, in order to get access to secured data by setting the authentication to highGMAC and using encryption and authentication key.The point is when i start the connection, all parameters from AARQ and aare are guaranteed but i struggle to to pass the invoke reply to hls authentication method with this error."Invalid password: Server to Client challenge do not match". may i get your help
here i share with you the log file.

GXDLMSDirector 8.1.2109.3001
10:11:32 Initializing serial connection.
10:11:32 10:11:32.093 Info Opening
10:11:32 10:11:32.093 Info Paramètres du port série: Nom du port: COM4 Vitesse de transmission: 300 Bits de données: 7 Parité: Even Bits d'arrêt: One Contrôle de flux: None Eop: None
10:11:32 10:11:32.108 Info Open
10:11:33 IEC Sending:/?!<CR><LF>
10:11:33 10:11:33.124 Sent 2F 3F 21 0D 0A
10:11:38 Disconnect request
10:11:38 10:11:38.129 Sent 7E A0 08 02 01 61 53 54 52 7E
10:11:43 Failed to receive reply from the device in given time.
10:11:43 10:11:43.136 Sent 01 42 30 03 0D 0A
10:11:48 Failed to receive reply from the device in given time.
10:11:48 10:11:48.140 Sent 2F 3F 21 0D 0A
10:11:53 10:11:53.156 Info Closing
10:11:53 10:11:53.265 Info Closed
System.Exception: Failed to receive reply from the device in given time.
à GXDLMSDirector.GXDLMSCommunicator.InitSerial()
à GXDLMSDirector.GXDLMSCommunicator.InitializeConnection(Boolean force)
à GXDLMSDirector.GXDLMSDevice.InitializeConnection()
à GXDLMSDirector.MainForm.Connect(Object sender, GXAsyncWork work, Object[] parameters)
10:12:49 Initializing serial connection.
10:12:49 10:12:49.484 Info Opening
10:12:49 10:12:49.484 Info Paramètres du port série: Nom du port: COM4 Vitesse de transmission: 300 Bits de données: 7 Parité: Even Bits d'arrêt: One Contrôle de flux: None Eop: None
10:12:49 10:12:49.499 Info Open
10:12:50 IEC Sending:/?!<CR><LF>
10:12:50 10:12:50.515 Sent 2F 3F 21 0D 0A
10:12:50 10:12:50.843 Received 3F 3F 2F
10:12:50 10:12:50.874 Received 2F
10:12:50 10:12:50.905 Received 4B
10:12:50 10:12:50.937 Received 46
10:12:50 10:12:50.984 Received 4D
10:12:51 10:12:51.015 Received 36
10:12:51 10:12:51.046 Received 5C
10:12:51 10:12:51.093 Received 32
10:12:51 10:12:51.124 Received 4B
10:12:51 10:12:51.156 Received 61
10:12:51 10:12:51.204 Received 69
10:12:51 10:12:51.235 Received 66
10:12:51 10:12:51.267 Received 61
10:12:51 10:12:51.298 Received 20
10:12:51 10:12:51.345 Received 54
10:12:51 10:12:51.376 Received 65
10:12:51 10:12:51.407 Received 63
10:12:51 10:12:51.454 Received 68
10:12:51 10:12:51.485 Received 6E
10:12:51 10:12:51.517 Received 6F
10:12:51 10:12:51.564 Received 6C
10:12:51 10:12:51.610 Received 6F
10:12:51 10:12:51.642 Received 67
10:12:51 10:12:51.673 Received 79
10:12:51 10:12:51.720 Received 0D
10:12:51 HDLC received: /KFM6\2Kaifa Technology<CR><LF>
10:12:51 Maximum BaudRate is set to : 9600
10:12:51 BaudRate is : 9600
10:12:51 Moving to mode E.
06 32 35 32 0D 0A
10:12:51 10:12:51.720 Sent 06 32 35 32 0D 0A
10:12:53 10:12:53.736 Info Closing
10:12:53 10:12:53.861 Info Closed
10:12:53 10:12:53.861 Info Opening
10:12:53 10:12:53.861 Info Paramètres du port série: Nom du port: COM4 Vitesse de transmission: 9600 Bits de données: 8 Parité: None Bits d'arrêt: One Contrôle de flux: None Eop: None
10:12:53 10:12:53.876 Info Open
10:12:54 Send SNRM request.
7E A0 08 02 01 61 93 58 94 7E
10:12:54 10:12:54.892 Sent 7E A0 08 02 01 61 93 58 94 7E
10:12:54 10:12:54.939 Received 7E A0 21 61 02 01 73 BB
10:12:54 10:12:54.954 Received BB 74 81 80 14 05 02
10:12:54 10:12:54.970 Received 04 00 00 00 01 08 04 00 00 00 01 CE 6A
10:12:54
7E A0 21 61 02 01 73 BB 74 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
10:12:54 Parsing UA reply succeeded.
10:12:54 Send AARQ request.
7E A0 6C 02 01 61 10 68 AE E6 E6 00 60 5D A1 09 06 07 60 85 74 05 08 01 03 A6 0A 04 08 4D 4D 4D 00 00 BC 61 4E 8A 02 07 80 8B 07 60 85 74 05 08 02 05 AC 12 80 10 3B 5E 68 3D 04 3B 68 41 2D 49 67 5D 1D 75 66 09 BE 23 04 21 21 1F 30 00 00 00 00 72 1F 00 8D 3B FB 8F 9C 0B 93 C7 B9 70 FD 10 FE B7 86 44 14 9C 17 E6 21 EF F6 48 55 7E
10:12:54 10:12:54.970 Sent 7E A0 6C 02 01 61 10 68 AE E6 E6 00 60 5D A1 09 06 07 60 85 74 05 08 01 03 A6 0A 04 08 4D 4D 4D 00 00 BC 61 4E 8A 02 07 80 8B 07 60 85 74 05 08 02 05 AC 12 80 10 3B 5E 68 3D 04 3B 68 41 2D 49 67 5D 1D 75 66 09 BE 23 04 21 21 1F 30 00 00 00 00 72 1F 00 8D 3B FB 8F 9C 0B 93 C7 B9 70 FD 10 FE B7 86 44 14 9C 17 E6 21 EF F6 48 55 7E
10:12:55 10:12:55.158 Received 7E A0
10:12:55 10:12:55.173 Received A0 78 61 02 01 30 22 20 E6 E7 00 61
10:12:55 10:12:55.189 Received A1 09 06 07 60 85 74 05 08 01 03 A2 03 02
10:12:55 10:12:55.204 Received 01 00 A3 05 A1 03 02 01 0E 89 07 60 85 74
10:12:55 10:12:55.220 Received 05 08 02 05 A4 0A 04 08 4D 4D 4D 00 00 BC
10:12:55 10:12:55.235 Received 61 4E 88 02 07 80 AA 12 80 10 7B 1E 8D 6D
10:12:55 10:12:55.251 Received B2 BF 4F 4C E8 60 12 2B 1F 02 D5 09 BE 23
10:12:55 10:12:55.267 Received 04 21 28 1F 30 00 00 00 01 D5 14 81 8B 29
10:12:55 10:12:55.283 Received CE CF 7A 74 8A 9F F7 F2 2E 8E 68 F6 50 F5
10:12:55 10:12:55.298 Received 21 63 69 47 AE 0A FF 39 26
10:12:55
7E A0 78 61 02 01 30 22 20 E6 E7 00 61 69 A1 09 06 07 60 85 74 05 08 01 03 A2 03 02 01 00 A3 05 A1 03 02 01 0E 89 07 60 85 74 05 08 02 05 A4 0A 04 08 4D 4D 4D 00 00 BC 61 4E 88 02 07 80 AA 12 80 10 7B 1E 8D 6D B2 BF 4F 4C E8 60 12 2B 1F 02 D5 09 BE 23 04 21 28 1F 30 00 00 00 01 D5 14 81 8B 29 CE CF 7A 74 8A 9F F7 F2 2E 8E 68 F6 50 F5 21 63 69 47 AE 0A FF 39 26 7E
10:12:55 Parsing AARE reply succeeded.
10:12:55 Authenticating.
7E A0 40 02 01 61 32 D9 BB E6 E6 00 CB 31 30 00 00 00 01 1E 15 46 D4 39 CA CF 52 6E 97 62 F6 F3 20 2D 33 6B 34 32 3F 56 ED 0B 97 32 08 54 F0 69 03 43 B9 4E F5 D4 EE 1B D1 64 71 84 D2 57 F6 13 C4 7E
10:12:55 10:12:55.314 Sent 7E A0 40 02 01 61 32 D9 BB E6 E6 00 CB 31 30 00 00 00 01 1E 15 46 D4 39 CA CF 52 6E 97 62 F6 F3 20 2D 33 6B 34 32 3F 56 ED 0B 97 32 08 54 F0 69 03 43 B9 4E F5 D4 EE 1B D1 64 71 84 D2 57 F6 13 C4 7E
10:12:55 10:12:55.439 Received 7E A0 39 61 02 01
10:12:55 10:12:55.455 Received 01 52 50 AA E6 E7 00 CF 2A
10:12:55 10:12:55.470 Received AD 0E 36 1D D3 19 51 78 6A BE F6 6C 45 F9
10:12:55 10:12:55.486 Received 85 7B 7A 45 A6 E0 B8 F1 98 CD 39 8F B2 C2
10:12:55 10:12:55.501 Received A1 7A 93 FB 81 98 FF E7 BC FB 0C
10:12:55
7E A0 39 61 02 01 52 50 AA E6 E7 00 CF 2A 30 00 00 00 02 AD 0E 36 1D D3 19 51 78 6A BE F6 6C 45 F9 85 7B 7A 45 A6 E0 B8 F1 98 CD 39 8F B2 C2 A1 7A 93 FB 81 98 FF E7 BC FB 0C 7E
10:12:55 10:12:55.501 Sent 01 42 30 03 0D 0A
10:13:00 10:13:00.503 Info Closing
10:13:00 10:13:00.612 Info Closed
Gurux.DLMS.GXDLMSException: Invalid password. Server to Client challenge do not match.
à Gurux.DLMS.GXDLMSClient.ParseApplicationAssociationResponse(GXByteBuffer reply)
à GXDLMSDirector.GXDLMSCommunicator.InitializeConnection(Boolean force)
à GXDLMSDirector.GXDLMSDevice.InitializeConnection()
à GXDLMSDirector.MainForm.Connect(Object sender, GXAsyncWork work, Object[] parameters)

BlockCipher key: 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
Authentication Key:D0 D1 D2 D3 D4 D5 D6 D7 D8 D9 DA DB DC DD DE DF
1: 7E A0 08 02 01 61 93 58 94 7E
<HDLC len="A" >

<TargetAddress Value="80" />
<SourceAddress Value="30" />

<FrameType Value="93" />
<Snrm>
</Snrm>
</HDLC>
2: 7E A0 21 61 02 01 73 BB 74 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
<HDLC len="20" >
<TargetAddress Value="30" />

<SourceAddress Value="80" />

<FrameType Value="73" />
<PDU>
<Ua>
<MaxInfoTX Value="128" />
<MaxInfoRX Value="128" />
<WindowSizeTX Value="1" />
<WindowSizeRX Value="1" />
</Ua>
</PDU>
</HDLC>
3: 7E A0 6C 02 01 61 10 68 AE E6 E6 00 60 5D A1 09 06 07 60 85 74 05 08 01 03 A6 0A 04 08 4D 4D 4D 00 00 BC 61 4E 8A 02 07 80 8B 07 60 85 74 05 08 02 05 AC 12 80 10 3B 5E 68 3D 04 3B 68 41 2D 49 67 5D 1D 75 66 09 BE 23 04 21 21 1F 30 00 00 00 00 72 1F 00 8D 3B FB 8F 9C 0B 93 C7 B9 70 FD 10 FE B7 86 44 14 9C 17 E6 21 EF F6 48 55 7E
<HDLC len="6B" >

<TargetAddress Value="80" />
<SourceAddress Value="30" />

<FrameType Value="10" />
<PDU>
<AssociationRequest>
<ApplicationContextName Value="LN_WITH_CIPHERING" />
<CallingAPTitle Value="4D4D4D0000BC614E" />
<SenderACSERequirements Value="1" />
<MechanismName Value="HighGMAC" />
<CallingAuthentication Value="3B5E683D043B68412D49675D1D756609" />

<glo_InitiateRequest Value="3000000000721F008D3BFB8F9C0B93C7B970FD10FEB78644149C17E621EFF6" />
</AssociationRequest>
</PDU>
</HDLC>
4: 7E A0 78 61 02 01 30 22 20 E6 E7 00 61 69 A1 09 06 07 60 85 74 05 08 01 03 A2 03 02 01 00 A3 05 A1 03 02 01 0E 89 07 60 85 74 05 08 02 05 A4 0A 04 08 4D 4D 4D 00 00 BC 61 4E 88 02 07 80 AA 12 80 10 7B 1E 8D 6D B2 BF 4F 4C E8 60 12 2B 1F 02 D5 09 BE 23 04 21 28 1F 30 00 00 00 01 D5 14 81 8B 29 CE CF 7A 74 8A 9F F7 F2 2E 8E 68 F6 50 F5 21 63 69 47 AE 0A FF 39 26 7E
<HDLC len="77" >
<TargetAddress Value="30" />

<SourceAddress Value="80" />

<FrameType Value="30" />
<PDU>
<AssociationResponse>
<ApplicationContextName Value="LN_WITH_CIPHERING" />
<AssociationResult Value="00" />
<ResultSourceDiagnostic>

<ACSEServiceUser Value="0E" />
</ResultSourceDiagnostic>
<MechanismName Value="HighGMAC" />

<RespondingAPTitle Value="4D4D4D0000BC614E" />
<ResponderACSERequirement Value="1" />
<RespondingAuthentication Value="7B1E8D6DB2BF4F4CE860122B1F02D509" />

<glo_InitiateResponse Value="3000000001D514818B29CECF7A748A9FF7F22E8E68F650F521636947AE0AFF" />
</AssociationResponse>
</PDU>
</HDLC>
5 :7E A0 40 02 01 61 32 D9 BB E6 E6 00 CB 31 30 00 00 00 01 1E 15 46 D4 39 CA CF 52 6E 97 62 F6 F3 20 2D 33 6B 34 32 3F 56 ED 0B 97 32 08 54 F0 69 03 43 B9 4E F5 D4 EE 1B D1 64 71 84 D2 57 F6 13 C4 7E
<HDLC len="3F" >

<TargetAddress Value="80" />
<SourceAddress Value="30" />
<FrameType Value="32" />
<PDU>


<glo_ActionRequest Value="30000000011E1546D439CACF526E9762F6F3202D336B34323F56ED0B97320854F0690343B94EF5D4EE1BD1647184D257F6" />
</PDU>
</HDLC>
6: 7E A0 39 61 02 01 52 50 AA E6 E7 00 CF 2A 30 00 00 00 02 AD 0E 36 1D D3 19 51 78 6A BE F6 6C 45 F9 85 7B 7A 45 A6 E0 B8 F1 98 CD 39 8F B2 C2 A1 7A 93 FB 81 98 FF E7 BC FB 0C 7E
<HDLC len="38" >
<TargetAddress Value="30" />

<SourceAddress Value="80" />
<FrameType Value="52" />
<PDU>
<glo_ActionResponse Value="3000000002AD0E361DD31951786ABEF66C45F9857B7A45A6E0B8F198CD398FB2C2A17A93FB8198FFE7BC" />
</PDU>
</HDLC>

thanks in advance

Image

here is the setting for

here is the setting for security parameters.

Image

Hi,

The server challenge is invalid. You need to ask firmware update from the meter vendor where this is fixed.
Authentication key: C018AE45B37DAE665486F4151E0C1E6F
Client challenge: 3B5E683D043B68412D49675D1D756609
Invocation Counter: 2
Challenge that meter returns: 10 00 00 00 02 86 2F 07 9F 5E E0 09 9D 02 B0 95 90
Correct meter challenge: 10 00 00 00 02 06 CC 89 A0 2F 9C EE B1 06 C6 06 B8

BR,
Mikko

Hi thanks for your kick reply

Hi thanks for your kick reply.
Is there anyway to compel the meter to send the right value or not to simply check the f(CtoS) by changing the system title to 0x00000000 or something else ?
By the way, how do you found the correct meter challenge? Can you share with me some way compute it?
Thanks in advance.

Hi,

The meter uses its system title, authentication key, invocation counter, and challenge to generate the f(StoC). There is nothing you can do about this. Ask the new firmware where this is fixed.

You can count the CtoS or StoC by selecting "Tools" and "DLMS Translator". Select Ciphering tab and set the correct values and press "Generate password". You can see the CtoS in the message box.

BR,
Mikko

Image

Thanks for your feedback.

Thanks for your feedback.
Seem like i can do much to set this.
But thank you for all your help and support.
I will try to follow your advice. If there's any issues, I will make you know, thanks.

Hi,

Was thinking this and it might be that the meter expects a certain (static) client system title and uses that one, not the one that comes in the AARQ request.
Check from the meter documentation if the client system title is defined there.

Now you have used the same system title for the client that the meter uses.

BR,
Mikko

Hi,

Hi,
Thanks for your feedback.
I guess but I also ask the manufacturer the right system title but he replied ( picture) that there's no need to check f (CtoS).
And seems like we can't avoid checking the f (CtoS), i use the one that they gave back me but I get the same outcome like before.
So don't know where the point is !
Or is it possible to not put any system title and using an HLS with LN context name?

Image

And are these values:

And are these values:
\ICU00001
4D4D4D0000BC614E
some standard value which any meter know .
I see them often while searching.

Hi,

Of course, f(CtoS) needs to check. But I checked this and if you use 0000000000000000 as a client system title it will generate the correct result. I believe that you can read the meter if you use 0000000000000000 as the client system title. The best option is update the firmware for the meter where this is fixed.

BR,
Mikko

HI

HI
thanks for your reply
i try to use this values of system title (0x0), but the problem remains. cause of after successfully replying the AARE, the client send back an break message to stop the connection.
don't know why but i try with several tools like Ezreader but there also i got an invalid frame length for the AARE.
i want to follow your path , although i don't get the firmware update from the vendor.

GXDLMSDirector 8.1.2109.3001
Log created 11:07:46
11:07:48 Initializing serial connection.
11:07:48 11:07:48.294 Info Opening
11:07:48 11:07:48.295 Info Paramètres du port série: Nom du port: COM4 Vitesse de transmission: 300 Bits de données: 7 Parité: Even Bits d'arrêt: One Contrôle de flux: None Eop: None
11:07:48 11:07:48.318 Info Open
11:07:49 IEC Sending:/?!<CR><LF>
11:07:49 11:07:49.328 Sent 2F 3F 21 0D 0A
11:07:49 11:07:49.653 Received 3F 3F 2F
11:07:49 11:07:49.685 Received 2F
11:07:49 11:07:49.717 Received 4B
11:07:49 11:07:49.765 Received 46
11:07:49 11:07:49.796 Received 4D
11:07:49 11:07:49.828 Received 36
11:07:49 11:07:49.875 Received 5C
11:07:49 11:07:49.909 Received 32
11:07:49 11:07:49.940 Received 4B
11:07:49 11:07:49.973 Received 61
11:07:50 11:07:50.020 Received 69
11:07:50 11:07:50.051 Received 66
11:07:50 11:07:50.083 Received 61
11:07:50 11:07:50.131 Received 20
11:07:50 11:07:50.163 Received 54
11:07:50 11:07:50.195 Received 65
11:07:50 11:07:50.243 Received 63
11:07:50 11:07:50.276 Received 68
11:07:50 11:07:50.308 Received 6E
11:07:50 11:07:50.340 Received 6F
11:07:50 11:07:50.386 Received 6C
11:07:50 11:07:50.418 Received 6F
11:07:50 11:07:50.450 Received 67
11:07:50 11:07:50.497 Received 79
11:07:50 11:07:50.529 Received 0D
11:07:50 HDLC received: /KFM6\2Kaifa Technology<CR><LF>
11:07:50 Maximum BaudRate is set to : 9600
11:07:50 BaudRate is : 9600
11:07:50 Moving to mode E.
06 32 35 32 0D 0A
11:07:50 11:07:50.531 Sent 06 32 35 32 0D 0A
11:07:50 11:07:50.885 Received 3F 3F 7E
11:07:52 11:07:52.547 Info Closing
11:07:52 11:07:52.670 Info Closed
11:07:52 11:07:52.670 Info Opening
11:07:52 11:07:52.670 Info Paramètres du port série: Nom du port: COM4 Vitesse de transmission: 9600 Bits de données: 8 Parité: None Bits d'arrêt: One Contrôle de flux: None Eop: None
11:07:52 11:07:52.693 Info Open
11:07:53 Send SNRM request.
7E A0 08 02 01 61 93 58 94 7E
11:07:53 11:07:53.707 Sent 7E A0 08 02 01 61 93 58 94 7E
11:07:53 11:07:53.750 Received 7E A0 21 61 02 01 73 BB
11:07:53 11:07:53.771 Received BB 74 81 80 14 05 02
11:07:53 11:07:53.787 Received 04 00 00 00 01 08 04 00 00 00 01 CE 6A
11:07:53
7E A0 21 61 02 01 73 BB 74 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
11:07:53 Parsing UA reply succeeded.
11:07:53 Send AARQ request.
7E A0 4D 02 01 61 10 BD C5 E6 E6 00 60 3E A1 09 06 07 60 85 74 05 08 01 01 8A 02 07 80 8B 07 60 85 74 05 08 02 02 AC 12 80 10 6B 2B 79 24 02 3A 24 76 5B 38 5D 43 1C 36 00 61 BE 10 04 0E 01 00 00 00 06 5F 1F 04 00 20 5E 5D FF FF 6E A5 7E
11:07:53 11:07:53.790 Sent 7E A0 4D 02 01 61 10 BD C5 E6 E6 00 60 3E A1 09 06 07 60 85 74 05 08 01 01 8A 02 07 80 8B 07 60 85 74 05 08 02 02 AC 12 80 10 6B 2B 79 24 02 3A 24 76 5B 38 5D 43 1C 36 00 61 BE 10 04 0E 01 00 00 00 06 5F 1F 04 00 20 5E 5D FF FF 6E A5 7E
11:07:53 11:07:53.916 Received 7E A0
11:07:53 11:07:53.930 Received A0 59 61 02 01 30 F7 4B E6 E7 00 61 4A
11:07:53 11:07:53.947 Received 09 06 07 60 85 74 05 08 01 01 A2 03 02 01
11:07:53 11:07:53.963 Received 00 A3 05 A1 03 02 01 0E 89 07 60 85 74 05
11:07:53 11:07:53.978 Received 08 02 02 88 02 07 80 AA 12 80 10 7C 56 F7
11:07:53 11:07:53.994 Received 75 B2 F7 B9 54 E9 98 7C 33 1F 3A 3F 12 BE
11:07:54 11:07:54.007 Received 10 04 0E 08 00 06 5F 1F 04 00 00
11:07:54 11:07:54.022 Received 1A 1D 02 00 00 07 D5 DA
11:07:54
7E A0 59 61 02 01 30 F7 4B E6 E7 00 61 4A A1 09 06 07 60 85 74 05 08 01 01 A2 03 02 01 00 A3 05 A1 03 02 01 0E 89 07 60 85 74 05 08 02 02 88 02 07 80 AA 12 80 10 7C 56 F7 75 B2 F7 B9 54 E9 98 7C 33 1F 3A 3F 12 BE 10 04 0E 08 00 06 5F 1F 04 00 00 1A 1D 02 00 00 07 D5 DA 7E
11:07:54 Parsing AARE reply succeeded.
11:07:54 11:07:54.073 Sent 01 42 30 03 0D 0A

EZREADER software
2881'58.316+25409 Opened
2881'58.348+32 /?!<CR><LF>
2881'59.556+1208 /KFM6\2Kaifa Technology<CR><LF>
2881'59.559+2 <ACK>252<CR><LF>
2881'59.870+310 --- baud changeover 9600 ---
2882'00.911+1041 7EA0080201619358947E
2882'01.007+95 7EA02161020173BB748180140502008006020080070400000001080400000001CE6A7E
REQUEST:
<AssociationRequest>
<ApplicationContextName Value="LN" />
<CallingAPTitle Value="\ICU00001" />
<SenderACSERequirements Value="1" />
<MechanismName Value="HIGH_SECURITY_GMAC" />
<CallingAuthenticationValue Value="8C90F4CEB465F972C5F49C2ED415D120C1520E43D185A5478245160697AC0752" />
<InitiateRequest>
<ProposedDlmsVersionNumber Value="06" />
<ProposedConformance>
<ConformanceBit Name="Action" />
<ConformanceBit Name="EventNotification" />
<ConformanceBit Name="SelectiveAccess" />
<ConformanceBit Name="Set" />
<ConformanceBit Name="Get" />
<ConformanceBit Name="Access" />
<ConformanceBit Name="DataNotification" />
<ConformanceBit Name="MultipleReferences" />
<ConformanceBit Name="BlockTransferWithAction" />
<ConformanceBit Name="BlockTransferWithSetOrWrite" />
<ConformanceBit Name="BlockTransferWithGetOrRead" />
<ConformanceBit Name="Attribute0SupportedWithGet" />
<ConformanceBit Name="PriorityMgmtSupported" />
<ConformanceBit Name="Attribute0SupportedWithSet" />
<ConformanceBit Name="GeneralBlockTransfer" />
<ConformanceBit Name="GeneralProtection" />
</ProposedConformance>
<ProposedMaxPduSize Value="FFFF" />
</InitiateRequest>
</AssociationRequest>
2882'01.150+5 7EA069020161103C88E6E600605AA109060760857405080101A60A040849435530303030318A0207808B0760857405080205AC2280208C90F4CEB465F972C5F49C2ED415D120C1520E43D185A5478245160697AC0752BE10040E01000000065F1F040060FEDFFFFF6D187E
2882'01.422+271 7EA0656102013016E8E6E7006156A109060760857405080101A203020100A305A10302010E890760857405080205A40A04084D4D4D0000BC614E88020780AA1280105BB54C7292560F51C8F7D12FFF98940EBE10040E0800065F1F0400001A1F02000007A8957E
RESPONSE:
<AssociationResponse>
<ApplicationContextName Value="LN" />
<AssociationResult Value="00" />
<ResultSourceDiagnostic>
<ACSEServiceUser Value="0E" />
</ResultSourceDiagnostic>
<RespondingAPTitle Value="4D4D4D0000BC614E" />
<ResponderACSERequirement Value="1" />
<MechanismName Value="HIGH_SECURITY_GMAC" />
<RespondingAuthenticationValue Value="5BB54C7292560F51C8F7D12FFF98940E" />
<InitiateResponse>
<NegotiatedDlmsVersionNumber Value="06" />
<NegotiatedConformance>
<ConformanceBit Name="Action" />
<ConformanceBit Name="EventNotification" />
<ConformanceBit Name="SelectiveAccess" />
<ConformanceBit Name="Set" />
<ConformanceBit Name="Get" />
<ConformanceBit Name="MultipleReferences" />
<ConformanceBit Name="BlockTransferWithSetOrWrite" />
<ConformanceBit Name="BlockTransferWithGetOrRead" />
</NegotiatedConformance>
<NegotiatedMaxPduSize Value="0200" />
<VaaName Value="0007" />
</InitiateResponse>
</AssociationResponse>
2882'01.605+8 7EA0080201615354527E
2882'01.708+103 7EA02161020173BB748180140502008006020080070400000001080400000001CE6A7E
2882'01.830+121 Closed

Image

director setting

Image

error from ezreader

Image

Hi,

Please, don't add multiple questions for the same topic. I don't know what the problem is at the moment.
You have sent the AARQ and get the AARE from the meter, but you didn't add the next messages.

BR,
Mikko

HI,

HI,
thanks for your feedback
for the 0x000.....
in both case the software use sends a disconnect request after receiving the AARE
GXDLMS: send a break message " 01 42 30 03 0D 0A" == SOH.B.0.ETX.CR.LF
Ezrezader: send a disconnect request "7EA0080201615354527E" with an error " the system title receive doesn't match the declared value"
i start figure out the issue for me it's the security level which doesn't match with the application context, i' m trying to use lower security level (without syst_title) with the the application context "LN"
thanks for your help.
happy new year.

Invalid password: Server to Client challenge do not match

Forum Rules