News
The Tesla MCU1 conundrum: How early FSD adopters were left behind in limbo
When Tesla started selling Full Self-Driving back in 2016, the company was in a far different place than where it is today. Back then, Tesla was not the most valuable carmaker by market cap, nor was it a tried and tested business that no longer needs credits to become profitable on a quarterly basis. Back then, believing in Tesla and its promises for innovative tech was not something that was done lightly.
Back then, it took a leap of faith.
And that was exactly what a number of Tesla Model S and Model X owners did. With Elon Musk and Tesla noting that every vehicle produced at the time had the necessary hardware to achieve autonomous driving, a good number of Model S and Model X owners decided to go all-in on the promise that achieving self-driving was just a matter of software. And if it turns out that it wasn’t, Tesla would ensure that early adopters would get the hardware necessary to make their vehicles on par with the company’s newer, more advanced cars.
This promise has not been granted by Tesla — at least not fully — and a good number of early FSD adopters, who were the first to put their faith in the company and its autonomous driving program, have now found themselves in a limbo of sorts. A limbo that now involves an aging vehicle, a fully paid Full Self-Driving suite, and what is starting to seem like a path to FSD that is blocked by the company’s old MCU1 unit, which happens to be linked to a recall of about 130,000 Model S and Model X earlier this year.
An FSD Limbo
The Tesla Model S and Model X were still fitted with MCU1 units when the company started selling FSD. By this time, Tesla’s reputation as a producer of the best electric vehicles in the market was already established. It was then no surprise that when the company debuted its first FSD demo in 2016, numerous Model S and Model X owners were all too willing to support Tesla.
“I bought my Model S in 2017 based on their advertising claiming that it had the necessary hardware for self-driving. Tesla advertised that I would get true L5 autonomy. (The ad) also stated ‘The person in the driver’s seat is only there for legal reasons. He is not doing anything. The car is driving itself,’” a longtime Tesla owner told Teslarati in a statement. The Model S owner added that he initially purchased Enhanced Autopilot for $5,000, but he later bought FSD for an additional $5,000 last year when Elon Musk noted that he was confident that complete autonomy was on hand.
Tesla is a company built on rapid innovation. Over the years, Tesla has gained a reputation as a carmaker that rolls out improvements as soon as they are available. Unlike traditional automakers that typically wait a year before introducing minor updates to their vehicles, Tesla improves its electric cars through over-the-air software updates. But Tesla had also implemented hardware changes in the past, such as when the company started the rollout of its MCU2 units in March 2018. The company also updated its Autopilot computer from Hardware 2.0 to Hardware 2.5, and later, to Hardware 3.0.
Elon Musk, for his part, has assured FSD buyers that their vehicles would have the necessary hardware when Tesla achieves full autonomy. And to some degree, Musk has stayed true to his word. Owners of older vehicles that purchased FSD were provided a free upgrade to Hardware 3.0. Tesla, however, has introduced its MCU1 to MCU2 retrofit as a paid upgrade. Quite unsurprisingly, some early FSD adopters opted out of the optional infotainment system update. This has proven to be problematic.
Apparent MCU1 Limitations
As Tesla started rolling out more advanced features, vehicles equipped with MCU1 units started getting left out of key functions like Sentry Mode and Tesla Theater. Enhanced driving visualizations were also available only on vehicles that were fitted with MCU2 units. It was over this period that early FSD adopters found themselves steadily getting left behind. New features would be introduced, but they would be focused on MCU2 cars. Software updates were frequently rolled out to the fleet, but not for MCU1 vehicles. This was highlighted by a Tesla Model S 75 owner who purchased FSD, and who shared a photo with Teslarati showing that his vehicle is still running 2020 firmware despite the car stating that its software was up to date.

