In-vehicle NVH Testing
Add objectively to your assessments
Customer satisfaction drives the entire passenger vehicle powertrain NVH market and the ultimate verification of a product’s performance is how that product is perceived in-vehicle.
PLATO systems are used in-vehicle to provide objective assessments of NVH and, because the same core software is used that operates with factory-based systems, in-vehicle results can be used to optimise end-of-line assessment metrics and pass/fail boundaries.
The ABD VP106 is the perfect frontend for PLATO based in-vehicle measurements.
It powers and conditions up four NVH sensors (e.g. microphones, accelerometers) together with a separate RPM (tacho) signal, and it incorporates a National Instruments™ USB-4432 5-channel DAQ-module to link effortlessly to your laptop or tablet PC; providing sampled data with 24-bit precision.
Driver guidance and result extraction
Meaningful in-vehicle NVH results came from tests where conditions (i.e. speed and torque loading) have been held consistent.
PLATO’s real-time test conditions view provides test drivers with the ideal tool to make this happen.
Then, with the aid of run-averaging to reduce the effects of inevitable randomness on the results, salient order tracks are effortlessly extracted in real-time during controlled speed sweep (acceleration-deceleration) testing.
Protrusion and audibility
Human perception of powertrain NVH stems from audibility; for example, can the powertrain be heard above background noise arising from tyres, wind and other sounds?
In this example, order 21.25 (corresponding to transaxle final drive fundamental gear mesh order) stands at least 6dB above adjacent background noise. This is audible and a customer complaint.
The 'big picture'
This order track protrusion summary (using the same data as above) shows that final drive gear mesh is well into the audible zone around 2900 RPM.
It also shows that engine firing orders are the most audible components at lower RPM values.
Clear, precise results
In-vehicle NVH results are reported using PLATO’s intuitive test report and stored within PLATO’s results database (SQL) so they can be passed on to PLATO-SERVER, when the laptop/tablet PC networks are connected back at base.