Thread: Issue deploying robot code to cRIO
View Single Post
  #2   Spotlight this post!  
Unread 13-01-2013, 08:48
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,751
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: Issue deploying robot code to cRIO
I verified that there is an issue with RT connection.

If the cRIO has a deployed app and SmardDashboard communications are under way, an attempt to connect a LV project to the cRIO will hang "Waiting for ...".

This doesn't occur if SmartDashboard isn't in in use, and doesn't occur if the Dashboard isn't open.

Back to your post, Running a VI via the right-click you are using, or opening the panel and clicking the run button and running the VI in the debugger should never prompt for a restart. A restart is needed only when you Deploy or Run As Startup.

So, I have enough information to report and debug the RT issue. You shouldn't be bothered by this provided you run in the debugger. I'd like to understand what step is causing the prompt for reboot.

Greg McKaskle
Reply With Quote