|
|
|
 I personally think any student should be allowed to participate, as long as he/she is helpful and active. FIRST, to me, is about inspiration, not elitism. - Aignam [more] |
 |
|
|||||||
|
||||||||
|
|
Thread Tools |
Rating: 
|
Display Modes |
|
#2
04-03-2009, 18:45
|
||||
|
||||
|
Re: Time to build cRIO LabVIEW code
In Windriver it takes < 5 seconds to do a full rebuild, and 5 to 45 seconds to deploy.
I wouldn't expect more than a 50% difference between Labview and Windriver. In any case that is way out of line. I suggest contacting NI if you can't solve this issue. 
|
| 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 |
Threaded Mode