Station Slot Path considerations

The “Station Slot Path” property in some export tag types can accept a manually-typed path. In other words, if you type in a slot path value in one of these export tags, upon a Join if the corresponding containers (folders, archive folders, point folders) do not exist, they are dynamically created in the Supervisor station. This occurs regardless of whether they exist (or not) in the JACE station’s “profile.bog” file.

NoteThis differs from the initial AX-3.5 implementation of export tags, where a “Station Slot Path” property had to be reflected in the JACE’s “profile.bog” file—otherwise, the Join failed to export that item.

This “dynamic folder” creation results vary, depending on export tag type.

In the case of the PxViewTag and ComponentTag (which create ordinary folders), you are free to specify any slot path in the Station Slot Path property, starting with slot:

For example slot:Bldg_A/Floor_1

Create two levels of folders directly under the NiagaraStation that represents this JACE station (assuming these folders do not already exist).

In the case of the PointTag and HistoryImportTag or SystemHistoryImportTag, you must retain the leading NiagaraStation “device extension name” (points or histories), for things to work correctly.

You can also use special “BFormat” values within manually-typed Station Slot Paths. See BFormat options in Station Slot Paths.