Search

Scope: Core (OPC-10000-*) All specs

83 result(s) for Connection

OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts

3.1.9 Connection

Connection logical communication relationship between FunctionalEntities for exchanging information and coordinating joint operations
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.4.2.2 ExtensionFieldsType

Well-Known Extension Field Names Name Type Description PublisherId BaseDataType The PublisherId from the Connection Object . DataSetName String The Name from the DataSetMetaData . DataSetClassId Guid The DataSetClassId from the DataSetMetaData
OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts

5.4.3 Application engineering

with their Controller or other Controllers to be connected. Engineer B then adds the Connection configuration needed to exchange the data required for the application. Note This workflow describes
OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts

5.4.6 System integration

System integration The System Commissioner may adjust the Connection configuration, such as addresses of Connection partners, publishing intervals, and QoS mapping tables using a generic OPC UA client ... standard OPC UA Client 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
OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts

6.1 Controller-to-Controller communication

Assets, and FunctionalEntities also include identification information, allowing compatibility to be verified for each Connection . This release of the UAFX specification defines Connections using OPC UA PubSub for data exchange
OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts

6.2 UAFX Information Model

capabilities and diagnostic information. OPC 10000-81 formally describes AutomationComponent , Asset , and FunctionalEntity . A Connection is a logical relationship between FunctionalEntities for exchanging information and coordinating joint operations. Data
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

4.1 Overview

Overview This document provides a detailed description of Connection functionality and the related Information Model for OPC UA FX. For an overview, please
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

4.4.2 FunctionalEntityType

FunctionalEntity model is the interaction between FunctionalEntities , which is modelled as a Connection. The FunctionalEntity part of the model includes information such as status, diagnostics, and other information to help ... represent this Connection : Identification properties: Identity - When establishing a Connection between FunctionalEntities , it could be essential to confirm identity, e.g. to check that the other FunctionalEntity is the one that
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

4.6 FunctionalEntities and applications

interactions is represented in the FunctionalEntity by Connections (see Figure 8 ). Figure 8 - Example Connection between FunctionalEntities The process of establishing a Connection can include identity and compatibility verification, identifying ... information, setting ConfigurationData , configuring the communication, and finally, enabling the communication. An established Connection is represented on a connected FunctionalEntity by the ConnectionEndpoint . For more information, see the definition
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

4.7.1 Overview

NOTE For simplicity in this document, we will describe that a ConnectionManager monitors a Connection , with it being understood that this could be some other application
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

4.7.2 Creating / Monitoring / Closing Connections

Clients can monitor this status. Some ConnectionManagers could: know when to create a Connection . just respond to external or internal commands, i.e., the application triggers the creation of the connection ... monitor the 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
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

5.1 Overview

Subscribers , but additional concepts are required for OPC UA FX. These concepts include Connection establishment and bidirectional communication. The establishment of Connections further requires concepts such as identity and compatibility
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

5.4 ConfigurationData

used to set up and configure its functionality. As part of establishing a Connection between FunctionalEntities , some configuration might be required. This configuration is separate from the configuration required
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

5.5.1 Overview

data exchange between FunctionalEntities using logical connections. Figure 8 illustrates this interaction. A logical connection is represented by two ConnectionEndpoints , one on each FunctionalEntity that is part of the connection ... heartbeat describe unidirectional data exchange in one direction and a heartbeat message (for logical connection monitoring) in the opposite direction between two FunctionalEntities . Unidirectional connections describe unidirectional data exchange between
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

5.5.5 Persistent and preconfigured objects

FunctionalEntity that includes a preconfigured PublishedDataSet that is used as part of a logical connection. The other parts of the logical connection (e.g., ConnectionEndpoint , WriterGroup , DataSetWriter) are all created during ... connection establishment. If the Connection is not marked for persistence, the other parts are deleted on clean-up or on a power cycle, and the preconfigured Objects will remain
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

5.5.6.2.2 Single Connection using unicast network messages

