View Single Post
  #6   Spotlight this post!  
Unread 27-01-2013, 11:39
Alan Anderson's Avatar
Alan Anderson Alan Anderson is offline
Software Architect
FRC #0045 (TechnoKats)
Team Role: Mentor
 
Join Date: Feb 2004
Rookie Year: 2004
Location: Kokomo, Indiana
Posts: 9,113
Alan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond repute
Re: Connecting to cRIO...

Quote:
Originally Posted by randalcr View Post
We managed to find a work-around by closing the driverstation and dashboard when making changes. it seems to work about 90% of the time.

someone correct me if i'm wrong but i think it's probably some issue in the way the driverstation and dashboard get data to and from the bot.
You're correct enough. It's only the Dashboard communication that's causing the trouble, and it'll be fixed with an update soon. For now, your workaround is the officially sanctioned way to deal with it. The Driver Station program doesn't need to be shut down; you only have to close the Dashboard (and any other programs using the SmartDashboard data). If you do that before you try to send code to the robot, it should work every time.