12-24-2022 04:32 AM - edited 12-24-2022 04:41 AM
@TattWee wrote:
It could be due to the recent Vivado 2022 upgrades breaking some of the previous architecture, and the team need more time to fix it. My impression is that this delay is not usual.
Actually your impression is partly wrong. While NI in the past was fairly good in releasing drivers for things like DAQmx and similar high volume drivers within a month of a new LabVIEW release, other drivers like the NI-DMM, NI-Switch, NI-Scope and even NI-RIO occasionally, lagged often several months or more. It definitely never has been a good idea to use a newly released LabVIEW version for a new project development right after it came out. Usually by the time the SP1 release came out most of the dust had settled and it got reasonable to consider using a LabVIEW version for real projects.
I never understood the artificial limitation that a driver installer couldn’t be pointed at an arbitrary LabVIEW directory and it would install the necessary support in there. That NI can’t keep releasing drivers for very old versions of LabVIEW is obvious, but that it didn’t allow installing older drivers in a newer LabVIEW version was simply overzealous user paternalism. I did a few times install an older driver and just copied all the driver VIs over into a newer LabVIEW and the only tricky thing was to locate all the related files scattered all over the LabVIEW folder.
In many cases the reverse also worked just fine. Hide an old LabVIEW version by renaming its installation folder, in order for the installer to not be able to find and remove its older installation files, install the newer driver, rename the LabVIEW folder back and keep using it. This definitely is unsupported and not an option for real project work but still usually just worked.