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 trying to pull Billing Profile from 2 meters which consists of 103 objects & 64 objects from an embedded device. As a process i am reading capture objects and going for data read.

Data from the meter is completely read and during the parse stack at the embedded module is throwing an OUT_OF_MEMORY error (0X0104).

Meter 1 Info
Communication Mode:- Serial (UART)
Communication Protocol:- TCP Wrapper
Communication Interface:- NIC Port

Hi,
i see that the getting Generic Profile value using ReadRoiwbyEntry has different encoding parameters on cpp and c implementation, i am addressing to:
In cpp: https://github.com/Gurux/Gurux.DLMS.cpp/blob/master/development/src/GXD… it encodes the start index and count as UINT32.

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,
is there support to negative method index (in the italian standard) in https://github.com/Gurux/GuruxDLMS.c?

Thansk,
Alessandro

Hi,

I am trying to perform firmware upgrade to the meter, using the C source code available in github by modifying the code slightly.

Modifications:-
1. Commented all objects read. Post connection establishment, i have called imageupdatefromfile() function.

Hi,

I am trying to update the meter firmware using GuruxDLMS.c library. I am able to establish connection with the meter in Firmware Upgrade mode. Post this, while i am trying to read Image transfer enable status, block size and image transferred block status, meter isn't responding for the one of the TX sent by stack and stack is hanging in com_read function while returning with DLMS_ERROR_CODE_RECEIVE_FAILED error.

Request you let me know what could be the reason.

Please find below details for your analysis.

Hi Mikko, i am back working on the itron meter data reading. I created new forum post because i can't reply on the old one. 
After trying out the update, the issue on reading Itron SL7000's load profile (0.0.99.1.0.255) still persists
- if i read capture objects first (index 3), it returns error 13 : DLMS_ERROR_CODE_ACCESS_VIOLATED
- if i read without it, it returns error 258 : DLMS_ERROR_CODE_INVALID_PARAMETER, but i can see some data in the traces, and i can use GXDLMSTranslator to translate and get the data

Hi,

I use Gurux.c library and when i tested it with gxdlmsdirector ctt test
The Communication is ok between this two (Device and Software)
But when software was sent only this :

7e a0 2f 00 02 0e d3 03 10 5e 66 e6 e6 00 c8 1e
30 00 00 00 0c 63 a9 c6 fe 56 8e 96 a8 9f fe ed
1b c9 a9 a3 15 20 64 85 be 96 2f 07 00 c8 b8 6e
7e

Hi,

I’ve been working with the GURUX library for ANSI C and ran into an issue.

When I try to set the value of an object class_id = 1 and an attribute of type OCTET_STRING, I’ve noticed the following:

If I read the object first and then set it, inside svr_postWrite(dlmsSettings* settings, gxValueEventCollection* args) I get args->size == 1.

If I don’t read first and I write directly, then in the same function args->size == 0, which means no post-processing happens after the write.