Search

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

59 result(s) for ConnectionConfigurationSet

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

3.3 Conventions used in this document

following phrase, "an instance of ConnectionConfigurationSetType ," can be replaced with "a ConnectionConfigurationSet ". The phrase "instances of ConnectionEndpointType" can be replaced with " ConnectionEndpoints
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

3.3.3 Usage of Instance of a type

following phrase, "an instance of ConnectionConfigurationSetType ," can be replaced with "a ConnectionConfigurationSet ". The phrase "instances of ConnectionEndpointType " can be replaced with " ConnectionEndpoints
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

4.7.2 Creating / Monitoring / Closing Connections

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

5.5.2 Generation, deployment, and modification

configuration data represented by one or more logical connections are defined in a ConnectionConfigurationSet . The instances can also include configuration information for the utilized OPC UA communication model (e.g., PubSub ... 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 at commissioning time or communication
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

5.5.3 Establishing and closing Connections

AutomationComponents to establish the logical connections. For each logical connection to be established, the ConnectionConfigurationSet includes: address information, e.g., Server address, BrowsePath to the AutomationComponent , FunctionalEntity, etc., optional parameters
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.2.7 PublisherCapabilitiesType

that are part of the AutomationComponent . When the preconfigured PublishedDataSet is used in a ConnectionConfigurationSet , Connections shall be established to one or more of the FunctionalEntities whose variables are present
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.2.8 SubscriberCapabilitiesType

that are part of the AutomationComponent . When the preconfigured StandaloneSubscribedDataSet is used in a ConnectionConfigurationSet , Connections shall be established to one or more of the FunctionalEntities whose variables are present
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.7.1 Overview

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

6.7.3.2 Establishing Connections

Establishing 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 ... Figure 35 for an 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
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.7.3.3 Closing Connections

Closing 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 Model

6.7.4 EditConnectionConfigurationSets Method

ConnectionConfigurationSets shall be as if this Method was called with a DiscardUpdates Action . For ConnectionConfigurationSet, which is already in edit mode and locked to this Client Session, no action shall ... performed on this ConnectionConfigurationSet, and a successful result will be returned. If Action is CommitUpdates , the Method shall set the Property Edit to FALSE for all requested ConnectionConfigurationSets . The ConnectionManager
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.7.5.2 ProcessConnectionConfigurationSets signature

list to determine the status of the individual Call to Trigger processing on each ConnectionConfigurationSet . For possible values for StatusCode , see Table 86 . The possible Method result codes are formally ... Table 86 - Results StatusCodes Result Code Description Good Changing the State succeeded for the ConnectionConfigurationSet . Bad_NodeIdInvalid The syntax of the NodeId is not valid. Bad_NodeIdUnknown The NodeId refers
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.7.5.3.2 ActionRemoveConnections

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

6.7.5.3.3 ActionEnableConnections

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

6.7.5.3.4 ActionDisableConnections

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

6.8.1 Overview

Figure 11 label 3). The ConnectionManager may expose the ConnectionConfigurationSets in its AddressSpace . A ConnectionConfigurationSet exposes diagnostic information about the Connections as part of its Information Model . It also allows ... could provide an interface to trigger the processing of such Connection configurations. A ConnectionConfigurationSet may only be modified by a standard Client as follows: The SelectionListType
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.8.2 ConnectionConfigurationSetType definition

True 4:<Connection> 4:Endpoint2 ConnectionConfigurationSetStateMachine contains the current State of this ConnectionConfigurationSet . See 6.9 for a formal definition of the state machine. If Edit is present ... ConnectionConfigurationSet supports transactional editing. If Edit is TRUE, the ConnectionConfigurationSet is currently being edited by a Client . See 6.7.4 on editing a ConnectionConfigurationSet . <Connection> represents one or more
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.9.1 Overview

coordinate actions executed internally (a ConnectionManager establishing Connections ) that involve the processing of a ConnectionConfigurationSet . The States and Transitions that comprise the state machine are illustrated in Figure 38 . Numbers ... Error for several reasons. Transient errors will be resolved by re-processing the ConnectionConfigurationSet . If the transient error has cleared, the state machine will transition to Ready ; otherwise, it will
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.9.2 ConnectionConfigurationSetStateMachineType definition

