kmcdonal
Well-Known Member
- Joined
- Dec 6, 2019
- Threads
- 11
- Messages
- 276
- Reaction score
- 324
- Location
- CO
- Vehicles
- Nissan 350Z, Subaru WRX
- Thread starter
- #1
Has anyone figured out what all the nav system takes into account when computing the end of trip state of charge? I specifically am interested in whether it takes elevation gain and weather en-route into account.
If I enter a destination in the mountains into the nav system and look at the estimated charge left at the end of the trip, it seems to assume a much higher consumption rate than when I am coming back down. I am talking about roughly 4,000 feet of elevation gain on the way up and 4,000 on the way down. That said, the nav system seems to over-estimate how much battery I will have left after going up the mountain. In other words, while it has increased its estimated consumption, it doesn't seem to have increased it enough for the elevation gain. The opposite goes for going down the mountain. Just to be clear, this is the estimate that comes up right when you enter the destination and before you have started driving.
My hypothesis is that the nav system is taking elevation gain into account, but the algorithm does not fully take into account how much more energy is required to go up. Often when I am going up the mountain I need to get around slow moving trucks and that requires brisk acceleration and more consumption than what is included in the nav's calculation. This is just my hypothesis and I have nothing other months of trial and error to back it up. I looked in the Good to Know app and a few other places and haven't seen anything specific about how the nav system computes end of trip SOC.
This is probably wishful thinking, but if the nav system was looking at temperature en-route, that could play a factor too. When you gain 4,000 feet, the temperature drops a lot. That said, that would be a lot more smarts than I am expecting out of Porsche's first gen electric car, but maybe I am wrong.
Anyone have any thoughts on what the navigation system uses to determine consumption for a trip?
If I enter a destination in the mountains into the nav system and look at the estimated charge left at the end of the trip, it seems to assume a much higher consumption rate than when I am coming back down. I am talking about roughly 4,000 feet of elevation gain on the way up and 4,000 on the way down. That said, the nav system seems to over-estimate how much battery I will have left after going up the mountain. In other words, while it has increased its estimated consumption, it doesn't seem to have increased it enough for the elevation gain. The opposite goes for going down the mountain. Just to be clear, this is the estimate that comes up right when you enter the destination and before you have started driving.
My hypothesis is that the nav system is taking elevation gain into account, but the algorithm does not fully take into account how much more energy is required to go up. Often when I am going up the mountain I need to get around slow moving trucks and that requires brisk acceleration and more consumption than what is included in the nav's calculation. This is just my hypothesis and I have nothing other months of trial and error to back it up. I looked in the Good to Know app and a few other places and haven't seen anything specific about how the nav system computes end of trip SOC.
This is probably wishful thinking, but if the nav system was looking at temperature en-route, that could play a factor too. When you gain 4,000 feet, the temperature drops a lot. That said, that would be a lot more smarts than I am expecting out of Porsche's first gen electric car, but maybe I am wrong.
Anyone have any thoughts on what the navigation system uses to determine consumption for a trip?
Sponsored