92ShoOff
SHO Member
....if I can get it to drive there first. Okay so I've owned my '92 MTX since October of 2003 and have tuned it up and replaced MANY, MANY parts already. The car had 116k when I got it... and it's my daily-driver for work. So it now has 132k on the clock. Well I think just about every sensor on the car has gone bad since I owned it and each time the check engine light comes on, I run a scan, and end up with a bad sensor and then I replace it right after. Well, a few weeks bad I got a CID sensor code, and just this weekend I replaced the CID sensor. When I removed the old sensor (which seemed to look fairly new due to its cleanliness... but maybe those things don't tend to get too dirty on the inside or out) I noticed a tiny bit of engine oil collected at the bottom of the housing where the sensor was just removed from. I figured maybe that oil over time crept in there and that was what damaged the current CID sensor. So I sprayed just a little bit of throttle body cleaner where the oil was and wip it off with a paper towel. I bolted the sensor back on, clear the code, ran the scan again and everything seemed fine.
Well, just tonight on my way home from work I noticed my tach was skipping around... which is of course said to be a symptom of a bad CID sensor. Well my tach NEVER acted up before I changed the sensor, and now that I have, it is acting up. I don't get it. Then while I'm driving with my lights on I noticed every time I tapped my brake the headlights and dashlights flickered slightly and the tach needle would flutter really quickly. I also noticed that the higher the RPMs were, the more the needle would flicker. The needle went crazy when I tapped the brake at like 4-4500 RPM... the needle actually red-line (though my engine was already dropping down from the 4k RPM's). Then when I pulled home, as soon as I came to a stop in the driveway (I may not have even made it to a complete stop).. the engine stalled. It started back up with no problem... but it's never stalled on me before except it did it a few times while I was trying to get it out of my driveway one day when I first got it. I just don't get it! I've replaced so many sensors and I'm sure when I run a diagnostic scan on it tomorrow it's going to tell me I have yet ANOTHER bad sensor. And also, I'm now hearing a whining in my rear speakers.. very quiet, and the sound goes right on along with my engine's RPMs.
I think I may have heard from someone on here that when your compuer throws codes constantly the computer may be bad. Is that possible? I have an XJ2 EEC in mine... and other than constantly getting new codes after old problems were fixed and I don't know what other signs may point to a bad EEC.
These cars truly needed an integrated/on-board diagnostics scanner. This stuff just gets old. You know what? I think I'm going to run my scanner through the firewall, into the cab, and use some double-sided tape and stick it to my steering wheel. While it's there I can always tell all the ricers that they best back off 'cause that's my power programmer, right? Don't mess with the "red dragon", right? Haha. Yeah right. But I still think sticking my scanner to my steering wheel is an idea. Anyone else agree? Any help on all this would be REALLY REALLY appreciated as always fellas!
Thanks!,
Andrew
Well, just tonight on my way home from work I noticed my tach was skipping around... which is of course said to be a symptom of a bad CID sensor. Well my tach NEVER acted up before I changed the sensor, and now that I have, it is acting up. I don't get it. Then while I'm driving with my lights on I noticed every time I tapped my brake the headlights and dashlights flickered slightly and the tach needle would flutter really quickly. I also noticed that the higher the RPMs were, the more the needle would flicker. The needle went crazy when I tapped the brake at like 4-4500 RPM... the needle actually red-line (though my engine was already dropping down from the 4k RPM's). Then when I pulled home, as soon as I came to a stop in the driveway (I may not have even made it to a complete stop).. the engine stalled. It started back up with no problem... but it's never stalled on me before except it did it a few times while I was trying to get it out of my driveway one day when I first got it. I just don't get it! I've replaced so many sensors and I'm sure when I run a diagnostic scan on it tomorrow it's going to tell me I have yet ANOTHER bad sensor. And also, I'm now hearing a whining in my rear speakers.. very quiet, and the sound goes right on along with my engine's RPMs.
I think I may have heard from someone on here that when your compuer throws codes constantly the computer may be bad. Is that possible? I have an XJ2 EEC in mine... and other than constantly getting new codes after old problems were fixed and I don't know what other signs may point to a bad EEC.
These cars truly needed an integrated/on-board diagnostics scanner. This stuff just gets old. You know what? I think I'm going to run my scanner through the firewall, into the cab, and use some double-sided tape and stick it to my steering wheel. While it's there I can always tell all the ricers that they best back off 'cause that's my power programmer, right? Don't mess with the "red dragon", right? Haha. Yeah right. But I still think sticking my scanner to my steering wheel is an idea. Anyone else agree? Any help on all this would be REALLY REALLY appreciated as always fellas!
Thanks!,
Andrew
