The SupervisorExportTagNetworkExt is required for a Supervisor station to utilize export tags used in remote subordinate (JACE) stations. It is the only component you copy directly from the exportTags palette into a Supervisor station. Place it in the root of the NiagaraNetwork, as shown in Figure 12.
The property sheet is the default view (no specialized views), with properties described as follows:
-
Status
Read-only status of the network extension, typically “ok”.
-
Category Filters
Container for any CategoryFilter export tag components, where usage is optional. The default view is the Category Filter Manager, for adding, editing, and deleting CategoryFilter components.
For more details, see the next section CategoryFilters.
-
Alarm Source Info
A container slot you can use to differentiate export tag alarms (from a failed Join) from other alarms in the station. See “About network Alarm Source Info” in the Drivers Guide for general details.
The Supervisor’s AuditLog also records both successful and failed “exportTagJoin” jobs, including information on changed slot
values (old and new), and also the originating user.
-
Station Folder Path
Allows usage of “Station Info” metadata in remote JACE stations to automatically, upon a Join, create NiagaraStationFolders (device folders) on the Supervisor, to organize NiagaraStations under them. To do this, this property value must use “ord variables” that correspond to known string slots that have been added in the remote stations, under each JoinProfile, “Station Info” slot.
Typically, this feature is useful on extremely large systems, where a Supervisor may have many subordinate JACE stations.
-
The default “
slot:” is used for normal operation, meaning without creation of station folders. -
Optionally (although rarely used), you can append explicit text string(s), used by any subordinate station Join, regardless of its JoinProfile. For example: “
slot:test/Example” will put all joined NiagaraStation components in a NiagaraStationFolder named “Example”, itself a child of another NiagaraStationFolder named “test”. -
More typically, you append one or more ord variables, using a “
$()” syntax for each hierarchical level of NiagaraStationFolder you want created. To work, each ord variable must match the name of a string slot added to the “Station Info” container under a remote station’s JoinProfile.For example, a value of: “
slot:$(State)$(City)” that corresponds to remote Station Info string slots “State” and “City”, will result in two levels of NiagaraStationFolders. Each folder will be named the value of that slot, for example a “Virginia” folder may have subfolders “Richmond” and “Norfolk”, each of which contains one or more NiagaraStation components.For related details, see StationInfo.
-
-
Profile Export Tags
Specifies whether to include “Join time” statistics in the job log for each Join, reported in milliseconds (ms) for each item evaluated in a “Pre-Join”, “Join Time”, and “Post Join” fashion. The default is false, meaning no Join time statistics. Enabling may be useful in some cases where slower connections between the Supervisor and subordinate hosts are used, for example via GPRS modem.
-
Log Limit
Specifies the maximum (line) entries allowed in any job log in the Supervisor for any export tag Join, where the default is 600. If a job log exceeds this limit, earlier entries are not captured. Range is from 1 to 10,000. Note that if Profile Export Tags (above) is true, many additional line entries result.