Search

6 result(s) for FunctionalEntity,

• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  4.7.2 Creating / Monitoring / Closing Connections
  included FunctionalEntities report the status of Connections that are part of the FunctionalEntity, and Clients can monitor this status. Some ConnectionManagers could provide the following: know when to create
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  5.5.6.2.5 DataSetMetaData
  Independent of the lifetime of a Connection, another engineering tool can update a FunctionalEntity, including its preconfigured DataSets . In addition, the Descriptor can describe a different version of the FunctionalEntity
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.2.2 AutomationComponentType definition
  Table 5 - AutomationComponentType additional References SourceBrowsePath Reference Type IsForward TargetBrowsePath 3:FunctionalEntities 3:<FunctionalEntity> 0:IsHostedBy True 3:Assets 3:<Asset> The components of the AutomationComponentType ... BrowsePath References NodeClass BrowseName DataType TypeDefinition Others 3:FunctionalEntities 0:Organizes Object 3:<FunctionalEntity> 3:FunctionalEntityType OP 3:Assets 0:Organizes Object 3:<Asset> 3:FxAssetType
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  C.2 Usage of OPC UA safety Variables in a FunctionalEntity
  Usage of OPC UA safety Variables in a FunctionalEntity Figure C.2 indicates a FunctionalEntity, which includes a SafetyProvider . The FunctionalEntity contains safety and non-safety Variables in its InputData ... OutputData . Figure C.2 - FunctionalEntity with safety data From a FunctionalEntity's perspective, the safety Variables CtrARequest and CtrAResponse are organised within the InputData and OutputData . In addition, these Variables
• OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering
  8.3.2 Descriptor Import
  Controller A to complete the Information Model for Controller B, e.g., defining the complementary FunctionalEntity, InputData and OutputData information for Controller B. The exchange of a Descriptor between Controls Engineers
• OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering
  F.1.4 Creation of the FunctionalEntity structure
  F.1.4 Creation of the FunctionalEntity structure In this step of the example, the FunctionalEntity sub-model is created. See Figure F.7 . Figure F.7 - FunctionalEntity sub-model of Filling Machine example ... Core Libraries provide the FunctionalEntityType SUC for defining a FunctionalEntity ). Within each FunctionalEntity , define variables for the input, output, and configuration variables, and link the variables to the FunctionalEntity using