Car won’t go into DRIVE !

[borski]

Prefer not to post my videos here. If it’s a question of doubt or just curiosity about my rare “clacking + can’t drive/reverse issue”, would be willing to share privately. Have already shared videos with service/engineering and have another set of videos I will be sending to customer care today.

Not doubting, just have no idea what 'clacking' sounds like, haha.

 

[BassWinger]

This has been happening to me in my Air since the last update. Very frustrating. This morning it wouldn't correct until I exited the vehicle, locked it, let it power cycle off, then re-entered. Tech had no other suggestion.

I've started to notice every time it does it, the car thinks the Drivers door is open. Sometimes, it will show the animation that it's open. Other times, it won't let me lock the doors. But it always seems to come down to thinking the door is open.

 

[Bthegreek]

This is going well beyond annoying. Like others, I've rolled my eyes and generally been pretty forgiving of the litany of software issues that have plagued my car. This one is not one that I can be so forgiving of, both because of the severity of the issue as well as because of Lucid's utter silence on the issue and/or any attempt to rollback 2.6.16 to at least temporarily mitigate the issue. This can manifest itself as a safety issue. For that reason, I filed a complaint with NHTSA here: https://www.nhtsa.gov/report-a-safety-problem#index

Perhaps if enough of us do this, it'll finally force Lucid to pay the proper attention to the issue and maybe, to their overall SW development/test/validation process in general.

If Lucid doesn’t fix this issue in the next 2 weeks I am planing to do the same . It’s been a month already with this issue .

 

[Justmurr]

I will throw my proverbial hat into this ring. ‘25 Air Touring, DD Premium FWIW.

For me, thus far this has not been a big deal or really even that noticeable. Feel really badly for those of you dealing with the worst of this.. and I hope my posting about it doesn’t give me bad juju.

Only happened to me a handful of times, the longest wait I’ve had was maybe 40 seconds, happened just last week.
This seems to have “developed” since the last OTA, in May, because I did not have any issues at all until recently or maybe the delays weren’t as noticeable until recently (shrug)

From my experience, seems like the following actions seem to set the stage for this defect to happen - this is merely a wild guess but…

• After charging, I am not always successful at stopping the charge before unplugging, could be something?
• After a quick exit and return, as if some shut down process did not complete?

 

[Cornell]

So, so far everyone that has replied that has this issue has DD Premium.

I have had this issue ever since 2.6.16 as well. For me, it only happens after charging. But _always_ after charging. It's a 2025 AT with DD Pro, no massaging seats. I haven't found any solution to abate the problem when it's happening as others have suggested in this thread. Just have to wait it out, usually 20-30 seconds. The other day though it was over a minute, so I did the Logo reboot, which fixed it. I guess I'm unlucky that I have this bug, yet lucky that it only happens after charging, so at least when I'm out and about I don't worry about it. Will definitely be nice when this is fixed.

 

[PureJoy77]

I've started to notice every time it does it, the car thinks the Drivers door is open. Sometimes, it will show the animation that it's open. Other times, it won't let me lock the doors. But it always seems to come down to thinking the door is open.

Agree 100%. The one commonality we all have with our varied scenarios of experiencing this issue is the opening and closing of the driver’s door. That explains why it happens after charging, not after charging, parked for hours, parked for minutes, with “clacking” (me and a few others reported), without “clacking” (most have reported), etc.

 

[petergottlieb]

I just talked with customer care about this (which is what my service center suggested I do). The official word is that a fix is "in testing." That said, there isn't a timeline for a release and Lucid itself (according to my agent) doesn't know why this is happening or what the common denominator is in the problem. So, that's not great. But if you haven't already, call customer service and let them know your car is affected and it's bothering you.

 

[ColonelBadger]

A little concerning that they don’t know why it’s happening or the common denominator. That suggest the fix is a “spaghetti against the wall” fix.

 

[Adnillien]

A little concerning that they don’t know why it’s happening or the common denominator. That suggest the fix is a “spaghetti against the wall” fix.

You can't read too much into what customer says since they are not part of the OTA team. If a fix is in testing, then the software does know the common denominator and the fix. Customer care is not being dishonest, the details just have not been shared with Customer care. I am not saying this is good, just saying not to read to much into what you hear from Customer care.

 

[tonybot]

A little concerning that they don’t know why it’s happening or the common denominator. That suggest the fix is a “spaghetti against the wall” fix.

I would be surprised if engineering doesn’t have specifics. But in my experience in the past CS is hit or miss and may not really have specific or latest info from engineering. I know that internal communication gap is not great but I will be very surprised if engineering is not on top it.

 

[petergottlieb]

I would be surprised if engineering doesn’t have specifics. But in my experience in the past CS is hit or miss and may not really have specific or latest info from engineering. I know that internal communication gap is not great but I will be very surprised if engineering is not on top it.

I am hopeful you are right about this. I agree that CS doesn't always know everything, but thought the company line at present was a datapoint worth sharing...

 

[californiaboy935]

Really disappointing that we’ve not seen a fix yet and for a $85k car it’s unacceptable to have this behavior. My real fear now is this time next year we’ll still have this issue and it will be forgotten just like the soft close door fisaco. This is the first time I’ve really started to have second thoughts about Lucid. I was planning on a gravity later this year for my wife, but if they can’t fix SW issues that change the behavior of your vehicle, in particular preventing you from driving it (albeit without a reboot or waiting 1-2 months) I’m not sure I trust them anymore.