Single Connection using unicast network messages This use case, illustrated in Figure 12 , describes a single logical connection between two FunctionalEntities located on the AutomationComponents A and B, each containing ... Publisher , a Subscriber , and a single PubSubConnectionEndpoint . Both FunctionalEntities could be publishing data (bidirectional Connection ), or only one could be publishing data while the other publishes a heartbeat (unidirectional connection
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.2.4.3.10.2 PubSub

EnableCommunicationResult are formally defined in Table 17 . The target of an enabled Connection is the Operational State , but various factors can affect this transition and are not reflected ... result of the EnableCommunicationCmd . The behaviour of the Connection Status and its dependency on PubSub objects is defined
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.2.5.1 CloseConnections signature

Connections to be closed. Remove When TRUE, the Objects dynamically created for the Connection are removed. Results The results of closing the Connections identified by the ConnectionEndpoints argument, see Table
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.2.6 AutomationComponentCapabilitiesType

further restricted based on the type of Connections being provided (i.e., a high-speed Connection might further reduce the number of available Connections ). The optional MinConnections indicates the minimum number
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.4.2 FunctionalEntityType definition

FunctionalEntity . The restrictions for a sub- FunctionalEntity only apply if the Connection is established with the sub- FunctionalEntity or if OutputData defined in the sub- FunctionalEntity are part ... Connection . If a Connection utilizes data from multiple sub- FunctionalEntities , a Server shall report an error ( Bad _ ConfigurationError ) if the requested settings do not meet all of the sub- FunctionalEntities
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.4.4 InputsFolderType

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 missing
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.4.5 OutputsFolderType

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 missing
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.5.2 ControlGroupType definition

CloseConnections Method will release any Locks that may have been acquired as part of connection establishment. The functionality provided by EstablishConnections ( ReassignControlCmd ) and CloseConnections is the same as that provided ... null String , in which case it is set to the ApplicationUri of the Client connection used to call this Method . The optional ReassignControl Method will assign all active Locks
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.6.1 Overview

Overview A ConnectionEndpoint is used to represent an endpoint of a Connection between two FunctionalEntities for data exchange. It provides information about which InputVariables and/or OutputVariables are exchanged. ConnectionEndpoints reside ... PubSub . This type specifies the exchanged Variables and contains the status of the Connection . Subtypes of ConnectionEndpointType provide details specific to the utilized communication model and specify how the Connection
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.6.2 ConnectionEndpointType definition

more OutputVariables RelatedEndpoint points to the related ConnectionEndpoint (i.e., the other end of the Connection ). The RelatedEndpointDataType is defined in 10.42 . If the ConnectionEndpoint is not exposed in the Information ... Model of the related connection partner, RelatedEndpoint will specify the path to the connected FunctionalEntity . IsPersistent indicates if the ConnectionEndpoint shall be persistent. Persistent ConnectionEndpoints shall be restored following
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.6.3 PubSubConnectionEndpointType definition

DataSetWriterName> Mode defines the mode of the ConnectionEndpoint with respect to the Connection . The modes are formally defined in the PubSubConnectionEndpointModeEnum defined in Subclause 10.41 . If the PubSub configuration ... DataSetWriter according to Figure 33 . Figure 33 - Status with Mode of Publisher For the connection types autonomous publisher and autonomous subscriber (see 5.5.1 ), RelatedEndpoint Address shall
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.7.3.2 Establishing Connections

illustration of the configuration information contained in the ConnectionConfigurationSet . The figure illustrates a single Connection . For further examples, please refer to Annex E . Figure 35 - ConnectionConfigurationSet example The EstablishConnections Method ... Figure 36 ) to verify and create the individual Information Model Objects related to a Connection . Figure 36 illustrates the sequence of commands to a single AutomationComponent when calling the EstablishConnections
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.7.6 ConnectionManagerCapabilitiesType

