It does everything like all the other cheap multivehicle OBD2 scanners can do for the Td5 EMS... shows you nice but false fault codes and erratic live data, that's what they do, believe me or not
Hi. That would be the best if you want to have no issues with such things and you can install a hidden "kill switch" under the dash if you want it to be unstartable for potential thieves
The wastegte seems to be tighter than from factory so it should not be low on boost for that reason
that became clear when you said it's from 2003.... i cant say more than i've already said about the black smoke
I've seen many logs and 10*C difference between the ECT and FT is quite usual and considered normal, as about hight FT input AFAIK when it exceeds 75*C a smoke limiter map kicks in and the ECU reduces the IQ(injected quantity), the higher the rpm...
As i said it doesnt seem a management issue, it's overfuelled for some reason and a bit low on boost... might be from the injectors or the turbo if you are certain that there is no boost leak... is it manual or auto? also how many threads are...
Maybe on the P38 as you can inflate all 4 of them more than normal and then it can be stiff but on the D2 being only at the rear if you inflate them more than normal the vehicle will not be horizontal and on a well calibrated D2 the ride is much...
:vb-headbang:
^^^ that's named cognitive dissonance, unless your SLS was not working well from the beginning ... though if you want something really good i recommend THESE but never expect to have the ride quality of one with air springs despite...
You might not notice it if you are not used to a well running Td5 driven with nervs. As long as you have the AAP fault code logged the ECU is on default for that specific code and one of the symptoms is "boost limited to 1 bar" so without correct...
See live stationary voltage inputs... if they are all similar or very close(between 2 - 2.3v) the problem is most probably the hub, if the one with the code is out of that it's a wiring issue ...or ECU misbehaviour
Check the MAP/IAT sensor. Mine did that. With help from on here I checked the data while it was running which proved that even though clean, it was fubar.
Just to say thank you Fery, problem sorted (till the next time!!) I hadn't seen the bit about swapping the relays but that did the trick. Strange as there was no sign, or smell of any burning or damage but anyway, changing it worked. I was all...