Connect with us

News

Tesla’s proven anti-pandemic safety plan has fallen on deaf ears amid an anti-Elon Musk narrative

Tesla's Fremont Paint Facility applying a coat to the Model S. (Credit: YouTube | Rivista Automobilismo)

Published

on

One of the most remarkable things that one can witness is the birth and spread of a narrative. Narratives are powerful, as they are capable of affecting and perhaps even changing the perception of people on a particular person or topic. Such a narrative is forming in the Tesla-sphere today: one that completely ignores a company’s proven efforts to battle the coronavirus, and one that brands the electric car maker’s CEO as a de facto villain that cares not for his employees. 

Amidst the ongoing issues surrounding the reopening of the Fremont factory, Tesla publicly shared a Return to Work Playbook that it will be using to protect and prevent its workers from contracting the coronavirus. The strategies outlined in the playbook are modeled after the company’s efforts in Gigafactory Shanghai, which successfully battled the virus when it was ravaging China. Tesla’s Shanghai plant was barely affected by the pandemic, and it is back in full operations today. 

Alameda County officials have not given Tesla the green light to resume operations in the Fremont plant, a factor that has resulted in heated online discussions between Elon Musk, TSLA critics and supporters, and local government officials. County officials argue that Tesla is yet to meet certain guidelines that would allow its formal approval to reopen the Fremont factory, but no details about these criteria have been released thus far. This has resulted in a rather sticky situation. The county says Tesla is not fulfilling safety guidelines, but it would not specify which. 

Strangely enough, Alameda County has also not discussed which parts of Tesla’s Return to Work Playbook are inadequate. A look at the playbook shows several intensive safety protocols that the company will be adopting to prevent the spread of the virus. But even the existence of the playbook itself, and more importantly, its contents, do not seem to be acknowledged by representatives of Alameda County when they speak against the electric car maker’s intentions to reopen the Fremont plant. 

https://twitter.com/flcnhvy/status/1259310677723959297?s=20

CEO Elon Musk has ordered Tesla’s Fremont factory to reopen despite opposition from Alameda County officials. Musk even noted that if anyone were to be arrested due to the factory’s reopening, it should only be him. Such a move has triggered a wave of negative coverage on the CEO, with some articles claiming that Musk is “asking” to be arrested, or “daring” law enforcement to apprehend him. A narrative has also formed suggesting that Tesla and Musk are “forcing” Fremont’s employees to build cars without any regard for public safety. A report from The Washington Post even quoted a Fremont factory worker who reportedly stated that “we are extremely frustrated, angry, scared, that Elon is putting his cars before his workers.”

Such a narrative is compelling, of course, and it makes for a good story. Every tale needs a villain, and Musk, with his outspoken, controversial remarks about the ongoing lockdown, is the perfect target. What is missing from this narrative is the fact that Musk himself has been quoted time and time again, in both spoken and written form, that workers at the plant are not forced to come to work at all. “I’d like to be super clear that if you feel the slightest bit ill or even uncomfortable, please do not feel obligated to come to work. I will personally be at work, but that’s just me. Totally ok if you want to stay home for any reason,” Musk wrote back in March. 

Advertisement
-
https://twitter.com/xxscotty209xx/status/1260100273608876032?s=20

A look at the social media feeds from Fremont factory workers paint a much less controversial picture amidst the facility’s reopening as well. Inasmuch as mainstream reports today are running with a narrative that suggests Tesla is forcing employees to catch the virus or perish for the sake of Musk’s pockets, such sentiments do not seem universal for the company’s workforce. Some workers at the factory have noted that they appreciate that work is being resumed, and that the company is indeed following through with its stringent anti-pandemic strategies. 

But such a scenario does not paint a narrative that is as compelling as a Machiavellian CEO forcing thousands of employees to perish for his personal profits. If Tesla is simply using a playbook that is tried and tested in Shanghai, and if workers are actually appreciative of the factory’s reopening, the anti-Elon Musk narrative gets lost. If there are no evil CEOs and mass numbers of employees being abused, Tesla’s Fremont facility becomes just a regular car production facility that is reopening its doors after a shutdown: one that is no different than car factories that are already open or are poised to reopen in the coming days. 

Unfortunately, the draw of Musk and Tesla and their surrounding narratives are simply too tempting to ignore. 

Tesla Return to Work Playbook by Simon Alvarez on Scribd

Simon is an experienced automotive reporter with a passion for electric cars and clean energy. Fascinated by the world envisioned by Elon Musk, he hopes to make it to Mars (at least as a tourist) someday. For stories or tips--or even to just say a simple hello--send a message to his email, simon@teslarati.com or his handle on X, @ResidentSponge.

Advertisement
Comments

Lifestyle

Watch Tesla’s “guardian angel” FSD feature take over for collision evasion

Published

on

By

Tesla’s Automatic Collision Evasion feature can be seen in one of the first owner videos of it in action.

Tesla owner Spencer (@scotsrule08) posted on Monday that the feature “worked flawlessly,” saying FSD reengaged itself just as he was about to hit a curb. Ashok Elluswamy, who leads Tesla’s AI team, shared the clip and wrote, “A guardian angel always looking out for you.”

