LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Agilent Technologies 2000 3000 X-series Driver Example Timeout

Solved!
Go to solution

I am running the example VIs, "Acquire Waveform.vi" and "Acquire Waveform Continuously.vi," that come with the Agilent Technologies Oscilloscope driver "Agilent 2000 3000 X-series."

 

While my issue and attempts at dealing with it are detailed in the attatched pdf, I will outline them here. When I run either of these example VIs, the initalize the scope without error, and they succesfully run the Auto setup VI, but whenever the VI attempts to read data from the scope, it exceeds the maximum allowed time for any reasonable value I input. I get the following error:

 

"Error 1073807339 at VISA read in Agilent 2000 3000 X-series.lvlib: wait for acquisition complete.vi->Agilent 200300 X-series.lvlib: read wave forms (single).vi-> 2000 3000 X-series Acquire save forem.vi

Possible reasons: VISA (Hex 0xBFFF0015) Timeout expired before operation complete"

 

I ran the VI with several inputs for maximum time, starting from 1ms and working my way up to 1,000,000ms. I get the same error for all of these except the longest time, in which case the error reads "The connection for the given signal has been lost" (not surprising, 16 minutes is a long time)

 

Additionally, I have to power cycle my scope to regain control after running this VI. I assume (hope) that this is a related issue and once the VI no longer times out, the scope will function normally.

 

I have looked through the existing forum posts related to this and found a few that weren't close enough or weren't answered satisfactorily, however, if you think I have missed something in that regard, please feel free to tell me or post a link to that particular thread.

 

Any tips tricks and advice would be greatly appreciated and kudos will be given to helpful posts.

 

Other information:

Labview version 13

VISA verions 5.4

OSX verison 10.7.5

 

Link to driver:

http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=9E84674573AF6AB8E0440021287E6A...

0 Kudos
Message 1 of 13
(7,095 Views)
It's unclear to me whether the *IDN? command of working for you. The initialize function has a Boolean control to request it. It's also unclear whether or not the scope has a waveform displayed when you attempt the acquisition. If the screen is blank, then s timeout makes sense.
Message 2 of 13
(7,064 Views)

To clarify, the scope triggers and displays a waveform as expected during the VI, but the waveform does not display on the front panel of the VI. 

 

When the VI finishes running, I do not get control of my scope back.

0 Kudos
Message 3 of 13
(7,058 Views)

Additionally, the Initialize VI does not output an error. The error is generated from a different VI. I realize this doesn't exclude the initialization as the problem, I just want to clarify. Is there a way I can verrify the ID Query? I seems as thought this is buillt into the VI.

0 Kudos
Message 4 of 13
(7,056 Views)
Thanks. You don't have a complete communication failure then.

I know I've used this scope and driver without any problems but the interface was probably GPIB. The USBTMC driver is supposed to emulate the GPIB protocol. I don't know if the issue is with agilent's implementation or something else. I would first make sure you have the latest driver and firmware from them. I would then try it on a Windows machine. Maybe someone else has other ideas.
Message 5 of 13
(7,040 Views)

I will continue looking into what you've mentioned, and try on a different machine. 

 

FYI, I have also tried this on a PC to the same affect, although my verison of Labview and VISA were quite old on that machine.

 

Further help from anyone else who has an insight would be appreciated, still. 

 

Thank you.

0 Kudos
Message 6 of 13
(7,036 Views)

I ran the VI on a PC running XP using Labview 2013. Same error. I'm currently downloading a newer version of VISA on that machine. I'll post those results as soon as I've run the VI. 

0 Kudos
Message 7 of 13
(7,024 Views)
Solution
Accepted by topic author asachs
I don't think the problem is with VISA but this can't hurt. I still suspect the instruments firmware.
0 Kudos
Message 8 of 13
(7,010 Views)

Oh, pardon me. I misunderstood you. I am updating the firmware now.

0 Kudos
Message 9 of 13
(6,986 Views)

It worked. Thank you so much, Dennis! You've been a great help.

0 Kudos
Message 10 of 13
(6,982 Views)