The Model S 75 owner’s experience is not unique. Over the course of this article’s research, Teslarati has received similar stories from early FSD adopters. A longtime electric vehicle advocate who purchased a Model S 100D with Enhanced Autopilot and Full Self-Driving described his current ownership experience as similar to having a device that is no longer supported.
“In the recent past, I have not even had 2021 firmware update as if my car is already unsupported before all the features promised are delivered. I was hoping to get FSD Beta, but that feature has not been demonstrated for my configuration by anyone, so far and no communication from Tesla on exactly when we can expect our car to participate in this to provide feedback,” the Model S 100D owner wrote.
While Tesla may be quite silent on whether its older MCU1 units are indeed the culprit behind the less-than-stellar ownership experience of FSD’s early adopters, those who have owned multiple Teslas over the years have all but confirmed that the aging component seems to be a key issue. One Tesla owner who shared his story with Teslarati noted that his 2017 Model S — which has FSD and whose infotainment system was upgraded to MCU2 — received the “Request FSD Beta” button just fine, but his 2017 Model X — which is still equipped with an MCU1 unit — did not receive anything at all despite having FSD.
“Now the beta button is finally coming. All the early adopters that paid for FSD were eager to get it. Most people had their computers upgraded by now to the FSD version and were told that is all they needed; it would work fine on MCU1. So the excitement for everyone grew, especially those that had waited the longest. After several delays, the button came. My Model S got the button right away, but it never came for the Model X with MCU1. There was no communication from Tesla at all. No email sent out in advance. All of those people found out through the disappointment of not getting it. Then searching through chat groups, (I discovered) that no one with MCU1 got it. Why can’t Tesla show some respect for these customers and at least communicate in advance?” the veteran Tesla owner told Teslarati.
Transparency and Understanding

One prevalent theme among the early FSD adopters who contacted Teslarati with their stories was the lack of communication on Tesla’s part. This is something that has been reported by longtime Tesla owners for some time now. And while it is understandable that Tesla is juggling a lot of balls in the air as it expands its business to other countries and other segments, having a responsive communications team, or at least investing some of its funds into the creation of one, would definitely not hurt.
Tesla owners, particularly early FSD adopters, are more than willing to be understanding of the company’s plight and challenges, after all. In this sense, Tesla would probably be better off behaving more like a company that truly cares for its customers and less like a traditional automaker that is just looking for the next sale.
Unfortunately, this is something that became a reality for Tesla FSD adopters who purchased vehicles just before March 2018, when the company transitioned its vehicles to MCU2 units. As per a Tesla Model S 75D owner, his order initially had a March 2018 delivery date, but he was encouraged by the company to take an early delivery instead. As a result, he has missed out on numerous features, and he is yet to enjoy some key FSD capabilities that the company has been rolling out as of late.
“I have a December 2017 Model S 75D. I had placed an order for it in mid-December with a delivery date of March 2018. Tesla reached out to me just before the end of the year with a vehicle that someone canceled their order on. If I had known that March 2018 vehicles and not December 2017 vehicles would have MCU2, I would have never accepted the other car. I feel like they misled me on my order.
“I told myself I was okay with it because my original order stated it would be fully capable of FSD. Unfortunately, as years passed, MCU2 vehicles had plenty of extra features, and figured I would eventually get my FSD capabilities anyways. Unfortunately, I am now seeing Model 3, Model Y, and Model S vehicles with orders placed years after me getting capabilities I should have received. Now they are getting FSD Beta, and I am left wondering if I will ever get it with MCU1. I do not wish to spend money on the MCU2 upgrade as they said my vehicle was already capable,” the Model S 75D owner wrote.
What Elon Musk is Pledging Now
Elon Musk has been made aware of the issue surrounding FSD’s early adopters, and most recently, the CEO noted that early production vehicles would require some camera upgrades to get full access to the FSD Beta. Musk noted that the new cameras, just like HW3.0, were included in Full Self-Driving’s price so retrofits are all but assured. Yet even in the CEO’s recent statements, a reference to the complications that are seemingly caused by the company’s aging MCU1 units was absent.
Years ago, these Tesla owners put their faith in Elon Musk and his vision to achieve Full Self-Driving. And they were given a word. This promise has been met to some degree, but not fully. Details such as the absence of MCU2 units are severely hobbling the experience of Tesla owners that quite literally helped fund the development of Tesla’s growth into a mass market manufacturer and a key player in the autonomous driving sphere. And until the company decides to do something for its early FSD adopters, Tesla would continue to have some of its most loyal customers be subjected to a substandard ownership experience.
Early Model S and Model X owners are a small fraction of Tesla’s fleet at this point. The number of owners who purchased FSD and are still stuck with MCU1 units is even smaller. The costs to upgrade these owners’ cars would undoubtedly be substantial, but they would likely be marginal for Tesla in the long run, especially with the way the company has been growing year-over-year. Perhaps Tesla could provide complimentary MCU2 retrofits to early FSD buyers when they get their cameras upgraded for free. By doing so, Elon Musk could prove that he is a man of his own word.
Musk himself said it, after all. He may be late, but he pulls through. Now it’s time to stand by these words. With the rollout of the FSD Beta, Full Self-Driving is closer than ever. Tesla just has to pull through for a group of owners who took that leap of faith when the company announced its intentions to develop a self-driving system.
Don’t hesitate to contact us with news tips. Just send a message to tips@teslarati.com to give us a heads up.
News
Tesla briefly offered this Robotaxi part for your personal car
Tesla briefly offered one Robotaxi part in its Parts Catalog for your personal car, only to remove it just a short time after it was first noticed.
Tesla’s Robotaxi camera washer apparatus was briefly available for purchase on the company’s Online Parts Catalog. The camera washer was first noticed on Model Y Robotaxi vehicles about six months ago in Austin.
🚨 Tesla looks to have installed Camera Washers on the side repeater cameras on Robotaxis in Austin
pic.twitter.com/xemRtDtlRR— TESLARATI (@Teslarati) January 23, 2026
First noticed by Not a Tesla App, the Camera Washer entries appeared for the new “Juniper” Model Y under a category called “Halo,” which has also now disappeared. Interestingly, Halo probably is related to Tesla’s internal “Project Halo,” which was a project that aimed to retrofit customer-owned Model Ys into functional Robotaxis.
This hardware addition would likely be required for the vehicle to operate as a Robotaxi, as the Camera Washer seems to be a non-negotiable part of the vision-based system Tesla utilizes for self-driving efforts.
However, this part has since been removed and is no longer visible on the EPC.

