Car won’t go into DRIVE !

[Da445]

@marqie (who works for Lucid) has already mentioned that they are aware of this issue and actively working on a fix.

I agree it can’t come soon enough, but it isn’t a matter of them not listening.

Well, then they need to communicate directly to customers that they're aware of it and working on the issue. Crappy communications are equivalent to not listening in my book. Frankly, the more troubling issue is inadequate SW testing before release. How long until they push an update that is an even greater safety risk?

 

[johnse]

The fact that Lucid continues to invest in factory expansions in multiple locations before investing in solving basic and continuing issues with their in-service fleet shows that they're chasing the wrong objective(s).

I understand your frustration. I don't work for Lucid, nor am I an Air owner (waiting for my Gravity). But I've been a Software developer for 45+ years.

I can tell you with absolute certainty that more than 99% of Lucid's employees have nothing to contribute to solving a software issue like this. Would you have the entire company stop doing anything until the team investigating this issue succeeds in determining the root cause, duplicating the problem, fixing it, confirming the fix works, validating the fix doesn't break something else, and finally delivering it over the air?

You can see in just this forum that a few folks have the problem, but a lot more (presumably, since there are thousands of people registered here) don't have it. I'm sure Lucid tests updates, but if one-in-a-thousand cars has some timing difference--parts behaving at one end of tolerance or the other, environmental issues, etc.--their testing won't necessarily catch it...but with tens of thousands of cars out there, it will show up.

Finding such a problem requires:
* Knowing it's happening
* Getting descriptions of the problem and timestamps that a specific VIN had the problem
* Getting enough such data to find correlations

I would bet that the involved teams started looking into this as soon as it started being reported. Working with CS so they can gather timestamps and logs gets more information to the team, so it's important to actively engage with Lucid instead of just complaining in a forum.

Some bugs of this nature can be extremely difficult to track down.

Please be patient and remember that a company the size and scope of Lucid really can walk and chew gum--or debug software and build factories--at the same time.

 

[Da445]

I understand your frustration. I don't work for Lucid, nor am I an Air owner (waiting for my Gravity). But I've been a Software developer for 45+ years.

I can tell you with absolute certainty that more than 99% of Lucid's employees have nothing to contribute to solving a software issue like this. Would you have the entire company stop doing anything until the team investigating this issue succeeds in determining the root cause, duplicating the problem, fixing it, confirming the fix works, validating the fix doesn't break something else, and finally delivering it over the air?

You can see in just this forum that a few folks have the problem, but a lot more (presumably, since there are thousands of people registered here) don't have it. I'm sure Lucid tests updates, but if one-in-a-thousand cars has some timing difference--parts behaving at one end of tolerance or the other, environmental issues, etc.--their testing won't necessarily catch it...but with tens of thousands of cars out there, it will show up.

Finding such a problem requires:
* Knowing it's happening
* Getting descriptions of the problem and timestamps that a specific VIN had the problem
* Getting enough such data to find correlations

I would bet that the involved teams started looking into this as soon as it started being reported. Working with CS so they can gather timestamps and logs gets more information to the team, so it's important to actively engage with Lucid instead of just complaining in a forum.

Some bugs of this nature can be extremely difficult to track down.

Please be patient and remember that a company the size and scope of Lucid really can walk and chew gum--or debug software and build factories--at the same time.

CS is the second largest issue here. Getting them to return a call, engage, etc. is near impossible these days. Lucid is not scaling their CS in any way, shape or form to support the installed base much less anticipated growth, such that I cannot even get someone on the phone to discuss. I'm complaining here in the hope that more people will come forward with similar issues so that Lucid CS actually takes notice.

 

[borski]

I understand your frustration. I don't work for Lucid, nor am I an Air owner (waiting for my Gravity). But I've been a Software developer for 45+ years.

I can tell you with absolute certainty that more than 99% of Lucid's employees have nothing to contribute to solving a software issue like this. Would you have the entire company stop doing anything until the team investigating this issue succeeds in determining the root cause, duplicating the problem, fixing it, confirming the fix works, validating the fix doesn't break something else, and finally delivering it over the air?

You can see in just this forum that a few folks have the problem, but a lot more (presumably, since there are thousands of people registered here) don't have it. I'm sure Lucid tests updates, but if one-in-a-thousand cars has some timing difference--parts behaving at one end of tolerance or the other, environmental issues, etc.--their testing won't necessarily catch it...but with tens of thousands of cars out there, it will show up.

Finding such a problem requires:
* Knowing it's happening
* Getting descriptions of the problem and timestamps that a specific VIN had the problem
* Getting enough such data to find correlations

