18.02.2018, 19:59
Hi,
My reaction was based on some experience more then a year ago, so i just runned some tests to see what is happening. I can't update RD also anymore, but that's what we did on the Sauter project, not sure if BACnet module is changed after that. Also in my automation server the flags are triggered now.
I can also see why, as we are writing to a array property and not to the value property, so the value property gets updated from the array override, and the overridden flag is triggered. When you write directly to the value property the status flag is normal again. So there is nothing wrong, and all functions as BACnet should work, its just a logical result of writing to the array property (1 to 16). You can't set the controller to 17 (value property) like in our Ecostruxure Building MPM.
However i don't care about status flags, it's just a indicator and not a alarm or something and beside just showing the state it does nothing further..
BR,
Erwin
My reaction was based on some experience more then a year ago, so i just runned some tests to see what is happening. I can't update RD also anymore, but that's what we did on the Sauter project, not sure if BACnet module is changed after that. Also in my automation server the flags are triggered now.
I can also see why, as we are writing to a array property and not to the value property, so the value property gets updated from the array override, and the overridden flag is triggered. When you write directly to the value property the status flag is normal again. So there is nothing wrong, and all functions as BACnet should work, its just a logical result of writing to the array property (1 to 16). You can't set the controller to 17 (value property) like in our Ecostruxure Building MPM.
However i don't care about status flags, it's just a indicator and not a alarm or something and beside just showing the state it does nothing further..
BR,
Erwin