i was at the track friday and everything was doing good until i got a real good hard launch. i pulled a 1.800 60' and the car did not shift into second gear. is this the infamous OBD1 problem of not being fast enough? OR is it becuase i had my belt off for 3 previous runs and b/c it was in the red zone (felt like shifts got slower as the battery level dropped)

im just curious b/c i dont want to do any suspension ods for better 60's if it isnt going to shift. ill go ahead and swap BACK to an OBD2 computer and be done with it

thanks for any info/opinions

 

OBD1 may not have a 1ghz. Intel processor, but it is plenty fast to calculate the instructions given to it. You either have a solenoid fault or a mechanical failure.

 

You need to at least charge your battery if it's not got a belt on it. Your running the ECM too low on volts and your gonna mess everything up including the injector firing.

-Shannon

 

If the computer sees to big of a diferance between rpms and mph the trany will go into safe mode thinking it is sliping and not shift. It is very common problem when using a higher stall converter. It will only do it when you get a very hard launch with no tire spin. I fought it for quite some time pulling the trany 3 times thinking it was the problem. I talked with my programer Ed Wright and he tried a few changes in the pcm and after 2 tries the problem was gone.

My 60's were in the 1.5s and the trany would not shift untill I let off and it would go right into 3rd. Ed is the only one I know of that can fix it.

I also ran with out the belt for a long time but that is not it.

I now run 60's in the low 1.3s with no problems.

I hope this helps, Rick

 

I had the same problem and it turned out to be the TPS. Replacing it was easy and the problem was gone. Hope this helps.

 

SO, i got half and half here. is it that the OBD1 is physically to slow to handle hard launches with my 3200 stall and 333 RWHP or is it that the OBD1 wasnt fast enough to recieve all the info with the battery voltage dropping ?

 

I think you are confusing processor speed with programming limitations. The OBD-I and OBD-II setups use the same processing speed, as far as I know. Its the programming in OBD-I that presents a problem with high stall converters. As Drag Bear points out, appears Ed Wright has found a way to overcome those programming limits.