Torque

Forums

Forums

Guest  

Show or hide header
Welcome Guest, posting in this forum require registration.




Torque » Torque OBD ECU Scanner » Torque Discussion / Ideas » First run problems: wrong readings, stops motor while driving

Pages: [1]
Author Topic: First run problems: wrong readings, stops motor while driving
jimjames
Member
Posts: 7
Post First run problems: wrong readings, stops motor while driving
on: November 11, 2017 (GMT)

Okay, finally got my Samsung Note 3 with Torque Pro set up on my 2001 7.3 Excursion (223,000).In no particular order, coolant temp reads 368.6 F, battery varies from 14.3, down to 1.1v (and other absurd readings and it is a relatively new alternator) but the issue is my first trip to town, the motor sputtered and quit. Put in neutral (40 mph), tried to start, did not, pulled over, turned ignition off, sat a minute, started right up. ALso, for a bit, blinking red icon where it shows the blue dealies (the little car)

Thoughts??

74 YO, world traveler, living in a log home in Wyoming.

piemmm
Administrator
Posts: 6629
Post Re: First run problems: wrong readings, stops motor while driving
on: November 11, 2017 (GMT)

Hi!

Unfortunately this is a known problem with the Ford ECUs (this is normally limited to the F1/250 ECUs) built around Feb-April 2001.

The ECU is running a bugged firmware which causes it to reboot when used with OBD

Unfortunately Ford are not willing to fix the issue for this ECU. There is a special setting (Fx50 ECU workaround) in the main app settings, which tries to avoid triggering the ECU bug, though I can’t recommend you use any OBD app with that vehicle due to the ECU reboot issue

Capp777
Member
Posts: 2993
Post Re: First run problems: wrong readings, stops motor while driving
on: November 11, 2017 (GMT)

Check under Adapter Status icon information
to see if any errors are being reported.

I don’t believe your diesel is fully OBDII compliant
and I suspect unrecognized pids and mode 09
calls might be causing the stuttering. I would
test your custom pids KOEO and remove any that
are not returning valid data.

There are special settings which might also apply
so I suggest verifying your settings as well.

There is a thread with additional info for the 7.3
so I will try to find it and add the link below. You
should read to the end of the thread before adding
any of the pids mentioned as they were a work in
progress.

https://torque-bhp.com/forums/?wpforumaction=viewtopic&t=3903.0

jimjames
Member
Posts: 7
Post Re: First run problems: wrong readings, stops motor while driving
on: November 11, 2017 (GMT)

Thanks, guys. Appreciate your efforts….

74 YO, world traveler, living in a log home in Wyoming.

jimjames
Member
Posts: 7
Post Re: First run problems: wrong readings, stops motor while driving
on: November 12, 2017 (GMT)

“Unfortunately this is a known problem with the Ford ECUs (this is normally limited to the F1/250 ECUs) built around Feb-April 2001.” I might note, the Excursion is built on an F-250 chassis, so I will assume it’s equivalent to the F-250 pickup of that time period. I’ll check the dates tomorrow…..

74 YO, world traveler, living in a log home in Wyoming.

jimjames
Member
Posts: 7
Post Re: First run problems: wrong readings, stops motor while driving
on: November 12, 2017 (GMT)

Well, as luck would have it, date of mfg on this Excursion is March, 2001

Might note I have an Edge Evolution, for years, tuned to Extreme (best mileage on extreme!) and it showed me the codes for two glow plug problems (Replaced all 8 a month ago)

So, as to the Torque, I’ll use it for diagnostics from time to time but not run it while driving. And, for .95, I can live with that.

Thanks for the feedback, guys, appreciate it

74 YO, world traveler, living in a log home in Wyoming.

jimjames
Member
Posts: 7
Post Re: First run problems: wrong readings, stops motor while driving
on: November 12, 2017 (GMT)

By the way, when I tap Adapter Status icon, it kills the motor, just an FYI

74 YO, world traveler, living in a log home in Wyoming.

Capp777
Member
Posts: 2993
Post Re: First run problems: wrong readings, stops motor while driving
on: November 12, 2017 (GMT)

KOEO… there is a mode 09 call for VIN number
in the Adapter Status information.

piemmm
Administrator
Posts: 6629
Post Re: First run problems: wrong readings, stops motor while driving
on: November 12, 2017 (GMT)

Hi!

