Experiencing issues with your robust 7.3 diesel engine can be frustrating, especially when you’re trying to diagnose the problem yourself. Like many owners of older trucks, I recently picked up an ’01, and soon discovered it needed some tender loving care. The initial gremlin was the engine dying intermittently, particularly when cresting hills and letting off the gas. Hoping to pinpoint the issue, I decided to invest in an Android OBD2 scanner. This is my experience, and a cautionary tale, of how things can sometimes take an unexpected turn when using diagnostic tools on these engines.
Initially, the symptoms were perplexing. The engine would cut out while driving, a potentially dangerous situation. After replacing the Camshaft Position Sensor (CPS), which is a common culprit, the problem persisted. It became clear the engine was more likely to stall when the fuel demand decreased, such as when going downhill or cresting a hill. Driving like this for 2,500 miles was nerve-wracking, to say the least.
While waiting for my new Android OBD2 scanner to arrive, other electrical gremlins began to surface. The power window would intermittently fail, and the radio developed a mind of its own, switching stations and turning on and off randomly. Then, the worst happened. Cresting a hill, the engine died again, but this time, it wouldn’t restart. Cranking the engine resulted in nothing; I was stranded and had to call for a tow. The truck would crank strongly, but simply wouldn’t fire up.
Finally, the Android OBD2 scanner arrived – the Veepeak Mini Bluetooth OBD2 Scanner. Eager to get some diagnostic codes, I plugged it in and paired it with my Android device. Initially, things looked promising. The scanner connected, and I could see it attempting to read codes. I heard relays clicking, and bizarrely, the windshield wipers cycled on and off. Just as the scanner seemed to be completing its scan, the screen went blank, and no diagnostic trouble codes were displayed.
Worse still, after this failed scan attempt, the scanner wouldn’t reconnect at all. And to compound the issues, the truck now wouldn’t even crank! Turning the key resulted in complete silence – no starter engagement, nothing. The battery was definitely fine. It appeared that attempting to use the OBD2 scanner had somehow made the situation significantly worse.
At this point, the potential culprits seem to be pointing towards either a faulty Engine Control Module (ECM) or a problem with the wiring harness. It’s possible the electrical anomalies and the scanner malfunction are related to a larger electrical system issue. My current troubleshooting plan is to first inspect and potentially replace the wiring harness, checking for any obvious signs of damage or corrosion. If that doesn’t resolve the issue, replacing the ECM would be the next logical step. If, after these measures, I’m still unable to pull codes and get the engine running, it might be time to consult a professional mechanic.
Has anyone experienced similar issues when using an Android OBD2 scanner on a 7.3 diesel engine of this era? Any advice on a logical troubleshooting order, or specific areas to investigate, would be greatly appreciated before I resort to more drastic (and potentially expensive) measures.
