really bad knock all of a sudden
Thread Starter
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
Sorry, just saw this for the first time. Only read up to page two.
The cylinders you listed in order from left to right I am assuming. So the low compression is in #3 actually. The last two cars we took apart had damage/low compression on #3 and seems to be a pattern to that cylinder.
I'd change the fuel pump relay for sure.
How many miles are on the car now?
If you need something let me know.
The cylinders you listed in order from left to right I am assuming. So the low compression is in #3 actually. The last two cars we took apart had damage/low compression on #3 and seems to be a pattern to that cylinder.
I'd change the fuel pump relay for sure.
How many miles are on the car now?
If you need something let me know.
What sort of damage did you see? Physical or just worn rings?
Have you had any experience with compression tests not being consistent?
Car has done 15000 km's - Relay has been swapped
wow, I do know that the last generations of HEUI ford powerstroke diesel engines drive injection with oil pressure over fuel and those go to hell when the anti-foaming agents get used up. Maybe Mivec is also hard on the oil package or gets frothed enough to cause erratic actuation.
International trucks/fleetguard products actually makes an anti-foaming booster additive for people who tow with those motors as an emergency charge in case their rig peters out in the middle of nowhere towing heavy.
International trucks/fleetguard products actually makes an anti-foaming booster additive for people who tow with those motors as an emergency charge in case their rig peters out in the middle of nowhere towing heavy.
Thread Starter
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
just had a quick look at the code.
MIVEC load axis uses a different to what I am logging.
HOWEVER in the code, the two variables (MIVEC vs what I am logging) come from the same source and are basically a copy of each other.
Therefore I am led to believe that the MIVEC exhaust cam is having a hard time getting to the target, and is infact staying more retarded that requested.
eg I am requesting -1.9 exhaust cam, but am logging -2.9... this is 3000->3500rpm at 245load
Can someone else please check their cars/logs for similar symptoms?
Bryan - on Boosted4's car (right username??) where he had bad knock and you pulled apart the engine what sort of things did you try with MIVEC?
MIVEC load axis uses a different to what I am logging.
HOWEVER in the code, the two variables (MIVEC vs what I am logging) come from the same source and are basically a copy of each other.
Therefore I am led to believe that the MIVEC exhaust cam is having a hard time getting to the target, and is infact staying more retarded that requested.
eg I am requesting -1.9 exhaust cam, but am logging -2.9... this is 3000->3500rpm at 245load
Can someone else please check their cars/logs for similar symptoms?
Bryan - on Boosted4's car (right username??) where he had bad knock and you pulled apart the engine what sort of things did you try with MIVEC?
Last edited by tephra; Feb 9, 2010 at 08:02 PM.
Evolving Member
Joined: Jun 2007
Posts: 109
Likes: 0
From: New Zealand
just had a quick look at the code.
MIVEC load axis uses a different to what I am logging.
HOWEVER in the code, the two variables (MIVEC vs what I am logging) come from the same source and are basically a copy of each other.
Therefore I am led to believe that the MIVEC exhaust cam is having a hard time getting to the target, and is infact staying more retarded that requested.
eg I am requesting -1.9 exhaust cam, but am logging -2.9... this is 3000->3500rpm at 245load
Can someone else please check their cars/logs for similar symptoms?
Bryan - on Boosted4's car (right username??) where he had bad knock and you pulled apart the engine what sort of things did you try with MIVEC?
MIVEC load axis uses a different to what I am logging.
HOWEVER in the code, the two variables (MIVEC vs what I am logging) come from the same source and are basically a copy of each other.
Therefore I am led to believe that the MIVEC exhaust cam is having a hard time getting to the target, and is infact staying more retarded that requested.
eg I am requesting -1.9 exhaust cam, but am logging -2.9... this is 3000->3500rpm at 245load
Can someone else please check their cars/logs for similar symptoms?
Bryan - on Boosted4's car (right username??) where he had bad knock and you pulled apart the engine what sort of things did you try with MIVEC?
just had a quick look at the code.
MIVEC load axis uses a different to what I am logging.
HOWEVER in the code, the two variables (MIVEC vs what I am logging) come from the same source and are basically a copy of each other.
Therefore I am led to believe that the MIVEC exhaust cam is having a hard time getting to the target, and is infact staying more retarded that requested.
eg I am requesting -1.9 exhaust cam, but am logging -2.9... this is 3000->3500rpm at 245load
Can someone else please check their cars/logs for similar symptoms?
MIVEC load axis uses a different to what I am logging.
HOWEVER in the code, the two variables (MIVEC vs what I am logging) come from the same source and are basically a copy of each other.
Therefore I am led to believe that the MIVEC exhaust cam is having a hard time getting to the target, and is infact staying more retarded that requested.
eg I am requesting -1.9 exhaust cam, but am logging -2.9... this is 3000->3500rpm at 245load
Can someone else please check their cars/logs for similar symptoms?
As for the exhaust, it's pretty much spot on during cruise since my cruise exhaust mivec is 0*. Once I go WOT or any load where the cam is suppose to retard, it seems to retard more than it's target. Example: requested -2.0* but actual is -3.5.
Thread Starter
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
it actually gets worse when you at a higher rpm - i presume because the turbo can instantly spool, and you skip through load cells so damn fast!
so say your at 4000 in 4th, and you go WOT.
my MIVEC E map starts at -20 @ 80 load, -12 @ 140load, -5.6 @ 200load and drops to -1.2 @ 250load
however watch the actual exhaust cam.. on mine it gets to -6 and then i stop the WOT pull... so never hits the target of -1.2:
so say your at 4000 in 4th, and you go WOT.
my MIVEC E map starts at -20 @ 80 load, -12 @ 140load, -5.6 @ 200load and drops to -1.2 @ 250load
however watch the actual exhaust cam.. on mine it gets to -6 and then i stop the WOT pull... so never hits the target of -1.2:
Last edited by tephra; Feb 9, 2010 at 09:22 PM.
So basically what we are getting is that for you hit a target -5 exhaust cam timing for example. You really need to set it for -3.8 or something along those lines... However during cruise actual will match target...
Thread Starter
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
well i am still figuring that out... tomorrow I will get a full WOT pull done, so it will be interesting to see if by 4500-6000rpm the MIVEC-E gets to the target (because at full load MIVEC-E is pretty much the same)
hehhe
