NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Unterminated errors using NI's IVI (AG6000) with Agilent's DSO5054A Oscilloscope

Hi,

 

I keep getting timeout errors when using the IVI file ag6000 with Agilent's DSO5054A Oscilloscope over GPIB.  Using TestStand, I am able to calibrate the o-scope about 50-60% of the time and read from the o-scope about 2% of the time.  When sending a command using the IVI, the o-scope typically displays "query UNTERMINATED."  Attached is the error TestStand gives when it is not able to talk correctly.  In MAX, I can talk to the o-scope using the GPIB communicator tool 100% of the time.

 

Is there an updated version of the ag6000 IVI file that works with the DSO5054A that I don't know about?

 

Thanks.

0 Kudos
Message 1 of 10
(4,337 Views)

Are you able to communicate with the instrument using the same IVI functions outside of TestStand, using LabVIEW, CVI, or some over progamming language?

 

 

Regards
Ray Farmer
0 Kudos
Message 2 of 10
(4,330 Views)

Using LabVIEW, I had the same issues in that it would work intermittently.  For the most part, sending the commands work, it is just reading back from the scope that is the issue.

0 Kudos
Message 3 of 10
(4,327 Views)

Are you giving enough time to perform the reading?

 

You may have to perform some low command such as Initiate Acquisition then do a Fetch after the Acquisition Status has reported IVISCOPE_VAL_ACQ_COMPLETE.

 

With Max this uses VISA command not IVI and therefore has a timeout set as default 10s, which is probably long enough to do a standard measurement.

Regards
Ray Farmer
0 Kudos
Message 4 of 10
(4,315 Views)

I believe I am giving enough time for the commands.  What I meant was that I know the NI GPIB card is good, the cable is good, and the o-scope is good, it is just the o-scope just does not like the signals sent using either the LabVIEW LabWindows/CVI Measurement Studio for Visual Studio IVI or the LabVIEW Plug and Play driver.  The site takes me from the DSO5054A page to a 6000 series driver, although according to the description it should work with the o-scope.

 

http://sine.ni.com/apps/utf8/niid_web_display.model_page?p_model_id=10028

 

Using the above IVI/Plug and Play drivers, the DSO5054A reads the correct signal but unterminated, so it doesn't know what to do half the time.  In TestStand, I added in the initiate command and added a wait of 10 seconds, and when it doesn't timeout on the calibrate command it will timeout on the fetch/read command.  In LabVIEW, using the read single waveform.vi the GUI displays the signal from the o-scope about 10% of the time, while the rest of the time it times out with error code -1073807339.

0 Kudos
Message 5 of 10
(4,309 Views)

Hi There,

 

Try going to the Teststand IVI Examples (All Programs->National Instruments->Teststand->Examples->IVI->IVIStepTypes.seq). Save this example under a different name, then isolate the Scope sequence series and configure it accordingly. Do you still receive this error? If you could attach your sequence file using this example, it would be most helpful.

 

Regards,

Jackie

DAQ Product Marketing Engineer
National Instruments
0 Kudos
Message 6 of 10
(4,279 Views)

Using this sequence seemed to work for the simulation world, but when I changed the value to "simulate=0" instead of "simulate=1," the o-scope still gave me the error again of "Query UNTERMINATED."  The auto setup seems to work every time the configuration does, but the read/fetch function is still not working as it should.  I ran about 10 sequences back to back and I had two successful runs, while the other 8 either failed to configure, or failed to read.

0 Kudos
Message 7 of 10
(4,269 Views)

Could you tell us more about the signal, you are trying to measure ? Might it be that there are lags between the trigger conditions that exceed the 1s timeout, you are using in the fetch step  ?

And it might be helpful, if you could show us a NI-Spy log with the problem.

0 Kudos
Message 8 of 10
(4,262 Views)

You are also using the HoldOff so are you sure your signal is where it's supposed to be. make sure your trigger levels are correct.

Regards
Ray Farmer
0 Kudos
Message 9 of 10
(4,259 Views)

Hi there,

 

Have you been in touch with an Applications Engineer at National Instruments? If so, we will handle your questions through your service request.


Regards,

Jackie

DAQ Product Marketing Engineer
National Instruments
0 Kudos
Message 10 of 10
(4,250 Views)