07-13-2012 09:25 AM
Is there anything in the loop throttling the speed of the loop such as wait statement?
A loop without a wait statement would certainly cause the loop to run extremely fast, a "greedy" loop, and would use 100% of your CPU even if not much else is going on inside the loop.
07-17-2012 12:19 PM
do you have something new about your problem? if not, do not hesitate to create a new topic to make it more visible to the community.
National Instruments France
07-17-2012 12:49 PM - edited 07-17-2012 12:54 PM
The problem still exist I've already formatted and Upgraded the Filedpoint firmware in the controller and the host to the latest version of Fieldpoint as well as the system state publisher. but nothing the CPU load is still 100% even without a vi running on it. Even I'd like to monitor the CPU load correctly now we have a cRIO 9075 controller wich is remplacing the cFP2100 function which is why I'll give up on this issue for now. Nonetheless it'd be great for NI to investigate further on this topic to not present the same problem with other controllers.
03-12-2013 02:08 PM
Sorry this is a little belated but the Fieldpoints always show 100% cpu utilization. They processor always takes into account every clock cycle so for Fieldpoints they just left it reporting as normal.
For cRIO is shows up as the idle thread. So your code when executing reports in its own section and idle isn't mixed in.
Good luck with your project. I just wanted to state this so if anyone else comes across the thread they don't think their cFP is broken because of this.
03-12-2013 03:00 PM
Thank you Kyle-H. This information helps though.
At the end we replaced the compact Fieldpoint controller for a compact RIO (because other application goals) so there was no need to deal with this anymore.