Connect with us

News

SpaceX’s first flight-proven Starship could fly again, says Elon Musk

CEO Elon Musk says that SpaceX wants to reuse its first flight-proven Starship prototype. (NASASpaceflight - bocachicagal)

Published

on

Elon Musk says that SpaceX wants to reuse its first flight-proven Starship prototype, although the rocket’s second hop might come after the debut of a totally different ship.

On August 4th, for the first time ever, a full-scale Starship prototype measuring some 9m (30 ft) wide and 30m (~100 ft) tall lifted off from SpaceX’s Boca Chica, Texas test facilities. Just three weeks shy of the first anniversary of Starhopper’s last flight test, Starship serial number 5 (SN5) essentially repeated the stubby prototype’s 150m (~500 ft) hop before (relatively) gently landing on an adjacent concrete pad.

Over the last several days, SpaceX has gradually been working through the unprecedented task of inspecting, safing, and relocating a flight-proven Starship. At the same time, the company has to check out the fixed launch mount structured that supported the test flight and provided Starship with power, propellant, and wired communications. As teams work to get both ship and mount ready for round two, CEO Elon Musk has taken to Twitter to discuss some of SpaceX’s nearer-term goals and plans for Starship testing – including SN5’s role in them.

CEO Elon Musk says that SpaceX wants to reuse its first flight-proven Starship prototype. (NASASpaceflight – bocachicagal)

Starship SN5’s hop debut was a spectacular success for SpaceX, verifying that steel and radically simple and manufacturing techniques can quickly build a cheap pressure vessel capable of controlled flight. The flight also reaffirmed that the next-generation Raptor engine is capable of operating uninterrupted for at least ~50 seconds, although Starhopper’s 150m hop proved the same thing some 20 engine prototypes and 13 months prior.

Still, while it unequivocally proved that SpaceX is on the right track, both the lead-up to Starship SN5’s hop and the hop itself hint that a few kinks will still need to be worked out. Notably, during SN5’s hop, part of Raptor engine SN27 appeared to catch fire at some point after ignition, producing substantial flames that lasted for at least 10 seconds. For any rocket engine, an onboard fire is always a possibility, but most engines are either designed to tolerate the inhospitable environment they create or heavily insulated from it.

Raptor SN27 was installed on Starship SN5 around July 3rd or 4th. (NASASpaceflight – bocachicagal)
Starship SN5 marked the successful debut of “v1.0” of a new kind of SpaceX landing leg. (NASASpaceflight – bocachicagal)
RIP landing legs :'( (NASASpaceflight – bocachicagal)

Festooned with sensitive wires and harnesses, Raptor prototypes are likely not meant to experience an extended onboard fire and remain functional, but SN27 nevertheless did just that. At a minimum, Starship SN5 thus likely needs a new Raptor engine before it can begin to prepare for a second hop.

The prototype will also assuredly need several new landing legs after destroying at least two during its launch and landing debut. It’s worth pointing out that the leg damage visible above is almost certainly the result of an intentional design choice, ensuring that landings slightly rougher than expected transfer most of their stress into Starship’s legs instead of its hull. Given just how simple they appear, the current leg design likely makes them effectively disposable, allowing SpaceX to focus its effort on unsolved problems as a more refined and reusable leg design comes to fruition.

SpaceX recently began stacking Starship SN8 besides SN6, a prototype that was more or less finished several weeks ago. (NASASpaceflight – Nomadd)

Aside from confirming that SpaceX at least intends to reuse Starship SN5 on future hops, Musk revealed that he wants to refine the launch procedure until the company is able to easily perform multiple Starship hops per day. This suggests that the next one or several months could be chock full of Starship hop attempts. Musk also noted that Starship SN6 – a prototype built along SN5 and effectively completed weeks ago – would likely attempt its first flight before SN5 hops a second time. SpaceX began stacking the upgraded Starship SN8 prototype just a few days ago, raising the question of whether Starship SN6 would be made redundant before it could even left the factory.

Thankfully, it seems that the ship will instead be able to work alongside its sister (SN5) to help SpaceX simplify and expedite Starship test and launch operations. As of now, it’s unclear when SpaceX intends to restart Starship testing, but Musk’s comments point towards the next test happening far sooner than later.

Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.

Advertisement
-
-

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