User`s manual

MDL-DataManager™ Reference Guide Architectural Energy Corporation
Section 5.0 Trouble Shooting Page 29
5.0 Trouble Shooting
If you experience problems with your MicroDataLogger unit (MDL), MDL-
DataManager software, or MDL-DataRetriever software, there are several potential
sources of the problem.
The following is a table of potential MDL problems, and the appropriate action to take
to correct the problem.
Hardware
Problems
Symptoms Action to be taken
“Low Battery Stop” occurs
After retrieving any data taken, fully
charge MDL and perform a battery life
test as described in the Battery Life Test
help topic. If the run-time is less than 50
hrs, return to AEC for testing and/or
battery replacement. If run-time is
greater than 50 hrs, the “Low Battery
Stop” most likely occurred due to short
Sample Intervals and/or high-powered
sensors.
No readings on a channel
Check to be sure that none of the
channel’s pins have been bent.
Otherwise return to AEC for repair. Call
first to obtain an RMA number.
MicroDataLogger unit crashes
(Black Boxes Appear in LCD)
Use a small screwdriver or similar metal
rod and gently touch the two conductors
of the external power jack on the right
side of the logger. This “re-boots” the
logger.
Note: A logger crash can be identified
by many black boxes appearing in the
LCD of the unit.
**** Appears in LCD
The MicroDataLogger unit’s LCD will
display a maximum of 5 digits plus a
decimal point and the sign (-) of the
number. If asterisks (****) appear in the
display, reduce the number of decimal
places in the Configuration Parameters
window for the channel(s) showing the
asterisks.
Note: Logged data is always recorded at
full accuracy and is not affected by the
display’s decimal digits setting. Two
decimal digits are the recommended
number to have for any data collection
efforts. A selection of three or more