I found, that DLMSDirector doesn't show monitored_value attribute of RegisterMonitor class correctly, if monitored value is attribute from class, other than Data, Register, ExtendedRegister or DemandRegister.
DLMS specification allow to use any class attribute for monitored value.
For example, I need to monitor attribute avaliable_credit in Account class.
DLMSDirector doesn't handle this case correctly.
Yes, there is a filter because it's hard to find the correct object if all the objects are listed.
Do you want to add something else than an Account object?
It's easy to modify the filter.
I understand you use the filter to reduce number of objects in selection list.
But, maybe it make sense to add new classes to filer on RegisterMonitor object reading ?
If RegisterMonitor object used some class for monitored value, you can add this class to filter.
Hi,
Hi,
Yes, there is a filter because it's hard to find the correct object if all the objects are listed.
Do you want to add something else than an Account object?
It's easy to modify the filter.
BR,
Mikko
Hi,
Hi,
Right now I need only Account object.
I understand you use the filter to reduce number of objects in selection list.
But, maybe it make sense to add new classes to filer on RegisterMonitor object reading ?
If RegisterMonitor object used some class for monitored value, you can add this class to filter.
Regards,
Vitaly
Hi,
Hi,
There is a check box that will show all the target objects in the next version.
It's released next week.
BR,
Mikko