ZoneType represents all functionalities of a heating zone, such as temperature monitoring, control, heatup and is formally defined in Table 14.
Table 14 – ZoneType Definition
|
Attribute |
Value |
||||
|
BrowseName |
ZoneType |
||||
|
IsAbstract |
False |
||||
|
References |
Node Class |
BrowseName |
DataType |
TypeDefinition |
Other |
|
Subtype of 0:BaseObjectType defined in OPC UA Part 5 |
|||||
|
0:HasProperty |
Variable |
Name |
0:String |
0:PropertyType |
O, RW |
|
0:HasProperty |
Variable |
HighestActiveAlarmSeverity |
0:UInt16 |
0:PropertyType |
M, RO |
|
0: HasComponent |
Variable |
ThermocoupleType |
0:UInt16 |
0:MultiStateValueDiscreteType |
O, RW |
|
0:HasComponent |
Variable |
CommunicationProtocolType |
0:UInt16 |
0:MultiStateValueDiscreteType |
O, RW |
|
0:HasComponent |
Object |
Temperature |
|
HRDTemperatureType |
M |
|
0:HasComponent |
Object |
Controller |
|
ControllerType |
M |
|
0:HasComponent |
Object |
HeatUp |
|
HeatUpType |
O |
|
0:HasComponent |
Object |
TemperatureRiseMonitoring |
|
TemperatureRiseMonitoringType |
O |
A user given name of the zone.
While the HighestActiveAlarmSeverity in the OperationType (see 9.3) indicates the severity of the highest active alarm of the complete HRD, here the Variable indicates the severity of the highest active alarm related to the current zone. Details of the error are listed in ActiveErrors (see 9.4) or via ZoneAlarmType (see 18.2).
This two Variables are used to specify the type of connected external temperature sensor and the used communication protocol between the sensor and the control system of the HRD.
The TypeDefinition for both Variables is MultiStateValueDiscreteType, so the Properties EnumValues and ValueAsText shall be filled with the supported values out of Table 15 and
Table 16.
Table 15 – Values for ThermocoupleType
|
EnumValue |
ValueAsText |
Description |
|
0 |
OTHER |
Other sensor type |
|
1 |
E |
Type E sensor: NiCr-CuNi |
|
2 |
J |
Type J sensor: Fe-CuNi |
|
3 |
K |
Type K sensor: NiCr-Ni |
|
4 |
N |
Type N sensor: NiCrSi-NiSi |
|
5 |
T |
Type T sensor: Cu-CuNi |
|
6 |
PT100 |
Pt 100-Sensor |
|
7 |
L |
Type L sensor: Fe-CuNi |
Table 16 – Values for CommunicationProtocolType
|
EnumValue |
ValueAsText |
Description |
|
0 |
OTHER |
Other connection type |
|
1 |
LOCAL |
Communication integrated in the local control system (local input) |
|
2 |
PROFIBUS |
Values via Profibus |
|
3 |
OPC_UA |
Values via OPC UA |
|
4 |
I2C |
Values via I2C |
|
5 |
CAN |
Values via CAN |
Which sensor types and protocols and combinations are supported is device dependent. Especially when the CommunicationProtocolType has the value 1 (LOCAL), the ThermocoupleType could be set to a fixed value by the HRD. A server can provide manufacturer specific values with EnumValues ≥ 100.
Setting and monitoring of the temperature. The HRDTemperatureType is defined in clause 14.
Unit: °C or F
Setting and monitoring of the controller (see 15 ControllerType).
Setting for heat up procedure. HeatUp is an alternative to the SetRamp functionality of MonitoredParameterType (see 16 HeatUpType).
TemperatureRiseMonitoring is an additional monitoring for the process temperature (see 17 TemperatureRiseMonitoringType).