The Histories extension of an R2ObixClient is where you can import data from the
R2 station’s log objects, as well as existing archives from its appdb (if it has the DatabaseService), by adding history import
descriptors. The default view of Histories is the ObixHistoryManager (Figure 2-20), where you specify which discovered logs
and archives you want to import, using the familiar oBIX “lobby” tree in the Discovered pane.
Figure 28. ObixHistoryManager is for importing
R2 logs and/or archives into the history space
NOTE: The ObixHistoryManager and created history import descriptors operate as they do in the history import views and descriptors
in the NiagaraNetwork and BacnetNetwork. For related details, see the NiagaraAX Drivers Guide sections “About the Histories extension” and “History Import Manager”.
Each added descriptor (after archived in
AX) produces one history in the station’s local history space, organized by default under a container with the same name as
the source R2ObixClient. The following figure shows an example of how the created histories appear in the
AX station’s history space.
Figure 29. By default, imported histories under container with name of ObixClient (often, stationName).
Figure 2-22 shows an example add/edit dialog for an ObixHistoryImport descriptor with default values, where the import descriptor
name matches the source
R2 Log object name, and the history ID is a combination of the R2ObixClient’s name / Log object name.
Figure 30. Add/Edit dialog for importing an
R2 log or archive by import descriptor
Note that an R2ObixClient histories discover includes an
R2 station’s “AuditLogService” and “ErrorLogService,” in addition to logs created by Log objects like “AnalogLog, BinaryLog,”
and so on. See the next section “ObixClient history import notes” for additional notes.
