Re: ARENA Fault
 

That is a large amount of effort and an even longer awards ceremony just to compensate for issues that shouldn't exist in the first place while taking away from an alliance's repair time.

Re: ARENA Fault
 

The problem here is that there are potential issues that are difficult to detect, and if they're difficult to detect then it's hard to get the issues fixed. If the teams were to switch ends and teams consistently had fewer issues on one end than the other, then it would become more obvious that there is an issue to fix. If the team has issues on both ends of the field then it shows the issue is specific to that team. The problem may still be something in the robot-FMS interaction, but at least you know the driver station isn't cursed (cough*centerbluestation*cough).

Re: ARENA Fault
 

I have found an issue for us with the Classmate and Intel's CPU power saving scheme called SpeedStep. By going into the Classmate's BIOS and disabling the SpeedStep option I was able to eliminate periodic system watchdog errors that we had been getting (approx 4 per minute).

While several people have said that the FMS doesn't care about watchdogs, the system watchdog is an indicator that communications between the Classmate and the cRIO has been lost (at least temporarily). I'm hoping that this was the reason that our robot stopped running in multiple rounds at the Suffield, CT scrimmage - I guess we will find out later this week at Hartford.

You can view the thread I started on this issue here (please post to this thread if this solution improves your robot communication issues):
http://www.chiefdelphi.com/forums/sh...d.php?p=943661

Merle Yoder
The GRUNTS Team#3146

Re: ARENA Fault
 

GDC response to my recommendation for managing operation off tether at competition - they will be considering how to do this for next year

http://forums.usfirst.org/showthread.php?t=15210