Connect with us

News

Elon Musk says SpaceX making good progress on Starship’s upgraded Raptor 2 engines

Published

5 years ago

on

As is routine, SpaceX CEO Elon Musk has taken to Twitter to offer a few details about the status of Starship, its Raptor engines, and a few upgrades planned for both.

In mid-December, Musk revealed even more ambitious plans to upgrade Starship by stretching its propellant tanks and adding another three Raptor engines, potentially boosting the ship’s maximum thrust by 50% and substantially improving payload performance. These latest details are focused on an upgraded version of the Raptor engine and on additional changes to Starship’s structural design and assembly process.

Starship SN8, December 2020. (SpaceX)

According to Musk, as SpaceX continues to ramp up ground testing of the upgraded engine variant, “Raptor 2 now operates routinely at 300 bar main chamber pressure.” For context, on February 10th, 2019, just days after SpaceX began testing the first full-scale Raptor prototype ever completed, the engine briefly reached a main combustion chamber pressure just shy of 269 bar (3900 psi). That narrowly beat records set by Russia’s RD-270 and RD-180 engines, the latter of which is used on ULA’s Atlas V.

It took 18 months before Musk revealed clear proof that at least one Raptor prototype sustained such high chamber pressures over a minute or more of steady-state operations. The same engine peaked at an impressive 330 bar (~4800 psi), briefly producing 225 tons (~500,000 lb) of thrust and soundly beating out Russia’s never flown RD-701 engine, which crested 290-300 bar in testing. Another ~18 months after that milestone, Raptor isn’t quite operational in the sense of supporting orbital-class launches but the engine isn’t far from its first and has since supported dozens of Starship static fires and seven flight tests – five of which occurred in a period of just six months.

Already, despite the fact that Raptor 1 or 1.5 engines have yet to even attempt an orbital-class launch, SpaceX has almost entirely moved on to a new and improved variant known as Raptor 2. According to Musk, all Raptor ground testing at the company’s McGregor, Texas development campus is now focused on the new hardware, which reportedly features much cleaner plumbing and wiring. The biggest change to Raptor 2, though, is an almost 25% increase in maximum nominal thrust over Raptor 1/1.5 – from around 185 to 230 tons (408,000-507,000 lbf). That’s partially enabled by widening the ‘throat’ of Raptor’s nozzle, which sacrifices a small amount of efficiency for more power density. However, Raptor 2 also contains design improvements throughout to enable sustained, reliable operation at chamber pressures up to 300 bar – 10% higher than Raptor 1.5.

On October 24th, Musk subtly live-tweeted one of the first Raptor 2 static fires, revealing that the engine reached a chamber pressure of 321 bar (~4650 psi) and briefly produced around 245 tons (~540,000 lbf) of thrust before destroying itself. Now, a little over two months later, Musk says that Raptor 2 prototypes are routinely operating at 300 bar without major issues, meaning that they can ignite and safely shut down after burning for several minutes at those pressures. In theory, given that 300 bar is Raptor 2’s targeted chamber pressure at max thrust, that means that the engine is now “routinely” operating at the level SpaceX wants and needs to take Starship to the next level.

It’s likely that one or several months of work remain before SpaceX can begin qualifying the first Raptor 2 engines (or, more importantly, hypothetical Raptor 2 Vacuum or Boost variants) for the first Starship or Super Heavy prototypes designed for the new engine. Nonetheless, the rapid progress SpaceX has made in the first few months of Raptor 2 testing is extremely encouraging.

Advertisement
-
-
Related Topics:

Eric Ralph is Teslarati's senior spaceflight reporter and has been covering the industry in some capacity for almost half a decade, largely spurred in 2016 by a trip to Mexico to watch Elon Musk reveal SpaceX's plans for Mars in person. Aside from spreading interest and excitement about spaceflight far and wide, his primary goal is to cover humanity's ongoing efforts to expand beyond Earth to the Moon, Mars, and elsewhere.

Advertisement
Comments

News

Tesla briefly offered this Robotaxi part for your personal car

Published

51 minutes ago

on

July 28, 2026

By

Credit: @tpgoebel | X

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.

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.

Continue Reading

News

Tesla Robotaxi gets sweeping but polarizing change

Published

3 hours ago

on

July 28, 2026

By

Credit: Tesla

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:

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.

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.

Continue Reading

News

Tesla Full Self-Driving v14.3.6 review: a rare regression, but some bright spots

Published

24 hours ago

on

July 27, 2026

By

Credit: Tesla

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.

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.

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.

Continue Reading