Below are the tuning configurations we use but can be adjusted accordingly.

...

BACnet Tuning

If you want to assign the tuning policies we recommend for BACnet IP follow the below. Keep in mind, not all networks are the same and sometimes policies will have to be adjusted accordingly to not overload the network. Networks with MSTP devices will have to be slowed down, even more, depending on the baud rate being utilized. The majority of the time it is the MSTP networks that need tuning vs BACnet IP.

The tuning setup allows the connectors to be COV based if COV is available and enabled on the devices. If COVs fail, it would then switching switch to polling on the intervals specified below. If using COV, make sure the “cov_increment” property on the analog object is configured to a proper value in the device side.

1.  Download Download bacnetTuning trio file unless you want to make you're own and assign them manually.

2. Upload the trio file to your database via folio app the Folio app → Launch and then by selecting on the Upload buttonImage Removed.

3. When selected, a pop-up window will be displayed where the user can:

...

4. If the user already has tuning policies, they can remove those following the below steps IF if they want to replace those with tuning policies found on this trio file. Reason The reason is the function that will be adding the tuning policies will not replace existing connTuningRefs already added to objectsthe points/connectors. If you don't currently have tuning policies, then you can skip this step.

• Open folio the Folio app

• Open the tools to → Advanced → Batch Tagging → Apply Batch Tags

• Then for the filter to find records field, we'll type in connTuningRef because want to find anything that already has a tuning policy on it.

• Then for the tag to remove, we'll type in -connTuningRef. With the minus/hyphen in front of the tag means to remove said tag.

• Should look like below and apply once done.

...

5. When the trio file is uploaded, the user will run finAssignConnTuning() in the query field.

...

6. It will return how many records have assigned tuning policies.

...

...

...

7. The user would then disable and re-enable all of the connectors. If there are a lot of them, we recommend to enable certain amount at a time.

8. Then we recommend to adjust the APDU Timeout property found in the BACnet Global Config window to 6000 milliseconds from 3000 if MSTP devices are on the network. As well as adding the bacnetDisableCov marker tag on all the tuning policies to put them in Polling mode.

...

The stats for the tuning policies are as follows (recommend prime numbers so that they don’t overlap as often):

• Conn Default Policy (connDefault) - 61 seconds

  Contains following tags on tuning policy itself.
  

• actorTimeout (number + duration, make sure to include unit "s") - 3 seconds.
  This can be configured between a range of 1-5 seconds with lower being better with IP type devices. The default is 5 seconds. This determines how long the connector waits before it throws an error. The shorter the duration, the quicker it'll fail if the device or network don't respond. Try setting it to 1-3 seconds. In regards to MSTP devices on the network, depending on baud rates its best to slow this down even more maybe 20-60 seconds or so. With baud rates on the lower end like 38400, should be around 60 seconds.

• bacnetRetryCount (number) - 3
  This can be configured between a range of 1-5 with higher being better. The default is 1. This determines how many times a connector will retry to connect before it throws an error. The higher amount of retries will give the connector more chances to re-establish connection with the device or network. Try setting it to 2-3 retries.

bacnetDisableCov (marker - optional and not in trio file)
If this is added to the connDefault tuning policy, then it will force the connectors to Polling only and disable COV. The user will have to add this manually if they want to disable COV.

• Sensors (fastSensor) - 13 seconds

• Commands (mediumCmd) - 23 seconds

• Setpoints (slowSp) - 47 seconds

• Schedule (scheduleTuning) - 7 seconds (does not contain writeSchedule tag)

• Schedule Objects (scheduleObjectTuning) - 7 seconds (contains writeSchedule tag)

...

When it comes to tuning Haystack connectors, it only requires a single tag that goes on the connector itself. Make sure to disable and re-enable the connector(s) afterwards.

• haystackPollFreq (number tag with unit "s" for seconds) - 5-15 seconds recommended. Adjust as needed.