I recently completed a cross country trip in our AGT--6,500 miles from Boston out to Yellowstone National Park and back over 3 weeks. Overall, the car performed very well. If you're curious to learn more about our trip, see our blog at https://lexlucid.net
We did have an interesting navigation failure. We had previously seen that sometimes the navigation system couldn't find some named destinations, so had learned not to necessarily trust when the navigation couldn't figure something out. We were trying to get from Jackson WY to Denver CO via a charger at Craig CO. Google said that Jackson to Craig was 327 miles, a distance we felt comfortable with on a single charge. The car navigation insisted that it was over 400 miles from Jackson to Craig via a different route. No amount of entering small town waypoints in between convinced the car to suggest the same route that Google wanted us to take. We didn't trust trying to go over 400 miles between chargers in mountainous terrain, so decided to ignore the car and follow Google's route. And then we found out why the car would not accept Google's route. When we crossed the state border from Wyoming to Colorado, the numbered state highway became a gravel road. At this point we were too far in to turn around and go back. We were forced to take our luxury sedan with 4 inches of ground clearance over 22 miles of gravel road before the route became paved again. The car survived the ordeal, and we made it to the Electrify America charger in Craig OK, and the charger even worked. But why did Google think it was OK to suggest this route? We had taken to using Google to double check every route suggested by the in-dash nav and A Better Route Planner because both were overly optimistic about our energy usage and would have us arrive places with only a couple of % of charge left.
I miss the days of paper maps. Hopefully the nav system works better in 2.0.
We did have an interesting navigation failure. We had previously seen that sometimes the navigation system couldn't find some named destinations, so had learned not to necessarily trust when the navigation couldn't figure something out. We were trying to get from Jackson WY to Denver CO via a charger at Craig CO. Google said that Jackson to Craig was 327 miles, a distance we felt comfortable with on a single charge. The car navigation insisted that it was over 400 miles from Jackson to Craig via a different route. No amount of entering small town waypoints in between convinced the car to suggest the same route that Google wanted us to take. We didn't trust trying to go over 400 miles between chargers in mountainous terrain, so decided to ignore the car and follow Google's route. And then we found out why the car would not accept Google's route. When we crossed the state border from Wyoming to Colorado, the numbered state highway became a gravel road. At this point we were too far in to turn around and go back. We were forced to take our luxury sedan with 4 inches of ground clearance over 22 miles of gravel road before the route became paved again. The car survived the ordeal, and we made it to the Electrify America charger in Craig OK, and the charger even worked. But why did Google think it was OK to suggest this route? We had taken to using Google to double check every route suggested by the in-dash nav and A Better Route Planner because both were overly optimistic about our energy usage and would have us arrive places with only a couple of % of charge left.
I miss the days of paper maps. Hopefully the nav system works better in 2.0.