My 7.3 diesel excursion sets a P1316 sporadically, when the throttle position is zero, seemingly at any engine rpm - idling in the driveway or on the freeway. It looses power but then stalls after 4-5 seconds.

Often, I can turn it off, clear the code and re-start the engine and it runs normally. If I don't clear the code it runs roughly and has no power. However, this method is increasingly uneffective.

I've checked the under valve cover connectors and that doesn't seem to be the problem.

Any ideas?

The odd thing is that it only seems to have a problem when the TPS is zero.

Thanks a lot, Sean.

 

P1316: Injector Driver Module Codes Detected

Well, have you done the IDM mod? This is for our information.

I wonder if it could be a bad TPS?

Here's a bump and I'm interested in comments and the results of this post as well.

 

A P1316 means that there are codes stored in the IDM. To retrieve those codes, you'll need a scanner that can run an injector buzz test. Once you run a buzz test, it will tell you which injectors or bank of injectors is causing the problem.

 

Haven't done the IDM mod or the buzz test. I've had the under-the-valve-cover connector problem, so I'm hesitant to think its the actual injectors although it could be. May have to buy an AE and do the buzz test.

Just speculation, but I'm wondering if the TPS is at zero, this may be a low voltage output, and there's a bad connection somewhere that is affected at low voltage but not at normal voltages for non-zero TPS conditions.

Thanks, Sean.

 

To be honest, I don't have an explaination for why the code only pops up when you are off the throttle. That's a new one for me. I would think that figuring out what codes are stored in the IDM might give a little insight as to why it's having a problem.

 

When you had your valve covers off, did you inspect your harness for wires being rubbed by moving parts..? Also, I would check the main wire harness that goes over the top of the drivers side valve cover. It has been reported from rubbing, you can get bare wires between the cover and harness.. and it will give you a P1316 code.

 

The harness was definitely rubbing on the valve cover, between were the factory tape ends and the connector.

One wire was almost worn through. Would have made a lot of sense this was the problem, a shorted wire, but there were no bare wires so it doesn't look like this was the problem, at least the current problem.

 

Also, I checked all the wires when the valve cover was off. The only thing I questioned, in addition to the connectors under the valve covers, was the connector directly on the outside of the valve cover - has anyone had problems with this connector?

 

Check for burned injector wiring pins on the under valve cover side of the connector. I have seen pics of blackened pins and they caused poor contact.

Also check for continuity from the outside of the connector to each injector connector. Each two wire injector connector has a separate wire for that injector solenoid and a common wire for the injector common single pin (the one in the middle on the UVCH connector).

 

****** http-equiv="Content-Type" content="text/html; charset=utf-8">****** name="ProgId" content="Word.Document">****** name="Generator" content="Microsoft Word 11">****** name="Originator" content="Microsoft Word 11"><link rel="File-List" href="file:///C:%5CDOCUME%7E1%5Cpswr001%5CLOCALS%7E1%5CTemp%5Cms ohtml1%5C01%5Cclip_filelist.xml"><!--[if gte mso 9]><xml> <w:WordDocument> <w:View>Normal</w:View> <w:Zoom>0</w:Zoom> <w:PunctuationKerning/> <w:ValidateAgainstSchemas/> <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid> <w:IgnoreMixedContent>false</w:IgnoreMixedContent> <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText> <w:Compatibility> <w:BreakWrappedTables/> <w:SnapToGridInCell/> <w:WrapTextWithPunct/> <w:UseAsianBreakRules/> <wontGrowAutofit/> </w:Compatibility> <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel> </w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:LatentStyles DefLockedState="false" LatentStyleCount="156"> </w:LatentStyles> </xml><![endif]--><style> <!-- /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} --> </style><!--[if gte mso 10]> <style> /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman"; mso-ansi-language:#0400; mso-fareast-language:#0400; mso-bidi-language:#0400;} </style> <![endif]-->Great advice, will check continuity at the UVCH connector.

The problem has only ever occurred at zero throttle speed independent of rpm. However, it just happened at full throttle (was on a country road). So now it seems to be no throttle or full throttle. I tried it again and it happened consistently at full throttle.

Still suspicious of the TPS (or accelerator position sensor).

However, checked my camshaft position sensor on cranking - no movement of tach. Is this conclusive that the CPS is bad?

Thanks again, Sean.
<!--[endif]-->

 

Great advice, will check continuity at the UVCH connector.

The problem has only ever occurred at zero throttle speed independent of rpm. However, it just happened at full throttle (was on a country road). So now it seems to be no throttle or full throttle. I tried it again and it happened consistently at full throttle.

Still suspicious of the TPS (or accelerator position sensor).

However, checked my camshaft position sensor on cranking - no movement of tach. Is this conclusive that the CPS is bad?

Thanks again, Sean.
<!--[endif]-->

 

Well you could easily rule out the CPS by getting one from Ford for 25 bucks and swap it out. It's a good idea to keep one in the glove box anyhow as these CPS' can leave you stranded if you don't have one handy to swap it out.

 

2002-2003's have a different tach signal input than the earlier Superduties. The tach on the 02-03's does not move while cranking, so that test only works on the 99-01's.

I don't see how at TPS can trigger a P1316. Again I don't know why it happens only at idle (and now at WOT), but there's really no way that the TPS can trigger an IDM code by itself. Something else is going on. I still think you'll need to pull the IDM codes to find out.

 

Unless it is the IDM that is having the problems.
But I agree, the problem has to be somewhere between the IDM and the injectors being that the TPS is connected to the PCM which tells the IDM what it should and shouldn't be doing.

 

Exactly! The TPS and IDM are separate from each other.

Now there may be certain conditions that trigger the IDM code and issues, and that condition might be under certain engine loads controlled by throttle positions. But that still leads straight to gathering codes from the IDM to pinpoint what's happening.