The OutputsFolderType is a subtype of the FolderType defined in OPC 10000-5.

The OutputsFolderType is formally defined in Table 48.

Table 48 – OutputsFolderType definition

Attribute	Value
BrowseName	3:OutputsFolderType
IsAbstract	False
References	NodeClass	BrowseName	DataType	TypeDefinition	Other
Subtype of the 0:FolderType defined in OPC 10000-5
0:HasComponent	Object	3:PublisherCapabilities		3:PublisherCapabilitiesType	O
3:HasOutputGroup	Object	3:<OutputGroup>		3:OutputsFolderType	OP
0:HierarchicalReferences	Variable	3:<OutputVariable>	0:BaseDataType	0:BaseDataVariableType	OP
ConformanceUnits
UAFX FunctionalEntity Base

The OutputsFolderType provides for the grouping of output variables. It shall be restricted to hold only Variables, PublisherCapabilities or nested <OutputGroup >. The OutputsFolder may be empty.

The optional PublisherCapabilities shall only be present on OutputData of the FunctionalEntity. It provides the Publisher capabilities associated with the OutputData and describes additional restrictions of the PublisherCapabilities defined in the FunctionalEntity or AutomationComponent. The restrictions for OutputData only apply if the Connection is established with Variables referenced in OutputData or any subfolders. If an entry is an empty array, then it shall not change the settings defined in the AutomationComponent, FunctionalEntity or if defined in a sub-FunctionalEntity.

<OutputGroup> allows for the nesting of Folders. Nested instances can be used to create a structure of output groups.

<OutputVariable> is a reference to output Variables in this FunctionalEntity. The Variables shall be Organized in this Folder, or the Folder shall reference the Variable via subtypes of the HasChild Reference (HasProperty, HasComponent or other subtypes). The BrowseNames of Variables in this Folder shall be unique within this Folder; the use of nested <OutputGroup > can be used to help accomplish this.

When using PubSub for periodic data with a fixed layout, Strings, ByteStrings, and variable-size arrays can cause problems. Without a defined maximum size for the Variables in a data packet, the fixed size of the data packet cannot be calculated. If using PubSub periodic data with a fixed layout, then the following apply:

• Any Variables that are included in this Folder that have a DataType of String shall include a MaxStringLength property.
• Any Variables that are included in this Folder that have a DataType of ByteString shall include a MaxByteStringLength property.
• It is also recommended that any arrays be defined to have fixed dimensions.

NOTE The Server does define an overall maximum size for Arrays, ByteStrings, and Strings, but typically, this global size is not appropriate for a specific Variable.