07-08-2022 11:26 AM
After updating from LabVIEW 2015 to 2021, I'm having issues related to VISA when running VIs that communicate with Keysight 8164B measurement systems. I attached the error message I keep getting (Hex 0xBFFF009E).
I tried to re-install LabVIEW a couple times (with and without the IVI Shared Components). Then after installation I tried to repair different components from the NI Package Manager: NI-VISA, NI-VISA Runtime, NI-488.2, etc. Usually after changing something I can run the program a couple times without a problem, but after restarting the system I get the VISA error. I can run other VIs that don't use VISA. I tried to install the Keysight 8164B drivers which were not installed before, this added an hp816x folder in C:\Program Files (x86)\IVI Foundation\VISA\WinNT but I get the same problem. I can always find the instrument in NI-MAX and communicate with it. The problem occurs when I open the VISA Test Panel or I run a VI with a VISA session. Also I noticed in NI-MAX under the VISA Properties tab of my instrument (see attached) that I can't download instrument drivers using LabVIEW IDFinder because it shows "LabVIEW Not Detected" although LabVIEW is installed and running.
Is there an issue with LabVIEW 2021 related to VISA? Maybe it's specific to using VISA sessions with a GPIB connection? Any suggestions if everything related to IVI should be installed with LabVIEW? I wish NI would allow us to install previous versions of LabVIEW with an active license. I spent too much time on this problem so I might just try to go back to LabVIEW 2015 by installing from my old CDs.
Solved! Go to Solution.
07-08-2022 12:26 PM
What version of NI-VISA do you have? You can find it in Measurement and Automation Explorer under software.
07-08-2022 01:52 PM
It's the latest version 21.5
07-08-2022 02:00 PM
Have you tried the steps here?
07-08-2022 03:03 PM
Yes, I found that troubleshooter page and tried those steps.
The Visa32.dll file was only under C:\WINDOWS\sysWOW64 after installation. My system is Win10 64-bit so this might be normal. However, I found that the file is also under C:\Windows\System32 on another computer with Win10 64-bit but with LabVIEW 2015 installed. I tried to copy that file to the same folder on my problem computer, but it doesn't help.
Right now I can't set VISA as primary because the VISA Conflict Manager isn't working (see attached). I think this is because I didn't install the IVI Shared Components when I re-installed LabVIEW. I first thought the issue was a conflict with the IVI VISA drivers.
01-02-2023 03:08 AM
Hi,
I cant find the labview library for the device (Keysight 8164B) anywhere, all links are broken. could you please share it with me?
01-02-2023 04:56 AM
01-02-2023 09:43 AM
yea, try the link there' its broken.
01-03-2023 04:20 AM
Hi Tamir,
this link directs you to the Agilent website - as is noted by "3rd party driver NOT supported by NI"!
You need to blame Agilent for changing their website - and you need to ask Agilent for providing a (new) LabVIEW driver…
01-03-2023 05:50 AM - edited 01-03-2023 05:54 AM
It seems impossible to find anything on Agilents website that references any of the 6163, 6164 or 6166 devices. Looks like they completely forgot about that product range and don't want to deal with it anymore. Not even Lightwave meter or similar gives any useful link.
But, since the measurement division of HP/Agilent is now rather under the Keysight brand, it might be interesting to search there, and low and behold:
Their IO Libraries Suite seems to be the software you would want to download and install as it is "supposed" to support 3rd party software including LabVIEW.
There is not an issue with LabVIEW and VSA at all. VISA is integrated in LabVIEW since almost its inception more than 25 years ago and the interface is as stable as you can find an interface.
What is usually the problem is that Keysight wants to install its own VISA software and requires in its own setup software some special setting to enable some sort of side by side mode with NI VISA.