08-24-2009 07:15 AM
I am using a cDAQ 9172 with NI9263 VO and NI9205 VI modules. I want to read a voltage in (feedback) and adjust the voltage out to read some porportial value of the voltage in. The trouble I am having is that the 9263 seems to be to slow. I need to update the voltage out at 500 Hz. I don't seem to get anywhere near that fast. Any ideas?
Solved! Go to Solution.
08-24-2009 11:09 AM
Hi there
LV 9.0 has just been released. Users with LV < 9.0 can't open your VI. Increase the chance to get some help by posting the VI in the lowest LV version possible (use the File\"Save as" menu item).
08-24-2009 11:50 AM
08-24-2009 12:10 PM
08-24-2009 12:40 PM
08-24-2009 01:35 PM
You are doing 1 sample analog inputs and outputs. One sample for each iteration of the loop. That means your acquisition is essentially software timed. Your acquisition can only be as fast as your software loop will run.
You should use N sample acquisition. If you acquire 500 samples, the loop will only need to run once per second. However you aren't really doing anything with the data other than displaying it in a scalar indicator. The human eye won't be able to see 500 samples per second. What do you really want to do with the data once you get it? Graph it, analyze it, log it to file?
08-24-2009 02:24 PM
08-24-2009 02:36 PM
I would recommend browsing through the DAQmx examples in the Example Finder. I'm sure there will be one there that does what you want. Also search the forums for similar questions.
It may be a matter of sharing the clock between modules, but I'm not familiar with cDAQ to know exactly how they function.
08-26-2009 06:38 PM
Hello bassinbc,
Ravens Fan is correct. In order to synchronize two devices they will need to share the same sample clock and start trigger. In LabVIEW, you can go to Help>>Find Examples. Once in the example finder, select Hardware Input and Output>>DAQmx>>Synchronization. From there you can select Multi-Device or Mult-Function. In Multi-Function there is a VI specifically for AI and AO synchronization, but one thing that it is missing is the shared RefClk because the program assumes it is the same card. Keep that in mind when choosing your program.
Regards,
08-27-2009 07:07 AM