Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

"Read Trace.vi" for Agilent U2042XA issues

Hello,

 

I am running a program fires a pulsed signal from a transmitter and it seems to always get hung in the Read Trace.vi that is in the agilent u2000 series library and I cannot figure out what the problem is.  I have gone through the programming guide for what settings have to be configured so there are not conflicts and I am not getting an errors on that front.  The issue is that this is their .vi and in the programming manual its using the "TRAC? HRES;" command, which as far as I can tell is correct, it matches the manual.  When I have the program step through each piece of that .vi it always gets hung on the VISA read right after it writes to it the resolution.  I have changed the byte count to a whole plethora of values including the return count when I query the sensor in MAX, which is 10 bytes, but 2 is what the .vi is set up for from their shop.  Does anyone have any experience with these particular sensors?  Is this a known issue or are there any work arounds to acquire a trace of the entirety of the pulses?  

 

The read trace is in a while loop right after a read measurement .vi and if I remove the read trace .vi it works as I assume it should(I have the glorious job of trying to figure out what someone else's program was supposed to do haha).  Everything that configures the sensor, triggering mode, acquisition modes, etc. etc. are all initialized and set before anything enters the loop and it looks good as far as I can tell when i query the device about particular settings once I stop the program.  Its just when it reaches the read trace, it dies.  I'm pretty confident I've narrowed down the issue to a configuration setting i'm missing that isn't allowing for the trace read to work but i'm at a loss otherwise.  Any ideas?

0 Kudos
Message 1 of 1
(103 Views)