2.8.0 Software Update

Geofencing is simply recognizing your location as a condition of whether is feature is enabled or not.

For geofenced charging, you might decide for myriad reasons that are not relevant to the discussion, you do NOT want/need to pull 17-18kwh from your charger at HOME because you're generally in no rush, however, if you are hitting a level 2 charger on the street while running errands and getting lunch, you want it to go as fast as possible.

In short, if you desire the ability to have different maximum charging rates (for L2 only, they're not doing this for L3 as they don't want people clogging up limited L3 chargers) based on WHERE you are, that's what geofenced charging rate selection is for.
I understood the geofencing but couldn't envision having to set different maximums. I get it now - thanks.
 
It turned out to be much more useful on our bmw than I originally thought, especially at low speeds. I do admit I'm more excited about not having to move the steering wheel on long straight highways like it in California
 
It's also likely that I will get better at spotting when that MIGHT become necessary over time and stage my hands on the wheel in any case (uncomfortable overtakes around corners with a higher speed entry, for example, where it is bad form to even get close to your lane boundary, let alone crossing it).
I've noticed a tendency for the car to want to take an exit when I'm using DA in the right lane. So, watch for that. It surprises me because I would expect the default to be to stay on the highway (esp since the road is mapped .. it would know that the widening lane is an exit not a slow lane up a hill for example?). Maybe I'm misunderstanding what the car was doing but just fwiw.
 
I've noticed a tendency for the car to want to take an exit when I'm using DA in the right lane. So, watch for that. It surprises me because I would expect the default to be to stay on the highway (esp since the road is mapped .. it would know that the widening lane is an exit not a slow lane up a hill for example?). Maybe I'm misunderstanding what the car was doing but just fwiw.
Experienced that during my first EV experience (rented Tesla Model Y 3 years ago) and have been on the lookout for it ever since. I've felt the Air 'flinch' in those instance, but not actually follow the wrong way. I've been testing more extensively in anticipation of hands free arriving and thus far have only gotten a few minor flinches (fraction of a second, and not too aggressive), or nothing at all. I, too, wonder what the technical nuances are of mapped highways.
 
I've noticed a tendency for the car to want to take an exit when I'm using DA in the right lane. So, watch for that. It surprises me because I would expect the default to be to stay on the highway (esp since the road is mapped .. it would know that the widening lane is an exit not a slow lane up a hill for example?). Maybe I'm misunderstanding what the car was doing but just fwiw.
Same here, especially left and right turn lanes on a curve, and not just with Lucid. I took a 1,200 mile road trip, and this was really frustrating (as demonstrated in the Out of Spec Ridge Back ADAS test in a construction zone in his case) . Then I started to notice that some of the exits were painted with dashed lines and that got me wondering if those are partially for autonomous driving. This is what ChatGPT says "In summary, while dashed lines at highway exits have long been a tool for guiding human drivers, they are increasingly important for the safe and efficient operation of autonomous vehicles."
 
Our 2023 AWD Pure always tries to take the exit when driving in the right lane. I just thought that was the nature of the beast.
yeah but why would it do that? typically the exit would not be taken and seems the safer choice at speed anyway (e.g. let human intervention take the exit if needed). unless there's some type of AI processing and it is trying to be trained, that's the only reason why I could see that happening???
 
Experienced that during my first EV experience (rented Tesla Model Y 3 years ago) and have been on the lookout for it ever since. I've felt the Air 'flinch' in those instance, but not actually follow the wrong way. I've been testing more extensively in anticipation of hands free arriving and thus far have only gotten a few minor flinches (fraction of a second, and not too aggressive), or nothing at all. I, too, wonder what the technical nuances are of mapped highways.
I've gotten a few of those flinches, not many at all. I think sometimes it can't quite figure out the lane situation so it hesitates ever so briefly. pretty cool actually to see it try to deal with the situation real-time. glad it starts to slow in those cases (just briefly then it comes back to life after it figures out the situation).
 
Seems not. I’d much rather they delay it if necessary to make sure it is perfect before releasing it. I think they made a mistake by giving a specific date because that will just lead to all sorts of complaining.
Holding accountability of a $150,000 car and a 7 billion dollar company to meet simple dates seems reasonable
 
Holding accountability of a $150,000 car and a 7 billion dollar company to meet simple dates seems reasonable
Lucid is immune to this (most expecting that :D)
They might have pushed it to at least one and that may be happened to be not one in this group or one being silent.
 
Holding accountability of a $150,000 car and a 7 billion dollar company to meet simple dates seems reasonable
LOL is all I have to say. I believe Lucid made a mistake of giving a specific date, for this exact reason, but let's not kid ourselves that companies/individuals/anyone who lives on planets earth hasn't missed a deadline before.
 
LOL is all I have to say. I believe Lucid made a mistake of giving a specific date, for this exact reason, but let's not kid ourselves that companies/individuals/anyone who lives on planets earth hasn't missed a deadline before.
Yes, no issue with missing deadlines as this are not life threatening fixes.

At some point Lucid needs to stop making this a habit. I think they didnt miss there dates, update may have been pushed to selective few to make sure on the bugs. They delivered Super Charging as they promised :d
 
yeah but why would it do that? typically the exit would not be taken and seems the safer choice at speed anyway (e.g. let human intervention take the exit if needed). unless there's some type of AI processing and it is trying to be trained, that's the only reason why I could see that happening???
My guess is that it is trying to follow the solid white line on the right edge of the lane, which follows the right side of the exit lane rather than the through lanes of the highway.

I get the little flinches others have described. Generally I find the ADAS is reasonably good. The only troubling thing that has happened to me (thus far) is that sometimes when I pass an exit, the car drifts left onto the dotted line separating the travel lane from the passing lane.
 
Yes, no issue with missing deadlines as this are not life threatening fixes.
Well actually they could be life threatening if they get the system wrong, so I agree it is better to be late and right then on time and wrong.
 
Well actually they could be life threatening if they get the system wrong, so I agree it is better to be late and right then on time and wrong.
Yes, one thing Lucid might have not said was date. Anyhow it seems like they want to put out his info before earnings. Hope this is being tested by select few owners now.
 
So we're on day one of a minimum 2-3 week rollout, and people are complaining about Lucid missing dates. Sounds about right.
 
So we're on day one of a minimum 2-3 week rollout, and people are complaining about Lucid missing dates. Sounds about right.
You made me laugh...even though I am one of the people complaining. I have never complained about a delayed update before, but I have been so excited for this one that I built it up in my head (even though I know from prior experience, that these are rolled out in phases)
 
Seems not. I’d much rather they delay it if necessary to make sure it is perfect before releasing it. I think they made a mistake by giving a specific date because that will just lead to all sorts of complaining.
Good business practice is that you don't announce a specific release date for anything without confirming first that the delivery is ready for general availability. And if an unexpected issue comes up after you announce a specific release date, you give your customer base a heads-up that there is a delay.

There's nothing good that can result for a company when they announce a specific date for a much-anticipated product release, and then there are crickets from the company. This problem increases as the customer base grows.

If this anticipated software release has been delivered to any of the customers, a simple message from the company like "The release has begun rolling out now. Be patient."
 
Back
Top