LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

how to make “visa find resource” working with Agilent device

Solved!
Go to solution

I am trying to use Agilent 82357B GPIB device with LabVIEW for instrument control.

I have checked:

1.       NI-VISA (ver 5.1.1) is the primary visa by checking visa.dll properties under windows\system32 folder

2.       Enable NIVISATulip.dll in NI Max Explorer

3.       Enable the Agilent libraries to work with NI 488.2 in Agilent IO library (ver 16).

I am able to communicate with the instrument in Max Explorer and talk to the instrument in LabVIEW with VISA write for almost all commands.

But I can NOT make one particular visa function (Visa find resource) working with Agilent 82357B GPIB.

 1.png2.png

With NI USB GPIB device, the same code above can find attached instruments as below, where GPIB1 is the Agilent device and GPIB0 is the NI device.

Agilent_and_NIVISA_and_NI4882.PNG

 

I have no clue on how to make “visa find resource” working with Agilent device.

Please help.

0 Kudos
Message 1 of 5
(3,280 Views)

help please!!!

0 Kudos
Message 2 of 5
(3,271 Views)
Solution
Accepted by xubuli2011

Quick question.  Did you also enable 488 support in Agilent? 

Untitled.png

 

If that does'not work try this.  and well see if you found a bug

System API.png

 


"Should be" isn't "Is" -Jay
0 Kudos
Message 3 of 5
(3,265 Views)

Hi Jeff,

 

Your "system find" solution totally works. Thank you very much for your help.

 

 

Message 4 of 5
(3,257 Views)

@xubuli2011 wrote:

Hi Jeff,

 

Your "system find" solution totally works. Thank you very much for your help.

 

 


/\/\/\/\/\/\/\ hand waving----- if there is a difference and the system find works we have a bug in find resources.

 

xu-  is your SSP up to date?  can you generate a tech report from MAX?.  call NI Tech support so we can duplicate, file and track this.  please-  nice work


"Should be" isn't "Is" -Jay
0 Kudos
Message 5 of 5
(3,248 Views)