Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

Problem with Agilent scope 54622a reset command in LabView 6.1 instrument driver

I'm trying to use ag5462x.vi with LabView 6.1 and when I start an aquisition I cannot avoid in any way to get the scope resetted to the factory default settings. In no way I can transfer the "no reset" info from the Initialize_with_options.vi to other subvis. I'm not an expert with LabView, so any possible help will be appreciated.
Yours sincerely,
Federico Rocchi
0 Kudos
Message 1 of 4
(3,628 Views)
Hi,

Try the ag5462x Reset.vi under the Utility subpalette of the instrument driver. This should be the reset function used by the initialize function.

DiegoF.
National Instruments.
0 Kudos
Message 2 of 4
(3,628 Views)
Hi Federico,

You are using an IVI driver and the behavior you are seeing is expected. Since the IVI specific driver performs the state caching, range checking, interchangeability checking and so on, it needs to start with the known valid settings.
Why is this a problem for you and what exactly you want to achieve?

Thanks!
0 Kudos
Message 3 of 4
(3,628 Views)
Hi gagi1,

thanks for the message and for the help. What I'd like to do is to acquire a waveform with signal triggering with a specific sec/div and a specific Volts/div. So I set on the scope the values I'd like to have, and run the vi. But as soon as it starts I see these values resetted to those defaults loaded in the memory of the scope by the manufacturer, changing then the scales. Moreover I cannot increase the aquisition time to values higher than 2 sec; if a higher value is set a timeout error occurs. In fact if I could change that value I could leave the very small default sec/div of the apparently unavoidable resetting procedure, rescaling the waveform after the aquisition. What I cannot really understand is why I have the option "No reset" in the
Initialize_with_options.vi and then, independently from the choice I'd like to have, the scope is resetted in any case. I hope to have explained my problems well, because, again, I'm not an expert with LabView. Any possible suggestion, clue or idea is really welcome. Thanks again,
Yours,
Federico Rocchi
0 Kudos
Message 4 of 4
(3,628 Views)