TransitionNumber 2 4:ProcessingToError 0:TransitionNumber 3 4:ErrorToProcessing 0:TransitionNumber 4 Ready - A ConnectionConfigurationSet in this State may be processed by the ConnectionManager . Processing - A ConnectionConfigurationSet in this State ... Internals of the processing executed in this State are described in 6.7.5 . Error - A ConnectionConfigurationSet in this State indicates an error has occurred during Processing . ReadyToProcessing - This transition shall
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.16.3.2 PubSubCommunicationModelConfigurationType definition

PubSubConfiguration and ConfigurationReferences are generated by the engineering tool creating the ConnectionConfigurationSet or by the ConnectionManager . The relation of configuration elements in PubSubConfiguration to a ConnectionEndpoint is provided ... determine all names and identifiers. For certain elements in PubSubConfiguration , the entity generating the ConnectionConfigurationSet may set their names (i.e., PubSubConnection , ReaderGroup , WriterGroup , DataSetReader , DataSetWriter ) to a specific value
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

8.5 AuditUpdateConnectionConfigurationSetEventType

AuditUpdateConnectionConfigurationSetEventType This EventType allows auditing modifications of a ConnectionConfigurationSet . Its representation in the AddressSpace is formally defined in Table 114 . Table 113 - AuditUpdateConnectionConfigurationSetEventType definition Attribute Value BrowseName 4:AuditUpdateConnectionConfigurationSetEventType IsAbstract ... HasProperty Variable 4:Name 0:String 0:PropertyType M ConformanceUnits UAFX Auditing ConnectionConfigurationSet Modification This EventType inherits all Properties of the AuditWriteUpdateEventType . Their semantics are defined
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

8.6 ConnectionConfigurationSetEventType

ConnectionManager that is executing the state machine. ConnectionConfigurationSetNode and Name identify the ConnectionConfigurationSet , which was processed. Action identifies the action that was requested to process the ConnectionConfigurationSet . If ConnectionManagerLog
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

8.7 ConnectionConfigurationSetProcessingStartedEventType

Processing State as a result of a ConnectionManager starting to process the ConnectionConfigurationSet . Its representation in the AddressSpace is formally defined in Table 115 . Table 115 - ConnectionConfigurationSetProcessingStartedEventType Definition Attribute Value
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

8.10 EstablishConnectionErrorEventType

ConditionClassId shall be set to LogEntryConditionClassType . SourceNode shall be the NodeId of the ConnectionConfigurationSet that is being processed . SourceName shall be the BrowseName of the Connection that was being created ... generated, one for each error code. ErrorCodeNode shall contain the internal Node in the ConnectionConfigurationSet to which the error is related. For example, if the error was related
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

8.11 CloseConnectionErrorEventType

ConditionClassId shall be set to 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
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 ... Name 0:QualifiedName BrowseName of the related < Connection > Node in the ConnectionConfigurationSet . LastActivity 4:LastActivityMask The last activity taken by the ConnectionManager on the Connection indicated by Name
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

10.30 LastActivityMask

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 (no bits ... then no activity related to the given Connection in the given ConnectionConfigurationSet has been taken. In this OptionSet, only one bit can be set except for the Error bit, which
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

11.4 HasAutomationComponentConfiguration ReferenceType

subtype of HasComponent ReferenceType . The SourceNode of this ReferenceType shall be a ConnectionConfigurationSet . The TargetNode of this ReferenceType shall be an instance of AutomationComponentConfigurationType. The HasAutomationComponentConfiguration ReferenceType is formally defined
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

11.10 HasCommunicationFlowConfiguration ReferenceType

subtype of HasComponent ReferenceType . The SourceNode of this ReferenceType shall be a ConnectionConfigurationSet . The TargetNode of this ReferenceType shall be an instance of CommunicationFlowConfigurationType or a subtype
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

11.11 HasConnectionConfiguration ReferenceType

subtype of HasComponent ReferenceType . The SourceNode of this ReferenceType shall be a ConnectionConfigurationSet . The TargetNode of this ReferenceType shall be an instance of ConnectionConfigurationType or a subtype
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

11.17 HasServerAddress ReferenceType

subtype of HasComponent ReferenceType . The SourceNode of this ReferenceType shall be a ConnectionConfigurationSet . The TargetNode of this ReferenceType shall be an instance of ServerAddressType or a subtype
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

13.3.1 General

illustration of what needs to be done for each possible Node description in the ConnectionConfigurationSet . It is recommended that the ConnectionManager caches the results of these operations and that they
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

13.3.3 PortableRelativePath provided

PortableRelativePath provided If the ConnectionConfigurationSet contains PortableRelativePaths , then the Client should perform the following steps ( Figure 70 provides an overview of the configuration and actions): Resolve the location
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

13.3.4 AliasName provided

AliasName provided If the ConnectionConfigurationSet contains AliasNames ( Figure 72 provides an overview of the configuration), then the Client should perform the following steps: Connect to the well-known ... AliasName Server can 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
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

13.5 ConnectionManager error reporting

ConnectionManager 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 ... ConnectionConfigurationSet as described in this subclause, such as finding or connecting to a Server , resolving Node Information by AliasName lookup or TranslateBrowsePathToNodeId, or even for Namespace lookup issues. The ConnectionManager
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.1.1 Overview

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 set. A ConnectionConfigurationSet
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 ... AutomationComponents being part of the logical connection) is indicated by dashed arrows. Figure E.1 - ConnectionConfigurationSet overview (single logical connection) This ConnectionConfigurationSet contains one Connection configuration Connection1, which contains the configuration
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.1.3.2 Multiple logical connections - two AutomationComponents

