Earlier quoted context omitted.
What's the priority then, telemetry data? Why is it rough out there?
Probably due to fires, failures, and fatigue.
Rivian software update bricks infotainment system, fix not obvious
301–310 of 386 posts
Re: Rivian software update bricks infotainment system, fix not obvious
#302Earlier quoted context omitted.
Teslas occasionally need to reboot / hard reset their software too, when driving no less, and during that period all that information, and most of the controls, are unavailable (like windshield wipers, etc.)
As someone who lives in a place where it rains almost every day for 9 months of the year, this reinforces my decision to never buy a Tesla. Does this kill the headlights too?
Re: Rivian software update bricks infotainment system, fix not obvious
#303Earlier quoted context omitted.
Having worked on 25K machines, I can assure you that it never deployed to every single machine and failed to do so in interesting ways all the time.
As a frontend web developer I'm constantly deploying software to many thousands of machines. And you know what? It's pretty damn simple.
And fortunately, no one bats an eye at a slightly broken site, but everyone hates even a slightly broken vehicle.
Re: Rivian software update bricks infotainment system, fix not obvious
#304Earlier quoted context omitted.
Having worked on 25K machines, I can assure you that it never deployed to every single machine and failed to do so in interesting ways all the time.
As a frontend web developer I'm constantly deploying software to many thousands of machines. And you know what? It's pretty damn simple.
If you had a hard requirement that a page load could never take more than 100ms, regardless of network conditions, you'd have quite a challenge on your hands.
Re: Rivian software update bricks infotainment system, fix not obvious
#305Earlier quoted context omitted.
I had to do this once or twice (its very very infrequent in my experience) and one time it was genuinely terrifying, as I had lost blinkers etc where a few interstates all intersect and merge etc. I still do love the car though.... but a very sketchy moment that I shouldn't have brought on myself while driving in that situation.
> I had to do this once or twice (its very very infrequent in my experience) This is something that’s _never_ supposed to happen. > but a very sketchy moment that I shouldn't have brought on myself while driving in that situation. How on earth can you rationalize a Tesla performing an update/hard reset while driving as _your_ fault? It should never be allowed to happen!
Re: Rivian software update bricks infotainment system, fix not obvious
#306Re: Rivian software update bricks infotainment system, fix not obvious
#307An interesting thought experiment: what happens when these vehicles are out of warranty, and automakers accidentally send a vehicle-bricking OTA update? Isn’t that property damage?
https://discussions.apple.com/thread/253315438
With the mandatory mobile phone updates for a few years you're definitely going to see a lot more cases like that.
A thread about Tesla directly related to your question:
https://teslamotorsclub.com/tmc/threads/wholl-be-responsible...
Re: Rivian software update bricks infotainment system, fix not obvious
#308Earlier quoted context omitted.
Yah, I know from friends at ford and vw that there's still vxworks and qnx, but even there, good grief, a-b with confirmed boot is about as basic as you can get. I confess I've seen incredible sloppiness about when a confirmation is done (too early, including in the initial init stages which is way too soon) and watchdogs (spawn off a process that has a while loop stroking the wd - just absolutely pointless).
I've seen kicking and petting the watchdog, but this is my first time seeing stroking
Re: Rivian software update bricks infotainment system, fix not obvious
#309Re: Rivian software update bricks infotainment system, fix not obvious
#310I built a whole remote software update mechanism for a control binary that ran on 25k+ servers across multiple data centers. Rest assured that after the first time I messed it up (which required ssh into each box individually), I wrote a lot of unit and integration tests to make sure that it never failed to deploy again. One of the integration tests ensured that the app started up and could always go through the inte…
> This ran in CI and would fail the build if it didn't pass. I don't mean to be pedantic, but since we're talking about what should happen instead, this is insufficient. It works until the day you realize you made some kind of manual change to your CI infra, or that CI has some non-standard configuration that makes it work for you but not some significant fraction of the fleet. People should do what you described in…