Tesla Full Self-Driving (FSD) Beta applicants who own older car models are still patiently waiting for access to the FSD Beta program. Some applicants have shared their frustrations at camera upgrade issues which prevent them from becoming an FSD Beta user.
Camera Upgrade Issues
Tesla owners with older car models have reported their frustrations regarding camera upgrade requirements. Most of the owners are waiting to enter Tesla’s FSD Beta program.
The common issue is that owners receive camera upgrade notifications even after Tesla Service installed new cameras. It has caused great confusion among a number of Tesla community members waiting to become FSD Beta testers.
In correspondence with Teslarati, FSD Beta applicant Houman H. noted that his 2017 Model S with FSD had yet to receive access to Tesla’s Beta program. The Model S owner had upgraded his vehicle to Hardware 3. He also proactively contacted Tesla Service to get the necessary camera upgrade for his car.
Even after the upgrades, Houman H. did not receive FSD Beta access. Instead, he received another notice of his ineligibility for the program, stating that his Model S still needed camera upgrades. Confused, Houman H. contacted Tesla Service, thinking there must have been a mistake in their records as he had already upgraded his cameras.



Who is affected by the Camera Upgrade Issues?
A few Tesla owners who own older models talked to Teslarati about their challenges while patiently waiting for access to the FSD Beta program. Most—if not all—of the owners Teslarati spoke to have a Safety Score between 80 to 90 and purchased FSD at least a year ago.
Most owners with camera upgrade issues own vehicles from 2017 or older. A few other owners have posted about camera upgrade issues online.
“I have been patiently waiting since November 2021 for the FSD beta for my 2017 MS P100D when my cameras were upgraded and the MCU2 was installed. The vehicle was delivered with MCU1 and AP2.0. Safety score has always been 95 or above,” shared Powderkeg in the Tesla Motor Club (TMC) Forum.
“Recently the Tesla app version 4.14.2 allows the user to view if their vehicle is eligible for the FSD Beta. Much to my chagrin my vehicle shows that it is not eligible due to the cameras needing to be replaced. I know they were replaced at the time of the MCU2 upgrade because they are listed under the parts section,” the TMC member elaborated.
Tesla’s Response to the Camera Upgrade Issue
The TMC member and Houman H. worked with their local Tesla Service Center to solve their issues. They received different reasons for their camera upgrade issues.
In Houman H’s case, one of his upgraded cameras needed to be replaced. Tesla reportedly mentioned that some upgraded cameras in select cars needed to be replaced due to an unspecified issue.
“So apparently they didn’t have to replace all of them, they said that there was a problem with one of their replacement cameras that wasn’t working for many people, I think it was the front right side camera so for many of them they had to be replaced Even if they had already been upgraded. Therefore, doesn’t sound like it’s a true situation where all of them have to be replaced, but there are select cameras on select cars that have to be upgraded again due to some type of problem,” Houman H. told Teslarati.
Powderkeg also received information from his local Tesla Service Center. In his case, Tesla stated that all cameras need to be upgraded to run the final production FSD software.

Another Teslarati reader, Frank H., noted that he couldn’t upgrade his cameras, even after several requests to his Tesla Service Center. Frank H. paid for FSD, but has not been able to participate in Tesla’s beta program because of old cameras.
“I paid for FSD years ago but have been unable to participate in the beta program due to old cameras. Now FSD is in wide release and Tesla still has not upgraded my cameras after several requests. I am told: ‘We are currently experiencing a parts shortage on all parts necessary to perform FSD camera upgrade,’” Frank H. shared with Teslarati.
Are you having trouble getting into the FSD Beta program, too? I’d like to hear from you. Contact me at maria@teslarati.com or via Twitter @Writer_01001101.
News
Tesla crosses major Unsupervised Self-Driving milestone
Tesla has reached a notable benchmark in its autonomous driving program after its Robotaxi fleet surpassed one million miles of unsupervised operation. The company made the announcement during its Cybercab event in Austin on September 3.
Tesla Vice President of AI Ashok Elluswamy told attendees he was happy to report the fleet had achieved one million miles of unsupervised Robotaxi operation as a testament to safety.
The new total marked a sharp increase from the 380,000 unsupervised miles Tesla disclosed during its second-quarter 2026 earnings update in late July.
In roughly six weeks, the company added about 620,000 miles. That acceleration followed Tesla’s decision to remove in-vehicle safety monitors from most of its operations outside the San Francisco Bay Area.

Credit: Tesla
Tesla first launched Robotaxi service in Austin in June 2025 with safety drivers present. It later began fully unsupervised rides and expanded into Dallas, Houston, Miami, Orlando, and Tampa. The San Francisco Bay Area remains the exception, where a safety monitor still rides in the vehicle under California permitting rules.
The company has not released a city-by-city breakdown of the one million unsupervised miles.
The milestone arrived as Tesla began offering public Cybercab rides in Austin. The purpose-built vehicle has no steering wheel or pedals and is designed only for autonomous ride-hailing. Production versions joined the existing fleet of modified Tesla vehicles already operating in the service.
Tesla’s unsupervised mileage is growing at a double-digit weekly rate according to earlier company comments, yet its fleet size remains modest compared with established competitors. Waymo has accumulated more than 200 million fully autonomous rider-only miles. Tesla has described its own unsupervised operations as having recorded zero notable incidents in the period leading up to the July update.
The one-million-mile figure reflects Tesla’s shift from supervised testing to broader driverless service in multiple states. It also highlights the company’s strategy of using both existing Model Y vehicles and the new Cybercab to scale its network.

