View Single Post
  #1   Spotlight this post!  
Unread 05-03-2010, 21:13
sparrowkc sparrowkc is offline
Registered User
AKA: Mark
FRC #1986 (Team Titanium)
Team Role: Alumni
 
Join Date: Jan 2007
Rookie Year: 2007
Location: Lees Summit
Posts: 114
sparrowkc is a splendid one to beholdsparrowkc is a splendid one to beholdsparrowkc is a splendid one to beholdsparrowkc is a splendid one to beholdsparrowkc is a splendid one to beholdsparrowkc is a splendid one to beholdsparrowkc is a splendid one to beholdsparrowkc is a splendid one to behold
Exclamation Week one regional control system showstoppers

We just finished day two of the Kansas City regional. Although we had some bright spots today (We're currently tied for the highest match score of this season ), two problems continualy plagued our robot's performance and left us dead in the water during at least three matches. I'm hoping to hear from teams that have experienced the same problems and what they are doing to solve them.

First Problem
On several occasions, we experienced severe lag (~5 seconds) between the driver controls and the robot's motion. This problem only emerges when we're on the field with the FMS. Sometimes it persists after a match across multiple power cycles, and then fixes itself seemingly randomly. I'm fairly confident that this is nota code problem; We've never seen it before and is solved by multiple reboots, not code changes.

Second problem
During some matches, our joystick simply did not work. Inputs on the IO board did work, and the joystick was listed in the setup tab of the DS. I know of at least one other team that had this problem. I remember it happening on and off the field. It seemed to persist across power cycles and then fix itself. Ours was a logitech 3-axis joystick. It was going through the hub, and I couldn't reproduce it after I connected it straight to the classmate.

So... Ideas? Comments?