Starting in AX-3.2, polling of Bacnet proxy points uses the Basic Bacnet polling design, with the following key points:
By default, any Bacnet proxy point polls only the (one) single, configured property for polling. Thus, if you specify “presentValue,” that is all the point’s out displays from BACnet—no native object status,
or currently active level (“bac=n”, if a commandable object), affect the point display.
However, as needed you can add either or both of these extra polled properties, and/or others, by editing the facets of proxy points. See Facets usage to poll additional properties. Also, note that if adding statusFlags, there is a point “status merge”—see Status merger for Bacnet proxy points.
Using an “added slot” method on a Bacnet ProxyExt, it is now possible to poll for data outside the normal boundaries of a single object poll, such as sometimes needed in “Event Enrollment” scenarios. For more details, see Advanced “add DOPR slot” to ProxyExt method.
Efficiencies in polling come about from a “PollListEntries” method, where any “pollable” component (proxy points, Config objects) that is subscribed is added by its poll service into aggregate poll list objects (by containing device), where they are better processed. In addition, “dibs” polling can make more efficient use of bandwidth by using ReadPropertyMultiple to poll objects.
For the most part, these efficiencies do not affect station polling configuration (however, starting in AX-3.2, the “maxDevicePollSize” property of a BacnetDevice, if still present, has no significance).
Copyright © 2000-2016 Tridium Inc. All rights reserved.