AnsweredAssumed Answered

Can't start Buenchvue

Question asked by menns on Apr 14, 2014
Latest reply on Nov 23, 2015 by w0dz

Like • Show 0 Likes0
Comment • 3

I am trying to set access a 33220A AWB through BenchVue.

When BenchVue starts it displays the following message :"No IO Library detected! Please check your IO Library installation and restart BenchVue." When I click OK BenchVue disappears.

I have installed the IO Libraries. I can access my instrument through connection expert. What else do I need to do to start BenchVue?

No one else has this question

Outcomes

3 Replies

randymatt Apr 16, 2014 9:24 AM
Mark Correct
Correct Answer
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. (?)
Like • Show 0 Likes0
Actions
- keysight-guy @ randymatt on Nov 23, 2015 12:03 PM
  Mark Correct
  Correct Answer
  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
  Like • Show 0 Likes0
  Actions
  - w0dz @ keysight-guy on Nov 23, 2015 1:00 PM
    Mark Correct
    Correct Answer
    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
    Like • Show 0 Likes0
    Actions

Can't start Buenchvue

Outcomes

Related Content

Recommended Content