|
|
|
![]() |
|
|||||||
|
||||||||
|
|
Thread Tools |
Rating:
|
Display Modes |
|
#1
|
||||
|
||||
|
Time to build cRIO LabVIEW code
How long is it taking other teams to 'build' their code through LabVIEW? We are very concerned about the amount of time it takes. When we make a subtle change to the code (maybe change an offset or tweak a threshold, etc) and we need to rebuild the code and deploy it to the cRIO, it takes ~15 minutes to do. This seems intolerable at the competitions. Each time we do a 'build' it seems to recompile all code (instead of doing a make).
Are other teams experiencing this? How long is it? The problem is when we get to the competition and we want to make a small tweak between matches, instead of taking a minute to compile and download our code, it takes 15+. Thoughts on what we might be doing wrong? |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Cruch Time Help! 3 LabVIEW Tutorial Videos: State Machines; Faster Code; Simulation | LVMastery | NI LabVIEW | 11 | 09-02-2009 14:36 |
| "No code" each time cRIO is rebooted | Shinigami2057 | C/C++ | 9 | 01-02-2009 16:56 |
| LabVIEW Woes: Build/Deploy time too long?! | leftylink | NI LabVIEW | 7 | 27-01-2009 21:52 |
| cRIO: Traditional or LabVIEW? | Spartan151 | Programming | 6 | 23-10-2008 17:18 |
| Students build SEGWAY in 3 months using Labview and the cRIO | neutrino15 | Programming | 31 | 27-04-2008 22:08 |