Hello,

Using GXDLMSSecureClient with Security.AuthenticationEncryption I've managed to receive the push message sent by a Honeywell gas smart meter. The OctetString value seems to be a compact frame, more precisely CF49. There is a posibility to parse the OctetString value and get the values as a "readable format" ?

Thank you in advance

I am trying to analyse traffic between wireless module RF-433 and electric meter Natris-I100 but some parts of the messages remain unclear.

1. The RF-module sends SNRM frame:
7E A0 21 02 23 21 93 48 55 81 80 14 05 02 07 EE 06 02 07 EE 07 04 00 00 00 01 08 04 00 00 00 01 B5 D4 7E

2. Meter replies by UA frame:
7E A0 21 21 02 23 73 8F 72 81 80 14 05 02 02 00 06 02 02 00 07 04 00 00 00 01 08 04 00 00 00 01 6F EF 7E

I'm trying to build app for get meter serial number using Android DLMS package. not able to get data from the meter.

It would be possible to increase serial baudrate to higher values, greater than 115200?

Hi,

I am trying to read billing profile from a meter whose object count is 63 from an embedded device during which the stack on the client is throwing an DLMS_OUT_OF_MEMORY. When i tried to perform the same using Gurux C source code (from git-hub) in Linux environment, read is successful.

Attached the transaction log and essentials for your reference.

Below is the part of the code which throws the error code:

Hi, i am developing a gas-meter following the newly italian directive unit-ts 11291-14-2.
It states that Start of Convetional Gas Day on attribute 2 requires time data type (id=27), but in you implmentation you expect a date-time (id=25): https://github.com/Gurux/Gurux.DLMS.cpp/blob/master/development/include…

In your opinion, is this a change affceting only the newly italian normative, or new dlms/cosem sepcification?

Thank you,
Alessandro

I’m currently working with an Itron SL7000 energy meter, which is connected to a Moxa NPort device via a serial COM port. The Moxa device converts the serial data to TCP and transmits it over port 4002 (IP: 10.100.121.101).

I’ve successfully tested the setup using the Ace Vision Web application, confirming that data is correctly transmitted from the source through the Moxa converter via HDLC tunneling over TCP. This indicates that the communication path from the energy meter to the Moxa device is      functioning properly.

Dear sir,

App crashing while click on meter setting option