Hello Robbo, sorry for the late reply
Looking at your NVH capture we have
two issues during acceleration
One is an E0.5 which we can often (but not always) attribute to misfire (or incomplete combustion)
A further description can be found here
viewtopic.php?p=86961#p86961
The other is T1 (A component rotating at the same frequency as the road wheel and tyre)
Below we can see both E0.5 and T1 vibrations above all others within the frequency view (approx. 30 mph, 1784 rpm during acceleration)
- Image 1
Be aware that 4th gear 30 mph may well introduce a “lugging” effect (low road speed high gear) and will certainly load the engine
.
With that said, if our E0.5 can be attributed to misfire, this is not acceptable
As road and engine speed increase, the dominate vibration is then T1; So much so that I had to rescale the Y axis to accommodate the peak vibration
- Image 2
Note above, the T1 marker does not sit right on top of the measured peak at 84.1 mg due to characteristic FFT processing of continually changing road/engine speed, this is quite normal.
Had our vibration been present at fixed speeds our T1 marker would sit on top of the measured peak
In order to now pinpoint this vibration (assuming the accelerometer was installed to the driver’s seat bolt in the typical orientation) we use the right click feature and select “Single” Display mode to determine the predominate offending axis
- Image 3
Above we can see our X axis (fore and aft blue) is the larger offender but I note that the Z axis (lateral green) is also high
In my experience, to make a vehicle vibrate laterally (side to side) you need a
lot of energy and often generated by tyres or driveshafts (Think of a scenario where a large mass can be rocked side to side)
We should not however jump to conclusions and be guided by the data.
I would now keep the accelerometer mounted on the driver’s seat (measuring the X axis only) and add additional accelerometers to the front caliper bolts (measuring the X axis only) whilst ensuring the orientation of additional accelerometer reflects that of the accelerometer connected to the driver’s seat bolt. This will help with “zoning” of the vibration, i.e., which corner of the vehicle is our offender
If we only have one accelerometer, then repeat the road tests measuring at each corner of the vehicle on the same road surface keeping the test conditions identical and variables to a minimum (not always possible I know)
Moving onto your psdata file
I have noticed periodic non-uniformity in the crank shaft sensor signal which I have highlighted below.
Worthy of investigation
- Image 4
The periodic non-uniformity does affect the math channel considerably and I wonder if the PCM has a similar issue with interpretation of this signal?
Below I have chosen to analyze the engine speed at 1784 rpm which is where our E0.5 vibration peak was most prominent (See image 1 above)
- Image 5
We can see above that our crankshaft acceleration does not exhibit any visible drop during each combustion event passing through the 1784 rpm band (Suggesting no misfire)
I would however inspect this capture across the
entire rpm range just to be sure (Note I have amended the math channel to “crank(A,60)" which improves the resolution dramatically
Once again, note the effects of the non-uniform crankshaft signal upon the math channel
Remember, we must be guided by the data collected above and our focus must be the huge T1 vibration as the E0.5 passes by reasonably quickly (unlike T1)
The following case study might help regarding the detection of E0.5 during periods of light throttle application during cruise conditions “Tip in”
viewtopic.php?p=103362#p103362
This may be another technique to acquire E0.5 data under differing load conditions
if a vibration is felt during such driving conditions
I hope this helps, take care…..Steve