LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

LabVIEW error -63198

  I use the LabVIEW 8.2 with the Real Time and the FPGA module. I have 3 VIs, one put in my PC category, another one in Real Time category and the third one is in FPGA category. Of course I have successfully compiled the VI under the FPGA category. I open the FPGA VI in the Real Time VI and close it after reading the data by using the FPGA interface icon in Real Time VI. And then, I run the Real Time VI in my PC by paste the Real Time VI in my PC block diagram, as a result. I run the 3 VIs in different places just by press the run button in my PC VI. Both RT and FPGA VI involve FIFO read/write.
 
  I don't know why when I run the VI in my PC after a few times( of course it will call the Real Time VI and the Real Time VI will call the FPGA Real Time), it display
 
  Error -63198 occurred at an unidentified location
  Possible reason(s):
  NI-RIO FPGA Communications Framework:  (Hex 0xFFFF0922) The system has run out of resource handles. Close any unused open    sessions and retry the operation.
 
Can anyone give me any help? What can I do to prevent this problem occurs or make it occurs less frequently?
 
I don't want to open the 3 VI and then compile and run them one by one as there is some delay due to the network(ethernet) and affect the performance of the Real Time and FPGA.
 
  Thank you for your attention!
 
 
 
 
 
 
 
 
0 Kudos
Message 1 of 3
(5,563 Views)
You say you have three different targets in your project 1) Host, 2) Real-Time and 3) FPGA (in the real-time system). It's not clear to me what you're doing when you say you're pasting your Realtime VI in your PC block diagram. But your error sounds like you're opening a new FPGA reference without closing the previous one.

If you can, please post your project.

Message Edited by Bill@NGC on 07-19-2007 12:51 AM

0 Kudos
Message 2 of 3
(5,551 Views)
Hi TCP/IP,
I agree with Bill's opinion.  It sounds like you are experiencing some memory leak issues.  If you find that rebooting the cRIO fixes your problem temporarily and then it returns, you probably want to double check your code to see if there's any opened references that are not closed.

Yi Y.
Applications Engineer
National Instruments
http://www.ni.com/support
0 Kudos
Message 3 of 3
(5,315 Views)