I would love to be able to set two trigger points for the same channel on the pico screen, so I could mark the four strokes and be able to use first look sensor on the tail pipe and identify misfires live. This could also be used to view in-cylinder waveforms live with divisions (Like the ATS Emmisfire scope).
Last edited by JorGdiondo on Wed Jul 13, 2016 12:36 am, edited 1 time in total.
I don't think you need two trigger points for what you have described - but if I haven't understood the exact need, please just post again.
You have two sets of rulers with PicoScope (time on the bottom left, and degrees rotation on the bottom right).
You can use those to bracket and mark the four strokes.
Another trick some of our guys have used is to use the zoom feature to fit the four stroke cycle over the background graticule. For live display though, the use of the PicoScope rulers should give you everything we need, and there are some nice case studies on our site using WPS500X that illustrate that, and focused on different techniques for misfire:
I'm just saying that rpm changes would be accounted for, if two triggers(drawing in the same place) were used for LIVE analysis, not after the fact (where of course you can mark 720 degrees and divide or zoom in).
Last edited by JorGdiondo on Wed Jul 13, 2016 12:50 am, edited 1 time in total.
JorGdiondo wrote:I'm just saying that rpm changes would be accounted for, if two triggers(drawing in the same place) were used for LIVE analysis, not after the fact (where of course you can mark 720 degrees and divide or zoom in).
Here's an example (if I figured out how to post an image):
There is presently no 'live' facility in the software to organise the X axis to cover say 720 degrees of a repeating signal as you have described.
It is in the ideas that we have discussed, but is not yet planned as we have been working through many other feedback requests and product improvements. It is always difficult to decide which features to add, and hence the reason we do value the comments, suggestions and requests from our users.
I think for now you will have to continue to use the non-live facilities and set the timebase to suit the RPM range of interest.
PhilS wrote:
It is in the ideas that we have discussed, but is not yet planned as we have been working through many other feedback requests and product improvements.
I guess it would be kind of difficult to automatize the time base for that, but maybe make the pico cursors follow both triggers? It would be a great feature and one would not need ACE Misfire or ATS (ACE sometimes mis reads wich cylinder misfired, and I would like to see the signals myself in an orderly fashion).
Just an idea.
Thank you for your prompt response, and keep up the great work.