Connections. NOTE In some cases, this status might include the status of the remote Connection . MonitorsAllConnectionEndpoints, when true, describes the capability of the ConnectionManager Information Model to report status information
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.8.1 Overview

Overview The ConnectionConfigurationSetType is an ObjectType representing one or more Connection configurations. Connections are grouped in a set, for example, to allow sharing communication model configurations by multiple Connections ... diagnostic information about the Connections as part of its Information Model . It also allows Connection configurations to be available for modification by standard Clients (see Figure 11 label
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.8.2 ConnectionConfigurationSetType definition

Variable 4:Edit 0:Boolean 0:PropertyType O, RO 4:HasConnectionConfiguration Object 4:<Connection> 4:ConnectionConfigurationType MP 4:HasCommunicationFlowConfiguration Object 4:<CommunicationFlow > 4:CommunicationFlowConfigurationType ... True 4:<AutomationComponentConfiguration> 4:<AutomationComponentConfiguration> 4:ToConnectionEndpointConfiguration True 4:<Connection> 4:Endpoint1 4:<AutomationComponentConfiguration> 4:ToConnectionEndpointConfiguration True 4:<Connection
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.9.1 Overview

processing succeeded) and 3 (processing failed) are only triggered internally on completion of Connection establishment processing. A ConnectionConfigurationSetStateMachine may transition to Error for several reasons. Transient errors will be resolved
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.9.2 ConnectionConfigurationSetStateMachineType definition

ProcessingToError - This transition shall be initiated if the ConnectionManager fails the processing of any Connection contained in the ConnectionConfigurationSet . Information about the success or failure of the establishment of specific
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.10.1 Overview

Overview The ConnectionConfigurationType ObjectType describes the configuration information needed to establish a single Connection contained in the ConnectionConfigurationSetType . The ConnectionConfigurationType is illustrated in Figure 40 . Figure 40 - ConnectionConfigurationType illustration
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.10.2 ConnectionConfigurationType definition

Endpoint1 and the optional Endpoint2 hold the configuration information for the endpoints of the Connection . The ConnectionEndpointConfigurationType is defined
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.11.1 Overview

Overview The ConnectionEndpointConfigurationType ObjectType holds the information for an endpoint of a Connection . The ConnectionEndpointConfigurationType is illustrated in Figure 41 . Figure 41 - ConnectionEndpointConfigurationType illustration
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.11.2 ConnectionEndpointConfigurationType definition

UAFX ConnectionManager Base FunctionalEntityNode specifies the identifier of the FunctionalEntity to configure for this Connection . If a PortableRelativePath is specified, the path shall be relative to FxRoot . ConnectionEndpoint specifies ... parameters for the ConnectionEndpoint to be used for the Connection . ExpectedVerificationVariables , if present, specifies the variables to be verified. If a PortableRelativePath is specified as Key , the path shall
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.12.1 Overview

Overview The ConnectionEndpointParameterType ObjectType holds the parameters to create the ConnectionEndpoint of a Connection . The ConnectionEndpointParameterType is illustrated in Figure 42 . Figure 42 - ConnectionEndpointParameterType illustration
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.12.2 ConnectionEndpointParameterType definition

unique within the 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 ... Name can be changed if the Connection does not exist. ConnectionEndpointTypeId specifies the well-known NodeId of the type definition, which shall be used to create the ConnectionEndpoint . This
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.13.1 Overview

ToInboundFlow References . The absence or presence of these References reflects the type of Connection in which the particular ConnectionEndpoint(s) are participating, such as bidirectional, unidirectional, unidirectional with heartbeat, autonomous ... publisher, or autonomous subscriber. For details about possible Connection types, see 5.5.1 . Examples of the configuration can be seen in Annex E . Multiple ConnectionEndpointConfigurations may reference the same CommunicationFlowConfiguration
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.13.3.2 PubSubCommunicationFlowConfigurationType definition

