
SapIP – IRT Instruction Manual 1/23/2017
Page 41
Dynamax, Inc.
Troubleshooting
-
Rather than encumber the normal behavioral descriptions with all this verbiage, the failure timeouts and
behaviors are separately described here:
1.
IRT Failures
-
The I2C serial data interface can tell if the IRT isn’t responding. After 10 seconds of continuous
attempts to communicate with the unit it will timeout and respond with a temperature of 1 degree
Kelvin or -272 degrees Celsius. This will be averaged as normal and you’ll see a reading of very
nearly absolute zero or -272 degrees C. This means the IRT temperature sensor isn’t
communicating. This behavior will effectively double the 10 second sample time and throw the
interval timer off accordingly. If the reading is 0 degrees K or -273.00 degrees C then the IRT is
communicating but the data is all zeros.
2.
Battery Failures
-
As discussed earlier, every time we send a radio sample packet the battery is checked. If the battery
voltage drops to its lower limits, the software will freeze in a loop waiting for the battery to heal.
The charger will then be set according to the last mode it was programmed to. This could be off,
fast mode, or trickle mode.
o
Note: If it’s off, the client will need to contact Dynamax.
-
Next, the LED will flash for 10 milliseconds after every 10 seconds. The purpose of this is to
conserve what remains of the battery’s voltage (in an extremely low battery drain state) until the
charger can bring the battery back.
-
Lastly, brown out failures will reset the CPU. These might occur under severe battery failures and
immediately after the charger begins to heal the battery. Brown-out resets could occur multiple
times but then after the last one the system voltages are stable enough for the CPU to run. Very
likely the unit will immediately drop into the battery voltage check discussed above and under
lowest possible drain conditions allow more time to heal the battery. The code has provision to
signal whether a brownout occurred but it’s commented out at this time.
3.
Radio Failures
-
Test Condition: with no coordinator active. Then resetting the unit.
-
The Radio LED will be off for several seconds then on for 6 seconds. Next, it will start the 9 blinks
separating each 1 second sleep resulting in a total of 10 seconds. This time, however, the LED will
stay on longer which indicates no association. During the data transmission time the LED stays on
solid indicating no association.
-
Test Condition: After a long time of no association, the radio will show an association failure
(blink code referenced in the Zigbee manual; section 6.4.2, pg. 80). That blink code is only
readable during transmission but not during the sleep/wakeup 10 second cycle because the sleep
pin turns it off before the blink code can be displayed.