Thread: ANNOUNCING: navX MXP Robotics Navigation Sensor
View Single Post
  #13   Spotlight this post!  
Unread 04-03-2015, 15:31
Kevin Sevcik's Avatar
Kevin Sevcik Kevin Sevcik is offline
(Insert witty comment here)
FRC #0057 (The Leopards)
Team Role: Mentor
  
Join Date: Jun 2001
Rookie Year: 1998
Location: Houston, Texas
Posts: 3,685
Kevin Sevcik has a reputation beyond reputeKevin Sevcik has a reputation beyond reputeKevin Sevcik has a reputation beyond reputeKevin Sevcik has a reputation beyond reputeKevin Sevcik has a reputation beyond reputeKevin Sevcik has a reputation beyond reputeKevin Sevcik has a reputation beyond reputeKevin Sevcik has a reputation beyond reputeKevin Sevcik has a reputation beyond reputeKevin Sevcik has a reputation beyond reputeKevin Sevcik has a reputation beyond repute
Send a message via AIM to Kevin Sevcik Send a message via Yahoo to Kevin Sevcik
Re: ANNOUNCING: navX MXP Robotics Navigation Sensor
Quote:
Originally Posted by Alan Anderson View Post
The one obvious and mostly reliable difference is the robot being turned on and probably running user code for a while before the Driver Station is on the network. That's what brings out the timer bug, and the buffered data flood, and perhaps other things that are currently mysterious (e.g. Network Tables glitches). The workaround of restarting the robot program from the Driver Station seems to get past such problems.
Off topic at this point, but when's the generally accepted best time to hit that reboot robot button prior to a match?
__________________
The difficult we do today; the impossible we do tomorrow. Miracles by appointment only.

Lone Star Regional Troubleshooter
Reply With Quote