Autopilot 2.0: ‘smooth as silk (17.22.46)’ control algorithm and Autopark updates put to test

Jun 17, 2017 | by Iqtidar Ali

Last month Elon Musk stated that He was excited about the upcoming Autopilot 2.0 update that will feel ‘smooth as silk’ in longitudinal control.

The previous autopilot firmware update (17.17.4) lacked some features like the Auto Perpendicular & Parallel Park, Auto Display Brightness, Auto High Beams & Automatic Emergency Braking.

The latest firmware update to Autopilot 2.0 v8.1 is the 17.22.46 which includes the features mentioned and enhancements to existing features as Summon and Side Collision Warnings (Read full release notes detailing every new and enhanced feature and how to use them here).

Bjørn Nyland tested the AP 2.0 (17.17.4) just a week before the new ‘silky smooth’ version started to roll-out over-the-air.

Let’s go over Bjørn’s Autopilot 2.0 demonstration & commentary video first for a comparison to the test performed by James Hansbert (video also below) on the latest firmware update i.e. 17.22.46.

In addition to testing longitudinal control James also tests other new features except for the Automatic Emergency Braking (of-course) & Auto High Beam.

Tesla owners also comment that the few times the vehicle was not able to detect a blank parking spot happened due to higher than recommended max speed of 15 mph (24 km/h). Certainly there are enhancements in the overall drive experience but still Autopilot 2.0 has room for improvement to be truly ‘smooth as silk’.

According to Elon Musk this update will be widely available via over-the-air update to Tesla owners this weekend.

Let us know your thoughts in the comment section below or stay tuned for updates by liking our Facebook Page.


Iqtidar Ali
[email protected]

Iqtidar Ali is a long time web developer and now writing for his childhood passion 'cars' further boosted by the advent of electric vehicles especially Tesla.

Warning: count(): Parameter must be an array or an object that implements Countable in /home/iqtidarali/public_html/wp-includes/class-wp-comment-query.php on line 405
No Comments

Post A Comment