Specifications

52
Two major problems arose during this phase. The first bug showed itself during the
first few days of testing. After operating for a full day or when an SD card was inserted
into the device, th e system would crash. An easy fix for this is to trip the b attery reset
and the s ystem would start up again. But the system would then become sluggish and
non-responsive at times. After many attempts, the PC software retrieved the log file and
configuration file from the device. The logs were replete with sensor measur ement errors.
The sensor causing the error was a previously un-configured digital port. However, looking
at the configuration file it became apparent that the last quarter of the file had become
corrupted. The culprit was some of the new code that was causing the stack to overflow
into the neighboring configuration file. This p roblem was fixed by optimizing the stack
usage and adjusting the global variables declared to reflect a more space-wise emph asis.
The allowed stack size grew from 376 bytes to 516 bytes. This is enough to guarantee no
further problems with the stack.
The second problem that surfaced during this phase was that the application reached
the code space limit of the MCU. The final code size came to 67K bytes with over 13,000
lines code. This means that the current platform has insufficient memory for all of the
desired functions this product. The radio fu nctions and operation require about 10K bytes
more. For a short term resolution, the Data Manager will come with two possible firmware
applications. One supports all LCD screens and the other will support the radio. For long
term, a new microcontroller will need to be selected and a new platform redesigned around
this IC.
5.2.3 Phase Three
The final stage of testing required the product to support all radio operations. This
included network personality changing, automatic mesh network creation and device s yn-
chronizations, computer-to-network pass through operations, and radio power management.
The novel ability to chan ge th e role of a particular network node is practically unattainable
for most ZigBee radio modu les. T his device contains images of the radio’s personalities
and re-flashes the radio as necessary. When a network starts up , the radios automatically