The video arrives in the middle of a staged rollout. Tesla first shipped Automatic Collision Evasion with FSD (Supervised) v14.3.9 in software update 2026.27.6 earlier this month, which Teslarati covered as it reached cars. Update 2026.27.10, which began going out on September 19, carried the feature improvements with FSD v14.3.10, according to release notes tracked by Not a Tesla App. The newer 2026.27.11 build is now reaching another wave of vehicles.


The feature only runs on HW4 vehicles, and it requires an active FSD purchase or subscription with both FSD (Supervised) and Automatic Emergency Braking enabled. HW3 owners receive FSD v14.2 Lite in the same updates, but that build does not include collision evasion.

Tesla’s release notes describe two triggers. The first is an imminent frontal collision that braking alone may not prevent, in which case the car can activate FSD to steer, brake or accelerate around the hazard. That scenario is limited to highways below 85 mph, with no pedestrians or cyclists detected and no slippery road surface. The second covers a driver who appears inattentive, such as reaching into the back seat, or who seems to have switched off FSD by accident. Spencer’s curb clip appears to fall into that second category.

Tesla plans big safety improvements for Full Self-Driving v15

Once the system takes over, the accelerator is muted and light brake input will not cancel the maneuver. Drivers need to apply firm, deliberate steering force to take back control, and the car chimes to hand control back once the danger has passed.

Elluswamy recently noted that earlier hazard prediction, faster reaction time and better collision avoidance would arrive with FSD v15, the next major version.

Continue Reading

News

Tesla Roadster event gets delayed due to unfavorable weather

Published

on

Credit: Tesla

Tesla is delaying its event for the Roadster, moving it from this Thursday, October 1, to Thursday, October 15, due to unfavorable weather.

The company has said it has been tracking the weather for this Thursday closely with local meteorologists, and because the event can only be held outside, Tesla is making the call to delay it:

“We’ve been tracking the weather closely with local meteorologists, but given the severe conditions predicted & because this event can only be held outdoors, we’ve made the difficult decision to reschedule. New date is October 15. Additional details to follow.”

We are sure that this is bringing back PTSD for some Tesla fans, and we know it is not ideal, but this also reveals some things about the event. Tesla said that this can only be held outdoors, meaning it bodes well for the rumors that the vehicle could potentially hover.

Some believe that this was essentially confirmed by the FAA airspace restriction they were granted, but this could have been for a drone show or to keep drones from spying on the event.

Tesla Roadster is available for order once again following brief hold

The Roadster event has been long-awaited, and it is unfortunate that the weather is going to keep us all waiting a little bit longer.

The Tesla Roadster will be unveiled in Waco, Texas.

Continue Reading

Elon Musk

SpaceX turned a heralding moment for Starship into its greatest

Starship reached orbit despite losing an engine, deployed 26 Starlink V3 satellites on Flight 14.

Published

on

By

SpaceX’s Starship reached orbit for the first time on Monday, and for a few nail-biting minutes it looked like it wouldn’t. During ascent on Flight 14, one of Ship 41’s six Raptor engines shut down early, and SpaceX’s livestream host Dan Huot told viewers the team had decided not to commit to orbit. Minutes later, after what Huot described as a lot of conversation in the control room, the final poll came back in favor, and a roughly 19 second burn of a single Raptor pushed the ship into orbit about 170 miles up.

The reversal matters because SpaceX had written the exit ramp into the mission plan. The company said it would only fire the orbital insertion burn if flight controllers confirmed enough backup hardware remained for the deorbit burn, a condition Teslarati laid out ahead of the flight. Losing an engine was exactly the scenario that rule was built for.

Pressing forward fits Elon Musk’s history. Falcon 1 failed three straight times before its fourth launch reached orbit in 2008, with SpaceX nearly out of money, and Starship was developed by flying prototypes until they broke. What changed this year SpaceX going public, and with $SPCX sliding below its IPO price in July when Flight 13 slipped, the short interest climbed significantly, as Teslarati reported at the time. A Starship potentially lost today with revenue generating next-gen Starlink satellites aboard would have landed directly on shareholders.

That pressure showed up after orbit. SpaceX cut a flight planned to last nearly 10 hours to about three, moving splashdown from west of Chile to the North Pacific near Hawaii. SpaceX gave no reason, though Musk said this month the company was being extremely cautious about debris risk. The single Raptor for deorbit worked, and Ship 41 completed its flip and landing burn before breaking apart in the water, an outcome SpaceX expected. Musk has structured SpaceX’s governance to shield long term bets from market pressure.

The payload is the bigger business story. Musk posted that all 26 Starlink V3 satellites deployed and are “operating nominally.” Each V3 is rated for about 1 Tbps of downlink and 160 Gbps of uplink, so this single launch adds roughly 26 Tbps, about 10 times what a Falcon 9 load of V2 Mini satellites adds. The V3 is too large for Falcon 9, making Starship the only vehicle that can build out the planned 100,000 satellite constellation, at up to 60 per flight once it reaches routine service. Unlike the 20 V3 units on Flight 13, which reentered on a suborbital path, these will raise their orbits and could begin serving customers within weeks and bring in hundreds of millions of additional dollars in projected Starlink revenue.

SpaceX has already begun winding down Falcon 9 Starlink launches from Florida in favor of Starship. Reported targets put Flight 15 as early as October 19, leaving about three weeks to diagnose Monday’s engine shutdown before the next orbital attempt.

Continue Reading