How do I resolve Error 63198 with FPGA Code on a Compact RIO?

[Mohoyt]

We’re developing a CompactRIO based RT application around the crio-9012 controller & 9103 fpga chassis.  When running the FPGA code from the Host VI, occasionally (approximately 1 in 3 runs) this error message appears, and the FPGA code does not execute.

‘Target Specific Error Encountered’

‘A Driver for the target returned the following error. Consult the LabVIEW help database or the target documentation for help in resolving the issue.

Error Code: -63198

NI-RIO FPGA Communications Framework: (Hex 0xFFFF0922). The system has run out of resources. Close a session and retry the operation.’

The only way to restore FPGA execution is to restart LabVIEW.

Previously in 2-months of integration the error never appeared. Recently the software on the CRIO has been updated to 2.3, from 2.1.3.

What is causing this problem and how can I go about resolving it?

Thanks,

Moses

 

RT target cRIO-9012, FPGA 9103 chassis. CRIO modules 9423, 9474, 9215 & 9263, NI-RIO 2.3, LV 8.2, RT 8.2, FPGA 8.2, Win2000 SP3.

.jpg image of error attached.

[Bassett_Hound]

Hi Mohoyt,

Most likely your running into an RPC connection attempt that's failing because there are already 8 RPC sessions open (currently the maximum) or there are too many RPC sessions in parallel.  After 5 minutes of inactivity, the 2.3 RIO RPC server will terminate idle RPC connections. If your using a console out connection you should see the message "NI-RIO server terminating an idle session" on the console.

Just guessing, but I would probably say the code is looping around an open conneciton without calling a close.  Has anything else changed since you upgraded?  You might want to post some images of the code so everyone can take a quick look.

Bassett

[jonemo]

I am currently having the same problem. The FPGA reference that I open is closed in the code.

[Bassett_Hound]

I'd probably guess the same thing.  You might post a image of your code or attach a small project that reproduces the issue.

Bassett

[jonemo]

I traced the error down to aother problem that I had for much longer time. In case you don't like long description of totally farcial stories stop reading now.

I have bought a cRIO 9014, thats the new one. Unfortunately, I am using LabVIEW 8.20. That brings along the problem that the two don't really work together (or rather the old Measurement and Automation Explorer cannot work with the new cRIO because this runs RT8.5). Together with the hotline I developed the solution to keep all the old LabVIEW things and put "downgraded" firmware on the RIO by FTP (that was put together for me by the guy from the hotline).

So far so good. Unfortunately, I had already installed the new RIO drivers and new MAX, etc. As this appeared to be working I started off doing stuff and sporadically received the above error. This has the same root cause as some other errors I encountered such as this: http://digital.ni.com/public.nsf/allkb/b77ceb8067558f6f86257203007f1e91. Hence, I should really downgrade my computers software to the old RIO drivers.

Now comes the big joke. Because I am struggling with this problem for three weeks now (on an almost daily basis running from one incompatibility into another while dealing with equally ignorant support staff on the phone) I had reinstalled my LabVIEW in its entirity. Since then "National Instruments" does not appear in the software list in my Windows Control Panel anymore. This leaves me no way to downgrade my software to the old RIO drivers. Which leaves me in the deadlock of incompatibilities.

So my current problems now boil down to: How do I manage my host PC's National Instrument software if NI does not appear in my Control Panel's software list???

[Mugur]

Jonemo

unfortunately i don't have a solution for you but rather a question. I am facing a similar problem. I have a 9012 controller and on the host computer LV 8.0. I can't acces the controller in LV and I guess I have to downgrade my cRIO to LV RT 8.0. I really appreciate if you advice me on how to do that, and what potentially problems I can face. Do I need to back up mu cRIO first?

regards

mugur