From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
07-03-2020 04:07 PM
Hi everybody. The attached vi is collecting some information of the current hardware. It used to work for my CompactDaq under Linus RT as well as on my windows10 laptop.
For whatever reason it has stopped working on Windows. The CpuLoadTotal gives a failure code 2147220623 which means that this feature is not available on this resource. All the other features give valid values.
As mentioned before: It was working fine for 1 year and now I get a failure message. It might be related to the DSM-service that I just started using. Does anyone know if I have to stop the DSM?
I tried some other ways to get cpuload-information, but they do all fail.
07-14-2020 09:55 AM
No ideas anyone?
07-14-2020 10:28 AM
07-14-2020 11:41 AM
Save in 2017 and share and I'll see if I can reproduce the issue on my machine.
Saying "Thanks that fixed it" or "Thanks that answers my question" and not giving a Kudo or Marked Solution, is like telling your waiter they did a great job and not leaving a tip. Please, tip your waiters.
07-14-2020 11:49 AM
07-14-2020 12:07 PM
Works fine for me as well, using LV 2017 32 bit and Windows 10 Enterprise.
Saying "Thanks that fixed it" or "Thanks that answers my question" and not giving a Kudo or Marked Solution, is like telling your waiter they did a great job and not leaving a tip. Please, tip your waiters.
07-14-2020 02:10 PM
Works fine for me also. Win 10 Pro 64-bit, LabVIEW 2019 32-bit.
07-15-2020 03:15 AM
Thanks to all of you for your efforts. It used to work for me, too. But it does not work anymore. That’s the reason for my posting.
Somewhere in a forum I found something that indicates that the DSM might block the access to cpuload information. This makes sense to me, because I started the DSM for the first time just recently. But it seams that I cannot „Stop“ the DSM. Maybe there is a service that I have to stop, or something in an ini-file ...