Have a descreened MAF on my 88 TPI 350. While datalogging I can see Airflow figures in the regions of 2000-3000 at idle and 15000-30000 while opening throttle. Are these figures normal? Arent these supposed to be 2 to 3 digit numbers? I am using the $32B with 1227165_160 from gearhead efi website.

 

Are they random flashes of high numbers or is it actually sitting there stable at those values?

typically idle i see 7-12 g/s or so, light cruise anywhere from 20-80. Wot peak 190-220 depending on mods on stockish motor. The max is 254, and can be hit with heads cams cars.

 

Its stable. As soon as I touch throttle it goes steadily to 3000, 5000, 7000. If I floor it, it goes to 34000.
And its not a glitch. It does it all the time.

Origin of the question is that I occasionally have a Check Engine light throwing random errors but almost all the time, Code 34. I also have a power flat spot in the regions of 3000RPM so I am trying to figure out what is going on.
This Airflow figure surprised me a bit but I always assumed that tunerpro is applying some conversion to the numbers.

 

 

Tunerpro's Airflow definition

 

Assume you have version 5 and converted the .ads file to .adx?

edit. Nvm i see you seem to have done that

 

Yes I did Import ADS and then I chose Save Definition As...

 

Try dividing by 256 using the conversion tab....25793/256 = 100.75.

Your adx is displaying the raw 16 bit (decimal) value with no scaling/conversion factor. Same issue the other guy had recently.

 

That seems odd. 160 baud? Can you try another file?

i know on some ads to adx conversions the body size in the command gets messed up but there is no transmit data option to check on that file

http://www.gearhead-efi.com/Fuel-Inj...nformation-32B

 

What I am noticing is that if I open the ads file from the tunerpro website or from the gearhead-efi site that you provided, with Notepad, it has a strCodeMask of 6E and strYear of 1989 which to me suggests its not the correct one as listed in its description.

 

I believe 6e ads/adx will work with 32b but some things may be off. Not sure. I’ll have to check my files. Last 32b car i touched i want to say i went to $6e to avoid all this hassle lol

the dividing by 256 idea above seems to give expected values

 

But $6e still uses MAF no? I did program a chip for $6e removing also the cold start injector but didnt notice any improvements so for now I reverted to the stock PROM to avoid any other unknowns.
If I use the X/256 conversion it displays the right numbers meaning that my MAF is working fine.

I guess that concludes my query. Still with the flat spot issue. More investigation....

 

Yeah 6e is maf and the expanded xdf is what i use. I like that platform better and most familiar with it. Use maf for fuel and no pulsewidth tables to tune.