contained in its parent object, but the parent information is required to establish the Connection . For the usage of SelectionLists, see 6.8.1 . Table 98 - PubSubCommunicationFlowConfigurationType definition Attribute Value BrowseName
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

8.3 AuditConnectionCleanupEventType

AuditConnectionCleanupEventType This EventType allows Connection clean-up, as performed by a Server, to be audited. Its representation in the AddressSpace is formally defined in Table 111 . Table 111 - AuditConnectionCleanupEventType definition ... HasProperty Variable 3:RelatedEndpoint 2:RelatedEndpointDataType 0:PropertyType M ConformanceUnits UAFX AutomationComponent Auditing Connection Cleanup AuditEvents of this class are generated by Servers that implement UAFX in the case when
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

8.8 ConnectionConfigurationSetProcessingSucceededEventType

transition from the Processing State to the Ready State after successful completion of the Connection establishment. Its representation in the AddressSpace is formally defined in Table 116 . Table 116 - ConnectionConfigurationSetProcessingSucceededEventType
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

8.9 ConnectionConfigurationSetProcessingFailedEventType

Processing State to the Error State as a result of encountering an error during Connection establishment. Its representation in the AddressSpace is formally defined in Table 117 . Table 117 - ConnectionConfigurationSetProcessingFailedEventType
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

8.10 EstablishConnectionErrorEventType

ConnectionConfigurationSet that is being processed . SourceName shall be the BrowseName of the Connection that was being created. If the error is not related to a specific Connection , then it shall ... that was being taken, e.g. resolving NodeIds , configuring an SKS, verifying Nodes , or establishing Connection . It shall include the FxErrorEnum value reported in the ConnectionDiagnosticsDataType associated with this error. ErrorCode
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

8.11 CloseConnectionErrorEventType

LogEntryConditionClassType . SourceNode shall be the NodeId of the ConnectionConfigurationSet that the connection belonged to . SourceName shall be the BrowseName of the Connection that was being closed. Message describes the issue ... with this error. ErrorCode shall contain the detailed error code returned in the Close Connection Method. ErrorCodeNode shall contain the NodeId of the Connection that was being closed. GroupingId shall
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

9.2.2 ServerAddressType definition

selected Address will be reflected in the ServerAddressDataType structure, which will be used for Connection establishment. SecurityMode is the MessageSecurityMode to be used for establishing a secure communication ... Address . The SelectionListType (see 6.8.1 ) will provide the supported SecurityModes for this Connection . RestrictToList shall be set to TRUE. Any selected SecurityMode will be reflected in the ServerAddressDataType structure, which
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

9.3.2 SecurityKeyServerAddressType definition

selected Address will be reflected in the SecurityKeyServerAddressDataType structure, which will be used in Connection establishment. SecurityPolicyUri is a string that contains the security policy to use when establishing ... secure communication. The SelectionListType (see 6.8.1 ) will provide the supported SecurityPolicyUris for this Connection . RestrictToList shall be set to TRUE. Any selected SecurityPolicyUri will be reflected in the SecurityKeyServerAddressDataType structure
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

10.19 ConnectionDiagnosticsDataType

ConnectionDiagnosticsDataType This Structure provides the status of a Connection in a ConnectionConfigurationSet . The ConnectionDiagnosticsDataType is formally defined in Table 164 . Table 164 - ConnectionDiagnosticsDataType structure Name Type Description ConnectionDiagnosticsDataType Structure Subtype ... Structure defined in OPC 10000-5 Name 0:QualifiedName BrowseName of the related < Connection > Node in the ConnectionConfigurationSet . LastActivity 4:LastActivityMask The last activity taken by the ConnectionManager
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

10.20 ConnectionStateEnum

ConnectionStateEnum The ConnectionStateEnum 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 ... items Name Value Description ConnectionNotMonitored 0 ConnectionManager does not monitor the state of the Connection ConnectionNotEstablished 1 Connection does not exist ConnectionInitial 2 Connection is being established, but the communication
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

10.30 LastActivityMask