Now the true question lingers: Why would Tesla add this Camera Washer to the Model Y parts catalog? Is it planning to make it available for owners to utilize on their own cars for personal use, or will it become a prerequisite for Robotaxi operation in customer-owned cars?
While discussing the upgrade options for Hardware 3 vehicles during the Q1 Earnings Call, Tesla CEO Elon Musk had said that the company could establish small, satellite shops that would upgrade cameras and self-driving computers. Perhaps this same strategy could be utilized for vehicles that want to be included in Robotaxi but do not have the correct hardware.
AI4 is currently represented as capable of unsupervised self-driving, and the same was said about HW3 at one point, only for Tesla to admit last quarter that it would, unfortunately, not be possible. Perhaps AI4 vehicles might need this camera washer as a prerequisite, just as HW3 cars will need that camera and computer upgrade.
This could be the first hint of that’s where we are headed.
News
Tesla Robotaxi gets sweeping but polarizing change
Tesla has started rolling out a broader change to the ride experience for its Robotaxi fleet by silencing turn signals, but the change is certainly polarizing.
Tesla has generally made it clear that its purpose-built ride-hailing platform, Robotaxi, will cater to the rider in nearly every way possible. This includes having climate preferences, music, and other personal settings loaded up in the car as the rider enters.
But Tesla is taking it a step further by muting turn signal chimes altogether, a change that appears to be a way to make the ride more peaceful:
Tesla has finally turned off the blinker/turn signal noises in their Model Y Robotaxis.
This is a small update, but will definitely be noticeable for riders. It didn’t really make much sense to leave the turn signal sound on when it’s Unsupervised. pic.twitter.com/ITwx60PAMO
— Sawyer Merritt (@SawyerMerritt) July 27, 2026
However, there are a handful of people who are not thrilled about this change. Turn signals are a conditioned part of the human mind for those who ride in a car regularly.
Taking a turn without one feels strange and odd, and not hearing it click while activated could set off some alarms for riders, who might use the noise as confirmation that other drivers know of their intention to turn.
I kind of like it being on, threw me off when riding with Zoox who has had it disabled
— Dan Burkland (@DBurkland) July 27, 2026
Turn signal noises are still audible in customer cars, so if you use FSD in your personal vehicle, you will still hear the turn signal.
The move is certainly one that is unique, but not one that separates it from other ride-sharing services. In a normal car, the clicking sound confirms to the driver that the blinker is active. In a fully driverless Robotaxi, that feedback serves no purpose for passengers, other than peace of mind.
News
Tesla Full Self-Driving v14.3.6 review: a rare regression, but some bright spots
Tesla released Full Self-Driving version 14.3.6 last week, and after what was potentially one of the best FSD releases in v14.3.5, there has been a bit of a regression. While there are some bright spots, the changes made to v14.3.6 seem to have backtracked some behaviors.
Overall, it is hard to really complain about FSD in any sense; it has revolutionized how I travel literally anywhere. According to my self-driving app, the last time I went a day without using it was 59 days ago.
However, I think it’s also important to recognize when things are just plain bad with FSD. There are times it does truly mind-boggling things, and I’ll dive into those here. Additionally, I only had these issues on local roads, not on highways. Highway operation, generally, is always incredible other than the occasional complaint about speed or left lane camping.
With those things being said, my personal experience may not represent others’ experiences. A handful of people have said they have had a similar experience on v14.3.6, while others have said it is more than normal.
Turning Hesitancy, Inaccuracy
I’ve noticed more inaccuracy turning into multi-lane stretches of road than in any version I can remember. I’ve had at least three instances of FSD turning into a stretch of roadway that has two or more lanes, and not selecting a lane confidently as it has in past versions.
I think Tesla FSD v14.3.6 is a regression from previous .3 branches
This version in particular has been incredibly hesitant, jerky, and indecisive at times. There’s actually been two drives that I have decided to not used FSD for the remainder of the trip. These were local trips… pic.twitter.com/YobHDOKRS6
— TESLARATI (@Teslarati) July 26, 2026
Instead, the car will drive over one of the dashed road lines, and the steering wheel will jerk back and forth before picking the lane. It should be said that it has always picked the correct lane when choosing based on the navigation, but it is still very indecisive. The steering wheel jerking is reminiscent of some of the later versions of v13.
I admit I really hate to see the steering wheel jerking come back. However, I think when Tesla releases v14.3.7, it won’t be present. When there are occurrences of it in FSD versions, it is usually resolved by the following release.
FSD Disregards Manual Turn Signals
This is my biggest bone to pick with FSD other than Navigation issues, but this one seems like it would be such an easy fix.
If Tesla is going to put the word “Supervised” on the end of “Full Self-Driving,” then when I tell the car to do something, it should do it. If I input an increase in speed by pressing the accelerator, the car will immediately respond. It does not disregard my input because it feels it is traveling at the right speed.
FSD should never disobey and turn off turn signals that the driver inputs. Trying to direct the car into the correct lane, I had initiated the left turn signal not once, not twice, but three times, with the car turning it off all three times and continuing in a lane that would end in just one block. The only solution at this point would be to zipper merge.
This goes back to the fact that self-driving’s biggest bottleneck might be rider preference. A zipper merge might have been more than reasonable, might have saved me time that I spent sitting through an additional light cycle, and might be something many drivers would do. I was in no hurry, I traditionally do not try to zipper merge because it feels inconsiderate, and lastly, the car should have just followed my input.
This caused me to disengage and drive manually the rest of the way home. Sometimes I just do not need FSD to try to pass every car it can at intersections.
Bird Braking is a Thing of the Past
The big complaint with recent versions of Full Self-Driving has been what we’ve coined as “bird braking,” which is when the car will brake suddenly as a bird flies past.
There have been zero issues with this so far in v14.3.6, which is an excellent improvement.
FSD Might Already Be Taking Note of Driver Preferences
Another thing I have noticed over the past few days is that v14.3.6 seems to already be taking my preferences with navigation into account.
This is something that is supposed to be rolling out with the Summer Update, but I have a hunch it’s already present and might have been included in this v14.3.6 build. On Friday, FSD pulled into an entrance to a local convenience store that it had never attempted to go into before.
Typically, I manually pull into this entrance because it avoids heavy cross traffic at the main entrance. FSD has always chosen that congested main entrance.
I don’t want to get anyone excited but my Tesla running FSD v14.3.6 just:
✅ Pulled into an entrance at my local Sheetz that I routinely pull into manually but FSD never has entered
✅ Pulled into my assigned parking space at home despite many other spots being vacant https://t.co/ZUShvknTWO pic.twitter.com/83O5a2S0eh
— TESLARATI (@Teslarati) July 24, 2026
Additionally, FSD has pulled into my assigned parking spot at my townhouse community on multiple occasions with this release. This is something that used to happen ocassionally, but not consistently.
It also navigated back to the same convenience store last night, drove through crazy cars scrambling to gas pumps, navigated out of the parking lot correctly, drove me home, and, once again, parked in my assigned spot.
As previously stated, this release just seems to have a few things that need to be brought to Tesla’s attention, and also to make others who use FSD aware of some things that I’ve experienced. I look forward to the next release that will remedy these issues, just as Tesla has always done in the past.