The mode 09 calls aren’t sent if you tick the “Ford F150/F250 2000/01 ECU bug workaround” in the “Special Settings/Options” part of the app :-)

Capp777
Member
Posts: 2993
Post Re: First run problems: wrong readings, stops motor while driving
on: November 12, 2017 (GMT)

Is this true for auto check for DTCs too?

I assumed that since his engine had died
that mode 09 was the culprit and the special
setting had not been used.

piemmm
Administrator
Posts: 6629
Post Re: First run problems: wrong readings, stops motor while driving
on: November 12, 2017 (GMT)

Hi!

If you have the “Periodically scan for faults” option ticked in the settings (it should be off by default) then it will still send a request for fault codes

If that’s a problem I can add a wrapper around it to also not send them when that option is ticked (I’m guessing the pending request is causing a fault, and the default current faults request is ok? – not having easy access to the bugged version of this vehicle makes adding features a bit slow)

Capp777
Member
Posts: 2993
Post Re: First run problems: wrong readings, stops motor while driving
on: November 12, 2017 (GMT)

I have read where other 7.3 users had to
make sure that option was off to prevent
the same issue from happening. Does that
code include a mode 09 VIN call for its
report as well?

I’m thinking it was user MJ in the linked thread
above whom mentioned this. Next to last post
on page 8…

Quote from m j on January 28, 2014
I need to experiment with torque converting “as needed” I guess
the only thing I want in celcius is ambient temps from the IAT.

torque kills the engine (not really) when it attempts to read DTC on our PCM.
auto scan for DTC option, after deselecting that I have not had an issue.

for a manual trans it doesnt really ‘kill the engine’.
if you are travelling and torque does its auto DTC scan the PCM resets, you get a dead pedal and if you are in gear the dead engine decels the vehicle. if you tap the throttle a few times it will come back to ‘life’ and the road speed will have kept the motor spinning so it just ‘wakes back up’.
I did a 2500km trip towing a car trailer and part way through discovered what was causing the issue

End Quote.

piemmm
Administrator
Posts: 6629
Post Re: First run problems: wrong readings, stops motor while driving
on: November 12, 2017 (GMT)

Hi!

Nope it doesn’t do a 09 request for the fault code scanning, unless you go to that activity itself and perform a scan manually, it’s simply a current and pending codes request for the ‘periodically check’ option – it’d be handy to know if the current 03 request works (whereas I suspect the pending may cause the ECU bug to trigger), as that means the option will still be able to work. For the moment I’ll disable it if the workaround special option is ticked until I know any more as that’s probably the best thing at the moment

Capp777
Member
Posts: 2993
Post Re: First run problems: wrong readings, stops motor while driving
on: November 12, 2017 (GMT)

Maybe jimjames can answer your mode 03
question. MJ hasn’t posted in a long time and
I still drive an OBDI Jeep.

jimjames
Member
Posts: 7
Post Re: First run problems: wrong readings, stops motor while driving
on: November 13, 2017 (GMT)

Gentlemen, thank you for the feedback, I enjoy the new information, the “workarounds” suggested, but I’ll leave things as they are and will test the “when the motor dies, give it a chance and it will kick-start while rolling” suggestion. IF it works, reliably, I’ll just go with what I’ve got. Thanks to all……….

74 YO, world traveler, living in a log home in Wyoming.

Capp777
Member
Posts: 2993
Post Re: First run problems: wrong readings, stops motor while driving
on: November 13, 2017 (GMT)

Jimjames,

I believe Ian is trying to isolate if a mode 03 call
by itself causes an engine stumble. Torque’s
fault scan uses mode 03 and another mode to
read pending codes as well.

There is a send OBD Command display which could
be used to send mode 03 command by itself which
would provide the answer Ian seeks.

Hope something in these posts helped your
situation.

jimjames
Member
Posts: 7
Post Re: First run problems: wrong readings, stops motor while driving
on: November 13, 2017 (GMT)

Thanks, Capp……… I got enough info to overwhelm the issue. As I said, if the motor dying is simply a blip that takes care of itself (restarts while still moving), it’s not a problem. I am rarely driving in a city, here in Wyoming, so the trade off is: do all the changes versus go with what I got to work with……which is what I’ll do……… Thanks, again, to all………

74 YO, world traveler, living in a log home in Wyoming.

Pages: [1]
WP-Forum by: Fredrik Fahlstad, Version: 2.4
Page loaded in: 0.075 seconds.

  Follow me on twitter