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.