LabVIEW code ramifications upgrade from B series DAQ to M series DAQ

[Blair_Hogg]

We have a LabVIEW automated test system that was developed by a third part many years ago using a PCI-6014 B series device. I need to replace the device and the 6014 is no longer available. What issues might I run into if I upgrade to a PCI-6221 M series device? Will the virtual instruments still work the same? 

The .vi's were written in LabView 8.0. For signal generation and measurement AO Write, AO Start, AO clear and AI acquire code blocks were used. 

Thanks!

[Blair_Hogg]

I think that I found my answer here:

http://www.ni.com/product-documentation/4342/en/

[Kevin_Price]

That link is a good resource for getting started.  The existing DAQ vi's will *not* run with an M-series 6221 device.  (Aside: a newer X-series board might be a better choice, even if it means upgrading the PC hardware to provide the needed PCIe slots.  Possibly the 6321 which is likely the intended replacement for the 6221.)    Your code uses the legacy "Traditional NI-DAQ" driver which never supported M-series.  You'll need to rewrite all the DAQ code in terms of the DAQmx driver.

Not all the functionality is a direct 1-for-1 replacement.  The linked article illustrates that *some*, but tends to emphasize the things that map more straightforwardly.  In general, I think it usually works out better to define what the DAQ tasks need to do and how they work together, and then just program the tasks from scratch in DAQmx.  Maybe use the original code as a reference for figuring out functionality, but don't try to substitute one DAQ-related function at a time.

-Kevin P