Search

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

36 result(s) for ConnectionEndpoints

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

3.3 Conventions used in this document

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

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.6 FunctionalEntities and applications

models. The FunctionalEntity includes Connection information that reflects the established communication model, represented by ConnectionEndpoints . For more information
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

4.7.2 Creating / Monitoring / Closing 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 . For example ... Vendor-specific diagnostic applications monitor Connections defined in ConnectionConfigurationSets on a ConnectionManager and the ConnectionEndpoints on AutomationComponents to present comprehensive Connection information to the operator or engineers, including identification information
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

5.5.1 Overview

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. Figure 28 provides a more
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

5.6 Health

Health Assets , FunctionalEntities , ConnectionEndpoints , and ConnectionConfigurationSets provide general health status and diagnostic conditions. This health status is aggregated from child Objects to parent Objects (e.g., from ConnectionEndpoints to the FunctionalEntity
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.2.4.1 Overview

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

6.2.4.3.9.2 PubSub

implementation shall abort processing as described in 6.2.4.3.11 . The EstablishConnections implementation shall verify that ConnectionEndpoints with their IsPersistent Property set to TRUE reference a DataSetReader and/or DataSetWriter which are persisted
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.2.4.3.10.1 General

EstablishConnections implementation shall enable all communication model-specific Objects related to the ConnectionEndpoints in an atomic operation
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.2.4.3.11 Abort

Rollback actions Command Rollback action VerifyAssetCmd None VerifyFunctionalEntityCmd None ReserveCommunicationIdsCmd None CreateConnectionEndpointCmd All ConnectionEndpoints in the context of this Method Call shall be deleted. EstablishControlCmd All requested ControlGroups requested
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.2.5.1 CloseConnections signature

below, and the arguments are described in Table 22 . Signature CloseConnections ( [in] 0:NodeId[] ConnectionEndpoints, [in] 0:Boolean Remove, [out] 0:StatusCode[] Results ); Table 22 - CloseConnections Method arguments Argument Description ... ConnectionEndpoints The list of Connections to be closed. Remove When TRUE, the Objects dynamically created for the Connection are removed. Results The results of closing the Connections identified
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.2.5.2 CloseConnections behaviour

behaviour The Method implementation shall disable all communication model Objects for each element in ConnectionEndpoints in an atomic operation. For additional details on ConnectionEndpoints, see 6.6 , and PubSubConnectionEndpoints ... PubSub configuration model is not exposed) if no further References from other ConnectionEndpoints exist. Their parent Objects ( WriterGroup , ReaderGroup , PubSubConnection , and PublishSubscribe ) shall be left in their current state
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.4.2 FunctionalEntityType definition

PublisherCapabilitiesType O 0:HasComponent Object 3:SubscriberCapabilities 3:SubscriberCapabilitiesType O 0:HasComponent Object 3:ConnectionEndpoints 3:ConnectionEndpointsFolderType O 0:HasComponent Object 3:ControlGroups 3:ControlGroupsFolderType O 0:HasComponent Variable ... Output-/InputData level only apply to that data, i.e. not for heartbeats. The ConnectionEndpoints Folder provides a container for all Connection -related information that this FunctionalEntity might contain. For details
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.4.8 ConnectionEndpointsFolderType

ConformanceUnits UAFX FunctionalEntity Base The optional CommHealth aggregates the Status of all ConnectionEndpoints contained in the Folder . The aggregation rules are defined as follows: If at least one ConnectionEndpoint established
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.6.1 Overview

FunctionalEntities for data exchange. It provides information about which InputVariables and/or OutputVariables are exchanged. ConnectionEndpoints reside in the ConnectionEndpoints Folder of a FunctionalEntity . The ConnectionEndpointType is illustrated in Figure
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.6.2 ConnectionEndpointType definition

path to the connected FunctionalEntity . IsPersistent indicates if the ConnectionEndpoint shall be persistent. Persistent ConnectionEndpoints shall be restored following a power cycle by the AutomationComponent . The restoration of a persistent ... Objects An AutomationComponent indicates support for persistent Connections ; see SupportsPersistence in 6.2.6 . Non-persistent ConnectionEndpoints following a power cycle behave as if the CloseConnections Method was called with Remove
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.7.3.2 Establishing Connections

