The number that actually occurs depends on a few things, including the timebase that is selected. The idea of specifying in the software means that the software can then "aim" at getting this number of samples. It may not be able to get exactly that number however. The maximum in all cases is the size of the buffer and the number of active channels also needs to be taken into account.
The calculator assumes that you are using the buffer value that you entered.
PicoScope changes its data acquisition at 200ms/div to a streaming mode and no longer used the internal memory in the ADC unless you are set to Block Mode under Settings/Options/Advanced. At 100ms/div and faster it's using Block Mode regardless.
In streaming mode the data is not stored in the buffer but streamed to the PC during the screen time. This rate varies from PC to PC and can be affected by the PC performing other tasks at the same time. My PC streams at 500s/sec with PicoScope 5.
At 5s/div, Block Mode no longer functions and you will stream regardless of the settings. This makes sense because now you will likely collect more samples streaming than you will using the internal buffer.
So, the reason that the calculator doesn't match your results is that you are streaming rather than using the buffer. The calculator will be very close to actual if you are using the buffer in Block Mode. It will be a few samples off sometimes due to complex scope operational variances, but very close.
Hope this explains.
Tom Roberts
(The Picotologist) http://www.autonerdz.com
skype: autonerdz
THE PicoScope Automotive Authority
In North America
When using Block Modes regardless of time domain, the scope interprets the best sampling interval from the number of samples you require and the total time to collect samples in. The fastest sampling rate is 20Ms/Sec. Each sampling rate is half the previous one working backwards:
20Ms
10Ms
5Ms
Etc...
When you move into longer timebases the scope will have to choose between 2 very different sample rates. At the 2 sec per div and slower, you will notice a difference in the total number of samples collected. It may even appear that the buffer is not being totaly utilised.
To bridge this gap, we have written a fast streaming mode to stream data upto 3Ms/Sec straight down the USB pipeline. Currently, this mode is only available to programmers who write programs with our drivers. Application support will follow in due course.
I hope this helps you to get the most out of your scope.
Best regards,
Michael
Michael - Tech Support
Pico Technology
Web Support Forum
Impressed, eh? If you knew my obsession with trying to spot the pattern between requested versus achieved capture counts, you'd probably be sending in the Nice Young Men In Their Clean White Coats...
Luckily you don't know how many hours I've spent, repeating trial runs, trying to become competent, confident and "fluent" with this new tool. Not just with this question of capture size, but with most other aspects too. But the breakthrough evades me. I don't want to stay a simple-minded user, relying only on basic features.
Even trying to use only the basics, I go back to the broken car, patiently reconnect the test wires, and fail, fail, fail to execute the intended plan; fail, fail, fail to capture the set of traces that I need: flummoxed by the sophisticated tool that does something that I didn't expect, in response to a "trivial" change.
Back on topic: the Sample Rate Calculator is really neat and will help me to overcome this example of deficiency in the documentation.
My second thought: why isn't the Sample Rate Calculator built into the software?
My third thought: is something back-to-front here? Since capture size and sampling rate are (IMO) so important, why bury then in the background? -- Question for Michael
My second thought: why isn't the Sample Rate Calculator built into the software?
Under measurements you can select # of samples. Think you already discovered this. So we kinda already have a samples calculator built in.
Here at Autonerdz, we designed the calculator to help compare the raw sample rate performance of different instruments. By analyzing the performance, techs won't waste time comparing features of scopes that can't perform. Or worse, buy something that can't perform. The calculator is included on our training CD set "The Nerd Series"
You might like this. Not only is it the quantum leap forward in the software we have been waiting for to make full use of the 3000 series automotive scopes, you can put the samples selection menu right in the tool bar. In addition, the streaming is mega faster. I have collected almost a million samples per channel with it with minutes of complex data on a single screen. This is new ground for scopes and even in this beta stage, it's already beyond that which has ever been done
Tom Roberts
(The Picotologist) http://www.autonerdz.com
skype: autonerdz
THE PicoScope Automotive Authority
In North America
Tom is right, perhaps you need to consider PicoScope R6.0. The performance of this version outstrips many of the features of our PS 5.0, and even some it will not be able to support.
Active sampling rate calculator is on the wanted list of widgets for PS 6.0. We will get there. Until then, I recommend using Toms' calculator and working from the sample count in the measurements. As I mentioned before, the scope determines the best sample interval. At longer timebases this will vary greater than at shorter timebases. Hence the fast streaming modes in PS 6.0.
Also, the Nerd series offers an excellent training package and should be considered by anyone working in the automotive sector.
Best regards,
Michael
Michael - Tech Support
Pico Technology
Web Support Forum
I have read the new manual, looks good. It covers a lot of improvements.
I'm having a bit of trouble with the installation because it keeps wanting me to go back on the internet, but I have to swap out the network card to put in the USB 2.0 card.
Should I just leave the network card in until the end and then substitute the USB card?