Lucid Gravity 3.4.0 software update

Miraculously I just received a push notification for the update!
I just received the update notification also. Unfortunately my Gravity is in service for a couple of minor things and I will likely not get it back until next week so I cannot play with the new update for a while.
 
Prior to 3.4.1, my car stops charging once it hits the target and throws an error. This persisted through the 3.4.1 update. It will charge at a high AC rate (so I’ve no issue at 80A), then once it hits 80% (my set limit), it throws a “Vehicle Not Charging” error. Happens even when I use the Lucid wall adapter. Seems unique to me but Lucid is aware. Only annoying in winter as it then loses an absurd amount of range overnight with 25 degree temps. Which also seems to be a bug.

Example - Charges to 308 miles by midnight - throws the error, then is down to 297 miles by 7:00am. See pic.
Lower estimated range by morning isn't a surprise. Colder battery, colder cabin, etc. The GOM (Guess-O-Meter) takes many factors like that into account to estimate how far the car might be able to go, but of course that's all it is... an estimate.

I haven't been getting any home charging errors in the car, but I have mine limited to only 20A. I'd rather slow charge it unless I need faster charging for some reason. Unless I'm starting from a low SOC (which is rare), an overnight home charge makes it to 80% slow charging. And I'm not on a TOD rate plan where I need to squeeze it into a shorter time window for cheaper rates.
 
Lower estimated range by morning isn't a surprise. Colder battery, colder cabin, etc. The GOM (Guess-O-Meter) takes many factors like that into account to estimate how far the car might be able to go, but of course that's all it is... an estimate.
Yes, but…if I didn’t leave the car plugged in and it had 308, it has had 305/306 by morning with the same weather conditions vs the 297 when it was plugged in all night and threw the error. There’s an odd “excessive drain” issue going on when it’s plugged in - or at least the calculations are getting thrown off. And it’s happened over 10 times, so it’s consistently off.

May move this to bugs thread as I can’t pinpoint to 3.4.1…

BTW, I charge at 48A usually. I can charge higher, but choose not to.
 
1770407283291.gif
 
Yes, but…if I didn’t leave the car plugged in and it had 308, it has had 305/306 by morning with the same weather conditions vs the 297 when it was plugged in all night and threw the error. There’s an odd “excessive drain” issue going on when it’s plugged in - or at least the calculations are getting thrown off. And it’s happened over 10 times, so it’s consistently off.

May move this to bugs thread as I can’t pinpoint to 3.4.1…

BTW, I charge at 48A usually. I can charge higher, but choose not to.
It shouldn't be drain as long as the battery% isn't dropping (which presumably it isn't because you're plugged in and drawing power to keep it up to 80%). Likely just the estimated range calculation (which is always rough to begin with).

While it sounds like you had similar conditions on other nights to compare against, it's never the exact same conditions. But yeah, it could be some quirk in the calculations. I would almost think it would be the other way around when plugged in all night as the battery might be just a little warmer from charging. But what goes into the GOM calculation is always a mystery, and rarely very accurate. Plus unless you start the nav, it really has no idea how you're going to be driving anyway. Usually they rely on recent driving patterns, where a taking the highway the day before would bias the calculation toward higher speed thus lower range. Or vise versa. The GOM can shift 30% or more based on temperature and other conditions. 9 miles is a relative speed bump in the grand scheme of GOM variance.
 
Nothing for me.
Tried to spend some time watching Emad Dlala on "Batteries Included Podcast."

I say "tried," because he had to drop off completely.
Looks like the VP of Technology and Digital needs to upgrade his home WiFi.
 
I had that prob elm. It bricks my car. 2 days at serviced center and its running well with 3.4.1
That’s good to know. I’m like 150 miles from the SC so it’s been mobile service for me. They’re supposedly trying something tonight to see if they can fix it, they there’s no guarantees at this point.

I just hope mobile service can address the issue.
 
Oddly, the first week I owned the vehicle, parked outside in sub 30 degree F New England weather, with no home charging, I was loosing 5-10% SOC per night. In the past week this has improved to 0-1% per night, in even colder weather (close to or below 0F). Only thing I can think of is the key fob update, as I haven’t yet received the vehicle update. Thoughts?
 
Oddly, the first week I owned the vehicle, parked outside in sub 30 degree F New England weather, with no home charging, I was loosing 5-10% SOC per night. In the past week this has improved to 0-1% per night, in even colder weather (close to or below 0F). Only thing I can think of is the key fob update, as I haven’t yet received the vehicle update. Thoughts?
Definitely something way off there. Short of it actually being driven, the only thing I can think of that would use up 5-10 kWh in 12 hours is cabin & battery heating. Electronics ain't gonna burn that much. That much electricity doesn't leak out into the air, it has to have a load.

Must have had a toasty warm car all night if you were really seeing the battery drop that much between drives.
 
Definitely something way off there. Short of it actually being driven, the only thing I can think of that would use up 5-10 kWh in 12 hours is cabin & battery heating. Electronics ain't gonna burn that much. That much electricity doesn't leak out into the air, it has to have a load.

Must have had a toasty warm car all night if you were really seeing the battery drop that much between drives.
According to the cabin temperature as displayed in the app, the cabin was very cold both before I went to bed and when I woke up. But again, this SOC drop stopped after about a week, maybe around the Key FOB update.
 
Of course, can't say all 3 were pressed at the same instant, but for me, just keep pressure on all 3 will eventually reboot after 5 minutes or longer.
Never had any problem the few times I reset the Lucid Air.
Yes. 5’ or longer and it will eventually reboot. Just have to be patient and continue until the fingers are numb. Never like that with the Air. Always enjoyable to do the reboot after a long day of work and wanting to just go home…..
 
Yes. 5’ or longer and it will eventually reboot. Just have to be patient and continue until the fingers are numb. Never like that with the Air. Always enjoyable to do the reboot after a long day of work and wanting to just go home…..

It shouldn’t take that long. You have to press the brake first and then hold the buttons on the steering wheel. If you do them at the same time it usually won’t register.
 
Back
Top