Quoting here, as it's a more logical continuation ...
kadman wrote: ↑Thu Sep 16, 2021 12:25 pm
So.....You bought Multiecuscan, and all the leads, and the OBD connector. And you did nothing with it at all, which means.
You never plugged it in, never erased the existing codes, never started it up to record if existing codes re appeared.
Never ran a live diagnostics with the laptop whilst driving. Ergo no data to inspect to correct your faults.
And no indepth inspection of existing actuators and fuel details. That would have possibly prevented you in breaking down on the roadside.
Bought and used the leads and the software. Got the three errors previously noted. Cleared them, never saw them again. Tried to provoke the "uphill at high revs" error yesterday on the one hill that might have triggered it in the past, and didn't get the warning as before. Never got a second chance.
In the meantime, removed and checked the intercooler for holes, the removed and checked the various airhoses, checked the wastegate, changed the old part of the exhaust for a new one, checked as many sensor connections as I could find (all OK, no corrosion on any of them).
MultiECUscan with engine running while static gave no warnings; whether or not all the other live data was within range I don't know because I had no reference values. Couldn't do diagnostics while driving because I wasn't road legal till 11h15 yesterday (also the position of the OBD port and the weight of the ELM lead make for a very unstable combination - not sure it would have been possible without a second person in the cab to hold everything stable ...
All academic now because the emissions will be zero for the foreseeable future.