Since the release of the latest FSD release, beta 9.2, a Twitter user, Ostyn, has asked Elon for an update around the famous button. You know, ‘The Button'. The one that will give us mere mortals a peek into a world where cars drive themselves, freeing us humans to... well, probably just to spend more time on our phones.
The button was initially expected back in April of this year, however Tesla decided to move FSD to a vision-only model, which resulted in a delay, but also greatly increased its capabilities.
After Ostyn asked Elon about the button, Elon responsed that the button may become available in beta 10 or 10.1. Tesla is currently on beta 9.2 of FSD. If we expect a new beta release every two to three weeks, then the question becomes, how many releases before we get to version 10 or 10.1?
Luckily, Elon later clarified that we can expect version 9.3 next, followed possibly by 9.4. then the holy grail, version 10.
Beta 10 or maybe 10.1. Going to pure vision set us back initially. Vision plus (coarse) radar had us trapped in a local maximum, like a level cap.
Pure vision requires fairly advanced real-world AI, but that's how our whole road system is designed to work: NN's with vision.
Elon mentions that there would be significant architecture changes in version 10.0, so I think it's fair to expect that version to take longer than the two/three week time period.
So if we add these time intervals up, the soonest we can expect the FSD Beta to be publicly available would be, in at the very least, six weeks, which brings us to October. That's of course assuming that everything runs smoothly, that Tesla releases an update every two weeks and that the update with the button comes in version 10. There are a whole lot of ‘ifs' in there, and as you can imagine, this is an unlikely scenario.
If we take a more realistic approach, the next betas may each come in about three weeks. Let's say the button is in version 10.1, instead of version 10, and version 10.1 comes three weeks after the 10.0 update. Then the big question is, how long will Beta 10 take if we know it'll contain significant architectural changes? We may be looking at 4-8 weeks.
So at the higher end, we're looking at having the button available to the masses in about 17 weeks, or about 4 months.
That puts us almost exactly at the end of the year, which seems like a natural goal for Tesla to strive for given previous releases.
It's surely something for us to look forward to, but as we know things change, especially when developing world-leading AI.
Tesla’s been on a roll with Supercharger improvements lately, from the 325kW charging update for the Cybertruck, to 500kW with V4 Superchargers coming next year. While those improvements have been limited to the Cybertruck, Tesla didn’t put all their focus on their new flagship vehicle, but looked at their more affordable vehicles as well.
LFP Battery Heating
Tesla’s Superchargers can now heat LFP Batteries - those that are in the Model 3 and Model Y Rear Wheel Drive variants. This applies to Long Range and Standard Range models, which saw a limited run. This is another update included as part of the 2024 Tesla Holiday Update - which really arrived with a lot of unannounced new features and capabilities.
The change is pretty interesting - Superchargers of the V3 and V4 variety can now pre-heat batteries for Model 3 and Model Y vehicles equipped with LFP battery packs. That means those vehicles are able to get back on the road faster when it's extremely cold. Of course, Tesla still advises you to precondition before you arrive, saving drivers time and money.
Max de Zegher, Tesla’s Director of Charging, also commented on the new feature. Essentially, Tesla is inducing an AC (alternating) ripple current through the battery to warm it up. Keep in mind that Superchargers are DC charging. That means it is possible to get a cold-soaked LFP vehicle on the road 4x faster than before, assuming that it didn’t precondition at all and that it is in the worst-case scenario (below 0ºF).
In essence, Tesla is using some engineering magic to turn the circuits inside the LFP battery into an electric heater - and powering that heater through the Supercharger. An AC ripple current is a small oscillation in the DC charging current that generates heat through electrical resistance, warming up the battery. Those ripples are a byproduct of converting AC to DC and back - so Tesla is using the onboard charger to induce those ripples to warm up the battery. Definitely an innovative technique that’s really only possible with the versatility of the NACS connector.
We’re hoping Tesla can implement this across their full lineup of vehicles, but we’ll have to wait and see how it is trialed across LFP vehicles first and if it is even possible on vehicles with 2170 or 4680 battery packs.
Tesla launched two FSD updates simultaneously on Saturday night, and what’s most interesting is that they arrived on the same software version. We’ll dig into that a little later, but for now, there’s good news for everyone. For Hardware 3 owners, FSD V12.6.1 is launching to all vehicles, including the Model 3 and Model Y. For AI4 owners, FSD V13.2.4 is launching, starting with the Cybertruck.
FSD V13.2.4
A new V13 build is now rolling out to the Cybertruck and is expected to arrive for the rest of the AI4 fleet soon. However, this build seems to be focused on bug fixes. There are no changes to the release notes for the Cybertruck with this release, and it’s unlikely to feature any changes when it arrives on other vehicles.
FSD V12.6.1 builds upon V12.6, which is the latest FSD version for HW3 vehicles. While FSD V12.6 was only released for the redesigned Model S and Model X with HW3, FSD V12.6.1 is adding support for the Model 3 and Model Y.
While this is only a bug-fix release for users coming from FSD V12.6, it includes massive improvements for anyone coming from an older FSD version. Two of the biggest changes are the new end-to-end highway stack that now utilizes FSD V12 for highway driving and a redesigned controller that allows FSD to drive “V13” smooth.
It also adds speed profiles, earlier lane changes, and more. You can read our in-depth look at all the changes in FSD V12.6.
Same Update, Multiple FSD Builds
What’s interesting about this software version is that it “includes" two FSD updates, V12.6.1 for HW3 and V13.2.4 for HW4 vehicles. While this is interesting, it’s less special when you understand what’s happening under the hood.
The vehicle’s firmware and Autopilot firmware are actually completely separate. While a vehicle downloading a firmware update may look like a singular process, it’s actually performing several functions during this period. First, it downloads the vehicle’s firmware. Upon unpacking the update, it’s instructed which Autopilot/FSD firmware should be downloaded.
While the FSD firmware is separate, the vehicle can’t download any FSD update. The FSD version is hard-coded in the vehicle’s firmware that was just downloaded. This helps Tesla keep the infotainment and Autopilot firmware tightly coupled, leading to fewer issues.
What we’re seeing here is that HW3 vehicles are being told to download one FSD version, while HW4 vehicles are being told to download a different version.
While this is the first time Tesla has had two FSD versions tied to the same vehicle software version, the process hasn’t actually changed, and what we’re seeing won’t lead to faster FSD updates or the ability to download FSD separately. What we’re seeing is the direct result of the divergence of HW3 and HW4.
While HW3/4 remained basically on the same FSD version until recently, it is now necessary to deploy different versions for the two platforms. We expect this to be the norm going forward, where HW3 will be on a much different version of FSD than HW4. While each update may not include two different FSD versions going forward, we may see it occasionally, depending on which features Autopilot is dependent on.
Thanks to Greentheonly for helping us understand what happened with this release and for the insight into Tesla’s processes.