Initialize Visa Agilent N57

I am trying to initialize a session to an Agilent N5764A. I keep getting an error code -1074001254 saying
N5700 Write to Instrument -> Config
Voltage Limit.vi -> N5700 Getting Strarted.vi ->
Agilent 5700 Initialize.vi ->
<ERR> Error sending N5700 Command:
:VOLT 0
<ERR> n5700 "SYST:ERR?" returned:
-410, "Query INTERRUPTED"
The weird thing is that I have 2 of these agilents connected to a PXI Box via GPIB. One of them has address 5 and the other 6 (the one giving the error). When I change the address to 5 and re-run the .vi, it initializes and works fine. I am using the built in tlabview initialize function, and i have tried closing, clearing the visa session, as well as restarting the computer, and also moving around the GPIB connections to no avail. Any advice would be great.
Thanks
Solved!
Go to Solution.

I came to the realization that I was trying to configure a 3rd agilent that was connected to the system, expcept it was a different model number so i was using the wrong .vi. Thanks for trying to help however.

Similar Messages

Initialize visa to use for all tests

Does anyone know how to initialize VISA to use for all tests then close it at the end of the last test?
Example:
The test sequence starts with initialize instruments then testing starts until the last test is to close all instrument handles.
Thanks in advance.

Is this a LabVIEW question or a TestStand question? It actually does make a difference in my answer.
If you are strictly only in LabVIEW, then you just pass your reference wires around where they are needed.
What I like to do for TestStand is make an Action Engine to control my reference to an instrument session. This method also works well with strictly LabVIEW as well. But is overkill for somewhat simple applications.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

How to build distribution package with Agilent VISA as primary

Hi everybody,
I build a distribution package under LW 8.0 in a PC(Agilent VISA is primary), then I install the distribution package in another PC.
But I found the distribution package install NI VISA as primary in another PC. So How could I make Agilent VISA as primary when I build Distribution Package?
Does anyone can help me?

TaoZ,
Does your application use both NI-VISA and Agilent VISA? NI-VISA is only functional as the primary VISA, so if you need to use both NI-VISA and Agilent VISA, Agilent VISA will need to be secondary. If you are using just Agilent VISA, then you should not need to install NI-VISA. If you already have NI-VISA installed on the system, then typically Agilent VISA will overwrite NI-VISA because they use higher version numbers than us, but this is not necessarily always the case. Which version of each driver are you working with?
National Instruments
Product Support Engineer

Agilent 34401A multimeter to PC with Labview driver via RS232

Hello!
I am trying to measure a voltage with Agilent 34401A multimeter connected to PC via RS232 cable. I installed the driver. When I am starting Read Single Measurement.vi. It gives me an error:
Error-1073807346 occured at Visa Open in Agilent 34401.lvlib: Initialize.vi->Agilent 34401 Read Single Measurement.vi
Possible reason(s):
Visa: (Hex 0xbFFF000E) The given session or object reference is invalid.
I would like to ask, how can I adjust my system to use RS23 with Agilent 34401A, if it is possible? If not, should I get GPIB card and cable?
Thank you!
Yulia.

LabVIEW already comes with a driver for the 34401 pre-installed, so I'm not sure I understand what you installed. The pre-installed driver is in the Instrument I/O >> Instrument Drivers >> Agilent 34401 functions palette.
As for the control that Dennis is referring to, it's the VISA control.
As for the VISA version, you should have received a set of driver CDs along with LabVIEW. That will have the minimum VISA version required. Don't remember off the top of my head which version it is. Probably something like 4.1.
Attachments:
visa.png ‏42 KB

Agilent 34410A

Bonjour,
Je veux utiliser le multimetre Agilent34410A
J'ais telecharger les drivers, et j'essais de faire fonctioner les exemples, mais j'ais une erreur:
Error -1073807346 occurred at VISA Open in Agilent 34410A.lvlib:Initialize.vi->Agilent 34410A Read Single.vi
VISA: (Hex 0xBFFF000E) The given session or object reference is invalid.
est ce que qq'un a deja eu ce probleme.

