HLS Mechanism_id(2)

By Shanmukhi , 7 March, 2024

Forums

After send f(ctos) we are getting Access Error : Device matched a unmatched type

we are using mechanism id (2) . we are giving password as "hello"
our AARE is passed and action request came from gurux director we can able to decrypt it

but further we are failing.

Image

Hi, In the log, you are not…

Hi,

In the log, you are not sending f(ctos) or password yet. Those are sent in step 3. You are just sent AARQ and the meter returns AARE that you have added.

I believe that your password is wrong.

BR,
Mikko

7E A0 41 00 02 04 01 61 32 16 F6 E6 E6 00 CB 30 30 00 00 00 01 F9 E1 7E D2 C1 0D 43 3C D4 96 9D B5 33 42 3F 59 F2 55 02 9D F5 E2 06 F2 BC 8C 1C 8F E7 2B 08 A7 F4 6B A7 ED 46 E3 41 E4 5C 44 F5 04 C7 7E

The above request, the meter can able to decrypt. We don't know which algorithm/mode is used in Mechanism_id(2) of GURUX.

Can you share details of the algorithm/mode used in Mechanism_id(2) of GURUX?

Hi, High authentication is a…

Hi,

High authentication is a problem because DLMS specification does not specify details of the HLS mechanism. Indian standard uses Aes-128 for High authentication, so Gurux DLMS libraries are also using Aes-128 for High authentication.

BR,
Mikko