LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Open FPGA VI Reference error and can't compile FPGA

I have a CompactRIO controller project and I'm getting an error "Open FPGA VI Reference: FPGA VI not compiled". The Open FPGA VI Reference is currently configured to open the VI (rather than build specification or bitfile). I have tried all the steps in this article to try to compile the VI. I tried clicking the Run button in the VI does nothing. I tried creating a new build specification, right-clicking it and selecting Rebuild, and the error is still there, even when I try reconfiguring it to open the new build specification. I can't even try configuring it to open the bitfile, because I need the file path, but to to view the file path, I have to right-click the build specification and then click Properties, but doing that, the properties dialog box does not open up. This confuses me the most. I would appreciate any help on this.

0 Kudos
Message 1 of 11
(3,931 Views)

Hi dbrother,

 

do you have LabVIEW-FPGA module installed and activated?

Can you show (aka attach) your whole project, including the lvproj file and all VIs/etc as ZIP?

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 2 of 11
(3,916 Views)

Hi GerdW,

 

Thanks for your reply. I do have the LabVIEW FPGA module installed and activated. I've attached my project as a zip. Sorry I forgot to attach on my first post.

0 Kudos
Message 3 of 11
(3,911 Views)

Hi dbrother,

 


@dbrother wrote:

I tried creating a new build specification, right-clicking it and selecting Rebuild, and the error is still there, even when I try reconfiguring it to open the new build specification. I can't even try configuring it to open the bitfile, because I need the file path, but to to view the file path, I have to right-click the build specification and then click Properties, but doing that, the properties dialog box does not open up. This confuses me the most. I would appreciate any help on this.


There is a BuildSpec in the FPGA target tree: have you tried to "Build" the bitfile using the existing BuildSpec?

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 4 of 11
(3,897 Views)

Hi GerdW,

 

If you're talking about the one under RT CompactRIO Target > Chassis > FPGA Target, then yes, I believe that is the BuildSpec that I have been trying to build.

 

I noticed 2 other buildspecs, one under the My Computer tree and another under RT CompactRIO Target tree directly. These have a caution symbol. Right clicking lets me click Explain Warning, and it says "LabVIEW currently cannot load the selected item. The required module, driver, or plug-in either is not installed or has an expired license..." I thought I had everything installed, but perhaps I am missing something.

0 Kudos
Message 5 of 11
(3,887 Views)

Do you have 32-bit or 64-bit LabVIEW installed? At this time, LabVIEW RT only has a 32-bit version of the module, and so it requires the 32-bit versions of LabVIEW and LabVIEW FPGA.

Cheers!

TJ G
0 Kudos
Message 6 of 11
(3,877 Views)

I have the 32-bit version of LabVIEW 2019 installed.

0 Kudos
Message 7 of 11
(3,856 Views)

Darn, never that easy huh? Well, if you post a MAX technical report, I'd be happy to look through it for any other potential SW incompatibilities as a potential cause. The yellow /!\ icon in the project usually indicates something is missing or corrupt... and if I read your above post correctly then that's what you're seeing on the cRIO target, right?

Cheers!

TJ G
0 Kudos
Message 8 of 11
(3,851 Views)

Hi TJ,

 

Thank you for your kind offer. I've attached the report.

 

On another thread, I realized that the target listed in my project explorer window is the wrong one (in fact, one I don't even own). I've added the correct target, moved all the files to the new target, and removed the old target from the project. I'm not sure if it had any influence on this issue, but I'm still getting the error and I wanted to mention this in case it is somehow relevant.

0 Kudos
Message 9 of 11
(3,838 Views)

Sorry for the delay. I don't see anything wrong with any of the listed software versions in the report...

 

Did both cRIO targets show up with a /!\ on them? If so, at which point in the hierarchy? Maybe a screenshot of the project as you see it would help?

 

Also, it may be worth opening a support ticket at this point if you have that as an option...

Cheers!

TJ G
0 Kudos
Message 10 of 11
(3,763 Views)