Connect with us

News

SpaceX CEO Elon Musk talks Starship explosion: “We were too dumb”

Published

on

Two days after a last-second failure caused Starship SN9 to smash into the ground and explode, SpaceX CEO Elon Musk has returned to Twitter with some harsh preliminary reactions.

Right off the bat, in response to a question about why Starships SN8 and SN9 both attempted their unsuccessful landings with only two of three available Raptor engines, Musk frankly stated that “we were too dumb.” At face value, it’s a decent question, given that there are no obvious showstoppers to explain why Starships couldn’t make the most of the redundancy their three Raptor engines can offer.

After completing an otherwise flawless 6.5 minutes launch, ascent, and belly-flop descent, Starship SN9 began a critical ~120-degree flip maneuver, sequentially igniting two Raptor engines and using that thrust to flip from a belly-down attitude to a tail-first landing configuration. Unfortunately, though the first Raptor did fire up and put in a good effort, the second engine failed to ignite, leaving the building-sized rocket to impact the ground traveling far too quickly.

Ironically, more than three years ago, Musk himself revealed in a Reddit Ask Me Anything thread that he and his engineers had decided to modify Starship’s (then known as BFS) design by adding a third Raptor to its central cluster of two engines.

“Btw, we modified the [Starship] design since IAC [2017] to add a third medium-area-ratio Raptor engine partly for that reason (lose only 1/3 thrust in engine out) and allow landings with higher payload mass for the Earth to Earth transport function.”

Elon Musk – Reddit AMA – October 2017

Primarily meant to enable more efficient landings in Earth’s atmosphere, adding a third engine to that cluster would logically increase the chances of a successful (or at least survivable) landing in the event that one engine fails. Greater thrust and an improved thrust-to-weight ratio both during launch and landing would fundamentally improve the efficiency of Starship, likely making up for most or all of the added weight.

Starship SN9 lifted off with three Raptors but attempted to land with two. According to Elon Musk, that may have been an oversight. (SpaceX)
Back in 2017, BFS featured two smaller-nozzle Raptors, whereas SpaceX eventually side on three (and three Raptor Vacuum variants) for Starship. (SpaceX)
Ironically, the original ‘Starship’ (ITS) also featured a cluster of three central landing engines. (SpaceX)

In retrospect, it’s not entirely surprising to learn that a three-engine landing burn is probably the most logical option if three landing-class engines have been included in the design. In SpaceX and Musk’s defense, however, there are also several good reasons to use as few Raptor engines as possible.

Throttling high-performance rocket engines is exceptionally difficult and Raptor is not yet a fully mature engine, meaning that it’s throttle capabilities are likely less than optimal. That’s relevant because the higher a rocket’s thrust-to-weight ratio during landing, the more aggressive its landings have to be. SpaceX is apparently extremely conservative with Starship in this regard, prioritizing slow, gentle landings by only using two of three available engines.

Advertisement
-
-

Ironically, it’s possible that that attempt at risk reduction resulted in harder landings for both Starship SN8 and SN9, as three-engine landing burns could have potentially slowed them down significantly more before impact.

At the same time, though it may have mitigated the severity of both landing failures, three-engine landing burns would not have resolved the fundamental issues that caused them. In SN8’s case, low fuel header tank pressure doomed the Starship, while SN9 is more ambiguous. Aside from the clear Raptor ignition failure, which a three-engine burn could have resolved by downselecting to two healthier engines, the one Raptor that did ignite appeared to suffer some kind of uncontained failure seconds before landing.

Impressively, despite that apparent combustion chamber or preburner failure, the engine’s landing burn seemed to continued uninterrupted until the moment of impact. As such, it’s hard to say if that lone Raptor was still producing substantial thrust or if it was in the throes of a catastrophic failure. If it could have held on for another 5-10 seconds and the third Raptor (the engine that didn’t reignite) was able to restart and perform without issue, a three-engine landing burn could have easily made SN9’s demise less violent or even have enabled a soft landing.

While a three-engine burn all the way to touchdown appears to be extremely risky or impossible for present-day Starships, Musk implied that there was nothing preventing SpaceX from reigniting all three engines during the initial flip and landing burn and using that time to determine the health of all three engines. If all three were healthy, Starship would shut down one for a soft landing. If one engine failed to restart or lost thrust shortly after ignition, the other two would already be active and able to take over.

