Very rich after 6PSI?

[Mcgeek]

Hello all!

Been tuning a boosted 355 with ose11p and have run into an issue where just after 6PSI the AFR goes very rich. I have even made big changes to the boost multiplier to see what effect it has but still the same thing injector duty cycle goes through the roof.

I dont have any logs saved at the moment but was wondering if someone with knowledge of this code and using it with boost could have a look over the .bin to see if i've missed something simple? the off boost section of the map is spot on.

Thanks in advance,
McGeek

[Holden202T]

more info required ?

when you say very rich what sort of numbers are you seeing ? at 150kpa in the AFR table your going from 12.5 target to 12.2 ?

really need a log to see whats happening, but I can't see anything specific that stands out in the tune as an issue.

[Mcgeek]

I'll save a log next time it's on the dyno, probably wont be for a week or two.

Just as boost passes the 6psi mark and around 5200rpm the actual afr goes from being on target to 10.60:1 only on around 50% throttle so far and the power curve just takes a dive.

Fuel pressure is rising fine at the 1:1 ratio

I'll post a log as soon as I can.

Thanks!

[antus]

I wouldnt be changing the boost multiplier, thats not intended to be changed. With a jump like that would needs logs. Its quite possible its a bad map sensor and its sending bad input to the ecm. Any DTCs showing?

[PaulR]

done a compare to the std 11p blcc bin? theres 36467 bytes different!! whats going on there?

[Mcgeek]

The boost multiplier was just changed as a diagnosis attempt, easiest way to make a large change at a given boost pressure.

As Paul mentioned it does seem like the file might actually have corrupted.

We were having a lot of comms errors through the obd port so i made a comms board directly into the '424 ECU to resolve this, the corruption may have occurred when we were having comms errors?

No DTC logged.

I'll move the current maps into a non corrupted bin and give it a go and record a log at the same time.

Should be in around a week.

Will keep you all posted - cheers

[antus]

done a compare to the std 11p blcc bin? theres 36467 bytes different!! whats going on there?

Your posted bin only contains the calibration, not the 11P operating system, ALDL responses or os update over ALDL segments. Use the delco flashtool to get a complete bin, or disable the oseplugin optimisation calibration area only->read. It'll take more than double the time to read but will give you a complete file (which will have more than required - it'll contain stuff out of the PCMs RAM too, but thats not a problem). Its a lot quicker to work with calibration area only but you should be aware that your bin wont work if directly flashed to a chip.

If you need to start again from scratch because the OS isnt running and you cant connect over ALDL and you want to go back to that cal you would put the stock 11p bin on the nvram with a programmer, then use tunerpro or the delco flashtool to upload the calibration over aldl. That process will merge it back together for you.

calibration area only.png (12.49 KiB) Viewed 3988 times

Use the tunerpro difference tool and restrict the range to 4000 -> 7FFF to identify calibration changes in 11P and skip over the missing segments.

11p calibration differences.png (40.59 KiB) Viewed 3988 times