Figure 35 - ConnectionConfigurationSet example The EstablishConnections Method (see 6.2.4 ) is used to establish ConnectionEndpoints on an AutomationComponent . The Method allows for the establishment of multiple Connections with a single Call ... arguments required for the EstablishConnections Call (see 13 ). If any of the ConnectionEndpoints require SKS configuration, the ConnectionManager shall also call the SKS and add the appropriate configuration ( SecurityGroups and/or
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.7.3.3 Closing Connections

initiate a ProcessingToError transition in the ConnectionConfigurationSetStateMachine (see 6.9 ). If any of the ConnectionEndpoints require SKS configuration and were removed, the ConnectionManager shall also remove the appropriate configuration from
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.7.5.3.2 ActionRemoveConnections

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 Model

6.7.5.3.3 ActionEnableConnections

ConnectionConfigurationSet , the ConnectionManager shall call the EstablishConnections Method containing the EnableCommunicationCmd for all contained ConnectionEndpoints . See 6.7.3.2 for ConnectionManager behaviour
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.7.5.3.4 ActionDisableConnections

call the CloseConnections Method (see 6.2.5 ) with Remove set to FALSE 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 Model

6.7.6 ConnectionManagerCapabilitiesType

describes the capability of the ConnectionManager Information Model to report status information for all ConnectionEndpoints of all Connections created by this ConnectionManager . This capability extends the MonitorsLocalConnectionEndpoints capability and shall
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.8.2 ConnectionConfigurationSetType definition

updated every time the ConnectionManager finishes processing the ConnectionConfigurationSet. If a ConnectionManager monitors ConnectionEndpoints , it shall also update the value when it acquires new information about the status
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

10.9 CommHealthOptionSet

CommHealthOptionSet This OptionSet defines flags indicating the health of the ConnectionEndpoints . The CommHealthOptionSet values are formally defined in Table 139 . Table 139 - CommHealthOptionSet values Value Bit No. Description CommInitial ... least one of the ConnectionEndpoints has its Status set to Initial . CommPreOperational 1 At least one of the ConnectionEndpoints has its Status set to PreOperational . CommError 2 At least
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

10.13.4 ClientServerCommunicationLinkConfigurationDataType

ClientServerCommunicationLinkConfigurationDataType Provides the configuration of references between ConnectionEndpoints and Object instances specific to the Client Server communication model. This DataType will be specified in a future version of this document
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

10.19 ConnectionDiagnosticsDataType

with specific error information at any time. This may include errors related to monitored ConnectionEndpoints (see FxErrorEnum RuntimeError ) or errors related to the operation of a local SKS (see FxErrorEnum ... failure to verify Assets on a single AutomationComponent affects all Connections that have ConnectionEndpoints in that AutomationComponent ). Finally, some failures affect only single ConnectionEndpoints , e.g. failure to create a ConnectionEndpoint
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

10.20 ConnectionStateEnum

Connection ; ConnectionManager has successfully removed the Connection ; ConnectionManager detected that one or both ConnectionEndpoints have been removed (e.g., due to ConnectionEndpoint auto-cleanup or AutomationComponent power-cycle). ConnectionStateEnum combines ... Status of all ConnectionEndpoints participating in a Connection (see 10.20 ). For Connection types bidirectional, unidirectional and unidirectional with heartbeat, the value is calculated according to Figure 58 . Figure
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

10.23 FxCommandMask

requested functional entities. CreateConnectionEndpointCmd 2 The addressed Server shall create or modify ConnectionEndpoints . EstablishControlCmd 3 The addressed Server shall establish control over the requested ControlGroups . SetConfigurationDataCmd 4 The addressed Server
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

10.34 OperationalHealthOptionSet

Bits 0:15 contain an aggregation of the CommHealthOptionSet (see 10.9 ) from the associated ConnectionEndpoints (definition is repeated here for tools) . Bits 16-19 represent the FunctionalEntity status
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

10.42 RelatedEndpointDataType

String The name of the ConnectionEndpoint . In case an AutomationComponent does not expose ConnectionEndpoints in its Information Model , ConnectionEndpointName is set to null. A RelatedEndpointDataType is set to null
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

D.3.6.3 Using preconfigured and customized DataSets

connection. Figure D.23 - Sample for analogue input module - preconfigured and customized DataSet ConnectionEndpoints established on that FunctionalEntity can use a preconfigured or customized DataSet as illustrated in Figure D.24 . Conn ... using the customized PublishedDataSet PDS_B. Figure D.24 - Preconfigured and customized DataSet used by ConnectionEndpoints
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.1.2 Single logical connection

configuration for a single logical connection. Connection1 contains two ConnectionEndpointConfigurations for the two ConnectionEndpoints EndpointA and EndpointB. Each ConnectionEndpointConfiguration contains all parameters required for creating the ConnectionEndpoint , verifying the affected
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

G.1 Diagnostics Client

state of an established Connection . A Connection is considered to be established when all ConnectionEndpoints required by it (see 5.5.1 ) exist
OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking

3.3.2 Usage of Instance of a type

ConnectionConfigurationSet ". The phrase "instances of ConnectionEndpointType" can be replaced with " ConnectionEndpoints
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles

5.2.5 UAFX FunctionalEntity

Interface, including the Tuning FunctionalGroup of the IFunctionalEntity Interface ConfigurationData Component. Server UAFX IFunctionalEntity ConnectionEndpoints Supports ConnectionEndpoints of the IFunctionalEntity Interface . Server UAFX ConnectionEndpointsFolder CommHealth Supports CommHealth of the ConnectionEndpointsFolder
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles

5.4.4.2 UAFX Descriptor Contents - UAFX Information Model

ConnectionEndpoint Base If the product supports the UAFX ConnectionEndpoint Base ConformanceUnit and includes preconfigured ConnectionEndpoints , the AML descriptions of all instances of subtypes of ConnectionEndpointType and their contents are included ... Objects required by that ConformanceUnit and their contents are included. Offline UAFX Descriptor IFunctionalEntity ConnectionEndpoints If the product supports the UAFX IFunctionalEntity ConnectionEndpoints ConformanceUnit and includes preconfigured ConnectionEndpoints