reading the data from TDS210

[rcarr]

Here is the screen shot of the read code and plotting code.

[BerkO]

Also one more thing, the driver you are using is the older version.  After the release of 8.0 we created a newer driver (better compliant of our current standards) which will graph a single channel for you directly.

Since you are using LV 8.2 I recommend using that driver instead of the old one.  You can find that driver here.

[BerkO]

Hi Rcarr,

You are correct, the scaling is not working properly at all, not only it requires you to initialize first (to turn on headers) the waveform that is plotted to labview doesn't match the scale of the scope.

Please get rid of that version and use the project style driver that I linked in my previous post.  Make sure you fully delete the old version driver because the default conditions for each are different therefore trying to use one and then the other will cause a lot of hard to debug problems.  I can certainly help you with other issues that arise due to changing the other parts which used the old driver.

I attached the screenshot of the code and you can see it here.

One thing to note is that before this code executes, make sure the scope has both waveforms properly scaled (run Autosetup VI if needed).

Please let me know if you have further problems.

Message Edited by BerkO on 04-18-2008 03:26 PM

[rcarr]

Thanks so much for your help. However, I am getting this error message when I try to run the program: Scan failed. The input string does not contain data in the expected format. Attatched are the screen shots of the code I used to set up the oscilloscope and the code to send the data to the computer. Any suggestions on getting rid of that error message? I made sure that I completely deleted the old driver before I installed the new one. Thanks in advance for the help.

[BerkO]

Hi Rcarr,

In which VI are you getting the error?

Can you watch with highlight execution and pinpoint which VI is giving you the problem?

[rcarr]

By highlighting the execution the error appears in each vi after the initialize vi. That happens in both frames.

Message Edited by rcarr on 04-22-2008 11:00 AM

[BerkO]

Hi Rcarr,

I couldn't reproduce the problem and the driver seems to be working properly (I tested with two square signals and got the correct XY graph and waveform outputs).
Now you are initializing a second time in the second sequence frame and that might be the problem, usually serial doesn't want to make it easy for you and it might at weird situations.  Since you are initializing and configuring the instrument in the first frame,  you won't need to do it again, just passing the resource (and possibly the error line as well) would be sufficient.

Please refer to the screenshot for what I mean.

Let us know if this helps.

[rcarr]

Thanks BerkO. Attatched is the vi with the new driver, and coding based on what you have shown me. I am still getting that error:(. I have even made sure that my serial settings match. Somehow I don't think my RS232 wants to cooperate.

Message Edited by rcarr on 04-22-2008 02:23 PM

[BerkO]

Hi Rcarr,

I ran your code directly too and it seems to be working (excluded the part that didnt relate to the scope).  Please try and power cycle the instrument first, then make sure it responds properly to the IDN query in MAX.  Then run your VI.  I have seen cases where data was left at the output port of the instrument (parts of the waveform data for example) and even if you send in new queries, it wouldn't stop sending out that data first and then it would respond to the next command that was passed.  This would cause a problem when scanning for certain patterns in the output.

If starting from scratch doesn't solve the issue either, can you please pin point the exact location (which VI, which scan from string function etc.) and see what is going into the function (with a probe or an indicator on the input to the function).  As far as your current code, it seems to be working.

[rcarr]

I have attached a screen shot of where the error occurs in the coding. I hope that helps in clarifying the error message that I am still getting. Thanks again for the help.