Hi, am trying to read meter that supports compact array for load profile reading. I have following observation with Compact array.
- Whenever I read few entries that fit in single window, all works fine.
- Whenever I try reading more entries that triggers block transfer, director throws exception
Hello, I'm currently encountering a situation where I'm using the official version of the.c client source code to read the electricity meter data, but the reading keeps failing.
The all-0 key I set when using the GXDLMSDirector client can be read normally,However, use https://github.com/Gurux/GuruxDLMS.c/tree/948da08617e623f5e3f6dd3dab9ad… appear error.
This is my execution order：
Hi Mr. Mikko, I would like to ask you about the blockCipher and Authentication keys . I try to find the keys inside meters the main 4mb eeprom memory where the security keys is stored. The meter saves the most data(not all) ciphered in the main eeprom memory and I can’t locate the address with the saved keys. I have read with programmer the eeprom.
Is there some software to “translate” the ciphered hex dump of the eeprom memory?? Is it possible to help me?
I have been trying for months to do that with no success.
I'm working on a project with some Hexing meters. I was able to connect to the meter via the optical port using HDLCWithModeE at 300 baud, 7E1, with GURUX DLMS Director and Python, and publish the data via MQTT. However, I don’t know how to establish a connection through RS485. I’ve tried multiple baud rates, servers, and users using the baud rate scan in GURUX DLMS Director, but without success.
The final goal is to have an ESP32 connect to the meter via RS485 and publish the acquired data to my MQTT server.
Hi everyone, I’m prototyping a smart meter interface using an ESP32 to read DLMS/COSEM data over RS-485 and then relay that information via MQTT. For inspiration on reliable multi-node communication, I found this guide on ESP-NOW peer-to-peer networking really insightful: https://www.theengineeringprojects.com/2022/01/esp-now-protocol-with-es…
Hello, wanted to ask a question, maybe you will have some insights.
We are trying to find a solution to launch DLMS over Lorawan. One thing is that our product is battery-powered water meter.
I have questions:
1. Maybe you have real life examples that this was done before?
2. time / Duty cycle - this time is very strict in lorawan, how it is possible to overcome this barrier when DLMS handshake takes up to 6-12 telegrams?
