As a child of the LonNetwork, the LonTuningPolicyMap (Tuning Policies) operates as in most other drivers. See “About Tuning Policies” in the Drivers Guide for more details. By default, only a single LonTuningPolicy exists, however, you can add new tuning policies (duplicate and modify) as needed.
You assign a tuning policy to LonComponents (nvs) under a Lon device, not on specific proxy points. See LonComponents. One way to do this is using the Nv Manager (default) view of a Lon device. See About the Nv Manager. Also see the next section, Affects of tuning policy, by LonComponents.
By LonComponent, the assigned tuning policy affects behavior as shown in Table 2.
Table 2. Affects of tuning policy on LonComponent behavior
| LonComponent | Affect |
|---|---|
| nci or cp | No affect |
| nvo | No affect |
| nvi with proxy (unbound) | Min/max times and start/on/enable flags apply |
| nvi with proxy (bound) | Min/max times and start/on/enable flags apply |
| nvi linked to nvo (unbound) | Min/max times apply to update |
| nvi linked to nvo (bound) | No affect |
A writable proxy point only updates its target LonComponent when the control point is commanded to a new value, or when (in
the case of an nvi) a write initiates because the maxSendTime was exceeded. Note it will not reassert (update) its “writeValue” if the device’s value is changed by some other means, even if this is detected by a poll.