Welcome to Tesla Motors Club
Discuss Tesla's Model S, Model 3, Model X, Model Y, Cybertruck, Roadster and More.
Register

Update reduced the standard charge on my P 85 from 242 to 212 miles

This site may earn commission on affiliate links.
Software that is rolled out to cars is considered GA, I wouldn't call it "early adopter" vs. not. It's just that you were chosen for your upgrade sooner rather than later.

Has there been an update yet that hasn't been partially rolled out, stopped, patched, and then updated before there was a larger roll out? Certainly was the case with the last 3.

- - - Updated - - -

REST logs:
With 4.4, my maximum charge was 249 rated (achieved exactly once since I started logging).
With 4.5, my maximum charge has been 234 rated.

Do you perhaps have the battery_level value for each of those?
 
Do you perhaps have the battery_level value for each of those?

249 - Closest I could find for non-streaming was 246. What a weird data point from lapping day at the track. Observe the est_battery_range and the battery_level.
charging_state=Complete
charge_to_max_range=false
battery_range=246.89
est_battery_range=50.12
ideal_battery_range=282.64
battery_level=96
car_version=1.31.11


234
charging_state=Complete
charge_limit_soc=90
charge_limit_soc_std=90
charge_limit_soc_min=50
charge_limit_soc_max=100
charge_to_max_range=false
battery_range=234.1
est_battery_range=238.77
ideal_battery_range=269.43
battery_level=91
car_version=1.33.44
 
Last edited:
On the recommendation of a person at Tesla service 800 # I did a max "Trip" charge on the car last night. I have a Nema 14-50 outlet and a single charger. I set it to start charging at 4 AM this morning and around 9AM it had maxed out to 260 miles. The only other time I did a max "Range" charge was a few months ago at Fremont service dept (they accidentally charged it to max range instead of standard) and at that time it showed a range of 267 miles. This morning the person at Tesla told me the engineer says it is the 4.5 update and did not know if and when this problem would be corrected. So, in my car the previous Standard charge gave me 240-242 miles and now post 4.5 update the max Daily charge gives me 212.
 
On the recommendation of a person at Tesla service 800 # I did a max "Trip" charge on the car last night. I have a Nema 14-50 outlet and a single charger. I set it to start charging at 4 AM this morning and around 9AM it had maxed out to 260 miles. The only other time I did a max "Range" charge was a few months ago at Fremont service dept (they accidentally charged it to max range instead of standard) and at that time it showed a range of 267 miles. This morning the person at Tesla told me the engineer says it is the 4.5 update and did not know if and when this problem would be corrected. So, in my car the previous Standard charge gave me 240-242 miles and now post 4.5 update the max Daily charge gives me 212.

That's good news then. Nothing wrong with the battery, just something they need to fix in the next update.
 
Some more follow-up to...
How did you get 96% on a standard charge though? Drove downhill a lot?
This is very curious. Observe the orange and red parts below. I think I may ask Tesla to pull the logs and see if they can diagnose. A simple 14-50 receptacle should have fairly stable and simple behavior at 1am at a racetrack with no humans likely nearby, shouldn't it? It's as if the "wake_up" request wakes up more than just the streaming API.

20130519_011453.log said:
...
Code:
	https://portal.vn.teslamotors.com/vehicles/.../command/charge_state
charging_state=Charging
charge_to_max_range=false
max_range_charge_counter=0
fast_charger_present=false
battery_range=232.79
est_battery_range=49.01
ideal_battery_range=267.92
battery_level=91
battery_current=20.2
charge_starting_range=null
charge_starting_soc=null
charger_voltage=221
charger_pilot_current=40
charger_actual_current=39
charger_power=9
time_to_full_charge=0.18
charge_rate=26.5
charge_port_door_open=true
scheduled_charging_start_time=null
scheduled_charging_pending=false
user_charge_enable_request=null
charge_enable_request=true
...
Code:
	https://portal.vn.teslamotors.com/vehicles/.../command/vehicle_state
