-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
[UK] 2020.32.x
- Thread starter NorfolkMustard
- Start date
OfficialMark_H
VLOGGER
Talk of this being faked (hence the font change) and features not known in EAP
MrBadger
Badger out
It's same to assume the very few cars (1 per country it seems) that have got this are either Tesla employees or other testers, as the same cars got 2020.28.10 which - as far as I know - never made it out to the wild.
TeslaFi.com Firmware Tracker
MrBadger
Badger out
I think v10 was 2019.32.11 which we got 29 Sep 2019 and installed the day TeslaFi had spotted it. We also took 2019.32.2.1 which was our first update after taking delivery and that was still v9. That had been in the wild for 12 days prior to then. I can remember v10 not coming as a fresh 4 weekly build and a huge anti-climax after what some had promised. We were only on v9 for a day or so.
It would make sense if v11 was the AP rewrite, so based upon last years time frame, they still have the best part of a couple of months which I think is in line with EMs comments on rewrite timeframes. I did get the impression that v10 had slipped though - possibly waiting on smart summon that failed to materialise at the same time and subsequently rumoured to have had problems - and some will say still does!. Hope v11 is not a similar anti climatic rollout.
I'll comment that v10 soon quickly turned into 10.1 then 10.2 but remains stuck since them. Not sure how those updates worked in previous versions and what triggered a minor version update.
It would make sense if v11 was the AP rewrite, so based upon last years time frame, they still have the best part of a couple of months which I think is in line with EMs comments on rewrite timeframes. I did get the impression that v10 had slipped though - possibly waiting on smart summon that failed to materialise at the same time and subsequently rumoured to have had problems - and some will say still does!. Hope v11 is not a similar anti climatic rollout.
I'll comment that v10 soon quickly turned into 10.1 then 10.2 but remains stuck since them. Not sure how those updates worked in previous versions and what triggered a minor version update.
Last edited:
Got it too. A model X on Twitter has Powerwall coordination in this update too
https://twitter.com/4rsfed/status/1291961158841192448?s=21
https://twitter.com/4rsfed/status/1291961158841192448?s=21
Also, not in the notes but I think it’s new.
Service > Clear Autopilot camera calibration
Service > Clear Autopilot camera calibration
More likely for a Type2 charge to be left unattended, and once the car end unlocks the charger end can be disconnected, cable stolen.
this CCS unlock also makes it possible for another car to use the charger if the driver of the first isn’t around
this CCS unlock also makes it possible for another car to use the charger if the driver of the first isn’t around
I read the patch notes as the charger cable unlocking automatically when the car is unlocked, rather than once the charge has ended. It says “once charging has stopped”, not “finished”. It could’ve been worded a bit less ambiguously.
Previously you needed to manually unlock the charger port as a separate action to unlocking the car (or instead of), and it seems that will continue to be the case for Type-2, for some reason.
Perhaps Tesla envision people going in and out of their cars when they’re at home, without wanting to stop charging by the cable auto-unlocking, but that this isn’t typically the case for rapid charging (because who is doing that at home?).
Similar threads
