hey guys,
Well... FULL SERVICE only 1K miles ago by one of the best in LA... total confidence in the guy. But about a week ago I was exiting a steep driveway, and BONK, the back end seemed to smack on concrete--it wasn't THAT loud or terrible sounding, but what do you think? I drove all day today flawlessly and aggressively, then--ZIP... nada in the driveway. Engine ignites but won't turn. Thoughts?

 

Friend of mine suggested resetting the alarm. No problem now, started right up. German engineering! Posting this in case anyone else is a goofball...

 

What does "engine ignites but won't turn" mean?

 

How about it turns over but won't fire?

 

Sounds right...still can't figure out why the alarm would have anything to do with this problem.

 

immobilizer not letting the car crank is my guess.

 

Probably - if the switch didn't recognize the transponder chip would the car crank or just do nothing when the key was turned?

 

It didn't makes sense. I had in fact reset the alarm twice before resetting it a third time--when it turned over and started. When I posted my 2nd post in this thread, I was pretty frustrated and reported the events incorrectly--as I actually forgot that I had already reset it. I locked the car, and went away for about 30 mins. Came back, would not start. Locked it again. Went away another 30. Would not start. Then my friend came over, pressed the lock/unlock key a few times--and voila. And that's when I reported what happened. What do you think it was now that you have the full picture? I thought maybe the computer just blipped? And finally cleared?

 

I'm not sure how the factory alarm works or if it would store any codes if it thought there was a fault.

I might try to either take it to a dealer or shop that can pull any codes and clear them (or just unplug the battery), and also try your other key to see if that makes a difference.

 

appreciate the feedback--

One thing I left out was--after my last service--my mechanic forgot to reset the service now mssg--so it is on every day. Maybe that had something to do with the 'lockout'. But anyway--seems fine now, and I'll have that mssg reset this wek.

 

Message has nothing to do with your "lockout".