Need Help Diagnosing a Problem
#1
Need Help Diagnosing a Problem
Hi everyone I have a 2004 GP white s2000, only mods are KWv1's ,K&N intake, and some cosmetics. A year and a half ago the car started to give me some strange problems that I haven't been able to fix. I really need some help here.
The problem usually occurs in warmer weather (60 degrees plus). The car will drive fine for some period of time, then all of the sudden the temp gauge will read one bar, check engine will come on, and car will go in to a sort of limp mode.
Previous to the problem, and after I let it sit for a while and cool down, the car will store no codes. While the problem is occurring the computer will not even respond/connect to any code readers.
I have taken the car to the local Honda dealer (they game me limited attention because the "car was too low"), a local friends shop, and tried to diagnose my self, with no luck at all
When it is cold out the car car runs fine. I figured a temp sensor would have just threw a code, and I dont want to spend a lot of money to not fix anything, but im starting to run out of options here. Please help me out!!! I hate seeing her sit in the garage all summer.
Thanks, Matt
The problem usually occurs in warmer weather (60 degrees plus). The car will drive fine for some period of time, then all of the sudden the temp gauge will read one bar, check engine will come on, and car will go in to a sort of limp mode.
Previous to the problem, and after I let it sit for a while and cool down, the car will store no codes. While the problem is occurring the computer will not even respond/connect to any code readers.
I have taken the car to the local Honda dealer (they game me limited attention because the "car was too low"), a local friends shop, and tried to diagnose my self, with no luck at all
When it is cold out the car car runs fine. I figured a temp sensor would have just threw a code, and I dont want to spend a lot of money to not fix anything, but im starting to run out of options here. Please help me out!!! I hate seeing her sit in the garage all summer.
Thanks, Matt
#2
Maybe the thermostat?
#5
I would agree, seems electrical to me. I would look at the coolant temp sensor. The fact that a code reader won't connect seems odd though. A coolant temp sensor isn't very expensive and should be a easy swap. I would change it and see if that corrects the issue.
#6
I hope it's not ecu related.
#7
If the thermostat that is stuck open it will throw a CEL code for low coolant temp. The ECU needs to see a higher temp after running a certain amount of time, if it doesn't then it will spit out a CEL and may go into limp mode or limit VTEC for sure. It usually happens about 10 minutes or so after start up. The car doesn't run as well when it's cold either contrary what many people may think.
I have no idea why you can't connect to the ECU though.
I have no idea why you can't connect to the ECU though.
Trending Topics
#8
Thanks everyone for your input, I was going to post a video of the problem, but couldn't figure out how to post it. I purchased a temp sensor and thermostat. Hopefully one of these will fix the problem, id much rather spend my money on a t1-r sparrow exhaust than an ECU.
Thread
Thread Starter
Forum
Replies
Last Post