Search

7 result(s) for Variables,

• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  4.4.3 Integrated object model
  representing Objects in the AddressSpace . This model represents Objects in terms of their Variables, Events and Methods , and their relationships with other Objects . OPC 10000-3 describes this model
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.4.2 Creating an Instance
  BrowseName and NodeClass shall match the InstanceDeclaration . In the case of Objects or Variables, also the TypeDefinitionNode shall either match or be a subtype of the original TypeDefinitionNode
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.3.3 VerifyAsset method
  Asset verification (see VerificationMode ). Each mode depends on a set of mandatory and optional Variables (see definition of AssetVerificationModeEnum in 10.4 ) to be present for verification. The VerifyAsset Method also ... accepts additional Variables for verification. An Asset implementing the VerifyAsset Method shall at least support the VerificationMode AssetCompatibility and expose the corresponding mandatory and implemented optional Variables in its Information
• 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
  define a fixed set of optional items, like in MyAssetType, which fixed optional IvendorNameplateType variables (i.e., making them mandatory). It could define a fixed structure of Connectors or a structure ... include the provided structures, extensions, or other functionality. These subtypes might also contain Objects, Variables, or Methods that have no bearing on the OPC UA FX model. When
• 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
  instance of FxAssetType . The FunctionalEntity organizes in its InputData , OutputData , and ConfigurationData Variables, which are components of the MyModelInstance (derived from the MyCompanionSpecType). Figure B.7 - Parallel ... existing UA models Another variance would be defining separate Variables in the FunctionalEntity , where the underlying device just references the same memory location for its value, as a Variable being
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  C.3 Usage of OPC UA safety Variables in Connections
  Usage of OPC UA safety Variables in Connections OPC UA Safety provides an application protocol using safety Variables , which is implemented by the SafetyProvider / SafetyConsumer . The communication layer is completely ... being transported. Any logical connection could reference any number of safety and non-safety Variables , even from different SafetyProviders or SafetyConsumers . There is nothing special in establishing a connection containing
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  E.6.6 Loading / Saving ConnectionConfigurationSets
  nodes on the Server . But in this case, the PublishedDataSet or SubscribedDataSet describes Variables that are on the Publisher or Subscriber Server , which is very likely to be a different ... PubSubConfiguration (i.e., not map). The engineering tool does not provide DataSets that include Variables, and the ConnectionManager generates the PubSubConfiguration. The actual manner in which this is handled is vendor