Quote:
Originally Posted by jbbjjbt
Phil,
Does the nxt look like it's running?
Jon
|
In the example I just descibed, the NXT was clearly not running.
It's the old story though, the more debugging you put in, the harder it is to know whether you are effecting the operation of the program.
To make it obvious that the program was running, I added a light sensor, and turned on/off the "illumination" to make it act as a signal light. One flash per second for Auto, and two flashes flashes per second for Teleop.
It make it pretty clear when the program was running/stopping.
Just this morning I caught the program terminating when it wasn't meant to.
I thought I saw a message go by, so I hooked up a video cam to watch the sequence. After running perfectly for 10 times, I finally caught the glitch.
http://www.ourcoolhouse.com/images/NXT_FileError.wmv
If you play the linked video, you'll see the program shut down at T=14 seconds. If you freeze frame it, you'll notice an interesting error message just as it dies. See attached pic
- File Error - Wassup ????
OK, I guess I have some more googling to do.
Note: I have checked my NXT memory and I'm only about 1/2 full.
57K out of 115K bytes used???