i would like to know how to set up triger on pico so it will capture glitch such as crank signal failing and stop on that screen i am still learning.

---

kev g wrote on Jan 30^th, 2011 at 2:28am:

i would like to know how to set up triger on pico so it will capture glitch such as crank signal failing and stop on that screen i am still learning.

Kev

Why dont you try to let the power of the Pico sample rate do the work for you and add more time, then there is no need for the trigger.

Tom has gone to great lengths to help us by making tutorials.
you can access them by.

http://www.autonerdz.com/picokit.htm#_DOH!__I

Mick

---

Kev,

As Mick suggested, much longer capture times would be good.

As for trigger, while not needed for the capture itself, it sure can be handy to catch an unattended failure.  If the engine is stalling, you can repeat trigger off of any signal that will fail when the engine stops.  Therefore the scope will stop acquiring data when the engine dies.  

This allows you to capture the failure while you are at lunch.  The information will be waiting for you when you return.   ;)

thanks i will try that i have used long capture times i remember that the snap on modis does glitch capture and wanted to try it with the pico.

scope it from crank to start up,what Tranny is it ?

Thats some amplitude you have going off there ?

Kev,


Quote:

i remember that the snap on modis does glitch capture and wanted to try it with the pico.

The Modis has no ability to trigger a capture and therefore you could not do the unattended capture of a stall I described above with a Modis.

Perhaps you refer to Modis Peak Detect?  Peak detect does not increase true sample rate or the number of samples collected.  It just selects different samples to store in the buffer to help detect faster events that might otherwise be missed.  

Pico has so much power that peak detect features are not needed.

Tom Roberts wrote on Jan 30^th, 2011 at 7:39am:

As for trigger, while not needed for the capture itself, it sure can be handy to catch an unattended failure.  If the engine is stalling, you can repeat trigger off of any signal that will fail when the engine stops.  Therefore the scope will stop acquiring data when the engine dies.

This sounds like a very nice feature, unfortunately I can't figure out how to configure it. Could you please make a few more words on this?

Partyzan wrote on Feb 19^th, 2014 at 1:07am:

Could you please make a few more words on this?

Not sure more words would explain.  The tutorial videos do though.  Seeing it makes it so much easier to absorb.

Play with repeat trigger.  The scope only will acquire when the signal meets the trigger requirements.

this is such a nice feature of pico!  I tried it only now, because a manual doesn't note it fully:

"Repeat: PicoScope waits indefinitely for a trigger event before displaying data. It repeats this process until you click the Stop button. If there is no trigger event, PicoScope displays nothing."

Very important thing is not mentioned: when the signal is gone, the last buffer is left on the screen. I think they should add this to the manual of the soft :)

Anyhow, thank you Tom for one more good tip!