Just to add another voice into the void: Cross shopping between a R2 and one of the Scouts seems weird to me: its really deciding between a compact(ish) SUV (R2) and a large one or full size truck (Scout).
If they ever come to market I suspect we may end up with a Scout - as *sometimes* the R1...
ensured this was not the case - the tailgate is working as expected (stated this in my post above but should have been more clear - the tailgate button operates as expected, ie a phone in close range allows opening even on a locked truck; the tonneau cover button is operating even when the...
About to try a hard reset - but the powered tonneau cover on our gen2 is not ālockingā following the 26.30.15 update. As a result anyone can open it by pushing the button on the outside of the truck. All other doors/openings etc seem to be working normally (ie the tailgate doesnāt open - unless...
Not fast and loose at all - mfrs can either use a 0.7 multiplier to go from the dyno results to āreal worldā or use a series of factors to produce a potentially more accurate result. Rivian do the latter for all the measurements they have done to date - which actually shows a minuscule...
using the following: https://dis.epa.gov/otaqpub/display_file.jsp?docid=65095&flag=1 and fitting it to the numbers published at energyefficiency.org:
Vehicle
EPA doc raw CD range
EPA doc raw highway CD range
Raw 55/45 blend
Published EPA range
Inferred EPA factor
Effective city range...
Re ADAS compute:
Gen1 had no nvidia.
Gen2 peak TOPs is around 508 (2x Nvidia Orin AGX at 256 each).
Rivian's marketing has muddied the waters here a bit - mostly referring to the capability of a single orin, contrasting that to a pair of RAP1s.
Re infotainment:
Rivian has never used an...
Itās pretty truthful⦠ā¦if you know how to cut through their marketing.
OP looks to be seeing around EPA rated range for their config - 20ā ATās on a quad gen1 large pack.
Rivian get funny by blending drive modes for their āheadlineā figures - eg the 371 mile āratingā for a gen2 tri with 22ā...
I would separate the model from the harness here.
Rivian absolutely should and does own the harness: vehicle state, command execution, safety boundaries, permissions, context, memory/chat retention, and the handoff between local and cloud paths. That is where Rivian-specific differentiation is...
That actually makes the governance question more concrete.
If Mind is already part of Rivianās production environment, then this is not just a theoretical future concern. The relevant questions are whether Rivian is paying Mind, whether those terms are armās length, whether they were approved...
No - and I dont think there should be any expectation - as you are the one driving the R1.
Full context - I asked for similar in my R1T - as at one point of the 6k miles on it (at the time). ~3K had been done by Rivian whist in for warranty work. I didn't expect to get a positive outcome, but...
There is another angle here that is worth separating from the broader automation debate.
The issue is not whether industrial robotics is useful. It clearly could be. The governance question is whether Rivian shareholders are fully protected if Mind Robotics becomes deeply tied to Rivianās...
I mostly park our R1ās outside here in STL - as other have said itās the cold starts that really take the toll on range. As a result for very short trips (ie ~5 miles or so) can see a massive impact, but by the time we are actually going somewhere Iād put it at around 15-25% impact during Jan/Feb.