Search

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

25 result(s) for ConfigurationData

OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

4.6 FunctionalEntities and applications

identifying the information to be exchanged, establishing exclusive access (locking) to the information, setting ConfigurationData , configuring the communication, and finally, enabling the communication. An established Connection is represented
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

5.1 Overview

identity and compatibility verification of Asset and FunctionalEntity , establishing control via ControlGroup selection, setting ConfigurationData , and communication configuration. These concepts are mapped to existing OPC UA communication models
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

5.3 ControlGroups

control will often result in the locking of configuration or restricted access to ConfigurationData as defined by the FunctionalEntity (when the ControlGroup was defined). ControlGroups expose what restriction would occur
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

5.4 ConfigurationData

ConfigurationData ConfigurationData describes a collection of Variables within a FunctionalEntity that are used to set up and configure its functionality. As part of establishing a Connection between FunctionalEntities , some configuration ... required for the actual communication. The EstablishConnections Method allows any of the FunctionalEntity's ConfigurationData to be set. ConfigurationData can contain Variables that have the AccessLevelEx Attribute NonVolatile
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.2.4.1 Overview

allows for creating ConnectionEndpoints , establishing control, verifying FunctionalEntity and Asset compatibility, applying ConfigurationData , and configuring the communication model to be used for data exchange. It is recommended that this Method
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.2.4.2 EstablishConnections signature

CommandMask SetConfigurationDataCmd is set, at least one of the ConnectionEndpointConfigurations elements shall contain ConfigurationData with at least one element. If CommandMask SetConfigurationDataCmd is not set, all ConfigurationData in all ConnectionEndpointConfigurations ... CommandMask ReserveCommunicationIdsCmd is not set, ReserveCommunicationIds shall be null or empty. CommunicationConfigurations Provides the ConfigurationData specific to the communication model utilised by the provided Connections . For a formal definition
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.2.4.3.1 Overview

restricted regarding the size of the Arguments issued in a single call, e.g. ConfigurationData . How the commands are processed is described in Subclauses 6.2.4.3.2 to 6.2.4.3.10 . Figure 20 - Command processing
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.2.4.3.7 Command SetConfigurationDataCmd

Value to the Key for each element in ConnectionEndpointConfigurations and each element in ConfigurationData . If the ConnectionEndpoint related to ConfigurationData has IsPersistent set, SetStoredVariables (see 6.4.6.3 ) shall be called ... indicated by Key having the NonVolatile bit in the AccessLevelEx Attribute not set. If ConfigurationData is empty, ConfigurationDataResult shall be set to null or empty (see 10.15 ). The EstablishConnections implementation
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.2.5.2 CloseConnections behaviour

Objects referenced by other ConnectionEndpoints shall not be removed. What occurs with the ConfigurationData that was applied when establishing the ConnectionEndpoints is vendor-specific. NOTE A FunctionalEntity could provide application ... specific behaviour for its ConfigurationData , i.e. it might roll it back to a predetermined setting, or it might leave it as configured
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.4.1 Overview

functionality in an OPC UA FX Information Model . A FunctionalEntity can provide InputData , OutputData , ConfigurationData , diagnostic information and Methods for manipulating or sharing the data. It is expected that other
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.4.2 FunctionalEntityType definition

InputsFolderType O 0:HasComponent Object 3:OutputData 3:OutputsFolderType O 0:HasComponent Object 3:ConfigurationData 3:ConfigurationDataFolderType O 0:HasComponent Object 3:Capabilities 3:FunctionalEntityCapabilitiesType O 0:HasComponent Object ... Table 42 - FunctionalEntityType additional subcomponents BrowsePath References NodeClass BrowseName DataType TypeDefinition Others 3:ConfigurationData 0:Organizes Object 5:Configuration 5:FunctionalGroupType O 3:ConfigurationData 0:Organizes Object 5:Tuning
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.4.6.1 Overview

Overview The ConfigurationDataFolderType is used to organize ConfigurationData Variables and provides the Methods for supporting the storage of Variables (see 5.4 ). A ConfigurationDataFolder may contain sub- Folders derived from FunctionalGroupType
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.4.6.3 SetStoredVariables method

data variables. NodeId shall be the NodeId of a configuration data variable belonging to ConfigurationData of this FunctionalEntity or one of its SubFunctionalEntities. Results An array of StatusCode corresponding ... Table 52 - Results StatusCodes Result Code Description Bad_InvalidArgument The NodeId is not a ConfigurationData Variable or does not belong to this FunctionalEntity or one of its SubFunctionalEntities . Bad_NotSupported
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.4.6.4 ClearStoredVariables Method

