DLMS missing data with "Profile Generic"

Networking Solutions
1

I have a DLMS energy meter (Secure Prometer 100) connected to a RUT956 (FW 07.17.1) via TCP. The mapping/scan works correctly, and I am able to read values from data and registers. However, when trying “Profile Generic,” which holds a 300-second interval log of energy data, I am not able to retrieve the data (neither the clock nor the entries). The request seems to return only the addresses and settings, not the actual entries/lines of data. So it is connecting correctly. See output below.
When using other software (such as Gurux GXDLMSDirector), the meter data is available.

Any idea how to resolve this? If a solution is not available through the GUI, hints on scripting would be greatly appreciated—especially with the option to specify a time range. I have also tested with older firmware versions, but I am currently running 07.17.1, which seems the most stable with DLMS.

Output testing “Profile Generic”
{
“error”: 0,
“result”: {
“Energi”: {
“prometer100”: {
“1”: “1.0.99.2.0.255”,
“2”: “”,
“3”: “[Clock 0.0.1.0.0.255, Register 1.0.1.8.0.255, Register 1.0.2.8.0.255, Register 1.0.5.8.0.255, Register 1.0.8.8.0.255, Register 1.0.6.8.0.255, Register 1.0.7.8.0.255, Data 1.0.96.5.4.255, Register 1.0.157.27.0.255, Register 1.0.177.27.0.255, Register 1.0.197.27.0.255, Register 1.0.11.132.0.255, Register 1.0.11.132.124.255, Register 1.0.12.132.124.255, Register 1.0.14.27.0.255]”,
“4”: “300”,
“5”: “2”,
“6”: “”,
“7”: “16182”,
“8”: “16416”
}
}
}
}

3

Hello,

Thank you for your inquiry. Your request is currently under review and analysis. Once the evaluation is complete, I will get back to you with further information, findings, or suggestions.

Thank you for your patience in the meantime.

Best regards,

4

Hello @Vegard,

Our R&D team is aware of certain issues with the DLMS Client when using specific COSEM types, and fixes for these are planned in future firmware releases (≥ 7.19).

For your particular case, to troubleshoot and debug the issue effectively, we’ll need to continue the process privately, as sensitive information (such as troubleshoot exports, public IP addresses, or serial numbers) will be required. You should find a support request form in the inbox of the email address used for your forum registration. Kindly fill out that form and reference Ticket ID: 15275 when submitting it. Once received, we’ll get in touch with you directly via email to investigate this matter in detail and work towards a potential solution/workaround.

Best regards,

5

Thanks a lot, Martynas — both for the detailed answer and the quick feedback!

I’ve created a support case with R&D as you suggested to investigate the issue and maybe come up with a workaround until future firmware releases.

Greatly appreciated

Best regards Vegard

6

This topic was automatically closed after 60 days. New replies are no longer allowed.