Bonjour,
Vous trouverez dans les liens ci-dessous des informations sur l'erreur -1073807346 :
http://digital.ni.com/public.nsf/allkb/A2561CDE98B66DD4862566510078264F?OpenDocument
http://forums.ni.com/ni/board/message?board.id=140&message.id=4291&requireLogin=False
http://forums.ni.com/ni/board/message?board.id=140&message.id=5276&requireLogin=False
Cordialement,
Christophe S.
FSE East of France І Certified LabVIEW Associate Developer І National Instruments France

Visa attribute error -1073807330

When I run Agilent 546XX Serice Acq Digital Wfm Edge Triggered.vi, I get error...
"Error -1073807330 occurred at Property Node (arg 6) in Agilent 546XX Series.lvlib:Initialize.vi->Agilent 546XX Series Acq Digital Wfm Edge Triggered.vi"
The Knowledgebase refers to stop bit being set incorrectly. But, it show "1" which matches MAX.
Thanks.
Solved!
Go to Solution.

That's not the actual problem. That driver has a bug in the Initialize VI in how the baud rate is configured. The baud rate is set as an integer value, e.g., 9600. The problem is that the Initialize VI has a front panel cluster where the "Baud Rate" is a ring, but the values it spits out are 0, 1, 2, 3, instead of 9600, 19200, 38400, 57600. One way to fix it is to insert a case structure in the Initialize VI so that it translates the 0, 1, 2, 3 to the proper baud rate values. I'm suggesting this method since the other way to fix it is to change the baud rate control so the control sends out the correct value. However, you'd need to do this in all VIs that use the Initialize VI - i.e., all the examples.
I'm surprised the driver was released with this bug.

How can I activate a functional global without displaying a LabVIEW VI ??

Hello. I'm using Teststand and have been got stuck on a problem now.
Whenever I communicate to a LabVIEW VI which is activated as a functional global, I purposely displayed the LabVIEW VI on front pannel to make sure the data communication.
However once I released the check mark 'Show VI front pannel when called' , the data transmission including receiving vanished. As a matter of fact, always the numeric data resturns ' 0 '.
So the data communication must be transacted with a shift resgister function at each step in Teststand, so it always provides a command to the functional global VI for an e-num item selector.
Therefore it looks the shift register function doesn't work at the point anymore in the functional global VI.
Otherwise as long as I suspend the VI as a display, checking on the box 'Show VI front pannel when called' , I exactly can make sure the data communication , receiving the command and returning the data.
Have you heard that kind of unusal problem before?
Do you think it happened due to data communication or just simply Teststand applicational error?
If it has some useful information, I try to fix them.
Thank you.
Noriyuki

hirose wrote:
Hello. I'm using Teststand and have been got stuck on a problem now.
Whenever I communicate to a LabVIEW VI which is activated as a functional global, I purposely displayed the LabVIEW VI on front pannel to make sure the data communication.
However once I released the check mark 'Show VI front pannel when called' , the data transmission including receiving vanished. As a matter of fact, always the numeric data resturns ' 0 '.
So the data communication must be transacted with a shift resgister function at each step in Teststand, so it always provides a command to the functional global VI for an e-num item selector.
Therefore it looks the shift register function doesn't work at the point anymore in the functional global VI.
Otherwise as long as I suspend the VI as a display, checking on the box 'Show VI front pannel when called' , I exactly can make sure the data communication , receiving the command and returning the data.
Have you heard that kind of unusal problem before?
Do you think it happened due to data communication or just simply Teststand applicational error?
If it has some useful information, I try to fix them.
Thank you.
Noriyuki
I'm not sure about the current versions of TestStand but in previous versions you had the possibility to preload certain test steps or initializer VIs. TestStand made sure to keep them in memory for the entire duration of the particular test sequence. You create such an initializer VI and call your init method in there and mark that step as preload. On loading the sequence or initializing it your step gets called and stays in memory for the entire duration. I would be surprised if TestStand doesn't support this anymore.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Insufficient system resources error