Credit: Tesla
Whether the rapid recent growth continues will depend on further city expansions, regulatory approvals, and the performance of the purpose-built Cybercab in everyday paid rides. Tesla has not specified how many of the latest miles involved the new vehicle versus the rest of the fleet.
The announcement underscores Tesla’s progress toward a larger robotaxi network while illustrating the remaining gap in total autonomous experience relative to longer-operating rivals.
News
Tesla Robotaxi will be a 24/7 service: here’s when
Tesla AI lead Ashok Elluswamy said this week that 24-hour Robotaxi service is close. Replying on X to a rider who wanted Cybercab trips all night, he wrote that the capability would arrive “next month or so” once “the next tech to merge on the v15 plan” is ready.
The comment landed on September 4, one day after Tesla opened public Cybercab rides in Austin. It is the clearest near-term timeline yet for overnight unsupervised operation. Tesla’s paid Robotaxi network currently runs from 6 a.m. to 10 p.m. seven days a week across Austin, Dallas, Houston, Miami, Orlando, and Tampa.
next month or so. the next tech to merge on the v15 plan will enable it.
— Ashok Elluswamy (@aelluswamy) September 4, 2026
That 16-hour window is shorter than the 6 a.m. to 2 a.m. schedule the company used for much of the prior year.
Elluswamy did not name the specific feature or say whether the change would apply first to purpose-built Cybercabs, the existing Model Y fleet, or both. He also offered no city-by-city rollout list. The link to Full Self-Driving v15 is nevertheless significant.
Tesla has described v15 as a step-change architecture with seven parallel improvement tracks and roughly ten times more parameters than earlier builds. Early versions of that software already operate on the Robotaxi fleet and contain about 40 percent of the planned gains.
By July 2026, the unsupervised fleet had logged more than 380,000 miles across six cities in two states with what the company called an impeccable safety record and no notable incidents caused by the vehicles themselves. Tesla has repeatedly argued that camera-based end-to-end neural networks, rather than extra sensors, are the core of the solution.
Overnight service would test that claim in lower-light conditions and would also raise vehicle utilization, a key variable for Robotaxi unit economics. The company has already begun using public Superchargers at night and is building dedicated Robotaxi charging sites.
Riders have asked why software must change if the cars already drive in the dark. The practical answer appears to be reliability and scale: Tesla has held back mass expansion until more of the v15 stack is merged, citing the need for higher confidence before putting thousands of unoccupied vehicles on streets around the clock.
If the next module arrives on the timetable Elluswamy sketched, 24-hour service could begin in October 2026 in at least some markets.
That would mark a shift from a daytime-bounded pilot to a service that can run whenever demand exists, including the late-night hours that have so far remained out of reach.
News
Tesla Full Self-Driving will now overtake manual driving to avoid disaster
Tesla is beginning to roll out Full Self-Driving Supervised v14.3.9 with a new active safety layer that can take control even when the driver is operating the car manually.
Tesla AI said the software can activate FSD on the driver’s behalf when an imminent collision is detected and Automatic Emergency Braking may not be enough. It may also engage if the system detects heavy distraction or an accidental FSD disengagement.
FSD Supervised v14.3.9 starting to roll out shortly
This release includes a new active safety feature set: FSD Supervised can now activate on your behalf when an imminent collision is detected and Automatic Emergency Braking (AEB) may not be enough.
It may also engage if we…
— Tesla AI (@Tesla_AI) September 4, 2026
The capability is essentially Automatic Collision Evasion. However, unlike conventional AEB, which mainly applies the brakes in a straight line, this feature can use steering, braking, and acceleration together if the car calculates that stopping alone will not prevent impact and a safer path exists. The system may change lanes or move toward a shoulder when conditions allow, then continue driving after the immediate threat is handled rather than simply coming to a stop.
The intervention is meant as a last-resort safety net, not a replacement for attentive driving.
Tesla Full Self-Driving v14.3.7 early review: FSD saved me from an accident
Tesla’s own description still frames FSD as supervised assistance. Secondary reports on internal release notes say the feature can fire while the car is being driven manually if cabin-camera monitoring suggests the driver is not sufficiently attentive, such as reaching toward the back seat, or if FSD appears to have been turned off unintentionally.
After the emergency maneuver, the car is expected to alert the driver and request a return to manual control.
The safety case is straightforward. Many collisions happen in the last second because a driver is looking away, fumbles a control, or faces an obstacle that braking cannot fully solve. A system that can both recognize that AEB is insufficient and execute a coordinated evasive path can reduce those remaining high-severity events.
Re-engaging after accidental disengagement also addresses a practical failure mode: a small steering nudge that drops FSD at the worst moment. The advantage is a background safety net that uses the same vision stack already running in v14, instead of leaving the car solely to emergency braking once the driver is no longer in command.
The feature still depends on FSD being enabled and, according to reports, an active FSD purchase or subscription. It does not make the vehicle unsupervised. Drivers remain responsible, and Tesla has not published how often the system is expected to intervene or how it will handle false positives.
If the rollout is conservative and the false-alarm rate stays low, the update is a meaningful step: FSD is no longer only a feature the driver turns on. In the rare moments when disaster is already forming, it can step in.