ElmScan 5 OBT plugin causes engine shutdown, (?)
Thread Starter
|
Tuned
Joined: Aug 2008
Posts: 276
Likes: 9
From: Alaska (not Anchorage)
ElmScan 5 OBT plugin causes engine shutdown, (?)
I have just hooked up my ElmScan 5 OBT plugin to my truck. I've had it for a while, but never tried it. I installed the ScanTool.net software on a laptop and fired the truck up.
Everything seemed to work fine until I selected the next set of sensors to receive output when the truck shutdown totally. I disconnected the OBD plugin and after several cranks, restarted my motor. Usually the motor fires right up on first crank. I hooked the OBD cables back up, looked at the first set of sensor data, switched to the second set of data, and the motor died immediately. It took about 20 seconds of cranking to restart.
This is very, very weird. This truck always starts great. Has anyone else experienced similar problems with this or other OBD tools?
Everything seemed to work fine until I selected the next set of sensors to receive output when the truck shutdown totally. I disconnected the OBD plugin and after several cranks, restarted my motor. Usually the motor fires right up on first crank. I hooked the OBD cables back up, looked at the first set of sensor data, switched to the second set of data, and the motor died immediately. It took about 20 seconds of cranking to restart.
This is very, very weird. This truck always starts great. Has anyone else experienced similar problems with this or other OBD tools?
Thread Starter
|
Tuned
Joined: Aug 2008
Posts: 276
Likes: 9
From: Alaska (not Anchorage)
Here's the link to their site: ScanTool.net LLC - Scan Tools, PC, iPhone, & Android based OBD-II (OBD2) Interfaces, OBD diagnostic software
At the moment, the "box" that plugs into the OBD port does not appear to be getting input from the truck. All fuses associated with OBD and PCM in the truck are fine. Moving the box to my wifes car and plugging it into her OBD port, I still do not get flashing LEDs on the box.
I assume that something in the Powerstroke OBD system may have fried the box.
At the moment, the "box" that plugs into the OBD port does not appear to be getting input from the truck. All fuses associated with OBD and PCM in the truck are fine. Moving the box to my wifes car and plugging it into her OBD port, I still do not get flashing LEDs on the box.
I assume that something in the Powerstroke OBD system may have fried the box.
Cargo Master
Joined: May 2010
Posts: 3,047
Likes: 9
From: Snohomish, WA
You may find this happens often with that type of software. I have heard many people complain about that with phone apps and the OBD II interfaces they use.
It looks like that software has the option to be upgraded to get Ford specific codes. Did you purchase that upgrade too? If not, you will only get a few (RPM, Boost, MPH) parameters on the basic OBD II platform. You may be able to get into some of the generic body codes too.
Looking at the price for the software, upgrade and adapter it is close to the same price as AE. If it works on the Ford Specific Codes, it would be a handy little tool for those on the go.
It looks like that software has the option to be upgraded to get Ford specific codes. Did you purchase that upgrade too? If not, you will only get a few (RPM, Boost, MPH) parameters on the basic OBD II platform. You may be able to get into some of the generic body codes too.
Looking at the price for the software, upgrade and adapter it is close to the same price as AE. If it works on the Ford Specific Codes, it would be a handy little tool for those on the go.
Trending Topics
Post Fiend
Joined: Sep 2003
Posts: 6,096
Likes: 26
From: Mesa AZ
I suggest you call the manufacturer and see what they recommend. My guess is the software is running a VIN check when it changes to the next set of systems and that is causing the shutdown. The 7.3 PCM isn't compatible with the VIN lookup routine.
FTE Stories
Ford Trucks for Ford Truck Enthusiasts
AEV FXL Super Duty - the Super Duty Raptor Ford Doesn't Make
Brett Foote
Lobo Vs Lobo: Proof the F-150 Lobo Should Be Even Lower!
Michael S. Palmer
Ford's 2001 Explorer Sportsman Concept Looks For a New Home
Verdad Gallardo
10 Best Ford Truck Engines We Miss the Most!
Joe Kucinski
2026 Shelby F-150 Off-Road: Better Than a Raptor R?
Brett Foote
2027 Super Duty Carhartt Package First Look: 12 Things You NEED to Know!
Michael S. Palmer
10 Most Surprising 2026 Ford Truck Features!
Joe Kucinski
Top 10 Ford Trucks Coming to Mecum Indy 2026
Brett Foote
5 Best / 5 Worst Ford Truck Wheels of All Time
Joe Kucinski
Thread Starter
|
Tuned
Joined: Aug 2008
Posts: 276
Likes: 9
From: Alaska (not Anchorage)
Okay...I think I've got this figured out.
The Elmscan 5 Bluetooth is fine. The problem was that when I'd upgraded the software, the serial port assignments somehow got bolluxed so my laptop was unable to send a PID request to the OBD processor in the truck, (or my wife's Subaru)...so no flashing lights indicating data flowing from car to computer.
Earlier this evening I purchased the PRO version of Torque for use on my Android phone to read OBD2 codes. I really like it. I'll do a write up regarding how to configure for our trucks and post in the next few days.
The Elmscan 5 Bluetooth is fine. The problem was that when I'd upgraded the software, the serial port assignments somehow got bolluxed so my laptop was unable to send a PID request to the OBD processor in the truck, (or my wife's Subaru)...so no flashing lights indicating data flowing from car to computer.
Earlier this evening I purchased the PRO version of Torque for use on my Android phone to read OBD2 codes. I really like it. I'll do a write up regarding how to configure for our trucks and post in the next few days.
Thread
Thread Starter
Forum
Replies
Last Post
444dieselrod
1999 - 2003 7.3L Power Stroke Diesel
9
Mar 13, 2005 10:39 PM
