Search

5 result(s) for TypeDefinitions

• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  3.3 Conventions for Node descriptions
  level InstanceDeclarations , that are not directly visible in the table. The TypeDefinitions and DataTypes used in the InstanceDeclarations , and the ReferenceTypes are defined in their individual tables
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  4.7 Changes in AddressSpace over time
  possible and probable that the AddressSpace of a Server will change over time (i.e. TypeDefinitions can change; NodeIds can be modified, added or deleted). Server developers and administrators need
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  3.3.1.1 Node definitions
  level InstanceDeclarations , that are not directly visible in the table. The TypeDefinitions and DataTypes used in the InstanceDeclarations , and the ReferenceTypes are defined in their individual tables
• OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation
  7.3 Calibration Target Information Model overview
  which is provided by the calibration target category. The information model only provides the TypeDefinitions to manage calibration targets. It does not provide, how to organize several calibration targets
• OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning
  4.2.3.2 Namespaces
  these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They ... allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction