LabVIEW 2012 Error -61017 sbRIO-9606

[LabviewingToday]

I get this error when I using the Open FPGA VI Reference.

The FPGA VI compiles and executes properly but when I try to use it with RT, I get the above error.

Any clues?

Thank you!

[LabviewingToday]

I am sorry I forgot to report the error message:

Error -61017 occurred at Open FPGA VI Reference in rt_host.vi

Possible reason(s):

LabVIEW FPGA: You must recompile the VI for the selected target.

Again, the FPGA VI is compiled and executes as expected on its own but when I try to open it within the RT VI, I get the above error message right away.

[Paul-B]

Hello LabviewingToday,

Thanks for the post, I have a few questions for you in order to have a better understanding of you application:

What is your application, what is the scope of your project?

Has this error always occurred?

Does this error occur for all you applications or a specific custom VI?

Can you compile a blank/simple FPGA VI for testing purposes and see if you can execute it with your RT VI?

What are the steps to reproduce? Please provide some more information or a simplified version of you code that repeats this error so that I can test it on my end.

Trouble shooting steps you can try right now are to delete your Open FPGA Reference and recreate it. Also, if you can successfully compile and run your FPGA VI you can try to reference the compiled bitfile rather than the FPGA VI using the Open FPGA Reference in RT.

Paul-B

[Akiel]

Can i ask in the project how is the fpga set to run, on simulated hardware or real hardware. I think you can get this error if the fpga code is set to run on real hardware without it being present.

[ErikL68]

This issue still exists with LabVIEW 2013.

I got mine working by following these steps:

1. Link the Open FPGA Reference to the Bitfile generated by the FPGA Compiler.
2. Update my TypeDef of the FPGA Reference to also point to the Bitfile.  Annoyingly, this still leaves a coersion warning indicator on the wire going into the Refernce indicator of my FPGA Init sub-VI.
3. Download the Bitfile to the FPGA by right-clicking on the FPGA Target on the sbRIO "Chassis" and clicking "RIO Device Setup", browsing to the file, and clicking "Download Bitfile" .  My FPGA Bitfile was also set to "Autoload VI on device reboot" but that shouldn't be important (and may be dangerous depending on if your FPGA code supports a "safe mode" or not).  If you don't, you'll need the "Reset" and "Run" commands in your FPGA Init sub-VI.
4. Re-build my project.
5. Select "Deploy" from the right-click menu on the Build Spec
6. Select "Run as Startup" from the right-click menu on the Build Spec, and of course, allow the sbRIO to reboot.

I had previously assumed "Run as Startup" also auto-deployed everything, but it didn't seem to work after a FPGA Re-compile.  Only a "Deploy" done separately first got it working.  I've also tried to have the Open FPGA Reference VI link to my Main FPGA VI (along with the TypeDef reference) but had no luck.

[Sam_Sharp]

I had a similar problem last week which I had to go through NI Support to fix.

My problem was that my bitfile was up to date and would run fine interactively but when I tried to Open FPGA Reference in my VI I got error -61017. If i force a recompile it would then run until I rebooted my PC and it would do the same again.

In my case, the problem was caused by moving from LV2012 to LV2013 and I had an unused FIFO in the project which was never called in the FPGA VI...for some reason the reference to the FIFO was still there in LV2012 but not there in LV2013.

The 'fix' was to create a new project, add the FPGA VI to it and compile it under another project and then link the original Open FPGA reference to the new bitfile (or try a bitfile in a different location or a different bitfile altogether) which then updated the FPGA reference, broke my VI because the FPGA reference no longer had the FIFO (quick fix) and then it ran fine from then on.

Maybe the same will work for you but if not, someone might find this after searching for the same error code.