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.
17.11.45 just downloaded and installed on my 2016 AP2 S. Adds Automatic Emergency Braking and enables it by default. There is now a menu item just below Collision Avoidance to disable it.
17.11.45 just downloaded and installed on my 2016 AP2 S. Adds Automatic Emergency Braking and enables it by default. There is now a menu item just below Collision Avoidance to disable it.
That's a very odd version number, considering most folks have been getting 17.14.35 lately.
If something hasn't happened to change the naming scheme, it was frozen a month ago, before the one we've been installing and never released to the public?
A 17.16.xx would make a lot more sense. But I guess you never know what Tesla is thinking.
It is a very odd version number and if it is correct those of us on 17.14.23 may never get that one because it would be a retro-grade firmware which I have never seen reported before on a car. :/
We don't know whether AP was improved. It likely was refined. Clearly no new features or increases in speed but that isn't necessary dispositive of AP improvement.
Good point. A large number of cars (65%?) are still on a 17.11.x version so those wouldn't be "going back" to a lower version. People with a 17.14.x version might end up getting a different version than 17.11.45 which includes AEB.
Good point. A large number of cars (65%?) are still on a 17.11.x version so those wouldn't be "going back" to a lower version. People with a 17.14.x version might end up getting a different version than 17.11.45 which includes AEB.
The reason the 17.11 version is odd is that it's pretty clear that their SW versions are year, week, build. So this software was built in week 11 (March 12th). It appears they may have actually been verifying this without any changes for 5 weeks.
The reason the 17.11 version is odd is that it's pretty clear that their SW versions are year, week, build. So this software was built in week 11 (March 12th). It appears they may have actually been verifying this without any changes for 5 weeks.
They may be iterating on branches now. There may very well be 2 or 3 branches of AEB firmware in parallel, each operating in shadow mode, and the 17.11.x branch was the first to be deemed ready, and they simply push an incremental build to turn it on.