LabWindows/CVI
Getting the CPU temperature
NI has the System Control library that lets you query a lot of things of your system. It may not come with a LabWindows CVI instrument library front panel file but certainly has a header file and import library that you can use in your code. It may not support every possible feature of every computer system but has a lot of things to query that work across various OSes all the same.
If you can’t do what you want with this library it gets all very hairy. Each OS is totally different in what and how you can query things, if you even can!
@RobertoBozzolo wrote:
Can WMI be a solution for your needs? If so you could read this StackOverflow thread and experiment it with my code on using WMI
I noticed a “realtime” in that post. It may not mean NI Phar Lap ETS realtime but if it does, WMI is not even remotely an option. But the NI System Control API is available on all platforms Ni currently supports including all realtime platforms, Windows and Linux (maybe MacOS too, not sure about that).
Accessing it directly by reading CPU registers is most likely not possible as many of those special opcodes are privileged, meaning they can only be called from a Ring0 context, meaning from inside the kernel. Also depending on the compiler it may not support inline assembly or compiler intrinsics. Not sure about CVI but I doubt it does.
- last edited on by
Content Cleaner
@Laci0503 wrote:
@rolfk wrote:
NI has the System Control libray
Could you please provide a link to it? I have been looking for it everywhere but no luck.
https://www.ni.com/en/support/downloads/drivers/download.system-configuration.html#371210
As mentioned, I’m not sure it comes with native LabWindows CVI support. But it absolutely comes with External C compiler support for MSVC and you can always link that in your CVI project.
To get your realtime app be able to call this API you have to make sure the according support is installed on the target. Go into NI-Max, find your target and check the installed software. Select “Add additional software” if you don’t find it already installed.
Device driver development for Phar Lap ETS is an option that has long passed away. The necessary SDK was very expensive but since Interval Zero EOLed Phar Lap ETS in 2013 you can’t obtain it anymore even if you want to shelf out that much money.
What type of sensors are supported and which varies greatly per OS. I’ve mostly used it on NI sbRIO hardware where it supports several temperature sensors including in the FPGA itself.
