View Single Post
  #1   Spotlight this post!  
Unread 08-03-2009, 12:23
ptan ptan is offline
Paul C. Tan., P.Eng.
AKA: Paul Tan
no team (Bolt Action)
Team Role: Mentor
 
Join Date: Dec 2005
Rookie Year: 2000
Location: Toronto
Posts: 61
ptan is a splendid one to beholdptan is a splendid one to beholdptan is a splendid one to beholdptan is a splendid one to beholdptan is a splendid one to beholdptan is a splendid one to behold
Re: [FTC]: Playing Forensic Roboticist.

Quote:
Originally Posted by PhilBot View Post
At least 3 times in a sequence of 10 runs, the program ran Autonomous, and then when when it was meant to transition to Teleop, it stopped the Auto program and then failed to restart the NXT in Teleop. It just sat there with the "ready to run" screen up.

What was more disturbing was that the FMS system indicated that the NXT was "running", whatever that means.
Interesting... Were you running a full field (i.e. 4 robots?). I have not yet seen this problem in our team's test field, but we have been only running our single robot with the FMS. We did experience this at the Ontario tournament along with several bluetooth issues.

I'm going to try to set up a similar test bed as yours, but with just 4 NXT controllers and the FMS to see if I can recreate the failure rate (3 out of 10) that you reported. Can you tell me if you are using Windows XP or Vista? And what service pack level are you using?

Like yourself, I'm also interested in getting down to the bottom of these mysteries.
__________________
Paul C. Tan., P.Eng.
Coach - FTC Team 27 (now retired)
Coach - VRC Team 2027 (now retired)
Past Mentor - FRC Teams 188, 610, 1009, 2634

Last edited by ptan : 08-03-2009 at 12:42.
Reply With Quote