View Single Post
  #9   Spotlight this post!  
Unread 10-02-2013, 11:07
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: building and deploying code

I don't completely follow what errors are occurring, but are you certain that you aren't suffering from the "Waiting for ..." issue that was documented in the known issues list? The symptom is that once you have deployed code to the cRIO and it is running as a startup application, it doesn't abort properly so that new code can begin running.

A LabVIEW update 5.1 was released primarily to fix this issue. The workaround documented on the known issues list involved aborting the dashboard before starting to download new code. This allowed for the deployed application to abort cleanly.

Greg McKaskle
Reply With Quote