Topic Sponsor
2004 - 2008 Ford F150 General discussion on the 2004 - 2008 Ford F150 truck.

Occasional P0356

Thread Tools
 
Search this Thread
 
Old 06-23-2019, 02:24 PM
  #11  
Junior Member
 
Bryan T Barker's Avatar
 
Join Date: Jun 2019
Location: florida
Posts: 15
Received 0 Likes on 0 Posts
Default

Ok guys, thanks for all the info and diagrams, the code originally set(with others,355,356,358) about a year after new coils.knew it was plug time and I had them done, ran great for a couple days then rough runs in the mornings that cleared out after a bit.
Recently very rough and won't run well with cam sensors hooked up.( Limp mode with them unhooked??)
I will ohm the coils, etc, I checked both sides of the coil with a logic probe I had, showed power(red) and ground(green, when pulsed on)
Old 06-23-2019, 07:19 PM
  #12  
Junior Member
 
Bryan T Barker's Avatar
 
Join Date: Jun 2019
Location: florida
Posts: 15
Received 0 Likes on 0 Posts
Default

ok well, was going today to have the mech rescan codes with his snapon so I pulled over shut off the truck, plugged in the cam sensors an drove to his shop, he wasnt there, my scanner now gives p0355,p0356.
Came back home pulled coil 6 and 5.
ohm meter set to 200, top of coil six(new coil) .8-.9 same on another new coil and an original(#1) on truck, coil 5 ohm across top pins .8-.9.
meter set to 200k , two new coils ohm from top pin to bottom spring 7.4
old coil from 5 ohm top pin to bottom spring 5.9.
used the 2 new coils on 5 and 6, pulled both plugs, not burnt up, small dab dielectric on boots, coil and injector plugs.
Fired it up, same thing and still pending codes p0355,p0356
also
Quote:
"Only thing I could add is - you might disconnect battery, unplug and re-plug PCM plug several times to 'burnish' the contacts and spray some good electrical contact cleaner in it. That is a prime spot to have an intermittent connection point that is effected by heat cycles etc" tried this too as well as recleaned with electronic cleaner.
Old 06-23-2019, 08:34 PM
  #13  
LightningRod
 
F150Torqued's Avatar
 
Join Date: Jan 2014
Location: San Antonio Texas
Posts: 2,412
Received 640 Likes on 513 Posts

Default

That tells us the primary and secondary windings inside all the coils are are 'in tact'. Doesn't say anything about the (REMOTE) possibility that some windings internaly were shorted together - basically reducing its efficiency. But I ain't going there because you are getting P035x and NOT P030x. The minor difference in COP primary to secondary (spring) reading can be explained by WHICH primary terminal you were touching. One pin would read both primary windings and secondary windings, the other would read only secnodary windings - which don't have much resistance at all. But you verified it ain't OPEN - eliminating one of the causes of P035x.

There is an 'S'-load to be known about all the little quirks involved in troubleshooting these computer system based systems. At no point implying you don't know about one - but I just don't know you know. "Pending" suggests it isn't a "HARD" code - but rather HAS occurred. Of course, many codes including 'pending' ones are sticky. Once set, they stay until a couple or three drive cycles are logged without re-occurrence, or codes are cleared with a code reader OR disconnecting battery for a long enough period.

I'm assuming the PCM was cleared by one of those two methods. /// I'm usually NOT an advocate of 'clearing' codes indiscriminately. Often I'd rather run a couple of drive cycles and see if the code clears - but I have a live data scanner. Under the assumption the pending(s) were cleared- I'll ask. Did you visually check / clean the COP <> Spring connection and make double dog sure good connection. Did you 'stretch' spring to insure contact/connection with plug anode? Does the 'flemzy' little plastic clip on COP primary connector "SNAP"? (IF NOT, replace them with one of those ridiculously priced $28.00 pig tail clips and solder / heat shrink it on). If they don't 'SNAP', the rubber insulator inside CAN & WILL push the clip up enough to create a flaky connection. I once completed a 300 mile trip with a piece of Oak Tree branch crammed between one and the Heater Hose to hold it down on COP # 3.

You are doing good. Keep us posted.
The following users liked this post:
Paul E Walnutz (06-24-2019)
Old 06-24-2019, 03:14 AM
  #14  
Junior Member
 
Bryan T Barker's Avatar
 
Join Date: Jun 2019
Location: florida
Posts: 15
Received 0 Likes on 0 Posts
Default

Originally Posted by F150Torqued
That tells us the primary and secondary windings inside all the coils are are 'in tact'. Doesn't say anything about the (REMOTE) possibility that some windings internaly were shorted together - basically reducing its efficiency. But I ain't going there because you are getting P035x and NOT P030x. The minor difference in COP primary to secondary (spring) reading can be explained by WHICH primary terminal you were touching. One pin would read both primary windings and secondary windings, the other would read only secnodary windings - which don't have much resistance at all. But you verified it ain't OPEN - eliminating one of the causes of P035x.

There is an 'S'-load to be known about all the little quirks involved in troubleshooting these computer system based systems. At no point implying you don't know about one - but I just don't know you know. "Pending" suggests it isn't a "HARD" code - but rather HAS occurred. Of course, many codes including 'pending' ones are sticky. Once set, they stay until a couple or three drive cycles are logged without re-occurrence, or codes are cleared with a code reader OR disconnecting battery for a long enough period.

I'm assuming the PCM was cleared by one of those two methods. /// I'm usually NOT an advocate of 'clearing' codes indiscriminately. Often I'd rather run a couple of drive cycles and see if the code clears - but I have a live data scanner. Under the assumption the pending(s) were cleared- I'll ask. Did you visually check / clean the COP <> Spring connection and make double dog sure good connection. Did you 'stretch' spring to insure contact/connection with plug anode? Does the 'flemzy' little plastic clip on COP primary connector "SNAP"? (IF NOT, replace them with one of those ridiculously priced $28.00 pig tail clips and solder / heat shrink it on). If they don't 'SNAP', the rubber insulator inside CAN & WILL push the clip up enough to create a flaky connection. I once completed a 300 mile trip with a piece of Oak Tree branch crammed between one and the Heater Hose to hold it down on COP # 3.

You are doing good. Keep us posted.

Thanks for all the help brother,I've read so many of ur replies and its clear u know if stuff!!
Yes I did clear the codes(battery) and also cleared scanner , I didn't pull the boots to check cops as they are new I also didn't stretch the springs, will try that.
I definitely heard both snap upon plugging in ( made sure I heard it as I am having so much trouble)
No idea what a "s" load is ...lol, also the pending state of the code, possibly because o just idled it in the drive way??didn't road test it as it was still so bad.
Thanks again!
Old 06-24-2019, 03:21 AM
  #15  
Junior Member
 
Bryan T Barker's Avatar
 
Join Date: Jun 2019
Location: florida
Posts: 15
Received 0 Likes on 0 Posts
Default Live data

Dunno if this helps
Edit..also have freeze frame data and it was set from....u guessed it p0356...



Sorry about the sideway ones! Lol




Last edited by Bryan T Barker; 06-24-2019 at 03:24 AM.
Old 06-24-2019, 04:20 AM
  #16  
Member
 
Freak007's Avatar
 
Join Date: Jun 2019
Posts: 51
Received 10 Likes on 8 Posts
Default

Couple things I find interesting... MIL distance, CLR Distance and Warm ups all indicate to me that this is a pretty active fault. It occured almost immediately after clearing the codes. Run time shows roughly 40 minutes, and IAT temp tells me the truck was probably sitting there idling the whole time... Underhood temps are toasty. Did you measure the coils hot, or cold? Did you clear the codes after moving #5 coil?

[RANT] Additionally, a pet peeve of mine is "scan tools" reporting MAF data in lb/s as that is nearly useless. On that truck I would expect to see the idle MAF be around 6-7 grams/sec. I had to dig up a calculator, but .02lb/sec is roughly 9 g/sec, which I would see as abnormally (almost 50%) high. However, 6 g/sec converts to .013 lb/sec, and 7g/sec works out to .015 lb/sec which *is* what I would consider in range, but would round to .02 lb/sec which *is not* what I would consider in range... [/RANT]
Old 06-24-2019, 04:38 AM
  #17  
Junior Member
 
Bryan T Barker's Avatar
 
Join Date: Jun 2019
Location: florida
Posts: 15
Received 0 Likes on 0 Posts
Default

Originally Posted by Freak007
Couple things I find interesting... MIL distance, CLR Distance and Warm ups all indicate to me that this is a pretty active fault. It occured almost immediately after clearing the codes. Run time shows roughly 40 minutes, and IAT temp tells me the truck was probably sitting there idling the whole time... Underhood temps are toasty. Did you measure the coils hot, or cold? Did you clear the codes after moving #5 coil?

[RANT] Additionally, a pet peeve of mine is "scan tools" reporting MAF data in lb/s as that is nearly useless. On that truck I would expect to see the idle MAF be around 6-7 grams/sec. I had to dig up a calculator, but .02lb/sec is roughly 9 g/sec, which I would see as abnormally (almost 50%) high. However, 6 g/sec converts to .013 lb/sec, and 7g/sec works out to .015 lb/sec which *is* what I would consider in range, but would round to .02 lb/sec which *is not* what I would consider in range... [/RANT]

Ur up too early like me lol, the motor was warm but not operating temp when measured and codes were cleared, I've been looking where to change that lb/s reading just not sure where, and was wondering about the MAF, it has been cleaned to btw.
As far as under hood temp, dunno if it matters but I am in Florida, that was in my driveway with sun beating on top of me at about 430-5:00 on a feel like temp of over 100.
Ur knowledge is incredible, glad ur offering help,
Thanks
On another note, u are correct about the code being immediate, I can start up, it's pretty smooth and after a few seconds( maybe 10-15) idle drops and becomes erratic
Old 06-24-2019, 06:20 AM
  #18  
Junior Member
 
Bryan T Barker's Avatar
 
Join Date: Jun 2019
Location: florida
Posts: 15
Received 0 Likes on 0 Posts
Default

Ok freak, change my scanner, MAF reads high 5s to low 6s after drive to work with cam sensors unplugged.
Plugged em back in 7 to 7.4 , restarts smooth, then idles Lower,rough
Old 07-05-2019, 04:43 PM
  #19  
Junior Member
 
Josh Adkins's Avatar
 
Join Date: Jul 2019
Posts: 3
Likes: 0
Received 0 Likes on 0 Posts
Default I’m having the same issue

P0356 hits soon as cleared codes. After the engine is hot less of instance. Did go a whole day without the miss or code. Next day boom.
Plugs, cops, cop connectors, cam sensors, vct solenoids, crank sensor...all new. Ground pulses with noid light, 12.5 v on all cop hot wires. 0 ohms on cop signal wire to pcm. I can’t figure it out unless I have valve issues or unless timing is off a tooth??? I don’t know but I’m pulling out my hair with this thing. The fact it went away for a day and is back again is what has me stumped. Anybody help with this???
Old 07-05-2019, 05:38 PM
  #20  
Junior Member
 
Bryan T Barker's Avatar
 
Join Date: Jun 2019
Location: florida
Posts: 15
Received 0 Likes on 0 Posts
Default

Originally Posted by Josh Adkins
P0356 hits soon as cleared codes. After the engine is hot less of instance. Did go a whole day without the miss or code. Next day boom.
Plugs, cops, cop connectors, cam sensors, vct solenoids, crank sensor...all new. Ground pulses with noid light, 12.5 v on all cop hot wires. 0 ohms on cop signal wire to pcm. I can’t figure it out unless I have valve issues or unless timing is off a tooth??? I don’t know but I’m pulling out my hair with this thing. The fact it went away for a day and is back again is what has me stumped. Anybody help with this???
Yes that sounds very irritating, like me mine as well,I still have another vct to install on mine( I changed the other one, didn't help)


Quick Reply: Occasional P0356



All times are GMT -4. The time now is 05:41 PM.