hi Am trying to connect the Gurux GXDLMS Director to the landisgyr meter and it has a CU-XE communication module. There are no Obis codes in the software, and it says failed to receive reply from device. can you help? I can only connect with the MAP110 from landisgyr but with Gurux is giving me problems.

Hi,

Attribute 4 of ActionSchedule return DayOfWeek is 1),
but as a result GXDateTime has DayOfWeek as FF

7E A0 1C 00 02 4A 45 61 54 44 71 E6 E6 00 C0 01 C1 00 16 00 00 0F 00 80 FF 04 00 3D 7E 7E

7E A0 24 61 00 02 4A 45 74 09 30 E6 E7 00 C4 01 C1 00 01 01 02 02 09 04 00 00 00 00 09 05 07 EA 02 FE 01 97 BF 7E .

Why is this happening?
Can something be done about this?

Hello,

we intend to use the Gurux DLMS .NET stack for a system that needs to communicate with a large number of smart meters in parallel.

Our application architecture is fully asynchronous and uses async/await throughout the entire call chain. However, we have not found any indication that the Gurux DLMS stack supports asynchronous communication.

From what we can see, communication appears to be implemented using synchronous/blocking socket calls.

Our concern is the following:

I am using two L&T Trivector meters connected through RS-485 looping with a USB-to-Serial converter. Earlier I asked about multiple connections in the Gurux forum(https://www.gurux.fi/node/35203). I created a sample program using the Gurux DLMS Client in C#.

The issue I am facing is:
When reading data from one meter, if I power ON the second meter, the current meter stops responding.

I suspect there may be a communication conflict or addressing problem in the RS-485 multi-drop setup.

Hi, have you writed the date&time successfully to Prometer 100 via DLMS protocol in GXDLMS software? It seems that write is denied by prometer 100. We use client 32, password is ABCD0001, DLMS client can read date&time OBIS 0.0.1.0.0.255.
Whether Prometer 100 support date&time write permission?

data = "/?!\r\n";
writeTrace("<- " + now() + "\t"
+ GXCommon.bytesToHex(data.getBytes("ASCII")));
media.send(data, null);
if (!media.receive(p)) {
throw new Exception("Invalid meter type.");
}

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

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

Hi Kurumi,

I’m using Gurux DLMS with HDLC and based part of my receive logic on the examples in the Gurux repository. In particular, I copied the pattern here (https://github.com/Gurux/Gurux.DLMS.Net/blob/751914f4a9a6fd504e5b8c6430…) where a reply is treated as “no data yet” when:

reply.Error == 0 && reply.Data.Size == 0