wait time minimum

[marconi2005]

I would like to know which the smallest value than I can use  whith the  function wait time and wait time until ... . Is possible use values less then 1ms like microseconds. Because i have a problem in control with a board 6023E a step motor i need send two signals une    for control the direction and other for control the step but this pulses (step) need have  frquencys  larger than 10000Hz

[marconi2005]

here is the screenshoot http://ftp.ua.pt/incoming/marcolab/prb.jpg

[johnsold]

The resolution of the Wait functions is 1 millisecond. The minimum time is zero milliseconds. If you are trying to do software timing faster than tens or even hundreds of milliseconds you will probably not have good results unless you are running on a real-time OS. Operating system latencies on any desktop OS will inevitably disrupt your timing at that level.

Some DAQ boards are able to provide hardware timng much faster than what can reliably be achieved with software.

Lynn

[marconi2005]

How can  running on a real-time OS.

[AnalogKid2DigitalMan]

I think the 6023 has a counter/timer on board. You can use this to supply a freqency to step your motor. You could also use one of the digital I/O to control direction.

[SanaaT]

Look at this link below:

https://www.ni.com/en/support/documentation/supplemental/21/using-quadrature-encoders-with-e-series-...

I'm sure that it will help you.

Sanaa T

[Kevin_Price]

I'd like to refer you to another thread I was in a while back.  The essentials are:

1. Use of a 'timed loop' (requires LV 7.1 I think) where the pulsetrain output is the timing source.  This allows iteration speed to be governed at resolutions below 1 msec. 

2. Timed loops get a very high execution priority, so you'll likely get better consistency than you would with 'Wait (msec)'.  Nevertheless, the timing still won't be guaranteed under Windows.

3. The example I posted doesn't sound like an exact match for your current app, but does illustrate a few ideas you may be able to use.

4. The example includes a 3rd counter used to count # pulses and verify correct behavior.  As mentioned, you'll need to get rid of everything related to that 3rd counter since your E-series board only has 2 counters.  Also, I wasn't able to test on an E-series board.  I think it should work there, but can't verify.

-Kevin P.