LabWindows/CVI
DAQmx support
Solved!
Wolfgang, just as margin note, sometime the list of supported HW in DAQmx readme is unreliable.
For example, your NI 9262 C-series card is *not* present in that list, in 20.1, 19.0, 18.0, and 17.0, if I see well 🙂
But the related special APIs are present, at least in headers and online help.
Anyway, may be the problem you shown with DAQmxGet9262CalAdjustPoints iis only an issue due to the order of installation of LabWindows vs DAQmx.
@Wolfgang wrote:
Thanks Rolf,
I can try your suggestion - because I don't have a hard disk anymore I am not afraid of hungry drivers 😁
What I am wondering about is what actually changed in LabWindows that makes it incompatible - if CVI 2017 is supporting DAQmx 19 so why are CVI 2019 or CVI 2020 having problems with it, as far as I know the changes made to the two recent CVI versions were not in the DAQ API but in the IDE, an improved editor and enhanced debugging...
It's usually not incompatibility but simple lack of support for it in the installer. LabVIEW and LabWindows/CVI both require specific bindings to call external drivers. For LabVIEW that are VIs and sometimes wrapper DLLs that help managing parameters between LabVIEW friendly datatypes and the low level DLL interface. For LabWindows/CVI that are the instrument driver front panel files and possible UIR files, as well as the import libraries for the driver DLLs. Also the headers need to be installed in local directories in order for LabWindows/CVI to be able to find them out of the box. The actual driver DLLs are installed system wide in the according system folders for all of these software.
Each LabWindows/CVI version has its own install directory and therefore its own location where these files need to be installed. The installer only can know about versions that existed at the time it was created. So your DAQmx 19.1 driver installer simply can't know about LabWindows/CVI 2020 at all, and therefore not add the necessary support to an installation of it.
There are other complications such as the fact that some of these installed files might be binary in nature and version specific. Then if the installer doesn't come with the correctly created files for the version you want, it simply won't work. if that is not an issue and it often isn't you can copy the necessary files yourself from a successful installation to your new application version. But it is a tedious job to track down all these files and not make any errors along the way. And of course if it doesn't work you can't blame NI, they told you "It is not supported!"
