Out of Spec's Rivian Route Planning Woes

[Redline]

Are we really still mad at Kyle for that?

Sponsored

 

[Deacon]

The Out of Spec team has been running an R1S DM Max press car in their recent Ft. Collins CO to Las Vegas road trip 'races', and experienced some strange route planning behavior where it almost forces the route to RAN chargers, even L2 chargers with hours of wasted time, instead of known EA and Tesla chargers along the route. We've never seen this before in our R1T DM Max, on our recent 4,500 mile road trip to Texas and back and along many of the same driving segments they had issues, or right now just plotting a trip to Ft. Collins...so WTF? Anyone else seen this?

I plan my route and chargers before I leave - don't totally rely on the NAV system to find where I will charge.

 

[Bar_Down]

I doubt many of us (or future Rivian drivers) will push things to the edge like the OOS guys do. Also, I wonder if they had filtered for only 150kW chargers when they had the weird, far out-of-the-way routing to the level 2 Rivian Waypoint charger.

I have only had one weird routing with the Rivian NAV where I wanted to go north into the UP and then west (through the charging desert) to Wisconsin. The Rivian NAV initially wanted me to go south to Traverse City RAN to charge and then North, stopping again at the Mackinaw City RAN when I was already closer to Mackinaw than Traverse City and had plenty of charge to go well beyond mackinaw. I knew that wasn't correct, so I started over, and it got it right on the second try. I have no explanation for the first, goofy routing.

I tend to use Waze & ABRP on my phone while also using the Rivian NAV. I trust the Waze most for routing, and find the Rivian NAC is conservative on its planning (displaying and being able to set Arrival SOC% would really help). I am still figuring out ABRP 5.0 with the data feed from the Rivian... it looks promising so far.

 

[Tlohrenz]

The Out of Spec team has been running an R1S DM Max press car in their recent Ft. Collins CO to Las Vegas road trip 'races', and experienced some strange route planning behavior where it almost forces the route to RAN chargers, even L2 chargers with hours of wasted time, instead of known EA and Tesla chargers along the route. We've never seen this before in our R1T DM Max, on our recent 4,500 mile road trip to Texas and back and along many of the same driving segments they had issues, or right now just plotting a trip to Ft. Collins...so WTF? Anyone else seen this?

I've only had my R1T for 5 weeks and on its for trip from Longmont to Lamar, CO, Rivian want me to stop at the RAN in Boulder vs EAs east of town on I-70. I even tried telling it to ignore Rivian chargers and it still wanted me to go to the RAN 10 miles west when I need to go east. Rivian definitely has charger bugs in their route planning.

 

[CarlM408]

Also, I wonder if they had filtered for only 150kW chargers when they had the weird, far out-of-the-way routing to the level 2 Rivian Waypoint charger.

FWIW there is no setting for charger speed in the route planning settings, only in the map's charger display settings. Rivian does make this just about as confusing as possible, with different settings in route planning (which is hard to find), map filtering, and on your mobile device. They gotta sync all that together.

 

[Mkreaden]

Keep in mind they are trying to get views for their videos. May be valid, may not be, but failure will probably get more views than success. Personally I think their videos are way too long to be useful, so I don’t consider anything they present.

No conspiracy theory here… Kyle is legit and this podcast is the best info for EV tech.

 

[CarlM408]

I've only had my R1T for 5 weeks and on its for trip from Longmont to Lamar, CO, Rivian want me to stop at the RAN in Boulder vs EAs east of town on I-70. I even tried telling it to ignore Rivian chargers and it still wanted me to go to the RAN 10 miles west when I need to go east. Rivian definitely has charger bugs in their route planning.

No to doubt you in any way, but can you please describe how you told it to ignore Rivian?
I.E., changing the nav map's charger display filter is not the same thing as changing the route planning charger preference settings:

 

[azbill]

What type of charger is that one you aim for? And what SOC do you arrive at?

I like to arrive at 15-20% at most. For me, along I-10, Indio (EA) is 220 miles and is reliable. Cabazon (EA) is 260 miles and not so reliable. I get 300 miles on the highway in conserve mode with my 21 tires. And I typically leave the charger at 60% if possible, keep the charging rate in the high zone.

On my return trips I will charge at Quartzsite, but just to 50%, that gets me home at about 10%.

 

[Tlohrenz]

I've only had my R1T for 5 weeks and on its for trip from Longmont to Lamar, CO, Rivian want me to stop at the RAN in Boulder vs EAs east of town on I-70. I even tried telling it to ignore Rivian chargers and it still wanted me to go to the RAN 10 miles west when I need to go east. Rivian definitely has charger bugs in their route planning.

 

[strykerwsu]

My network and adapter type selections seem to keep resetting. After a few selection updates I usually get it to match ABRP. Overall I just rely on ABRP and Plugshare.​

 

[CarlM408]

Ah yeah okay, so that there is how you adjust the filter of what chargers the Navigation shows you on the map.
That's not how one sets the route planning preferences.

Select a destination, do NOT press GO (do not collect $200), select Details, then Settings to adjust the route planning settings. If that's not quite clear please find 5 minutes to watch my video which shows this in detail:

 

[DuoRivian]

^^^^ BINGO ^^^^

cut-the-line kyle needs to pay the mortgage.

His trust fund pays for the rent!

 

[defcon888]

I think the thing about EV's and owning one is there is a little planning that goes into long trips. We aren't at the stage of infrastructure like ICE vehicles and probably won't be for another 10+ years.

Before we took our trip to Disneyland from NorCal (about 600 miles 1 way), I studied Plug-share and ABRP (more Plug-share) like a teenager studying for a exam. I read reviews of ll the station we would stop at and others that we might stop at if needed. I had them all written down.

When we arrived at a charger (RAN in Manteca), I would enter the next station in the navigation and then off we went to the next station and then repeated the process. We stopped at 1 EA and 1 EVGo (which was nice because it was at an In N Out Burger so we got a burger while we charged), when we were done eating, we were fully charged.

Moral of the story......don't rely 100% on ABRP and/or a navigation system......do some "pre" work and rely on that.

 

[Treebeard]

The Out of Spec team has been running an R1S DM Max press car in their recent Ft. Collins CO to Las Vegas road trip 'races', and experienced some strange route planning behavior where it almost forces the route to RAN chargers, even L2 chargers with hours of wasted time, instead of known EA and Tesla chargers along the route. We've never seen this before in our R1T DM Max, on our recent 4,500 mile road trip to Texas and back and along many of the same driving segments they had issues, or right now just plotting a trip to Ft. Collins...so WTF? Anyone else seen this?

Yes, I have had to end the trip, and then re- plan or do point to point. Sometimes it seems to remember a trip that is ended and reused it when re-planning.

 

[MXA121]

I have found that the in-truck navigation system does not accept any filters/presets. It chooses the route it thinks is best. I MUCH prefer planning my trips in the Rivian App. You can define way more parameters and I find it to be very accurate.

Recent road trip I experienced several weird things.
1. Chose first charger way to early even when I had full charge and could go way further.
2. Chose EVGo, which I refuse to use, so I update my 'filter' in the map area, still takes me there.
So, I have to manually pick which charger I want, and I navigate directly to that. Then while it's charging, I plan my next stop.
It should be better.

Sponsored