glfredrick
Explorer Addict
- Joined
- January 25, 2003
- Messages
- 2,427
- Reaction score
- 26
- City, State
- Louisville, Kentucky
- Year, Model & Trim Level
- 86-98 Ranger STX
I'm having problems that seem to be GEM module related on the 97. This isn't the first time I've had GEM troubles, and I'm wondering if anyone else has had these issues, and what it takes to fix them.
Symptoms...
4x4 sometimes engages when it isn't needed, especially when backing up and turning sharply (like backing out of a parking spot on dry blacktop). Once engaged, the 4x4 will stay locked in until we shut off the truck, making it drive hard, steer hard, and generally suck.
Dash lights do not function when the headlights are on. All the various warning lights (like 4x4 -- speed control -- OD off, etc) go away when the headlight switch is turned on. They are still lit (turn off the headlights and they are right there) but never show when the lights are on.
Failure to allow a computer scan. When I try doing a code read, I get a malfunction code and the scan stops. I'm using top end scanner tools from Snap On with all the latest updates (Modis, Color Graphing Scanner, Solus) and also cheapy simple OBD II code readers all with the same issues.
In the past we had Ford re-flash, and then replace the GEM, which helped drivability for a short time, but the problems quickly returned. Is something killing the GEM or do I have another issue at hand?
Symptoms...
4x4 sometimes engages when it isn't needed, especially when backing up and turning sharply (like backing out of a parking spot on dry blacktop). Once engaged, the 4x4 will stay locked in until we shut off the truck, making it drive hard, steer hard, and generally suck.
Dash lights do not function when the headlights are on. All the various warning lights (like 4x4 -- speed control -- OD off, etc) go away when the headlight switch is turned on. They are still lit (turn off the headlights and they are right there) but never show when the lights are on.
Failure to allow a computer scan. When I try doing a code read, I get a malfunction code and the scan stops. I'm using top end scanner tools from Snap On with all the latest updates (Modis, Color Graphing Scanner, Solus) and also cheapy simple OBD II code readers all with the same issues.
In the past we had Ford re-flash, and then replace the GEM, which helped drivability for a short time, but the problems quickly returned. Is something killing the GEM or do I have another issue at hand?