Hello Mikko,

As written in Green Book:

"NOTE As specified in DLMS UA 1000-1 Ed. 13:2019, 4.1.2, manufacturers may add proprietary methods and/or attributes to any object, using negative numbers."

There is a lot of index positivity checks (for methods and attributes ) in GXDLMSClient.cs, so as far as I see proprietary methods or attributes will be blocked. Any way to change this behaviour?

Best regards, Andre

Hello Mikko,

I'd like to ask you about System title field structure.

As I know, Server system title is 8 bytes long, first 3 bytes is manufacturer code and 5 more are meter serial.

I never thought that System title must obey some rules too except 8 bytes long,
so I named it in my case as 'homepc08'

Recently I've noticed that DLMS Director in Translator dialog is trying to decode this field as

Hi to all,
We are managing an AMI project and we designed with our provider an external modem than can connect to different existing meters, including elster A1800. The modem is powered with external 220v source and connected to the elster meter through the rs485 port. The meter has been configured to enable the connection with the modem and the dlms protocol has been activated also to support data collection from our HES.

Hi, Mikko

1. In getCompactArrayItem() use only gxfree(value); but i think need use:
var_clear(value);
gxfree(value);

like in function getCompactArrayItem2().

2. In getCompactArrayItem2():
if (tmp->Arr == NULL)
{
//here need gxfree(tmp); because in row 1637: dlmsVARIANT* tmp = gxmalloc(sizeof(dlmsVARIANT));
return DLMS_ERROR_CODE_OUTOFMEMORY;
}

Please, check it.

Thanks!

Hello Gurux Team,

I am using the latest official Gurux.DLMS.Client.Example.Net to communicate with a DLMS meter over a serial (HDLC) connection.

Environment
Gurux.DLMS : 9.0.2605.2801
Gurux.Common : 8.4.2503.602
Gurux.Serial : 8.4.2503.603
.NET Framework : 4.7.2
Communication : Serial (HDLC)
Meter Configuration
Interface Type : HDLC
Referencing : Logical Name (LN)
Authentication : HighGMAC
Security : AuthenticationEncryption
Security Suite : Suite0

Hi, GX Team,
pls help us to fix this issue while reading the Time from Python Code:-

I'm testing an embedded LN-only DLMS/COSEM server with the GXDLMSDirector Application Conformance Test. 13 of 14 tests pass; the only failing one is T_APPL_DATA_LN_N1, and it always fails on subtest 3 ("Read non-existing object").

The tool sends a GET for a non-existing object (class 15 / Association LN,
OBIS FF FF FF FF FF FF, attribute 1):

C0 01 C1 00 0F FF FF FF FF FF FF 01 00

The overall result is always:

T_APPL_DATA_LN_N1 subtest 3 succeeded when Short Name referencing is used.
T_APPL_DATA_LN_N1 failed.