LabWindows/CVI
DAQmx support
Solved!
I have to say that I have used DAQmx 20.1 with CVI 2020 and I have noticed no problems at all.
I don't know if I was just lucky, or that will backfire soon.
What I can say is that LabWindows appears so neglected by NI staff that I wouldn't be surprised if whoever wrote those NI-DAQmx 20.1 release notes didn't even know the new version exists.
Ok, stop ranting.
The NI-DAQmx 20.1 readme is dated July 2020.
The LabWindows 2020 readme is dated August 2020.
So, theoretically, who he wrote the DAQmx readme would not have mentioned any future version. I don't see any problem in this.
No wonder someone said they are not compatible.
From my experiences in various contacts with people at NI, it was not uncommon to come across people who had no idea what LabWindows was.
Apart from the name, the part number and the price, they know very little about it.
Or rather, I strongly hope this is the case 🙂
Hi,
thanks for your hypothesis 😁
In my case I have to rely on DAQmx 19 (or earlier) because of my hardware so I can't test if DAQmx 20.1 will work with CVI 2020 because DAQmx 20.1 does not work with my DAQ board.
In my case (CVI 2020 and DAQmx 19.0) I receive the following error:
For your hypothesis I have two examples of the opposite:
DAQmx 19.1 was released June 2019, DAQmx 19.5 was released Oct 2019, whereas CVI 2019 was released May 2019. Still neither version 19.1 nor 19.5 are officially compatible with CVI 2019.
My problem actually may not be compatibility but the fact that NI support stops assisting you with your problem using the argument that the two software versions are not promised to be compatible. So no need to investigate the issue of their customer further.
Wolfgang, I think the problem you have with DAQmx 19 is not so much with LabWindows, but with libraries that are missing that function your code is calling at all. I don't think I'm wrong when I say that it depends on the specific hardware that has been abandoned by NI and for which some specific functions are needed.
In my case, unlike Roberto, I want (and am allowed) to update as soon as possible.
My configuration, so to speak "validated", is made up of LabWindows 2020 and DAQmx 20.1, and therefore I have never had problems like you did. The hardware I use should be far from abandoned by NI.
I agree that the "formal" compatibility issue is important for interfacing with NI support, but in my past experience the rare times I've tried asking for support isn't that it has had great results (read: none). Therefore this is not an issue for me.
It is very likely that the next version of DAQmx will be declared compatible with LabWindows 2020, if anyone remembers that it exists :-).
If a driver release, be it DAQmx or whatever is released before a specific software release, it will never officially support that release. NI is not going to backport changes to earlier releases. When DAQmx 20.1 is out, anything smaller than 20.1 is considered legacy status and except for high security bugs, nobody will go and look back. So DAQmx 19.x officially supporting LabWindows 2020 (or LabVIEW 2020) is going to stay a pipe dream forever.
You can go through the trouble of identifying what files the DAQmx 19.x installer puts into your CVI 2017 folder and then copy them manually one for one to the 2020 installation if you really want to. Chances are, that if you were diligent in really catching all the dependencies, that things simply will work. I did that once or twice for LabVIEW and it kept working. But no guarantees and no support from anybody else for this. If it eats your hard disk or something even worse, that is your risk. 😁
