Injector Buzz test from android
Laughing Gas
Joined: Jul 2012
Posts: 856
Likes: 63
From: Los Angeles/Ventura, CA
"On sale" for $79.95 at the website you referenced. I hope this does the trick.
It's a Van Gogh
Joined: Feb 2010
Posts: 7,798
Likes: 1,331
From: Elk Grove, CA
The stalling while pulling codes with Torque issue is weird, but I have a hypothesis. I can pull codes while running on my 02, no problem. Done it a dozen times. Yet when I tried pulling codes on my buddy's 02, same phone and same $13 fleabay OBDII adapter, killed it every time. Both trucks are 02 with AT and GPCM. Don't know his PCM code but it's gotta be the same family. Only difference I know is mine has a chip and RF chokes due to HIDs, his is bone stock. So I'm thinking the RF chokes on my PCM protect if from interference from the cheap adapter. And a higher quality adapter like the MX just doesn't generate the same electronic noise.
Even so I think the best advice is never pull codes when rolling. It can wait til you're stopped.
Once in a moment of caffeine fueled lucidity I figured out the Gauge Pro interface and read some PIDs. Never did find how to do a buzz test tho. Next time it had forgotten my settings and I no longer had the acumen (or 20 minutes) to get it working. Maybe I should have my gamer teenage daughter take a crack at it.
Even so I think the best advice is never pull codes when rolling. It can wait til you're stopped.
Once in a moment of caffeine fueled lucidity I figured out the Gauge Pro interface and read some PIDs. Never did find how to do a buzz test tho. Next time it had forgotten my settings and I no longer had the acumen (or 20 minutes) to get it working. Maybe I should have my gamer teenage daughter take a crack at it.
Thread Starter
|
Posting Guru
Joined: May 2013
Posts: 1,199
Likes: 2
From: Oklahoma
Great advice here! The PCM doesn't understand the request and is causing the stumble/stall.
Laughing Gas
Joined: Jul 2012
Posts: 856
Likes: 63
From: Los Angeles/Ventura, CA
Just got the ScanTool MX and am experiencing the same problem with the SES light being activated when I pull fault codes. It's a bit disheartening given the cost.
The few times I tried, I did notice the option to deactivate mode $09 sensors using the OBDwiz software seems to keep the SES from tripping.
I really would like to get this issue nailed down for the group.
I'll try to call the ScanTool folks in the morning to see if they can help.
The few times I tried, I did notice the option to deactivate mode $09 sensors using the OBDwiz software seems to keep the SES from tripping.
I really would like to get this issue nailed down for the group.
I'll try to call the ScanTool folks in the morning to see if they can help.
Hotshot
Joined: Jan 2011
Posts: 18,849
Likes: 179
From: Puget Sound
I may be mistaken, but I thought I saw the same option in Torque settings. I recall clicking that box.
Laughing Gas
Joined: Jul 2012
Posts: 856
Likes: 63
From: Los Angeles/Ventura, CA
There are two options you may be remembering: (1) an option to hide mode $01 sensors that are not supported, and (2) an option for Ford F150 2000/01 ECU bug workaround. I do not choose the first option but do choose the second. I have fooled around with this configuration and this does not solve the problem.
Still waiting on a call back from ScanTool (which does its best to avoid publishing its phone number).
David
Hotshot
Joined: Jan 2011
Posts: 18,849
Likes: 179
From: Puget Sound
I just went through my settings again, and I spotted the $01 you were referring to. I also noticed I disabled any and all fancy-schmancy settings having to do with figuring the MPG. I have enough devices lying to me without asking the tablet to do the same. I set Torque to link to my specific BT adapter, not just hunt for any 'ol adapter in range. I also set my vehicle protocol to SAE J1850-PWM (41.6K baud). I did not use the Ford F150 2000/01 ECU bug workaround, and here's why:
I don't have one of those. I don't know what the "workaround" is, but I don't want a piece of it.
I don't have one of those. I don't know what the "workaround" is, but I don't want a piece of it.
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
Laughing Gas
Joined: Jul 2012
Posts: 856
Likes: 63
From: Los Angeles/Ventura, CA
Tugly,
Thanks so much for your reply.
If you wouldn't mind pulling fault codes with your Torque/OBD setup and reporting back whether it trips the SES light, it would be appreciated.
The additional empirical evidence might help others decide whether it's truly worth spending the money on the scanTool MX versus a generic device. If the problem is rooted in the software, than we all might do as well (or at least almost as well) with the generic version.
If the mode $09 sensors are the problem (overloading the BUS), I'll report back.
David
Thanks so much for your reply.
If you wouldn't mind pulling fault codes with your Torque/OBD setup and reporting back whether it trips the SES light, it would be appreciated.
The additional empirical evidence might help others decide whether it's truly worth spending the money on the scanTool MX versus a generic device. If the problem is rooted in the software, than we all might do as well (or at least almost as well) with the generic version.
If the mode $09 sensors are the problem (overloading the BUS), I'll report back.
David
Hotshot
Joined: Jan 2011
Posts: 18,849
Likes: 179
From: Puget Sound
I just checked my OBDLink app and it has the ability to program PIDs like Torque. I don't recall it having this ability before, but I do remember being disappointed that there was no way to add IPR to the app. I also noticed there are some advanced Ford PIDs with the same formulas as Torque... very interesting. With this new feature, I want to explore the possibilities.
On the subject of $09, you really want that disabled. Pulling the VIN is part of this mode, and anybody with AE can confirm pulling the VIN is a system crasher.
I'll be in the driveway later today and I'll try a few things.
On the subject of $09, you really want that disabled. Pulling the VIN is part of this mode, and anybody with AE can confirm pulling the VIN is a system crasher.
I'll be in the driveway later today and I'll try a few things.
Laughing Gas
Joined: Jul 2012
Posts: 856
Likes: 63
From: Los Angeles/Ventura, CA
The next interesting question is why the crash happens. I have a colleague whose company manufactures vehicle locating devices and they pull the VIN (to make sure their device hasn't been put into a different vehicle). I have yet to speak with the system engineer but I believe the solution may lie in when the command is issued. If issued when other codes are pulled, the BUS may get overloaded resulting in the crash. If we can share the solution (assuming they would allow me to do so) with AE/Torque, we might get a workaround if the app developers are willing to make a change.
David
Hotshot
Joined: Jan 2011
Posts: 18,849
Likes: 179
From: Puget Sound
Remember, we're talking about 15 years ago - so it's hard to say if they accommodated loading a VIN into the PCM to begin with. The PCM just might see a VIN poll as an illegal command, and issue forth a middle finger.
Thread
Thread Starter
Forum
Replies
Last Post
LCA078
1999 - 2003 7.3L Power Stroke Diesel
2
Apr 24, 2018 07:05 AM