After applying fix for using Agilent E5810A LAN/GPIB with NI-VISA 5.2 or greater, I receive error code 0xBFFF00A5 with all configured instruments

[dk_81]

The error code 0xBFFF0011 (Insufficient location resources . . .) is a known, unsolved issue for NI-VISA 5.2 and greater.  See bug #375426.  Although that was reported with an Agilent E5810, it seems to affect other VXI-11 based lan/gpib gateways in the same fashion.

Dave Kinsell

TAMS Inc.

[Edna-S]

Hey dK_81,

Yes that is right. CAR# 375426, is in progress. The workaound solution is to install VISA 5.1 or earlier, and follow the below link. Our R&D team is working on resolving the issue.

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

Thank you!

[dk_81]

Thank you Edna for the response.  However, that KB article you reference simply isn't correct.  The E5810 and other VXI-11 based gateways don't work with 5.2 and later, CAR# 375426 will need to be resolved in order to fix that.  Although the settings in the KB article are reasonable things to check, they don't allow the third-party gateways work with VISA 5.2 and later. 

Regards

Dave Kinsell

[SP_80]

Hello,

I wanna let you know that meanwhile there exists CAR#425003 which is specially related to the TAMS L488 LAN-GPIB Adapter. NI checked the device and could reproduce these problems with MAX.

Nevertheless, for me it seems that the reason for the malfunction of all (already mentioned) third party LAN/GPIB interfaces (i.e. Agilent E5810A, TAMS L488, ICS 8065...) could be the same.

So, NI please let us know when this bug is fixed. Good luck!

Best regards

SP

[lenzk]

Hi,

are there any updates on this issue?

I experience the same issue with my TAMS-LAN-GPIB adapter since I have to use the newest Labview with MAX 5.5.0f0 and NI-VISA 5.4.

On my other machine with MAX 5.0.3 and NI-VISA 5.0.3  I have full access to all GPIB devices attached to the TAMS-LAN-GPIB adapter using the common address scheme "TCPIP0::.....::gpib0,6::INSTR" for example.

Now with the new MAX, this does not work anymore. I can connect to the TAMS-adapter but not to the attached GPIB devices.

On validate I alway get the 0xBFFF00A5 error.

The NI-488.2 version on the new machine is 3.1.

Any ideas or solutions?

Regards,

Kilian

[lenzk]

Another thing iuf it might help.

I just compared what NI Spy/NI I/O trace gives me:

on the new machine where it is not working it says:

viOpen (0x0318B0C8, "TCPIP0::192.168.3.6::gpib0,16::INSTR",0,0,0x00000000)  STATUS=0xBFFF00A5

on the older machine where it works:

viOpen (0x041C62B8, "TCPIP0::192.168.3.6::gpib0,16::INSTR",0,0,0x0424C210) STATUS=0

Regards,

Kilian

[SP_80]

Killian,

thanks for the addtional information from NI SPY. Perhaps this could help NI for finding the reason for this bug.

The behaviour you describe is exactly what everybody of us experienced with the latest version of LabVIEW.

So, let's hope that NI will fix this bug soon.

Until it is fixed we have to work with NI-VISA 5.0.3 or earlier...

Regards

SP

[dk_81]

Good point about 5.0.3 or earlier being required to work around.  CAR # 375426 says it got broken at 5.2, and a KB article says the same, but I just verified it's broken in VISA 5.1.2.

[lenzk]

Hi,

I had a longer communication with the tech support. NI promised me to fix this issue and they say that it might be fixed in VISA 5.5. However, a release date is unclear.

In the moment I downgraded to VISA 5.0.3 where it works.

Regards,

Kilian

[dk_81]

VISA 5.0.3 uses MAX 4.7.4, whereas later versions bring in MAX 5.0.  The problem appears to be the newer MAX trying to use gpib0::7 type of addressing for instruments, rather than the correct gpib0,7  Perhaps one could user newer VISA with the older version of MAX?