Kaifa MA309

By Florian.Sams , 2 September, 2024
Forums
DLMSDirector

Dear Forum,

I have a new Meter that I want to test.
Now I am trying to connect via optical probe, but in the end it should be read via TCP/IP Connection and Cellular modem.

I can read the Meter with the public Client, but LLS and HLS is not working.

Is it a configuration problem or is the meter behaving differently than expected?

NOT Working LLS:

Send SNRM request.
TX: 7E A0 20 03 23 93 CD EA 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
RX: 7E A0 20 23 03 73 CB 2D 81 80 14 05 02 02 00 06 02 02 00 07 04 00 00 00 01 08 04 00 00 00 01 6F EF 7E
Send AARQ request.
TX: 7E A0 49 03 23 10 D9 3C E6 E6 00 60 3B A1 09 06 07 60 85 74 05 08 01 01 A9 03 02 01 11 8A 02 07 80 8B 07 60 85 74 05 08 02 01 AC 0A 80 08 30 30 30 30 30 30 30 31 BE 10 04 0E 01 00 00 00 06 5F 1F 04 00 62 18 5D 02 1C 1C B2 7E
RX: 7E A0 10 23 03 30 A6 11 E6 E7 00 0E 0D 03 02 37 0D 7E
RX: 7E A0 07 23 03 73 B9 F5 7E

PUBLIC Client:

Send SNRM request.
TX: 7E A0 07 03 21 93 0F 01 7E
RX: 7E A0 07 21 03 73 01 40 7E
Send AARQ request.
TX: 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 62 FE DF 02 1C B3 41 7E
RX: 7E A0 37 21 03 30 6C 7C E6 E7 00 61 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 11 02 1C 00 07 DE 83 7E

Any help appreciated.

Florian.Sams

1 year 9 months ago

Thanks Kurumi.
I am pretty sure about the Client Adresses.
I have the manufacturer maintenance Tool available and can read and access the meter from there.

16 - Public
17 - Read Out Client
23 - Central System

Regarding IP Connection, this is not an issue yet, first I need to make it work with Optical probe.

Kurumi

1 year 9 months ago

Hi,

I believe that Read Out Client is not using any authentication. Try to change LLS to None and change client address to 0x11.

BR,
Mikko

Florian.Sams

1 year 9 months ago

Hi Kurumi,

according to the manufacturer tool.

Client adress 17
Low Level Security

This is a trace from the Application, connection is via IP so translate with wrapper.

00 01 00 10 00 01 00 2B 60 29 A1 09 06 07 60 85 74 05 08 01 01 A6 0A 04 08 43 54 54 30 30 30 30 30 BE 10 04 0E 01 00 00 00 06 5F 1F 04 00 00 1F 3F FF FD

00 01 00 01 00 10 00 37 61 35 A1 09 06 07 60 85 74 05 08 01 01 A2 03 02 01 00 A3 05 A1 03 02 01 00 A4 0A 04 08 4B 46 4D 69 75 5B C4 02 BE 10 04 0E 08 00 06 5F 1F 04 00 00 10 11 02 1C 00 07

00 01 00 10 00 01 00 0D C0 01 C1 00 01 00 00 60 01 00 FF 02 00

00 01 00 01 00 10 00 0E C4 01 C1 00 09 08 38 39 39 30 30 30 33 34

00 01 00 10 00 01 00 17 62 15 80 01 00 BE 10 04 0E 01 00 00 00 06 5F 1F 04 00 00 1F 3F FF FD

00 01 00 01 00 10 00 17 63 15 80 01 00 BE 10 04 0E 08 00 06 5F 1F 04 00 00 10 11 02 1C 00 07

00 01 00 11 00 01 00 44 60 42 A1 09 06 07 60 85 74 05 08 01 01 A6 0A 04 08 43 54 54 30 30 30 30 30 8A 02 07 80 8B 07 60 85 74 05 08 02 01 AC 0A 80 08 30 30 30 30 30 30 30 31 BE 10 04 0E 01 00 00 00 06 5F 1F 04 00 00 1F 3F FF FD

00 01 00 01 00 11 00 37 61 35 A1 09 06 07 60 85 74 05 08 01 01 A2 03 02 01 00 A3 05 A1 03 02 01 00 A4 0A 04 08 4B 46 4D 69 75 5B C4 02 BE 10 04 0E 08 00 06 5F 1F 04 00 00 10 14 02 1C 00 07

00 01 00 11 00 01 00 0D C0 01 C1 00 01 00 00 2A 00 00 FF 02 00

00 01 00 01 00 11 00 16 C4 01 C1 00 09 10 4B 46 4D 31 30 33 30 37 38 39 39 30 30 30 33 34

Kurumi

1 year 9 months ago

Hi,

Select "Supported Services" tab and uncheck following conformance:

GeneralProtection
GeneralBlockTransfer
DeltaValueEncoding
Access

BR,
Mikko

Florian.Sams

1 year 9 months ago

Hi Mikko,

makes no difference.
I can read the Conformance Bits from the Maintenance Client Application and select them accordingly in the Director, still the same outcome.

Kurumi

1 year 9 months ago

Hi,

There are two odd things with the manufacturer application.
It sends CallingAPTitle and CallingAuthentication fields with Low authentication.
Those are not needed with Low authentication and those are now tested in DLMS conformance tests.

You have also set UserID to 0x11. Remove that. I hope that helps and the reason is not with CallingAPTitle or CallingAuthentication.

https://www.gurux.fi/GuruxDLMSTranslator?translate=00010011000100446042…

BR,
Mikko

Florian.Sams

1 year 9 months ago

Regarding CallingAuthenticationValue, this is the password, correct?
With LLS password needs to be sent if I understand correctly.

If I understand the greenbook correctly, as soon as the authentication functional unit is set (ACSERequirement = 1), it is allowed to send mechanism an Authentification value:

Fields of the authentication functional unit (when present):
• sender-acse-requirements:
a) if not present or present but bit 0 = 0, then the authentication functional unit is not selected. Any following fields of the authentication functional unit may be ignored;
b) if present and bit 0 = 1 then the authentication functional unit is selected;
• mechanism-name: it carries the COSEM_Authentication_Mechanism_Name the client proposes for the association;
• calling-authentication-value: it carries the authentication value generated by the client.
If the value of the mechanism-name or the calling-authentication-value fields are not acceptable then the proposed AA shall be refused.

The CallingAPTitle is also something I find suspicous.
Can I force the director to send it as well?
It is optional in the AARQ MEssage according to the Greenbook, but if the meter expects it, not much I can do correct?

edit:
I removed the ClientID in other tests, also didn't work.

Kurumi

1 year 9 months ago

Hi,
My bad. CallingAuthentication must send in LLS, but CallingAPTitle not.

You can't force to send CallingAPTitle because that is not needed with LLS authentication.

You can modify the source code and check if this is the reason.

Get the Gurux.DLMS.Client.Example.Net and try to connect with that.
https://github.com/Gurux/Gurux.DLMS.Net/

Before connecting, modify GenerateAARE so the system title is sent.

https://github.com/Gurux/Gurux.DLMS.Net/blob/30a096568fd6fe2000366d5011…

BR,
Mikko