Search results

A possible given the time span people have stated is a temp derate. We can’t check most of the related temps obviously, but have a look in your charge inlet or gun for any debris or something that could increase connection resistance. Reducing charge power due to inlet pin over temp would be a...

At AC charge speeds of 19kW, there is no good reason to derate speeds, not for the battery at least. For DC charging yes but those reasons don’t really apply here. Weak stance from Lucid.

Tesla charging is nice and convenient, but expensive

NACS itself is pretty easy. The high power DCFC capability of Gravity to step up the 400V, not as simple to implement.

May you be blessed with the first drops of 3.0

Received 2.9.3. Was on 2.9.2. Started update and it almost immediately ended successfully. Don’t think it actually did anything.

I do not and never have. Also the seat never actually moves when it displays the message. 2.9.0 related, I just received a 2.9.3. The only notes are that it fixes a prior 2.9.2 issue. Strange considering they already repushed 2.9.2 to the users whose cars were bricked.

Fun piece of 2.9.0 (2.9.2 actually) feedback. Every time I get in the car now, the dash displays a message about adjusting seating position, implying its profile switching. I’m the only one that drives the car, no amount of switching around profiles or resets has stopped this message from...

Checked my app after finishing a V2V session. I haven’t seen this “Energy Bank Duration” time before. Seems to go away pretty quickly after opening the app too. I can only interpret this as provision for V2H, maybe it’ll actually be real? Edit: This is on Air, not Gravity

Happened to me twice in the past week, and never before. Once before and once after 2.9.

Has been on WiFi with connectivity since the update just fine. Tried signing out and couldn’t sign back in. Power cycled the TCU by unplugging and that fixed it.

Anyone having connectivity issues after 2.9.0/2.9.2? When the car is outside of WiFi, the app shows “Vehicle Offline” even though the car shows service and seems to be searching fine. Tried hard reset

Lucid and myself can trade stories about ridiculous regressions and failed OTAs. We’re still OTAing direct in the dead of night without user involvement.

This issue makes me again wonder what happened to the “Insider Track” type communication we received a while ago? Some people want to try new features with risk accepted, maybe they have relatively easy access to another car. That could have gone a long way with this issue.

Confirming that as someone with a fault free original install of 2.9.2 on Pure, I did not receive another OTA of the same version as others did. Looks like an interesting targeted deployment.

Agree things happen. I’ve been in this position to manage as well as being one of the engineers on call for events like this. It’s a learning experience but agree that how they respond and fix is what we should takeaway, more than the issue happening itself.

If it was my car, I’d personally try to keep it asleep to preserve 12v, just in case it is an overall issue with HV and not just drive. Again my 0.02, but I personally wouldn’t want to be awaiting an OTA fix and have a dead battery when it does come.

First road trip in my 24 Pure. Leaving home it said we’d arrive to the first charge stop at 18%. About an hour into the drive, the estimate was still the same, but the route planning got cold feet and wanted me to add a much earlier, very short stop. I had to fight with the navigation while...

I’m on 19s and threw the hubcaps back on for the long drive. Love how they ride and love the range, but every time I’m next to a nice AGT on the highway with the nice 21s I feel quite inadequate.