Quick question....I keep getting the following error after my LabVIEW
7.1 program has been running for a while:
"Error -1073807300 occurred at agn330xa Initialize With Options.vi
Possible reasons(s):
Driver Status: (Hex 0xBFFF003C) Primary Error: (Hex 0xBFFF003C)
Insufficient system resources to perform
necessary memory allocation."
It varies on which instrument's driver it occurs on, but it alway seems
to occur on the initialization VIs after my program
loops back through itself a few times. This error causes me to close
out LabVIEW completely before my program will run again.
I am closing out the VISA sessions after each of my tests for all
instruments used in that test.
Any thoughts??
Thanks,
Ryan

The upgrade didn't help. Still get the error.
Since my last change, the error is consistantly occurring at the exact same place every time, on the same driver VI, and on the same iteration through my program.
My program basically loops through the bulk of the program 6 times, and it is now on the third time through that it gets stuck on this error. Before I put in the VIs to close the VISA sessions, it was always getting stuck on the second loop through. So putting the VISA closes in helped. What else more can I do??
Is there a way to allocate more resources for my program, or some way to free up more memory to use for it?
Any other thoughts at all would be helpful.
Message Edited by REash on 12-07-2006 04:27 PM

Agilent 53131A VISA Driver ?

Hello !
I´m looking for a driver to Agilent 53131A...
The current driver for download don´t have/use
VISA (current driver is CERTIFIED by NI but VISA is not
implemented, strange ?) !
Software: Labview 7, Teststand 3
I don´t like re-work...
Thanks in advance
Niklas Lithander
NOTE Norrtelje AB

Let's try again...
Try these steps:
1. Follow the link in my previous post.
2. Download the "CVI" version.
3. Extract the zipped contents into a temporary directory.
4. Start LabView.
5. Open a blank vi.
6. Under TOOLS => Instrumentation => select "Import CVI instrument driver"
7. Select "HP5313XA.FP" from your temp directory.
8. It should select all already, so simply click on "OK".
9. Let it convert.
10. Go back to the "new" block diagram in LV.
11. OPEN a file called "HP5313XA.llb". It is located in the instrument library inside your LabVIEW directory.
12. Select the vi you want (ex: initialize.vi)
13. It will be in VISA.
14 )
-enjoy-
JLV

LabView - Agilent 34970A initializer error

i am using LabView 6i connect with GPIB-PCII (ISA) to Agilent 34970A
i downloaded VISA software and use it to control my device. However,
the initializer for the 34970A sent an error message "old visa occur
with my device". LabView can still run, but didn't trigger the device
to start taking measurement.
the error message number is 107380743
i would be appricated if anyone can help on this issue

Here's a copy of my modifed VI.
Attachments:
HP34970A_Initialize.vi ‏113 KB

When trying to work with Agilent 34401A multimeter (serial RS-232 connection), HP34401A Getting Started.vi gives always the message: "Error 1073807369 occurred at Old VISA Open ".

Baud rate and parity are set correctly, RS-232 cable is also connected correctly. My QuickBasic program has no problems to read and write to the Multimeter. It is obviously a software problem: the same error is persistent if I disconnect RS-232 cable.
I downloaded NI-VISA 2.6 for Windows 95/98/NT/ME/2000/XP frorm digital.ni.com and installed it. But it did not help.
Thank you in advance
Best regards
Alexei Soloviev

