Conformance Testing tips and tricks
Content:
> Submission of test results for Certification
> Mandatory objects - Current Association
> Identifiers in the CTI
> For Certification all test options shall be enabled: DoNotTest []
> Use of the "continue after failure" feature of the CTT
> Logical Device Name
Submission of test results for Certification
When the test has been successfully completed, please use the "Create Certification Report" item from the CTT Help menu and send the resulting .zip file together with your certification request to DLMS Support <ctt-support@dlms.com>.
Only .zip created by the CTT Tool is accepted . Other file formats (for example .rar) will be refused. Please see Yellow Book Ed.4.0 Clause 6.4.6 and 6.4.7.
Should you encounter any problems during testing, please use the "Create Snapshot" item from the CTT Help menu and send it to DLMS Support <ctt-support@dlms.com>.
Mandatory objects - Current Association
– INCONCLUSIVE (Current association object not found)
Phenomenon:
The CTT reports: Current association INCONCLUSIVE(Current association object not found).
This may occur only when LN refrencing is used.
Explanation:
At the end of testing the COSEM objects in each Association, the CTT tries to report the list of objects found.
For this purpose, it needs to have access to the associated_partners attribute of the Current Association LN object.
If this attribute is not implemented, or the attribute is not accessible for read, or if the SAPs of the client and the server held by the attribute do not match the application addresses carried by the supporting layer of the COSEM Application layer, then the CTT produces the INCONCLUSIVE verdict and the object list is not reported.
This leads to the rejection of the test report.
| Nr | Class | V | OBIS name | Description |
| 156 | 8 : Clock | 0 | 0000010000FF(0.0.1.0.0.255) | Ch. 0; Clock object; #1 |
| 196 | 27 : Modem configuration | 0 | 0000020000FF(0.0.2.0.0.255) | Ch. 0; Modem configuration |
| 197 | 28 : Auto answer | 0 | 0000020200FF(0.0.2.2.0.255) | Ch. 0; Auto answer |
Identifiers in the CTI
The conformance Certificates issued by the DLMS UA use strictly the identifiers found in the test reports.
No information outside the Test Report - which also incorporates the CTI - is taken into account.
The name of the Manufacturer, the meter type identifier and the test laboratory are also shown on the list of certified equipment as taken from the Test Report and reproduced in the Certificate.
Therefore, please make sure that all identifiers are correctly declared in the CTI:
// Identification of the manufacturer
Manufacturer = {
Name = 'xxxxx'
ThreeLettersId = 'XYZ' // FLAG 3 letters
}
// Identification of the physical device. As media identifier define ABTRACT
// plus others media like ELECTRICITY, GAS etc...
PhysicalDevice = {
Ident = 'xxxx'
MediaIdentifiers = [xxx, yyy]
SerialNr = 'xxxxxx' // Any string
}
See also Clause 7.4 of the Yellow Book.
For Certification all test options
shall be enabled: DoNotTest []
To facilitate the testing process, the CTT provides some test options. When an option is selected, the CTT skips the related test.
The test options to be skipped can be specified using the DoNotTest set. These options are listed in Yellow Book Ed. 4.0 Clause 6.2.2 Table 2.
For example: [LOG_0_IS_MGMT_LOG_DEVICE, LOG_0_HAS_ALL_SECURITY_LEVELS, ATTRIBUTES_TYPE_CHOICES, ATTRIBUTES_VALUES]
When the purpose of the test campaign is to produce a test report to be submitted to obtain a Certificate, then all options shall be disabled: the DoNotTest set shall be empty.
See also the CTT Help file, under “CTI file content”:
TestOptions
Optional
Control of specific aspects of the testing process.
structure:
DoNotTest
Optional
Controls the suppression of specific tests.
set of enum, with:
LOG_0_IS_MGMT_LOG_DEVICE , when set then do not check that the Logical device 0 is the Management logical device (ServerSAP = 1) and that its NO_SECURITY Association is the public association (ClientSAP = 0x10)
LOG_0_HAS_ALL_SECURITY_LEVELS, when set then do not check that the associations needed for the HDLC and APPL tests belong to Logical device 0.
ATTRIBUTES_TYPE_CHOICES, when set, then do not test the type of attributes having a CHOICE type.
ATTRIBUTES_VALUES, when set then do not test the values (ranges, and sub-ranges) of attributes.
Use of the "continue after failure feature"
of the CTT
The CTT offers a "Continue after failure" feature (Options > Miscellaneous). This feature may be useful to find errors while the DUT is not yet passing all tests.
However, after a failure the CTT and the IUT are outside of their normal operation mode and their behavior may not be coherent any more. In such cases, the test should be run again with the "Continue after failure" feature disabled.
See also Yellow Book Ed. 4.0 subclause 6.2.3.
In any case, this feature shall be disabled if the purpose of the test is to produce a Certification report to be submitted to the DLMS UA.
Logical Device Name
The "Logical Device Name" LDN is a very important element in identifying the source of the metering data. It is specified in the subclause 4.1.8.2 of the Blue Book.
4.1.8.2 COSEM logical device name
The COSEM logical device can be identified by its unique COSEM logical device name. This name can be retrieved from an instance of IC “SAP assignment” (see 4.4.3), or from a COSEM object “COSEM logical device name” (see 4.12.2.24).
The logical device name is defined as an octet-string of up to 16 octets. The first three octets shall carry the manufacturer identifier. The manufacturer shall ensure that the logical device name, starting with the three octets identifying the manufacturer and followed by up to 13 octets, is unique.
The 13 octets hold a kind of serial number to distinguish each and every logical device. The type and version is not sufficient. The content of the 13 octets is left to the manufacturer, however, it is a good practice to include parts of the meter type, version and serial number so that the uniqueness of the LDN for each and every Logical Device can be ensured.
Test reports carrying the same Logical Device Name as to be found in an already existing certificate will be rejected.
The manufacturer identifier is administered on the Internet site of the DLMS User Association, and the list is maintained by the FLAG Association.