When “tagging up” a subordinate (JACE) station opened in Workbench, you can copy (drag and drop) from the exportTags module’s palette, shown in Figure 11.
Often, only a few types of export tag extensions are used—for example; PxViewTag, HistoryImportTag, and possibly PointTag.
Each of these components is briefly described as follows:
SupervisorExportTagNetworkExt
This is the only component that goes in the Supervisor station (not subordinate station). You copy one into the NiagaraNetwork of the Supervisor. For configuration details on its properties and child components, see SupervisorExportTagNetworkExt.
SubordinateExportTagNetworkExt
You copy one into the NiagaraNetwork of a subordinate station. It provides two special views for working with export tags, and also produces a JoinProfile container under each NiagaraStation component in the station’s NiagaraNetwork. For configuration details on its properties, child components, and views, see SubordinateExportTagNetworkExt
PxViewTag
Use this export tag to export any PxView in the subordinate station up to the Supervisor station. Copy it on the folder/container in the JACE station with the PxView, then specify it as a view on any designated folder/container under the “profile.bog file” (determines the NiagaraStation structure on the Supervisor). Several properties in the tag require configuration.
PxViewTags are a powerful feature, and automatically encapsulate several other functions, including “on demand” Niagara virtual components for real-time values, along with importing of any graphics files used in the PxView. The resulting “virtual” or “substitute PxView” operates like the original PxView in the subordinate station, without the overhead of Niagara proxy points.
In some use cases, it is possible that PxViewTags may preclude the need for PointTags and ComponentTags, comprising the vast majority of export tags in a subordinate station. For details, see PxViewTags.
PointTag
Use a PointTag to export any control point or proxy point in the subordinate station as a Niagara proxy point in the Supervisor station. Simply copy the PointTag onto the source point in the subordinate station (for example, a Lonworks proxy point or BACnet proxy point). For details, see PointTags.
HistoryImportTag
Use a HistoryImportTag to export a particular history in the subordinate station. Simply copy the HistoryImportTag onto the point’s history extension, or alternatively, under the history extension’s “HistoryConfig” child container. For details, see HistoryImportTags.
SystemHistoryImportTag
Use a SystemHistoryImportTag to export groups of histories in the subordinate station that have matching “System Tags”, utilizing a feature introduced starting in AX-3.4. You can copy a SystemHistoryImportTag anywhere in the station. For details, see SystemHistoryImportTags.
ScheduleImportTag
Use a ScheduleImportTag to designate an existing schedule on the subordinate station as a “master”, thereby creating a “slave” schedule on the Supervisor station. Copy a ScheduleImportTag onto any existing schedule (BooleanSchedule, NumericSchedule, and so on) in the station. Usage of this export tag is expected to be infrequent. For details, see ScheduleImportTags.
ScheduleExportTag
Use a ScheduleExportTag to associate (or create) a “master” schedule on the Supervisor station with a new “slave” schedule on the subordinate station. Copy a ScheduleExportTag onto the Niagara ScheduleImportExt descriptor of a new schedule (BooleanSchedule, NumericSchedule, and so on) in the station’s Schedules extension under the NiagaraStation for the Supervisor. For details, see ScheduleExportTags.
FileImportTag
Use a FileImportTag to export a specific file or folder(s) of files to the Supervisor. Copy the FileImportTag anywhere under the component space (Config) of the subordinate station, and configure the source file ord in the “File” property. Note that file imports can also automatically occur as a result of using PxViewTags. For details, see FileImportTags.
ComponentTag
Use a ComponentTag to export a copy of a component other than a control point or proxy point, for example a kitControl component or Program component.
Component tags do not create a proxy. If you change properties on the component with the tag in the source station, those
changes are not reflected in the copy of the component located in the Supervisor station.
Simply copy the ComponentTag onto the source component. You can specify the exported component to be in any designated folder/container under the NiagaraStation (that represents the subordinate). For details, see ComponentTags.
ExportTagProgram
This is an example Program component with a ComponentTag already applied, to demonstrate one application of the ComponentTag. Usage allows automating any “post join” operations from any additional supplied program logic, within the “template” design of the program code. Use is targeted for users who are experienced with Program components. Possible post-join operations might include creating links. For details, see ComponentTag example (ExportTagProgram).