Object Limiter attribute (2) Monitored Value wrong type during write

Project: 
GXDLMSDirector

Hello,

I would like to report the issue with Limiter class attribute Monitored Value write.
In Attached log file when read this attribute returns correctly:
<GetResponse>
<GetResponseNormal>
<InvokeIdAndPriority Value="C1" />
<Result>
<Data>
<Structure Qty="03" >
<UInt16 Value="0005" />
<!--1.0.1.24.0.255-->
<OctetString Value="0100011800FF" />
<Int8 Value="02" />
</Structure>
</Data>
</Result>
</GetResponseNormal>
</GetResponse>

But after changing the monitored value and executing write GXDLMSDirector sends the data with wrong type for Monitored Value structure element Attribute Index instead of Int8 it sends UInt8 (In DLMS Blue Book it is stated that this element is of type Integer or Int8):
<SetRequest>
<SetRequestNormal>
<InvokeIdAndPriority Value="C1" />
<AttributeDescriptor>
<!--Limiter-->
<ClassId Value="0047" />
<!--0.0.17.0.0.255-->
<InstanceId Value="0000110000FF" />
<AttributeId Value="02" />
</AttributeDescriptor>
<Value>
<Structure Qty="03" >
<Int16 Value="0005" />
<!--1.0.15.24.0.255-->
<OctetString Value="01000F1800FF" />
<UInt8 Value="02" />
</Structure>
</Value>
</SetRequestNormal>
</SetRequest>

If you need more info please contact me.
Best regards,
Vanja Ninkovic
MIGMA s.p.

Status: 
Closed (fixed)
Priority: 
Normal
Category: 
Bug report
Component: 
Code
Reporter: 
nine
Created: 
Tue, 03/19/2019 - 13:12
Updated: 
Wed, 03/20/2019 - 10:58

Comments

Kurumi's picture

Hi,

You are right. Thank you from this info. This is fixed and we have started tests. We'll release new version tomorrow where this is fixed.

BR,

Mikko

Hi,
Thanks for prompt response and action, GXDLMSDirector is really good application and I like using it.
I have few more issues and I will post them soon for review.

Administrator's picture

Status: Active » Closed (fixed)