LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

tektronix

I am having a problem with changing the settings on my tds 2024b while I am acquiring my signal. When I put the settings in the while loop to change them while I am aquiring my signal it does not aquire the whole signal only a really tiny piece. I need to be able to operate the labview code like I am operating the oscilliscope but only on the computer. Someone pls help

0 Kudos
Message 1 of 15
(3,669 Views)
You can't do that programmatically. You must wait for the data to be completely transferred. Otherwise, the instrument will report a 'query interrupted' error. I can't look at your VI since I am posting by phone.
0 Kudos
Message 2 of 15
(3,651 Views)

You need to allow the oscilloscope time in order for it to capture the signal.  Therefore, you should probably add a wait after setting it to run mode to allow for the trigger and the waveform to be fully captured before asking for the waveform.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
0 Kudos
Message 3 of 15
(3,638 Views)

I tried the wait vi for the program but for some reason it didn't work, I put it inside the while loop

0 Kudos
Message 4 of 15
(3,610 Views)
What sort of wait? Are you now waiting for the data transfer to be complete before changing the settings?
0 Kudos
Message 5 of 15
(3,603 Views)

I can't see your code because I don't have the latest LabVIEW, but from the quetion and responses, I gather you are using the Tektronix flavor of SCPI.  I believe Tektronix supports the *OPC? query so you can use that instead of a hardocoded wait.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 6 of 15
(3,591 Views)

just the wait until next multiple, that way if I get to end of the scope processing time it will work for the next multiple so I can aquire all the signal in any given time frame. I was thinking of putting a timed loop of sorts for my changes with the oscilliscope

0 Kudos
Message 7 of 15
(3,587 Views)
None of that seems like a reasonable solution. It's the acquisition times are fast, a cheap way is to put the acquisition in a timeout event of an event structure and the controls in their own events. A notifier in the acquisition loop would tell the loop with the controls that it can write. In any case, you have to do things sequentially since that is how the instrument and GPIB is designed.
0 Kudos
Message 8 of 15
(3,582 Views)

the configure channel vi comes before the actual signal, how would I give the signal enough time to aquire then be able to change the settings afterwards?

0 Kudos
Message 9 of 15
(3,565 Views)
Besides the two approaches I already said, you could use a state machine.
0 Kudos
Message 10 of 15
(3,560 Views)