Safe and reliable production changes, and how Rivian recently got this wrong(blog.substrate.tools) |
Safe and reliable production changes, and how Rivian recently got this wrong(blog.substrate.tools) |
and then it goes into canary testing, "pre flight tests" and rollback
When I first got the Volvo the GPS and LTE connection would periodically stop working for a day or two. They pushed a fix for it. Later they added CarPlay, which wasn't there when I got the car. Good updates. But not as frequent at Rivian.
Was Volvo able to fix it with another OTA or did people have to go in for service?
I tried to buy one, but the dealer in Montana was such a pain about it! How did you like it as a car?
Sounds to me like they certainly could have a canary fleet, but if they do, they didn’t have sufficient process controls to only allow updates to the public after having gone through canary testing.
I think you're suggesting they might have a canary fleet, but there wasn't anything/enough that preventing a mistake from bypassing the carry fleet before going to production?
Could be!
For example:
apt-listchanges: Changelogs
---------------------------
bind9 (1:9.16.48-1) bullseye-security; urgency=high
* New upstream version 9.16.48
- CVE-2023-4408: Parsing large DNS messages may cause excessive CPU
load
- CVE-2023-5517: Querying RFC 1918 reverse zones may cause an assertion
failure when "nxdomain-redirect" is enabled
...glibc (2.31-13+deb11u8) bullseye; urgency=medium
* debian/patches/any/local-qsort-memory-corruption.patch: Fix a memory
corruption in qsort() when using nontransitive comparison functions.
...imagemagick (8:6.9.11.60+dfsg-1.3+deb11u2) bullseye; urgency=medium
* Fix CVE-2021-3574: memory leak was found in TIFF coder
* Fix CVE-2021-4219: a special crafted file could lead to a DOS.
* Fix CVE-2021-20241 / CVE-2021-20243: divide by zero in
some coders (Closes: #1013282)
And so forth. If something makes me raise an eyebrow I can go look at the source code to see what's up. I also like for upstream maintainers and other members of the community being able to do that same. Having that process in place helps keep everyone honest. Why not have this for my car's computers too?For the install I would rather download a signed image onto a USB drive and flash from that versus letting my car communicate with the mothership indiscriminately. I also want to downgrade at any time with a previous known-good image when there's something about the update that I don't like. For example, if it sends my car's console unit into a bootloop.
(Edit: 4th power, damn) https://en.m.wikipedia.org/wiki/Fourth_power_law
So a 8500 car does 64x as much road wear as my small sedan.
For me, I don't want to have to tinker too much, but I want to be able to. I think the ideal would be something like SteamOS on Steam Deck where you can get into the system, and you can change or add things. But the default is just having it all take care of for you.
That said, cars have all sorts of regulations about how certain things work. I have no idea how any of the above ideas would interact with those regulations.
Bricking am expensive smart phone is infuriating, but bricking an expensive household appliance or even more expensive automobile is a non starter.
The signed image on USB seemed to be the norm from maybe 2010-2020 but it seems cellular connectivity has gotten too cheap and telemetry too valuable...
I got my R1T in June 2023 and since here are a few things they've improved, just off the top of my head, not bothering to look it up:
1. Significant improvement to ride quality via different / better suspension tuning.
2. Ability to schedule warming the cabin and pre-condition the battery
3. Completely redesigned the UX for setting drive modes and suspension height (for the better IMO)
4. Added a ton of car info, like battery temp, motor temp, and other info like altitude, various angles the vehicle is at (for off-roading), degrees the front wheels are turned
5. Added additional settings for ride softness / firmness (I got this update yesterday and haven't tried it yet)
When an update is ready I get a notification in the car and from the Rivian app on my phone. I can just hit apply and it installs it.
IMO a USB install would be a substantially worse experience and it would be much less likely that customers would actually install it.
But, for the type of person who just wants the car to stay the same as it was the day they bought it, and never change, it's not the vehicle for them. Personally I really like that it's continually improving and I don't have to go in for service or even go out to the truck to do an update.
Nevermind that the wealthy ain't fretting for one second over OTA updates. Imagine a personal vehicle budget where the Porsche is technically your daily driver, but you never drive it because you're driven everywhere.
A /personal IT team/.
A boy can still dream!
I never said I didn't want updates. What I said is that I want to understand what the updates are and then choose to upgrade or downgrade when and how I see fit. Or better yet make the updates OSS and then let me do my own builds with the features and functionality I prefer as they are developed.
One thing that is right is that a Rivian is not for me, for a lot of additional reasons.
https://twitter.com/ajisuzu1/status/1681123111364620294?s=46
TLDR; From a road wear perspective there is no real difference between a heavy EV and a lightweight smaller ICE.
Edit: Not sure why I get downvoted so heavily. It is just a fact that the weight difference between an EV and comparable ICE has no measurable difference to road wear.
People like the above poster just like to touch on the fourth power law but not how the calculations actually work.
ESAL is part of that calculation. A 5 axel semi has a ESAL of 2.35, a dumptruck ~4, a 3.5ton vehicle .004, a 3ton vehicle .002. When we are talking about the difference in hundreds of pounds between EV and ICE, there is no wear difference.
The difference in road wear between a 2k lbs. vehicle and an 8k lbs vehicle is too small to matter.
I guess it'll be interesting when we are trying to support electric medium duty or heavier trucks, like WA is trying to do. Guess they'll be subject to Class 7 & 8 weight anyways, because if you try to make a currently-medium-duty truck into an EV it's way over the limit.
I mostly just have doubts about our current revenue model scaling for it (since it's heavily reliant upon gas tax and the truck weight $$ amounts don't match up), and the general lack of lighter EVs in the US. Something will have to change there
I'd be totally happy in the city with a 2-2500 lbs BYD Seagull or whatever. But that vehicle doesn't exist in the US.
I want a $10k small car for just intracity trips. Easier to park, small battery charges fast enough at home even on 120V 20A. Cheaper to insure.