6.4.7 FunctionalEntityCapabilitiesType
The FunctionalEntityCapabilitiesType extends the FolderType defined in OPC 10000-5. It shall be restricted to holding only Variables that reflect the capabilities of the FunctionalEntity.
The FunctionalEntityCapabilitiesType is formally defined in Table 60.
| Attribute | Value | ||||
| BrowseName | 3:FunctionalEntityCapabilitiesType | ||||
| IsAbstract | False | ||||
| References |
Node
Class | BrowseName | DataType | TypeDefinition | Other |
|---|---|---|---|---|---|
| Subtype of the 0:FolderType defined in OPC 10000-5 | |||||
| 3:HasCapability | Variable | 3:<Capability> | 0:BaseDataType | 0:BaseDataVariableType | OP |
| 3:HasCapability | Variable | 3:FeedbackSignalRequired | 0:Boolean | 0:BaseDataVariableType | O |
| ConformanceUnits | |||||
|---|---|---|---|---|---|
| UAFX FunctionalEntity Base |
<Capability> - is an OptionalPlaceholder (defined in OPC 10000-3 ) to indicate that additional capabilities may be added by this document, by a companion specification or by a vendor application. These capabilities shall include a Description, and they follow all of the rules associated with an OptionalPlaceholder.
If the optional FeedbackSignalRequired is present and set to TRUE, the FunctionalEntity requires a feedback signal for all Connections. A feedback signal is represented by the reception of either data or a heartbeat. The following connection types (see 5.5.1) support feedback: bidirectional, unidirectional with heartbeat, unidirectional Subscriber, and autonomous Subscriber. If FeedbackSignalRequired is missing or set to FALSE, the connection types unidirectional Publisher and autonomous Publisher are also supported.