Picard
Well-Known Member
- Thread starter
- #1
Does anyone have insights into what Rivian is using to power their MCU and Driver+ modules and what embedded OS they built their UI on? As I read about the "laggy" behavior of the maps, I am starting to wonder if this is all SW (still being ironed out) or whether there is an underlying HW constraint here that SW will need to optimize for.
Its clear that the Rivian (and pretty much every other manufacturer) sees the value in up-selling enhanced capabilities and apps to generate a lucrative revenue stream post purchase of the vehicle. To realize this goal, putting the right compute guts into the vehicle on day 1 is key. I really hope Rivian has nailed this.
Its clear that the Rivian (and pretty much every other manufacturer) sees the value in up-selling enhanced capabilities and apps to generate a lucrative revenue stream post purchase of the vehicle. To realize this goal, putting the right compute guts into the vehicle on day 1 is key. I really hope Rivian has nailed this.
Sponsored