Check Engine Light

Reply Subscribe

Thread Tools

Search this Thread

Mar 21, 2017 | 08:25 AM

Poncho450

Thread Starter

Lead Driver

Joined: Oct 2014

Posts: 5,946

Likes: 1,359

From: NY/Canada border

Check Engine Light

Had a CEL appear yesterday morning. My code reader shows an O2 sensor issue - P2197 and P2629.
Dropped it at the dealer this morning. Never mentioned that I'd read the codes just to see what their verdict is. He said that they don't see the 6.2's that often so he couldn't even run down some common problems for me. But he did say that the diesels have been having some DPF issues, though he didn't get into specifics because I don't drive one so it doesn't really matter to me.
Truck has 6500 miles on it. Anyone else had low mile 6.2 issues?

Mar 21, 2017 | 10:19 AM

seville009

Logistics Pro

Joined: Nov 2004

Posts: 4,795

Likes: 47

2011 F350 6.2l 90,000 miles.....no issues.

At 6,500 miles, yours is still relatively new, so it may simply be something that was slightly defective or not installed correctly at the factory that is just now showing up. My guess is it'll be a simple fix.

Mar 21, 2017 | 05:35 PM

Poncho450

Thread Starter

Lead Driver

Joined: Oct 2014

Posts: 5,946

Likes: 1,359

From: NY/Canada border

Quote:

Originally Posted by seville009

They did call this afternoon. It is indeed an O2 sensor. Part will be here in the morning. They want to look over some other wiring while it's on the lift.
I did crawl under the truck last night just to see if there were any obvious wire breeches. Didn't seem to be, but there are a few wires running to each sensor, all covered by insulation. That insulation is pulled back on all 4 sensors enough that you can see the individual wires inside of it. One was pulled back about an inch.

Mar 22, 2017 | 02:00 PM

Poncho450

Thread Starter

Lead Driver

Joined: Oct 2014

Posts: 5,946

Likes: 1,359

From: NY/Canada border

All fixed. From the paperwork- "Pinpoint test for code P160A. Perform relearn. Retest. Received code P0059 and P2626. Perform pinpoint test DZ1-DZ10. Replaced Bank 2 O2 sensor. Clear codes. Reset KAM. Retest OK".
The P160A is an ECM activation error. I wonder if my 5 Star set that thing? From what I can find online it does not set a CEL, but can be seen and cleared with IDS. Now I'm hesitant to reinstall my daily/tow tune for a vacation trip in a couple days. Nobody at the dealer mentioned a word, but I don't want to chance voiding the warranty. 5 Star guy? Anyone care to weigh in on this?
Looks like at least one person had a bad O2 sensor on a low mile Super Duty: https://www.ford-trucks.com/forums/1...ode-p2626.html

Mar 22, 2017 | 02:20 PM

seville009

Logistics Pro

Joined: Nov 2004

Posts: 4,795

Likes: 47

I've got a 5 Star tune on my 2011 6.2l; haven't had any CEL with it (or without it).

Mar 22, 2017 | 02:42 PM

Poncho450

Thread Starter

Lead Driver

Joined: Oct 2014

Posts: 5,946

Likes: 1,359

From: NY/Canada border

Quote:

Originally Posted by seville009

I've got a 5 Star tune on my 2011 6.2l; haven't had any CEL with it (or without it).

A few things that I found online say that the P0160 doesn't set a CEL. And my BlueDriver OBD code reader didn't see it. But apparently Ford's IDS does. This has me wondering if making changes in the ECM through a tuner set off this code to alert Ford.
I reset it back to factory tune before I took the truck in, but apparently that code lurks around anyway.

Mar 22, 2017 | 02:43 PM

Chuck's First Ford

Postmaster

Joined: Jul 2015

Posts: 4,392

Likes: 22

From: very South Texas

could be Simple bad connector or sensor.. and nothing to do with your "Tuner"...

proceed as normal..

till proven otherwise.

my understanding.... some codes anything can read... some only Ford can read... (legal stuff)..... like for car crashes...

most can be deleted with a 2 hour battery disconnect... but NOT Everything..