Keysight 35670a Digital Analyzer Start Action VI

[Pchrostoski92]

Hello,

I am trying to use the agilent/keysight 35670a dynamic signal analyzer with labview 2012. Labview sees and recognizes the device using gpib, but when my program or even the driver example program gets to the start action the program stops in its track and then when I try to stop the program labview stops responding.

I am not sure why this is happening as no error message comes when I run the debug. Any help on this would be great

Thank you,
Phil C

[BennyBenson]

Have you tried communicating with the device in NI Max?

[Pchrostoski92]

Yes and NI Max has it there. It is currently my only GPIB device. What I noticed digging deeper the visa write function in the start-stop action VI looks to be timing out. I am not sure why.

[BennyBenson]

Which driver example program are you running? Could you post it?

[Pchrostoski92]

I am using two different VI's one that i wrote and one of the examples with the driver they are both timeing out at the same spot.

The example VI is the Averaging FFT vi attached. The other VI is the is my example VI attached. They all stop at the Start Measure Command VI (A picture of this exact VI is attached). When i looked deaper it was getting caught up at the start stop action (picture attached in second reply). Then finally i looked deeper into that and the visa write looked to be timing out (picture again attached in second reply). I am able to choose my keysight 35670A as the resource name to send through everything. But i guess when it wants to write to visa name it is timing out. All the commands go to the actual digital analyzer, but labview times out.

Thank you for taking time to try and help me.

[Pchrostoski92]

attaching the last two images of the VI's i mentioned in my last post.

[BennyBenson]

You mentioned that you could see the device in Max, but have you actually attempted to communicate with the device or read anything from the device. Basically, I just want to be sure that you can correctly address the device in Max, just to be sure it's not a driver or hardware issue.

[Pchrostoski92]

I tried using MAX to communicate using the command *IDN?. Then reading from the 35670A. I get an error iberr = EABO. From what I am reading this is due to a timeout condition when doing a GPIB read.

[BennyBenson]

Do you receive this error when trying to query or write to the device?

Possibly read over this document. http://digital.ni.com/public.nsf/allkb/A80DBFCCAC36EBDE862562C80058856E

[Pchrostoski92]

It would be when I try to read from the device, it works when I query from the device. Will preface I am not too experienced using NI MAX to communicate with a device