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. Node
  3. GXObisValueItem Entries Without MaskSize Appear To Be Interpreted As Bit Flags

GXObisValueItem entries without MaskSize appear to be interpreted as bit flags

By Matt_Plumer , 6 November, 2026
Forums
DLMSDirector

Hello again :),

I have a question about how GXDLMSDirector interprets GXObisValueItem entries in manufacturer OBX settings.

My Values collection contains entries such as:
"<GXObisValueItem>
<Value>0</Value>
<UIValue>Valve open</UIValue>
</GXObisValueItem>
...
<GXObisValueItem>
<Value>64</Value>
<UIValue>Valve closed due to remote or local control</UIValue>
</GXObisValueItem>"

There is no MaskSize defined for these items.
The values are intended as mutually exclusive discrete states. In other words:

actual value = 64
should mean:
Value == 64
and not:
Value contains bit/mask 64

However, GXDLMSDirector appears to interpret these entries using bit/flag semantics and displays them using a CheckedListBox.

I would expect the behavior to be conceptually different depending on whether a mask is defined:
MaskSize not specified / zero:
exact value mapping
received value == GXObisValueItem.Value
MaskSize specified:
bit/mask interpretation
Is the current behavior intentional?

If GXObisValueItem without MaskSize is intended to represent an exact value mapping, it seems that the current UI is treating it as a bit field instead.

Could you please clarify the intended semantics of GXObisValueItem.Value and MaskSize in this scenario?

That's all from me,
Thank you in advance for your replays.

Profile picture for user Kurumi

Kurumi

1 week 5 days ago

Hi, Mask size is used when…

Hi,

Mask size is used when the bit value can be something other than 1 or zero.

Status, error, etc. values are pain because they are not defined in DLMS standards and manufacturers are using all kinds of values and combinations.

BR,
Mikko

Matt_Plumer

1 week 5 days ago

Hi, I understand, but even…

Hi,

I understand, but even if I don't use Mask size, it is "0" in OBIS Object options, don't have it in my .obx file, but it looks like Gurux still reads uint values as a bit field instead.

BR,
Matt

Profile picture for user Kurumi

Kurumi

3 days 8 hours ago

HI Matt, The new Gurux.DLMS…

HI Matt,

The new Gurux.DLMS.Director is released in December. This is fixed for that.

BR,
Mikko

  • Log in or register to post comments
  • Create new account
  • Reset your password

Hire Us!

Latest Releases

  • Thu, 11/19/2026 - 10:57
    Gurux.DLMS.Python 1.0.204
  • Thu, 11/19/2026 - 10:12
    gurux.dlms.c 9.0.2611.1901
  • Tue, 10/13/2026 - 12:00
    gurux.dlms.java 4.0.97
  • Tue, 09/22/2026 - 14:02
    Gurux.DLMS.Net 9.0.2609.2201
  • Mon, 09/21/2026 - 10:18
    Gurux.DLMS.Net 9.0.2609.2101

New forum topics

  • MST Golf Puri Indah Mall 1 | WA 083148835648
  • Landis E650 meter reading over DLMS
  • class_id = 40, version = 2, pushsetup Unparsed data frame
  • GXObisValueItem entries without MaskSize appear to be interpreted as bit flags
  • CheckedListBox incorrectly selects GXObisValueItem Value=0 for non-zero values
More
RSS feed
Privacy FAQ GXDN Issues Contact
Follow Gurux on Twitter Follow Gurux on Linkedin