Thread: Labview can't connect to cRIO
View Single Post
  #10   Spotlight this post!  
Unread 24-01-2013, 07:45
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
  
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,752
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: Labview can't connect to cRIO
The bug is only in this year's version of SmartDashboard. I was mentioning it because the symptom fit.

The most common cause I saw last year for not being able to deploy was that the robot would be disabled and the disabled code was using lots of CPU because it was constantly throwing errors. We changed the framework slightly this year to help avoid that.

I'd encourage you to start from this year's template and merge in some of last year's code and see if the deploy issue goes away. Otherwise, let's debug it -- which isn't the same as guessing at the issue.

And it should not be necessary to reboot in order to be able to deploy.

Greg McKaskle
Last edited by Greg McKaskle : 24-01-2013 at 07:46. Reason: Another thought
Reply With Quote