PicoScope 7 Automotive
Available for Windows, Mac, and Linux, the next evolution of our diagnostic scope software is now available.
|Honda Civic FK2 (8th generation)
While the future may be “Electric” the internal combustion engine (ICE) has many years left before it disappears forever. However, I am certain that it never will. Looking at the current legislation, 2030 will see conventional petrol and diesel cars/vans banned from sale with an extension to plug-in hybrids until 2035. (Used cars will be unaffected by the ban).
If we do the maths on the above, the ICE will continue to be present in various vehicles up to 2035 along with a multitude of vehicles going back to 1886. Needless to say, that is a lot of engines with potential for diagnosis and failure. The following case study looks at the application of PicoScope and the NVH software when tackling a typical engine noise and consequential failure.
The customer reported that the vehicle would not start when the fuel level was low! A breakdown service was called, fuel was added and the engine started. The following day the engine failed to start again and so the vehicle was promptly recovered to the garage for diagnosis.
Verifying the customer complaint is an essential step in the diagnostic process, but it is quite often a time-consuming task without success. On this occasion, we verified the customer’s complaint as the engine would crank but failed to start even with a sufficient fuel level displayed on the instrument panel.
With continual cranking at wide-open throttle, the engine would eventually start. It ran unevenly at idle speed accompanied by a rattling sound, a sulfur smell from the exhaust, and failure to free-rev beyond 2100 rpm. Getting the engine up to 2100 rpm required coaxing of the gas pedal. The rattling sound from the engine would, however, improve above 1500 rpm.
N.B Periodically during cranking, the engine timing would appear over-advanced with momentary laboured cranking and ‘popping’ via the intake.
You can find an audio recording of the engine start-up symptoms here.
With the customer’s complaint verified, we confirmed the Vehicle’s ID and Specification.
Confirmation of specification is of the utmost importance when it comes to diagnosis. There is often a temptation for customers to modify their vehicle with fashionable accessories that lack the fundamental quality control and engineering that was intended for the vehicle. The customer confirmed that no such accessories had been installed.
The Customer Interview followed the four targeted open question principle to establish facts from fiction:
1. How long has the problem been evident?
No previous experience of a non-start event or an engine running problem until the initial call out of the breakdown service.
2. When did you first notice the problem?
The symptom occurred twice in the space of two days leaving the vehicle immobilised and requiring recovery to the garage on the second occasion.
3. Has any work been carried out on the vehicle recently?
No. The vehicle was a recent purchase with no previous history.
4. When do you experience the problem?
When attempting to start the vehicle, once started the engine would continue to run.
Quite often, the customer interview leads to a "probable" diagnosis and my line of thinking here was a mechanical engine timing issue, based on the lack of vehicle history, the high mileage, and the rattle from the engine at idle accompanied by popping via the intake.
In the Basic Inspection, we confirmed that there were no fluid leakages, no visible signs of damage to hoses, connections, and wiring harnesses and no sign of that favourite discovery; accident repair.
A vehicle scan of all onboard control units revealed only three fault codes stored within the Air conditioner ECU and none of them related to engine performance! Live engine data at idle speed did however reveal a fluctuating intake manifold pressure of 0.53 bar (absolute) which was no surprise given the unstable idle and intake popping.
Before diving deeper, we took a step back and checked for Technical Bulletins (Recalls & Campaigns etc.). This is paramount. The most efficient route to qualify the presence of “known issues and fixes” etc., is to use the manufacturer technical portal combined with the vehicle chassis number.
While this may seem obvious, there are a number of avenues to obtain free technical bulletins and “known fixes”! I have learned that while the entire description of such obtained data matches the exact symptom you are experiencing, the information obtained may well be for other markets i.e., not applicable to UK specification vehicles. (Please don’t fall into this trap as I have with previous vehicles).
• Contaminated or incorrect fuel supply
• Ignition and fuel timing control
• Mechanical engine timing error
• Valve train control error
The action plan was predominantly governed by accessibility, probability and cost.
Contaminated or incorrect fuel was quickly eliminated with a fuel sample taken at the injector rail. Everything checked out here.
Based on the acquired scan data, I was leaning away from ignition and timing control errors as the engine performance improved above 1500 rpm and no related fault codes had been stored.
A valve train control error was possible but requires intrusion. Therefore, the focus was on the integrity of the engine’s mechanical timing.
1. Difficulty in starting the engine with laboured cranking
2. Unstable idle speed
3. Failure to willingly free rev
4. Popping sound via the intake
5. Rattle from the engine at idle
Arguably, the least intrusive way to verify mechanical engine timing is to carry out a cam and crank correlation test as discussed here. This test will include dynamic timing errors caused by worn camshaft drive belts, idlers and chains, etc. The below waveform is quite complex and has a lot to digest. This is because I also introduced pressure pulse analysis with the Pico WPS500X pressure transducers.
The first step in the analysis required focusing on the correlation between the crankshaft (Ch A) and the camshaft (Ch B) signals. Here, I had chosen the final falling edge of the crankshaft sensor engine position reference signal (two teeth in close proximity to one another) and the first falling edge of the camshaft sensor signal thereafter, which equated to 59.88° of crankshaft rotation or indeed, two teeth of the crankshaft pick-up.
The next step was to access the waveform library for a known good correlation capture as described here.
The waveform below is a known good comparison downloaded from the waveform library. Thanks to sennis201, wherever you are, for uploading and sharing this.
We used the same measurement points and could clearly see that the crank and cam correlation is different at 110.4° of crankshaft rotation or four teeth of the crankshaft pick-up. From this, we could now conclude that our camshaft timing was advanced!
Because I had included a pressure transducer into cylinder 1, the intake manifold, and the exhaust tailpipe, we could verify the above conclusion by looking at known events in the 4-stroke cycle.
The waveform above shows the 4-stroke cycle exhibited by cylinder 1, leading to the following analysis:
• The exhaust valve open event (EVO) was advanced from the typical opening point of approx. 155° ATDC of the compression stroke
• The exhaust valve close event (EVC) was advanced from the typical closing point of approx. 365° ATDC of the compression stroke
• The inlet valve open event (IVO) was advanced from the typical opening point of approx. 355° ATDC of the compression stroke
• The inlet valve close event (IVC) was advanced from the typical closing point of approx. 620° ATDC of the compression stroke (hugely variable depending on engine design and VVT)
• The popping noise via the intake was caused by the 1.5 bar pressure held in the combustion chamber due to the advanced closing of the exhaust valve. Therefore, when the intake valve opened the pressure would escape back into the intake manifold
• Our fault condition was affecting all valves on cylinder 1
There was most certainly enough evidence to remove the timing cover and inspect the mechanical valve timing of this single overhead camshaft, chain-driven engine. However, could we apply another non-intrusive technique, using NVH, to link the rattling noise emitted from the engine to our valve timing error?
In the image below, you can see the setup where we used an NVH microphone and accelerometer to capture a recording of the vehicle when starting and running at approx. 1000 rpm (the engine was too unstable to run at idle). The microphone captured the airborne noise generated by the engine while the accelerometer captured the structure-borne vibration and noise from inside the timing cover.
In the screenshot above, note the “spike” formation of the data in the signal history. This indicated instantaneous high energy peaks present for a very short period of time. Consider these spikes as momentary “strikes” attributed to combustion.
N.B. The audio recording at the start of this case study was taken from this NVH file using the audio export feature discussed here.
We can view these “strike” events with improved resolution in the NVH Time Domain view below. The accelerometer has captured approximately 18 periodic strikes in 1 second which equates to a first-order engine vibration at E1 (18 Hz x 60 = 1080 rpm).
At this stage, we have captured the noise and vibration “signature” from our engine in order to qualify any improvements should authorisation be given for a repair. Now as bad luck would have it, moments after the above NVH recording was captured the engine cut out accompanied with an awful metallic sound from the cylinder head!
The NVH capture below is what to expect when cranking an engine with no compression as a result of contact between the inlet valves and the piston!
Note the higher-than-normal cranking speed at 318 rpm (318 / 60 = 5.3 Hz) and 11 strike events per second (11 Hz) 11 x 60 = 660 rpm. These periodic strike events are caused by contact between components at the rate of twice per engine revolution (2 x 5.3 Hz) and may well be a foul condition between the pistons and the deformed inlet valves or “flapping” of a worn timing chain.
Needless to say, it was worth a look below to discover how far our valve timing had shifted to cause the catastrophic damage indicated above. Note that the cam and crank correlation has now advanced to 11.23° or indeed a tooth count of zero from our known good capture of 110.4° which equates to an advanced valve timing of 110.4 – 11.23 = 99.17° (crankshaft rotation) / 2 = 49.6° of camshaft deviation (I think this explains the piston to valve collision).
N.B note the lack of compression from cylinder 1 on channel F too!
As you can see it had stretched roughly 1.2 cm.
We replaced all the relevant parts, the engine was reassembled and we proceeded to take the following captures to verify the repair.
Starting with cam and crank correlation at idle, acceleration and deceleration.
Here we evaluate the “push pull” effect of the crankshaft on the timing chain assembly by comparing correlation values.
In the following screenshot, we captured the cam and crank correlation at 3500 rpm during crankshaft acceleration.
Correlation deviation: 116 – 109.7 = 6.3° (crankshaft rotation) / 2 = 3.15° of camshaft deviation!
This raised an eyebrow for sure as this deviation seems excessive based on this discussion where we concluded that 3° of camshaft deviation is sufficient to generate a correlation code! Of course, this depends on the vehicle manufacturer and the engine design. This engine does not utilise a camshaft phaser between the timing gear and camshaft (the relationship is fixed) and therefore the deviation should be minimal.
The variable valve control is carried out by using oil pressure to variate the camshaft profiles and not the cam and crank phase! Food for thought once again, and no doubt worthy of further discussion.
Postfix in-cylinder analysis
Below we had cylinder 1 captured during stable idle after start-up. Note the typical 4-stroke cycle waveform with clearly defined EVO at approx. 140° ATDC of the compression stroke (before fix 103°) and IVC at approx. 562° ATDC of the compression stroke (before fix approx. 540°). While it is difficult to categorically establish EVC and IVO (accompanied by the change of direction of the piston during overlap), we can see these typical events occurring around the 360° ATDC of the compression stroke (before the fix these events were clearly visible before the 360° due to the advanced valve timing).
Note how the previous vibration orders E0.5 and E1 were no longer detected by the accelerometer now that complete combustion and chain tension had been restored. Our normal E2 vibration order was now measured at 112 mg via the accelerometer (before fix 238 mg).
Now let’s take a look at the time domain below. The difference between pre and postfix is like night and day with the near absence of intense “strike” events.
At this stage of post-fix analysis, I would like to include a mobile phone recording as we have discussed here.
Please listen to both recordings below which were taken simultaneously (in front of the timing cover) one using an NVH mic and the other using a mobile phone
The following audio file was taken from the above NVH capture using the microphone on Channel D:
The following audio recording is the same as the one above but captured using a mobile phone
Notice that there is a clear difference in the perceived clarity between the recordings, given the mobile phone is optimized for a specified range of frequencies, incorporates a degree of noise-cancelling, has directional qualities and in some cases, utilize multiple microphones. The noises therefore captured by mobile phones have a degree of “enhancement” which you can hear in the mobile phone recording above between 18-22 seconds where there appears to be loud tappet-style noise that is not so prominent to the human ear or indeed in the NVH recording. While mobile phones are incredibly useful and readily available, I would not base a diagnosis on a smartphone recording alone.
Additional sound analysis software
When using the PicoDiagnostics NVH software, you may wish to expand on the analysis of sounds using additional free software such as Audacity or Sonic Visualizer which we have discussed here and here.
Looking back at our initial NVH capture taken before the fix, we have exported the sound from channel A (accelerometer attached to the timing cover) and imported this data into Sonic Visualizer where we have additional analysis features at our disposal.
The image below has our exported data from the time domain of PicoScope NVH (blue waveform/engine speed 1080 rpm) with the addition of a Melodic Spectrogram (Heat Map) which is optimized for melodic content.
Note how frequency is now on the Y-axis, time on the X-axis and the energy level (amplitude) of the sound is displayed using colours. (Brighter colours = higher energy/amplitude.)
In the screenshot above, we can clearly see the bright red and yellow “strikes” displayed at a rate of four beats per second (4 Hz) The use of bright colours indicates that these beats contain sufficient energy levels to be distinguished from all other sounds within the recording (the most dominant sound level).
Given that these beats are detected by the accelerometer attached to the timing cover (similar to a stethoscope) we have further evidence that these intensive, periodic energy beats are characteristic of a strike or contact between components which I suspect are the tensioner guide and timing chain (see below).
The relationship of the beat frequency (4 Hz) to our engine frequency at 1080 rpm /18 Hz is not easily defined because the timing chain/tensioner will be responding to incomplete combustion events every revolution of the engine. This will create a “whip” in the chain which no doubt will introduce a unique vibration characteristic.
Below we have a postfix capture where the results speak for themselves with very little sound energy to display until the engine was free-revved towards the end of the capture.
A timing chain kit, a used camshaft with eight used inlet valves, and all associated gaskets/consumables.
With all diagnoses, there has to be a logical procedure to follow that includes various levels of diagnostic intrusion accompanied by costs. (The more intrusion the more cost) There is no doubt that the case study above is quite unique, given we were able to capture data prior to engine failure which most would have diagnosed without lifting the bonnet. With that said, the least intrusive of all the techniques above was our NVH measurement, which could be applied during routine servicing in order to build an engine/vehicle NVH signature. This could in turn allow for early warning of such catastrophic failures.
I wish to say thanks to Kevin Ives at Ives Garage for his support throughout the above case study, which spanned from October 2019 to March 2021 (That was a lot of coffee and cake.)
August 20 2021
thankyou thats a real eye opener as to how small a chain stretch can result in such a lot of valve delay. i speculate that this is a result of the diminutive cam sprocket diameters now being used. i recently had similar issues on a nissan xtrail 2.4 D which has cam sprockets in the region of 60mm dia duplex chain which in my opinion is cost cutting madness and which ,judging by the noise of said engines, must be introducing a lot of stress and chatter into the chain drive
March 29 2021
Thanks for a really informative case study. I’ve often wanted to use sound recordings for diagnostics….. clearly a complex venture.