My meter is sending an AARE APDU similar to the the example of the green book "11.6 Encoding of the AARE APDU", example: "LN referencing with no ciphering, HLS, successful establishment of the AA", the complete AARE APDU is showed in "Table 116".
This example uses the high-level-security-mechanism-name (5), but does not send the system title in the AARE, and the response in the pass 4 is not showed.
Now, in the Secured Connections tab of Gurux, I chose "security: none", this is because when I select "security: authentication", gurux sends in the AARQ the context_id (3) instead of the context_id (1) and in this case I think that the AARE must be different from the example in the green book.
should I change it to security: authentication?
Should I send the system title in step 4, or the system title is needed in the AARE when "security: authentication" is selected?
Just as comment, in the green book, in the 9.2.2.2.2.1 Overview, you can find:
NOTE 2 The elements (System_Title), (Certificate) and (Client_User_Id) are optional.
It's true that system title is optional. Each meter has own system title. It's made from manufacturer ID and serial number. For this reason, it's usually coming with AARE message. Otherwise, the user must set it by hand before the ciphered connection can be established.
We are changing it so it can be optional in the future versions.
Hi,
Hi,
What programming language you are using? We'll check this.
BR,
Mikko
Hi Mikko,
Hi Mikko,
I am developing an electrical metter using c language. I downloaded the Gurux DLMS Director for .Net 4.6. to test the comunnication.
https://www.gurux.fi/Downloads/gxdlmsdirector46/GXDLMSDirector.applicat…
Regards!
Hi,
Hi,
Your meter doesn't return system title.
BR,
Mikko
Hi Mikko,
Hi Mikko,
My meter is sending an AARE APDU similar to the the example of the green book "11.6 Encoding of the AARE APDU", example: "LN referencing with no ciphering, HLS, successful establishment of the AA", the complete AARE APDU is showed in "Table 116".
This example uses the high-level-security-mechanism-name (5), but does not send the system title in the AARE, and the response in the pass 4 is not showed.
Now, in the Secured Connections tab of Gurux, I chose "security: none", this is because when I select "security: authentication", gurux sends in the AARQ the context_id (3) instead of the context_id (1) and in this case I think that the AARE must be different from the example in the green book.
should I change it to security: authentication?
Should I send the system title in step 4, or the system title is needed in the AARE when "security: authentication" is selected?
Best regards!
Hi,
Hi,
This is interesting. In Green Book example the server system title is not sent in AARERE.
http://www.gurux.fi/GuruxDLMSTranslator?pdu=6142A109060760857405080101A…
All the meters what we are reading are returning system title in AARE.
http://www.gurux.fi/GuruxDLMSTranslator?pdu=6156A109060760857405080101A…
System title is not sent in Green Book AARQ example.
http://www.gurux.fi/GuruxDLMSTranslator?pdu=6036A1090607608574050801018…
I'll ask is APTitle mandatory when GMAC is used.
BR,
Mikko
Hi Mikko,
Hi Mikko,
Thanks for your answer,
Could you send me the APDU that gurux receives in step 4 (Answer to the challenge: f (CtoS))?
Best regards!
Hi Rafael,
Hi Rafael,
Here is an example from the real meter.
http://www.gurux.fi/GuruxDLMSTranslator?pdu=6156A109060760857405080101A…
BR,
Mikko
Hi Mikko,
Hi Mikko,
Thanks for your answer,
Just as comment, in the green book, in the 9.2.2.2.2.1 Overview, you can find:
NOTE 2 The elements (System_Title), (Certificate) and (Client_User_Id) are optional.
Regards!
Hi,
Hi,
It's true that system title is optional. Each meter has own system title. It's made from manufacturer ID and serial number. For this reason, it's usually coming with AARE message. Otherwise, the user must set it by hand before the ciphered connection can be established.
We are changing it so it can be optional in the future versions.
BR,
Mikko