8.46.1 Overview

The ProcessControlLoopType is the general description of a control loop consisting of the desired value (SetPoint) for a measured value (ProcessValue) which is obtained by acting on an actuator (ControlValue).

The ProcessControlLoopType is formally defined in the following table.

Table 133 – ProcessControlLoopType Definition
Attribute Value
BrowseNameProcessControlLoopType
IsAbstractFalse
References Node Class BrowseName DataType TypeDefinition Other
Subtype of the TMCDeviceType, i.e. inheriting the Instance Declarations of that Node.
0:HasComponentObjectsControlValueProcessControlItemTypeM
0:HasComponentObjectsProcessValueProcessControlItemTypeM
0:HasComponentObjectsSetPointProcessControlItemTypeO
0:HasPropertyVariableWatchdogEnabled0:Boolean0:PropertyTypeM, RW
0:HasPropertyVariableWatchdogTimeout0:Duration0:PropertyTypeM, RW
0:HasComponentObjectExternalAlarms0:FolderTypeM
0:GeneratesEventObjectTypeExternalAlarmType
Conformance Units
TMC Process Variables Ingestion and Control
BrowseName Description
ControlValueThe ControlValue is the output of the control loop function. The control value directly drives the actuator.
ProcessValueThe value read by a sensor or other analog measurement of the physical quantity that is monitored.
SetPointThe value we aim to obtain from the ProcessValue by means of driving the control value.
WatchdogEnableWhen WatchdogEnable is True, if a ProcessControlLoop component’s RemoteControl is True and the time between two consecutive writes of the RemoteValue is longer than WatchdogTimeout, then the underlying system will generate an alarm, set RemoteControl to False and take control of the loop. When WatchdogEnable is False, no watchdog alarm is generated.
WatchdogTimeoutThe longest time between two write actions before a watchdog alarm is generated by the underlying system. The value is expressed in milliseconds. If the written value is below (above) the minimum (maximum) value that can be managed by the underlying system, the underlying system will overwrite it with the minimum (maximum).
ExternalAlarmsThe external alarms folder is used to organize external alarms.

The components of the ProcessControlLoopType have additional subcomponents which are defined in the following table.

Table 134 – ProcessControlLoopType Additional Subcomponents
BrowsePath References NodeClass BrowseName DataType TypeDefinition Others
ExternalAlarms0:HasComponentObject ExternalAlarm1ExternalAlarmTypeM
ExternalAlarms0:HasComponentObject ExternalAlarm2ExternalAlarmTypeM
ExternalAlarms0:HasComponentObject ExternalAlarm3ExternalAlarmTypeM
ExternalAlarms0:HasComponentObject ExternalAlarm4ExternalAlarmTypeM
ExternalAlarms0:HasComponentObject ExternalAlarm5ExternalAlarmTypeM
ExternalAlarms0:HasComponentObject ExternalAlarm6ExternalAlarmTypeM
ExternalAlarms0:HasComponentObject ExternalAlarm7ExternalAlarmTypeM
ExternalAlarms0:HasComponentObject ExternalAlarm8ExternalAlarmTypeM
ExternalAlarms0:HasComponentObject ExternalAlarm9ExternalAlarmTypeM
ExternalAlarms0:HasComponentObject ExternalAlarm10ExternalAlarmTypeM
ExternalAlarms0:HasComponentObject <ExternalAlarmN>ExternalAlarmTypeOP

The ExternalAlarms folder provides 10 spare external alarms that are mandatorily implemented by the underlying system. Additional ones can be added via the ExternalAlarmN optional placeholder.