Connect with us

News

Tesla-Rivian lawsuit heats up as Judge denies misappropriation request

Published

on

Tesla’s lawsuit against Rivian that claims the latter company attempted to steal trade secrets is heating up after Judge William Monahan threw out Rivian’s misappropriation of trade secrets claim. The Santa Clara, California Superior Court Judge also declined to dismiss claims that Tesla believes seven of its former employees revealed trade secrets to Rivian after beginning employment with the Normal, Illinois-based company.

Judge Monahan agreed to dismiss Rivian’s intentional interference in contract claim because it falls under the “trade secrets” portion of the lawsuit. Bloomberg uncovered the new ruling.

In July, Tesla initiated a lawsuit against Rivian, indicating an “alarming pattern” of poaching employees and stealing trade secrets was taking place. In its original complaint, Tesla believed four individuals, and potentially two additional ones went to Rivian and took secrets with them.

Tesla said:

“Misappropriating Tesla’s competitively useful confidential information when leaving Tesla for a new employer is obviously wrong and risky.”

Elon Musk then commented on the lawsuit several days later, saying that Rivian was “absolutely” poaching Tesla’s former employees but admitted it wasn’t a “massive percentage.” However, Musk said the employees who left and started working for Rivian “definitely” took Tesla’s intellectual property. One employee, Tami Pascale, who worked for Tesla as a Senior Staffing Manager, admitted to taking “at least ten confidential and proprietary documents from Tesla’s network, which would allow Rivian to poach Tesla’s highest-performing talent and promising employment prospects.”

Advertisement
-

“They’re doing bad things, so we sued them,” Musk said in an interview with Automotive News.

Tesla’s Elon Musk talks Rivian lawsuit, “They’re doing bad things, so we sued them”

Tesla has been pretty open with its information in the past. Musk has stated that the company’s patents are open and free to use on numerous occasions, especially if it will increase the push toward sustainable transport. However, poaching Tesla’s possible employees and developmental talent is not apart of the deal and is the basis for why it decided to take Rivian to court.

Rivian denied any wrongdoing and responded to the lawsuit in mid-August 2020, stating:

“As is evident from the many defects on the face of its complaint, this lawsuit is driven by these improper aims, and Tesla’s desire to use the judicial system as a prop to deflect attention from Tesla’s own challenges, to foment fear, uncertainty, and doubt about Rivian, and to provide the pretext to disparage Rivian and its own former employees in the press.”

Tesla claims that at least 178 of its former employees have gone on to work at Rivian, the July complaint said.

Advertisement
-

The case will take place in California’s Superior Court in Santa Clara County. It is recognized as Tesla Inc. v. Rivian Automotive Inc., case number 20CV368472.

Tesla lawsuit vs. Rivian 20… by Joey Klender

Joey has been a journalist covering electric mobility at TESLARATI since August 2019. In his spare time, Joey is playing golf, watching MMA, or cheering on any of his favorite sports teams, including the Baltimore Ravens and Orioles, Miami Heat, Washington Capitals, and Penn State Nittany Lions. You can get in touch with joey at joey@teslarati.com. He is also on X @KlenderJoey. If you're looking for great Tesla accessories, check out shop.teslarati.com

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.

Advertisement
-

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.

Advertisement
-
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.

Advertisement
-

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