Limiter Threshold Normal value change is wrong type with new monitored value

Project: 
GXDLMSDirector

Hi,
I would like to report issue with Limiter Threshold Normal raising error during value change after new Monitored value has been changed.
Reproduction steps:
1. Limiter initial monitored value is 1.0.72.7.0.255 L3 Voltage with Value type UInt16, and according to Blue Book all Threshold attributes have same type as monitored value Uint16 this is ok for now.
(" Limiter before monitored value change log.txt " and " Limiter before monitored value change.PNG").
2. With new updated version monitored value can be changed and we change it to 1.0.1.24.0.255 Li Active Power Average with Value type UInt32 (" Limiter before monitored value write.PNG" and "Limiter after monitored value write log.txt").
3. After above change read Limiter again and from log all Threshold attributes now have same CHOICE type as monitored value UInt32, this is all good up to now. ("Limiter after monitored value change log.txt")
4. Now I want to enter new Threshold Normal value change it from 240V to 66000W, upon enter application raises error shown in "Limiter error when entering new threshold normal value.PNG".

It seams that application does not update type info on Threshold attributes after monitored value attribute change, and still thinks that Threshold normal is of old type UInt16 and raises error that 66000 number trying to enter is larger from 65535 that UInt16 type can hold, but in fact application should determine its type automatically based on Monitored Value type (as described in DLMS Blue Book) on every Monitored Value change.

If you need more info please let me know.

Best regards,
Nine

Status: 
Closed (fixed)
Priority: 
Normal
Category: 
Bug report
Component: 
Code
Reporter: 
nine
Created: 
Wed, 04/03/2019 - 09:05
Updated: 
Thu, 04/04/2019 - 13:48

Comments

Administrator's picture

Status: Active » Closed (fixed)