Search

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

24 result(s) for OutputData

OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>

3.2.1 Output Data

Output Data Data, which a device cyclically receives from the controller and which it outputs to the device application or the peripherals
OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model

3.2.3 Output Data

Output Data Data, which a Device cyclically receives from the Controller and which controls the Device application or the peripherals
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.7 PublisherCapabilitiesType

PublisherCapabilities is referenced from a FunctionalEntity (see 6.4.2 ) or OutputData (see 6.4.5 ), a preconfigured PublishedDataSet shall only reference OutputVariables of this FunctionalEntity and its sub- FunctionalEntities . If the PublisherCapabilities
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 Object 3:InputData 3: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 ... 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 instances
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.4.5 OutputsFolderType

OutputsFolder may be empty. The optional PublisherCapabilities shall only be present on OutputData of the FunctionalEntity . It provides the Publisher capabilities associated with the OutputData and describes additional restrictions ... PublisherCapabilities defined in the FunctionalEntity or AutomationComponent . The restrictions for OutputData only apply if the Connection is established with Variables referenced in OutputData 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 listed in the OutputData of the FunctionalEntity related to the ConnectionEndpoint or a SubFunctionalEntity of the FunctionalEntity. The referenced ... Variables may be a subset of the Variables referenced by OutputData . The communication represented by the ConnectionEndpoint shall include all referenced InputVariables and OutputVariables . A ConnectionEndpoint shall include at least
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

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

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 ... 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-15 ). Safety
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 ... 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 four channels plugged
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

D.3.6.2 Using preconfigured DataSets

four channels. In this case, a possible Information Model would organise the Variables in OutputData (the top-level folder). The preconfigured PublishedDataSet PDS_AI4 defines the fixed layout
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

D.3.6.5 Using groups

D.3.6.5 Using groups Subfolders within the OutputData can be used, for example, to group data. Suppose that our sample module is an 8-channel input where a channel
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

D.3.7.3 Example of a complex ControlGroup

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. The ListToBlock prevents
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

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, the exported Descriptor with
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

F.1.4 Creation of the FunctionalEntity 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 an application ... 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

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 a Reference ... least one Variable . Server UAFX IFunctionalEntity OutputData Supports OutputData of the IFunctionalEntity Interface . This includes a Reference to at least one Variable . Server UAFX IFunctionalEntity ConfigurationData Supports ConfigurationData
OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>

3.2.3 IO Data

Data For Devices, all Input and Output Data (cyclic transmission
OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>

3.2.4 DO IO Data

Data For a Drive Object (PROFIdrive), all Input and Output Data (cyclic transmission
OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>

3.2.5 EO IO Data

Data For an Encoder Object (encoder), all Input and Output Data (cyclic transmission
OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model

3.2.5 IO Data

Data For Devices , all Input and Output Data (cyclic transmission