8 OperationType
8.1 OperationType definition
The ObjectType of OperationType contains components which are necessary to operate the GDD. It is formally defined in Table 3.

| Attribute | Value | ||||
| BrowseName | OperationType | ||||
| IsAbstract | False | ||||
| References | Node Class | BrowseName | DataType | TypeDefinition | Other |
|---|---|---|---|---|---|
| Subtype of 0:BaseObjectType defined in OPC 10000-5 | |||||
| 0:HasComponent | Variable | DeviceMappingNumber | 0:UInt32 | 0:BaseDataVariableType | M,RW |
| 0:HasComponent | Method | IdentifyDevice | O | ||
| 0:HasComponent | Variable | HighestActiveAlarmSeverity | 0:UInt16 | 0:BaseDataVariableType | M,RO |
| 0:HasComponent | Variable | ActiveErrors | 4:ClassifiedActiveErrorDataType[] | 0:BaseDataVariableType | M,RO |
| 0:HasComponent | Method | ResetAllErrors | O | ||
| 0:HasComponent | Method | ResetErrorById | O | ||
| 0:HasComponent | Method | ResetEnergyMeasurement | O | ||
| 0:HasComponent | Variable | MainFailureBehaviour | MainFailureBehaviourEnumeration | 0:BaseDataVariableType | O |
| 0:HasComponent | Object | TotalEnergy | 4:EnergyType | O | |
| 0:HasComponent | Variable | EnergyConsumptionResettable | 0:Double | 0:AnalogUnitType | O, RO |
| 0:HasComponent | Object | MaintenanceInformation | MaintenanceInformationType | O | |
| 0:HasComponent | Variable | EnergyConsumptionLimit | 0:Double | 0:BaseDataVariableType | O |
| 0:HasComponent | Variable | RemoteControlOpcUa | 0:Boolean | 0:BaseDataVariableType | M,RO |
| Conformance Units | |||||
|---|---|---|---|---|---|
| OPC 40082-6 Basic | |||||
| OPC 40082-6 IdentifyDevice | |||||
| OPC 40082-6 ResetAllErrors | |||||
| OPC 40082-6 ResetErrorById | |||||
| OPC 40082-6 ResetEnergyMeasurement | |||||
| OPC 40082-6 MainFailureBehaviour | |||||
| OPC 40082-6 TotalEnergy | |||||
| OPC 40082-6 EnergyConsumptionResettable | |||||
| OPC 40082-6 MaintenanceInformation | |||||
| OPC 40082-6 EnergyConsumptionLimit |
8.2 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, the IMM must map the connected peripheral devices to internal logical devices and channels in a fixed configuration (e.g. dryer systems according to the injection unit). |
The mapping must be stable after reconnecting the devices and is therefore not possible via IP addresses, which can be assigned dynamically via DHCP. DeviceMappingNumber sets the mapping order of peripheral devices of the same type on the local network and is therefore of type UInt32.
| Example: | 1 |
8.3 IdentifyDevice
The peripheral device on which this method is called shows itself by e.g. activation of a LED or by Message on the UI of the device.
Signature
IdentifyDevice();| Attribute | Value | ||||
| BrowseName | IdentifyDevice | ||||
| References | Node Class | BrowseName | DataType | TypeDefinition | Modelling Rule |
|---|
NOTE: This Method is identical to the IdentifyDevice Method in other specifications of the OPC 40082 series.
8.4 HighestActiveAlarmSeverity
| Description: | Indication of the severity of the highest active alarm (0 = no active alarm - 1000 = possible error, severity classes defined in OPC 40083, clause 6.4). It provides a minimal error handling for devices without alarm support. However, the variable shall be filled even if alarms are supported. |
| Example: | 400 |
8.5 ActiveErrors
Description: List of the active errors of the device. It provides a minimal error handling for devices without alarm support. However, the variable shall be filled even if alarms are supported. The ClassifiedActiveErrorDataType is defined in OPC 40083. If there is no active error, the array is empty.
The node id is the source id of the drying bin.
8.6 ResetAllErrors
Method to reset all errors of the device.
Signature
ResetAllErrors();| Attribute | Value | ||||
| BrowseName | ResetAllErrors | ||||
| References | Node Class | BrowseName | DataType | TypeDefinition | Modelling Rule |
|---|
8.7 ResetErrorById
Method to reset one error of the device.
Signature
ResetErrorById (
[in] 0:String Id)| Argument | Description |
| Id | Id of the error, listed in ActiveErrors, that shall be reset. |
| Attribute | Value | ||||
| BrowseName | ResetErrorById | ||||
| References | Node Class | BrowseName | DataType | TypeDefinition | Modelling Rule |
|---|---|---|---|---|---|
| 0:HasProperty | Variable | 0:InputArguments | 0:Argument[] | 0:PropertyType | 0:Mandatory |
8.8 ResetEnergyMeasurement
Method to reset the EnergyConsumptionResettable Variable of the device and all components (e.g. bins, desiccant bed).
Signature
ResetEnergyMeasurement();| Attribute | Value | ||||
| BrowseName | ResetEnergyMeasurement | ||||
| References | Node Class | BrowseName | DataType | TypeDefinition | Modelling Rule |
|---|
8.9 MainFailureBehaviour
Determines how the dryer should react after a power failure, for example. The MainFailureBehaviourEnumeration is defined in Table 9.
| Name | Value | Description |
| STANDBY | 0 | The dryer starts in standby. |
| CONTINUE | 1 | The dryer starts in last position. |
8.10 TotalEnergy
This Object provides information about the actual power and the total lifetime energy consumption of the whole device. The EnergyType is defined in OPC 40083.
8.11 EnergyConsumptionResettable
Consumption of the granulate drying device in kWh since the last reset. For information about the reset method, see ResetEnergyMeasurement in 8.8.
8.12 MaintenanceInformation
This Object provides information about all maintenance activities related to the granulate dryer. The MaintenanceInformationType is defined in 13.49.
8.13 EnergyConsumptionLimit
This variable limits the energy consumed by the device relative to a user-defined default state (100%).
Example: Set to lower than 100 % when high drying levels are not required.
May also be used to enable more energy consumption.
Range: 0 % - 200 %
8.14 RemoteControlOpcUa
Variable to read the actual remote control state of the server instance.
If RemoteControlOpcUa is FALSE, the interface is read-only (Variables not writeable, methods not executable).
The value shall be stored persistently.