LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Which is better between Wait (ms) and wait until next ms multiple when input is 1 ms

Solved!
Go to solution

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

0 Kudos
Message 11 of 24
(1,617 Views)

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. 

 

https://www.ni.com/docs/en-US/bundle/labview-api-ref/page/vi-lib/utility/high-resolution-polling-wai...

 

How can a specified number of seconds to control a loop in sub-millisecond?

 

Regards,

Gu

0 Kudos
Message 12 of 24
(1,604 Views)

@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?

Message 13 of 24
(1,590 Views)

Thank you Altenbach

gu

0 Kudos
Message 14 of 24
(1,581 Views)

@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+

 

 

 

Message 15 of 24
(1,565 Views)