Search

26 result(s) for DeviceType

• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  4.7 DeviceType
  DeviceType This ObjectType can be used to define the structure of a Device . Figure 10 shows the DeviceType . It is formally defined in Table 35 . Figure 10 - DeviceType Table ... DeviceType definition Attribute Value BrowseName 1:DeviceType IsAbstract True References NodeClass BrowseName DataType TypeDefinition Other Subtype of the ComponentType defined in 4.5.7 HasInterface ObjectType 1:ISupportInfoType Defined in 4.5.3 . HasInterface
• OPC-10000-19 – OPC Unified Architecture - Part 19: Dictionary Reference
  4.1 General
  semantic of an OPC UA Object. As an example, OPC 10000-100 defines the DeviceType ObjectType expressing that instances of this ObjectType represent devices. Subtypes of the DeviceType are used
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  B.3.2.1 Extending an existing type
  based on a type that might already include the required information (i.e., DeviceType from
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  4.1 General
  Device or parts of a Device where parts include mechanics and/or software. DeviceType is commonly used to represent field Devices . Modular Devices are introduced to support subdevices and Block Devices
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  4.6 ComponentType
  ComponentType Compared to DeviceType the ComponentType is more universal. It includes the same components but does not mandate any Properties . This makes it usable for representation of a Device ... BrowseName DataType TypeDefinition Other Subtype of the TopologyElementType defined in 4.3 . HasSubtype ObjectType 1:DeviceType Defined in 4.7 . HasSubtype ObjectType 1:SoftwareType Defined in 4.8 . HasInterface ObjectType 1:IVendorNameplateType Defined
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  7 Identification of Asset
  following options, as shown in Figure 1 : Usage of 2: ComponentType or 2: DeviceType . An Object representing an asset can have the TypeDefinition 2: ComponentType , 2: DeviceType , or a subtype ... well. OPC 10000-100 defines most of the Properties as mandatory on the 2: DeviceType , with default values when the value cannot be provided. The 2: ComponentType and the Interfaces
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  9.2 Overall health status of an asset
  older versions of OPC 10000-100 the Variable was only defined on the 2: DeviceType . In order to support older versions of OPC 10000-100 , Objects representing an asset ... provide the 2: DeviceHealth Variable as done by X:Asset3 by using the 2: DeviceType . Note that in the current version of OPC 10000-100 2: DeviceType does implement
• OPC-30000 – OPC UA for Programmable Logic Controllers based on IEC61131-3
  7.2.1 Overview
  Ctrl Programs executed under the control of Tasks . The CtrlResourceType is derived from the DeviceType defined in OPC 10000-100 . Figure 16 shows the CtrlResourceType . It is formally defined ... Value BrowseName CtrlResourceType IsAbstract False References NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype of the DeviceType defined in OPC 10000-100 , i.e. inheriting the InstanceDeclarations of that Node. HasComponent Object
• OPC-30010 – OPC UA for AutoId Devices - AutoID: OPC UA for AutoId Devices
  6.1.1 General
  shows an overview for the AutoIdDeviceType with its Properties and the base type DeviceType . It is formally defined in Table 7 . Figure 6 - AutoIdDeviceType overview There are several options
• OPC-30010 – OPC UA for AutoId Devices - AutoID: OPC UA for AutoId Devices
  6.1.2 ObjectType definition
  BrowseName AutoIdDeviceType IsAbstract True References Node Class BrowseName DataType TypeDefinition Modelling Rule Subtype of DeviceType defined in OPC 10000-100 . HasComponent Object RuntimeParameters FunctionalGroupType Optional HasComponent Object IOData FunctionalGroupType Optional
• OPC-30060 – OPC UA for Tobacco Machine Communication
  6 Tobacco Machine Communication Information Model overview
  main construct is the MachineModuleType ObjectType which is derived from an OPC 10000-100 DeviceType containing additional Information, including MachineModuleHistoricalRecord ( 8.2 ), MachineModuleConfiguration ( 8.3 ), MachineModuleLiveStatus ( 8.4 ), MachineModuleProduction ( 8.5 ), MachineModuleSpecification
• OPC-30060 – OPC UA for Tobacco Machine Communication
  8.49 TMCDeviceType ObjectType
  TMCDeviceType ObjectType The TMCDeviceType ObjectType is used to include UIInfo and specify which DeviceType components are mandatory when used in compliance with TMC. The TMCDeviceType is abstract, meaning there will ... Value BrowseName TMCDeviceType IsAbstract True References NodeClass BrowseName DataType TypeDefinition Other Subtype of the DeviceType defined in OPC 10000-100, i.e. inheriting the Instance Declarations of that Node. 0:HasComponent
• OPC-30090 – OPC UA for Field Device Tool (FDT) - Part <mm>: <Part Name>
  12.2.1.4 Mapping for Online Device ("Objects" standard Object online reference)
  from the device. This data may be different from the data provided in the DeviceType . Table 61 - Online device parameter mapping OPC FDT BrowseName Interface Method Data member Description ManufacturerId
• OPC-30100 – OPC UA for SERCOS Devices
  5.1 General
  grouping concept to provide alternative viewpoints. A class of devices is represented by the DeviceType ObjectType . This includes predefined elements to describe and identify a device. SercosDeviceType extends the DeviceType ... Therefore the elements are inherited from FunctionalGroupType, TopologyElementType and DeviceType . All OPC UA mandatory elements are implemented. SercosProtocolType represents the Sercos communication protocol implemented by the TopologyElement
• OPC-30100 – OPC UA for SERCOS Devices
  5.3 SercosDeviceType
  TopologyElementType defined in OPC UA for Devices companion specification. Inherit the Properties of the DeviceType defined in OPC UA for Devices companion specification. HasComponent Object ParameterSet FunctionalGroupType Mandatory HasComponent Object
• OPC-30110 – OPC UA for POWERLINK - POWERLINK: OPC Unified Architecture
  5.1 Overview
  POWERLINK Device and defines a standardised way to generate the mandatory Properties for a DeviceType (like SerialNumber, RevisionCounter, etc.) from values of certain POWERLINK Objects . In case a Device implements ... interface (by implementing multiple ConnectionPoints ), the selection of the ConnectionPoint as source for the DeviceType Properties is implementation specific. Figure 12 shows an example for a Device (DeviceExample1) that implements
• OPC-30110 – OPC UA for POWERLINK - POWERLINK: OPC Unified Architecture
  6.1.2 PowerlinkDeviceType Definition
  Attribute Value BrowseName PowerlinkDeviceType IsAbstract False NodeClass BrowseName DataType TypeDefinition Modelling Rule Subtype of DeviceType defined in OPC 10000-100 . Object <CNIdentifier> PowerlinkCnConnectionPointType OptionalPlaceholder Object <MNIdentifier ... PowerlinkMnConnectionPointType OptionalPlaceholder The PowerlinkDeviceType is an example for a DeviceType that only implements POWERLINK Managing Node (MN) and/or POWERLINK Controlled Node (CN) interfaces, for instance for the representation of POWERLINK
• OPC-30110 – OPC UA for POWERLINK - POWERLINK: OPC Unified Architecture
  6.1.5 Mapping for DeviceType (Types namespace)
  Mapping for DeviceType (Types namespace) The Type PowerlinkDeviceType is a subtype of DeviceType defined in OPC 10000-100, which mandates a list of Properties for the Device . Table 16 defines ... selection of the interface as source for these objects is device specific. Table 16 - DeviceType Mapping DeviceType / OPC 10000-100 POWERLINK BrowseName DataType Description 1:SerialNumber String Value
• OPC-30140 – OPC UA for PROFINET
  B.1.1 PnDIDeviceType
  BrowseName PnDIDeviceType IsAbstract False References Node Class BrowseName DataType TypeDefinition Modelling Rule Subtype of DeviceType defined in [OPC 10000-100] . HasInterface ObjectType IPnDeviceType Applied from IPnDeviceType HasComponent Object Interfaces PnInterfaceContainerType ... HasComponent Variable State PnDeviceStateEnumeration BaseDataVariableType Optional Although mandatory, some of the properties inherited from DeviceType may not be supported. In this case Vendors shall provide an empty string for properties
• OPC-30140 – OPC UA for PROFINET
  B.1.2 PnDIControllerType
  BrowseName PnDIControllerType IsAbstract False References Node Class BrowseName DataType TypeDefinition Modelling Rule Subtype of DeviceType defined in [OPC 10000-100] . HasInterface ObjectType IPnControllerType Applied from IPnControllerType HasComponent Object Interfaces PnInterfaceContainerType
• OPC-30200 – OPC UA for Commercial Kitchen Equipment
  5.1.1 General
  General The general DeviceType from the OPC UA information model for the device configuration is taken as the basis in this specification. This information model is defined in IEC62541
• OPC-40077 – OPC UA interfaces for plastics and rubber machinery - Data exchange between injection moulding machines and MES
  7 IMM_MES_InterfaceType
  Manufacturer http://opcfoundation.org/UA/DI/ server specific The variable Manufacturer is a child of the DeviceType (supertype of MachineInfomrationType ) which is defined in OPC UA DI. BrowseName Namespace Namespace index Remarks
• OPC-40082-1 – OPC UA interfaces for plastics and rubber machinery - Peripheral devices - Part 1: Temperature control devices
  9.1 DeviceMappingNumber
  DeviceMappingNumber Description: Unique identifier/address/number for devices of the same DeviceType within a local network. Several peripheral devices of the same DeviceType can be connected to a machine. In most applications
• OPC-40082-2 – OPC UA interfaces for plastics and rubber machinery - Peripheral devices - Part 2: Hot runner devices
  9.1 DeviceMappingNumber
  DeviceMappingNumber Description: Unique identifier/address/number for devices of the same DeviceType within a local network. Several peripheral devices of the same DeviceType can be connected to an client (e.g. injection moulding
• OPC-40082-3 – OPC UA interfaces for plastics and rubber machinery - Peripheral devices - Part 3: LSR Dosing Systems
  9.1 DeviceMappingNumber
  DeviceMappingNumber Description: Unique identifier/address/number for devices of the same DeviceType within a local network. Several peripheral devices of the same DeviceType can be connected to an IMM. In most applications
• OPC-40082-4 – OPC UA interfaces for plastics and rubber machinery - Peripheral devices - Part 4: Dosing Systems
  7.3 DeviceMappingNumber
  DeviceMappingNumber Description: Unique identifier/address/number for devices of the same DeviceType within a local network. Several peripheral devices of the same DeviceType can be connected to a production machine