Instruments not accessible via E5810A on VISA 5.4

[tergu@gmx.at]

After upgrading to the latest version of LabVIEW and VISA I am having problems connecting to my GPIB instruments on a E5810A gateway. At first I tried to configure everything the same as in my old installation (enable the tulip dll, manually add instruments with ip + gpib0,x). When I click validate I get an error 0xBFFF0011 telling me that the device is not connected or that the location information is not correct. After that I researched the forum and read these threads and the kb article:

http://digital.ni.com/public.nsf/allkb/C6ADD4D65354570086257AA1002F5F67

http://forums.ni.com/t5/Instrument-Control-GPIB-Serial/After-applying-fix-for-using-Agilent-E5810A-L...

https://forums.ni.com/t5/Instrument-Control-GPIB-Serial/After-applying-fix-for-using-Agilent-E5810A-...

I have no real clue on how to get this working again. I tried to enter gpib0,1 or gpib0::1, disabled and re-enabled the tulip dll... When i go to the website of the gateway and list the devices there they are all found.

When I just enter GPIB0 as device MAX can open a VISA session but I am not sure where it connects then?

I am running Windows 7 64bit, LabVIEW 2012 SP1 f4 and VISA 5.4, MAX5.5.0f0

Any help will be much appreciated!

[HeinzG.]

Hi,

could you post a screenshot of the website of the gateway and of MAX. A MAX-Report would also be nice.

Kind regards

Heinz

[Pumuckl]

...here you go.

I tried the old way (gpib0,1) and the new way?? (gpib0::2). When creating the LAN resource the dialog doesn't let you enter the "::" I did that after creating it. Both give the same error when I try to open a visa test panel:

The connection to just "gpib0" can be made without a problem.

The screenshot of the devices connected to the gateway:

Cheers,

Christian.

[HeinzG.]

Hi Christian,

I'm sorry, I have to tell you this behavior is a Known Issue, which has not been solved yet. You can look it up here:

http://www.ni.com/white-paper/14172/en#375426_by_Date the ID is 375426

I'm sorry for the inconvenience you're experiencing. 

Kind regards

Heinz

[Pumuckl]

Thanks Heinz.

Do you know of any plans to resolve that issue?

Best regards,

Christian.

[HeinzG.]

Hi,

yes of course, we will fix this issue. But I can't tell when - I hope in the next version of VISA.

Kind regards

Heinz

[Pumuckl]

Hi,

Would you be so kind and post that info here? I don't want to upgrade to the next version to find out that the problem was not fixed.

Best regards,

Christian.

[HeinzG.]

Hi again,

I will if I don't forget to. But you can also find out:

In the readme of the next version should be a section like this:

...

Known Issues and Bug Fixes

For a list of Known Issues of NI-VISA 5.4, visit ni.com/info and enter the Info Code NIVISA54KnownIssues.

For a list of Bug Fixes for NI-VISA, visit ni.com/info and enter the Info Code NIVISAFixList.

 ...

If the ID is not listed in the NIVISAFixList it is not fixed, yet.

Best regards

Heinz

[SP_80]

Hi everybody,

I just want to add that I have nearly the same problem with the TAMS L488 LAN-GPIB Adapter.

Meanwhile I started a support request at NI and they could duplicate the problem in their lab and created a "Corrective Action Request" for their development team to fix this issue.

Until the problem is solved I work with NI-VISA 5.0.3 or older. Maybe this could be a temporary solution for some of you, too.

Best Regards

SP

[dk_81]

This issue (#375426)  shows up as known in VISA 5.4.X on this list:

   http://www.ni.com/white-paper/14792/en/

But shows up as a 5.4 bug fix here:

   http://digital.ni.com/public.nsf/allkb/82A6CC08D574B40E862578EA0067D8A3

I'm fairly confident it's still present in 5.4.  Any word if it really will get fixed in 5.5?  It's a big deal for people who have gateways that can't be used with current software.