LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to use second physical processor on Timed Loop structure

Hi.

 

I have a Windows 10 computer that has two physical processors, each with 32 cores. Both are operating correctly and are identified by the Task Manager. However, when using a Timed Loop in LabVIEW, associating values for the input "Processor" greater than or equal to 32 (cores of the second processor), the error “-825 Invalid CPU Specified for timed structure.” is returned. I have also checked LabVIEW's affinity with this second processor via the Task Manager.

0 Kudos
Message 1 of 4
(303 Views)

@RafaelFalcaro wrote:

Hi.

 

I have a Windows 10 computer that has two physical processors, each with 32 cores. Both are operating correctly and are identified by the Task Manager. However, when using a Timed Loop in LabVIEW, associating values for the input "Processor" greater than or equal to 32 (cores of the second processor), the error “-825 Invalid CPU Specified for timed structure.” is returned. I have also checked LabVIEW's affinity with this second processor via the Task Manager.


Yes, you're perfectly right, (I guess because of this kb and timed loop is slightly related to RT):

 

Screenshot 2025-01-09 15.13.39.png

 

But usually you don't need timed loop as long as simple while loops (56 loops for 56 cores in my case) can utilize PC up to 100%:

 

Screenshot 2025-01-09 15.17.47.png

 

Or simple parallel for-loop the same:

 

Screenshot 2025-01-09 15.19.28.png

Message 2 of 4
(288 Views)

From what I understand Timed loops are not really appropriate for desktop LabVIEW applications because Windows is not a real time operating system.

========================
=== Engineer Ambiguously ===
========================
0 Kudos
Message 3 of 4
(251 Views)

@RTSLVU wrote:

From what I understand Timed loops are not really appropriate for desktop LabVIEW applications because Windows is not a real time operating system.


They sometimes useful, but in very very rare cases. For example, you can use the fact that everything within given timed loop is single-threaded, feel difference:

 

tl.png

 

But for parallel code execution multiple while loops, or parallel for-loops or multiple instances of parallel running SubVIs usually sufficient, there are no significant advantages to run the code on dedicated CPU, LabVIEW and Windows are OK with "load balancing".

0 Kudos
Message 4 of 4
(244 Views)