I think I solved a long running intermittent problem and wanted to share what I found. My 91 explorer would occasionally have the CIL come on and run poorly or stall. Turn off motor, restart, and everything would be OK until next time. No codes. Most of my sporadic efforts first focused on relays and wiring around the power box because it seemed like the computer was losing power.
Back at this thread: http://www.explorerforum.com/forums/showthread.php?t=267027 I decided I needed new plugs and wires, I changed them and it cut down on the frequency but didn't fixed it. I started looking at the coil pack, ignition module, and associated wiring.
I ended up finding that at the ignition module there are two wires (PIP and SPOUT) that the module and the computer use to communicate with each other on spark timing and both have a grounded braid on them, which Y's together to a common ground.
The SPOUT wire's braid right near where it passes by/under the battery tray was corroded nearly all the way through, although the wire harness itself looked ok until I open it up and looked more closely.
A splice and some heat shrink---problem solved!!
I'm glad its fixed although the geek in me wouldn't mind knowing the mad scientist reason why there wasn't a code for what was going on.
Back at this thread: http://www.explorerforum.com/forums/showthread.php?t=267027 I decided I needed new plugs and wires, I changed them and it cut down on the frequency but didn't fixed it. I started looking at the coil pack, ignition module, and associated wiring.
I ended up finding that at the ignition module there are two wires (PIP and SPOUT) that the module and the computer use to communicate with each other on spark timing and both have a grounded braid on them, which Y's together to a common ground.
The SPOUT wire's braid right near where it passes by/under the battery tray was corroded nearly all the way through, although the wire harness itself looked ok until I open it up and looked more closely.
A splice and some heat shrink---problem solved!!
I'm glad its fixed although the geek in me wouldn't mind knowing the mad scientist reason why there wasn't a code for what was going on.