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

The InputsFolderType is formally defined in Table 47.

Table 47 – InputsFolderType definition

Attribute	Value
BrowseName	3:InputsFolderType
IsAbstract	False
References	NodeClass	BrowseName	DataType	TypeDefinition	Other
Subtype of the 0:FolderType defined in OPC 10000-5
0:HasComponent	Object	3:SubscriberCapabilities		3:SubscriberCapabilitiesType	O
3:HasInputGroup	Object	3:<InputGroup>		3:InputsFolderType	OP
0:HierarchicalReferences	Variable	3:<InputVariable>	0:BaseDataType	0:BaseDataVariableType	OP
ConformanceUnits
UAFX FunctionalEntity Base

The InputsFolderType provides for the grouping of input variables. It shall be restricted to hold only Variables, SubscriberCapabilities or nested <InputGroup>. The InputsFolder may be empty.

The optional SubscriberCapabilities shall only be present on InputData of the FunctionalEntity. It provides the Subscriber capabilities associated with the InputData and describes additional restrictions of the SubscriberCapabilities defined in the FunctionalEntity or AutomationComponent. The restrictions for InputData only apply if the Connection is established with Variables referenced in InputData 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.

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

<InputVariable> is a reference to input 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 <InputGroup > 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.