Limp Home Mode

[Jackpine]

Looks just like what Sburn had, doesn't it?

So, by hitting the reset button for your message center, you made Failsafe mode go away?

This is sounding more like a glitch in the PCM, rather than something in a tune.

Wish we knew if Bill found anything in Sburn's files.

Since Lars is going to post a note in the Mod's board, maybe Bill will be able to tell us something.

- Jack

[Sburn]

Originally Posted by JackandJanet

Looks just like what Sburn had, doesn't it?

So, by hitting the reset button for your message center, you made Failsafe mode go away?

This is sounding more like a glitch in the PCM, rather than something in a tune.

Wish we knew if Bill found anything in Sburn's files.

Since Lars is going to post a note in the Mod's board, maybe Bill will be able to tell us something.

- Jack

As a followup, this error only happened the one time I reported it. And that was with canned #2 tune.

I'm now using a custom tune, and have never had it happen with that, period. I've also never tried to adjust that tune via the Custom Setting menu, since it's perfect for me as Bill wrote it.

[Jackpine]

Thanks, Sburn. And, I guess Bill never found anything wrong, did he?

- Jack

[88Racing]

If you go over to f150online and type in "p2106" or "p061" into the search bar.
You will see a bunch of posts about and mostly refering to edge and canned level 2 tow.
Back then Bill was looking at it when he was working for edge. I wonder if its a glitch that really never got worked out? But it kinda points the finger at the drive by wire system also.

Lars

[Sburn]

Originally Posted by JackandJanet

Thanks, Sburn. And, I guess Bill never found anything wrong, did he?

- Jack

Not that I ever heard.

[coolio4433]

After setting level 2 (nothing custom, just basic level 2) and driving 1/2 mile I got the p061B code as well.

Pulled into a gas station, set back to stock, ran my errand.
When I got home I put it back to level 2 and drove around a bit and it was like it never happened.

I guess I won't worry too much about this issue unless it happens again or frequently.

[Power Hungry]

I had addressed this in an earlier thread, but can't seem to find it at the moment.

Anyway, from what we've seen this phenomenon seems to happen immediately after programming a truck and driving it for the first time, especially under hard acceleration. The PCM triggers the P061B DTC, pops the "wrench" on the dash, and the engine goes limp. After cycling the key, the problem usually doesn't reoccur until the next programming session.

As near as I can tell, the PCM is detecting a disparity in calculated torque versus a preset estimated torque table witch triggers the P061B DTC. Why this usually only happens once is still a bit of a mystery and there are minor corrections we can make to eliminate this issue entirely.

It should be noted that we only ever see this problem on vehicles with CAIs and usually only when running canned tunes, although some earlier custom tunes may exhibit this issue as well.

As mentioned, any custom files with this issue can be modified to resolve this issue. Just let me or Corey know and we'll get it on the rebuild list.

Take care.

[coolio4433]

Good to know. Thanks Bill.

I won't worry too much about the code then, and when my custom tune is ready it sounds like I shouldn't have this problem anyways.

[88Racing]

Originally Posted by Power Hungry

I had addressed this in an earlier thread, but can't seem to find it at the moment.

Anyway, from what we've seen this phenomenon seems to happen immediately after programming a truck and driving it for the first time, especially under hard acceleration. The PCM triggers the P061B DTC, pops the "wrench" on the dash, and the engine goes limp. After cycling the key, the problem usually doesn't reoccur until the next programming session.

As near as I can tell, the PCM is detecting a disparity in calculated torque versus a preset estimated torque table witch triggers the P061B DTC. Why this usually only happens once is still a bit of a mystery and there are minor corrections we can make to eliminate this issue entirely.

It should be noted that we only ever see this problem on vehicles with CAIs and usually only when running canned tunes, although some earlier custom tunes may exhibit this issue as well.

As mentioned, any custom files with this issue can be modified to resolve this issue. Just let me or Corey know and we'll get it on the rebuild list.

Take care.

That's probably why we say not to hammer it and be nice when running L2 canned tune and a cai.

Lars

[MercedesTech]

Originally Posted by Power Hungry

I had addressed this in an earlier thread, but can't seem to find it at the moment.

Anyway, from what we've seen this phenomenon seems to happen immediately after programming a truck and driving it for the first time, especially under hard acceleration. The PCM triggers the P061B DTC, pops the "wrench" on the dash, and the engine goes limp. After cycling the key, the problem usually doesn't reoccur until the next programming session.

As near as I can tell, the PCM is detecting a disparity in calculated torque versus a preset estimated torque table witch triggers the P061B DTC. Why this usually only happens once is still a bit of a mystery and there are minor corrections we can make to eliminate this issue entirely.

It should be noted that we only ever see this problem on vehicles with CAIs and usually only when running canned tunes, although some earlier custom tunes may exhibit this issue as well.

As mentioned, any custom files with this issue can be modified to resolve this issue. Just let me or Corey know and we'll get it on the rebuild list.

Take care.

Bill, How ya been ? Its been a long time since we last talked. Hope everything is going well with you and yours.


I was probably one of the first people to report this problem to you. It happened with my canned tuned, and then continue to happen with my custom tunes. I do NOT have CAI. But, I have learned to live with it, as it is really no big deal. When you first load a custom tune, realize it will go into limp home mode. I always set my custom tunes in large open parking lots. Once it is loaded, I drive off. Within a few minutes the wrench is thrown. I put it in park, go into diagnostics on the Gryphon. I clear any and all trouble codes. Turn off truck. Restart truck and you will be good to go. It has taken me one or two times to get it, but that is why I advise any tune change to happen in a large open lot. That way you have plenty of room to test drive it after each loading session. Just my 2 cents.

If there is a way to fix this, I would be interested in it.