BACnet Network points with n:history

If BACnet control points in the station have standard history extensions, they already have the implied n:history tag assigned.

If a BACnet device supports trend log objects and is collecting trend data in the BACnet device, the station's BACnet driver may be configured to import the BACnet trend log objects from the remote BACnet device. This is a similar situation to importing histories from remote stations instead of adding a history extension to a network control point.

The BACnet protocol does not support the concept of reading an n:history tag from a remote BACnet device. To map from the control point to the imported BACnet trend data—if you are using BACnet history imports—you must manually assign n:history tags to the BACnet control points. It may be more efficient to use a program object or robot editor to add the n:history tag and dynamically configure the tag value with the history ID of the applicable imported BACnet trend.