GPIB - VISA problem (LV2014 and Keysight IO Libraries)

[abig]

Hello together!

I'm trying since two days to bring LV2014 - Keysight IOLib - Agilent DSO6014L together.....
And I need some help.

What I want to do

I have a LabView VI to the control the osziloskop and to get values from it. I created the VI with LV8.5.1 and it was working with Agilent Io Lib 14 and Windows XP extremely well. Unfortunately, I had to change to a new computer...

And the problems started, I do not get the components together (anyhow, not without error messages in MAX):

I have connected an Agilent DSO6014L over an Agilent GPIB 82357A to a Windows 7 Enterprise edition - 64 bit.

I've already posted my problem in the german LabView Forum ( http://www.labviewforum.de/Thread-LV-2014-und-Keysight-IO-Libraries-Suite-17-1 )

GerdW has alreday answered and proposed to connect via LAN or to change to a NI GPIB.

But maybe there is a solution to solve my issue, keeping the "old" hardware.

Currently I can run my VI because I use aliasnames that I've assigned in the IOLib and MAX (below I listed the steps that I've done).

But in MAX I still got the error "0xBFFF003A (VI_ERROR_INV_SETUP)" from viFindRsrc.

-> Funny thing. If I dis/enable the tulip passport - save the settings - and restart MAX. I don't have any errors and I can see my GPIB instruments.... uuuuntil I Refresh teh View!?!?

Steps to get it running:

• Installed Labview 2014 - no restart!
• Installed Keysight IO Libraries Suite 17.0.19313.5 (default), automatically as secondary VISA
• Under Keysight Connection Expert enabled GPIB Cards for 488 Program and set PXI options (active resource manager and default trigger manager) to National Instruments
• Connected the GPIB Agilent 82357A and installed the driver (skip windows update driver search for speed up)
• Installed the oscilloscope driver (in my case ag6000 for DSO6014L) for LabView 2014 32 and 64 bit support
• Restart
• Turn on oscilloscope
• Search it in the IOLib - here all is working fine no problems to control the oscilloscope
• In MAX turn on NiVisaTulip.dll under Passports (Restart MAX, getting the 0xBFFF003A Error)
• Restart

Now there are some steps that I could do maybe also before the restart:

• In Keysight IOLib I set the GPIB IDs to 1 (VISA Interface ID and SICL Interface ID) - there was a note that the tulip passport uses the GPIB0 and that that causes into connection issues
• In MAX under VISA Conflict Manager I enabled Agilent VISA under Installed VISA implementations
• In MAX under General Settings - PXI/PCI Interfaces - enabled the option to show all devices accessible to VISA
• In MAX under passports disabled NiVi488.dll and NiViGpvx.dll

Now it was running one times and I've set the same alias name under IOLib and MAX for my oscilloscope.

Aditionally:

• Installed IVI drivers fpr Keysight IOLib
• Reinstalled NIVISA1401Full with 32 and 64 bit support
• Done all NI updates

[GerdW]

never mind…

[abig]

Hello,

I followed an advise from GerdW and connected my oscilloscope over LAN to my workstation.

It's quite simple:
http://digital.ni.com/public.nsf/allkb/D...4A00771A52

After some clicks it's running without changes on my VI. Immediately I've given an alias name, because the GPIB address becomes very long with the IP address included.

I've recognized the following:

My VI works fine with the oscilloscope using the alias name.

Only under MAX I have still problems. Only if I dis/enable the tulip passport - save the settings - and restart MAX, it's working with MAX until a refresh.

It seems that the tulip passport is the reason for VISA issues in MAX, if I deactivate tulip it's also working fine with MAX.

Maybe there is still an option to set or to deactivate to make VISA (tulip) and MAX working together without any problems?

Best regards and a nice weekend

[Dennis_Knutson]

Are you using the Keysight GPIB controller for any other instrument? If you aren't, I would recommend removing it and all Keysight software and just have NI-VISA installed.

