View Single Post
  #7   Spotlight this post!  
Unread 30-01-2009, 00:10
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: Proper procedure for deploying Labview code?

I'm also without cRIO nearby. Can someone else post the results of their deployment? That last part where it is deploying the file that defines the deployment doesn't sound necessary, and may be where things go wrong. Since it isn't a VI, the RAM debugging doesn't care about it, but the real build/deploy feels the need to take the XML file that describes the build.

If this is correct, open the deployment in the project and look to see if it references any files other than your top level VI. If need be, open and compare to the original deployment file in a new project. The project has this habit of making changes to the project and build scripts as you drag files to the project -- mostly nice, but sometimes surprising results.

Since you've been dragging files to the project You may also want to verify the files come from the disk files you think they do. This is where the second tab on the project is useful. That or the View or Tools menu item for showing the file path.

Greg McKaskle
Reply With Quote