last activity taken by a ConnectionManager processing a given ConnectionConfigurationSet (and, in turn, on Connection configurations within). If the OptionSet is zero (no bits set), then no activity related ... given Connection in the given ConnectionConfigurationSet has been taken. In this OptionSet, only one bit can be set except for the Error bit, which can be set with
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

10.42 RelatedEndpointDataType

related instance of ConnectionEndpointType , serving as the "other end" of the Connection . The RelatedEndpointDataType is formally defined in Table 210 . Table 210 - RelatedEndpointDataType structure Name Type Description RelatedEndpointDataType
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

13.1 Overview

requirements for this Client functionality. Some additional key points related to establishing a connection are: The Connection and security information may have changed since the engineering tool generated configuration information ... devices, i.e., on the same device that has one end of a logical connection. The configuration might contain Nodes in any of the following formats: PortableNodeId , PortableRelativePath or AliasName , each
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

13.3.1 General

General The Method Calls to establish a Connection require information from the ConnectionConfigurationSets and their components. That information may be represented as PortableNodeId , PortableRelativePath or AliasName . These all need
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

13.3.2 PortableNodeId provided

NamespaceArray of the target Server . This array can be checked before establishing a Connection to ensure it has not changed. Repeat for all Servers . When resolving NamespaceUri , if a null
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

13.3.3 PortableRelativePath provided

NamespaceArray of the target Server. This array can be checked before establishing a Connection to ensure it has not changed. Additionally, the NamespaceMetadata ( NamespacePublicationDate ) shall be cached. This data
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

13.3.4 AliasName provided

resolve all AliasNames in all records in the ConnectionConfigurationSet . The returned list of Servers ( Connection information) and NodeIds should be cached. Figure 72 - AliasName Resolution If an AliasName was used ... obtain the Server information, the connection process might be slightly different (illustrated in Figure 73 ). The AliasName Server provides the information required to connect to the Server . Once connected
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

D.3.6.5 Using groups

Float channels) and/or allow customized DataSets , depending on the setting of PreconfiguredDataSetOnly. A Connection can, for example, select Channel1 and Channel6. Figure D.27 illustrates this sample. Figure D.27 - ConnectionEndpoint using
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

D.3.7.4 Using ControlGroups with Connections

EngineeringUnits of Temperature (see Figure D.28 ) should not change during the lifetime of a Connection . A connection configuration to achieve this behaviour would establish the control of MonitorControl using ... SetConfigurationDataCmd , and reassign control to the ConnectionEndpoint using ReassignControlCmd . Then as long as the connection is established, the EngineeringUnits are locked and cannot be changed
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.1.2 Single logical connection

E.1.2 Single logical connection Figure E.1 depicts the configuration elements contained in a ConnectionConfigurationSet and their relation to each other for a single logical connection. The relation between the configuration ... resulting runtime elements (present or created on the AutomationComponents being part of the logical connection) is indicated by dashed arrows. Figure E.1 - ConnectionConfigurationSet overview (single logical connection) This ConnectionConfigurationSet contains
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.4.2 Bidirectional connection

E.4.2 Bidirectional connection The Connection configuration for a bidirectional connection contains the following configuration information (see Figure E.11 ): EndpointA, indicating InputVariables and OutputVariables, EndpointB, indicating InputVariables and OutputVariables, Flow1 ... Flow2 and SubA for the information flow from EndpointB to EndpointA. Figure E.11 - Bidirectional connection illustration
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.4.3 Unidirectional connection with heartbeat

E.4.3 Unidirectional connection with heartbeat The Connection configuration for a unidirectional connection with heartbeat contains the following configuration information (see Figure E.12 ): EndpointA, indicating OutputVariables, EndpointB, indicating InputVariables, Flow1 ... EndpointB, Flow2 and SubA for the heartbeat from EndpointB to EndpointA. Figure E.12 - Unidirectional connection with heartbeat illustration
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.4.4 Unidirectional connection

