Faster Chip Available for Retrofitting in the Air?

Hummmm..... Does anyone know where the SOC is? I would bet that Lucid was using a Orion Nano and the upgrade is just a Orion NX or AGX. If that is the case, the whole SOC is just on a SO-DIMM and swapping them will take a whole 10 seconds providing you can get to it easily. All of the Orion's are the same architecture with different ARM core, cuda and tensor cores and more RAM. So it should be plug in and play. A Orion NX 8GB will cost $500 while the 16GB will be $700. Compute difference is 70 vs 100 TOPs while the Nano was was up to 40 TOPs. I have a Orion NX 16GB I could test with if someone could point me in the direction of where it is in the car. With that being said, I only have dream drive and do not have the extra cameras, so the drag on the SOC from all the inferencing is not happening on my car, thus even if I did the upgrade, I probably would not be able to notice the difference.
Infotainment and ADAS are separate computers. The discussion is of replacing the infotainment computer, that’s why it really has no effect on ADAS. Just UI speed.
 
The Lucid uses the DRIVE Orin chip which maxes out at 254 TOPS:

More info at
Makes sense, but that begs the question of what the upgrade could and would be. Orin was based on Ampere, the Lovelace SOC was canceled and Blackwell will not be out until next year at the earliest. Dream drive is probably on the single Orion board, DDP needs to be on the dual Orion Board. The only upgrade option I am seeing is Quad Orion by linking two Dual boards together. If you have nVidia developer access there is a old on demand webinar called DRIVE AGX Hardware Update with NVIDIA Orin that walks through the options and what you get.

 
The more I use my car DD, the more I want the unlock to be faster. Even with the app set to persistently active on my Android it lags to open. The fob is even worse I feel.

I did finally reboot my car and that didn't take too long (held down Air logo). It was acceptable. It's the unlocking for me.
 
The more I use my car DD, the more I want the unlock to be faster. Even with the app set to persistently active on my Android it lags to open. The fob is even worse I feel.

I did finally reboot my car and that didn't take too long (held down Air logo). It was acceptable. It's the unlocking for me.
This is probably more of a backend server thing vs a in car compute upgrade. A educated guess would be that there is some backend key authentication that happens on some server somewhere with a few back and forth handshakes.
 
Did we not hear from Lucid that there is no plan to retrofit the chip? Are people still speculating about this?
 
People aways want what they can't get (or can't get immediately). That's why this thread and every thread on OTA updates are so popular.
We live in a world that provides near instant gratification for almost anything. Sometimes enjoying the anticipation of something big, like a major OTA update, is just as satisfying as receiving it. At least this is the perspective I am trying to keep.
 
We live in a world that provides near instant gratification for almost anything. Sometimes enjoying the anticipation of something big, like a major OTA update, is just as satisfying as receiving it. At least this is the perspective I am trying to keep.
This is a very healthy attitude! I applaud you, I do my best to savor wanting something as much as having it.
 
This is probably more of a backend server thing vs a in car compute upgrade. A educated guess would be that there is some backend key authentication that happens on some server somewhere with a few back and forth handshakes.
Unlocking a car shouldn't rely on communication with any server. It would be clearly bad design if it does.
 
Unlocking a car shouldn't rely on communication with any server. It would be clearly bad design if it does.
Unlocking the car with the Mobile Key or Fob does not need communication with a backend server. The only time it does is when you're using the Mobile App to remotely unlock the car.
 
Unlocking a car shouldn't rely on communication with any server. It would be clearly bad design if it does.
Well the question I was responding too the poster called out his android phone connecting and unlocking their car and since the phone is not using Bluetooth or NFC for proximity(as far as I can tell), there would be some backend server key authentication especially since that key needs to be different from what we have on our physical key. However, the back end authentication from a security standpoint is really not as bad of a design as you are implying. Only have had the car for a week now and don't fully know how things work yet, but with other keys, if I can intercept a few of the codes from your key and figure out what the next rolling code is going to be, I can get into your car and have a copy of that key. This set up would piss a lot of people off and thus would probably way too unpopular to have and still sell a lot of cars, but there is a lot of merit to it.
 
Unlocking the car with the Mobile Key or Fob does not need communication with a backend server
This is correct.
since the phone is not using Bluetooth or NFC for proximity(as far as I can tell)
Mobile key is Bluetooth. Both for proximity detection and authentication.
However, the back end authentication from a security standpoint is really not as bad of a design as you are implying.
It's not that it's bad from a security standpoint, it's bad from a practicality standpoint. What if I'm in an area without LTE? I just can't unlock my car?
with other keys, if I can intercept a few of the codes from your key and figure out what the next rolling code is going to be, I can get into your car and have a copy of that key
Correct, this was a terrible idea, but most manufacturers haven't been doing it this way even with their regular old key fobs for years now. It's not just a predictable rolling code. Unless you're Kia and you're full of bad decisions.
 
Interestingly enough Lucid is not supported by Google's digital car key even though Lucid is a member of the Car Connectivity Consortium.
Digital Car Key requires UWB for passive unlock. It is the right technology for this usage, but it is relatively new technology. All recent iPhones support it, but only a few Androids have it (mainly Pro Version of Pixel and Samsung).
I guess Lucid decided to go (or even had to go) with what was already well known at the time of Air development. Maybe Gravity will have UWB
 
Digital Car Key requires UWB for passive unlock. It is the right technology for this usage, but it is relatively new technology. All recent iPhones support it, but only a few Androids have it (mainly Pro Version of Pixel and Samsung).
I guess Lucid decided to go (or even had to go) with what was already well known at the time of Air development. Maybe Gravity will have UWB
I cannot confirm Gravity will have this. But I have a very strong suspicion it will.
 
Back
Top