NIStune watertemp misread?

Whacker · Post by **Whacker** » Sun May 03, 2009 2:05 am

Hi!

I'm really desperate for some help here.. I've done all I can think of to solve this problem but now I'm stuck.. Any idea would be helpful

I can't tune my car with NIStune as the engine coolant temp sais 205° at all times...

I first thought it was the sensor so got a new one which of course was with the wrong connections but this is what I did:

I took the old one out of the engine and measured the resistance when it's in warm water along with the new one and there seem to be nothing wrong with it.. Well it differs about 0,1 but it's within the right margins according to the workshop manual..

Then I though it might be the plug which I connect it with that might have suffered some kind of short cut..
So removed it and replaced it with pins which I then fitted directly to the pins on the sensor..
Tested both sensors this way but still said 205° in NIStune... It said 26° when not connected to the sensor..

I get the following ECU Messages:
Consult_DTC_Temp (Starts=0)
Consult_DTC_Cooling_Fan_Circuit (Start=0)

I've also checked all the connections to the ECU and everything seems fine... The only thing left is the ECU and as I guess it worked before it has to have something with NIStune..

Also the check engine light is on but don't know if it has anything to do with this...

Any help would be truly appreciated..

Thanks
/Elias

Matt · Post by **Matt** » Sun May 03, 2009 5:20 pm

which ecu have you got?

nistune will only read what the ECU itself is reporting. Either a problem with blown input to ECU or wire going from sensor

Since you have checked the wire, it may be worth seeing if you can borrow another ECU and check for the coolant DTC code (via flashing LEDs on that)

Or also measure resistance of coolant temp sensor on ECU pins (ie temp sensor pin and sensor ground actually on ECU harness) and see if the resistance is correct

ECU is reporting its not seeing the sensor or its resistance is out of range

Whacker · Post by **Whacker** » Sun May 03, 2009 10:12 pm

Thank you for yourt time but problem is solved.. Talked to Pete through emails and he looked at the bin and saw a lot of blank values and one of them were the Temperature Conversion table..

A very long story how this happened but that's how it ended

Thanks....

Matt · Post by **Matt** » Sun May 03, 2009 10:25 pm

oh... didnt even think of that one. raw temp goes through this table into the ECU reported temperature... yeah it being wiped out would do that

Whacker · Post by **Whacker** » Wed May 06, 2009 9:04 pm

So it seems =) Thanks anyway though...

Now it's time to get back to battle the next problem.. Massive overfueling

haha....