View Single Post
  #6   Spotlight this post!  
Unread 04-03-2015, 12:01
Alan Anderson's Avatar
Alan Anderson Alan Anderson is offline
Software Architect
FRC #0045 (TechnoKats)
Team Role: Mentor
 
Join Date: Feb 2004
Rookie Year: 2004
Location: Kokomo, Indiana
Posts: 9,112
Alan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond repute
Re: Labview Programming Computer Features Recommendations

Quote:
Originally Posted by Qbot2640 View Post
My questions are all about quick program build speed and quick push to the RoboRIO. We're making multiple small tweaks to the program, and each one has a 5 to 10 minute build, then a long deploy as well. It makes dialing in an auto distance or other small movement really tedious.
I don't intend this to sound condescending, but you're doing it wrong.

If you are making lots of little changes in quick succession in order to test things, you shouldn't be building the code in between each change. You should be executing it "interactively" by runnin the Robot Main VI. The first time you do that it will take about the same amount of time as a Build/Run as Startup, but every subsequent time will be a matter of a few seconds while LabVIEW "deploys" only the changed part of the program and runs it.

Once you are satisfied with all your changes and want to deploy the code so that it persists through a power cycle, only then should you finally Build and Run as Startup.
Reply With Quote