what do you think of them? also when I was driving home the check engine light came on what could it be

 

Hi,
i dont own a intrepid but 1 of its brothers a 94 eagle vision.We have had it in the family since day 1 and 189k miles later it is a great powerful,handling,running car.You say your check engine light came on, when you were driving it.It could be a bad 02 sensor.Have a mechanic or take it to aamco they`ll diagnose it for free.I had a check engine light come on alot and it was a matter of time before i couldnt take seeing it on once i replaced the 2 02 sensors the check engine light never came back on again.

thanks
pat

 

A check engine light can be caused by anything from emmisions, to required engine singnals (for operation). Any auto Zone (or simmilar parts store) will checkout whats wrong with a ODB scan tool for free. After the read, post the findings, and I will get back with you.

 

I took it to auto zone and they said they cant read them that far back .so he said turn my ignition on. and off w/out starting the engine
3 times and count how many tie the check engine light comes on
well it didnt even come on at all. Also it only came on on my way home from the lot.It was a 25 mile trip so im leary of taking it out of town till i get it figured out.Also the struts are making some noise s well any1 else had strut issues with these?

 

In 96 the new OBD II became the industry standard however some autos were already using OBD II in the early 90's. Did he look at your car, or just say "95, no can do"? Another option he should have been able to offer, was to purchase an ODB I reader for your car (if that's what you have). If you plan to keep the car, I think it would be a good investment of the few $.

As for the key reading method, (just as with a scan tool), this will only work if there is a code to read! Are you saying there was no engine light when you were trying to read the code? Did you try after the engine light came on? If not, you should try. It may be you have the older OBD or the light is just flickering (faulty) randomly because the fault should have been stored in the computer. When you went to try the "key on" trick, the fault codes should have been there(for 50 key cycles, I think). Does anyone else reading this post know if OBD I stores faults the same as OBD II? Also, does the "key trick" work on OBD I cars?

Every now and then, my struts "squeak". It may do it for a month, and then it clears up. Due to time ect, I have just left them alone, and will repair them when it becomes more defined. Mine have done this for around a year now and I am not too concerned. You may want to have someone check yours out to be safe because this is impossible to judge via a computer chat board!

 

I think the problem with not getting the code is that you need to leave the ignition "ON" after all the switching. And just to be sure, DONOT START the car then shut it off three times, just turn the key to the on position, back off, on, off, then on again. Then start counting the flashes. A pause means its done with that number, the next flashes are the next number. For example, flash, flash, pause, flash, flash, flash, pause is 23. There will be a series of numbers. It might help to write it down. I found the codes in a library book (which also explains the procedure) and I'm sure they are available on-line, but I don't knowany links. One linkon this page (while I was typing) looked like it might have the information, but I didn't check it. Good Luck!