tektronix dpo2024 error message -1073807339

[Willy0120]

Hi, Sir:

I got a problem when using Tektronix DPO2024 to scan.

The error -1073807339 happended when I scan many times.

Do you have any suggestion for this part?

[Gregory]

Are you triggering your oscilloscope? It might be waiting too long for another trigger.

I noticed you are using a queue to pass data around. However, you are losing one of the main benefits, which is that you can pass data to a parallel loop and view/manipulate it without slowing down the acquisition. To get your parallel processing going, you will need to make a second while loop with all of your dequeue element code in it.

[Willy0120]

---

gregoryj 已寫：

Are you triggering your oscilloscope? It might be waiting too long for another trigger.

I noticed you are using a queue to pass data around. However, you are losing one of the main benefits, which is that you can pass data to a parallel loop and view/manipulate it without slowing down the acquisition. To get your parallel processing going, you will need to make a second while loop with all of your dequeue element code in it.

---

Hi gregoryj

I didn't trigger the oscilloscope. Actually, I can scan at the beginning, after scan time is much than 200 or more, the error is random happend.

For the second point, you mean I can add one more while loop to use the data? How to do? I have no ideals.

[Gregory]

Hi Willy,

I am not sure what is going on with the oscilloscope. As far as the parallel loops go, I've drawn a little (non-functioning) snippet for you. Here is your program now (with all the functionality stripped out):

If you move the "Process/Save Data" portion to a parallel loop, you can have both things happening in parallel. It would look something like this:

There are many ways to stop the second loop. The way seen here (which I don't use in practice) is that an error will stop the loop. The error comes because the "Release Queue" function was used after the top loop stopped, and when the dequeue element tries to take an element out of the non-existing queue, an error will occur. In practice, I usually enqueue clusters with at least 2 elements, one element contains a command (like a string or enum) and the other contains the data. In this way I can command the bottom loop to perform an action, or to exit.

Look up Queued Message Handler (QMH) in the examples and on the forums for more examples on this technique.

[Kyle97330]

I've got two Tektronix 2014B scopes that I get that error on as well.

As far as I can tell, it just happens sometimes when using USB to download entire waveforms.  On other Tek scopes with GPIB or Ethernet I never get that error, and I never get it when I am doing something simple (i.e. quick settings changes or measurements are OK, it's just waveform downloads).

The only way I ever found to fix it was to rerun the initialize/reset VI and reprogram all of the settings back to where they were before the error.  This does take a fair amount of time.

[Dennis_Knutson]

How big are the waveforms and what do you have the timeout value set to? Have you tried increasing it?

[Willy0120]

---

Kyle97330 已寫：

I've got two Tektronix 2014B scopes that I get that error on as well.

As far as I can tell, it just happens sometimes when using USB to download entire waveforms.  On other Tek scopes with GPIB or Ethernet I never get that error, and I never get it when I am doing something simple (i.e. quick settings changes or measurements are OK, it's just waveform downloads).

The only way I ever found to fix it was to rerun the initialize/reset VI and reprogram all of the settings back to where they were before the error.  This does take a fair amount of time.

---

Hi, Kyle97330:

Thanks for your information.

I will try to use the GPIB interface to control.

[Willy0120]

---

Dennis_Knutson 已寫：
How big are the waveforms and what do you have the timeout value set to? Have you tried increasing it?

---

Hi, Dennis:

I already setup to the maximum timeout value. It can't increase anymore.

[Willy0120]

---

Willy0120 已寫：

---

Kyle97330 已寫：

I've got two Tektronix 2014B scopes that I get that error on as well.

As far as I can tell, it just happens sometimes when using USB to download entire waveforms.  On other Tek scopes with GPIB or Ethernet I never get that error, and I never get it when I am doing something simple (i.e. quick settings changes or measurements are OK, it's just waveform downloads).

The only way I ever found to fix it was to rerun the initialize/reset VI and reprogram all of the settings back to where they were before the error.  This does take a fair amount of time.

---

Hi, Kyle97330:

Thanks for your information.

I will try to use the GPIB interface to control.

---

Hi, Kyle97330:

I tested the program from USB to GPIB interface. The error message still happened radom.