ok,so the past few weeks ive been having a few problems with my 85 z28 TPI 700r

all started with throwing a code 32 when cold,and running like crap,then it would throw a code 33,34


recently the car has had a intermittent habit of just dying,no warning,just dead.

well today it happened 3 times,the car would restart,but then die again,then after a few tires it just ran fine,no ses light

i filled the thing up with gas tonight,got 10 feet fro m the pump,ses light,and it died argh wtf?!

tried restarting a few times,it always restarts,then dies right after it fires up,eventually after like 3 attempts it started and ran,so i headed for home,well it did it again,so i parked it and took the + cable off,cleared the codes

restarted car,idled fine,threw it in gear gave it some gas and ses light AGAIN! so i just said FUG it and headed home,and noticed a few wierd VERY wierd things {and this isnt halloween related}

first off,since ive had the car,it never really seems to compression brake,just slowly slowly slows down,never really feels like you let off the gas,well tonight,after the SES light came on for the last time and i headed for home,i noticed when i eased off the pedal because of a car in front of me,the car just seemd to slow down quickly,and the tach dropped{this not normal} ,got back on the gas,the tach would shoot up,and power restored,the engine never DIED,but always felt like it might. after a few miles of this,doing 30 mph in a 55,i got pissed and decided to pass the person in front of me,so i nailed the throttle to WOT,it kicked into first and got all over sideways,which it has never done before{ im thinking} i let it shift itself into second,and it again scooted sideways and fishtailed,pulling HARD harder then it ever has before to full redline 5500. i stayed WOT to see what the car would do,and backed off around a buck 10,let it slow down by itself,and it was slow,then i noticed when the RPMS got to around 2k or so,and i wasnt giving it gas,the engine was acting like the key was being shut off,and turned back on,then it would act normal if i got slightly back on the gas.

so being curious to see what would happen,i was nearing my home,and i stopped to try a launch,all the while the SES light has been on,i just nailed it from off idle,and it went all over the damn road spinning like mad blah blah,just has insane HP and TQ for some reason,i cant figure out WHY NOW?!

BEFORE all this stupif **** happened,the car ran good,pulled hard,but didnt like above 4500 rpms,just felt like the car was put in nuetral

btw when i got home i pulled the codes,33 and 34


CAN ANYONE shed some light on this PLEASE?! im almso tat my wits end with this car,if it doesnt start running right,im yanking the stupid TPI off and putting a carb on it.

 

as for the code 32 when it's cold same here. it's the EGR temp switch that is bad, telling the ECM that EGR gas is flowing through it when it's not.

 

yeah,i already knew that,just havent had a chance to change it yet.

 

Code 34....this was a problem in the factory original prom chips. there was a TSB on this, you had to buy a new chip ($44). If the TSB has been done and you have unplugged your MAF and plugged it back in, you may want to look at the female pins on the harness for the MAF, they can get bent out of shape easily and cause intermittant contact with the MAF pins (been there done that 18 years ago)

 

ill have to check that info out and see which chip i have.

while the engine is running,and no SES light present,should unplugging the maf while running,make the car die right away? thanks for your help .

 

It will either die right away or run like total crap, that puts you into the "default" fueling.

 

Maybe everyones car is different, but mine idled fine with MAf disconnected...MAF was shot and would barely start and stay running, part of the diag is to disconnect it, if idles well, then...

Anyway,,

What troubleshooting have you done besides disconnecting thebattery? I recall your otherpost with a lot of info....seems you have absorbed some of it, i/e knowing anout the code 32...

Why not fix and troubleshoot a few things, then get back to us?