I'm going to report some data myself, and then explain why, and what I think it might mean.
On Friday I took a trip from Syracuse to Rochester and back. (The trip back is shorter because I stopped at the Syracuse supercharger and only tracked the mileage to that point.) Below is the data for the two "trips", including four different start and end points.
Model: P85D
Delivery Date: December 24, 2014
Current Firmware version: 6.2.2.4.236
Firmware version at time of delivery (if known): Irrelevant
Odometer Mileage | Actual Mileage | Difference | % | Source (Actual Mileage) |
|
|
|
|
|
94.6 | 93.75 | 0.85 | 0.907 | Mapquest |
82.7 | 81.99 | 0.71 | 0.866 | Mapquest |
So...what do I think the above means?
Well, it would appear that my odometer actually is still overstating the actual mileage, and by very close to the exact amount--.8% or so--that people seemed to think the odometers were off by before. In that case, how do I explain my earlier theory that the problem had been corrected?
The 50-60 mile trips I had been recording --WERE-- being recorded by the Model S as being shorter than they had been, by a few tenths of a mile. I'm now thinking that with my snow tires on, my odometer (and presumably all D odometers, or at least the early ones) was overstating mileage by substantially more than that .8%. I had never attempted to quantify how much my odometer was overstating the mileage by. It was others who came up with the .8% figure. I couldn't quantify my overstatement because of the length of my driveway, my wife driving around the parking lot at the other end of the trip, etc. I just knew that even with those distances added in, the mileage had to still be overstated. After my car came back from the service center with the all-seasons on, and with the software update, the overstatement amount came down by very close to that .8% figure. I'm now thinking that I very well may have reached the wrong conclusion that Tesla had corrected the problem, when in actuality, the problem is just worse with snow tires on.
Sorry for the false alarm, if that's what my thoughts that the problem was resolved turn out to have been.