I was working on an '89 IROC with a MAF 355ci stealth-ram, ZZ9 cam, headers, T-56.

It threw a code 33 and 36.

33 - MAF (gm/SEC HI)
36 - MAF burn off

We replaced the MAF sensor and code 36 went away, but still getting code 33.

Any suggestions?

 

Anyone??

 

Your car is mad for not having any real times, take it too the track and the code will magically dissapear!!!(I dont know the whole story, just saw some guys pushing you to go)

I get random code 36 too

 

If you can read, I wrote that I was working on an '89 IROC (MAF motor). I have a speed density 1991 Z-28, see sig. I do not have a MAF sensor on my motor.

The 89 IROC is the one throwing code 33.

 

Probably needs to have the MAF High Diagnostic (Error 33) Threshold set higher than the factory setting of 45 gm/sec., in the PROM. That's the only way I got rid of it with my 383 MAF 58mm TB setup.

Do a search and you'll find a far better explanation than I could give, but, basically, it's drawing more air than expected at certain conditions and sets the code. Nothing short of turning it off and restarting it seem to help me, except for reprogramming it of course.


HTH!

 

Easy there buddy! I think he was pullin' your chain.

Regarding the MAF car, send him my way, i'll tune his car.

 

Touchy subject apparently??? Why wont he run it?(since we had an offer to solve the problem I can ask )

Sounds like a good setup to me....

 

Haha Neil, ****, you can barely get your own car running!

I changed the MAF threshold to 55 in the chip. We'll see if it does the trick.

Thanks!

 

Whoaaaaaa, hold it!!!!!

What in da he%$ are you doin' burnin' chips for MAF cars anyway? I mean you can barely tune your MAP-POS, aka runnin' like a raped ape, right?

I've seen your car run, oh, wait a minute it was kinda hard seein' ya in my rear view mirror, you were really tiny!

D'OH that's what your girlfriend said!

I just kidding.

 

Bring your crop dustin', oil burning, POS down to my side of town and I'll run ya for bragging rights.

Dont get embarrassed if your mini-ram 383 gets spanked by a TPI 355 !!

You need to get with the program and switch to Speed density. But, the extra power might push your weak motor over the edge and you might break something. And my speed density PROM is 32k which is twice as big as yours (just like everything else I have, mine's twice as big) !!



Alright, enough talking sh*t, I'll find out in a week or two if changing the MAF threshold fixes the code 33.

And hurry up and get your wheels so we can finish the Z06 brake swap.

Later

 

Yeah, you might try raising the gm/sec default (above 45) as SMasterson suggested and keep an eye on BLM's and O2 volts.
Seriously, when he comes back to Houston, come on down and we can scan his car with diacom. Oh, and tell him to tune it up this time! Fuel filter, cap & rotor, plugs & wires (if needed) and air filters.
Oh, and if your going to make a comeback, make it worth my reading time! Someday to you will have a fast car, someday far..........far........away...........

 

LOL, .......yea, someday you might make up your mind and buy some wheels that will fit over your brakes!!

I already changed the gm's/sec threshold limit upto 55. When UPS drops off the chip to him, he's gonna let me know if the code 33 clears up.

Also, Datamaster just released a Beta version of their software that is supposed to work on a MAF car.

 

Oh, yeah, disregard that last post except for the part of you having a fast car someday.

 

Exactly, cause it's allready faster than your car! It's ok, I wont tell anybody!

:rockon:

 

This post... is classic.

I need to save it

 

Glad to humor you Steven!

Neil's a character! It's too bad he's leaving the state (he's scared to race), so he's moving and using his new job as an excuse!

 

Is your TPS voltaqe set a little low, perhaps?

 

TPS was at .52 at idle.

I think the stealth-ram was just pulling too much air for the stock MAF threshold in the PROM to handle at idle. I upped it 10 grams in the PROM and re-burned the chip. If this doesnt take care of the code 33, then I'm stumped!

 

That's it BIOOOOOOOOOOOOOOOOOTCH! Off topic or not, line up that little, 355 TPI candy a$$ motor with my 383 mini-ram! You are going down. I will spank your a$$ all over the highway, road, dirt road, you name it!

Ok, i'm done.

 

You're probably right. Since I'm making too much power to hook, you'll probably get a slight jump on me off the line and you'll be blowing so much smoke (crop dusting) for to me to see the road and I'll have to shut it down just so I dont wreck into anything due to lack of visabilty.

LoL, sorry, I have to give ya crap cause your car isn't road safe yet (brakes).

Neil's car actually run's pretty good. He can kill a Z06 with his by a few more lengths than I did.

When I get gears and tires you may be in trouble though Neil. It should be a good race if you dont get scared and move out of state first!

 

Vader has a great point that the BS'ers who hijacked the thread haven't commented on...

The TPS voltage at idle should be at least .54...closer to .6...

Change that before you put in the different PROM and see if the code 33 goes away...

