News
Volkswagen, a rocky $50B EV bet, and the bid to chase Tesla’s software prowess
Among the old guard of the automotive industry, very few could hold a candle to Volkswagen, which has initiated a $50 billion bet on electric vehicles. The plan, it seemed, was aimed at ensuring that the veteran automaker could catch up to Tesla, a dedicated EV maker that has made a name for itself by releasing vehicles that receive over-the-air updates on a regular basis.
Yet as the first result of Volkswagen’s dedicated EV efforts, the ID.3, rolled off the assembly line, it became clear that releasing software-driven electric cars was not as simple as building the next iteration of the Golf. When the ID.3 was released, the vehicle was incomplete. It could drive, turn corners, and basically do anything that regular cars are expected to do. Software-wise, however, it was nowhere near done. Features that were promised were absent, and promised capabilities such as over-the-air updates were unavailable.
Even the ID.3’s heads-up display, a feature that is not present in rivals like the Model 3, didn’t function. Early users of the vehicle also reported hundreds of software bugs. By June last year, Volkswagen decided to delay the ID.3’s launch and sell the first batch of the cars without full software. The vehicles are expected to receive an update that would provide the ID.3 with its full feature set, but the initiative will require a service visit around February 2021.
As noted in a report from The Wall Street Journal, Volkswagen’s issues with the ID.3 were the result of the veteran automaker not being proficient in software. For years, industry analysts and leaders alike have suggested and peddled the “Tesla Killer” narrative, suggesting that once the big players of the auto industry get serious about electric vehicles, Elon Musk’s EV startup would be completely overrun. As it turned out, building electric cars was not as simple. Just because a company can produce good gas and diesel-powered cars does not mean that they can produce good EVs.
Karsten Michels, a senior engineer for Continental AG, one of the firms which Volkswagen tapped to develop the ID.3’s software, noted that the gravity of the task surrounding the development of custom vehicle software was underestimated. “Maybe we underestimated how much work is involved and how little we could actually rely on existing legacy software,” Michels said.
Peter Rawlinson, CEO of Lucid Motors, expressed his thoughts on the situation. “(Ever since Tesla launched its first car in 2008) there was this feeling that the really serious players are going to come. Now, the Germans have finally come, and they’re not as good as Tesla,” he remarked.
Volkswagen, for its part, seems to be taking the lessons it learned during the ID.3 rollout and is applying it for the release of the ID.4, a crossover SUV that could rival the Tesla Model Y. Herbert Diess, the Chairman of the Board of Management of Volkswagen Group and an executive who has struck a friendship of sorts with Tesla CEO Elon Musk, initiated efforts to overhaul the company’s software strategies. If successful, the ID.4, which will be produced in Europe, China, and the United States, would deliver on the promises set forth by the ID.3.
Ultimately, Volkswagen has learned a notable yet painful lesson during the ramp of the ID.3, the most notable of which is that software is something that legacy automakers still need to work on. Granted, software has been running in gas-powered cars for years, with average vehicles including dozens of parts with chips that are designed to perform specific tasks. EVs, however, require a different type of software, one that is more akin to those used by smartphones today. With electric cars, in-vehicle software becomes the heart of the vehicle, with updates becoming the equivalent of service visits in a gas-powered car. In-vehicle software today is never complete as well, as they must always be open to improvements.
Danny Shapiro, senior director of automotive at Nvidia, related his thoughts on the complexity of in-vehicle software. “The key here is taking this distributed system in the car, dozens if not hundreds of applications, and centralizing everything. This is very complex, especially with a car where the safety level is critical. You can’t just flip a switch and be a software company,” he noted.
Don’t hesitate to contact us for news tips. Just send a message to tips@teslarati.com to give us a heads up
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.
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.
Tesla launched the all-electric, steering wheel-less, and pedal-less Cybercab last night at a quiet and small event in downtown Austin, Texas.
The launch, which marked the beginning of unsupervised ride-hailing for Tesla’s Robotaxi platform with Cybercab, has already caught the attention of the National Highway Traffic Safety Administration (NHTSA) who has more questions.
NHTSA opened an Audit Query (AQ) into the Cybercab’s Federal Motor Vehicle Safety Standards (FMVSS) certification that Tesla gave the vehicle. Manufacturers self-certify vehicles much of the time to avoid excessive regulatory delays.
Tesla Cybercab interior, note the lack of steering wheel and pedals. (Credit: @niccruzpatane/X< /a>)
However, the agency needs more information; it said in a summary:
“On September 3, 2026, Tesla began commercial deployment with a small number of its Cybercab vehicles in Austin, Texas. Tesla notified the Agency that it certified those Cybercab vehicles as compliant with all applicable Federal Motor Vehicle Safety Standards (FMVSS). Tesla also notified the Agency that it plans to gradually expand commercial deployment of the Cybercab to include additional vehicles and locations.”
It also went on to state that the Cybercab lacks traditional automotive controls, which is a groundbreaking move. The process is entirely new to the NHTSA, which gives the agency some leverage to put Tesla’s launch under a microscope:
“The vehicles lack permanently attached, conventional manual controls, such as a brake pedal, gas pedal, steering wheel, and mirrors. NHTSA is opening this AQ to examine the process and technical data on which Tesla relied when certifying the Cybercab and related issues. Among other things, NHTSA will consider the extent to which Tesla’s certification depended on determinations that certain FMVSS are inapplicable to the Cybercab.”
Tesla has added 45 Cybercab units to its fleet of Robotaxi-enabled cars in Austin, according to public documents the company submitted to the State of Texas over the past week. Enabling this level of self-driving is something Tesla has worked toward for many years, and now that it is finally here, it seems more than reasonable that regulatory agencies will have some questions.
Many outlets might try to frame this as a negative, but it is truly an agency looking to gain more information about groundbreaking tech that Tesla has been developing for years.
In an effort to keep riders, pedestrians, and property safe, any and all data accumulated from these first days, weeks, and months of rides will likely be shared with the NHTSA to enable broader rollout strategies across the United States and more in the future.
Tesla Robotaxi will be a 24/7 service: here’s when
Tesla Full Self-Driving will now overtake manual driving to avoid disaster
