Duper Suty
Registered User
TL;DR This particular post is asking the question "Did I accidentally clear the codes trying to link the obd-2 while the truck was running"
Reason I'm asking is this may point me in a positive direction for further diagnosis.
To frame the whole situation, I have a 02/97 super duty 2wd E4OD I've gone through the gauntlet of electrical and mechanical troubleshooting for sudden loss of 2nd and drive. Downloaded Forscan and got an elm327 OBD-II through the mail to read codes in an effort to see if any were stored (no CEL or flashing OD light). I have a list of what I've done to troubleshoot I'm organizing into chronological order I will provide once I neaten it up.
Anyway, I made the rookie mistake of running the truck while it was connecting to the obd-2 port. It shut down once it linked and the dash lights went nuts. I closed the Bluetooth link, shut key off, and removed the obd-2 adapter. Truck did restart on its own and cycled the gauges and dash lights fine. I wanted to see if the rest of it was okay afterwards, so I drove it around the block and Drive came back. It drove like it was factory fresh for about 1.3 miles, where I really hammered it going uphill and the exact issues I was chasing returned. Limped it back home, shut it down but put key on and pulled codes with Forscan.
Still chasing issues, but I'm curious if I accidentally did something along the lines of clearing the codes when I linked the obd-2 and it shut down. Codes I pulled after I got it back home are provided in a posted screenshot just for relevancy
Again, I have notes on what I've done in an effort to resolve this that I will compose into its own post.
Reason I'm asking is this may point me in a positive direction for further diagnosis.
To frame the whole situation, I have a 02/97 super duty 2wd E4OD I've gone through the gauntlet of electrical and mechanical troubleshooting for sudden loss of 2nd and drive. Downloaded Forscan and got an elm327 OBD-II through the mail to read codes in an effort to see if any were stored (no CEL or flashing OD light). I have a list of what I've done to troubleshoot I'm organizing into chronological order I will provide once I neaten it up.
Anyway, I made the rookie mistake of running the truck while it was connecting to the obd-2 port. It shut down once it linked and the dash lights went nuts. I closed the Bluetooth link, shut key off, and removed the obd-2 adapter. Truck did restart on its own and cycled the gauges and dash lights fine. I wanted to see if the rest of it was okay afterwards, so I drove it around the block and Drive came back. It drove like it was factory fresh for about 1.3 miles, where I really hammered it going uphill and the exact issues I was chasing returned. Limped it back home, shut it down but put key on and pulled codes with Forscan.
Still chasing issues, but I'm curious if I accidentally did something along the lines of clearing the codes when I linked the obd-2 and it shut down. Codes I pulled after I got it back home are provided in a posted screenshot just for relevancy
Again, I have notes on what I've done in an effort to resolve this that I will compose into its own post.