Error -61330

[LV_USER_MA]

Hi Everyone,

I've been working with Labview 2013, with a setup using the NI PCI-7813R connected to a cRIO 9151.  We are scaling up our system, and have switched over to a cRio 9067 Chassis which has the controlled built in to the chassis.

In setting up the new system, we have to upgrade to labview 2014. When I try to compile our code on the new chassis, I am getting the following error:

Error -61330 occured at niFpgaCompileWorker_ProcessStatusPipe.vi"640001<-niFpgaCompileWorker_GetStatus.vi<-niFpgaCompile_Worker.vi:6460001

Possible Reason(s):

LabVIEW FPGA: An internal software error in the compile worked has occured.

There was a problem initializing the compilation. Exception: The process cannot access the file 'toplevel_gen_proplmpl.xdc' because it is being used by another process.

As a note, I am not running any programs in tbe background, or MAX. 

[a_clucker]

Hi LV_USER_MA,

This error is fairly broad. Please try turning off your firewall. If that doesn't work, try running LabVIEW as an administrator, then compile. If it still fails, you can try using our Compile Cloud Service. This will help narrow down whether it is something caused by the VI you are you compiling or the compile tools installed on your computer.

As for your specific error, it sounds like a resource utilization problem  - something is preventing the compiler from accessing  'toplevel_gen_proplmpl.xdc'. Are you trying to compile two things at once? Maybe a past process is still holding the resource (incorrectly)? If so, you could try restarting your computer and then compiling first thing.

-Friar Tuck

[LV_USER_MA]

Thanks for the tips. I turned off my firewall, made sure NI had an exception, ran LV as admin, and still no luck. Unfortunately, I won't be able to use Cloud compile, because of our company's policy. In terms of resource utilization, everything is below 25%. So I think something is getting stuck somewhere in the process. My guess is that something changed when we went from Xilinx 10.1 to the new Xilinx. I've compiled smaller bits of the code, without a problem, so I'm going to try to rebuild the whole program incrementally to find the bug. A bit tedious, but hopefully it will yield a solution. Any other suggestions are always welcome!

[a_clucker]

Hi again,

Have you ever been able to compile for the cRIO 9067? I missed in your first post that you had recently switched over. The 9067 has a Zynq 7 FPGA chip, and needs Vivado Compile Tools. Also, if you're still using the PCI-7813R you'll need to install Xilinx Compile Tools 10.1 (which is also listed in the linked KnowledgeBase). You can install both on your computer. Also, if you do need to install 10.1, you'll need to make sure you install the right version of 10.1 for your version of LabVIEW (e.g. there's a version for LabVIEW 2014).

Regards,

Friar Tuck

[LV_USER_MA]

Thanks. I'm still working at it, but making progress. I've determine the snippet of code that's causing the problem. It's located in a subvi. Oddly, this subvi compiles fine and the parent VI compiles fine, but when the subvi is in the parent vi, I get the error. We thought it might be PC memory utilization, but that wasn't it either; all files have read/write access, no firewall, etc.

This error did not happen before using the 7813R, and it's the exact same code so I'm guessing it has something to do with the compilation tools (or the fact that I transferred the code over to a new target and haven't checked a "box" somewhere. When I first setup the system, I added all the new compile tools, including vivado. I won't be using the 7813R at all, as the 9067 has everything built in.

I'm going to try to install the 10.1 tools, but when I last checked, they had actually been installed with my clean install of LV2014 (+ Xilinx). I'm currenly eliminating the subvi and placing the code directly in the parent. Hopefully, one of those routes will work.

[a_clucker]

Hi LV_USER_MA,

That is odd that the parent and child VIs can compile alone, but not when the parent is calling the child. I believe moving the code from the child into the parent is a wise troubleshooting step to take. Please let us know the result.

Thanks,

Friar Tuck

[LV_USER_MA]

Thanks. Still trouble shooting. Moving the subvi code into the parent code doesn't work. I can't post the code for proprietary reasons, but it consists of seven LV functions: high-throughput add, high throught multiply, array subset, merge/coerce, number to boolean array, and array to boolean number. I'm now rebuilding the code piece by piece and compiling it. The individual functions compiled, but all of them together don't...so, I have about 16 more compilations (45 min. waittime) before I find the probelm, hopefully.

[a_clucker]

One additional thing we can try is repairing the installation of the Xilinx Compile Tools. If you go to Control Panel - Programs and Features - National Instruments, you should see a list of all you installed NI software. Please select the compile tools and select "Repair" on the right hand side.

[marc_from_canada]

Hey LV_USER_MA,

Were you able to resolve this issue? I am getting the exact same error when I try to compile the FPGA on a cRIO 9068. I have tried everything recommended in the posts up to the post from a_clucker on April 9th, but nothing has fixed the error. At this point my last effort will be to find any labVIEW updates from NI which might be applicable to the FPGA compiler.

[LV_USER_MA]

Hi,

I spent four days narrowing down the error, deleting and rebuilding the code bit by bit. In the end, my error came from the high throughout multiplication function (http://zone.ni.com/reference/en-XX/help/371599H-01/lvfpga/ht_multiply/). I switched to a traditional multiplication function, and the cod compiled.

It's really confouding, and I have no idea why the error would occur, but my only suggest at this point is to start deleting you code, and be patient!