IMO the inaccurate estimated arrival state of charge is a much bigger issue than the long charging time at 100% issue. You can kind of deal with the extra time when charging. But if you're counting on arriving with 10% and you can't make it, potentially getting stranded, it is a big problem.
It's been hard to get attention on this issue, both at the service level and in the community.
Here is my theory:
I would also throw in that there's like NOT a ton of Max Packs either. 80/20, 70/30 tops Large&Standard/Max, unless that changed with Gen2 for 2025?!?Here is my theory:
1. Rivian is prioritizing charging speed over keeping the battery modules balanced.
2. The only way to truly get all the modules balanced when doing a DCFC is to charge it to 100%.
3. The longer your DCFC, the worse the imbalance. However, I think the worst imbalance probably happens when charging during the fastest speed: 10-60%. So if you do a 10-60% charge, you are very likely to have an inaccurate estimated SoC at destination, especially if it is below 20%.
4. Rivian is aware of this issue but fixing it may require slowing the charging speed. Which will cause all kinds of bad press and upset drivers. They compromised and are accepting the out of balance situation as a good trade off vs. charging speed.
5. It may be impossible to fix this without slowing the charging speed, but maybe Rivian is fine tuning the BMS to improve balance between modules when charging.
6. It is rarely reported as a issue because most people don't use DCFC in a way that causes the problem to show up. They don't DCF charge to 100%, and they arrive at the destination with 20% or more SoC.
7. The Rivian nav defaults to 20% as the destination SoC. Coincidence? I think not.
Hmmm. Good point.
on that trip from Everett to Spokane (298mi, via I-90, w/decent head winds) I L2'd to 100 at home before we left, and it said we'd get there with ~7% ended up topping up at the SC because it was a bet I was willing to take with 105 miles left to Spokane.Hmmm. Good point.
DCFC is required to make this issue appear, IMO.
L2 charging has never caused this for me. If you can travel all on L2, the SoH below 10% is accurate, in my experience.
I don't do a lot of DCFC. I can survive on just L2 for most of the time.
I thought I had seen someone who had theirs bouncing around significantly during a trip. Seemed like it was relying on too small of recent driving usage for the estimations on the nav. Doesn't feel like your issue.I wonder if the rather vague "range estimate fluctuations" software fix highlighted below is meant to resolve this issue?
Hope that if it does fix it for Gen2 and my Gen1 is magically fixed, then we'll know. lol
Agreed. I would understand if it were uphill in the snow both ways, but when conditions don't make sense for the arrival SOC prediction. There's a problem somewhere.
' ... how many of us Max Packers seeing this issue are still on OEM Pirelli's? Could the simple answer be we've likely all swapped out to a third party tire and kept it at the Default Tire Swap settings because the 3rd party tire is 'close enough'?
No, it isn't the tires. I am still on the OEM Pirelli tires.Had a thought yesterday...cut to my Lady quickly jabbing with 'Oh...did it hurt...
What we're actually witnessing is the slight difference between the OEM tire calibration compared to say the Defender MS/2 setup that's pretty dang close to the Scorps but not exact?!? Could that be enough to cause what we're seeing?
Could be a plausible explanation as to why it appears to be more obvious on road trips vs daily driving (more time on the road = longer durations of faster wheel spin, wheels not calibrated exactly to what the computer thinks they are = different/wonky arrival estimations)
Does that math?
Also, has anyone with a Gen1 got the update yet where they claim it fixes it for Gen2? I have not received the update yet, but I'm usually ~10days after @RivianTrackr posts the new update.
Well there goes that theory, worth a shot lol
