We are having a problem where the cRIO “crashes” or keeps losing comms from the laptop when we try to run the code for vision processing on the cRIO. We used the NI Vision Assistant to generate code which we put into Labview to run on the cRIO, and the actual NI Vision program works when the VI is ran locally on the computer. Is there something that we might have missed?
If you are using an 8-slot you may be using a function that isn’t in the vision library (the 8-slot has a reduced library). It is also possible you are using up all of the cRIO CPU. You can check this on the Charts tab of the Driver Station.
Beyond that what I would recommend is using the imaging tool to enable NetConsole and using that to see if there are any error messages being thrown to the console.
What is the IVA icon at the far right of the picture doing? My guess is that you are using some uncommon vision functions and have found a but, possibly due to odd parameters being passed in. If you send in your entire project, we can look at it more closely. Send it to the NI forum.
We had a problem like that for a while when we started vision processing. Look for memory leaks, undeleted pointers to images, etc. some of the different ways of image acquisition don’t overwrite the old image but put a new one in memory. Try a loop counter to see how many times it runs. if it runs 20-30 loops and then stops, that’s most likely your problem.