DTXr

h1. Changelog 3.1.7

version:3.1.7 (2023-01-09)

* New features:

1. A new function to set the object reliability property from JS:

This feature can be used when sensors and actuators are controlled via JS. In that case it is JS that is responsible for handling the reliability of an object.

Set to other than the default noFaultDetected will cause desired event/alarms to SCADA/BMS.

<pre><code class="javascript">

Controller.setLocalObjectReliability(binaryOutput,0,Reliability.communicationFailure);

</code></pre>

2. A new function to set the overridden flag on an object from JS.

This can be used to signal that someone else than the BACnet stack is controlling the physical state. Eg. a manual switch or a security gate.

Note, when overridden is set on a BinaryOutput any write to presentValue is denied while a BinaryInput works as normal where the flag is only for information purpose (BACnet standard)

<pre><code class="javascript">

Controller.setLocalObjectOverridden(binaryOutput,0,true);

Controller.setLocalObjectOverridden(binaryInput,0,true);

</code></pre>

3. AlarmValue property is now editable on object page for binary object types. ( when intrinsic reporting is enabled)

* Principal changes

The OutOfService property is now used as BACnet standard states for physical points.

This means that if OutOfService is TRUE, a write to a BinaryOutput +is allowed but will not cause any change on physical port.+ (eg. relays will not be engaged)

And if OutOfSerivce is TRUE on a BinaryInput, changes on the physical port +will not be reflected in the BACnet stack.+

* Bug fixes from tickets:

#9 - Polarity

Polarity is now fixed on all object type where applicable. As explained in the ticket, it is the physical port that is affected of this change. Or rather the glue between BACnet object and physical state (aka the LION driver).

* Other bug fixes

The IP change casued an error in LION-devices. Fixed by re-using the channel assignments rather than create a new one.

* Build:

No change