There are some ways to speed up the code, but it's highly unlikely that you will be able to "stream" all data to the pc from the scope. If that's your goal, then you should look at scope internal storage options. Your code would trigger the measurement to run for N seconds, saving all data internally on the scope. Once the measurement completes then you can download the data from the the scope and do post processing.
If you need real-time capture of one point on a trace then look at the "marker" functions. You can usually get a single marker reading buffered to internal memory back from the scope
As it stands your code is trying to download and save two trace 22500 each. Transferring 45000 pts takes time, saving that data to a file (which you open/write/close every loop) takes time, sending commands to scope to read data takes time. During all those little delays the scope is capturing data which you will miss.
A few tips to speed up what you showed.
- use shift registers to save data and only write data after the loop ends (faster, but could be memory limited)
OR
- open the file before the loop, close the file handle after the loop and only write data during the loop (slower but not saving big volume of data in memory)
- don't update a table in the loop, don't update the chart in the loop.
On another note..
- Saving a data file with an array of points from the Get Date/Time seconds doesn't seem like what you want to do. If you want to save the trace data with a timestamp to be able to replot your signal versus time later, then you need to get the time base settings from the scope and calculate the time based on that increment between points. Or just save the trace and rebuild the timestamp in what ever analysis software afterwards.
Give these suggestions a try and let us know how it goes.
Craig
