SFOTurtle
Active Member
I wish! I'm getting 191-193 rated miles on a full (100%) charge and I'm on 4.5 which should report higher numbers.
That is the lowest I've seen on TMC for a full 100% SOC for a 60.
You can install our site as a web app on your iOS device by utilizing the Add to Home Screen feature in Safari. Please see this thread for more details on this.
Note: This feature may not be available in some browsers.
I wish! I'm getting 191-193 rated miles on a full (100%) charge and I'm on 4.5 which should report higher numbers.
It was still charging but after I waited for 20 minutes it was still at 250 miles.
I wonder if 5.6 computes the range based off the fleet average kW/m, rather than the old rated value. I know my average watts/mile is higher than rated; I can reach the rated value if I try, but normally I drive faster than that
That means it was trying to balance the pack. If possible, you should just let it continue until it completes. It might take over an hour.
I'm troubled by this word choice.balancing the pack or not, it won't pick up the 15 miles from 250 to 265 mile (100%) range that was lost with the v5.6 update from v4.5.
(or even the 10 miles lost with the 90% charge when it was updated. (230 down to 220))
I'm troubled by this word choice.
I don't think we know if the word "lost" (implying degradation) really applies yet.troubled that I used it or what it says about the new "formula"
That is the lowest I've seen on TMC for a full 100% SOC for a 60.
I don't think we know if the word "lost" (implying degradation) really applies yet.
They put that in every single update.If you read the firmware 5.8 release notes Tesla explained that they have changed the way they calculate the remaining miles in your battery to be more accurate. You have not ACTUALLY lost anything.
If the miles were there and now they are not and can not be found then they are lost. You can play semantics with the terminology if you need to but after each update we "lose" miles.
[QUOTE
They put that in every single update.
Miles are never there, only energy. If you have lost energy, you have lost "miles". If you haven't lost energy, it's ambiguous (possible misleading) to say that miles have been lost.
I would prefer it if the rated miles more accurately reflected 307whr/ml. I never achieve rated miles when averaging 307 and it is frustrating when trying to calculate range.
Thanks, hans. Your wording is more helpful than mine, I think.Miles are never there, only energy. If you have lost energy, you have lost "miles". If you haven't lost energy, it's ambiguous (possible misleading) to say that miles have been lost.
You got that impression from my post? Wow. I think I need to relearn English.the dismissive attitude that some members here have to other people concerns has gotten old.
I think I loosely recall 286 being the "proposed, amended, accounting for buffer" number in that TLDR post a bit back. So yah, ~290.You have to average ~290 to achieve rated range.
I disagree, given the fact that the only measurement that Tesla give us is range, once that goes down then something has been lost. Until they give us other units of measure, or actually tell us how they are coming up with the range number then these questions will continue. For me I don't care one way or another, and don't believe that any range has been truly lost, but the dismissive attitude that some members here have to other people concerns has gotten old.
Agreed. REST already provides it, so it's just the in-car UI that's lacking this. They provide charging rate in energy (as an option), so it seems silly to only show state of charge in miles.Tesla should display the State of Charge (SOC) numerically rather than just as a green bar that leaves everyone guessing.
Thanks, hans. Your wording is more helpful than mine, I think.
- - - Updated - - -
You got that impression from my post? Wow. I think I need to relearn English.
- - - Updated - - -
I think I loosely recall 286 being the "proposed, amended, accounting for buffer" number in that TLDR post a bit back. So yah, ~290.