There is only one thread with this code in the search. At the end of that thread one person got this code at 27,000 miles. Today I got an engine light and a P04DB code. The truck has 27,000 miles. The regen had started about 2 minutes before I had to park and wait at school. When I left school the soot level was at 100%. I pulled out on the highway and the regen restarted and then a few seconds later TorquePro told me there was an engine code. The engine light went out shortly after the regen started. I drove it on the highway at speed until the regen finished and soot was back below 18%. I drove it the long way home until all the EGTs were at an acceptable temp and shut it down. I assume the code was related to the the fact that the regen didn't complete or something. Any ideas? Thanks in advance.

 

Copied:

The 6.7L diesel engine has a crankcase ventilation separator mounted on the driver side rocker cover, with a tube connecting the separator to the fresh air inlet of the turbocharger. The tube on the separator side has a tamper proof collar installed and is plastic welded to the separator. On the fresh air inlet side, a hall effect sensor is present, to detect connection to the inlet casting assembly. The tube cannot be disconnected on the separator side, and if it is disconnected from the inlet casting, a P04DB code is set, as sensor output drops below a calibrated threshold. There are also circuit range checks, P04E2 and P04E3 to detect shorts to ground, or short to battery/disconnected sensor, respectively.

Crankcase Ventilation Monitor
DTCs
P04DB – Crankcase Ventilation System Disconnected
P04E2 – Crankcase Ventilation Hose Connection Sensor Circuit Low
P04E3 – Crankcase Ventilation Hose Connection Sensor Circuit High

Monitor Execution
Once per driving cycle – P04DB
Continuous – P04E2, P04E3
Monitor Sequence None
Sensors OK P04DB - CVM (P04E2, P04E3)
Typical Monitoring Duration 2 sec

 

See page 108

http://www.fordservicecontent.com/fo...DOBDSM1401.pdf

 

Strange. I haven't even opened the hood since putting washer fluid in about 2 weeks ago. I guess I'll take a look and see if it somehow got disconnected.

 

I can't see anything out of place. No codes and no lights today. I guess I may just mark it up, like the last one, as a computer glitch.

 

So TorquePro keeps telling me the code is back but I haven't had an engine light. Everything seems to be operating normally. I guess its time for a dealer visit.

 

I had the same CEL code recently - light came on but went off after several engine stop. Happened twice. So I had dealer check for stored codes when I had truck in for an oil change and they found this code. Replacement Part is apparently on nationwide back-order.

 

Thanks for the info. I haven't had another engine light and now the code is gone according to TP. Apparently it is an intermittent problem. If the engine light doesn't come on I assume anyone not monitoring with some type of device will never know there is a problem.

 

Its probably just your sensor went bad. I've had the same problem with mine as well and have checked all my hoses when it comes on and nothing has ever actually been disconnected.

 

 

I've been getting the P04DB code for the last year. Last December Ford released the the Customer Satisfaction Program (aka voluntary recall) 17M04 above so I printed out the information and scheduled service at my local Ford dealership. When scheduling the appointment, they didn't know about any recalls or extended warranty about the CCV sensor so I had to tell them about the 17M04 program. They scheduled the repair. When I took the vehicle in they told me there was a $140 diagnostic fee if I decided to not have the work done there (not applicable to me but I thought this was a bit high). After leaving the truck with them for an entire day, I finally called back and got the status (they had my phone number wrong), they wanted to replace the CCV sensor and starting quoting me prices of $110, etc. This guy was just some service department manager and didn't know that they had to replace the entire CCV filter because the sensor is fixed to the CCV hose and the CCV hose is fixed to the filter box. I again had to tell them about the recall/customer service program above and they fell in line. They didn't have the part in-stock so they had to order it, would be another day. Finally got my vehicle back on day 2 with $0 repair cost. Yay! They got it right finally!

CEL is no longer on, we'll see how long it lasts. The warranty on this part is good to 120,000 miles or 11 years, whichever comes first. I'm at 73k so still have plenty of time left.

 

Just got this code today. Did a search here on FTE and poof there it is. FTE is TOPS in my book! And it's a freebee fix. I'll take a nap now.

 

Just got mine replaced yesterday. I was having serious shifting problems going uphill under load. The transmission would jerk so bad going from 6th gear to 5th and the last incident all the way to 3rd gear. It would jerk so bad that I thought the airbags would inflate. Anyway I got tired of dealing with it so I took it to the dealer and had them do a transmission service ($310.00) and they checked for metal in the pan and replaced the screen and put in new fluid. They did not find any shavings in the pan and the transmission wasn't throwing a code. They did find the 17M04 error with the P04DB code and replaced the crankcase collar and reprogrammed the PCM. I am hoping that this will solve my issues with the transmission shifting under load.

 

Just did a delete and installed h&s tuner, truck is throwing a P04db code (no others).. once cleared the code will stay off until I re start the truck in which it throws the code again. Has anyone heard of an issue like that being cause by a tuner? I am replacing the CCV hoping that will clear the code.

 

ericjryan01, did replacing the CCV clear the code for you?

I've got a 2015 with 208,xxx miles on it, so its no longer covered by the recall or any program, but I've got the P04DB code. I clear it with my scanner, but it comes back when I restart the truck. I'm also looking to a delete, so we're on similar paths.