Time to build cRIO LabVIEW code

[Greg McKaskle]

What would be really nice is if deploying from the front panel would work as build/download at its current speed.

I agree. That is pretty much the way RT used to work. It is now more capable and strips files down a bit more, but the time is much longer than I expect.

Again, don't accept 15 or 20 minutes as typical. Change the checkbox for libraries.

Greg McKaskle

[Ken Patton]

Originally Posted by Greg McKaskle

I agree. That is pretty much the way RT used to work. It is now more capable and strips files down a bit more, but the time is much longer than I expect.

Again, don't accept 15 or 20 minutes as typical. Change the checkbox for libraries.

Greg McKaskle

For those of you using Labview, listen to Greg. His advice on this is solid. Without the checkbox checked, we have a 20 minute build time. With it checked, we have a 2-3 minute build time. Still pretty long, but much better.

The other thing to remember is that you can do the build without being connected to the robot. Only the final step - right-clicking on your build and selecting Run as Startup - needs to be done while connected to the robot. And that takes only ~1 minute.

Having said all that, it does need to be improved, there is no doubt. Like Dave said, it makes it difficult to help someone who is in a bind, and it makes you not want to help them because you are afraid that they will have no code when the match starts.

Ken