where is the fuel map table for 1227165 to adjust air fuel ratio

[carcaper]

cannot locate fuel map table in the definition. Anybody have experience with these models? 1987 Chevy Camaro 5.7 Auto

[brian617]

Assuming the 1227165 definitions are similar to the other ECM/PCMs look under BPW parameters, then VE tables.

[EagleMark]

There are no VE tables in $6E, it's MAF only. All fueling is controlled by MAF tables.

[brian617]

Well there you have it, I'm wrong again Still learning, errr trying.

[Fast355]

Well there you have it, I'm wrong again Still learning, errr trying.

Its generally a table that corellates BPW to LV8 and RPM in those old MAF setups.

[carcaper]

There are no VE tables in $6E, it's MAF only. All fueling is controlled by MAF tables.

ok eaglemark, first of all I don't speak computer language. I have no clue what you are talking about when you say $6E. So if I used VE tables before that I have experience with how can I use that experience to tune this differant system? I see the maf tables and I understand how the maf changes in voltage according to air flow but why do we have 6 tables and only 1 column in each instead of how the VE table looks with several columns. I can only assume that I need to open all 6 maf tables and watch for my courser for the current stage that needs to be address right? And please explain the $6E part, for I dont know what that has to do with my question.

[EagleMark]

$6E is hex for the designation of the mask/definition. You should see that in the XDF file your using to adjust the bin.

MAF is using voltage to frequency... what it's doing is measuring air flow and calculating fuel based on the numbers in these tables.

Working with MAF in six tables is hard and IIRC there are differant multipliers for each table? I'm not well versed in $6E so can't help to much. But you adjust the MAF tables similar as a VE table to increase or decrease fueling needs. One thing about MAF is it has to be a very smooth transition/slope from end to end. Which is hard with changing tables. I think the reason they are split up is the limits of TunerPro, or what limits used to be, it would not scroll and could not see half the table.. steveo had changed the $EE mask to include all in one table.

[Fast355]

$6E is hex for the designation of the mask/definition. You should see that in the XDF file your using to adjust the bin.

MAF is using voltage to frequency... what it's doing is measuring air flow and calculating fuel based on the numbers in these tables.

Working with MAF in six tables is hard and IIRC there are differant multipliers for each table? I'm not well versed in $6E so can't help to much. But you adjust the MAF tables similar as a VE table to increase or decrease fueling needs. One thing about MAF is it has to be a very smooth transition/slope from end to end. Which is hard with changing tables. I think the reason they are split up is the limits of TunerPro, or what limits used to be, it would not scroll and could not see half the table.. steveo had changed the $EE mask to include all in one table.

Its unlikely that it is $6E...Most likely $32 or $32B.

[carcaper]

ok opened up all 6 maf tables and could not find any trace whatsoever with engine running. as far as the $6E I am not seeing that anywhere.

[RobertISaar]

I think the reason they are split up is the limits of TunerPro, or what limits used to be, it would not scroll and could not see half the table.. steveo had changed the $EE mask to include all in one table.

not a tunerpro limitation.... ECM code limitation. GM chose to split it up into multiple smaller tables and use 8-bit values for all MAF applications except for 94-95 LT1, which used a single 16-bit table to move away from the need for scalars(and on later codes, scalars and offsets(even though oddly enough, offsets are 16-bit....)).

it could be patched to use a single 16-bit table, probably with little to no speed/size penalty, though i don't know of how much use it would actually be.

as for EE..... it has always been a single 16-bit table...... i really don't know who decided to split it up or why, but viewed as it is now is correct. there are certainly more extreme examples that i've come across, like the 60V6 MPFI code that has a 112 row table for helping control idle IAC operation, or the 255 row 60V6 SFI code for low pulsewidth injector offsets....