Table 56 - Results StatusCodes Result Code Description Bad_InvalidArgument The NodeId is not a ConfigurationData Variable or does not belong to this FunctionalEntity or one of its SubFunctionalEntities . Bad_NotSupported
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.5.2 ControlGroupType definition

ControlGroups, see Annex D.3 . The FunctionalEntity may provide Variables in its InputData , OutputData and ConfigurationData Folders . A ControlGroup may include any combination of the input, output, and configuration Variables from ... FunctionalEntity . A FunctionalEntity may provide information in InputData , OutputData and ConfigurationData that are not part of any ControlGroup . ControlGroups are primarily used for locking, but they may also be used
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.7.3.2 Establishing Connections

ControlGroups Variable in Endpoint1 or Endpoint2 Object in the instances of ConnectionConfigurationType . SetConfigurationDataCmd Set ConfigurationData on the FunctionalEntity to adapt its behaviour as required (e.g., setting engineering units). The argument ... ConnectionEndpointConfigurations ConfigurationData that is passed for this command is constructed out of the ConfigurationData Variable in Endpoint1 or Endpoint2 Object in the instances of ConnectionConfigurationType . ReassignControlCmd Reassigns the ControlGroups
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.11.2 ConnectionEndpointConfigurationType definition

HasComponent Variable 4:ControlGroups 4:PortableNodeIdentifier[] 0:BaseDataVariableType O 0:HasComponent Variable 4:ConfigurationData 4:PortableNodeIdentifierValuePair[] 0:BaseDataVariableType O ConformanceUnits UAFX ConnectionManager Base FunctionalEntityNode specifies the identifier of the FunctionalEntity ... controlled. If a PortableRelativePath is specified, the path shall be relative to FunctionalEntityNode . ConfigurationData , if present, specifies the parameters to apply for the configuration of the FunctionalEntityNode . If a PortableRelativePath
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.14.2 AutomationComponentConfigurationType definition

Asset associated with this AutomationComponent . The AssetVerificationType is defined in 6.15.2 . CommunicationModelConfig provides the ConfigurationData specific to the communication model utilized by the Connections
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

10.14 ConnectionEndpointConfigurationDataType

parameter is to be omitted, it shall be set to null or empty. False ConfigurationData 2:NodeIdValuePair[] Specifies the ConfigurationData to be applied. If this parameter is to be omitted
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

10.15 ConnectionEndpointConfigurationResultDataType

shall be null or empty. ConfigurationDataResult 0:StatusCode[] StatusCodes related to applying ConfigurationData . If CommandMask SetConfigurationDataCmd is set, the length of this array shall match the length of ConfigurationData ... each element shall contain the result of the corresponding element in ConfigurationData . If CommandMask SetConfigurationDataCmd is not set, it shall be null or empty. ReassignControlResult 0:StatusCode[] StatusCodes related
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

B.2 Creating a new model based on OPC UA FX

might also define fixed Variable(s) that all instances would contain, such as the ConfigurationData in MyFunctionalEntityType. It could define fixed ControlGroups or a fixed group of SubFunctionalEntities . Then
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

B.3.2.1 Extending an existing type

FunctionalEntity , so the IFunctionalEntity Interface was added to the model. The InputData , OutputData and ConfigurationData folders provided by the Interface were updated to include references to the already defined (existing
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

D.3.6.1 Overview

related to this Asset will provide OutputData only. To keep the following examples simple, ConfigurationData (e.g., measurement range and unit) is not shown. The dashed lines in the figures
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

F.1.9 AutomationComponentConfigurationConfDataType

AssetVerification is not available, the field is null. False CommunicationModelConfig 4:CommunicationModelConfigurationDataType Provides the ConfigurationData specific to the communication model utilized by the Connections . If the optional CommunicationModelConfig
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles

5.2.5 UAFX FunctionalEntity

IFunctionalEntity Interface . This includes a Reference to at least one Variable . Server UAFX IFunctionalEntity ConfigurationData Supports ConfigurationData of the IFunctionalEntity Interface . This includes a Reference to at least one Variable ... ConfigurationDataFolderType . Server UAFX ConfigurationDataFolder Hierarchy Supports a hierarchy of ConfigurationDataFolders. Server UAFX IFunctionalEntity ConfigurationData Configuration Supports ConfigurationData of the IFunctionalEntity Interface, including the Configuration FunctionalGroup of the IFunctionalEntity Interface ConfigurationData