PicoScope 7 Automotive
Available for Windows, Mac, and Linux, the next evolution of our diagnostic scope software is now available.
Moving on a little from Arjen's input regarding crankshaft rotational speed (acceleration) after a firing event, this has intrigued me for some time as this is the method by which misfire detection is calculated. My line of thinking here is that if the PCM can see an acceleration in the rotational speed and calculate a percentage of misfire, then so should we using the scope. Here again is where I am at a loss and would value any input. I have attached a psdata file looking at CAM-CRANK-CYLINDER PRESSURE-IGNITION PRIMARY NO.1 cylinder. Moving along to next ignition event after NO.1 cylinder (identified by time rulers) I have added a maths channel to channel A measuring frequency which you might expect to see increase momentarily after the ignition event whilst on the power stroke, but the data does not support this theory!You have set wheels in motion in my head again and so I will try to capture a vehicle on site where by we can assess the compression waveform in relation to Cam and Crank correlation.
Thanks again for the input
It's a trick I often use when looking for miss fires. Personally I would have more time on the screen and then multiply the maths calculation by X amount vertically. It's another feature I would like to see Pico adopt.Here again is where I am at a loss and would value any input. I have attached a psdata file looking at CAM-CRANK-CYLINDER PRESSURE-IGNITION PRIMARY NO.1 cylinder. Moving along to next ignition event after NO.1 cylinder (identified by time rulers) I have added a maths channel to channel A measuring frequency which you might expect to see increase momentarily after the ignition event whilst on the power stroke, but the data does not support this theory!