About tuning policies

A network’s tuning policies configure rules for evaluating both write requests (for example, requests to write to proxy points) as well as the acceptable freshness of read requests that result from polling. Some drivers, such as BACnet, also support different poll frequency groups: Slow, Normal, and Fast. Tuning policies are important because they can affect the status of the driver’s proxy points.

In a network’s Property Sheet, expand the Tuning Policies (Map) slot to see one or more contained tuning policies. Expand a tuning policy to see its configuration properties.

Figure 1. Example Tuning Policies Map (OpcUa)


Some driver networks do not have tuning policies, for example, an RdbmsNetwork, and others, such as the NiagaraNetwork have simplified tuning policies.

By default, a driver’s Tuning Policy Map contains a single default policy. However, you typically create multiple tuning policies, with different property values. Then, when you create proxy points under a network device, you assign a tuning policy to each point (as needed).

CAUTION:

Using only a single (default) tuning policy, particularly with all property values at defaults, can lead to possible issues in many scenarios. In general, you should create multiple tuning policies, configuring each based on the needs of the network’s proxy points and the capabilities of the driver. In particular, tuning policy properties that specify writes from the framework should be understood and applied appropriately.

For example, under a BacnetNetwork you could change the default tuning policy’s Write On Start property from the default (true) to false. Then, duplicate the default tuning policy three times, naming the first copy “Slow Policy”, the second copy “Normal with Write Startup”, and the third copy “Fast Policy”.

In two of those copies, change the Poll Frequency property from Normal to Slow or Fast, corresponding to its name. In the “Normal with Write Startup” tuning policy, change its Write On Start property back to true.

The result would be four available (and different) tuning policies to apply when creating and editing proxy points.