Hi,

I'm trying to connect to wasion meter. the security is using HighGMAC. and the response is "Connection is permanently rejected. No common AcseVersion"
I try many combination on client, logical, physical address and i think the current value is correct because the meter responding and responsive. What could possibly go wrong? Is it regarding the title, block cipher, etc?

Hello Gurux Team,

We are currently facing an issue while reading meter data using Gurux DLMS libraries.

In the field, some meters are configured to return values with 6 digits (for example, energy or billing-related parameters). However, while reading these values through Gurux, we are consistently receiving only 5 digits, even though the meter display shows 6 digits.

Observations:

The meter display clearly shows a 6-digit value.

Gurux response contains only 5 digits for the same OBIS/field.

Hi sir,

Where can i download Gurux android app.

I would like to know whether the Gurux DLMS supports AMR for bidirectional meters used in SRTPV applications. Any guidance would be appreciated.

hi, am new in DLMS community.

this is my object lis.

gxObject* ALL_OBJECTS[] = {
BASE(association),
BASE(ldn),
BASE(hdlc),
BASE(clock1),
BASE(activePowerL1), BASE(voltageR), BASE(currentR), BASE(frequency),
};

below is the association view for this list

Hi,
i have l&t meter(ER300P) 2016 make it working in both optical and rs485 but it take to much time for InitializeConnection around 4 min for both GXDLMSDirector and gurux dlms client example

Dear sir,

I'm trying to connect L&T ER300P meter by Optical probe. It is not able to connect the meter. And it show a pop up message called - Failed to receive reply from the device in given time.

Here is the Error and Device Property Details
1. https://ibb.co/tTSRbvGw
2. https://ibb.co/W4vJJk4v

Hello All,

I was trying to parse an HDLC frame(not DLMS) using GXDLMS DLMS translator.
I found that the online version of the tool parses the frame in a different manner than the offline tool, specifically the HDLC payload.
The online version always deducts the first byte of the payload while the offline tool shows the whole payload as expected.
I'm using HDLC type format 3 which shows that the payload starts right after the 2-bytes Header Check Sum (HCS).

Is there a reason why the offline parsing mechanism differ than the online one ?