The ControllerType describes the control unit of motion devices. One motion device system can have one or more instances of the ControllerType. The ControllerType is formally defined in Table 37.

image028.png

Figure 19 – Overview ControllerType

Table 37 – ControllerType Definition

Attribute

Value

BrowseName

ControllerType

IsAbstract

False

References

Node Class

BrowseName

DataType

TypeDefinition

Modelling Rule

Subtype of the ComponentType defined in OPC Unified Architecture for Devices (DI)

HasProperty

Variable

2:SerialNumber

String

PropertyType

Mandatory

HasProperty

Variable

2:Manufacturer

LocalizedText

PropertyType

Mandatory

HasProperty

Variable

2:Model

LocalizedText

PropertyType

Mandatory

HasProperty

Variable

2:ProductCode

String

PropertyType

Mandatory

HasComponent

Object

CurrentUser

 

UserType

Mandatory

HasComponent

Object

Components

 

FolderType

Optional

HasComponent

Object

Software

 

FolderType

Mandatory

HasComponent

Object

TaskControls

 

FolderType

Mandatory

HasComponent

Object

2:ParameterSet

 

BaseObjectType

Mandatory

HasSafetyStates

Object

<SafetyStatesIdentifier>

 

SafetyStateType

OptionalPlaceholder

Controls

Object

<MotionDeviceIdentifier>

 

MotionDeviceType

OptionalPlaceholder

The following instance declarations are not defined by this type, but by the supertype ComponentType

and repeated here for better readability

HasProperty

Variable

2:AssetId

String

PropertyType

Optional

HasProperty

Variable

2:DeviceManual

String

PropertyType

Optional

HasProperty

Variable

2:ComponentName

LocalizedText

PropertyType

Optional

The SerialNumber property is a unique production number assigned by the manufacturer of the device. This is often stamped on the outside of the device and may be used for traceability and warranty purposes. This property is derived from ComponentType defined in OPC UA DI.

The Manufacturer property provides the name of the company that manufactured the device. This property is derived from ComponentType defined in OPC UA DI.

The Model property provides the name of the product. This property is derived from ComponentType defined in OPC UA DI.

The ProductCode property provides a unique combination of numbers and letters used to identify the product. It may be the order information displayed on type shields or in ERP systems. This property is derived from ComponentType defined in OPC UA DI.

The AssetId property is a user writable alphanumeric character sequence uniquely identifying a component. The ID is provided by the vendor, integrator or user of the device. It contains typically an identifier in a branch, use case or user specific naming scheme.

This could be for example a reference to an electric scheme. For electric schemes typically EN 81346-2 is used.

An use case could be to build up a location oriented view in a spare part management client software. It enables to identify parts with the same article number which is not possible if this entry is not used.

This property is defined by ComponentType defined in OPC UA DI.

The DeviceManual property allows specifying an address of the user manual for the controller. It may be a pathname in the file system or a URL (Web address). This property is defined by ComponentType defined in OPC UA DI.

The ComponentName property provides a user writeable name provided by the vendor, integrator or user of the device. The ComponentName may be a default name given by the vendor. This property is defined by ComponentType defined in OPC UA DI.

The CurrentUser obje provides information about the active vendor specific user level of the controller.

Components is a container for one or more instances of subtypes of ComponentType defined in OPC UA DI. The listed components are installed in the motion device system, e.g. a processing-unit, a power-supply, an IO-board or a drive, and have an electrical interface to the controller.

Table 38 – TypeDefinition of Components of ControllerType

Attribute

Value

BrowseName

Components

References

Node Class

BrowseName

DataType

TypeDefinition

Modelling Rule

HasComponent

Object

<ComponentIdentifier>

2:ComponentType

MandatoryPlaceholder

The AuxiliaryComponentType and DriveType are the only subtypes of ComponentType for use in this container which are described in this specification. The intention is to integrate inside this container devices which are defined in other companion specifications using DI.

Software is a container for one or more instances of SoftwareType defined in OPC UA DI.

Each controller has at least one software installed.

Table 39 – TypeDefinition of Software of ControllerType

Attribute

Value

BrowseName

Software

References

Node Class

BrowseName

DataType

TypeDefinition

Modelling Rule

HasComponent

Object

<SoftwareIdentifier>

2:SoftwareType

MandatoryPlaceholder

TaskControls is a container for one or more instances of TaskControlType.

Table 40 – TypeDefinition of TaskControls of ControllerTyp

Attribute

Value

BrowseName

TaskControls

References

Node Class

BrowseName

DataType

TypeDefinition

Modelling Rule

HasComponent

Object

<TaskControlIdentifier>

TaskControlType

MandatoryPlaceholder

Table 41 – ParameterSet of ControllerType

Attribute

Value

BrowseName

ControllerType

References

Node Class

BrowseName

DataType

TypeDefinition

Modelling Rule

HasComponent

Variable

TotalPowerOnTime

DurationString

BaseDataVariableType

Optional

HasComponent

Variable

StartUpTime

DateTime

BaseDataVariableType

Optional

HasComponent

Variable

UpsState

String

BaseDataVariableType

Optional

HasComponent

Variable

TotalEnergyConsumption

Double

AnalogUnitType

Optional

HasComponent

Variable

CabinetFanSpeed

Double

AnalogUnitType

Optional

HasComponent

Variable

CPUFanSpeed

Double

AnalogUnitType

Optional

HasComponent

Variable

InputVoltage

Double

AnalogUnitType

Optional

HasComponent

Variable

Temperature

Double

AnalogUnitType

Optional

Description of ParameterSet of ControllerType:

  • Variable :The TotalPowerOnTime variable provides the total accumulated time the controller was powered on.
  • Variable StartUpTime: The StartUpTime variable provides the date and time of the last start-up of the controller.
  • Variable UpsState: The UpsState variable provides the vendor specific status of an integrated uninterruptible power supply or accumulator system.
  • Variable TotalEnergyConsumption: The TotalEnergyConsumption variable provides total accumulated energy consumed by the motion devices related with this controller instance.
  • Variable CabinetFanSpeed: The CabinetFanSpeed variable provides the speed of the cabinet fan.
  • Variable CPUFanSpeed: The CPUFanSpeed variable provides the speed of the CPU fan.
  • Variable InputVoltage: The InputVoltage variable provides the input voltage of the controller which can be a configured value. To distinguish between an AC or DC supply the optional property Definition of the base type DataItemType shall be used.
  • Variable Temperature: The Temperature variable provides the controller temperature given by a temperature sensor inside of the controller.

The HasSafetyStates reference provides the relationship of safety states to a controller. The InverseName is SafetyStatesOf.

The Controls reference provides the relationship of a motion device and controller. The InverseName is IsControlledBy.