08-25-2018 03:50 PM
Hi all,
Relatively new to LabVIEW and CRIO devices and I would appreciate any help that I can get in setting up the CRIO with DAQmx drivers. I am using the CRIO 9048 and a Windows 10 PC, but I am having trouble installing the DAQmx drivers on my CRIO device. When I attempt to install the NI-DAQmx 17.6.0 drivers on the CRIO device it is giving me a message that says I cannot install them because a newer version (18.1.0) is installed on the host PC. However NI MAX says that the 17.6 Device Driver is installed. I have attached some screenshots of the NI MAX window for the host PC and CRIO to help clarify what I have described above. Thank you in advance for your help.
-Maxwell
Solved! Go to Solution.
08-26-2018 09:40 AM
When you deal with LabVIEW RealTime, you are dealing with two systems -- LabVIEW on the Host (your Windows 10 PC), and LabVIEW RealTime on the Remote (your cRIO). Both Host and Target generally need to be running the same Version of LabVIEW. It appears that you have LabVIEW 2017 installed on the Host, but might have LabVIEW 2018 installed on the cRIO (it is difficult to tell from your MAX listing).
When you do a first-time installation of LabVIEW, for example, installing LabVIEW 2017 on a new PC, you should do it from the installation media for LabVIEW 2017, and should only use LabVIEW 2017 installation tools. Once LabVIEW is installed, you may be offered updates -- I recommend that you not installed updates for later versions (i.e. it is OK to install a 2017 update, but do not install a 2018 update). Some updates are "supposed to be" backward-compatible, but many (most?) are not.
The same thing goes for the Remote RT System -- if you are running LabVIEW 2017 on the Host, you must install LabVIEW 2017 on the Remote, and (in my opinion) should not install any LabVIEW 2018 components on your Remote.
I think you've got a "mixed system" here. Over the years, I've dealt with many of these problems, never with cRIOs, but with PXI systems. I've tried various "short-cuts", often at the suggestion of NI Applications Engineers, but they've never worked. The only solution is to remove LabVIEW and all its components completely, then do a clean, one-version, installation.
I am sure there will be other readers of the Forum who do have cRIO experience and can correct or expand on my comments. Some may even disagree that you are best served by a re-installation (and they may be right!), but my experience is that when dealing with "mixed" Versions, a clean reinstall saves a lot of time and grief.
Bob Schor
08-26-2018 04:55 PM
Hey Bob,
Thank you very much for the response and all of the helpful information. I followed your suggestion and everything is working. Again thank you very much!
-Maxwell