E.4.4 Unidirectional connection The Connection configuration for a unidirectional connection contains the following configuration information (see Figure E.13 ): EndpointA, indicating OutputVariables, EndpointB, indicating InputVariables, Flow1 and SubB describing the configuration ... information flow from EndpointA to EndpointB. Figure E.13 - Unidirectional connection illustration
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.4.5 Autonomous publisher

E.4.5 Autonomous publisher The Connection configuration for an autonomous Publisher contains the following configuration information (see Figure E.14 ): EndpointA, indicating OutputVariables; Flow1, describing the configuration for the information flow from
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.4.6 Autonomous subscriber

E.4.6 Autonomous subscriber The Connection configuration for an autonomous subscriber contains the following configuration information (see Figure E.15 ): EndpointA, indicating InputVariables, Flow1 and SubA describing the configuration for the information
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.4.7 PubSub DataSets

skip any values that it is not interested in. In a ConnectionConfigurationSet , a specific Connection can use a preconfigured DataSet or dynamically create a DataSet for the Publisher or Subscriber ... engineering tool. Three possible combinations of DataSets exist for an information flow on a Connection between two FunctionalEntities to be configured: Preconfigured DataSets exist on both endpoints. A preconfigured DataSet
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.5 Interaction with an SKS

capabilities. The SKS will return keys only if it trusts the Client making the connection and the SecurityGroupId is known. The pull can be triggered on the Subscriber ... configured. Retry intervals can affect how fast communication starts for a Connection . Typically, a retry interval should be short enough to not delay communication but not so short that
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.6.6 Loading / Saving ConnectionConfigurationSets

EstablishConnections (see 6.16.3.2 ). No issues exist in using the structure to set up a Connection , but if the configuration of the ConnectionManager Server is saved as a UANodeSet XML File
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

F.1.2.5 Optional fields

F.1.2.5 Optional fields Connection configuration and communication flow-related configuration Structures use Structures with optional fields to handle the optional Variables . In other configuration Structures , AllowSubtypes is needed. Since AllowSubtypes
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

F.1.3 ConnectionConfigurationSetConfDataType

null or empty String array. False Connections 4:ConnectionConfigurationConfDataType[] A list of Connection configurations to be established. False CommunicationFlows 4:CommunicationFlowConfigurationConfDataType[] A list of communication model-specific configurations to apply ... addressing information for AutomationComponents . False AutomationComponentConfigurations 4:AutomationComponentConfigurationConfDataType[] A list of AutomationComponents used for Connection establishment. False RollbackOnError 0:Boolean Indicates the behaviour that should be followed when there
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

F.1.4 ConnectionConfigurationConfDataType

F.1.4 ConnectionConfigurationConfDataType This Structure DataType holds the information for a Connection configuration. It is semantically equivalent to the ConnectionConfigurationType as defined in 6.10.2 , except that the element ProcessingResult, as defined ... ConnectionConfiguration False Endpoint1 4:ConnectionEndpointConfigurationConfDataType The configuration information for the first endpoint of the Connection. False Endpoint2 4:ConnectionEndpointConfigurationConfDataType The configuration information for the optional second endpoint of the Connection
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

F.1.5 ConnectionEndpointConfigurationConfDataType

FunctionalEntityNode 4:NodeIdentifier FunctionalEntityNode specifies the identifier of the FunctionalEntity to configure for the Connection . If a RelativePath is specified, the path shall be relative to FxRoot . False FunctionalEntityNodeSelection ... filled in by the ConnectionManager after getting the NodeIds from the AutomationComponent during connection establishment. True PreconfiguredSubscribedDataSet 0:String If it is not an empty string, it specifies the name
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

F.1.9 AutomationComponentConfigurationConfDataType

