LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

error -61499 occurred at Compileinstructions.txt. File was not found.

Solved!
Go to solution

Problem Description :

I have a cRIO application that was using an NI-9401 DI module, that I needed to modify to use a cRIO or NI-9411.  I added the module to the 9104 chassis, modified the project to include the correct HW, deleted and re-added the FPGA DIO VI in the app and went to compile it...

 

When I did, I got:

 

error -61499 occurred at Compileinstructions.txt. File was not found. Check

 

target Support SW installation.

 

Does this sound like my Labview Install is hosed up and my Xilinx compiler is missing or broken?  Let me know.  I am up against a deadline to modify this code.  I tried to re-installing the FPGA modules and re-compiling, but when I try to open teh FPGA VI to recompile LV crashes too.

Things are degenerating fast here... I was really not looking forward to blowinga  DAY reloading ALL THE LV system...since I KNOW this what the help desk is goinf to tell me...I've seen this movie too many times.

 

Any ideas are appreciated.

 

JPR

 
0 Kudos
Message 1 of 8
(5,182 Views)

Hey I found the post from 2007 on this subject...wish I'd seen this first...

I tried repairing the FPGA SW modules and now LV crashes when I try to open any FPGA VI.

 

I am "repairing" my LV install now.

 

ANy other comments or ideas on teh original FPGA issue or my repair woes are appreaciated.

 

JRP

 

0 Kudos
Message 2 of 8
(5,180 Views)
Solution
Accepted by topic author neutronjohn
It clearly looks like an installation error.  Make sure you repair LabVIEW, LabVIEW FPGA, NI-RIO, and any other features that appear to be related.
0 Kudos
Message 3 of 8
(5,149 Views)

Hey folks - this was not an install or a firewall issue.  This was an slip-up during the RT application build.  When I built the application I accidently picked 2 RT VIs as the startup VI, instead of choosing the "master" VI.  One was an FPGA calibration vI, and ther other was the master that called the cal. code, set up the TCPIP link, and started FIFOs to harvest thr output of a large channel count DAQ runnning on the FPAG chassis.....

 

...at any rate, having 2 VIs selected as  startup for the RT build was bad news.  The NI AE (thanks Chris) suggested that this causes a deadlock on your RT controller when 2 VIs both try to startup.  When I selected the master as startup, the RT starts up normally, TCPIP listeners work,  and all is well. 

 

Happy developing...Smiley Happy

0 Kudos
Message 4 of 8
(5,107 Views)

Hi guys, I am having a problem with my Crio Fpga program. When i compile it. I get the error 61499. Please see the attached file for more details. I try to reinstall the fpga module but the error is still there. What can i do? It is urgent, please.

0 Kudos
Message 5 of 8
(4,660 Views)

Hello,

 

Just as a quick heads up, usually posting on a year old thread will not get a lot of replies.  If you have an urgent issue its better to post a new thread.  But that's beside the point.

 

As for the problem, did you look at the ideas that the previous poster added? Also there is this KB that talks about the possibility of a corrupt dll.  Finally I have seen this problem if your Xilinx compiler is installed in a directory with a long name.  It should be default be installed to C:\NIFPGA2009.  Make sure that it is installed here and not somewhere with a deep path or any foreign characters in the directory name.

0 Kudos
Message 6 of 8
(4,643 Views)

Hi David,

Thank you but this is not the problem, i check the directory and it is where you said it must be. And the dll, i delete all the files which were in the Temp so that it can create new ones and it is fine. But still i cannot compile. I decided to uninstall everything and intall labview But i am getting this error or message at the end of labview 2009 installation (Check the attachment). I remember, i also had it on the first installation. Can this be my problem? What must i do? Can i continue with the others installation?

Thank you.

 

 

0 Kudos
Message 7 of 8
(4,592 Views)

This picture is just a warning saying that since the firewall is enabled you may have other problems.  However you can continue with no problem.  Did reinstallation solve your problem?

0 Kudos
Message 8 of 8
(4,574 Views)