Weird MAP Issue, starting turbo tune

[SprungtS]

This image shows the OFT v4.03 B01C files are hacked A01G maps, and it shows some of the tables I'm talking about that are missing in RomRaider. Does anyone have the storage address for any of these tables for the A01G? I'd take them for any CAL ID, I'll switch to a RR tune quickly if it means I can fix this load limit issue.[

[SprungtS]

Oh man, what a beautiful ending to this 2 day long saga:

Got it fixed. Managed to get the correct addresses and table values for not only the load limiters, but also the MAP scaling which was incorrect on the OFT-provided defs. There are three MAP scaling maps - A, B, and C based on the def I used for reference. The A01G hacked OFT ROMs only include table B. I expect that's why it wasn't working before, but it's working now on the Omni 3 bar.

Also, fuel is a little rich across WOT.... but it's rock steady already at 11.4-6:1. I don't trust it to be exactly accurate but I get readings down to 11.25 and it only hit that rich when the PI injectors came in. Time to start actually tuning lol.

Check it out if you're interested! Going to start a new thread I think with that new question, I've been logging PI/DI and although I'm using slightly modified 2017+ ratio tables with 35% port injection over ~2800RPM, I'm showing only DI until around 3500RPM consistently. There's a screenshot at the end here of the first WOT pull I did after fixing this def showing that phenomenon.

[SprungtS]

Nevermind on the new post - fixed the DI:PI ratio as well. It seems there are a couple more arguably important tables missing - or I’m just blind and missing them looking for a different name, but I’ve been through all these files pretty thoroughly line by line.

The stock ROMs have a table that gives a lower threshold and a table that gives an upper threshold to PI ratios. At least under some conditions (at least at WOT from what I’m logging) the stock lower threshold of 35% means that any value in the ratio table under 35% will be treated as 0% - not sure why that makes any sense, but that’s what it does. I thought I had set my higher load ratios all to 35% but in fact had used 30%, and it was causing 100% DI for a period of time where I wanted to keep a blend.

Bumping those values to 35% (35.2%) has a nice smooth blend of DI:PI throughout my WOT pulls. And smooth is the word that comes to mind, damn does it drive smoothly. Can’t wait to retune my 2020 with all I’ve learned the last couple days lol. I’ll try to come back up here and post some logs this weekend - kid’s birthday is tomorrow so I’m not sure how much logging I’ll get to do!

[NoHaveMSG]

Originally Posted by SprungtS

As I said, I have two Omni 3 bar sensors. One of them is brand new. They both do the exact same thing. And regardless, changing MAP scaling should change pressure logs even if the sensors don’t read anywhere close to what they should read. Changing MAP scaling has zero effect on my logs. That’s why I’m stumped.

ETA: even with the stock MAP sensor plugged in, no amount of changes to my MAP scaling table makes any change to the value interpreted by the ECU. It’s like I’m changing values for a RAM address that’s incorrect.

I have a brand new bad Omni

[SprungtS]

Originally Posted by NoHaveMSG

I have a brand new bad Omni

I never doubted that could happen. Even quality parts and QC sometimes miss a dud. But specifically for mine it wasn’t high on the probability list even without making changes and checking logs, since the car had been running on the same one for years and a brand new one performed the same way. Both acted exactly as expected as far as voltage output, at least after flashing over the EcuTek tune that was present.

Car has been rock solid since my last post. Put in several hours of driving, logging, tweaking, and it feels great. Need to finish some minor cosmetic stuff and I think I’m finished with it for now.