LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Mass Compile compactRIO RT project

I am trying to mass-compile a project in Labview 2011 for a compactRIO target. During the compilation, I get a series of badVI messages for all VIs which include the FPGA reference.

 

In my code, I open the FPGA-VI reference in the realtime top-level-VI and pass it to several subVIs via bound typedefs as explained here:

Why Do I Have a Broken Wire When Passing My FPGA VI Reference Into a SubVI?

This works great in the project, none of the subVIs have broken run buttons when opened there. Just the mass compile does not work.

 

My question:

Is it normal that mass compilation doesn't recognize the FPGA reference type-def or is this an indicator for a problem like corrupted VIs?

 

Why I am doing this: We are migrating the project from LV2010 to LV2011 and are experiencing crashes of the IDE in the new version. A mass-compile seems like the most straightforward way to make sure that our code is healthy.

 

Labview 2011(32bit) on Win7(64bit)

cRIO 9012 + cRIO9111 backplane and some c-Series cards

 

Thanks in advance, any help would be greatly appreciated.

0 Kudos
Message 1 of 4
(2,593 Views)

bump....

0 Kudos
Message 2 of 4
(2,564 Views)

Hi cermf,

 

sorry for the delay. In my opinion, the easiest way would be to delete all the FPGA-reference ins and outs of the subvis, masscompile, and replace them 

with the input control and output indicator you create once in a LV 2011 Project from a LV FPGA Reference VI which is set to "dynamic".

It is a bit of work (depending on the project size), but it will prevent you from trouble in future versions from this point on.

 

kind regards

 

Marco Brauner NIG

0 Kudos
Message 3 of 4
(2,556 Views)

Hi Hans Aplast,

thank you very much, I did what you said and it removes the BadVI messages, for all real-time VIs except the toplevel one where the FPGA-ref is created.

After that I tried a few other things like making the FPGA-reference non-dynamic or trying a different FPGA-VI, but the only way to remove this last BadVI was to remove the FPGA-reference altogether from the toplevel VI. Which is pointless since I need the FPGA.

 

Even substituting the real-time toplevel VI with this dummy and the FPGA-VI with a similar dummy doesn't remove the BadVI-message.

real-time toplevel Dummy

 

Anything else I could try to resolve this?

 

kind regards

Christian Freier

0 Kudos
Message 4 of 4
(2,546 Views)