I've HLS as "77777777777777777777777777777777" in hex "wwwwwwwwwwwwwwww" in ASCII but when I send via gurux or any other meter reading software i.e. kalki, the CallingAuthentication Value changed it into "0F286E004D6C3C291564560557271D11". I know its a CtoS challenge for pass1 but how hls is converted to this string, or I should say from which encryption method it is encrypted that I didn't understand. I'm trying to establish client id 48 of a smart energy meter. and If any one can provide me a document where after pass1, how to create data for pass3 then it would be very handy. thanks in advance.
Open source solutions for DLMS smart metering
Hi, This is described in the…
Hi,
This is described in the Green Book. In short, the meter sends a challenge to the client that the client encrypts with the secret and then sends it back to the server as a CtoS.
The meter does the same for the client challenge.
BR,
Mikko