MT-700 series installer guide
Page 9
2)
The Subsystem cannot be changed on a Node after it has been dropped in Alliance. To change
subsystems, the node must be deleted and a new node dropped.
3)
The sensor type cannot be changed on a Sensor after it has been dropped in Alliance. To change
sensors, the sensor must be deleted and a new sensor dropped.
NOTE:
If a Node or Sensor is deleted in Alliance, its history and logs will also be removed.
Additional Features
Alarms
Alarm Set 2
In addition to the standard alarm threshold, the controller provides a second set of alarm parameters
that can be used to complement the primary alarm. The second set is usually configured with narrower
alarm limits, but a longer set time. This can be used to identify poorly performing equipment and warn
when product shelf life may be reduced. For example, the primary alarm can be set to activate if the
measured temperature is 15°F above optimal for one hour; but the second alarm can be set to activate
if the measured temperature is 8°F above optimal for four hours. This second condition may not
warrant a high priority alarm; but it can be a good indicator that the system needs attention.
By default, Alarm Set 2 is inactive and must be enabled on each sensor.
To configure
Set 2, open the ‘Alarm Settings’ tab in the sensor configuration win
dow. In the lower right
portion, click
‘Set 2 Active’ and modify the alarm settings as desired.
Click the ‘OK’ button to save
changes.
NOTE
: When a sensor is configured for Dual Use, Set 2 is used as the primary alarm for the second
temperature setting. For details, see the Dual Use Sensors section.
Cumulative Alarms
One advanced feature built into Micro Thermo monitoring is Cumulative Alarming. The Cumulative
Alarm monitors an input over an extended period of time (usually 24 or 48 hours), and calculates the
total time that the input exceeds the high/low limits. This differs from the standard alarm sets, which
require a continuous high/low measurement to activate. Instead of resetting every time the
measurement returns within limits, the Cumulative Alarm counts all current and previous exceptions
that occur within the Cumulative Period.
The Cumulative Alarm is an integral part of temperature monitoring, for maintaining food quality and
shelf life. The cumulative effect of temperature variations has a significant impact on refrigerated food.
The variations can also be an indicator of current or developing issues in the system
–
the instability
being caused either adjacent to the sensor or propagating from elsewhere in the system. In either case,
a Cumulative Alarm should be investigated to determine the cause.
To configure the
Cumulative Alarm, open the ‘Alarm Settings’ tab in the sensor configuration window.
In the upper right section, select the alarm set to use for high/low limits and then specify the Set Time
and Cumulative Period parameters.
Disabling Alarms
The U700 Monitoring Node allows alarms to be disabled for individual sensors. Permanently disabling
an alarm inhibits all alarms for that specific sensor. This remains in effect until a technician manually re-
enables the alarm through Alliance. While an alarm is disabled, the icon in Alliance will appear light blue
for easy identification. However, if a sensor never requires an alarm (e.g., an auxiliary input), it may be
preferable to leave the alarm enabled with the alarm limits set to the
sensor’s min/max range. T
his will
effectively disable the alarm, but will not affect the Alliance display.
