The problem seems to me deeper. I checked the package in GuruxDLMSTranslator and got the error. I don't understand what the problem is. When Security = None there is no error in GuruxDLMSTranslator.
At first glance, the package contains no errors
7E A0 78 61 02 2F 30 01 99 E6 E7 00 61 69 A1 09 06 07 60 85 74 05 08 01 03 A3 05 A1 03 02 01 0E BE 23 04 21 28 1F 30 00 00 00 00 E4 F4 65 90 28 9A CF 8F B6 EE 80 32 3B 06 34 75 6F 32 48 AA CD 61 1A 1D D3 E3 A4 0A 04 08 30 30 30 30 30 30 30 30 A2 03 02 01 00 88 02 07 80 AA 12 80 10 C9 C3 C9 C3 FE 65 FE 65 90 C3 90 C3 7E B8 7E B8 89 07 60 85 74 05 08 02 02 80 56 7E
The server system title is 8 bytes long value. Have you modified the source code because there are only 7 bytes? Your meter is also returning an invalid reply. ApplicationContextName is invalid. ResultSourceDiagnostic should be ciphered and the server system title is missing.
I figured out the problem.
The fact is that, apparently, the GXDLMSDirector program parses the package by sequentially processing the tags. The vulnerability of such a mechanism is that when the BE and A4 tags are swapped, such an algorithm crashes during operation. The way out of this situation would be to parse the BE tag with an intermediate search for the A4 tag (if it has not been encountered before) inside the package as needed.
Hi,
Hi,
Check "Logical Name Referencing" from meter settings.
BR,
Mikko
Hi, Mikko!
Hi, Mikko!
Thanks for your reply!
The problem seems to me deeper. I checked the package in GuruxDLMSTranslator and got the error. I don't understand what the problem is. When Security = None there is no error in GuruxDLMSTranslator.
At first glance, the package contains no errors
7E A0 78 61 02 2F 30 01 99 E6 E7 00 61 69 A1 09 06 07 60 85 74 05 08 01 03 A3 05 A1 03 02 01 0E BE 23 04 21 28 1F 30 00 00 00 00 E4 F4 65 90 28 9A CF 8F B6 EE 80 32 3B 06 34 75 6F 32 48 AA CD 61 1A 1D D3 E3 A4 0A 04 08 30 30 30 30 30 30 30 30 A2 03 02 01 00 88 02 07 80 AA 12 80 10 C9 C3 C9 C3 FE 65 FE 65 90 C3 90 C3 7E B8 7E B8 89 07 60 85 74 05 08 02 02 80 56 7E
Best regards,
Rostislav
Up
Up
Up
Up
Hi,
Hi,
I can't check this because I don't know the logical name of the meter. Can you add all messages between the client and the meter?
BR,
Mikko
Mikko,
Mikko,
Logical name = KAC00000001 (obis 0.0.42.0.0.255)
This is the entire data exchange (there is no further exchange):
> 7E A0 08 02 2F 61 93 78 87 7E
< 7E A0 08 61 02 2F 73 6D FC 7E
> 7E A0 7D 02 2F 61 10 4C 02 E6 E6 00 60 6E A1 09 06 07 60 85 74 05 08 01 03 A6 0A 04 08 30 30 30 30 30 30 30 8A 02 07 80 8B 07 60 85 74 05 08 02 02 AC 12 80 10 61 54 65 18 21 21 0F 18 13 3A 01 14 11 2C 39 4C BE 34 04 32 21 30 30 00 00 00 00 ED F5 73 31 97 60 6F 71 49 0F 20 4C 9B FF D8 46 A8 DF DE F4 6E 20 E5 67 1E 22 55 F2 E0 70 77 3F 4C A8 FF 03 D6 1F 16 73 13 13 B6 68 59 7E
< 7E A0 6C 61 02 2F 30 51 00 E6 E7 00 61 5D A1 09 06 07 60 85 74 05 08 01 01 A3 05 A1 03 02 01 00 BE 23 04 21 28 1F 30 00 00 00 00 E4 F4 65 90 28 9A CF 8F E9 AC 80 32 3B 06 37 45 2D F7 9F E1 19 EA 0C 97 83 ED A2 03 02 01 00 88 02 07 80 AA 12 80 10 04 8A 04 8A C0 B8 C0 B8 F8 47 F8 47 F7 1D F7 1D 89 07 60 85 74 05 08 02 02 C1 23 7E
> 7E A0 08 61 02 2F 73 6D FC 7E
Gurux.DLMS.GXDLMSException: Connection is permanently rejected. The application context name is not supported.
Best regarqs,
Rostislav
Hi Rostislav,
Hi Rostislav,
The server system title is 8 bytes long value. Have you modified the source code because there are only 7 bytes? Your meter is also returning an invalid reply. ApplicationContextName is invalid. ResultSourceDiagnostic should be ciphered and the server system title is missing.
BR,
Mikko
MY METER NOT CONNECTED SINCE
MY METER NOT CONNECTED SINCE THEY POP UP INVALID
Hi Hemant Kumar,
Hi Hemant Kumar,
Please, create a new topic if you have a new question.
BR,
Mikko
Hi, dr. Mikko!
Hi, dr. Mikko!
I figured out the problem.
The fact is that, apparently, the GXDLMSDirector program parses the package by sequentially processing the tags. The vulnerability of such a mechanism is that when the BE and A4 tags are swapped, such an algorithm crashes during operation. The way out of this situation would be to parse the BE tag with an intermediate search for the A4 tag (if it has not been encountered before) inside the package as needed.
The forum thread can be considered closed.