About the Histories extension

Not all drivers have devices with a HistoryDeviceExt—notably, this exists only if the driver protocol (or device) provides local data logging. Currently, a Histories device extension exists under components NiagaraStation, ObixClient, R2ObixClient, and BacnetDevice (under a BacnetDevice, this extension is named “Trend Logs”).

Note“Database device” components in any of the RdbmsNetwork drivers (rdbSqlServer, rdbMySQL, etc.) also each have a Histories extension. See “Importing and exporting data using the RdbmsNetwork” in the Rdbms Driver Guide for related details.

Figure 45. Histories device extension (NiagaraStation)


Histories device extension (NiagaraStation)

A device’s Histories extension serves as the parent container for history descriptors—components that specify how history-type collections (log data) are imported or exported. By default, it also contains a Retry Trigger, see About the Retry Trigger.

The difference between a history import and history export are as follows:

You create history import descriptors and export descriptors under the Histories extension of a device using separate views. For details, see About Histories extension views.