tektronix tds3000- acquisition fail

[araaz]

Hi All,

I am trying to connect tds3032 oscilloscope to fetch data and measure some parameters. But, the connection is not helping at first place. It seems, installed labview in my computer is able to read the GPIB address, but it is not able to run any vi. I was only trying to run the example VIs come with the driver. Please find below the snapshot of the error I am getting. 

N.B: I have tried with 2 GPIB as well as in two computer. The program is itself not written by me, but the example vi that is included in the driver. I am assuming, the problem is with the oscilloscope only. Please let me know your if you have encountered the same problem and your advise and suggestion on it,  ASAP, as I am working on this.

Thanks,

Akhtar

When I click on continue, it is showing some undefined error code.

[Dennis_Knutson]

That's an error coming from the scope itself. Check the manual for the error description to see off there are any details. Check with Tek as well. You could narrow down the source of the error by seeing which function actually causes the error.

[araaz]

errorquery.vi is causing the error. I have run each and every individual subVI within that VI, and each of them is running normally. But I am getting the error, when I am trying to display the graph, and when I am trying to run the errorquery.vi subVi, it is returing

241: Hardware missing

0:no events to report- queue empty.

[nyc_(is_out_of_here)]

---

@araaz wrote:

errorquery.vi is causing the error. I have run each and every individual subVI within that VI, and each of them is running normally. But I am getting the error, when I am trying to display the graph, and when I am trying to run the errorquery.vi subVi, it is returing

241: Hardware missing

0:no events to report- queue empty.

---

You don't understand the words Hardware missing ?

Apparently you are trying to make a measurement with a HARDWARE option that your scope does NOT have.

[araaz]

But I have connected the oscilloscope to my computer, the driver for that scope is installed and the program also reads the GPIB address successfully, so I am not understanding what hardware I am missing. Sorry, but I am very new in the field of labview. So I am not understanding what is it implying with the message "hardware missing"

[nyc_(is_out_of_here)]

blindly using drivers

now you'll actually have to understand how to use the instrument

http://www1.tek.com/forum/viewtopic.php?f=5&t=386

[Dennis_Knutson]

You simply don't understand. The error query checks the scope with an ERR? query and if the scope says it had an error, it creates a LabVIEW error and reports what the scope says. One of the functions causes the error and you need to find out which one. Perhaps there is s missing option that you did not purchase. Perhaps a vertical or horizontal setting its not present on your model of scope. The point being that you need to understand the scope and isolate where the problem occurs. Each function in the example can be run by itself and after each function, you can call the error query function.

[mcduff]

The Example VI that he is using seems simple enough, just a channel query & data from the scope. Not sure why it would say hardware missing. He is not taking a FFT or anything special from his screen shots. I suggest to turn on execution highlighting and see exactly where it fails. cheers, mcduff

[nyc_(is_out_of_here)]

---

@mcduff wrote:
The Example VI that he is using seems simple enough, just a channel query & data from the scope. Not sure why it would say hardware missing. He is not taking a FFT or anything special from his screen shots. I suggest to turn on execution highlighting and see exactly where it fails. cheers, mcduff

---

How can you tell anything with a front panel that it is "simple enough"?

The Block Diagram is what counts.

[Dennis_Knutson]

It is simple and if I had to guess the missing hardware would be the specific timebase setting. It's a driver for all models in the series. The point being though that no one should have to guess. Running the error query after each function call is necessary if each function call does not call the query itself.