markz wrote:WHATS BEEN LEARNT
Ok.. so instead of 2500 samples per scope trace.....I should be setting it to 32000 samples per scope trace. That explains where all the missing events went!
Yes, when you want the higher sample rate and more resolution. This will slow the screen update rate though so, if you do not need the resolution turning it down will speed things up. When capturing something as fast as a secondary firing line your 212/3 will begin to break down at 10ms/div.
Let's do the math for the 212/3:
32,000 samples / 100ms = 320khz requested sample rate
The scope then chooses 187.5khz since 320khz is between ranges.
187,500 samples x .00001 firing line duration = 1.9 samples maxed out.
This will show most of the high peaks. Longer time basses will not. You can overcome this by using the mix/max and current selection which will leave shadows of the minimum and maximum values for each trace while showing the current trace as it is updated. Just a few passes and you will reliably see the high spike shadows on the screen. You may have to update your software to get that feature but it's free
markz wrote:No. 2
For those of you who can set the "Max readings per sample" in an older version of picoscope software between 1 and 16, choose 1 for automotive work.
markz wrote:WHAT REMAINS!
What is this ETS feature..I believe you can set it between a value of 2 and 5, and also there is a slow and fast mode.
Could someone explain if and how these can affect our ignition waveforms? What should we be setting them to.
Don't use this feature on an automotive application. This is for very fast repetative signals. The scope takes a few passes then constructs the waveform from the data. We don't deal with steady repetative signals so this would only serve to distort the picture.
markz wrote:Also...there is another setting in the win.ini file... I think it is "No of times to update display" or something like that ( i am not at my pico pc!). I think it is set at 10 on my pc.
Screen Update Rate? Maximum is 30 screens per second. I leave mine maxed at 30. It will be considerably slower than this dependent on the time base and the number of samples. It can make the PC pretty busy so if yours seems to lock up and get unresponsive to the controls, turn it down a little.
Hope this helps