09-07-2021 01:22 AM
The DAQmx 21.0 manual mentions that controllers like cDAQ-9135 are supported: https://www.ni.com/pdf/manuals/374768aj.html
However, the controllers run WES7 32-bit. And NI installers from May 2021 onwards cannot run on 32-bit machines: https://www.ni.com/en-au/support/documentation/supplemental/19/national-instruments-support-for-wind...
Furthermore, all controllers listed at https://www.ni.com/en-au/shop/hardware/products/compactdaq-controller.html?modelId=119594 are marked "Mature" in their lifecycle.
What's the roadmap for these controllers? How can we use them with LabVIEW 2021 and DAQmx 21.x?
10-05-2021 10:01 AM
According to the articles you will still be able to work with cDAQ 9135, you just won't be able to install new drivers (drivers released after may 2021) on your cDAQ 9135.
Regards,
Lilit
10-05-2021 11:55 PM
@LiYepe wrote:
According to the articles you will still be able to work with cDAQ 9135, you just won't be able to install new drivers (drivers released after may 2021) on your cDAQ 9135.
Hi Lilit,
NI DAQmx 21.0 was released in July 2021. Its Readme says that NI cDAQ-9135 (WES7) is supported. Is this an error in the documentation?
10-06-2021 08:20 AM - edited 10-06-2021 08:27 AM
Well, here's something:
"NI installers that use software components with version 20.7 or newer do not support Windows 7 or 32-bit Windows systems as of Meta Deployment Framework (MDF) 20.7, which is the underlying engine used to create distributions."
NI Installer Requires Windows 10 64-Bit (Version 1507) Or Newer - National Instruments
So, I myself don't use anything later than LabVIEW 2020 SP1.
I did originally create my source code in 2021 and copied the EXE over to the cDAQ and it worked as expected. However, when using the Installer, it indicated that Win 10 was required even though I specified Windows 7 in the build; which is when I posted in the Discussion Forum and got the above information. So I guess 2021 will work as long as you don't use the installer.
Oh, and just a note, LV 2020 (non SP1) has a bug in the General Error handler.