View Single Post
  #1   Spotlight this post!  
Unread 13-01-2013, 09:04
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: The various methods of deploying code from Labview

The first two have the same results.

The last item in the project is called the Build Specifications. Basically the Makefiles for constructing any applications or libraries from the VIs.
Here is my take at the terminology.

Build -- executes the script to build whatever you asked for, but it is stored locally on the host computer and isn't placed on the controller.
Deploy -- puts the latest version of the output of this script on the controller. If not built, it prompts you to build it first.
Set as Startup -- tells the controller to run this app, if present on power up.
Unset as Startup -- don't ...
Run as Startup -- The higher level command that builds, deploys, and sets as startup.

I confirmed the issue with the dashboard in your previous post. At this point in the season, you should typically be running from source and debugging, and I wouldn't recommend deploying and doing startup yet.

Greg McKaskle
Reply With Quote