LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Issue with VISA device

Solved!
Go to solution

Hi,

in a program that works many years i have a agilent 34461a connect over usb. Program works fine last 12. may. Yesterday i have run program and now it have a error with communicate 34461 over VISA. In the MAX i can see the device correct. I think no change in usb setup from 34461, no change in connection to pc. i don't know the reason.

 

 

0 Kudos
Message 1 of 18
(2,172 Views)

Just the word "error" could mean a lot of things, please provide more information about the error and your application.

Santhosh
Soliton Technologies

New to the forum? Please read community guidelines and how to ask smart questions

Only two ways to appreciate someone who spent their free time to reply/answer your question - give them Kudos or mark their reply as the answer/solution.

Finding it hard to source NI hardware? Try NI Trading Post
0 Kudos
Message 2 of 18
(2,138 Views)

Did you try the VISA interactive control panel from MAX?  If that worked, did you remember to close the panel to release the VISA Resource?

 

Another uncommon problem may be that a calibration facility has changed the device language.   That supply supports both SCPI and HPPSL (HP power supply language) 

 Send "SYSTem:LANGuage?" and read the response.


"Should be" isn't "Is" -Jay
0 Kudos
Message 3 of 18
(2,134 Views)

Hi,

below the error message. This time i am not be able to VISA interactive control from MAX (not visible).

 

SeppR_0-1654160847785.png

 

0 Kudos
Message 4 of 18
(2,100 Views)

BFFF0011h = Insufficient location information or the device or resource is not present in the system.

 

Make sure NI-VISA and NI-488.2 are both properly installed.

 

Also make sure the instrument can be "seen" in NI-MAX and that NI-Max can open a VISA session to it.

 

Another good tool that gets installed with the full version of NI-VISA is the VISA Test Panel. 

VTPCapture.PNG

 

I find this invaluable for troubleshooting instrument connectivity issues.

========================
=== Engineer Ambiguously ===
========================
0 Kudos
Message 5 of 18
(2,059 Views)
Solution
Accepted by SeppR

Now it work correct.

The link from resource name in lv code to visa (alias) was lost, for whatever reason.

--> edit in MAX.

Thanks

 

 

0 Kudos
Message 6 of 18
(2,042 Views)

@SeppR wrote:

Now it work correct.

The link from resource name in lv code to visa (alias) was lost, for whatever reason.

--> edit in MAX.

Thanks

 

 


You most likely moved the USB connection to another USB Port.  The serial enumerator (in Windows Registry HKEYs) reserved the alias for that device on the original port and hence, when it connected through a new port, it registered as a new device because of the new location.

 

Now that you know that, you can work within the Plug-n-Pray framework with fewer problems.


"Should be" isn't "Is" -Jay
0 Kudos
Message 7 of 18
(2,014 Views)

@SeppR wrote:

Now it work correct.

The link from resource name in lv code to visa (alias) was lost, for whatever reason.

--> edit in MAX.

Thanks

 

 


Probably the number one reason not to hardcode VISA alias or anything VISA related. (GPIB address, IP address, com port, etc.)

 

Write a routine that searches all the available VISA resources for your instrument on startup. 

 

Here's an example I wrote to find a Ci5001iX AC power source:

FindCi.png

========================
=== Engineer Ambiguously ===
========================
0 Kudos
Message 8 of 18
(2,009 Views)

@RTSLVU wrote:

@SeppR wrote:

Now it work correct.

The link from resource name in lv code to visa (alias) was lost, for whatever reason.

--> edit in MAX.

Thanks

 

 


Probably the number one reason not to hardcode VISA alias or anything VISA related. (GPIB address, IP address, com port, etc.)

 

Write a routine that searches all the available VISA resources for your instrument on startup. 

 

Here's an example I wrote to find a Ci5001iX AC power source:

FindCi.png


Better yet Rename the Alias programmatically.  Very useful for USB devices when they move or even when devices are swapped out for calibration.

Rename Alias.png


"Should be" isn't "Is" -Jay
Message 9 of 18
(1,995 Views)

Hi Sir,

 

I am also working with 34461A, could you share your sample code ?

Or say, where you get the sample code.

Thanks.

Learning from other people
0 Kudos
Message 10 of 18
(1,429 Views)