Oh gotcha, I just went back and reread that; my bad I didn’t read that right.I didn't say it was a rotor problem I was explaining a symptom, not a problem
Disclaimer: Links on this page pointing to Amazon, eBay and other sites may include affiliate code. If you click them and make a purchase, we may earn a small commission.
Oh gotcha, I just went back and reread that; my bad I didn’t read that right.I didn't say it was a rotor problem I was explaining a symptom, not a problem
Any chance the tach signal wire could create any problems? On the gray connector, white which goes up to the cluster. Pretty sure it's just an output wire that goes to the cluster, but just making sure.I didn't say it was a rotor problem I was explaining a symptom, not a problem
Im going to try adding that ground and wiggling the wires some more, aswell as hard wiring it to the battery for testing, but past that if its happy with the coil on the firewall, ill just let it be happy there.
Any chance the tach signal wire could create any problems? On the gray connector, white which goes up to the cluster. Pretty sure it's just an output wire that goes to the cluster, but just making sure.
Side note from the post first, I wish I knew how to quote your different parts of the response, would be a lot more organized lol, but,I'm reminded of this:
Patient: "Doctor, it hurts when I do this"
Doctor: "Then don't do that"
IMHO that's just hiding a problem and hoping it doesn't come back to bite you in the @ss.
Well, in normal operation it's an "output" to the tach, and it's "driven" by the ignition control module... but if something was amiss on the tach wire it could cause a problem. If prior owner did some funky stuff and that wire was left bare and somehow exposed to a possible ground point (firewall, etc.), a momentary ground of that wire would create a momentary spark from the coil, and repeated, erratic grounding of that wire would cause repeated, erratic sparks from the coil.