Musk says that Starship SN10, already at the launch pad and likely days away from its first tests, will attempt to adopt that approach on an upcoming test flight expected as few as 2-3 weeks from now.

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 Full Self-Driving v14.3.6 review: a rare regression, but some bright spots

Published

on

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

Elon Musk

Musk’s massive Terafab project will get final location soon

Published

on

Credit: SpaceX

Elon Musk’s massive Terafab project, which will be the first true conglomeration between each of his major entities, is set to get its final location soon, the CEO said on Tesla’s recent earnings call.

“The Terafab, we expect to announce a location soon, and provide more details about our plans in that regard. We’ll leave that to the product, the launch announcement rather than try to squeeze it into an earnings call,” Musk said last Wednesday.

Tesla Terafab set for launch: Inside the $20B AI chip factory that will reshape the auto industry

Terafab was announced by Musk back in March and was essentially a massive, vertically integrated semiconductor manufacturing project that would provide all the chips the three companies needed for their AI initiatives without needing third-party companies.

The plant will produce over 1 terawatt of AI compute each year, and will help back up projects like Optimus, Full Self-Driving, and other AI-based projects that Musk’s companies are working on.

In April, less than a month after the project was launched, Intel announced it would join the project, contributing manufacturing expertise and consulting to Terafab as a whole. Intel is one of three chip manufacturers that produce sub-5 nanometer chips at scale. TSMC and Samsung are the other two.

However, there was no true indication of where Terafab would end up, but most believe it will likely be somewhere in Texas. Business Insider has reported that SpaceX plans to build out Terafab in Grimes County, Texas, but this is unconfirmed.

Musk confirmed recently that it would not be on Giga Texas property, as it is simply too large.

Terafab holds much of Musk’s grand ambitions for the future within its construct. It holds so much responsibility for the future and the biggest projects that Musk’s companies can imagine.

“I think this is a very big announcement and it deserves to have its own day in the spotlight and not be squeezed into an earnings call,” he said. “I do think Terafab is going to be an amazing initiative and a necessary one, and one without which we will be constrained in our ability to scale Optimus production, because we simply won’t have enough AI chips.”

He continued by stating that Terafab is necessary for scaling Optimus, which Musk said could be the biggest product of any kind of all time. “It’s crucial to solve that, and we’ll have to solve memory, logic, and packaging in order to scale Optimus.”

Continue Reading

News

Elon Musk reveals SpaceX performed secret Starship test on Flight 13

Published

on

Credit: SpaceX

SpaceX performed a secret test on a specific portion of Starship with its recent 13th test flight last week, CEO Elon Musk revealed.

Starship’s 13th test flight took place last Friday, and in many aspects, it was one of the most overwhelmingly successful launches in the project’s history.

All of the mission objectives were met without incident, both the Super Heavy Booster and Ship managed to perform safe splashdowns in the Gulf of America and the Indian Ocean, respectively, and the deployment of Starlink satellites came and went without any complications.

However, there was more on the agenda for SpaceX with Flight 13. Musk revealed an internal test of the ship’s heat shield tiles, as the space exploration company wanted to push them to the limits after previous issues.

Many noticed that Starship’s initial launch seemed to be more accelerated than normal, and that was not a mistake. Musk revealed that SpaceX decided to give Flight 13 an intentionally aggressive acceleration rate in an effort to test how well the tiles would remain attached to the ship:

SpaceX had issues with some of the heat shield tiles remaining attached early on in the Starship program. The first six test flights presented some kind of anomaly with them, so the company’s big focus with them was to figure out a way to keep them intact through the duration of the flight.

Things truly improved as Flight 10 showed that ceramic tiles generally stayed attached to the ship far better due to refined attachment, as SpaceX utilized pins instead of adhesives. Flights 10 through 13 truly showed some clear progress with the heat shield tiles, and this latest test seems to be where some real progress was noticed, especially by Musk.

The 13th Starship launch last Friday was the second with Starship V3, SpaceX’s latest and greatest iteration of the spacecraft. Goals and ambitions are getting even grander as the project continues to progress. Musk has already hinted that SpaceX will likely try to catch Starship with Flight 14.

Continue Reading