skoehler wrote:So you run that program for 3 weeks - then what happens? The program crashes with an Exception on screen? What was the exception?
I don't know what happens exactly, all I know is that it seemingly is rebooting, then locks up on the splash screen where you have the leJOS logo and the firmware version - 0.9.1.
skoehler wrote:Did you save the verbose output of the linker or did you save a debug file when linking the application?
Yes, I have debug file. It's up here http://www.bangsholt.dk/WaveRobot.nxd
skoehler wrote:Then somehow you managed to reboot the brick (by pressing ENTER+ESCAPE?) and I guess you heard the ding-dong sound, but it didn't get past the boot-logo, right?
No, I tried to do ENTER+ESCAPE, no response, so instead I remove the battery pack and put it back in - then it worked.
skoehler wrote:Did you even try to reproduce this issue? I mean, it might not even happen every time. It might actually be a hardware error (bitflip in NXT's memory) or something weired that isn't reproducible.
Reproducing the issue is more crucial. Telling us what was on the screen would be worth something - unless you neither saved a debug file (*.nxd) when linking or the verbose linker output.
I don't know what steps to take to try and reproduce, as I don't know exactly what happened, I only saw the result of what happened, could you possibly provide some hints? I'll let the robots run another 3 weeks and see if it happens again. For what it's worth, I got two robots running at the exhibition and both had the exact same issue, which lead me to believe it's a bug in the programming somewhere and not a hardware issue.
I suspect that after 3 weeks we are getting very close to various internal timer values overflowing or going negative. leJOS wasn't really designed to run for so long.
Okay, that might also be a possibility. Good to know.