The client proposes conformance and the meter will tell what conformance it will support.
There might different conformance for each of the associations. For this reason, negotiated conformance is updated internally on the server-side.
Please, set conformance only for the association and let the framework do the rest.¨
Like this:
associationNone.xDLMSContextInfo.conformance = DLMS_CONFORMANCE_GET;
Dear Mikko,
This is conformance test failed issue we based
T_APPL_OPEN_13
0/0, ServerSAP = 1, ClientSAP = 16, LONG_NAMES, NO_SECURITY
1: Propose all services and capabilities in line
with the application context FAILED(Association could not be established)
Yellow book Test case for your reference
Subtest 1: Propose all possible services
Send an AARQ APDU with proposed-conformance = all possible services (including SN and LN services). Expect an AARE APDU.
Check the relevant fields of the AARE APDU. If:
• the result field is not Association-result = accepted (0); or
• the result-source-diagnostic field is not Associate-source-diagnostics = acse-service-user or the value is not null (0); or
• the negotiated-conformance is not equal to the conformance block declared in the CTI
the verdict is FAILED.
Release the AA.
Connected PC association gurux dlms c library request response:
already set this in PC association
associationNone.xDLMSContextInfo.conformance = (DLMS_CONFORMANCE)(DLMS_CONFORMANCE_GET | DLMS_CONFORMANCE_SET);
(AARQ response - T_APPL_OPEN_13 failed )
There is one row missing from the example server. It's updated and the new version is released shortly.
I'm sorry for this hassle. I was testing this with a different server and not with the example server.
I created an issue from this. http://gurux.fi/node/17948
Hi,
Hi,
The client proposes conformance and the meter will tell what conformance it will support.
There might different conformance for each of the associations. For this reason, negotiated conformance is updated internally on the server-side.
Please, set conformance only for the association and let the framework do the rest.¨
Like this:
associationNone.xDLMSContextInfo.conformance = DLMS_CONFORMANCE_GET;
BR,
Mikko
Dear Mikko,
Dear Mikko,
This is conformance test failed issue we based
T_APPL_OPEN_13
0/0, ServerSAP = 1, ClientSAP = 16, LONG_NAMES, NO_SECURITY
1: Propose all services and capabilities in line
with the application context FAILED(Association could not be established)
Yellow book Test case for your reference
Subtest 1: Propose all possible services
Send an AARQ APDU with proposed-conformance = all possible services (including SN and LN services). Expect an AARE APDU.
Check the relevant fields of the AARE APDU. If:
• the result field is not Association-result = accepted (0); or
• the result-source-diagnostic field is not Associate-source-diagnostics = acse-service-user or the value is not null (0); or
• the negotiated-conformance is not equal to the conformance block declared in the CTI
the verdict is FAILED.
Release the AA.
Connected PC association gurux dlms c library request response:
already set this in PC association
associationNone.xDLMSContextInfo.conformance = (DLMS_CONFORMANCE)(DLMS_CONFORMANCE_GET | DLMS_CONFORMANCE_SET);
(AARQ response - T_APPL_OPEN_13 failed )
TX: 7E A0 07 03 21 93 0F 01 7E
16:46:06
RX: 7E A0 1E 21 03 73 C3 7A 81 80 12 05 01 80 06 01 80 07 04 00 00 00 01 08 04 00 00 00 01 53 3B 7E
16:46:06 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 00 1E 1D FF FF C5 E4 7E
16:46:06
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 1E 1D 02 00 00 07 7A ED 7E
*******************
Other Meter request response :(AARQ response - T_APPL_OPEN_13 passed)
7E A0 07 03 21 93 0F 01 7E
7E A0 1E 21 03 73 C3 7A 81 80 12 05 01 80 06 01 80 07 04 00 00 00 01 08 04 00 00 00 01 53 3B 7E
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 60 FE DF FF FF DE 4E 7E
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 10 02 00 00 07 AC A8 7E
Hi,
Hi,
There is one row missing from the example server. It's updated and the new version is released shortly.
I'm sorry for this hassle. I was testing this with a different server and not with the example server.
I created an issue from this.
http://gurux.fi/node/17948
BR,
Mikko
Hi,
Hi,
The new version is released where this is fixed.
Find this line:
settings->proposedConformance = a->xDLMSContextInfo.conformance;
It'll fix this.
BR,
Mikko