LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Problem with the connection with a cRIO

Solved!
Go to solution

I’m encountering a problem. When I deploy my program into my cRIO, the program runs for a while but then loses all connection.This is the error dialog that I get:

 

   

 

   

 

 

The program is made in the scan interface mode, and consists of two sub frames (two subsequences). There are no hardware problems, the cRIO works perfectly for other programs. And the deployed program doesn’t consume too much memory in the cRIO.What could be the problem? 

 

 

Thanks in advance,

Kenneth

Message Edited by Kennie87 on 04-07-2009 06:10 AM
0 Kudos
Message 1 of 4
(3,132 Views)

1. Does you app keep on running, you can check this by creating a blinking User LED on the cRIO controller.

If you app is still running:

2. Check you CPU usage over time, a high CPU usage of higher priority than cRIO-PC communication could break the connection.

If you app has stopped:

3. Have you watched the memory usage over time? (Free and contiguous) I've also had problems like that, where there was free memory, but the lack of contiguous memeory made the app stop.

Regards,
André (CLA, CLED)
Message 2 of 4
(3,110 Views)

Hi Kenneth,

 

Thanks for the post and I hope your well today.

 

I have to agree on the CPU usage aspect.

 

I have seen many problems (in my own applications) where I have either not had any waits in my loops / or not used timed loops or that my code hasn't been efficent. For example, have you used any design patterns such as producer/consumer if you're acquiring at fast rates?

 

I was wondering if it would be possible to request the code? or at least the Host VI to see if there were any signs of what might be causing the connection to be lost?

 

Also, are you using shared variables? or anything else that my require extra processing?

 

I look forward to helping you to resolve your issue.

Kind Regards
James Hillman
Applications Engineer 2008 to 2009 National Instruments UK & Ireland
Loughborough University UK - 2006 to 2011
Remember Kudos those who help! 😉
Message 3 of 4
(3,096 Views)
Solution
Accepted by topic author Kennie87
This is a common problem. I am guessing you didn't put a wait in your while loop on the RT side which effectively starves the communication thread.
Adnan Zafar
Certified LabVIEW Architect
Coleman Technologies
Message 4 of 4
(3,082 Views)