Printable View
I'm getting this Error code P167F "Non-OEM programming detected.", the truck is a 2016 Heavy Duty 6.7L
the truck runs great for 10-15min and suddenly I get the error and the truck goes into a protected mode. what should I do in order to avoid this error
thanks in advance
That's an interesting one. I think another module is playing baby sitter for ford. Most flashes don't have thus issue. I can't find to much info on it specifically.
Can you disable it in the DTC list?
Yeah, I did try that. I don't get the check engine light now but the protected mode is still happening.
and if I go back to stock everything is normal again
Please e-mail support and reference this thread.
Have you turned the code off in the dtc list?
Just checking to see if this ever got resolved, I have a friend with a 16 that wants to try some programing.
Thanks
I have not gotten a ticket related to this issue yet.
Hello, I dropped an email to support to see if you have anything on this.
I'm having this pop up as well for a Very minor adjustment and correcting the speedo only.
What triggers this one? Someone is babysitting us lol.
Does this show up in an OBDII emissions scan as disabled?
There is like Nothing useful that comes up in searches for this that I have found so far.
Thx.
So, you flash the truck, now a P207F code sets? P207F is a reductant quality code.
I'm sorry, as the OP, I have P167F "Non-OEM programming detected" after tune.Quote:
Originally Posted by bradearlywine
LOL sorry IDK where I picked up the other code. I spaced it.Quote:
Originally Posted by X E Ryder
There are enough to make one's head spin - was good intent tho, thx!Quote:
Originally Posted by bradearlywine
2016 f250 Same issue minor changes and p167f DTC thrown. Any update on this?
Did you change anything related to the tire size or try re-calibrating the speedometer?Quote:
Originally Posted by Jwilliams
I changed the speed limiter and added 5% pulse width. That's it.
Can you Post your tune so i can look at it and see if there's a issue? It might be that you increased it outside of the parameter limits which creates the problem.