I would bet that the involved teams started looking into this as soon as it started being reported. Working with CS so they can gather timestamps and logs gets more information to the team, so it's important to actively engage with Lucid instead of just complaining in a forum.

Some bugs of this nature can be extremely difficult to track down.

Please be patient and remember that a company the size and scope of Lucid really can walk and chew gum--or debug software and build factories--at the same time.

Couldn’t have said it better myself.

 

[Bthegreek]

I understand your frustration. I don't work for Lucid, nor am I an Air owner (waiting for my Gravity). But I've been a Software developer for 45+ years.

I can tell you with absolute certainty that more than 99% of Lucid's employees have nothing to contribute to solving a software issue like this. Would you have the entire company stop doing anything until the team investigating this issue succeeds in determining the root cause, duplicating the problem, fixing it, confirming the fix works, validating the fix doesn't break something else, and finally delivering it over the air?

You can see in just this forum that a few folks have the problem, but a lot more (presumably, since there are thousands of people registered here) don't have it. I'm sure Lucid tests updates, but if one-in-a-thousand cars has some timing difference--parts behaving at one end of tolerance or the other, environmental issues, etc.--their testing won't necessarily catch it...but with tens of thousands of cars out there, it will show up.

Finding such a problem requires:
* Knowing it's happening
* Getting descriptions of the problem and timestamps that a specific VIN had the problem
* Getting enough such data to find correlations

I would bet that the involved teams started looking into this as soon as it started being reported. Working with CS so they can gather timestamps and logs gets more information to the team, so it's important to actively engage with Lucid instead of just complaining in a forum.

Some bugs of this nature can be extremely difficult to track down.

Please be patient and remember that a company the size and scope of Lucid really can walk and chew gum--or debug software and build factories--at the same time.

Nine pages of people complaining about the same issue it’s definitely NOT a minority !
Time stamps have been provided to Lucid engineers already several times indicating the issue .
But most importantly you won’t feel the same way and ask for patience if your car was a BRICK and unable to drive for unspecified periods of time !

 

[borski]

Well, then they need to communicate directly to customers that they're aware of it and working on the issue.

Agreed.

Crappy communications are equivalent to not listening in my book.

They aren’t, though, as not listening means they aren’t working on it, and crappy communication means they’re working on it but you’re possibly unaware. They are obviously not the same.

CS is the second largest issue here. Getting them to return a call, engage, etc. is near impossible these days.

True, I agree CS needs work.

Lucid is not scaling their CS in any way, shape or form to support the installed base much less anticipated growth, such that I cannot even get someone on the phone to discuss.

That is not true, and you’re making a lot of assumptions here. Scaling does not happen all at once; I agree it’s currently not great, but it has been through these waves before, and they have turned it around before. That doesn’t help you *right now*, but is far from “not scaling their CS in any way, shape or form.”

 

[borski]

Nine pages of people complaining about the same issue it’s definitely NOT a minority !

Compared to tens of thousands of cars on the road? Don’t be so sure. We have single digits complaints here; maybe very low double digits. I haven’t counted.

My point isn’t to minimize it, but we *don’t* know the stats.

Time stamps have been provided to Lucid engineers already several times indicating the issue .
But most importantly you won’t feel the same way and ask for patience if your car was a BRICK and unable to drive for unspecified periods of time !

I would hesitate in making assumptions like that. Given context, and the knowledge that they’re working on it, I would certainly be more frustrated - obviously.

But that would not affect my level of patience; this is a temporary issue they will resolve.

Also - your car is not a brick; it drives fine, it just takes a minute or two to boot up. I’m not defending it, but it’s far from bricked.

 

[borski]

Can someone with this problem help me test a theory, assuming it’s reproducible easily?

Try using Keep mode (under Climate), and then see if this occurs.

I have a theory that it is due to the car fresh booting whenever you enter the car, but the displays are simply not showing that. Keep mode would keep the car from fresh booting whenever you unlock it.

Obviously it is a workaround and would drain the battery a bit (about 1-2% per hour) but it may be a decent workaround if it works, and I’m curious if my theory holds.

 

[Celeras]

Compared to tens of thousands of cars on the road? Don’t be so sure. We have single digits complaints here; maybe very low double digits. I haven’t counted.

My point isn’t to minimize it, but we *don’t* know the stats.

Sure, however comparing the reports here to the numbers on the road is just disingenuous. At the time of this post, there are 19 members online on this forum, what are we talking about? I think it's pretty clear to everybody involved this impacts all newer Airs at minimum, even if they all don't encounter the fail case on a daily basis.

Can someone with this problem help me test a theory, assuming it’s reproducible easily?

