Niagara History Export Manager view

This view is available only on a station’s Histories extension (apart from database device components in some RdbmsNetwork drivers) of the NiagaraNetwork (niagaraDriver).

NOTE: If you are using the BACnet driver, Niagara histories in the local station can also be exposed to all networked BACnet devices as BACnet Trend Log objects. However, this is done using a different view under the Local Device component in the BacnetNetwork. Refer to the Niagara 4 BACnet Driver Guide for more details.

Like other managers, the Niagara History Export Manager is a table-based view.

Each row typically represents a history export descriptor. Each descriptor specifies how data from a local history is exported (“pushed”) from the station to a selected station, where it appears as a history. You use this view to create, edit, and delete history export descriptors. Each export descriptor you add results in the creation of a history on that remote station.

Following station configuration, this view provides a status summary for exporting local histories. You can also use it to issue manual Archive commands to one or more history descriptors. This causes an export (push) of history data into the selected histories at the remote station.

NOTE: Only history export descriptors appear in the History Export Manager view—any other components that may also reside under Histories do not appear. For example, you do not see the default Retry Trigger component, or history import descriptors. However, you can use the histories Property Sheet or the Nav tree to access those items.

At the bottom of the view, the New button lets you manually create new export descriptors in the station. Edit lets you edit one or more export descriptors. Discover, Add, and Match are also available, (these work similarly as in the Point Manager view). Archive is available to manually export (push data) into one or more selected histories.

NOTE: The view toolbar also contains icons for these button commands, as shown here. Positioning the mouse pointer over an icon displays the icon label.

Niagara History Export Properties

The following are properties of history export descriptors available in the Edit or Add window.

Figure 56. Add export descriptors window

Property	Value	Description
Name	Text string followed by numbers	For a history originating in the local host station, the name begins with Local_ . If Discovered for import, typically left at default. For a system history export, originating in the remote station, the name begins with NiagaraSystemHistoryExport. NOTE: : There is a possibility of Niagara history import/export failures, with history names above the specified character limit for an older platform.
HistoryId	Text in two parts: /stationname/historyname	Specifies the history name in the local station’s History space, using two parts: “/<stationName>” and “/<historyName>”. If Discovered, station name is “^” (a character representing the device name of the parent container) and history name reflects the source history name. Typically, you leave both properties at default values, or edit the second (<historyName>) property only.
Execution Time — Daily (default)	Time Of Day hours:minutes:seconds AM/PM timezoneRandomizationDays Of Week	Defines when the daily export or import automatically takes place. The hours follow a 24–hour clock.
Execution Time — Interval	Interval hours:minutes:secondsTime Of DayDays Of Week	Defines the amount of time between automatic exports or imports. Hours may number in the thousands.
Execution Time — Manual	N/A	Requires human intervention to initiate a history export or import.
Enabled	`true` or `false`	Activates (`true`) and deactivates (`false`) the object (network, device, point, component, table, schedule, descriptor, etc.).
System Tag Patterns	Text	Specifies one or more text strings matched against text values in “System Tags” properties of local history extensions (modifiable only for a NiagaraSystemHistoryExport descriptor). Matching text patterns result in histories exported into the remote History space.

NOTE: The Capacity and Full Policy of any exported history (created on a remote station) are determined by rules under that station’s NiagaraNetwork History Policies, and are set at creation time only.