Fans turn on, idle goes up and a few other things to protect the engine. Also when it happens the ECU or BCU stops updating the DIC with the ECT as it's considered to be invalid. If this happens enough times it will eventually set the DTC, but conditions have to be right. I suspect that the thermostat is the problem in that during certain ECU system checks it fails to measure ECT within the expected range causing the pending P0128. I have cleaned the connector a few times now and I clean the MAF after every oil change so I know it is neither of those. In each case SAE ECT always shows expected coolant temp with no hick up around the time the DIC rolls over to "-". I have always caught it with the DIC display "-" and showed either pending or current P0128 code. I have had the same problems off and on for over a year now. Similarly, If I leave the dash display on temperature, as soon as the display changes to ro from - I know the problem has come or gone. Since I live in a climate that A/C is almost always running (top up or down), the first clue while driving that the code is being trown, is the A/C stops running. Maybe this time I will embark on the contact cleaning since it is random, not predictable or repeatable on demand. To me this rules out thermostate issues, keeping it at the ECT level. The fact that as soon as the key is in the ignition position the cooling fans come on before starting is indicative all is probably ok, just the computer thinks it is hot. Somewhere else there must be another temperature sensor, as there is a monitor in the Torque app showing a normal temperature even though the dash display shows. The code P0128 is displayed relating to ECT reading being "low". I now have an Android app called "Torque" which finally came into use as this issue resurfaced a couple of days ago. Randomly after a few minutes or sometimes a few days, everything back to normal. The combination being fans run from start, no A/C, dash reads -, and CEL comes on. This problem occurred a few years ago for several months then ceased to be an issue all on its own. Wonder if this is common enough that it'll turn into a TSB?īack again. So.it looks like I may be at where CndnSol is. Dealer just called and said that he pulled the codes again and saw that the thermostat was intermittently sticking open, so they're replacing that and also the connectors to be sure. The dealer replaced the Engine Coolant Temp (ECT) sensor the following morning, and all was fine for 1 day - it went to -F again last night, so this morning I turned on the engine and the radiator fan immediately kicked on as an expected result. Tried cleaning the connector/sensor terminals, that didn't work either. I tried unplugging/reseating the sensor connector, that didn't work. Then about 15 minutes later, the display went to "-F" It normally should be around 190 - 210F depending on where I am. Earlier this week, I noticed the temp was reading erroneously low on my normal drive home from work, around ~150 ish give or take 8 degrees. I leave my DIC on the Coolant temp display. So add me to the list of folks with the exact same problem, at 21K miles.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |