88 GXL Automatic

When starting my engine to come home today, first, I flooded it by not cranking it long enough.

I pulled the EGI, cranked it, replaced the EGI and started it perfectly.

Then, I started getting the 2-beep (speed signal) error. My tach had failed completely, no reading, but my speedo was fine. Error signal would stop when at stop, but even rolling at idle speed, the beeping would resume.

Possibly related: Terrible gas smell in the vents, worse than ever before.

When I got home, I shut her off, popped the hood and smelled. No foul scents, though I did hear a series of "pfffff" sounds, almost like water droplets hitting a hot... engine. I don't believe it was the FPD because there was no gasoline smell.

Anything specific I should look for in the morning?

Thanks,
Goofy

 

Sounds like a nice fuel leak and fire waiting to happen. It sounsd like its a line under the manifolds so pulling them would be easiest, the FPD does sound like a likely culprit, but old hoses can be too.

 

I'll definitely be checking fuel lines tomorrow, I guess, but what about the tach problem though?

 

Next time you start it I bet the tach works.

You probably fooled the ECU into shutting off the trailing, I forget how this happens but it's happened to me a few times. Turning the key off and on again would've fixed it possibly.

 

2 beeps are not vehicle speed signal failure... it is engine speed signal... The power steering CPU is not getting a tach signal. Thinks the engine is off.

Not related to vehicle movement.

 

no tach could be the trailing coils.....

 

Exactly... and that woould explain the hard start as well

 

I've also had a low battery send my PS unit into a fit before, but restarting would shut it up, but the tach always worked.

 

i have the problem but only if the car revs to redline in nuetral. the tach just dies. but everyother situtation. no problems.

 

Just out of curiosity, why would it stop complaining if I were at a stop though? (Terrh, was right, worked fine in the morning. And the engine didn't smell like gas at all today.)

The start wasn't hard, by the way, it was user error. I cranked and let go accidentally, so it only got about a 1/2 second of gas. Rather than risk a bad flood I went straight to unflood procedure.

-Goofy

 

The bellhousing to firewall ground caused this problem with me when i did my clutch and somehow the ground fell off, i had slow starting and after a minute of first driving aftger i was done with the clutch the tach failed and i got a check engine light, no beeps though, and when i finally found the ground had fell off i put it back on and every thing was gravy, so i vote for checking grounds