Hello, My NXT has recently started to display some weird output when I terminate the program running on it. For example, it has just output 1R 368 369 370 3W 410 411 52 4W 410 65 5S 398 69 2W 410 411 144
I am using RConsole on Scientific Linux to catch output whilst the program is running. The only thing that has changed is I have started to use a ColorSensorHT on the robot to detect lines on a grid. I have already reflashed the NXT twice to 0.9.0-Beta, as some of my programs don't work nicely with 0.9.1.
Has anyone had this issue before/know of any solutions???
Wait for Andy to confirm, but it kind of looks like a data abort - you might have hit a firmware bug in 0.9.0.
What problems did you have with 0.9.1 - there might be a chance that the issue is already fixed in 0.9.1. Also, if there were serious problem with 0.9.1, you should report them so that we can fix them.
Also, old versions (like 0.9.0) are kind of unsupported. We won't supply you with a patched 0.9.0.
Thanks for the quick reply. The reason I haven't yet upgraded to 0.9.1 was because of deprecated and methods I used which were no longer used in 0.9.1, and with the level of code involved for my Undergraduate work, I didn't have the time to update all my code to utilise the new methods. Another reason was due to the number of failed flashes a few of my friends had, which bricked their units.
The original output you quoted is from the debugmonitor. It is not a data abort. Looks like you linked your program in debug mode. What is being shown is the state of the various threads and a short stack trace for each. Pressing enter+escape again should reboot the NXT back to the normal menu. See the tutorials for details of the debugmonitor...
No idea what is going on with your NXT after you flashed it sorry...
The debugmonitor is enabled via a linker option -g or --debug, it may also get activated in a subset form via -gr or --remotedebug but I'm not 100% sure. Sorry I'm away working at the moment so can't check this stuff any further...