Monitored value for Limiter Objects is not set while fetching the object

By sc-anokum, 12 March, 2024
Forums
Gurux DLMS for Java

Hi Mikko,

while fetching limiter object using the command,
GXDLMSLimiter data = new GXDLMSLimiter("0.0.17.0.1.255");
Object val = read(data, 2)

it is setting val as null, though on parsing the hex messages, it shows that correct value was received.

below are the hex messages exchanged :
TX: 11:26:16.264 00 01 00 01 00 01 00 0D C0 01 C1 00 47 00 00 11 00 01 FF 02 00
RX: 11:26:16.801 00 01 00 01 00 01 00 13 C4 01 C1 00 02 03 12 00 03 09 06 01 00 1F 07 00 FF 0F 02

Kurumi

7 months 1 week ago

Hi,

I believe that register object 1.0.31.7.0.255 does not exist in the association view and that is not created because of that.
In the next release, the monitored value is created if it's not in the association view.

BR,
Mikko

sc-anokum

7 months 1 week ago

Hi Mikko,

thanks for the update, can i ask if it's in the pipeline?, as i can see the same in dlms director but isn't populated using the java library.
I have attached the screenshot from director

Image

Kurumi

7 months ago

Hi,

That is implemented differently between C# and Java. This is changed for Java and it's updated for the next version. Most meters include all objects in association view and this is not causing problems. Your meter is an exception from this.

BR,
Mikko