Create a Tuning Policy - User Guide

 The user will head into the Tuning Policy Tree and select on Add button

This will open a pop-up called Create a Tuning Policy.

Once completed, the tuning policy will be displayed in a list underneath the tuning policy tree

Tuning policy options are:

Dis Name for Tuning Policy: This would be the name of the tuning policy. We advice the user to be careful with the name of the policy, so that it doesn't create confusion when choosing the Policy.

Enable Min Write Time: If the user needs to apply the min write time, then they can enable it by selecting this checkbox.

Min Write time in seconds: The minimum amount of time set to write the points values (between 0s and 10000s). Meaning if you have points that change often like every second, it won't write the value until the minTime is reached. Only works if “Enable Min Write Time” is enabled.

Enable Max Write Time: If the user needs to apply the max write time, then they can enable it by selecting this checkbox.

Max Write time in Minutes: The maximum amount of time set to write the points values (maximum 5000min). Meaning if you have points that didn't have a successful write after 10 mins (if maxWriteTime was set to 10 mins), it will write the value when maxTime is reached regardless if it changed or not. Only works if “Enable Max Write Time” is enabled.

Schedule Write: This applies only for schedule object points where the user desires to sync the FIN schedule down to the device (ie - Haystack or BACnet schedule objects). This is not for regular points that are not objects. The reason is if the tuning policy has a writeSchedule tag, it sends the whole schedule data which schedule objects know how to handle it. Whereas normal boolean points don't so it will break and not update.

Enable Poll Time: If the user needs to apply the poll time, they can enable it by selecting this checkbox.

Poll Time: How often you want the connector to poll curVal of the points (can be between 5s and 1h).

The recommended poll times for the tuning policies are as follows (recommend prime numbers):

Conn Default Policy - 61 seconds (slow)

Sensors - 13 seconds (fast)

Commands - 23 seconds (medium)

Setpoints - 47 seconds (slow)

Schedule - 7 seconds (fast)

Additional tuning policy tags that are available (not in the UI yet). The user will have to add these tags manually if they want to use them:

bacnetDisableCov (marker - BACnet specific): Applied to ConnTuning to disable the COV for a specific point or all the points in a connector. Works in ConnTuning applied on point or on connector, if both are present the tag value from the point's ConnTuning will have priority.

writeOnOpen (marker): Issue a write every time the connector transitions from closed to open. This policy is typically used when the remote device stores writes in RAM only and needs to be re-written after reboots. Works in ConnTuning applied on connector.

writeOnStart (marker): Issue a write when the system first starts up. If omitted then the system suppresses the initial priority array evaluation. Works in ConnTuning applied on connector.

These can be added by selecting the 'i’ icon of the tuning policy record to open the Property Editor. From the Property Editor, the user can also modify any of the other tags available.