...
car_version=1.31.11
...
Code:
	https://portal.vn.teslamotors.com/vehicles/.../command/wake_up
{"reason":"","result":true}
Code:
	https://streaming.vn.teslamotors.com/stream/.../?values=speed,odometer,soc,elevation,est_heading,est_lat,est_lng,power,shift_state,range
1368951269324,,6175.5,91,147,131,47.485853,-122.754186,-8,,233
1368951369324,,6175.5,91,147,131,47.485853,-122.754186,-8,,234
1368951432074,,6175.5,92,147,131,47.485853,-122.754186,-8,,234
1368951537324,,6175.5,92,147,131,47.485853,-122.754186,-8,,235
Code:
	https://portal.vn.teslamotors.com/vehicles/.../command/wake_up
{"reason":"","result":true}
Code:
	https://streaming.vn.teslamotors.com/stream/.../?values=speed,odometer,soc,elevation,est_heading,est_lat,est_lng,power,shift_state,range
1368951571196,,6175.5,92,147,131,47.485853,-122.754186,-8,,235
1368951649194,,6175.5,92,147,131,47.485853,-122.754186,-8,,236
1368951761194,,6175.5,92,147,131,47.485853,-122.754186,-8,,237
1368951835194,,6175.5,93,147,131,47.485853,-122.754186,-8,,237
Code:
	https://portal.vn.teslamotors.com/vehicles/.../command/wake_up
{"reason":"","result":true}
Code:
	https://streaming.vn.teslamotors.com/stream/.../?values=speed,odometer,soc,elevation,est_heading,est_lat,est_lng,power,shift_state,range
1368951874407,,6175.5,93,147,131,47.485853,-122.754186,-8,,237
1368951929157,,6175.5,93,147,131,47.485853,-122.754186,-8,,238
1368951962406,,6175.5,93,147,131,47.485853,-122.754186,-2,,238
1368951962656,,6175.5,93,147,131,47.485853,-122.754186,-0,,238
Code:
	https://portal.vn.teslamotors.com/vehicles/.../command/wake_up
{"reason":"","result":true}
Code:
	https://streaming.vn.teslamotors.com/stream/.../?values=speed,odometer,soc,elevation,est_heading,est_lat,est_lng,power,shift_state,range
1368952084856,,6175.5,93,147,131,47.485853,-122.754186,0,,238
Code:
	https://portal.vn.teslamotors.com/vehicles/.../command/wake_up
{"reason":"","result":true}
Code:
	https://streaming.vn.teslamotors.com/stream/.../?values=speed,odometer,soc,elevation,est_heading,est_lat,est_lng,power,shift_state,range"
1368952210565,,6175.5,93,147,131,47.485853,-122.754186,0,,238
1368952224064,,6175.5,94,147,131,47.485853,-122.754186,0,,238
1368952225064,,6175.5,93,147,131,47.485853,-122.754186,0,,238
1368952226064,,6175.5,94,147,131,47.485853,-122.754186,0,,238
1368952241314,,6175.5,94,147,131,47.485853,-122.754186,0,,241
1368952310314,,6175.5,95,147,131,47.485853,-122.754186,0,,241
1368952311314,,6175.5,94,147,131,47.485853,-122.754186,0,,241
1368952312314,,6175.5,95,147,131,47.485853,-122.754186,0,,241
1368952329314,,6175.5,95,147,131,47.485853,-122.754186,0,,244

Code:
	https://portal.vn.teslamotors.com/vehicles/.../command/wake_up
{"reason":"","result":true}
Code:
	https://streaming.vn.teslamotors.com/stream/.../?values=speed,odometer,soc,elevation,est_heading,est_lat,est_lng,power,shift_state,range