I think it’s unfair to categorize all of their vehicles as such. I have early build Lucid’s and they have never had any issues like this. I think it’s important to keep things in perspective. The door unlocking this has not been forgotten. It’s something actively being worked on and as a company lucid takes a really good look at consumer feedback.

I’m surprised OP hasn’t found something else is wrong with the vehicle, like a computer problem. I’m not in a position to diagnose from afar, but I’d say it’s important to keep context. I hope you end up getting the gravity as it is a magnificent vehicle and all of the time that I have spent in it I have been extremely impressed with Lucid.

 

[bakerjin]

Agree 100%. The one commonality we all have with our varied scenarios of experiencing this issue is the opening and closing of the driver’s door. That explains why it happens after charging, not after charging, parked for hours, parked for minutes, with “clacking” (me and a few others reported), without “clacking” (most have reported), etc.

I don't believe this is true. My kids have mentioned to me the car did the "clacking" thing when they enter the car first from the rear doors (after I remotely cool and unlock the car). The driver's door never opened.

 

[TonyLieske]

I will throw my proverbial hat into this ring. ‘25 Air Touring, DD Premium FWIW.

For me, thus far this has not been a big deal or really even that noticeable. Feel really badly for those of you dealing with the worst of this.. and I hope my posting about it doesn’t give me bad juju.

Only happened to me a handful of times, the longest wait I’ve had was maybe 40 seconds, happened just last week.
This seems to have “developed” since the last OTA, in May, because I did not have any issues at all until recently or maybe the delays weren’t as noticeable until recently (shrug)

From my experience, seems like the following actions seem to set the stage for this defect to happen - this is merely a wild guess but…

• After charging, I am not always successful at stopping the charge before unplugging, could be something?
• After a quick exit and return, as if some shut down process did not complete?

This sounds almost exactly like my experience. Have never been stranded or anything, usually it just takes an extra ~30 seconds for everything to be ready. Its so intermittent though that I have never noticed a specific pattern.

 

[ColonelBadger]

So the cockpit is definitely hung for a while when you can’t go in to Drive. I typically exit the vehicle and lock it, wait a few seconds and then unlock it and I’ve noticed a couple of things

1. Sometimes the left two cockpit screens stay on longer then the rest of the screens after locking the vehicle. Suggesting they’re unresponsive.
2. After waiting for those screens to finally switch off and when I get in to the vehicle after unlocking the car the screens will flash and reboot. Suggesting the OS has detected they’re unresponsive and need rebooting.

This is what I’ve see after charging.

 

[Kugs10]

I don't believe this is true. My kids have mentioned to me the car did the "clacking" thing when they enter the car first from the rear doors (after I remotely cool and unlock the car). The driver's door never opened.

It seems that the software gets caught in some sort of a delay upon entering the vehicle. The delay occurs at various points in the entry process. It may occur during facial recognition, during confirmation that doors are closed, during adjustment of the seating position, etc. The display locks according to what stage in entry the delay occurs. I don't think that the stage of entry is what causes the delay but rather various stages of entry are affected by the delay.

This is all speculation of course, but it feels as though the system is running a diagnostic on something, like the battery or motors or something, and the diagnostic is causing a delay. The most recent software update was directed at motor/battery efficiency so I wonder if the diagnostic process was adversely affected.

 

[ColonelBadger]

It seems that the software gets caught in some sort of a delay upon entering the vehicle. The delay occurs at various points in the entry process. It may occur during facial recognition, during confirmation that doors are closed, during adjustment of the seating position, etc. The display locks according to what stage in entry the delay occurs. I don't think that the stage of entry is what causes the delay but rather various stages of entry are affected by the delay.

This is all speculation of course, but it feels as though the system is running a diagnostic on something, like the battery or motors or something, and the diagnostic is causing a delay. The most recent software update was directed at motor/battery efficiency so I wonder if the diagnostic process was adversely affected.

Yeah I believe the latest SW detects more anomalies so I wonder if that process is taking too long sometimes and locking the cockpit screen. Not sure why charging makes that worse.

 

[Celeras]

I've posted a few times in this thread that this happens to me every single morning when the vehicle is plugged in, and that it lasts for several minutes.

Thus far I had lasted this long without seeing it in a non-plugged-in situation, but that can no longer be said. Its getting hotter now so I've started turning on climate before walking to my car on lunch break. Doing that has caused this to occur in the parking lot 4/4 times. Its a shorter freeze than the plug variety, maybe only 30 seconds. But otherwise exactly the same.

Sone people have said this happens to them randomly, but perhaps it's not so random after all?

 

[ColonelBadger]

I've posted a few times in this thread that this happens to me every single morning when the vehicle is plugged in, and that it lasts for several minutes.

Thus far I had lasted this long without seeing it in a non-plugged-in situation, but that can no longer be said. Its getting hotter now so I've started turning on climate before walking to my car on lunch break. Doing that has caused this to occur in the parking lot 4/4 times. Its a shorter freeze than the plug variety, maybe only 30 seconds. But otherwise exactly the same.

Sone people have said this happens to them randomly, but perhaps it's not so random after all?

Yes!!! Same thing. If I enable climate remotely to cool the car I also have the same problem getting in to drive.

 

[hvylumber]

Okay so the facial recognition being a contributing factor is definitely debunked, my next theory is that it’s related somehow to the Bluetooth connection to the phone key…. The loud clacking I’m hearing is from the Bluetooth connection to my phone audio, and when that stops the car allows driving