PDA

View Full Version : Engine Dies with Code P2149 Problem and Possible Solution


jkd159
09-05-2013, 06:55 PM
My 2005 T1N has twice died with the ultragauge showing cod P2149. Researching here, it seems the most common cause is a frayed wiring harness. I checked along the entire harness and found a slightly frayed spot where it rubs against the intake manifold. I put some silicone tape over the spot. Hasn't happened since, but I haven't driven enough miles to know for sure if that fixed the problem.

If that was the cause, how do people permanently fix issues with the wiring harness? Just wrap it in tape and hope for the best, or go in and try to repair individual strands of wire?


The damaged spot is in this photo, covered by orange tape:
http://jeffdeutsch.com/tmp/Sprinter/wiring_harness.jpg

JAM
09-05-2013, 08:34 PM
I would tape each bad wire individually. Had that happen on my rv and it's tough to get slack to do it

Aqua Puttana
09-06-2013, 01:25 PM
There can be pitfalls to opening a harness. Other conductors can be damaged in the process or the harness can be moved out of position where not noticed which can cause other wear points.

There are "liquid tape" products for electrical wire insulation repair.

If the damage doesn't look too bad (just one conductor?), were it mine, I would just dab a bit of WD40 on the spot with a Q-tip or short spritz, and put a piece of slit heater hose over the damaged spot.

:2cents: vic

Aqua Puttana
09-06-2013, 02:31 PM
This may be another example of the possible general nature of generic scans.

P2149 as a Sprinter specific code is listed as "Fault in analog to digital conversion with 3 sub codes.

Your harness damage finding would most likely be a grounded conductor issue. There are specific Sprinter DTC's which are listed for injector circuit grounds, P2123 and P2124 being just two that I found in a quick scan of my resources. So a Sprinter specific scan tool would likely give better direction.

Generic scans are fine as long as their limitations are realized should the troubleshooting drag on.

I include this post here for future searches. vic

This a Canned Response for Generic Scan Tools

You really should get the codes scanned with a Sprinter specific scan tool.

From 2 different code lists.

P2141 Cylinder #1 Injector Open Circuit_
P2142 Cylinder #2 Injector Open Circuit_
P2143 Cylinder #3 Injector Open Circuit_
P2144 Cylinder #4 Injector Open Circuit_
P2145 Cylinder #5 Injector Open Circuit_
(No P2146 listed at all for Sprinter)

P2141 Exhaust Gas ReCircuitulation Throttle Control Circuit Low
P2142 Exhaust Gas ReCircuitulation Throttle Control Circuit Hi
P2143 Exhaust Gas ReCircuitulation Vent Control Circuit/Open
P2144 Exhaust Gas ReCircuitulation Vent Control Circuit Low
P2145 Exhaust Gas ReCircuitulation Vent Control Circuit Hi
P2146 Fuel Injector Group 1 Supply Voltage Circuit

Your Ultrgauge is a generic OBDII performance monitor/scan tool. When a DTC is detected as existing by the Ultragauge unit it polls the ECM to read the code(s). Being that the scan tool is not Sprinter specific, it may spit out the closest code definition which it has available. Sometimes that readout is accurate, sometimes not.

In your case of an injector fault...
There are many specific injector DTC's listed for the OM647. Some definition examples other than "Open circuit" are: "Injector Fault with 3 possible specific sub codes, some Injector Actuation Fault codes with 3 or 4 possible sub codes, etc.". I could go on, but I believe even just this short list gives enough example. The possible codes being missed applies for everyone using a generic scan tool. There are many more possible Sprinter specific codes, with sub codes, for other problems than just this injector example. A ScangaugeII, Ultragauge, or other basic OBDII scan tool cannot read them.

Until you get a scan with a Sprinter specific scan tool you may be missing some information that will help to pinpoint the problem(s). Generic scans are fine as long as their limitations are realized should the troubleshooting continue with no results

That said, by resetting the codes with a generic scan tool you may have wiped out an important code which only surfaced at the time of the first failure and may never return again. That happened to me with my O2 related LHM. A O2 sensor related code showed once on my DAD scan tool to never return again. I have a perfectly good used spare EGR because I replaced it during the Delphi O2 sensor partial failure, LHM air mass code debacle.

As an aside, anytime that you get a scan by a Sprinter specific scan tool you should ask (demand?) for a complete listing of ALL the codes revealed before allowing them to reset. As I said earlier, there may be a code which you only have one shot at reading. With a complete list you can go back for reference if the repairs drag on.

A very detailed wiring harness inspection would be high on my list of things to do, but you really need to get a proper scan. Good luck. vic
******************************

A similar recent thread P2146 is here.

http://sprinter-source.com/forum/showthread.php?t=28526