Anybody running $0D TBI MAF

[babywag]

Looks SWEET!!!

Where does one find these elusive bin, ADX and XDF files? Are the VSS and the MAF the only pins changed/added?

I got the files from thirdgen.org
http://www.thirdgen.org/techboard/tb...-code-faq.html

I did contact the author and inquire about getting the latest code/files.
He said he'd put something together and get them to me.
However the above files from thirdgen do seem to work, just don't know if they're the latest/greatest.

The VSS is something I haven't figured out yet. The pins are F2&F3 for it in the MAF bin.
MAF is F12
IAT is B9

[EagleMark]

I think we had the origanal and update files in the $0D info thread?
http://www.gearhead-efi.com/Fuel-Inj...Information-OD

[JeepsAndGuns]

Random question. The $0D code has parameters and a flag to enable a MAT, as some of the CPI V6's use them. So whoever wrote the MAF code, did they change it to use the MAF mounted IAT instead of a MAT?

[babywag]

Random question. The $0D code has parameters and a flag to enable a MAT, as some of the CPI V6's use them. So whoever wrote the MAF code, did they change it to use the MAF mounted IAT instead of a MAT?

No, the TBI MAF code was written to use the IAT inside the MAF.
It's my understanding that if you're running a single plane unheated manifold you should also use a MAT.
If you're running a stock heated manifold like I am you should not need a MAT.

You're running a single plane unheated manifold so probably benefit from a MAT.
Also there is MPFI MAF specific code so for you probably best to start reading the MPFI MAF threads on thirdgen?
There are some people that had issues specific to MPFI+MAF.
It's pretty different in terms of fueling than this TBI version.

[Fast355]

No, the TBI MAF code was written to use the IAT inside the MAF.
It's my understanding that if you're running a single plane unheated manifold you should also use a MAT.
If you're running a stock heated manifold like I am you should not need a MAT.

You're running a single plane unheated manifold so probably benefit from a MAT.
Also there is MPFI MAF specific code so for you probably best to start reading the MPFI MAF threads on thirdgen?
There are some people that had issues specific to MPFI+MAF.
It's pretty different in terms of fueling than this TBI version.

Lack of cranking fuel for the MPFI was the thing I remember most. When I first started messing with it, the MPFI code would start with a puff of propane into the throttle body.

[EagleMark]

I'm having that exact issue right now. Was there ever a cure?

[JeepsAndGuns]

Mark, you running a 0D mpfi system too?

[EagleMark]

Just helping a guy tune one.

[babywag]

Just helping a guy tune one.

Is there a way in TunerPro to build a history table to log MAF flow vs. WBO2?
I've built tables before, but not sure how to set one up for this.
Seems TunerPro only allows for one output(Z) and I need both outputs??

Also I got the VSS output working using my existing 2k JTR VSS.
Same way as before with setting "Output Speed not from DRAC" @5D02
First I tried to hexedit the bin directly changing it to 31 vs 21, saving it, and burning a new chip.
TunerPro showed the difference(s), but it still didn't work.
So I copied/pasted the xdf parameter from standard $OD .xdf to my MAF .xdf and it worked.

Only other thing that I've seen not reporting correctly is NBO2 mV, but that is just a nuisance.

[EagleMark]

Only other thing that I've seen not reporting correctly is NBO2 mV, but that is just a nuisance.

I wonder if that data was changed to something else?

Sometimes you build another value with X and Y for the output and use it for history table.

If you have WB and use Lambda instead of AFR then the calculation for adjustment is the actual reading. 1.0 = Stoich/no ajustment if multiplied. .90 is rich so multiply. 1.10 is lean so multiply. So MAF = 3.2 and Lambda = .90 MAF * Lambda = new MAF

Not sure there is a X and Y in data to make MAF history table? Post the XDF, ADX and a bin I'd like to look, never worked on $0D MAF.

[babywag]

I wonder if that data was changed to something else?

Sometimes you build another value with X and Y for the output and use it for history table.

If you have WB and use Lambda instead of AFR then the calculation for adjustment is the actual reading. 1.0 = Stoich/no ajustment if multiplied. .90 is rich so multiply. 1.10 is lean so multiply. So MAF = 3.2 and Lambda = .90 MAF * Lambda = new MAF

Not sure there is a X and Y in data to make MAF history table? Post the XDF, ADX and a bin I'd like to look, never worked on $0D MAF.

Linked above in thread already, but here's what I started with...

[babywag]

Today I added a MAF to my other Jeep
Now I have 2 running the $OD TBI MAF code...

Cheapo cold air intake w/ junkyard parts $15
eBay MAF sensor $27.99
misc. wiring/solder/shrink tube ~$5
So for $50 it's up and running.
Still impressed w/ how well they run.

image.jpeg
This is the '90 Grand Wagoneer with it's new CAI & MAF

[JeepsAndGuns]

Hey, thats one of those 90's model cadillac air intake bonnets. I got one of those right after I installed my TBI years ago. We must have significantly different intakes or something, as there was no way shape or form I could get it to fit mine without hitting the hood. I wanted to use it so bad cause it was cheap and looked like it would work awesome.

[JeepsAndGuns]

Just helping a guy tune one.

Hey mark, you ever get the mpfi MAF working right?

[fatjoe216]

I too a nubee here have a 350 TBI in an Astro van. I have a MAF with a cold air intake but do not have the PCM setup yet and would like to try this. I'll keep an eye on this thread.