From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
08-30-2002 04:53 AM
08-30-2002 06:48 AM
08-30-2002 07:41 AM
04-18-2013 05:42 PM
Hi Kim,
I'm in the process of upgrading some older DAQ cards, MIO-16e series, to NI-USB-6529 series. VIs were writen using traditional driver for the older DAQ and now I've to convert them to DAQmx. I ran accross one of the VI used AI one PT and AI mult PT form traditional driver, can shed some light as to how convert these sub-VIs using DAQmx driver.
Thanks,
Chucky
04-18-2013 11:23 PM
@chucky9 wrote:
Hi Kim,
I'm in the process of upgrading some older DAQ cards, MIO-16e series, to NI-USB-6529 series. VIs were writen using traditional driver for the older DAQ and now I've to convert them to DAQmx. I ran accross one of the VI used AI one PT and AI mult PT form traditional driver, can shed some light as to how convert these sub-VIs using DAQmx driver.
Thanks,
Chucky
Chucky, this thread is over 10 years old so I bet Kim isn't around much anymore . It's much easier with DAQmx. You will want to replace these functions with DAQmx read, and select the correctly polymorphic instances for the tasks you have set up: either single channel single sample or single channel multiple samples (or some other variation if you have multiple channels also). I would suggest looking at some examples that ship with LabVIEW. You will find the DAQmx driver to be far less cryptic than the legacy DAQ.