Search
99 result(s) for ConnectionManager
-
OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts3.1.5 ConnectionManagerConnectionManager entity that interacts with AutomationComponents to establish Connections between FunctionalEntities Note 1 to entry: See OPC 10000-81 for a description of the ConnectionManagerType
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model12.3 ConnectionManagerConnectionManager The following instance shall exist in all Servers that expose a ConnectionManager . It is formally defined in Table 256 Table 256 - ConnectionManager definition Attribute Value BrowseName 4:ConnectionManager References ... TypeDefinition Organized by the FxRoot defined in 12.2 HasTypeDefinition ObjectType 4:ConnectionManagerType ConformanceUnits UAFX ConnectionManager Base The ConnectionManager is the well-known object that represents a ConnectionManager . A S erver
-
OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and ConceptsController-to-Device DCS Distributed Control System DHCP Dynamic Host Configuration Protocol CM ConnectionManager DNS Domain Name Service FE FunctionalEntity FX Field eXchange HMI Human Machine Interface IEC International Electrotechnical
-
OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts5.4.6 System integrationClient Server services, as shown in Figure 7 . Figure 7 - Connection commissioning The ConnectionManager uses OPC UA Methods exposed by each AutomationComponent to establish the configured Connections when the system ... shown in Figure 8 . See clause 6.2 for more details on Connections and the ConnectionManager . See OPC 10000-81 for more details. Figure 8 - Connection establishment
-
OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Conceptsdifferent QoS classes in the application configuration. OPC 10000-81 formally describes Connections . The ConnectionManager , described in OPC 10000-81 , is the entity responsible for establishing Connections . The ConnectionManager
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model4.7.1 OverviewOverview A ConnectionManager is an optional entity that interacts with multiple AutomationComponents to establish Connections between FunctionalEntities . The ConnectionManager can execute on any Server supporting the OPC UA FX Information ... Model . In the OPC UA FX Information Model , the ConnectionManager is represented by the ConnectionManagerType , which defines functionality and interfaces to manage the establishment of Connections between FunctionalEntities . Several ConnectionManagers
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelCreating / Monitoring / Closing Connections Connections to be created are part of a ConnectionManager configuration ( ConnectionConfigurationSet ). An AutomationComponent and the included FunctionalEntities report the status of Connections that are part ... Connections they create. Possible reasons for monitoring Connection status include: An application or ConnectionManager monitors ConnectionEndpoints on AutomationComponents to decide whether it needs to (re)establish or close Connections
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Modelcommunication model (e.g., PubSub or Client Server [future]). The engineering tool and ConnectionManager could reside on separate devices or be located on the same device. ConnectionConfigurationSets can be deployed ... ConnectionManager (see Figure 11 label 3) using functionality defined in Annex F or vendor-specific means. A ConnectionConfigurationSet can allow changes. For example, addressing information that is only available
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Modelclosing Connections As introduced in 4.7 , logical connection establishment can be executed by a ConnectionManager . If present on a Server , the ConnectionManager is represented in the Information Model ... instance of ConnectionManagerType (see 6.7 ). To start the establishment of logical connection s, the ConnectionManager could be triggered by vendor-specific means or by a Client using the ProcessConnectionConfigurationSets Method
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model5.5.6.2.5 DataSetMetaDataconfigured by an engineering tool on behalf of Descriptors and are deployed to a ConnectionManager (see 5.5.2 ). Independent of the lifetime of a Connection, another engineering tool can update
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model5.6 HealthConnectionEndpoints to the FunctionalEntity , from FunctionalEntities to the AutomationComponent , or from ConnectionConfigurationSets to the ConnectionManager ). The aggregated health status allows a Client to easily detect whether diagnostic conditions are present
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelAliasNames can be used to define a configuration for information used by the ConnectionManager . AliasNames allow offline engineering tools to assign alternate names to Variables or Objects that are used
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Modelmultiple Servers could be included under a single AggregatingServer . An AggregatingServer can expose a ConnectionManager , but only one well-known ConnectionManager is allowed on a Server . This single ConnectionManager
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model6.2.4.1 OverviewOverview The EstablishConnections Method establishes one or more Connections . The ConnectionManager typically calls it. It allows for creating ConnectionEndpoints , establishing control, verifying FunctionalEntity and Asset compatibility, applying ConfigurationData , and configuring
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model6.2.4.3.11 Abortsuch a rollback is the responsibility of the caller of the Method (e.g., the ConnectionManager ). The caller of the Method can use the CloseConnections Method to issue a complete rollback
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Modelshall indicate that a timeout occurred. The ConnectionManagerApplicationUri can be used to identify the ConnectionManager that created this ConnectionEndpoint . The ConnectionManagerApplicationUri shall be set to the ApplicationUri in the ApplicationDescription ... associated with the Client connection from the ConnectionManager that established this Connection. If the ConnectionManager is local to this AutomationComponent (no Client connection), this shall be set to the ApplicationUri
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model6.7.1 OverviewOverview Figure 34 illustrates the structure of the ConnectionManagerType . A ConnectionManager uses the configuration data stored in a ConnectionConfigurationSet (see 6.8 ) to establish Connections . Optional Methods are provided by ConnectionManagerType ... allow Clients to manage editing and trigger the processing of Connections . A ConnectionManager is represented by an instance of ConnectionManagerType ; see 12 for details on its location in the UAFX
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelBaseDataVariableType 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 ... 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
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model6.7.3.1 OverviewOverview The ConnectionManager performs the functionality described in this subclause. This functionality may be invoked by a ConnectionManagerType- defined Method or by vendor-specific means
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model6.7.3.2 Establishing ConnectionsEstablishing Connections To establish Connections defined in a ConnectionConfigurationSet , the ConnectionManager shall use the sequence of Calls illustrated in Figure 36 to the EstablishConnections Method on the involved AutomationComponents ... single AutomationComponent when calling the EstablishConnections Method . Figure 36 - Command sequence illustration A ConnectionManager shall call the EstablishConnections Method on the AutomationComponents , passing in one or several commands
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model6.7.3.3 Closing ConnectionsClosing Connections To close Connections defined in a ConnectionConfigurationSet , a ConnectionManager shall use the CloseConnections Method on the AutomationComponents (see 6.2.5 ). A ConnectionManager may remove or disable the Connections ... CloseConnections returns any error, the ConnectionManager shall complete closing all Connections in the ConnectionConfigurationSet and initiate a ProcessingToError transition in the ConnectionConfigurationSetStateMachine (see 6.9 ). If any of the ConnectionEndpoints require
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelMethod shall set the Property Edit to FALSE for all requested ConnectionConfigurationSets . The ConnectionManager shall only process committed updates. It shall reassign the Lock back to the ConnectionManager . If Version ... Method shall set the Property Edit to FALSE for all requested ConnectionConfigurationSets . The ConnectionManager shall discard the updates to the ConnectionConfigurationSet . It shall reassign the Lock back to the ConnectionManager
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model6.7.5.1 OverviewOverview The ProcessConnectionConfigurationSets Method causes the ConnectionManager to process the requested ConnectionConfigurationSets according to the specified Action : ActionEstablishConnectionsEnabled , ActionEstablishConnectionsDisabled , and ActionEstablishConnections - establish all Connections contained in the ConnectionConfigurationSets . ActionRemoveConnections - disable
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelObjectType ConnectionConfigurationSetProcessingSucceededEventType Defined in 8.8 0:GeneratesEvent ObjectType ConnectionConfigurationSetProcessingFailedEventType Defined in 8.9 ConformanceUnits UAFX ConnectionManager ProcessConnectionConfigurationSets If Auditing is supported, the ConnectionManger shall generate an Event of type AuditUpdateMethodResultEventType ... ProcessConnectionConfigurationSets Method calls. The SourceNode for this Event shall be the ConnectionManager . If ConnectionManagerLog is supported, the ConnectionManager shall produce a LogRecord for each ConnectionConfigurationSet in the invocation of this
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model6.7.5.3.1 ActionEstablishConnectionsEnabled / ActionEstablishConnectionsDisabled / ActionEstablishConnectionstheir related communication model. Establishing connections shall follow the behaviour specified in 6.7.3.2 . The ConnectionManager shall ensure the expected result of the requested Action as follows: Calling ProcessConnectionConfigurationSets with Action ... communication model as configured by the engineering tool generating the communication model. The ConnectionManager shall apply the communication model as is using the SetCommunicationConfigurationCmd and omit EnableCommunicationCmd from the command
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model6.7.5.3.2 ActionRemoveConnectionsConnections contained in the ConnectionConfigurationSets and their related communication model. For each ConnectionConfigurationSet , the ConnectionManager shall call the CloseConnections Method (see 6.2.5 ) with Remove set to TRUE for all contained ... ConnectionEndpoints . See 6.7.3.3 for ConnectionManager behaviour
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model6.7.5.3.3 ActionEnableConnectionsActionEnableConnections shall enable all Connections contained in the ConnectionConfigurationSets . For each ConnectionConfigurationSet , the ConnectionManager shall call the EstablishConnections Method containing the EnableCommunicationCmd for all contained ConnectionEndpoints . See 6.7.3.2 for ConnectionManager
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model6.7.5.3.4 ActionDisableConnectionsActionDisableConnections shall disable all Connections contained in the ConnectionConfigurationSets . For each ConnectionConfigurationSet , the ConnectionManager shall call the CloseConnections Method (see 6.2.5 ) with Remove set to FALSE for all contained ConnectionEndpoints ... ConnectionManager behaviour
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Modelshall be restricted to contain only Variables that reflect the capabilities of the ConnectionManager . The ConnectionManagerCapabilitiesType is formally defined in Table 88 . Table 88 - ConnectionManagerCapabilitiesType definition Attribute Value BrowseName ... BaseDataVariableType O 4:HasCMCapability Variable 4:MonitorsAllConnectionEndpoints 0:Boolean 0:BaseDataVariableType O ConformanceUnits UAFX ConnectionManager Capabilities Base <Capability> - is an OptionalPlaceholder (defined in OPC 10000-3 ) to indicate
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model6.8.1 Overviewappropriate use cases. ConnectionConfigurationSets are generated and deployed to the ConnectionManager (see Figure 11 label 3). The ConnectionManager may expose the ConnectionConfigurationSets in its AddressSpace . A ConnectionConfigurationSet exposes diagnostic information ... ConnectionConfigurationSet can specify and restrict the allowed changes. If Auditing is supported, the ConnectionManager shall generate an Event of type AuditUpdateConnectionConfigurationSetEventType for all ConnectionConfigurationSet data modifications. If the ConnectionManagerLog
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelHasComponent Variable 4:ConnectionsDiagnostics 4:ConnectionDiagnosticsDataType[] 0:BaseDataVariableType O, RO ConformanceUnits UAFX ConnectionManager Base Table 90 - ConnectionConfigurationSetType additional references SourceBrowsePath Reference Type IsForward TargetBrowsePath 4:<ServerAddress> 4:ToAutomationComponentConfiguration ... functionality. A ConnectionConfigurationSet that is not in editable mode shall be locked to the ConnectionManager and blocked from any changes (the Client is set to the NodeId of the ConnectionManager
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model6.9.1 Overviewstate machine is defined as a mechanism to coordinate actions executed internally (a ConnectionManager establishing Connections ) that involve the processing of a ConnectionConfigurationSet . The States and Transitions that comprise
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelObject 4:ProcessingToError 0:TransitionType 0:HasComponent Object 4:ErrorToProcessing 0:TransitionType ConformanceUnits UAFX ConnectionManager Base The components of the ConnectionConfigurationSetStateMachineType have additional references, which are defined in Table ... ReadyToProcessing 0:FromState True 4:Ready 4:ReadyToProcessing 0:HasCause True 2:FxRoot 4:ConnectionManager 4:ProcessConnectionConfigurationSets 4:ReadyToProcessing 0:HasEffect True 4:ConnectionConfigurationSetProcessingStartedEventType 4:ProcessingToReady 0:ToState True
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelBaseDataVariableType O 0:HasComponent Variable 4:PreconfiguredSubscribedDataSet 0:String 0:BaseDataVariableType O ConformanceUnits UAFX ConnectionManager Base Name specifies the BrowseName of the ConnectionEndpoint to create. This name shall be unique ... FunctionalEntity's ConnectionEndpoints Folder . This Name is required for maintaining/closing the Connection , thus a ConnectionManager shall reject changes to this Variable , if the Connection is established. The Name
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model6.13.1 Overviewaddress or update interval) without having to understand the internals of the CommunicationModelConfiguration . The ConnectionManager reflects the changes of a Client in the related elements in CommunicationModelConfiguration . CommunicationFlowConfigurations are referenced
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelAssetVerificationType OP 0:HasComponent Object 4:CommunicationModelConfig 4:CommunicationModelConfigurationType O ConformanceUnits UAFX ConnectionManager Base AutomationComponentNode specifies the AutomationComponent that is to be used for establishing Connections . If a PortableRelativePath ... specified, the path shall be relative to FxRoot . CommandBundleRequired , when TRUE, specifies that the ConnectionManager shall bundle commands to this AutomationComponent . AssetVerification holds the Asset verification parameters for an Asset
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelBaseDataVariableType M 0:HasComponent Variable 4:ConfigurationValues 0:PubSubConfigurationValueDataType[] 0:BaseDataVariableType M ConformanceUnits UAFX ConnectionManager PubSubCommunicationFlowConfiguration The PubSubConfiguration modifies the existing PubSub configuration on the addressed Server when establishing Connections ... /UA/FX/CM/Translation/ ", are not valid NodeIds but placeholders which shall be resolved before the ConnectionManager can use the PubSubConfiguration for connection establishment. The resolution consists of 2 steps. The first
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelConnectionConfigurationSetProcessingSucceededEventType Defined in 8.8 . 0:HasSubtype ObjectType 4:ConnectionConfigurationSetProcessingFailedEventType Defined in 8.9 . ConformanceUnits UAFX ConnectionManager Configuration Set Processing Events This EventType inherits all Properties of the BaseEventType . For all Events ... this type, the SourceNode (from BaseEventType ) shall be set to the NodeId of the ConnectionManager that is executing the state machine. ConnectionConfigurationSetNode and Name identify the ConnectionConfigurationSet , which was processed
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Modeltransition from the Ready State to the Processing State as a result of a ConnectionManager starting to process the ConnectionConfigurationSet . Its representation in the AddressSpace is formally defined in Table ... Node Class BrowseName Note Subtype of the 4:ConnectionConfigurationSetEventType defined in 8.5 . ConformanceUnits UAFX ConnectionManager Configuration Set Processing Events This EventType inherits all Properties of the ConnectionConfigurationSetEventType
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelEstablishConnectionErrorEventType This EventType is generated by a ConnectionManager when an error is returned on an EstablishConnection Method invocation or any related actions. Its representation in the AddressSpace is formally defined ... IsAbstract True References Node Class BrowseName Note Subtype of the 0:BaseLogEventType. ConformanceUnits UAFX ConnectionManager LogObject Events This EventType inherits all Properties of the BaseLogEventType . The ConditionClassId shall
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelCloseConnectionErrorEventType This EventType is generated by a ConnectionManager when an error is returned on a CloseConnection Method invocation. Its representation in the AddressSpace is formally defined in Table 119 . Table ... IsAbstract True References Node Class BrowseName Note Subtype of the 0:BaseLogEventType. ConformanceUnits UAFX ConnectionManager LogObject Events This EventType inherits all Properties of the BaseLogEventType . The ConditionClassId shall
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelSelectionListType M 0:HasComponent Variable 4:ServerUri 0:UriString 0:SelectionListType M ConformanceUnits UAFX ConnectionManager Base Address is specified as a DiscoveryUrl in the form scheme://hostname[:port][/path ... name that would need to be resolved to an IP address. A ConnectionManager shall be able to resolve a name to an IP address. Any selected Address will be reflected
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelSelectionListType M 0:HasComponent Variable 4:UsePushModel 0:Boolean 0:BaseDataVariableType M ConformanceUnits UAFX ConnectionManager Base Address specifies the address of the SKS as a DiscoveryUrl in the form ... name that would need to be resolved to an IP address. A ConnectionManager shall be able to resolve a name to an IP address. Any selected Address will be reflected
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelStructure defined in OPC 10000-5 ConformanceUnits UAFX AutomationComponent Base UAFX ConnectionManager Base For a definition of how this DataType shall be generated by the ConnectionManager
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelNode in the ConnectionConfigurationSet . LastActivity 4:LastActivityMask The last activity taken by the ConnectionManager on the Connection indicated by Name , including results of the activity. A zero indicates no activity ... apply to updating the LastActivity and all ConnectionEndpoint -related fields ( ErrorEndpoint1 , etc.). When a ConnectionManager finishes processing a ConnectionConfigurationSet , it shall set the corresponding bit in the LastActivity and clear
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model10.20 ConnectionStateEnumConnectionStateEnum provides information about the current state of the Connection , as determined by the ConnectionManager. See 10.19 for a description of the ConnectionState . The ConnectionStateEnum values are formally defined ... Table 166 . Table 166 - ConnectionStateEnum items Name Value Description ConnectionNotMonitored 0 ConnectionManager does not monitor the state of the Connection ConnectionNotEstablished 1 Connection does not exist ConnectionInitial 2 Connection
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model10.23 FxCommandMaskFxCommandMask This OptionSet defines flags indicating the commands a ConnectionManager may use in its Call to the EstablishConnections Method . The FxCommandMask values are formally defined in Table 172 . Table ... HasProperty Variable 0:OptionSetValues 0:LocalizedText[] 0:PropertyType ConformanceUnits UAFX AutomationComponent Base UAFX ConnectionManager Base
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model10.24 FxEditEnumFxEditEnum This enumeration defines the editing behaviour for a ConnectionManager . FxEditEnum is formally defined in Table 174 . Table 174 - FxEditEnum values Name Value Description StartEditing 0 The ConnectionManager shall allow ... editing of the ConnectionConfigurationSets . CommitUpdates 1 The ConnectionManager shall commit all updates from the ConnectionConfigurationSets . DiscardUpdates 2 The ConnectionManager shall discard the updates to the ConnectionConfigurationSets . The FxEditEnum representation
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model10.25 FxErrorEnumFxErrorEnum This enumeration defines the summary errors that a ConnectionManager may report. FxErrorEnum values are formally defined in Table 176 . Table 176 - FxErrorEnum values Name Value Description NoError 0 This ... processing was stopped due to some other error in the ConnectionConfigurationSet. ConnectionConfigurationSetInvalid 4 The ConnectionManager could not process this ConnectionConfigurationSet due to a configuration error. GdsConnectionError 5 There
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model10.26 FxProcessEnumFxProcessEnum This enumeration defines the processing behaviour of a ConnectionManager . FxProcessEnum is formally defined in Table 178 . Table 178 - FxProcessEnum values Name Value Description ActionEstablishConnectionsEnabled 0 The ConnectionManager shall establish ... enabled Connections from the ConnectionConfigurationSets. ActionEstablishConnectionsDisabled 1 The ConnectionManager shall establish disabled Connections from the ConnectionConfigurationSets. ActionEstablishConnections 2 The ConnectionManager shall establish Connections from the ConnectionConfigurationSets. ActionRemoveConnections 3 The ConnectionManager
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model10.30 LastActivityMaskLastActivityMask This OptionSet defines flags indicating the last activity taken by a ConnectionManager processing a given ConnectionConfigurationSet (and, in turn, on Connection configurations within). If the OptionSet is zero ... Error bit, which can be set with any of the other bits. If the ConnectionManager supports the ProcessConnectionConfigurationSets Method , then the activities correspond to the described actions in the Method
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelSubtype of the PubSubReserveCommunicationIdsResultDataType. TransportSpecificInfo 0:BaseDataType Transport-profile-specific information needed by the ConnectionManager to create a valid PubSubConfiguration for an AutomationComponent . If transport-specific information was requested ... DataType TypeDefinition Other Subtype of the 2:PubSubReserveCommunicationIdsResultDataType ConformanceUnits UAFX AutomationComponent PubSub Connections UAFX ConnectionManager PubSubCommunicationFlowConfiguration
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model12.2 FxRootmultiple AutomationComponents that include Assets and FunctionalEntities . It may also contain, at most, one ConnectionManager . NOTE AutomationComponents are part of the Server , i.e. the Server exposes the AutomationComponents as instances
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model13.1 OverviewServer with an OPC UA FX Information Model . All devices that implement the ConnectionManager are required to support Client functionality. This clause will describe the requirements for this Client functionality ... security information may have changed since the engineering tool generated configuration information ( ConnectionConfigurationSets ). The ConnectionManager may be local on one of the devices, i.e., on the same device that
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model13.2.1 Locating Server via GDSFigure 64 - Client connection process If the Server is the same Server that the ConnectionManager resides on, the EstablishConnections Method may be invoked by vendor-specific means, and all portable ... node identifiers can be resolved locally. The Session established by the ConnectionManager shall support the use of authentication and/or encryption. This includes: Application Authentication based on security mode and policy
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model13.2.2 Connecting to Server via LDSClient connection process- Local Discovery If the Server is the same Server that the ConnectionManager resides on, the EstablishConnections Method may be invoked by vendor-specific means, and all portable ... node identifiers can be resolved locally. The Session established by the ConnectionManager shall support the use of authentication and/or encryption. This includes: Application authentication based on security mode and policy
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Modelcreate a one-time connection. This type of connection can only be used by ConnectionManager exchanges that do not require a saved state across multiple invocations. For example, it cannot
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model13.3.1 Generaltext that provide examples to help explain these concepts. Figure 67 - Configuration resolution A ConnectionManager shall be able to resolve NodeIds using PortableNodeIds , PortableRelativePaths or AliasNames . The following provides ... done for each possible Node description in the ConnectionConfigurationSet . It is recommended that the ConnectionManager caches the results of these operations and that they are only performed on the initial
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model13.3.2 PortableNodeId providedPortableNodeId provided If the ConnectionConfigurationSets contain PortableNodeIds , then the ConnectionManager should perform the following steps ( Figure 68 provides an overview of the configuration and actions): Resolve the location
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelConnectionManager and Security Key Server (SKS) If a logical connection is configured to use secure PubSub communication, then a Security Key Server is required. An SKS is described in detail ... located on any Server in the network, including the Server where the ConnectionManager is located. A ConnectionManager shall be able to communicate with the designated SKS in all cases which
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelConnectionManager error reporting The ConnectionManager tracks errors for each ConnectionConfigurationSet by completing the ConnectionsDiagnostics array (see 10.19 ). These errors include any errors that result from the run time processing ... Node Information by AliasName lookup or TranslateBrowsePathToNodeId, or even for Namespace lookup issues. The ConnectionManager also report errors from interactions with an SKS (local or remote). The ConnectionManager reports errors
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model14.1 Namespace metadatathis document. Table 257 defines DataTypes that are shared between the AutomationComponent and the ConnectionManager . Table 258 defines the namespace associated with an AutomationComponent . Table 259 defines the namespace associated ... with a ConnectionManager . The Objects are used to provide version information for the namespaces and an indication of static Nodes . Static Nodes are identical for all Attributes in all Servers
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelMandatory http://opcfoundation.org/UA/FX/Data / Namespace for common DataType that are shared between a ConnectionManager and an AutomationComponent . Mandatory http://opcfoundation.org/UA/FX/AC / Namespace for NodeIds and BrowseNames defined in the AutomationComponent ... Server, a Server shall support either the AutomationComponent or the ConnectionManager. Optional http://opcfoundation .org/UA/FX/CM/ Namespace for NodeIds and BrowseNames defined in the ConnectionManager -related part of this document
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Modelopcfoundation.org/UA/FX/AC/ http://opcfoundation.org/UA/FX/CM/ depending on whether it is common data, AutomationComponent , or ConnectionManager -related. Online documentation for the NamespaceUris can be found here: For Data-related, here ... UAFX/opc.ua.fx.data.nodeset2.documentation.csv For AutomationComponent-related, here à UAFX/opc.ua.fx.ac.nodeset2.documentation.csv For ConnectionManager-related, here à UAFX/opc.ua.fx.cm.nodeset2.documentation.csv The NodeSets associated with this version of the specification can be found here: https://reference.opcfoundation.org/nodesets/?u=http://opcfoundation.org/UA/FX/Data/&v=1.00.04&i=1
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Modelused. The communication between Controller A and Controller B could be setup by the ConnectionManager in Controller A, it would see the ControlGroup and would utilize the preconfigured Dataset that
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelE.1.1 OverviewE.1.1 Overview The ConnectionManager processes ConnectionConfigurationSets to establish connections. This clause contains examples for ConnectionConfigurationSets . A ConnectionConfigurationSet contains a set of logical connections, which the ConnectionManager establishes as a complete
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Modelsingle logical connection. The relation between the configuration elements (present on the ConnectionManager ) and their resulting runtime elements (present or created on the AutomationComponents being part of the logical connection ... each referenced by a ServerAddress ServerA and ServerB, containing the configuration required for the ConnectionManager to be able to establish a secure Session to ServerA and ServerB
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelE.2.1 OverviewE.2.1 Overview The ConnectionManager uses the information in the ConnectionConfigurationSet to establish all contained Connections . The configuration information required as input to call EstablishConnections on a particular AutomationComponent ... following the References starting at each of the AutomationComponents listed in the ConnectionConfigurationSet . The ConnectionManager iterates through the AutomationComponentConfigurations . The ConnectionManager establishes a secure Session based on the information contained
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Modelcould be generated by the addressed AutomationComponent and are not be known by the ConnectionManager beforehand. OPC 10000-14 provides two ways of generating unique IDs by the AutomationComponent , either ... when configuring PubSub or by reserving IDs. Assuming a simple example, where a ConnectionManager processes a ConnectionConfigurationSet containing logical connections between two AutomationComponents , the sequence illustrated in Figure E.7 could
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelAutomationComponents Multiple logical connections across multiple AutomationComponents could require more steps. Assume that a ConnectionManager must establish a ConnectionConfigurationSet containing logical connections between multiple AutomationComponents . Figure E.8 illustrates an example ... such a ConnectionConfigurationSet . For this scenario, the ConnectionManager could set up the logical connections as follows: The ConnectionManager calls EstablishConnections on AC1, AC2, and AC3 using the ReserveCommunicationIdsCmd to reserve
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelE.4.1 OverviewPubSub CommunicationModelConfig contains the PubSub configuration elements to be applied to the AutomationComponent . The ConnectionManager uses the configuration information in Flow1 and Sub1 to update the communication model. CommunicationLinks indicate
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelE.4.7 PubSub DataSetsProfile , there are options related to the communication configuration. The engineering tools and/or ConnectionManager can make various selections. This can include optimizations which group multiple DataSetMessages into a single Network ... preconfigured or dynamically configured, the important aspect for the engineering tool and the ConnectionManager is that the appropriate published Variable is mapped to the appropriate subscribed Variable . This also includes
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Modelrelated to an external SKS. An SKS that is internal (i.e. part of a ConnectionManager ) would still be required to perform the same described functionality but may not implement ... Subscriber ). The ServerProfileArray can be retrieved online or from the Descriptor. ConnectionManager and SKS could be located on the same Server . In this case, the ConnectionManager could use vendor-specific
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelE.6.1 Overviewthat can be made (see 6.8.1 ). After a ConnectionConfigurationSet is edited (see 6.7.4 ), the ConnectionManager reflects the changes into the PubSubConfiguration . The PubSubConfiguration could be generated by an engineering tool ... ConnectionManager . Clause E.6 indicates PubSubConfiguration settings, which are based on using UDP-UADP as the transport Profile and UADP-Periodic-Fixed as the header layout Profile . Details for other transport
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelConnectionConfigurationSet and PubSubConfiguration were generated, the Namespaces could not exist on the ConnectionManager Server . This document describes how these NodeIds are to be resolved to the correct NamespaceIndex ... using the structure to set up a Connection , but if the configuration of the ConnectionManager Server is saved as a UANodeSet XML File or if the ConnectionConfigurationsSet is generated
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelF.1.1 Overviewstoring it within a File (see F.2 ), or for maintaining the configuration of a ConnectionManager (see F.3 ). For the base principles used for the mapping, see Subclause F.1.2 . Figure
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelF.1.2.2 Namespacescontains information for two different Servers . Node identifiers in the Information Model for the ConnectionManager (i.e., an instance of ConnectionConfigurationSetType ) use PortableNodeIdentifier (see 10.36 ) to support the resolution ... used as an index into the Namespace array of the related ServerAddressConfDataType . A ConnectionManager can map NodeId and RelativePath contained in the DataTypes to their portable versions using the NamespaceUri
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelEdit shall be set to False , and the Lock shall be assigned to the ConnectionManager . The ConnectionConfigurationSetConfDataType is formally defined in Table F.1 . Table F.1 - ConnectionConfigurationSetConfDataType structure Name Type Description ... TypeDefinition ModellingRule Subtype of the 0:Structure defined in OPC 10000-5 ConformanceUnits UAFX ConnectionManager File Configuration
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Modelsource variable NodeIds shall be null. They must be filled in by the ConnectionManager after getting the NodeIds from the AutomationComponent during connection establishment. True PreconfiguredSubscribedDataSet 0:String ... target variable NodeIds shall be null. They must be filled in by the ConnectionManager after getting the NodeIds from the AutomationComponent during connection establishment True ExpectedVerificationVariables NodeIdentifierValuePair[] Specifies the Variables
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Modeloptions can be modified. False CommandBundleRequired 0:Boolean CommandBundleRequired , when TRUE, specifies that the ConnectionManager shall bundle commands to this AutomationComponent . False AssetVerification 4:AssetVerificationConfDataType[] The Asset verification parameters ... TypeDefinition ModellingRule Subtype of the 0:Structure defined in OPC 10000-5 ConformanceUnits UAFX ConnectionManager File Configuration
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model/UA/FX/CM/Translation/ ", are not valid NodeIds but placeholders which shall be resolved before the ConnectionManager can use the PubSubConfiguration for connection establishment. ConfigurationReferences 0:PubSubConfigurationRefDataType[] ConfigurationReferences points to elements within ... References NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype of CommunicationModelConfigurationDataType defined in F.1.13 ConformanceUnits UAFX ConnectionManager File Configuration
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelFile allows the retrieval of the contents of the ConnectionConfigurationSets Folder of a ConnectionManager with one operation; writing it allows to add, remove, or replace ConnectionConfigurationSets . The ConnectionManagerConfigurationType is formally ... HasComponent Method 4:CloseAndUpdate Defined in F.3.2 . Mandatory ConformanceUnits UAFX ConnectionManager File Configuration
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelF.3.2 Open MethodWrite + EraseExisting (0x06). The Client shall be authorized to modify the configuration for the ConnectionManager functionality when invoking this Method on the Server with modes Write + EraseExisting (0x06). For this
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelF.3.3.1 CloseAndUpdate signaturewriting. If the Close Method is called, any cached data is discarded, and the ConnectionManager configuration is not changed. The file content shall be a UABinaryFileDataType as defined in Table ... F.37 . The Client shall be authorized to modify the configuration for the ConnectionManager functionality when invoking this Method on the Server . It is recommended that this Method be restricted
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelF.3.3.2.3 ElementRemoveignored and may be set to null or empty by the caller. The ConnectionManager shall call the CloseConnections Method on all affected AutomationComponents (see 6.2.5 ) with Remove set to TRUE
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelF.3.3.2.4 ElementReplaceF.3.3.2.4 ElementReplace The ConnectionConfigurationSetOperation ElementReplace replaces the ConnectionConfigurationSet in the ConnectionConfigurationSetFolder. The ConnectionManager shall call the CloseConnections Method on all affected AutomationComponents (see 6.2.5 ) with Remove set to TRUE
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelDescription ElementAdd 0 If this bit is set, the ConnectionConfigurationSet is added to the ConnectionManager configuration. ElementRemove 1 If this bit is set, the ConnectionConfigurationSet is removed from the ConnectionManager ... empty. ElementReplace 2 If this bit is set, the ConnectionConfigurationSet is replaced in the ConnectionManager configuration. The ConnectionConfigurationSet to be replaced is identified via the string part of the BrowseName
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Modelaware of when looking at a system that is composed of multiple vendor / ConnectionManager implementations. The behaviour of a ConnectionManager is describe in 13 . A ConnectionManager could monitor both sides ... local AutomationComponent ) or it could not monitor Connections at all (see Figure G.1 ). The ConnectionManager has capabilities (see 6.7.6 ) indicating the behaviour it supports. A diagnostics Client should be aware
-
OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networkingonnection between two UAFX Controllers . Figure 2 - Client/server with DNS resolution Controller A, with ConnectionManager (CM), has a DNS client and has been configured via DHCP or vendor-specific means
-
OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking5.6.4.2 Application and QoS engineeringsharing data between Controllers . As a final step, Connection configurations are transferred to a ConnectionManager that establishes the Connections during the workflow's connection establishment and operation phase ... steps, including the setup of network interface configurations and Connection information provided to the ConnectionManager . Complete details of the ConnectionManager are defined in OPC 10000‑81 . Figure 6 illustrates
-
OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX NetworkingConnection establishment and operation The connection establishment and operation phase begins with the ConnectionManager establishing the Connections described in its Information Model . Connection establishment is either initiated by the ConnectionManager ... internal logic or by a Client invoking a Method on the ConnectionManager as described in OPC 10000‑81 . Figure 11 - PubSub QoS and addressing configuration variables The ConnectionManager establishes Connections
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineeringSystem Integrator wants to provide it to the Controls Engineer , who is configuring the ConnectionManager component that is responsible for the connection establishment. A Descriptor with configuration information is typically
-
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles5.2.6 UAFX ConnectionManagerUAFX ConnectionManager Table 7 describes ConnectionManager -related UAFX Information Model ConformanceUnits. For additional information about these items, please refer to OPC 10000‑81 . Table 7 - UAFX ConnectionManager Category Title Description ... ConnectionManager Server UAFX ConnectionManager Base Supports the well-known instance of the ConnectionManagerType . This includes support of ConnectionConfigurationSetType instances, including any subtypes of ConnectionConfigurationSetType Components that are supported. Server UAFX
-
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX ProfilesUAFX ConnectionManager Client 2024 Facet Table 42 describes the details of the UAFX ConnectionManager Client 2024 Facet. This Facet extends the "Minimum UA Client 2025" Profile with ... Client functionality needed by a ConnectionManager . Table 42 - UAFX ConnectionManager Client 2024 Facet Group Conformance Unit / Profile Title Optional Minimum UA Client 2025 Profile Attribute Services Attribute Client Read Base
-
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profilesincludes the information required for configuring the Subscriber of an information flow in the ConnectionManager Information Model . Table 43 - UAFX SubscriberConfiguration Facet Group Conformance Unit / Profile Title Optional UAFX ConnectionManager ... UAFX ConnectionManager SubscriberConfiguration False UAFX ConnectionManager UAFX ConnectionManager SubscriberConfiguration ReceiveQos True UAFX ConnectionManager UAFX ConnectionManager SubscriberConfiguration Address True
-
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX ProfilesUAFX ConnectionManager 2024 Facet Table 45 describes the details of the UAFX ConnectionManager 2024 Facet. This Facet includes the functionality a UAFX ConnectionManager needs to establish Connections between FunctionalEntities . This ... Facet supersedes the UAFX ConnectionManager Facet . Table 45 - UAFX ConnectionManager 2024 Facet Group Conformance Unit / Profile Title Optional UAFX ConnectionManager Client 2024 Facet UAFX SubscriberConfiguration Facet UAFX SKS Push Facet
-
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX ProfilesUAFX ConnectionManager Connection Monitoring Facet Table 46 describes the details of the UAFX ConnectionManager Connection Monitoring Facet. This Facet includes the functionality needed for a ConnectionManager to monitor Connections . Table ... UAFX ConnectionManager Connection Monitoring Facet Group Conformance Unit / Profile Title Optional UAFX ConnectionManager UAFX ConnectionManager ConnectionsDiagnostics False UAFX ConnectionManager UAFX ConnectionManager Capabilities MonitorsLocalConnectionEndpoints True UAFX ConnectionManager UAFX ConnectionManager Capabilities MonitorsAllConnectionEndpoints
-
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX ProfilesUAFX ConnectionManager Diagnostic Counters Facet Table 47 describes the details of the UAFX ConnectionManager Diagnostic Counters Facet. This Facet includes the functionality needed for ConnectionManager tracking of Connection establishment. Table ... UAFX ConnectionManager Diagnostic Counters Facet Group Conformance Unit / Profile Title Optional UAFX ConnectionManager UAFX ConnectionManager Diagnostics FunctionalGroup False UAFX ConnectionManager UAFX ConnectionManager Diagnostics EstablishCall False UAFX ConnectionManager UAFX ConnectionManager Diagnostics
-
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles6.6.4.10 UAFX Controller 2024 Profilecollection of Profiles and Facets necessary to build a functional UAFX Controller , including a ConnectionManager . This Profile supersedes the UAFX Controller 2023 Profile . Table 49 - UAFX Controller 2024 Profile Group ... UAFX AutomationComponent Communication Subscriber Facet UAFX Asset Facet UAFX top-level FunctionalEntity Facet UAFX ConnectionManager 2024 Facet UAFX Station 2024 Facet Publisher UDP UADP Periodic Fixed StaticCfg Profile Subscriber