12-06-2023 12:11 PM
Hi Alex,
Thank you very much for your input.
I do not fully understand the meaning of your CPU spike. Did you mean the spike as shown in Altenbach's reply? some spikes have approximately 3 ms, My understanding of it is that there are many windows processes running in background scheduled by windows scheduler, a spike arises when one of the windows process starts, pulling CPU resource.
I will do more tests to see stability of my application VI. I will also try timed while loop.
As for the LabVIEW crash, I am not sure if I will encounter.
Regards,
Gu
12-06-2023 03:20 PM
Hi Yamaeda,
Thank you for your suggestion.
I checked my LB2015 and could not locate the high resolution time polling wait. It might be included in higher versions of LB. So I could not give it a try.
One thing I could not figure out is that the input is number of seconds as the link below shows.
How can a specified number of seconds to control a loop in sub-millisecond?
Regards,
Gu
12-06-2023 06:57 PM
@edmonton wrote:
How can a specified number of seconds to control a loop in sub-millisecond?
It is DBL, not an integer, so you could enter 0.01 for 10ms or 0.0001 for 0.1ms. Right?
12-06-2023 08:22 PM
Thank you Altenbach
gu
12-07-2023 07:21 AM
@edmonton wrote:
Hi Alex,
I do not fully understand the meaning of your CPU spike.
sorry, cpu spikes in Windows Taskmanager CPU Diagram -
if I remember correctly we where using higher polling times, e.g. not 1 or 2 milliseconds, but rather 10 milliseconds+