Quote:
Originally Posted by Greg McKaskle
At this point I don't have a project that shows the issue in a reproducible way. Please contact NI technical support and see if they have suggested solutions, and see if they would like a copy of your project and files so that it can be investigated more thoroughly.
Greg McKaskle
|
I took his advice and called NI on bag day, unfortunately I did not have the cRIO in front of me at the time. Tech support was very helpful and mentioned a couple of things to look for to identify the reason for not being able to deploy code.
1) Check for high CPU utilization:
If the CPU utilization is too high it does not deploy code. It pegged at 100% for a few seconds during the start up. Our CPU was running between 35 - 40% after initial start up was complete. This was still too high for our 4 Slot cRIO.
2) Check for CPU utilization with no applications running:
Reformat the cRIO, reboot and run without deploying any code. Check the CPU utilization at this point. We were running at 0%. If there was any CPU utilization, I was supposed to call back before they closed at the end of the day.
I offered a copy of our robot project code to test with. They said due to the many different environments, it would be a very generic test and may not reproduce our situation.
The suggestion was:
A) Use the cRIO Imaging Tool to set the NO APP Switch
B) Reboot cRIO
C) Deploy code
D) Use Imaging Tool to turn off NO APP Switch
E) Reboot cRIO
These steps are also necessary if we want to run the code from a laptop to debug. It is a viable work-around for now. I can imagine this becoming an issue at competitions if we need to redeploy any code in between matches.