G'Day Guys,
First up ... Good to see Tom initiate this 'diagnostic game' and the great participation by forum members so far. This is 'what it's all about' and I'm sure each and everyone of us will benefit somewhere along the line.
Not only Pico capture techniques, captures interpretation but also diagnostic methodology could also be discussed during the 'diagnostic game'
For the purpose of keeping things relatively simple, let's use the capture and the vehicle it was obtained from, as a sort of 'general guideline' if you like, to the Pico useage, screen capture interpretation and possible diagnostic strategies in this
particular instance.
As with any diagnostics, something should be known about the vehicle symptom or symptoms and the vehicle ignition, fuel and air systems.
This particular vehicle is of our local production/consumption, but I'm sure many of you can relate to it with ease.
THE SYMPTOM : service R/O was written thus - " runs roughish and lacks power "
mmmm ... front desk needs some educating me thinks!
Vehicle general info:
300,000km on speedo
In line 6cyl - firing order 153624
external modular coil
optical ignition - cranksensor 120° and 1° signals
multiport injection - current controlled injectors
2 x fuel pumps ( intank pre pump, external pressure pump )
Bosch Hot Wire Air Mass sensor
3 wire heated O² sensor
No EGR system
No data stream - DTC's only available
I approached this firstly by
confirming the symptom before attempting diagnostics/analysis.
Confirmation of the symptom proved out.
Bad multiple mis-fires and poor performance.
A check of DTC's showed 1 stored - 14 (speed sensor )
I chose to connect the Pico and sample the tailpipe emissions with the 5 gas analyser with the thought that the two could support my initial 'confirmation of the symptom' as a possible fuel related issue.
I chose Kv parade to give me an overall view of
all the cylinders and the 'effect' of the symptom.
As most of you have ascertained, the capture is showing a ' leanness' issue during combustion and it pertains to all cylinders.
The capture shows the effect but not the cause.
What would you do next?
With regards to the cylinder Kv's in the capture .. Tom has quite rightly noted that the initial higher Kv normally seen with 'lean' during a snap throttle was missed because of my scope settings.
What could/should I have done during initial scope setup before the snap Kv throttle test?
Would using the ' Save On Trigger ' scope function have caught the event?
Would you have approached the symptom with a different diagnostic/analysis strategy?
I won't provide the answer to the 'effect' of the fuelling issue just yet, but, the 'cause' was multi - layered

Cheers!
Kevin