Multiple logical connections - two AutomationComponents Figure E.2 depicts the configuration elements contained in a ConnectionConfigurationSet and their relation to each other for multiple logical connections between two AutomationComponents . Often, traffic
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.1.3.3 Multiple logical connections - multiple AutomationComponents

Multiple logical connections - multiple AutomationComponents Figure E.4 depicts the configuration elements contained in a ConnectionConfigurationSet and their relation to each other for multiple logical connections among multiple AutomationComponents . Figure ... Multiple logical connections using multicast This ConnectionConfigurationSet contains two ConnectionConfigurations, Connection1 and Connection2. Since outbound traffic from AC_A is using multicast in this scenario, both EndpointA1 and EndpointA2 refer
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.2.1 Overview

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

E.2.2.1 For logical connections between two AutomationComponents

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

E.2.2.2 For logical connections between multiple AutomationComponents

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

E.4.1 Overview

communication model. For simplicity, all samples describe a single logical connection contained in the ConnectionConfigurationSet. Note, however, that as shown in E.1.3 , a ConnectionConfigurationSet can contain multiple Connections , which could
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 ... PublishedDataSetData or SubscribedDataSetData (see F.1.5 ) or within the vendor-specific format. A ConnectionConfigurationSet might contain multiple Connections that all need to be communicating as a set. In this case
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.5 Interaction with an SKS