AutomationComponentConfigurationConfDataType This Structure DataType holds the information related to the AutomationComponent participating in a Connection . It is semantically equivalent to the AutomationComponentConfigurationType as defined in 6.13.2 . The AutomationComponentConfigurationConfDataType is formally ... ServerAddressIndex 0:Int32 Reference to the related Server in the ServerAddresses array of the connection set structure. False The AutomationComponentConfigurationConfDataType representation in the AddressSpace is formally defined in Table F.16
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

G.1 Diagnostics Client

ConnectionManager is describe in 13 . A ConnectionManager could monitor both sides of Connection it has created, it could monitor only one side of a Connection (the side that ... Monitor Overview If collecting diagnostics from a ConnectionManager that monitors both sides of a connection(CM2 in illustration), the diagnostics Client will only need to subscribe to the AggregatedCurrentState reported
OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking

5.3.2 HostName resolution using DNS

HostName resolution could be used: with UA Client Server communications, such as during UAFX connection establishment, and PubSub communications to exchange the real-time data for a Connection . Figure
OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking

5.6.1 Overview

kinds of communications. For example, the exchange of control data via OPC UA PubSub , connection establishment via OPC UA Client Server , link-local communication, e.g., LLDP (see 7.3 ) and gPTP ... translate the abstract QoS category and label of a Connection to concrete priority values in the message. Similarly, the UA Communication Stack can use the representation of VLAN interfaces
OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking

5.6.3 VLANs

layer, this abstract VLAN interface name can be used for ease of use during Connection engineering if the VLAN interface name has not explicitly been adapted. Moreover, the mapping from ... VLAN interface name to a concrete VLAN ID can still be adapted prior to connection establishment (see 5.6.4.5 ). This decoupling allows for any necessary adjustments, e.g., if the default VLAN
OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking

5.6.4.2 Application and QoS engineering

Station Components (see 6.3 ) on their Controller. Next, Controls Engineers set up the Connection configurations needed for sharing data between Controllers . As a final step, Connection configurations are transferred ... ConnectionManager that establishes the Connections during the workflow's connection establishment and operation phase (see 5.6.4.5 ). This subclause describes the details of these steps, including the setup of network interface
OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking

5.6.4.4 System integration

update the PubSubCommunicationFlowConfiguration Variable in the ConnectionManager's Information Model to adapt the Connection configurations for QoS settings and network settings such as setting destination IP addresses and network interface
OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking

5.6.4.5 Connection establishment and operation

Connection 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 ... Figure 11 - PubSub QoS and addressing configuration variables The ConnectionManager establishes Connections using the Connection configuration as set up by the Controls Engineer (see 5.6.4.2 ) and System Commissioner
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

6.3 Descriptor with configuration information

used for the continuation of the work of the next Controls Engineer. When a Connection needs to be defined between two Controllers , the two Controls Engineers may provide information about ... Controls Engineer , who is configuring the ConnectionManager component that is responsible for the connection establishment. A Descriptor with configuration information is typically built based on data from Descriptors with product
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles

6.6.2.8 UAFX IFunctionalEntity Run-Time Diagnostic Counters Facet

Time Diagnostic Counters Facet. This Facet includes the functionality needed for tracking FunctionalEntity Connection operation activities. Table 22 - UAFX IFunctionalEntity Run-Time Diagnostic Counters Facet Group Conformance Unit / Profile Title
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles

6.6.2.9 UAFX IFunctionalEntity Establishment Diagnostic Counters Facet

IFunctionalEntity Establishment Diagnostic Counters Facet. This Facet includes the functionality needed for tracking FunctionalEntity Connection establishment activities. Table 23 - UAFX IFunctionalEntity Establishment Diagnostic Counters Facet Group Conformance Unit / Profile Title
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles

6.6.4.8 UAFX ConnectionManager Diagnostic Counters Facet

ConnectionManager Diagnostic Counters Facet. This Facet includes the functionality needed for ConnectionManager tracking of Connection establishment. Table 47 - UAFX ConnectionManager Diagnostic Counters Facet Group Conformance Unit / Profile Title Optional UAFX