The ConnectionManagerType is formally defined in Table 77.
Table 77 – ConnectionManagerType definition
Attribute |
Value |
||||
BrowseName |
4:ConnectionManagerType |
||||
IsAbstract |
False |
||||
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
Other |
Subtype of the 0:BaseObjectType defined in OPC 10000-5 |
|||||
0:HasComponent |
Object |
4:ConnectionConfigurationSets |
|
0:FolderType |
M |
0:HasComponent |
Object |
4:ConnectionManagerConfiguration |
|
4:ConnectionManagerConfigurationType |
O |
0:HasComponent |
Method |
4:EditConnectionConfigurationSets |
Defined in 6.7.4 |
O |
|
0:HasComponent |
Method |
4:ProcessConnectionConfigurationSets |
Defined in 6.7.5 |
O |
|
0:HasComponent |
Object |
4:Capabilities |
|
4:ConnectionManagerCapabilitiesType |
O |
0:HasComponent |
Variable |
4:AggregatedCurrentState |
0:Boolean |
0:BaseDataVariableType |
O |
0:HasComponent |
Object |
5:Diagnostics |
|
5:FunctionalGroupType |
O |
0:HasComponent |
Object |
4:ConnectionManagerLog |
|
0:LogObjectType |
O |
|
|
|
|
|
|
0:GeneratesEvent |
ObjectType |
4:CloseConnectionErrorEventType |
|||
0:GeneratesEvent |
ObjectType |
4:EstablishConnectionErrorEventType |
|||
ConformanceUnits |
|||||
UAFX ConnectionManager Base |
The components of the ConnectionManagerType have additional subcomponents, which are defined in Table 78.
Table 78 – ConnectionManagerType additional subcomponents
BrowsePath |
References |
Node Class |
BrowseName |
DataType |
TypeDefinition |
Others |
5:Diagnostics |
0:HasComponent |
Variable |
4:EstablishCallCount |
0:UInt32 |
0:BaseDataVariableType |
O |
5:Diagnostics |
0:HasComponent |
Variable |
4:EstablishCallFailedCount |
0:UInt32 |
0:BaseDataVariableType |
O |
5:Diagnostics |
0:HasComponent |
Variable |
4:CloseCallCount |
0:UInt32 |
0:BaseDataVariableType |
O |
5:Diagnostics |
0:HasComponent |
Variable |
4:CloseCallFailedCount |
0:UInt32 |
0:BaseDataVariableType |
O |
ConnectionConfigurationSets provides a Folder for the ConnectionConfigurationSets (defined in 6.8) that are exposed by this ConnectionManager. It shall be restricted to holding only instances of ConnectionConfigurationSetType, which provide the data required by a ConnectionManager to establish Connections. This Folder may also contain other Folders that can be used to organise the ConnectionConfigurationSets. The Folder may be empty. The string part of the BrowseName of ConnectionConfigurationSets shall be unique within a ConnectionConfigurationSets Folder.
ConnectionManagerConfiguration provides standardised mechanisms for adding, removing, or replacing ConnectionConfigurationSets (see F.1).
EditConnectionConfigurationSets provides a way to alter the Edit Property of one or more ConnectionConfigurationSets in a single Call.
ProcessConnectionConfigurationSets causes the ConnectionManager to manage Connections contained in one or more ConnectionConfigurationSets in a single Call (see 6.7.5). In addition, vendor-specific means may be used to trigger the processing of ConnectionConfigurationSets. All processing of ConnectionConfigurationSets shall follow the behaviour defined in 6.7.5.3.
Capabilities is a ConnectionManagerCapabilitiesType Folder that describes the functionality provided by a ConnectionManager (see 6.7.6).
AggregatedCurrentState shall be set to TRUE if one or more ConnectionConfigurationSets’ ConnectionConfigurationSetStateMachine is in State Error. This only indicates that the ConnectionManager encountered a problem in processing one or more of the ConnectionConfigurationSets; it does not indicate the status of the Connections.
ConnectionManagerLog exposes a LogObject for the ConnectionManager. The LogObject (see OPC 10000-26) can be accessed to obtain the log of activity related to the ConnectionManager. Standardised Events that can be used to trigger records for the LogObject are defined in 8.9 and 8.10. LogObject records can also be generated without the generation of an Event. If the LogObject is supported, the ConnectionManager shall generate records for all EstablishConnections calls, CloseConnections calls, and any related calls (see 13), including reporting of all errors. The reporting of all errors might result in multiple log records for a single call. For example, if there are multiple verification errors (e.g. Asset verification or FunctionalEntity verification), all would be logged. To facilitate tracking of LogRecords between the ConnectionManager and an AutomationComponent, the ConnectionManager shall provide the SpanContextDataType as part of the EstablishConnection Method Call to each AutomationComponent, as defined in OPC 10000-26.
EstablishCallCount diagnostics counter provides a count of the number of EstablishConnections calls issued by the ConnectionManager. This applies to local and remote calls.
EstablishCallFailedCount diagnostics counter provides a count of the number of EstablishConnections calls that failed (any command). This applies to local and remote calls.
CloseCallCount diagnostics counter provides a count of the number of CloseConnections calls issued by the ConnectionManager. This applies to local and remote calls.
CloseCallFailedCount diagnostics counter provides a count of the number of CloseConnections calls issued by the ConnectionManage that failed. This applies to local and remote calls.
The Diagnostics FunctionalGroup contains Variables and Methods for diagnostics (see OPC 10000-100 Recommended FunctionalGroup BrowseNames). For UAFX, this includes the defined diagnostic Variable in Table 78 – ConnectionManagerType additional subcomponentsTable 78.