|
|
|
![]() |
|
|||||||
|
||||||||
|
|
Thread Tools |
Rating:
|
Display Modes |
|
#7
|
|||
|
|||
|
Re: Time to build cRIO LabVIEW code
Your complaints about the build time are completely valid. As I mentioned, it shouldn't be 20 minutes. If you find a team with that problem, the checkbox will fix it. It will still be longer than I'd like, but until I can rub someone's nose in it, it will take a few minutes.
As for the FPGA comment ... not so valid. The LV compilation portion of that is small. The vast majority is spent with the Xilinx compiler doing its thing. The diagram gets compiled directly to VHDL and the Xilinx compiler does the heavy lifting. I'm pretty sure that the compile time will shrink shortly after they can prove P=NP -- wiki it if that doesn't make sense. Basically it means that the layout problems are some of the most difficult and expensive problems around. Greg McKaskle |
| 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 |