Update: Rivian adding Gauge View feature to Dual Motor Rivians (per VP of Software)

[MrMusAddict]

Per Wassym Bensaid, VP of Software Development at Rivian:

Source:

Sponsored

 

[Electric Rivilution]

Awesome news! Nice to see the company fast to react and respond.

 

[Marchin_MTB]

I wonder if it was (A) a choice made by accident (without all of leadership being consulted), (B) a deliberate choice that they all bought in on but now walked back, or (C) a simple bug.

Either way I had a feeling things would end this way. Differentiating one very specific config by not including a compass and some temperatures seems just silly. My money is that it was A or C or a combo of the two.

 

[Donald Stanfield]

I wonder if it was (A) a choice made by accident (without all of leadership being consulted), (B) a deliberate choice that they all bought in on but now walked back, or (C) a simple bug.

Either way I had a feeling things would end this way. Differentiating one very specific config by not including a compass and some temperatures seems just silly. My money is that it was A or C or a combo of the two.

My money is on B. Differentiating between the models makes good financial sense for Rivian the biggest problem they have with the duals is they are so close in performance to the quad that for the price delta there is very little reason to buy a quad right now.

They need to give consumers a reason to buy the halo truck and the dual is still good enough to entice buyers as is. Better performance than any other EV truck right now. Still holds its own at its price point for the S too. Rivian needs to make the models more different.

They can and should do things like premium software for quads. They just need to do better about communicating that with customers. If they came right out and said so on the development notes people would have no right to complain.

 

[MrMusAddict]

I wonder if it was (A) a choice made by accident (without all of leadership being consulted), (B) a deliberate choice that they all bought in on but now walked back, or (C) a simple bug.

Either way I had a feeling things would end this way. Differentiating one very specific config by not including a compass and some temperatures seems just silly. My money is that it was A or C or a combo of the two.

My main skepticism about it being an accident or a bug is that the omission was exclusive to the base Dual Motor config. Performance had it, All Terrain packages had it.

That implies that their code has logic that would enable/disable the feature depending on the configuration. For example:

Enable Gauges if any are true:
  Has "Quad Motor"
  Has "Performance"
  Has "All Terrain Package"

If the "bug" was that they simply omitted Has "Dual Motor", then that in itself seems alarming to me. Because that implies that they built the ability to differentiate the configuration. If it were truly for everyone from the beginning, why even build out some code that defines those differentiations?

 

[Mobius1]

Isn’t Tesla selling a std version of Model S with software restricted range on the same hardware? Rivian will eventually package some cool features and sell for a premium, unless you opt to buy a higher model. Seems like they wanted to see the community reaction with something small, which is easily reversible based on backlash.

 

[djsider2]

That's exactly what DM is doing vs the DM Performance. If it was software related to "Performance" and not something like "Adventure" trim, then it makes sense. This feature did not make sense to put behind that differentiator.

DM buyers know they wont get improvements if its Performance targetted. Maybe software tuners will find 0.1s improvement for dual motors and give that out to DM Perf only. I believe that is perfectly acceptable and falls in line with what people expect.

 

[Hillbilly]

Ot, but I love the bed view in this update. Really helps with seeing into the trucks blind spots too.

 

[djsider2]

If the "bug" was that they simply omitted Has "Dual Motor", then that in itself seems alarming to me. Because that implies that they built the ability to differentiate the configuration. If it were truly for everyone from the beginning, why even build out some code that defines those differentiations?

They already have to do this because it's either its own value in the options list, or its the base case without extra checks. There's no way the differentiation ability isn't already in the software, whether it's Has "Dual Motor" or the default ELSE implementation if none of the other conditions were satisfied.

 

[EBEG]

Isn’t Tesla selling a std version of Model S with software restricted range on the same hardware? Rivian will eventually package some cool features and sell for a premium, unless you opt to buy a higher model. Seems like they wanted to see the community reaction with something small, which is easily reversible based on backlash.

This is true for a lot of products. I think there were some laser printers that were identical except for how fast the software let it print. The faster printing version was a couple hundred bucks more for the same hardware.

I seem to remember the Tesla thing came out when they did a software push allowing lower range models to go further during the evacuation for a hurricane in Florida.

 

[Mobius1]

This is true for a lot of products. I think there were some laser printers that were identical except for how fast the software let it print. The faster printing version was a couple hundred bucks more for the same hardware.

I seem to remember the Tesla thing came out when they did a software push allowing lower range models to go further during the evacuation for a hurricane in Florida.

That’s when I heard about it as well. I guess once the backlash simmers down, you figure out how you can cash in on it.

 

[Redline]

I really liked the interview I saw with Wassym. They've got some seriously exciting stuff coming.

 

[dleepnw]

I wonder if it was (A) a choice made by accident (without all of leadership being consulted), (B) a deliberate choice that they all bought in on but now walked back, or (C) a simple bug.

Either way I had a feeling things would end this way. Differentiating one very specific config by not including a compass and some temperatures seems just silly. My money is that it was A or C or a combo of the two.

if it was B, all the bitching and complaining worked.

 

[Dark-Fx]

My main skepticism about it being an accident or a bug is that the omission was exclusive to the base Dual Motor config. Performance had it, All Terrain packages had it.

That implies that their code has logic that would enable/disable the feature depending on the configuration. For example:

Enable Gauges if any are true:
  Has "Quad Motor"
  Has "Performance"
  Has "All Terrain Package"

If the "bug" was that they simply omitted Has "Dual Motor", then that in itself seems alarming to me. Because that implies that they built the ability to differentiate the configuration. If it were truly for everyone from the beginning, why even build out some code that defines those differentiations?

It's probably a decision tree like that for loading the correct widgets, since what you have and what mode you are in changes what widgets are displayed. Instead of failing to display the right thing it just wouldn't enable the screen. Entirely plausible to me that they just forgot to even check that it was displaying correctly for a base vehicle since they've had very little differentiation in vehicles before.

 

[ImAI]

why even build out some code that defines those differentiations?

you have to differentiate based on the components of the vehicle to make decision about which tiles you paint on the gauge view: for example to show tiles with 4 motors instead of 2.

but the snippet you wrote is not a code but a pseudo-code and it would not be implemented as a an if-then routine but rather as a bitwise operation on a binary value that represents what your vehicle has.

Sponsored