Try using Keep mode (under Climate), and then see if this occurs.

I have a theory that it is due to the car fresh booting whenever you enter the car, but the displays are simply not showing that. Keep mode would keep the car from fresh booting whenever you unlock it.

Obviously it is a workaround and would drain the battery a bit (about 1-2% per hour) but it may be a decent workaround if it works, and I’m curious if my theory holds.

Well it's every single morning for me, but since there's no way to enable this from the mobile app I would have to leave it running all night when getting out of the car and that's probably not something I'm going to do.

I do know that enabling Climate a few minutes before going to the car didn't seem to change anything.

 

[PureJoy77]

I think it's pretty clear to everybody involved this impacts all newer Airs at minimum, even if they all don't encounter the fail case on a daily basis.

Amen.

 

[borski]

Sure, however comparing the reports here to the numbers on the road is just disingenuous. At the time of this post, there are 19 members online on this forum, what are we talking about?

Hang on, you've got it backwards. I am not saying it isn't a major or widespread problem. I am simply saying I have no idea, and neither do you, for precisely the reasons you stated.

And short of evidence that it's widespread, the assumption would be that it isn't widespread. I'm in a different group with almost 100 Lucid owners; zero of them have the issue, myself included. That also doesn't mean it isn't widespread.

But we have no evidence that it is; that was my point.

I think it's pretty clear to everybody involved this impacts all newer Airs at minimum, even if they all don't encounter the fail case on a daily basis.

That is not clear at all. That is an assumption you've made based on very minimal data, possibly due to confirmation bias. That doesn't make you bad or even wrong; it just is not clear from any actual evidence we've gathered.

Lucid likely knows. We do not.

 

[Bthegreek]

Agreed.


They aren’t, though, as not listening means they aren’t working on it, and crappy communication means they’re working on it but you’re possibly unaware. They are obviously not the same.


True, I agree CS needs work.


That is not true, and you’re making a lot of assumptions here. Scaling does not happen all at once; I agree it’s currently not great, but it has been through these waves before, and they have turned it around before. That doesn’t help you *right now*, but is far from “not scaling their CS in any way, shape

 

[marqie]

Hi, everyone.

Due to a change in a recent software update, drivers may experience a delay when trying to shift out of Park immediately following some longer charging sessions. We are actively working on a fix to deploy in a future software update.

 

[Celeras]

Hi, everyone.

Due to a change in a recent software update, drivers may experience a delay when trying to shift out of Park immediately following some longer charging sessions. We are actively working on a fix to deploy in a future software update.

This aligns with what I've personally seen with my vehicle, however it should be noted that I was debunked pretty quickly earlier in the thread when I tested and suggested that charging/plugging in was the cause. Lots of people came out to say that they see the same thing when the car has not been plugged in at all.

 

[massducati]

Well, then they need to communicate directly to customers that they're aware of it and working on the issue. Crappy communications are equivalent to not listening in my book. Frankly, the more troubling issue is inadequate SW testing before release. How long until they push an update that is an even greater safety risk?

This aligns with what I've personally seen with my vehicle, however it should be noted that I was debunked pretty quickly earlier in the thread when I tested and suggested that charging/plugging in was the cause. Lots of people came out to say that they see the same thing when the car has not been plugged in at all.

Can confirm. It happens consistently after charging, and intermittently after sitting for periods of time.

 

[ColonelBadger]

Can confirm. It happens consistently after charging, and intermittently after sitting for periods of time.

This. I mostly see it after charging but have seen it after parked for quite a while but NOT charging. Seems to be a deep sleep/wake up issue.

 

[Bthegreek]

Hi, everyone.

Due to a change in a recent software update, drivers may experience a delay when trying to shift out of Park immediately following some longer charging sessions. We are actively working on a fix to deploy in a future software update.

Thank you for taking the time to shed some light and recognize the problem. Do you have a rough estimate on the time frame for the fix / update?
Again thank you !

 

[marqie]

Thank you for taking the time to shed some light and recognize the problem. Do you have a rough estimate on the time frame for the fix / update?
Again thank you !

I do not, but rest assured that the team is actively working on it.

 

[Bthegreek]

I do not, but rest assured that the team is actively working on it.

Thank you

 

[bakerjin]

Hi, everyone.

Due to a change in a recent software update, drivers may experience a delay when trying to shift out of Park immediately following some longer charging sessions. We are actively working on a fix to deploy in a future software update.

Thank you so much for your response and open communication! Just wanted to confirm as others have said that this is not isolated to long charging sessions. This happens constantly for me when I'm not charging, like when I'm returning to the car in a parking lot and just trying to get home. I only charge once a week but this happens to me every day.