In Gurux GXDMS Director tool, I tried to refresh objects to read all the objects from my meter, the new objects has been added to the list, but when I try to select and read them, I receive this error:

ERROR: The given key was not present in the dictionary.

Also the new object is MBUSDIAGNOSTIC

I would be grateful if you can help me with this problem.

Hi Kurumi,

Currently working on PC association using guruxDLMSserver.c with ESP32 using Arduino IDE .
With TCP communication we are able to download objects using GXDLMSDirector. Now we want to use US association.
Unable to assign authentication key and blockcipherkey in esp32 as dlms server.
What settings we need to do or add to get US association work.

Thank you

Greetings,

Im currently using DLMS Simulator to simulate a device, but im struggling to first read the device data correctly, I firstly used the integrated read function of the simulator, the conexion is correct and I generate a .xml but I get "invalid" values from the reads:

Command: "Gurux.DLMS.Simulator.Net.exe -h (ip) -p 4059 -i WRAPPER -c 2 -s 1 -a Low -P (password) -t Verbose -o fileoutput.xml"

srikanth@phytec:~/work/smart-energy-meter/smart-meter-integration/custom-dlms-meter-reader/dlms-python/yitran-dlms-python/Gurux.DLMS.Python/Gurux.DLMS.Client.Example.python$ python3 mqtt_obis.py
Starting MQTT client...
Connected to MQTT broker with result code 0
Subscribed to topics: meter/parameters, meter-id, obis-code
Received message from topic meter-id: EP1240009
Received meter-id: EP1240009
Meter ID set to: EP1240009

I am using the gurux client Sample from the github repo in the following link https://github.com/Gurux/gurux.dlms.java/tree/master/gurux.dlms.client…

I run it with provided argument I got the available meter that I have access to in XML file, but I don't how the get data received from meters and which function to use to return the data so I can store it in a json file and push it my pipelines.
anyone have an idea about that I will appreciate any help.

Hi,

I am trying to enable/disable HLS security on E360 meter from Landis. I am having troubles with how to generate correct frame for GXDLMSAssociationLogicalName object. I am trying to write "AuthenticationMechanismName" (attribute 6) to the meter but I would need to encode it not as a struct but as an octet string, could you help me with that?

This is an output frame that I am currently getting:
C104C102000F0000280002FF0600004000002B0000FF0200020207110211101202F411051108110211011600

Hi,

I use the settings:

Max payload size - 125

Packet SNRM with address size 1:

7E A0 1F 02 21 61 93 FF 13 81 80 12 05 01 7D 06 01 7D 07 04 00 00 00 01 08 04 00 00 00 01 89 E1 7E

Packet SNRM with address size 2:

7E A0 1F 02 21 61 93 FF 13 81 80 12 05 01 7D 06 01 7D 07 04 00 00 00 01 08 04 00 00 00 01 89 E1 7E

As far as I understand, the address with a size of 1 should be different, but here the packets are the same.

When using GXDLMSSecureClient with the HDLC interface, the clientAddress set in the settings object (client.settings.clientAddress) is incorrectly ignored during the generation of the HDLC SNRM frame if and only if a Security level other than Security.NONE is configured via client.ciphering.security.
If client.ciphering.security is left as Security.NONE, the HDLC source address is generated correctly based on settings.clientAddress.

Hello!

Recently, I’ve been trying to decode an information report packet with the PDU interface type, but the value always comes out as null, even though the GXDLMSTranslator decodes it correctly. I would like to know if this is indeed as it should be. I’m using the library version 9.0.2503.2001 for .NET.

Hello
I am facing this problem in getting the date. I would be grateful if you could suggest me a solution.
The time is correct, but the date is wrong, and the correct date is glorious
trace debug
Clock : Index: 2 Value: 01/01/1970 18:10:47<LF>
Index: 3 Value: -210<LF>
Index: 4 Value: 0<LF>
Index: 5 Value: 01/01/1970 00:00:00 UTC+00:00<LF>
Index: 6 Value: 01/01/1970 00:00:00 UTC+00:00<LF>
Index: 7 Value: 0<LF>
Index: 8 Value: 0<LF>
Index: 9 Value: 0<LF>