sebas-chan

Hi,

I would like to flash my EVO 6 GSR with the ceddy mod rom in order to log 1byte load. I replaced all the ceddy mod maps and ignition tables with the ones from my original rom. Then I flashed it to my ECU, went on a test-drive and hit the fuel cut 2 times out of 2 tries in 3rd gear... (I don't have any issues with my standard rom)

I did a log and marked the entry when I hit the fuel cut yellow... I can't find any reason for a fuel cut.

I left all the other ceddy mod rom options untouched, which means that boost cut shouldn't be an issue (running less than 15psi atm. anyways)

any ideas what could cause the fuel cut?

uprated fuel pump is installed and fuel pressure is at the correct level...

sebas-chan

I redownloaded the latest version of the ceddymods (1.2b) and noticed that a few settings are different from the version I got from a friend of mine. I'll import my maps and try it tomorrow... one question though:

what is the "ignition retard limit" good for and to what value should it be set to?
ceddy himself writes on geekmapped that its standard value is -5, but in fact its +5.1...
My standard rom has it set to 0, but I can't do that with ceddymods. (Entering 0 results in -0.2)
I'm confused

sebas-chan

So since my post is pretty high up in the google search ranking I feel like I have to give an answer to my own question.

I got those fuel cuts because I did not set the fuel-cut bit to 0. No matter how high you set the values it always causes a fuel cut exceeding 1.2bar boost.

In any case, I don't earn money with mapping and I am not planning on doing it, so attached is my current mapping, the standard TME mapping, the standard ceddymod for the EVO6 and the bang bang bang ruin my turbo mapping.
Use it with caution and after confirming!
Use it on your own risk!

My mapping is a pretty save one and only produces about 20-30 more bhp.

shrug

are these maps still using maf sensor or speed density?