Search

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

16 result(s) for InputData

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

6.2.4.3.9.2 PubSub

communication configuration exceeds capabilities ( PublisherCapabilities , SubscriberCapabilities or ComponentCapabilities ) of the AutomationComponent , FunctionalEntities , InputData or OutputData , or if communication configuration cannot be applied, Bad_ConfigurationError shall be set in the Result
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.2.8 SubscriberCapabilitiesType

SubscriberCapabilities is referenced from a FunctionalEntity (see 6.4.2 ) or InputData (see 6.4.4 ), a preconfigured StandaloneSubscribedDataSet shall only reference InputVariables from the FunctionalEntity and its sub- FunctionalEntities . If the SubscriberCapabilities
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

HasComponent Method 3:Verify Defined in 6.4.3 O 0:HasComponent Object 3:InputData 3:InputsFolderType O 0:HasComponent Object 3:OutputData 3:OutputsFolderType O 0:HasComponent Object 3:ConfigurationData ... will define subtypes of FunctionalEntityType . Subtypes will define additional Variables that would exist in InputData , OutputData and ConfigurationData . The subtypes might also add Objects and Methods or define nested FunctionalEntityType
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.4.4 InputsFolderType

InputsFolder may be empty. The optional SubscriberCapabilities shall only be present on InputData of the FunctionalEntity . It provides the Subscriber capabilities associated with the InputData and describes additional restrictions ... SubscriberCapabilities 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
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.5.2 ControlGroupType definition

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

6.6.2 ConnectionEndpointType definition

communication model connected to the ConnectionEndpoint . All referenced Variables shall be in the InputData of the FunctionalEntity related to the ConnectionEndpoint or a SubFunctionalEntity of the FunctionalEntity. The referenced Variables ... subset of the Variables referenced by InputData . The optional OutputVariables reference Variables that are to be reported by the communication model connected to the ConnectionEndpoint . All referenced Variables shall
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

B.3.2.1 Extending an existing type

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

B.3.4 Parallel use of OPC UA FX and existing UA models

FunctionalEntity as well as an instance of FxAssetType . The FunctionalEntity organizes in its InputData , OutputData , and ConfigurationData Variables, which are components of the MyModelInstance (derived from the MyCompanionSpecType). Figure
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

which includes a SafetyProvider . The FunctionalEntity contains safety and non-safety Variables in its InputData and 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 are referenced by HasComponent References from the SafetyPDUs Object of the SafetyProvider (see also
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

D.3.6.1 Overview

D.3.6.1 Overview InputData and OutputData can be modelled in various ways. The following clauses show examples of their usage. Figure D.20 illustrates the subtype of FunctionalEntityType that is used ... other devices as needed. Figure D.20 - Example FunctionalEntity Type The following examples illustrate how InputData and OutputData can be joined with DataSets . Consider, for example, an analogue input module with
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

D.3.7.3 Example of a complex ControlGroup

data. The interface is represented by the ListToRestrict and ListOfRelated References . By this, the InputData , OutputData , ConfigurationData, and all provided Methods belonging to the interface can be easily determined
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

8.3.2 Descriptor Import

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 is further described
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

8.4 Example workflow for sharing a Descriptor in OfflineEngineering

information of the exported Descriptor for the configuration of another AutomationComponent , e.g., for configuring InputData from the OutputData information in a Controller-to-Controller communication scenario. In both cases
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

F.1.4 Creation of the FunctionalEntity structure

SubscriberCapabilities structure exists in the FunctionalEntity sub-model at three levels: AutomationComponent , FunctionalEntity and InputData and OutputData levels. In Figure F.8 , a FunctionalEntity "FillControl" is created that represents ... digital output variable, "ValveOpenClose". Both Variables are organized as InputData and OutputData of the FunctionalEntity, "FillControl".The "FillLevel" signal is coming from a FunctionalEntity
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles

5.2.5 UAFX FunctionalEntity

that is referenced from this FunctionalEntity ), supports at least one of the UAFX IFunctionalEntity InputData or UAFX IFunctionalEntity OutputData ConformanceUnits . Server UAFX IFunctionalEntity InputData Supports InputData of the IFunctionalEntity Interface ... This includes supporting all required types Server UAFX FunctionalEntity SubFunctionalEntity Supports the HasSubFunctionalEntity Reference . InputData Server UAFX InputsFolder SubscriberCapabilities Base Supports SubscriberCapabilities of the InputsFolderType . Server UAFX InputsFolder Hierarchy Supports