Off Road NAV use - force to use Adventure Roads?

[mm01rivian]

Starting to plan some summer adventures in SW CO. I have all sorts of apps for this (TrailsOffRoad, OnX etc) but would prefer to route using onboard NAV. Is there a way to FORCE the nav to use the FS Roads, Dirt Roads etc? Eg, Can you plot running the Alpine Loop in your nav to see range estimates etc? Obviously rock crawling isn't exactly an easy estimate but at least SEE what might be possible?

Sponsored

 

[zefram47]

In large part, you can't do that. As mentioned TrailsOffroad, Gaia GPS, OnX, etc are what you want for actual trail planning. As for range, expect around 1 mi/kWh on the trails in the mountains and be glad if/when you get better. Climbing up some of the passes you'll see far lower, 0.6 mi/kWh rings a bell when I did some of the loop, but you'll obviously do better on the way back down. There are plenty of chargers around in Ouray, Lake City (slow and only two), and Telluride.

 

[COdogman]

Unfortunately there is no way to do this yet. Rumor is they may add some type of off road mapping integration in the future, but we don't have any details.

 

[mm01rivian]

In large part, you can't do that. As mentioned TrailsOffroad, Gaia GPS, OnX, etc are what you want for actual trail planning. As for range, expect around 1 mi/kWh on the trails in the mountains and be glad if/when you get better. Climbing up some of the passes you'll see far lower, 0.6 mi/kWh rings a bell when I did some of the loop, but you'll obviously do better on the way back down. There are plenty of chargers around in Ouray, Lake City (slow and only two), and Telluride.

Appreciate the Data Points. My Sedona run was mostly downhill (Schnebly) so didnt help my estimates. Some TR on here with the Alpine Loop so I am confident that can be done S/F Ouray and the Lake City Charger is ideally half way for a lunch top off if needed. Telluride also good.
FYI - Ouray Charger is offline right now (I have a message thread in with CO State EV dept to see what's up - still waiting for them to get more details).

The big "not sure" right now is a run over Stony Pass after dropping off some people at Montrose Airport. I plan to DCFC in Montrose as much as possible (need to hit the road to allow enough daylight). Montrose south to Silverton and then over Stony Pass. Creed seems to be the next DCFC with Del Norte down the road a bit more. Looks like about 121mi, 10.6k gain, 7.5k loss for Creed.

Wish List Items for future UX Updates for the group that actually uses a Rivian as an adventure vehicle.

Co-Brand OnX or equivalent app integration. Make use of that big screen - put OnX on the left and then all the data on the right (angles, alti, etc). VASTLY improve the 360 and other cameras views and include "guidance lines" so we can see edges of trails , where all 4 tires and corners of the vehicle are etc. Include distance estimate to objects in the overlay (Polestar does this pretty well ) Move the off-road camera views to the smaller screen so the driver can glance down to see the bumper and side cams. Speed etc can be small, offset and not intrusive. Work with said co branding to feature detailed elevation profiles AND efficiency data to give off-road range estimates based on shared data sets. If they can get it to estimate trailer weight and range hit they can do the same for off road trails...

 

[VSG]

Do your planning in your preferred app then send the waypoints to your Rivian where you can then use the onboard navigation to travel between waypoints. You might have to throw in a few extra waypoints to force the route to go down those sketchy back roads, but as long as the Rivian maps know about the roads this seems to work for me. The Rivian navigation does recalculate range based on your current usage and drive mode, and it converges on a good number eventually, so it is useful for keeping an eye on range at destination.

If you use ABRP, you can change the assumed efficiency and let it do the range calculations. You can then raise and lower the efficiency to bracket what you expect so that you can determine if you have enough headroom.

Don't forget that the in-vehicle navigation needs cell reception. I always download google maps on my phone for my planned route and carry paper trail maps.

 

[mm01rivian]

Do your planning in your preferred app then send the waypoints to your Rivian where you can then use the onboard navigation to travel between waypoints. You might have to throw in a few extra waypoints to force the route to go down those sketchy back roads, but as long as the Rivian maps know about the roads this seems to work for me. The Rivian navigation does recalculate range based on your current usage and drive mode, and it converges on a good number eventually, so it is useful for keeping an eye on range at destination.

If you use ABRP, you can change the assumed efficiency and let it do the range calculations. You can then raise and lower the efficiency to bracket what you expect so that you can determine if you have enough headroom.

Don't forget that the in-vehicle navigation needs cell reception. I always download google maps on my phone for my planned route and carry paper trail maps.

ABRP doesnt like dirt roads it seems. I've added over a dozen waypoints in planing and it won't calculate it. Someday.

Typically I download offline maps to at least 2 different maps. GAIA and Google is standard but InReach has been VERY handy in the past - I've had phone GPS crap the bed in remote areas before. (using an old school Inreach 1 with screen saved my bacon once WAY back outside Jackson hole driving quads one year) A paper road atlas is always onboard and makes for fun games with the kids "This is how you use PAPER maps!"

Sponsored