The Engine Clean standard: prove whether the fault is inside the unit, then choose the most sensible technical route.
Begin with the complaint and history
We need to know what the vehicle does, when the fault appears and what has already been disturbed or replaced. A precise history often determines whether vehicle diagnostics, bench testing or both are required.
Vehicle tests and bench tests answer different questions
Vehicle testing can confirm powers, grounds, wiring, network behaviour and related inputs. Bench testing can assess the removed unit under controlled conditions, including power-up, communication and internal inspection where appropriate. Neither should be presented as more conclusive than its actual scope.
What in-house inspection can include
Depending on the unit and failure, Engine Clean can carry out power-supply testing, bench reading, EEPROM, flash and MCU work, cloning, coding, microscopic PCB inspection and component-level repair. Not every ECU or failure is repairable.
A useful test produces a route
The result may support repair, a tested donor, cloning, programming, a new unit or further vehicle-side diagnosis. You receive a recommendation based on compatibility and evidence rather than a generic parts list.
Straight answers
Before ECU or module work
Can every ECU be fully tested on the bench?
No. Access and test coverage vary by unit, software, hardware and the reported failure. We explain the scope and limitations of the assessment.
Do you inspect ECU circuit boards?
Yes, where appropriate. In-house work includes microscopic PCB inspection and component-level investigation, subject to the unit and fault.
Can testing prevent damage to a replacement?
It can identify external faults such as supply, wiring, connector or water-ingress problems that should be corrected before another unit is fitted.