Connect with us

News

SpaceX returns Starship booster to factory after two major Raptor tests

Published

on

For the sixth time this year, SpaceX has returned the same Super Heavy booster prototype to its South Texas Starship factory after completing several tests.

Why is unclear. Super Heavy Booster 7 left the factory for the first time in March 2022 and has been stuck in a seemingly continuous state of testing, rework, and retesting ever since. While the pace of testing and progress was in many ways more aggressive from 2019 to mid-2021, it still can’t be said that SpaceX has been slacking off in 2022. Booster 7 alone completed more than 24 distinct tests (including six static fires) between early April and late November.

But in a shift from the first three or so years of steel Starship development, SpaceX CEO Elon Musk has ceased to be a consistent source of information on the purpose and results of many of those tests, even as NASA has begun to funnel hundreds of millions of taxpayer dollars into the Starship program. Save for occasional tidbits from SpaceX, Musk, and NASA; or deep unofficial analyses of public information, the day-to-day or week-to-week status of Starship has generally been relegated to speculation. Over the last few months, that information void has only grown larger.

Perhaps the biggest near-term update this year came from a senior NASA official on October 31st. In an advisory briefing, Mark Kirasich – Deputy Associate Administrator for Artemis Campaign Development – offered a surprising amount of detail about SpaceX’s near-term plans and even reported that Starship’s first orbital test flight was expected as early as December 2022, pending several crucial tests. But more than five weeks later, SpaceX appears to have only made a modest amount of progress towards those milestones and has yet to attempt the two most important tests.

Nonetheless, some progress – however indeterminate without official information – has been made. As of Kirasich’s briefing, SpaceX was in the middle of a relatively minor series of cautious propellant loading tests with Booster 7 and Ship 24, which were stacked on October 20th. After three more partial full-stack tests in the first seven days of November, Ship 24 was removed. Aside from the visible steps SpaceX took after, little is known about the outcome of those propellant loading tests.

Ship 24’s fate is a different story, but Super Heavy B7 appeared to make it through full-stack testing in great shape. On November 14th, Booster 7 completed a record-breaking 14-engine static fire, doubling its previous record of seven engines and likely becoming one of the most powerful rockets in history. Musk simply stated that the “test went well”.

Poor weather undoubtedly contributed, but it would be another 15 days before Booster 7’s next test. On November 29th, after an aborted test on the 28th, SpaceX followed Booster 7’s record-breaking 14-engine static fire with a longer 13-second test of 11 Raptors. Before engine ignition, SpaceX loaded Booster 7 with around 2800 tons (~6.2M lb) of liquid oxygen (LOx) propellant in less than 90 minutes, making it a partial wet dress rehearsal (the methane tank was barely filled) as well. Musk called it “a little more progress towards Mars” and SpaceX shared a photo of the static fire on Twitter, but the results of the test – meant “to test autogenous pressurization” – were kept mostly opaque.

Advertisement
-
-

That uncertainty didn’t help when two of Booster 7’s 33 Raptor engines were removed immediately after the long-duration test. Then, Booster 7 was removed from Starbase’s lone ‘orbital launch mount’ on December 2nd and rolled back to the factory’s High Bay assembly facility on December 3rd. Historically, SpaceX has only returned Booster 7 to the factory to repair damage or install missing hardware. Without official information, it’s impossible to say why Booster 7 returned for the sixth time.

The most optimistic explanation is that SpaceX brought the Super Heavy booster back to the factory to fully close out its engine section heat shield, which currently has 20 missing panels for each of its outer Raptor engines. But there’s a good reason that those panels were never reinstalled. Any replacements would need to be modified to ensure that the ad-hoc system installed to prevent the conditions that led to Booster 7’s first explosion from recurring can still be used for future static fire tests. Even then, it’s unclear why SpaceX would need to reinstall those panels now for Booster 7’s upcoming 33-engine static fire(s) and full-stack wet dress rehearsal(s) when they weren’t needed for 11 and 14-engine static fires and a dozen other fire-free tests.

Depending on why Booster 7 is back at the factory, there is a precedent for it returning to the launch site as early as next week. Alternatively, if major work or repairs are required, it could be six weeks before SpaceX returns the rocket to the launch pad. Given that the full wet dress rehearsals and one or several 33-engine static fires standing between Booster 7 and flight readiness will be riskier and more challenging than any other test the prototype has completed to date, there is no real chance that Starship will be ready for its first orbital launch this year.

In fact, without detailed information, especially regarding Ship 24’s mysterious state, it’s difficult to pinpoint a viable target for Starship’s orbital launch debut more specific than the first half of 2023. But with any luck, even if it requires a substantially longer wait, SpaceX’s recent decision to make Starbase move slower and break fewer things will hopefully pay off with a successful debut sometime next year.

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