![]() |
Posted by Aaron (92 SE Auto) on July 16, 2002 at 18:33:49:
Well, after driving the car for 2 days I finally got around to checking everything the FSM diagnostic procedure tells me to. I first check to see if there are any codes in the ECU. It flashed 55... nothing is wrong. I went ahead and did the procedure. I checked the input signal by checking continuity between the ECU and the detonation sensor sub harness connector.... checks out great. I checked the detonation sensor itself by checking the continuity between the sub harness connector and ground.... checks out great. Well, what the crap is wrong with my car? Everything checks out... but 2 days ago the ECU gave me the detonation sensor malfunction error. What happened? Also, I talked to the dealership technician and he said that very rarely does he see that motor come in for a detonation sensor replacement. He said, "It's usually something else causing that code to flash. I've seen the o2 sensor cause the detonation sensor code to flash." I said, "hmm... ok thanks". Any input is greatly appreciated. It will help me determine what the crap is going on. Thanks in advance.
Remember I told you guys that I ran a self diagnostic procedure by turning that ECU screw and looking at the red flashes. Well, I got the code 34 = detonation sensor. After reading the FSM a little more, I found out that if you turn off the ignition switch while the diagnotic mode is activated... it will erase any codes from memory. Now, I got the 55 code.. meaning nothing is wrong.