HOBO MX Temp/RH Data Logger (MX1101) Manual
1-508-759-9500 (U.S. and International) 6
www.onsetcomp.com
1-800-LOGGERS (U.S. only)
when the logger’s LCD screen refreshes every 15
seconds.
•
The actual values for the high and low alarm limits are set
to the closest value supported by the logger. In addition,
alarms can trip or clear when the sensor reading is within
the resolution specifications. This means the value that
triggers the alarm may differ slightly from the value
entered.
•
When you download data from the logger, alarm events
can be displayed on the plot or in the data file. See
Logger Events
.
•
Once cleared, an audible alarm starts beeping again if the
sensor values go out of the normal range. Even if an
audible alarm is cleared, a visual alarm may remain on
the logger LCD and in the app depending on the settings
selected for maintaining visual alarms or because the
alarm condition may still be in effect. In addition, an
audible alarm continues beeping when the sensor values
have returned to the normal range until it is cleared as
described in step 10.
•
Although an audible alarm and a visual alarm can occur
at the same time when a sensor alarm is tripped, they are
cleared in different ways. The audible alarm can be
cleared as described in step 10. Meanwhile, a visual
alarm is cleared as determined by the setting selected for
Maintain Visual Alarm Until configuration setting. This
means you could clear a beeping audible alarm and the
visual alarm remains on the LCD and in the app until the
logger is reconfigured, the sensor is in limits, or the alarm
button is pressed—depending on the setting you
selected.
•
If the logger is configured to stop logging with a button
push, any tripped alarms are cleared automatically when
logging is stopped and no Alarm Cleared event is logged.
This ensures that the logger starts checking for alarm
conditions when logging resumes (if the logger was
configured with Allow Button Resume selected).
Burst Logging
Burst logging is a logging mode that allows you to set up more
frequent logging when a specified condition is met. For
example, a logger is recording data at a 5-minute logging
interval and burst logging is configured to log every 30 seconds
when the temperature rises above 85°F (the high limit) or falls
below 32°F (the low limit). This means the logger records data
every 5 minutes as long as the temperature remains between
85°F and 32°F. Once the temperature rises above 85°F, the
logger switches to the faster logging rate and records data
every 30 seconds until the temperature falls back to 85°F. At
that time, logging then resumes every 5 minutes at the fixed
logging interval. Similarly, if the temperature falls below 32°F,
then the logger switches to burst logging mode again and
record data every 30 seconds. Once the temperature rises back
to 32°F, the logger then returns to fixed mode, logging every 5
minutes.
Note:
Sensor alarms, statistics, and the Stop Logging
option Never Stop (Overwrites Old Data) are not available in
burst logging mode.
To set up burst logging:
1.
Tap Devices. Press the Start/Stop button on the logger to
wake it up, if necessary.
2.
Tap the logger tile in the app to connect to the logger and
tap Configure & Start.
3.
Tap Logging Mode and then tap Burst Logging.
4.
Set the burst logging interval, which must be faster than the
logging interval. Keep in mind that the faster the burst
logging rate, the greater the impact on battery life and the
shorter the logging duration. Because measurements are
being taken at the burst logging interval throughout the
deployment, the battery usage is similar to what it would be
if you had selected this rate for the normal logging interval.
5.
Select Low and/or High and type a value to set the low
and/or high values.
6.
Repeat step 5 for the other sensor if desired.
Notes:
•
The high and low burst limits are checked only when the
logger's LCD screen refreshes once every 15 seconds. If
you set the logging interval to less than 15 seconds and
the sensor reading falls outside the levels, burst logging
does not begin until the next 15-second refresh cycle.
•
If high and/or low limits are configured for more than
one sensor, burst logging begins when any high or low
condition goes out of range. Burst logging does not end
until all conditions on all sensors are back within normal
ranges.
•
The actual values for the burst logging limits are set to
the closest value supported by the logger.
•
Burst logging mode can begin or end when the sensor
reading is within the resolution specifications. This means
the value that triggers burst logging may differ slightly
from the value entered.
•
Once the high or low condition clears, the logging
interval time is calculated using the last recorded data
point in burst logging mode, not the last data point
recorded in fixed mode. For example, a logger has a 10-
minute logging interval and logs a data point at 9:05.
Then, the high limit is surpassed and burst logging begins
at 9:06. Burst logging then continues until 9:12 when the
sensor reading falls back below the high limit. Now back
in fixed mode, the next logging interval is 10 minutes
from the last burst logging point, or 9:22 in this case. If
burst logging had not occurred, the next data point
would have been at 9:15.
•
A New Interval event is created each time the logger
enters or exits burst logging mode. See
Logger Events
for
details on plotting and viewing the event. In addition, if
the logger is stopped with a button push while in burst
logging mode, a New Interval event is automatically
logged and the burst condition is cleared, even if the
actual high or low condition has not cleared. The logger
checks the high and low conditions when logging
resumes (if the logger is configured with Allow Button
Resume selected).
Statistics Logging
During fixed logging, the logger records data for enabled
sensors and/or selected statistics at the logging interval
