LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

labview vi can run at lower frequency but not high frequency

/Y,

 

Thanks for your reply! The loop is for the multiplexer. Do you think I should neglect it? Or I need to insert one more DAQmx set timer?

I have total four multiplexer in my DAQ. Do you think I should combine them?

 

 

Best regards,

ppeng

0 Kudos
Message 11 of 14
(332 Views)

Looking at the code again, the digital ports are only set once, although repeatedly, so you can remove the loop and only execute it once. 🙂

If you want to set it several times, i'm reluctant to change a digital port at 1kHz, although it might work. One solution is to compare the control between iterations and only write to digital if changed.

/Y

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems
Certified-LabVIEW-Developer
0 Kudos
Message 12 of 14
(322 Views)

/Y,

 

Thanks again. I have removed the loop but it still cannot work well. Now the problem is there is no error coming out, but the time consequency is not function well. Do you know how to deal with this?

 

 

 

Best Regards,

ppeng

0 Kudos
Message 13 of 14
(308 Views)

ppeng, have you looked at some of the examples? A simple example that uses the hardware clock is "Cont Acq&Graph Voltage-Int Clk.vi". Basically, instead of using the timed loop (which has an upper limit of 1 kHz on Windows) to deliver one reading/channel at a time, you have the hardware deliver multiple readings/channel. Also, I strongly recommend dumping the channel data into a queue, and then reading that queue in a separate loop to write it to a file. That way, the data acquisition rate won't be limited by the file write operation.

0 Kudos
Message 14 of 14
(288 Views)