1368952458603,,6175.5,95,147,131,47.485853,-122.754186,0,,244
1368952479350,,6175.5,96,147,131,47.485853,-122.754186,0,,244
1368952480350,,6175.5,95,147,131,47.485853,-122.754186,0,,244
1368952491350,,6175.5,96,147,131,47.485853,-122.754186,0,,244
1368952492350,,6175.5,95,147,131,47.485853,-122.754186,0,,244
1368952494350,,6175.5,96,147,131,47.485853,-122.754186,0,,244
1368952497350,,6175.5,95,147,131,47.485853,-122.754186,0,,244
1368952498350,,6175.5,96,147,131,47.485853,-122.754186,0,,244
1368952499351,,6175.5,95,147,131,47.485853,-122.754186,0,,244
1368952505350,,6175.5,96,147,131,47.485853,-122.754186,0,,244
Code:
	https://portal.vn.teslamotors.com/vehicles/.../command/wake_up
{"reason":"","result":true}
Code:
	https://streaming.vn.teslamotors.com/stream/.../?values=speed,odometer,soc,elevation,est_heading,est_lat,est_lng,power,shift_state,range
1368952631601,,6175.5,96,147,131,47.485853,-122.754186,0,,244
1368952649601,,6175.5,96,147,131,47.485853,-122.754186,0,,248

1368952657601,,6175.5,96,147,131,47.485853,-122.754186,0,,247
...
 
Some more follow-up to...

This is very curious. Observe the orange and red parts below. I think I may ask Tesla to pull the logs and see if they can diagnose. A simple 14-50 receptacle should have fairly stable and simple behavior at 1am at a racetrack with no humans likely nearby, shouldn't it? It's as if the "wake_up" request wakes up more than just the streaming API.

I just tried it, but wake_up doesn't do that with me. (On 4.4)
 
I have seen range drop 2 miles immediately upon completion of a standard range charge so the drop from 248 to 247 at 96% SOC is not strange. However the jump in estimated range from 244 to 248 in 18 seconds is weird. I think that range estimation at near full and near empty is all strange for some perfectly reasonable physical explanation that I don't yet understand.
 
I'm seeing something similar after update.

* Before update, standard charge got me 240 miles (93%)
* Currently seeing 54% = 127 Rated miles via REST API
* Extrapolating this out... 90% = 212 miles, or 100% = 235 miles

Not sure if this is valid.

Has it been proven that there is a linear relationship between rated miles and charge% ?

I think you may have to change the slider until you get 93% via the REST API, and then only look at rated miles.
 
I'll do a full standard charge tonight and see how it goes. FWIW, in 4.4 the %'s extrapolated out correctly.

I also have v4.5 and I noticed the percentages on the slider did not seem to be very linear with the range you get after charging to different levels. But visually looking at the slider isn't very precise so I finally figured out how to run the REST API. I just ran the powershell script and it returned battery_range 181.0 and battery_level 74. A simple-minded extrapolation gives me 244.6 miles for a 100% charge. However, I went on a road trip this Saturday and did a full 100% charge and got 265 miles of range. From this, I'm concluding that the battery level reading in v4.5 is not linearly related to actual range. I heard the original build of 4.5 displayed numerical values for the percentage on the slider. Perhaps this is why they removed the numerical values in the later builds of 4.5 . . .
 
I posted the following on another thread. Reposting here since it seems relevant.

Just to provide everyone with another data point: I've been seeing some varying range estimates with different levels of charging--148 miles at 60%, 169-174 miles at 70%, and 237 miles at 92% (this was on version 4.4). So I was curious to see how much I would get on range charge. I did my first range charge this morning and got 262 rated miles. Interestingly, this number exceeds the number one would get simply from extrapolating from the rated miles at the lower charges.
 
I'll do a full standard charge tonight and see how it goes. FWIW, in 4.4 the %'s extrapolated out correctly.

So, things look ok. Here are some various #'s from last night's charge:


battery_range: 180.33,
est_battery_range: 187.37,
ideal_battery_range: 204.15,
battery_level: 72,


battery_range: 200.33,
est_battery_range: 207.66,
ideal_battery_range: 226.79,
battery_level: 79,
time_to_full_charge: 1.68,

battery_range: 234.33,
est_battery_range: 242.72,
ideal_battery_range: 265.28,
battery_level: 90,
time_to_full_charge: null,

5 hours later, still shows 90% charge, but vampires took 5 miles:

battery_range: 229,
est_battery_range: 238.25,
ideal_battery_range: 259.25,
battery_level: 90,
time_to_full_charge: 0,
 
Last edited: