LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

What does error 52005 mean?

Hi,

 

I am using lv 2010, and all the latest fpga ,rt and rio modules on my cRIO 9004. I am taking data from the analog input module and writing it into the DMA FIFO and reading from a Real-time VI on the cRIO 9004. When i execute this i get an error 52005 EVERY ATERNATE TIME . that is i deploy the code on RT and the first time i run it i get the error. I click on stop. the  run it again. it works fine. then i stop and run again. Error 52005. then again the same process. there is some recurring error, that gets reset every alternate run. i dont understand this. please see the attached VI , if it helps. 

 

Also there is another error 61141 that i get. I get this error when i access the RT memory over FTP using the FTP explorer on MAX . the error says that my fpga device is busy and needs to be cleared in order to execute anything further in it. I understand.It occurs when the FTP window is open and i try to run the RT VI. The funny thing is , it should not appear once i close my FTP session, right? but it does not. i have to reboot my cRIO in order to make it run. It could be a minor glitch, and it doesnt really matter much to me. just curious. But the 52005 is important as i plan to deply the unit as standalone RT.

 

Thank you for your time and help!

 

Rajesh

0 Kudos
Message 1 of 3
(4,199 Views)

sorry here is the VI

0 Kudos
Message 2 of 3
(4,194 Views)

Rajesh,

 

Have you seen this KB yet? http://digital.ni.com/public.nsf/allkb/8A49034C699AA6FF862577D2007D9970?OpenDocument. It talks specifically about using the Scan Clock FPGA Chassis I/O node, but that doesn't necessarily mean it won't apply to your situation.  You could try installing the cRIO software with Scan Engine support from MAX.

 

As far as the 61141 error is concerned, in theory you're right, but I really don't know why the error keeps occurring. It could be a built-in security feature of the cRIO where when that error is detected, you're prevented from continuing using FTP because there's a risk of further damaging the cRIO.

 

Rory

0 Kudos
Message 3 of 3
(4,153 Views)