View Single Post
  #13   Spotlight this post!  
Unread 23-03-2010, 20:50
FRC4ME FRC4ME is offline
Registered User
FRC #0339
 
Join Date: Feb 2008
Rookie Year: 2007
Location: Fredericksburg, VA
Posts: 324
FRC4ME has a brilliant futureFRC4ME has a brilliant futureFRC4ME has a brilliant futureFRC4ME has a brilliant futureFRC4ME has a brilliant futureFRC4ME has a brilliant futureFRC4ME has a brilliant futureFRC4ME has a brilliant futureFRC4ME has a brilliant futureFRC4ME has a brilliant futureFRC4ME has a brilliant future
Re: Take an exit with dignity

Quote:
Originally Posted by nukemknight View Post
We had very few teams have this happen at VCU, and it just so happened that 134 experienced this problem in back-to-back matches. 134 communicated with the FMS before beginning the match, but would not move in the tele-operated period, and seemed to still be stuck in their autonomous program although FMS had successfully placed 134 into tele-operated. As FRC4ME said, this could be a programming issue, although I can't say for sure. Can anyone on 134's programming team shed some light on how they got working again?
Wait...I have a question for 134: when you were unable to move, what did the driver station display read? "Autonomous enabled," or "teleop enabled?" (or something else?)

If it read autonomous enabled, I can't imagine how you could cause such a problem in programming.

If it read teleop enabled, but the robot seemed to still be running autonomous code, I can show you a million ways to cause such a problem in programming.

Quote:
Originally Posted by The Lucas View Post
Perchance do you have an old adaptor (WGA600N) and your alliance partners have the new adaptor (WET610N)? They are now making it a point to turn on all the new adaptors on first then the old ones.
This right here is an indication that FIRST does not fully understand the FMS they are dealing with. Correct me if I'm wrong, but the order in which you connect devices to a WiFi network should have no affect on how the system works. We have found a solution that seems to make things work, but I doubt anyone understands why it "works," and whether it leaves behind any residual problems. One of the first steps toward solving the FMS bugs, IMO, would be to determine why the boot order matters. This could possibly shed light into the root cause of other problems.

Quote:
Originally Posted by synth3tk View Post
Hard to do that when human nature tells us to only celebrate the "winning" teams.

In my honest opinion, it seems that there's very few people, at least from what I see at CD, that celebrate the non-competition merits of FRC teams. Again, that's only my opinion. Maybe I'm missing all the "good" threads.
Try this forum:

http://www.chiefdelphi.com/forums/forumdisplay.php?f=58

I don't think most of the teams in there won their regionals (yet, at least).
__________________
Go directly to queue. Do not pass pit.
Reply With Quote