Error -61024 When Trying to Run Code on an FPGA Target in LabVIEW

Issue Details

• When running an example or FPGA VI using an FPGA target (CompactRIO, FlexRIO, R Series Card), I get the following error message:

Error -61024 occurred at Open Dynamic Bitfile Reference

Possible reason(s):

LabVIEW FPGA: The device type that has been configured in this function does not match the actual type of the device.  

 

The error is shown in the following dialog box:
 

• I have installed the myRIO Toolkit on my PC to interact with the myRIO controller. However, even though I have installed the required software in the right order, I keep getting the following error message every time I try to use either the Express VIs or the Low Level VIs that are part of this toolkit:

 

Solution

1. If you are getting this error when trying to use a bitfile, the issue is often caused because the referenced FPGA bitfile (.lvbitx) was compiled for different hardware than you are currently using. To resolve this issue, you can try the following steps:

• Add your specific FPGA target to the project.
• Transfer all components (FIFOs, top-level and supporting VIs, derived clocks, etc.) over to the new target and recompile the project on this new target with the appropriate build specifications.

Once this compiles, you should be able to change the code on your LabVIEW block diagram to point the Open Dynamic Bitfile Reference function to the newly compiled bitfile. 

2. If you are getting this error when opening FPGA references remotely from a host, on the Open FPGA VI Reference.vi, try manually entering the network RIO resource name as rio://<ip address>/RIOx

3. If you are getting this error when using the myRIO Toolkit, this is likely to be related to corrupted LabVIEW, myRIO Toolkit, or firmware (on your myRIO controller) installation. Therefore, to solve the issue, please review the steps below:

• Repair your LabVIEW and myRIO Toolkit installation. To do so, you can refer to the following article: Repair Software in NI Package Manager (NIPM).
• Reinstall or, if possible, upgrade the firmware on your myRIO controller. 
• If none of the above steps solve the issue, try removing and reinstalling the myRIO Toolkit, LabVIEW FPGA Module, LabVIEW Real-Time Module, and LabVIEW.