silver_evo

Ive been doing some work after reading https://www.evolutionm.net/forums/sh...d.php?t=354213. I wrote a c# program that loads a .csv and a .hex and finds the differences in Wideband AFR and AFRMAP. Anyways, up top i was -25% off. My fuel map reads 7.8 and my LC-1 reads 11.3. Ive been trying to get the AFRMap to be 11.3 and the LC-1 to read 11.3. That way the AFRMap is a usable number. It might as well just be straight hex, because those 'AFR' values are garbage. So First i tried MAF Scaling, but it is an 8-bit number that stops at 319.7g/s and my program was recommending numbers up to 360g/s for 1600hz. So i did some thinking and maybe the MAF scaling is a 0 to 255 fraction for the MAF Size value. I changed MAF Size to 359 + 25% so it was 446. All that did was make me hit rediciolus loads and get a boost limit cut at 319% load. Neither of these changes actually changed my real-life AFR. So thats funny. Want to make your car looks like a champ on logs, just change your MAF size and hit MAX load! haha. So the only value left that i can see to change is the Injector Scaling, but that is the stock value of 513. And that value doesnt change with rpm, so it would just screw up my low-load AFRMAP numbers. mrfred, tephra.. Do you IDA loving dis-assemblers know any maps that correct the AFRMAP values? Ive tried to look in the rom and i cant even find ANY function that will read from the Fuelmap Addresses. Side question also. Any of the IDA users want to share an IDB file for 94170015 that has some data regions renamed to correct things, instead of unk_00000000. Thanks!

steadly2004

iTrader: (19)

Just to get in on this thread. My maps are in the 12's, and the wideband is in the high 10's. It would be awesome to get the numbers closer, or exactly the same.

tephra

iTrader: (6)

I would have thought the best way to handle discrepancies between Actual AFR and "map AFR" would be to apply some sort of correction offset to the scaling formula.

However I doubt the relationship would be linear thus very hard todo.

Interesting topic - hopefully you can come up with a neat solution