Information Model . The SKS responsible for generating the security keys related to a ConnectionConfigurationSet is indicated in the ConnectionConfigurationSet by the SecurityKeyServer configuration. In addition, the SecurityKeyServer indicates whether ... desired configuration for the SKS from the set of SecurityGroups and PubSubKeyPushTargets in the ConnectionConfigurationSet Object and PubSubCommunicationModelConfigurations of all AutomationComponentConfigurations in the ConnectionConfigurationSet (see 6.16.3 and Figure
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.6.1 Overview

E.6.1 Overview If using PubSub as a communication model, the ConnectionConfigurationSet contains a PubSubConfiguration Variable for each AutomationComponent's CommunicationModelConfig that has a DataType that is a large structure. This ... possible adjustment, some aspects of the large structure are exposed as Variables in the ConnectionConfigurationSet . Figure E.25 illustrates the relation between elements in the ConnectionConfigurationSet and the PubSubConfiguration . Note that
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.6.2 ConnectionConfigurationSet and WriterGroup

E.6.2 ConnectionConfigurationSet and WriterGroup As defined in OPC 10000-14 , a WriterGroup defines the Publisher of a NetworkMessage . It is recommended that the PubSubConfiguration contains a WriterGroup for each instance ... related PubSubConnection information, as illustrated in Figure E.26 , will be updated. Figure E.26 - ConnectionConfigurationSet and WriterGroup It is recommended to update WriterGroupId and PublisherId after issuing the ReserveCommunicationIdsCmd
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.6.6 Loading / Saving ConnectionConfigurationSets

E.6.6 Loading / Saving ConnectionConfigurationSets The ConnectionConfigurationSet can contain a PubSubConfiguration , which has a datatype of PubSubConfiguration2DataType . The PubSubConfiguration2DataType is a complex structure that can include DataSets (published or subscribed) that ... Server , which is very likely to be a different Server . Depending on how the ConnectionConfigurationSet and PubSubConfiguration were generated, the Namespaces could not exist on the ConnectionManager Server . This document
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

F.1.1 Overview

annex describes DataTypes that can be used to serialize the Objects that compose a ConnectionConfigurationSet (see 6.8 and 6.10 ) into a single structure ( ConnectionConfigurationSetDataType) . The ConnectionConfigurationSetDataType can, for example ... used for persisting a ConnectionConfigurationSet , for storing it within a File (see F.2 ), or for maintaining the configuration of a ConnectionManager (see F.3 ). For the base principles used
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

F.1.2.2 Namespaces

complete Server . For a UANodeSet XML file, it is the file. A ConnectionConfigurationSet (see 6.8.2 ) contains node identifiers related to different scopes, as illustrated in Figure F.2 . In this illustration ... ConnectionConfigurationSet contains 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
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

F.1.2.4 Extensibility

subtyping. This is a problem if Structures are embedded into other Structures , e.g., the ConnectionConfigurationSet -related Structure has an array of AutomationComponent related Structures . Therefore, each Structure has an additional
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

F.1.3 ConnectionConfigurationSetConfDataType

F.1.3 ConnectionConfigurationSetConfDataType This Structure DataType is used to hold the information for a ConnectionConfigurationSet . It is semantically equivalent to the ConnectionConfigurationSetType as defined in 6.8.2 with the exception that ... BrowseName 0:String String part of the BrowseName of the ConnectionConfigurationSet . False ConnectionConfigurationSetFolder 0:String[] Optional path of the ConnectionConfigurationSet folder used to group ConnectionConfigurationSets where each entry
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

F.3.3.1 CloseAndUpdate signature

empty. Table F.41 - CloseAndUpdate OperationResult Element Result Codes ResultCode Description Bad_BrowseNameDuplicated A ConnectionConfigurationSet with the BrowseName already exists in the ConnectionConfigurationSetFolder . The ConnectionConfigurationSet cannot be added. Bad_NoMatch ... ConnectionConfigurationSet with the BrowseName does not exist in the ConnectionConfigurationSetFolder . The ConnectionConfigurationSet cannot be removed or replaced. Bad_NothingToDo No ConnectionConfigurationSetOperation was specified. Bad_InvalidArgument An invalid combination of ConnectionConfigurationSetOperation
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

F.3.3.2.2 ElementAdd

F.3.3.2.2 ElementAdd The ConnectionConfigurationSetOperation ElementAdd adds the ConnectionConfigurationSet to the ConnectionConfigurationSets Folder tree in the Folder specified by the ConnectionConfigurationSetFolder . If Folders on the given path do not exist, they ... will be created. The operation ElementAdd does not include processing the ConnectionConfigurationSet . Processing can be triggered either by a Client using the ProcessConnectionConfigurationSets Method (see 0 ) or by vendor-specific
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

F.3.3.2.3 ElementRemove

F.3.3.2.3 ElementRemove The ConnectionConfigurationSetOperation ElementRemove removes the ConnectionConfigurationSet from the ConnectionConfigurationSetFolder. For ElementRemove, all elements of the ConnectionConfigurationSetConfDataType except BrowseName and ConnectionConfigurationSetFolder are ignored and may be set to null ... AutomationComponents (see 6.2.5 ) with Remove set to TRUE for all Connections contained in the ConnectionConfigurationSet
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

F.3.3.2.4 ElementReplace

F.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 ... contained Connections in the ConnectionConfigurationSet . The operation ElementReplace does not include processing the new ConnectionConfigurationSet . Processing can be triggered either by a Client using the ProcessConnectionConfigurationSets Method
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

F.3.4 ConnectionConfigurationSetOperation

ConnectionConfigurationSetOperation values Value Bit No. Description ElementAdd 0 If this bit is set, the ConnectionConfigurationSet is added to the ConnectionManager configuration. ElementRemove 1 If this bit is set, the ConnectionConfigurationSet ... removed from the ConnectionManager configuration. The ConnectionConfigurationSet to be removed is identified via the string part of the BrowseName and the ConnectionConfigurationSetFolder . All other elements in the ConnectionConfigurationSetConfDataType are ignored
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

G.1 Diagnostics Client

then the diagnostics Client would then have to read the ConnectionDiagnostics array from each ConnectionConfigurationSet to determine which ConnectionConfigurationSet (and actual Connection ) has encountered a problem. For some error cases
OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking

3.3.2 Usage of Instance of a type

following phrase, "an instance of ConnectionConfigurationSetType, " can be replaced with "a ConnectionConfigurationSet ". The phrase "instances of ConnectionEndpointType" can be replaced with " ConnectionEndpoints