HTH,

 

Actually that wont matter. It's sitting on .52 which is in spec. The minimum TPS % at idle is set to .48 in the PROM, so addind .02 volts wont matter any as far as the ECM is concerned with setting off an engine code.

 

What BIN are you using? The MAF scalar is skewed by the TPS voltage, and obviously the RPM. Did you also raise the target idle RPM? A 355 shouldn't be drawing that much more air than a 350, everything else being equal.

 

Using a modified ARAP.bin. I did raise the target idle RPM to 850 and the motor does idle at 825-875. The coding car in question does have aftermarket heads, 5 extra cubes, and a Holley Stealth ram, so it should pull a little more air than the stock TPI 350 it came with.

 

Try raising the TPS to the upper limit - 0.61V. Unless you changed the TPS scalar, the ECM could be expecting a lot lower flow. The extra five cubes is only 1½% more volume than a "regular" 350. Factory programming allows a lot more variation than that. The ECM is reading X g/S at 0.52V. Since your engine is idling 30% faster than it was designed and programmed for, that's likely what is causing the high (30% higher?) MAF reading.

Either re-write all the MAF tables, or raise the TPS.

Can you email the BIN?

 

Vader -

I'm just about to leave work. I'll e-mail you the .bin tomorrow morning.

Um..... yea...., I'm not even remotely interested in rewriting the MAF tables!! That would be one hell of a job!!

I'll also have him adjust his TPS upto .6 and see what that does for the situation. It will be a week at least before he recieves the second chip revision. I'll wait till I talk to you first to hear what you have to say about the .bin before I burn / ship him the new chip.

THanks!

Mike

 

K. Just send your custom BIN. I already have a stock ARAP to compare with it (who doesn't?). I had to write new MAF tables for a 355 TPI conversion in a '55 Chevy that had been using a 305TPI bin. It's just tedious, not difficult.

 

Seen this a dozen times......replace both MAF burnoff relays on the drivers side firewall next to the wiper motor. Should take care of the code 33.

 

I have a 87 Z28 Tpi. it gave a code 33 once, and just cleaning away the carbon buildup in the throttlebody & plenum cleared the code! I know that sounds simple, but that did it for me.

 

That's likely because the varnish (not carbon) was holding the throttle plates open slightly, allowing too much intake airflow at the prescribed TPS voltage - the essence of a "code 33". Cleaning your TB is like resetting the minimum air position in that the TPS voltage will again match the intake air rate.

The problem described is that the intake air rate is higher than allowed at the given TPS in the data tables. Setting up the target idle RPM in the programming doesn't automatically re-write or affect the error diagnosis portions of the programming.

 

Holy ****, I never knew MY code 33 problem could start this much madness. lol, 1bad91z i wanna know how the Houston showdown goes down, That is if Neil grabs his ballz and decides to race ya.

YES, it is my car thats being taked about in this thread, and i just stumbled across it. I just got done resetting my TPS to .54 and I still have the code 33. Im about to try a few more TPS settings to just see what happens. im gonna try .45, .5 , and .6 because after reading many threads similar to this one, ive noticed that everyone has their own opinion on what it should be. (I was just about to post a page about my code 33 problem b4 i saw this one)

 

ok, i tried all the above TPS settings and still get the code 33 w/ each one. Im gonna replace the MAF burnoff relays to just see what happens. any other suggestions?

 

Before you spend the money.

Clear the codes, back the IAC out, reset min idle, adjust TPS to .57

Rinse and repeat a few times before spending cash.

Do you get the code driving or right after startup on idle?

 

I always pull the code right after startup in idle.

 

Something aint set up right.

My bet is that there is nothing wrong with your hardware. I had previously experienced this when I leaned on my TPS and it went out of adjustment.

Fully clearing the computer and resetting all idle settings cleared it up for me, on the second try.

I like .57 for TPS and about 30 IAC counts.

Also what is modded in your chip for idle settings etc...?

 

I've changed several things for him. It would be easier to just send you .bin if you want to look at it. His car idles fine though.

I still think it's the MAF burn-off relays.

 

My mailbox is open...

 

Same here, copy us both on the .bin

 

By the way, does anyone know exactly where the MAF power on and MAF burnoff relays are located on my 89' camaro ? From just lookin my engine bay, i found only 3 relays that looked like the 2 ones that I just purchased from Autobone (both had same part #'s). One relay one the passenger side by the shiny A/C consenser thing, and the other 2 relays on the drivers side firewall.

Also, do the MAF burnoff and MAF power on relays use the same part # of relay? I hope so, mine are the same.

I went ahead and replaced the 2 relays on my drivers side firewall, and I still have the code 33.

How can I test or clean my IAC? the IAC is the only other thing i know to check or replace (50$ last time i checked).

Thanks for any help..

 

i can tell you right now it isn't the IAC i've replaced it on mine and it is still having the same problem as you