Hi Steve
I have problems with the 34401A and serial communication. Do you remember
where the error was in the code ?
Thanks
Klaus
wrote in message
news:[email protected]..
> Alexei,
> This may or may not help, I was tasked to do something similar
> recently and found an error in their driver. The GPIB VISA worked
> fine, but when I tried it on serial it played up. There was an errant
> carriage return (or CR/LF I can't remember). GPIB liked one and Serial
> liked the other. It always amuses me that we never have problems with
> Quickbasic!.
> If you want me to dig deeper give me a shout.
>
> Steve Watts
>
> On Thu, 24 Jan 2002 06:16:55 -0800 (PST), "Alexei V. Soloviev"
> wrote:
>
> >When trying
to work with Agilent 34401A multimeter (serial RS-232
> >connection), HP34401A Getting Started.vi gives always the message:
> >"Error 1073807369 occurred at Old VISA Open ".
> >
> >Baud rate and parity are set correctly, RS-232 cable is also connected
> >correctly. My QuickBasic program has no problems to read and write to
> >the Multimeter. It is obviously a software problem: the same error is
> >persistent if I disconnect RS-232 cable.
> > I downloaded NI-VISA 2.6 for Windows 95/98/NT/ME/2000/XP frorm
> > digital.ni.com and installed it. But it did not help.
> >Thank you in advance
> >Best regards
> >Alexei Soloviev
>

VIs for Agilent 33250A (function generator) and SR-844 (lock-in)

I am new to Labview. I was unable to find VIs for Agilent 33250A (function generator) and SR-844 (lock-in). Can someone help me find these?
Solved!
Go to Solution.

What did you actually search for? I just went to the Instrument Driver Network, entered '33250A', found it's driver, entered '844', and also found it's driver. I did not try this from the Tools menu in LabVIEW but it should also have found them.

Controlling Agilent E4438C ESG using NI-VISA GPIB

Hii all,
I am controlling Agilent E4438C ESG using NI VISA GPIB...Whenever i want to set the amplitude and frequency, i will send it the commands....but when i want to capture the information i am unable to do it....
I gone through the VISA GPIB user and programing manual ..there is various functions such as ibwrt etc..How can i use those commands in the LabVIEW...
One thing more ..i wanna to know, the commands vary according to the instrument type..
If yes from where i can get those commands for Agilent E4438C ESG....
Puneet
CLA 2014
CCVID 2014

You should download the driver. The main search page is at http://sine.ni.com/idnetwork/. Just enter 4438 into the search field and you will find the driver.
Your comment about capturing the information is not clear. What exactly do you want to read back from the instrument? You should spend some time reading the programming manual for the instrument. When you find the query (a command terminated with a '?") you want to issue, you would see if it exists in the driver. If it does, just execute the driver function. If it doesn't, then you do a VISA write of that command and then do a VISA Read.
p.s. The programming manual is available from the vendor.
Message Edited by Dennis Knutson on 02-13-2008 09:18 PM

Unable to initialize the VISA library

/usr/local/vxipnp/linux/NIvisa/NIvisaic --> Unable to initialize the VISA library. The VISA Interactive Control utility will exit.
Running RHEL 5.11 (32-bit)
[root@x74943 ~]# rpm -qa|grep nivisa
nivisa-4.5.1-f0
[root@x74943 ~]# rpm -qa|grep ni488
ni4882i-2.5.1-f0
gpibexplorer and driverwizard start up fine. I've never used nispy, but it is bombing too.
x74943(paul.autore)8> ./nispy
LabVIEW caught fatal signal
8.2.1 - Received SIGSEGV
Reason: address not mapped to object
Attempt to reference address: 0x10
Segmentation fault
Uninstall and re-install of NI-VISA didn't help. NIvisaic was running fine days ago. This system was not patched since it was working OK, but the root partition was reduced and a new physical volume was created for LVM so that /var, /tmp,... could be copied over and remounted as separate file systems.
I have not tried yet to mess with reinstalling NI-488.2
ldd /usr/local/vxipnp/linux/NIvisa/NIvisaic shows same output as an identical working system

This issue has been resolved. It may have been the re-install of NI-488 that really solved the problem. The ‘gpibprtk.ko’ module had a problem loading, but we also found a problem with a shared memory kernel parameter.

Agilent X-Series Status Byte Register Subsystem VIs

Hello!
I am looking to see if there exists LV code to identify the status of the STATus:QUEStionable event register of the Agilent X-Series Status Byte Register Subsystem? I'm not exactly sure if I can simply query the instrumentation with the SCPI command "STAT:QUES:REF?"using a VISA Write followed by a Read. This being new to me, I think you must configure specific bits of the register (i.e., enable a particular bit[s], using the event enable register) before you can proceed with the query? At any rate, it's a proper sequencing set of commands which is required, just like mostly everything I presume
Thank you in advance for your efforts!
Sincerely,
dan

send *esr? to return the event register and *ese? to determine which events are enabled
"Using a VISA Write followed by a Read?: " --Yes this is the correct approach
The Programmer's guide pg 32 Shows the STATus: subsytem commands to enable the event registers
Jeff

Initialize Visa Agilent N57

Similar Messages

Maybe you are looking for