无法启动Buenchvue

我有一些相同的问题。
它会启动，但永远不会找到仪器。
Windows XP Pro SP3我卸载了基于Agilent或VISA的所有内容，还安装了TEK / NI VISA。
重新安装IOLibSuite和BenchVue以及所有工作。
似乎与TEK签证存在冲突。
（？）



     以下为原文

  I had somewhat of the same problem. Once and a while it would launch but never find the instruments.

Windows XP Pro SP3

I uninstalled everything that was Agilent or VISA based, was a TEK/NI VISA also installed. Reinstalled IOLibSuite and BenchVue and all works. Seems there was a conflict with the TEK VISA. (?)

问题是Keysight VISA需要成为您的主要签证。
在Windows中，只需转到“控制面板”>“程序”>“程序和功能”，然后选择“Keysight IO库”，然后单击“更改”，然后选中“Keysight VISA作为主要VISA”旁边的框并继续。
这将覆盖＆amp;
禁用当前的主要VISA，但解决了问题



     以下为原文

  The problem is Keysight VISA needs to be your primary VISA. 

In Windows, just go to Control Panel > Programs > Programs and Features, then select Keysight IO Libraries, then click Change, then check the box next to "Keysight VISA as primary VISA" and continue. This will overwrite & disable your current primary VISA, but solve the problem

实际上，它比那复杂一点。
NI VISA和Keysight VISA可以在Keysight VISA是Secondary的“并排”安装中共存。
以下是规则：1。如果您首先安装NI VISA，然后是Keysight VISA，我们会自动检测NI版本并将其自身安装为“辅助”。
因此“visa32.dll”仍然是NI的，而“agvisa32.dll”是我们的。
2.如果您先安装Keysight VISA，那么NI VISA，NI会检测我们的版本并重新命名我们的版本，然后将visa32.dll置于其位置。
如果你有两个，Keysight Connection Expert使用Keysight VISA，但许多使用visa32.dll的应用程序（如BenchVue）将使用NI的。
这种方法很好，除非您碰巧有一些Keysight硬件然后由NI VISA控制。
例如，如果您有Keysight USB-GPIB适配器82357B，并且您尝试通过NI VISA控制它，则必须使用NI MAX启用“Passport to Tulip”以允许其软件访问我们的驱动程序。
此外，如果NI IO Libs中存在“损坏”的情况，您可以进入仪器存在且可以使用Connection Expert中的Direct IO与它们通信的情况，但是当您尝试连接到它们时它们将无法工作
他们在BenchVue或其他应用程序中。
此外，如果你有两个，然后你卸载NI VISA，NI删除了他们的visa32.dll，但没有恢复我们的，他们已经重命名。
BenchVue检测到丢失的visa32.dll文件，导致“No IO LIbrary”错误。
这往往令人困惑，因为Keysight Connection Expert仍然有效，因为它使用的是agvisa32.dll，它仍然存在。
我们没有与TekVISA共存的运气，也不建议使用我们的仪器。
除非你有专门使用特定版本VISA的自定义应用程序，否则你真的只需要一个。
Keysight IO Libraries具有一定的优势，特别是与BenchVue一起使用时 - 仪器发现速度和安装速度要快得多。
布赖恩



     以下为原文

  Actually, it's a little more complicated than that. NI VISA and Keysight VISA can coexist in a "side-by-side" installation where Keysight VISA is Secondary. Here are the rules:

1. If you install NI VISA first, then Keysight VISA, we detect the NI version and install ourselves as "Secondary" automatically. Thus "visa32.dll" remains NI's and "agvisa32.dll" is ours.
2. If you install Keysight VISA first, then NI VISA, NI detects our version and renames ours, then puts their visa32.dll in its place.

If you have both, Keysight Connection Expert uses Keysight VISA, but many apps, such as BenchVue, that use visa32.dll, will use NI's. This works fine unless you happen to have some Keysight hardware that is then being controlled by NI VISA. For example, if you have a Keysight USB-GPIB adapter, the 82357B, and you try to control it through NI VISA, you must use NI MAX to enable the "Passport to Tulip" to allow their software to access our drivers. Also, if there is something "broken" in the NI IO Libs, you can get into a scenario where instruments are present and you can talk to them using Direct IO in Connection Expert, but they won't work when you try to connect to them in BenchVue or other apps.

Also, if you have both and you then uninstall NI VISA, NI deletes their visa32.dll, but does not restore ours, that they had renamed. The missing visa32.dll file is detected by BenchVue, resulting in the "No IO LIbrary" error. This tends to be confusing, because Keysight Connection Expert still works, since it uses agvisa32.dll, which is still there.

We have not had the same luck coexisting with TekVISA and do not recommend its use with our instruments. Unless you have custom apps that specifically use a particular version of VISA, you really only need one. There are certain advantages to Keysight IO Libraries, especially when used with BenchVue - instrument discovery is a lot faster, as is installation.

Brian