LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

error code -61499

I just started getting this error. I have FPGA code that has been runnig for weeks just fine. Yesterday while making some changes to the host code I got an error stating I needed to recompile the FPGA code. That was strange since I didn't change anything in the FPGA code. However I attempted to recompile anyway and got the error code;

 

-61499 ("The VI cannot be compiled in its current state. It may be reserved in another application context for editing. Close other instances of the VI if possible")

 

I don't have any other instances running that I know of but to be safe I exited Labview and restarted everything with the same error.

 

I'm running LV 8.6.1 and NI-RIO 3.1.1 on windows XP. Anybody have some thoughts on how to clear this?

0 Kudos
Message 1 of 6
(4,369 Views)

Ray.R,

 

Thanks for the quick reply. I did see one of those but it didn't seem to apply.

 

I have the problem fixed, at least I am able to compile the FPGA code. I don't know why I had to recompile or what caused the proble in the first place. The problem I found with the FPGA code was ALL of the I/O had become disconnected (red X's) inside the FPGA code. After I went through all of the code and sub-vi's and reconnected everything it is happily compiling again. Hopefully once its done the rest of the application will be functional as well.

 

Thanks again.

0 Kudos
Message 3 of 6
(4,350 Views)

Hi,

 

Glad to hear you got everything working.  I'm not seeing a lot of documentation on Error -61499, but I did notice that the last line in Knowledgebase: Error -61499 in LabVIEW FPGA sounds similar to your resolution of reconnecting your I/O.  Let us know if you see this again.

 

Thanks!

 

- Greg J

0 Kudos
Message 4 of 6
(4,317 Views)

Greg,

 

This is interesting. I may try this solution anyway as this application continues to give Labview fits. I'm not getting the -61499 error any more and the FPGA code compiled and seems to be running fine BUT once out of every 3 or 4 attempts to run my application it will crash Labview without error messages. I restart Labview and sometimes it will ask to recover other times it will just start.

 

I probably can't post my code (I'll run it by the powers that be on Monday) but if you have any suggestions as to where to look for possible problems I would appreciate it.

 

My code is a Queue based producer/consumer with 4 additional while loops all running in parallel. I'm running LV 8.6.1 on XP Pro.

 

Thanks

0 Kudos
Message 5 of 6
(4,295 Views)

The best place to get information regarding LabVIEW crashes are the crash logs that are generated when you select 'Investigate Now' or 'Investigate Later' whenever given the dialog upon restart of LabVIEW after a crash.  The logs are saved to the following directory by default:  ...\My Documents\LabVIEW Data\lvfailurelog.  When you open the .txt file and look through it, you will be able to see any warnings and/or fatal errors that occurred to result in the crash.  You can then enter that information into the LabVIEW Support: Internal Error Support Page to get some helpful information about specific internal errors if that appears to be the culprit.

 

I hope this helps!

 

- Greg J

 

 

0 Kudos
Message 6 of 6
(4,248 Views)