When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
2022 F350 with 6.7. Currently in the middle of nowhere Montana. Started the truck yesterday and was greeted with a rough idle, thought it may have just been because it was cold but then a few miles down the road the service engine soon light came on. Started doing some troubleshooting and found that squirrels had made a huge nest in my air intake. Easily blocking 50% of the box. Removed that nest, cleaned out the air filter, and besides a little chewed up foam around the air filter everything seems to be fine. Pulled out Forscan and I’m getting codes P2B15, P2B1D, & P2B13. All the same codes for the cylinder 2, 3, & 7 “injection pulse offset exceeding learned limit”. I cleared the codes, drove 50 miles with no light, but then it immediately came back on upon next start. Cleared the codes again and same thing happened after another drive and restart. Makes sense to me that the injectors were not able to compensate for such reduced airflow and threw codes, but surprised it keeps coming back after I “fixed” it. Any settings I need to reset with Forscan maybe? Or could this be a larger issue I need to troubleshoot? Currently about 3 hrs from the nearest dealer and pulling a 17k trailer. So not easy to get to a dealer.
Likely it was field mice, those damn things get into everything if you're parked out in the wild for a period of inactivity.
Almost sounds like the injector mapping table needs to relearn settings after you corrected the obstruction, which may explain why it runs fine and codes can be cleared until you shut it down and restart. Over time it should relearn, but until then it's likely going to continue throwing those warning codes, perhaps. I'm not sure if performing a forced relearn in ForScan would set a new benchmark for the relearn procedure, but perhaps those more experienced with ForScan could chime in and assist. Try pinging @ZooDad here on the forum, perhaps he can assist with the ForScan question.
Edit: Like just mentioned, inspect all the wiring you can see for damage, as well.
Gone over the engine bay pretty thoroughly. As far as I can tell there’s no chewed wires, but definitely a possibility still. Just through Googling a bunch it sounds like I may need to reset “Minimum Fuel Mass Adaptions All Cylinders”. Rough idle is very intermittent now, as far as I can tell no other abnormalities during the drive. Big snowstorm going through now so I am going to wait to mess with it… with my luck I’d just brick my truck unnecessarily at a bad time.
Almost seems like a wire harness has been nibbled on, but not cut all the way through. That may explain why the CELs come and go like that. Hopefully you can find it and it'll be something simple. Shouldn't have to reset anything. I would think that pulling the battery cables for 15 minutes would reset everything after you cleared the mouse obstruction. Probably just some remaining wires getting random shorts due to being bitten by mice.
2022 F350 with 6.7. Currently in the middle of nowhere Montana. Started the truck yesterday and was greeted with a rough idle, thought it may have just been because it was cold but then a few miles down the road the service engine soon light came on. Started doing some troubleshooting and found that squirrels had made a huge nest in my air intake. Easily blocking 50% of the box. Removed that nest, cleaned out the air filter, and besides a little chewed up foam around the air filter everything seems to be fine. Pulled out Forscan and I’m getting codes P2B15, P2B1D, & P2B13. All the same codes for the cylinder 2, 3, & 7 “injection pulse offset exceeding learned limit”. I cleared the codes, drove 50 miles with no light, but then it immediately came back on upon next start. Cleared the codes again and same thing happened after another drive and restart. Makes sense to me that the injectors were not able to compensate for such reduced airflow and threw codes, but surprised it keeps coming back after I “fixed” it. Any settings I need to reset with Forscan maybe? Or could this be a larger issue I need to troubleshoot? Currently about 3 hrs from the nearest dealer and pulling a 17k trailer. So not easy to get to a dealer.
Thanks for any help or suggestions.
I hope this will help, dealership will take about a half hour, so it can't be that complex and it is an active TSB. I just don't know if ForScan can do this for you
I hope this will help, dealership will take about a half hour, so it can't be that complex and it is an active TSB. I just don't know if ForScan can do this for you
From the video above I'll confirm that field mice like to chew that insulation Rod shows and the mice like to make the home in the valley where he took the nest from. My 16 has had alot of the insulation chewed and removed. I've tried just about all the things he mentioned. Most don't work.
The best thing that works is a miniature Aussie shepherd that thinks it's a cat. He'll let us know there are visitors in the engine area and 2 snap traps at all times in the engine area where ever we are boondocking.
I use this hooked to battery which has helped some but not totally.
I'll use this for reaching in and remove nesting material in the valley area. The metal claw grabs really well.
I'll check the traps every morning and later in the day. I'll bet I've killed atleast 100 a year over the past 8 years easy. The dog has gotten a few mice, squirrels and chipmunks but will always let use know, he inspects the vehicles every trip outside.
Peppermint spray works well to keep them away, but needs to be done almost every other day to keep it strong enough to deter. Peppermint to a rodent is akin to ammonia to us.
Likely it was field mice, those damn things get into everything if you're parked out in the wild for a period of inactivity.
Almost sounds like the injector mapping table needs to relearn settings after you corrected the obstruction, which may explain why it runs fine and codes can be cleared until you shut it down and restart. Over time it should relearn, but until then it's likely going to continue throwing those warning codes, perhaps. I'm not sure if performing a forced relearn in ForScan would set a new benchmark for the relearn procedure, but perhaps those more experienced with ForScan could chime in and assist. Try pinging @ZooDad here on the forum, perhaps he can assist with the ForScan question.
Edit: Like just mentioned, inspect all the wiring you can see for damage, as well.
Thanks guys. Wound up disconnecting the batteries for ~30min. Didn’t clear or reset anything. Tried again, this time turning on headlights and putting a jumper wire between the disconnected negative cable and the still connected positive cable (to help bleed any lingering capacitors, etc). That worked. Codes cleared and appears PCM reset itself to factory settings. As the shift point are pretty sharp again. Put about 150 miles on the truck so far and codes have not returned and no rough idle anymore. Think I’m good.