[RTSLVU]

---

@Dennis_Knutson wrote:
Are you using theKeysight GPIB controller for any other instrument? If you aren't, I would recommend removing it and allKeysight software and just have NI-VISA installed.

---

I would have to agree with Dennis here. I don't know what changes happened when Agilent became Keysight but their software (Keysight IO Libraries and Benchlink for the 34972A in particular) has suffered tremendously. 

If you can, you should avoid installing any Keysight drivers or software at all costs.

[abig · Accepted solution]

Good morning,

thanks for your posts.

Yes I'm using Agilent GPIBs also for others VIs. So finaly I need a running solution.

I found this post:
Passport (GPIB) in MAX

"Agilent IO Libraries Suite v 16.2.15823.0" is working fine with all my equipment under IOLib, MAX and LabView 2014.

I tried also the "Agilent IO Libraries Suite v 16.3.17914.4", which is also working perfectly with all.

For my solution, I give a short summary of my installation (GPIB Agilent GPIB 82357A, Agilent DSO6014L):

• Windows 7 Enterprise Edition SP1
• LabView2014 SP1
• MAX 14.5.0F0
• Driver for LabView ag6000 (32 and 64 bit support)
• NIVISA1401Full (32 and 64 bit support)
• Agilent IO Libraries Suite v 16.3.17914.4 (IVI driver for 6XXX Oscilloscopes 1.3.24.0)

and settings:

• Agilent IOLib - Installed as secondary VISA over custom installation, I can't set the 488 option (checkbox is all the time reset), but it's working fine without. And I haven't change GPIB or SICL Ids. I've given an alias to my instrument.
• MAX - All passports are activated. I checked teh box show all device accessible to VISA. I've given the same alias to my instrument, like under Agielnt IOLib. Under Conflict Manager Agilent Simulation VISA is enabled and Agilent VISA is disabled, all chosen VISAs are National Instrument.

Best regards,

André

[Dennis_Knutson]

It's unclear what you changed to make it work but I'm glad you found a solution.

[abig]

I think it's clear:

I changed from the actual Keysight(Agilent) IO Libraries Suite 17.0.19313.5 (first post) to an older one Agilent IO Libraries Suite v 16.3.17914.4 (last post).

Because there is an incompatibility (or maybe a bug) between LV2014 and IOLib 17.0.19313.5 that caused error messgaes in MAX.

By the way ('marked as my opinion"):

In the last 8 years I recognized, that many times the actual IO Libraries Suite is incompatible to the actual version of LabView.

To do fingerpointing is senseless in this case, I think it`s based on noncooperativeness between NI and Agilent/Keysight.

I found never a hint from NI or Agilent, where they say this version (eg. IOLib) is running or tested with this version (eg. MAX or LV).

What I saw in the last years, it's that all the time the clients/users figure out how they can bring these worlds together.

[hognala]

Good news, dear world!

We have finally found and fixed a compatibility bug between Keysight IO Libraries Suite 17.x and NI-VISA. This bug would manifest if you had both Keysight and NI installed, then turned on "Passport for Tulip".

The resolution is pretty straightforward:

1. Uninstall IO Libraries Suite 17.0 - 17.2 Update 1.

2. Install IO Libraries Suite 17.2 Update 2 (17.2.20818.0) from www.keysight.com/find/iosuite

*Don't just do an upgrade, as that will potentially leave some "junk" configuration behind that will cause you grief (uninstall is key).

If you continue to have problems, feel free to email me directly about this at:

ioproblems@keysight.com

Alan Copeland

Lead IO Libraries Support Engineer at Keysight

[Briton]

Hi

Just to clear it out. If I want to use a 82351B High Performance PCIe-GPIB from Keysight instead og a NI GPIB PCIe card, i have to install IO Libraries Suite 17.2 Update 2 or newer?

I use LV 2015

Thanks in advance

Bjarne