Thanks for the feedback, nice to know I'm heading in the right direction.
My last stumbling block is spark advance as the tables all reference grams/cyl which looks like an air mass calculation which i'm guessing is using the MAF sensor (i wsn't planning on using one as i was going speed density tune).
So now i'm trying to find how its uses the map sensor for spark correction
Usually MAFless programming will set the MAF into a permanent error, which causes the PCM to use the low octane spark tables. Perhaps copy / paste the high octane spark table into the low octane spark tables.
dave w
Simply exchanging the MAP with a 2 BAR requires one to change many variables. But it can work. You can adjust tunerpro to display the correct units in your tables and constants to help prevent you from forgetting to scale a MAP value. Then you need to check everything that is MAP related to adjust the value back to stock or back to a reasonable number.
When MAF is in error PCM calculates MAF using primary VE table, RPM, and IAT. VE also plays a part in AE/DE. Different OS's / PCM's are biased more or less toward VE. No matter which OS, correctly tuned VE tables should be considered mandatory.
Posting Permissions
Reply With Quote
Bookmarks