Another hybrid k04-023

[beachbuggy]

Only trying to help!

Get your boost stable and the lambda will follow.

Sort out timing swings and timing will stabilise ,egts drop and timing increase.

 

[Miguel_S#]

Boost i do not have n75
Timing i think The problem is knock sensor/ plugs/ or wiring

 

[beachbuggy]

Running a 21psi spring in an actuator is not needed and only makes it an on off switch.. Use a softer spring and use the ecu to control and you will get a much better boost control . You will then have better AFR..

You timing is swinging due to intervention, sensor and wiring effect cf which is a continual reduction in timing value until cf 0 is reached for x amount of cycles, it does not cause swings in timing..

 

[beachbuggy]

What ecu software you now running on the me7.5?

 

[Miguel_S#]

What ecu software you now running on the me7.5?

018h
Your injectors

 

[Miguel_S#]

hello again,
its not been easy this task, old car some malfunctions
after a new fuel pump, knock sensor, boost sensor

i dont know why after 7.5k the afr go to 11
tomorrow i will talk to fkkvs

timing better now, but cylinder 1 is not good

 

[Miguel_S#]

i have this errors
i dont have vvt

17968/P1560/005472 - 17968 - Maximum Engine Speed Exceeded (Engine Warranty VOID! ☺ )

16396/P0012/000018 - Bank 1: Camshaft A (Intake): Advance Setpoint not Reached (Over-Retarded)

 

[beachbuggy]

Lambda 11 (0.75) because knock fuel protection kicking in.. check egts though

Vvt activated in your map cdnws 3? Needs to be set 0 .

 

[Miguel_S#]

its not egt protection

 

[badger5]

whats the timing CF's look like Miguel?

 

[Miguel_S#]

cylinder 1 -10
cylender 2,3 and 4 -6

 

[badger5]

ouch..
back those down a little.. #1 is excitable is'nt it

 

[Miguel_S#]

just only with n75

-3 CF

the fuel problem remains, its not knock protection

 

[beachbuggy]

See what your egt protection limit is kicking in at then. At 240grams egts could still peak over 850.

 

[beachbuggy]

If you're still struggling to find out why. You need to log all the lamfa and bts variables and see which one is kicking in at the exact point.

 

[Miguel_S#]

If you're still struggling to find out why. You need to log all the lamfa and bts variables and see which one is kicking in at the exact point.

yes its not easy,
what vcds camp do suggest

 

[Miguel_S#]

today i just cut the plug to knock sensor and weld the wires, timing is know better but not good

after log the egt stuff i think everything is good with egt

 

[beachbuggy]

Can you post
Load
Specified load
Corrected load?

 

[Miguel_S#]

what do you think

 

[beachbuggy]

Hard to tell as you logged the wrong load variable. Need the _w for 16 bit so won't cap reading @180

You can also try setting KFFDLBTS to 0 to disable bts to see if it's that which is kicking in the extra fuel.

I assume also lamfa is 0.75 at 7400?

 

[Miguel_S#]

lamfa is 0.8 at 7400rpm
i set krmxn to 0 and the result

 

[badger5]

timing intervention coinciding with the lambda drop...
cause or effect?

hmmm

 

[beachbuggy]

what are the rev limiters set too? rev limiter will cut timing.... Both

 

[Miguel_S#]

rev limiters is set to 8k

 

[schwartza3]

stupid question, does me7.5 ever run in open loop?

afr looks fine all the way to 7500rmp, it's not leaning out so why sudden jump in injector duty cycle to dump extra fuel
you can see a tiny increase in intake air temps but shouldn't cause such a dramatic drop in timing & injector duty cycle increase

 

[beachbuggy]

Yes of course. If any of the protection systems kick in or the adjustments come in then it will go open loop.

BTS is a prime example of this, it ignores the 02 and just dumps fuel.

 

[schwartza3]

Ok, fair enough, explains why the graphs look the way they do, ecu is just guessing how much fuel should be added.
In open loop, obviously it ignores the o2 sensor but is it using the maf signal g/s to calculate how much fuel should be added?

Might explain why it's dumping so much fuel if it's based on 280g/s which looks a bit high i thought, engine load looks a bit too high as well, could it be that the maf is not scaled? is it using a stock sized maf?

 

[beachbuggy]

Won't be the maf readings or scaling. Even a Hta30 running 495bhp on a 3" s3 maf has no issues once it's above the maps 292grams limit. All that happens is the axis stop and last values are used. O2 should remain closed loop regardless and only go open when a variable bit which controls a protection gets triggered.

If you can't find the cause in a map then you need me7 logger and log every variable you can and find the one which triggers at this point.