06-02-2010 10:16 AM
Solved! Go to Solution.
06-03-2010 07:13 AM
06-03-2010 08:04 AM
If memory serves me, I was only able to do that by connecting a display to the CPU.
Ben
06-03-2010 08:07 AM
06-03-2010 08:16 AM
06-03-2010 08:37 AM
This seems to only be available in LV 8.6+. My immediate needs are for LV 8.5, but this might prove useful for code that I need to support in 8.2 as well. Is there any way an NI applications engineer can backsave this for me? I see that it requires ni_emb.dll and NI_Real-Time Target Support.vi. Shoot, on second thought I have a Main VI that runs both on windows systems and RT systems and introducing this to the windows system would cause the code to break. Perhaps I could use a conditional disable with target type to avoid this.
06-03-2010 10:40 AM
06-03-2010 11:28 AM
No hardware reason to not upcovert. It's more of a risk thing, plus it's not my decision.
The reason I wanted to log PXI CPU utilization was beacuse one of the PXIs in a 5 PXI system seems to randomly reboot about once a week. We've been replacing pieces of the system part by part(chassis, controller, cards) and verifying the electrical system(the only thing left is the PXI Power cable). I don't think it's the software because the same code runs on all 5 PXIs. The CPU utilization might be useful in getting to the bottom of this, but I doubt its the culprit. I would only argue for upgrading to LV 8.6 if we've exhausted all other options first.
06-03-2010 11:41 AM
sgregor249 wrote:No hardware reason to not upcovert. It's more of a risk thing, plus it's not my decision.
The reason I wanted to log PXI CPU utilization was beacuse one of the PXIs in a 5 PXI system seems to randomly reboot about once a week. We've been replacing pieces of the system part by part(chassis, controller, cards) and verifying the electrical system(the only thing left is the PXI Power cable). I don't think it's the software because the same code runs on all 5 PXIs. The CPU utilization might be useful in getting to the bottom of this, but I doubt its the culprit. I would only argue for upgrading to LV 8.6 if we've exhausted all other options first.
If that chassis is a RT target then that is one of the signatures of a memory leak. When you run out of memory in a RT app it reboots.
Ben
06-03-2010 12:22 PM