Skip to main content
Home
for DLMS smart meters
Open source solutions for DLMS smart metering

Main navigation

  • Home
  • Products
  • About us
  • Open Source
  • Community
  • Forum
  • Downloads
User account menu
  • Log in

Breadcrumb

  1. Home
  2. Bug In ParseObjects() C#

Bug in ParseObjects() C#

By Rahuls , 18 October, 2024
Forums
Gurux.Net

Hello mikko,

I think maybe its a bug

if im reading object using Read() i will get correct value since there are 2 timezone values.
Read(it,5)
obj
{Gurux.DLMS.Objects.GXDLMSDayProfile[1]}
[0]: {1 10:00:00.000 AM 0.0.10.0.100.255 1 8:00:00.000 PM 0.0.10.0.100.255 2}

But on calling ParseObjects(), i am just receiving just 1 timezone value.

ParseObjects(it.LogicalName, attrIndex, obj)
"[{\"DayId\":1,\"StartTime\":\"10:00:00.000 AM\",\"ScriptCode\":\"0.0.10.0.100.255\",\"Selector\":1}]"

ofcourse i cab skip this call and use directly Read(), but parseobjects is useful for parsing other octet values.

thanks

Profile picture for user Kurumi

Kurumi

1 year 9 months ago

Hi, ParseObjects is used to…

Hi,

ParseObjects is used to parse the association view and you don't need that. Values are updated to the COSEM object when you read the value.

BR,
Mikko

  • Create new account
  • Reset your password

Hire Us!

Latest Releases

  • Mon, 08/17/2026 - 11:28
    Gurux.DLMS.Python 1.0.202
  • Mon, 08/17/2026 - 09:47
    gurux.dlms.cpp 9.0.2608.1701
  • Mon, 08/17/2026 - 09:25
    gurux.dlms.c 9.0.2608.1701
  • Mon, 07/27/2026 - 12:37
    gurux.dlms.cpp 9.0.2607.2701
  • Thu, 07/23/2026 - 16:19
    gurux.dlms.java 4.0.96

New forum topics

  • DLMS Image Transfer: “byte must be in range(0, 256)” with 512-byte block size in Python
  • Connecting to meter using Wrapper
  • DLMS Server / Meter emulation in Golang library
  • Unknown Baudrate
  • negative indexing for custom method/attribute
More
RSS feed
Privacy FAQ GXDN Issues Contact
Follow Gurux on Twitter Follow Gurux on Linkedin