Quote:
Originally Posted by Levansic
Now, our diagnostic log on the DS is completely empty, except for a new message at references the watchdog. Again, we are not in any way calling any watchdog functions in our team code.
The new solitary error code is as follows:
Watchdog Expiration: System 1, User 0
Because the robot is now working great, I'm of the opinion that this error doesn't matter. At the same time, I am a little concerned because we shouldn't have any error for a function we aren't calling.
|
The system watchdog is based on communications and can't be disabled. The user watchdog is what you can control programmatically. I believe it's normal (or at least not uncommon) to see a single System watchdog expiration when starting the program.
A year where the students learn a lot and win nothing is more rewarding than a year where the team does well and doesn't learn much. - Molten [more] 
14-09-2012, 13:41
Threaded Mode