Connect with us

News

SpaceX Falcon 9 Block 5 rocket’s drone ship return captured in stunning detail [gallery]

Published

on

Teslarati photographer Pauline Acalin has captured SpaceX’s first West Coast Falcon 9 Block 5 booster recovery in the best detail yet seen of the rocket upgrade, well-worn after its first successful launch of Iridium NEXT-7, July 25.

Iridium-7 marked a number of important debuts for SpaceX: Falcon 9 Block 5 (Booster 1048, in this case) completed its first West Coast launch from SpaceX’s Vandenberg pad, drone ship Just Read The Instructions’ (JRTI) first rocket recovery attempt and success in nearly ten months, and recovery vessel Mr Steven’s first (albeit unsuccessful) attempt at catching a Falcon fairing with a dramatically enlarged net and arms.

Although inclement wind conditions foiled Mr Steven’s fairing catch effort and put pressure on Falcon 9 B1048’s journey to JRTI, Iridium-7 was flawlessly placed in orbit and Falcon 9 managed a slightly off-center but still thoroughly successful landing on the drone ship off the coast of California. With that launch and land debut on the West Coast and a second successful East Coast launch of a Block 5 rocket to the East just a few days prior, SpaceX has effectively demonstrated the basic functionality and reliability of the upgrade’s many far-reaching changes to the underlying Falcon 9 architecture.

Just Read The Instructions recovers a rocket

After nearly ten months largely spent berthed at SpaceX’s original Port of San Pedro dock space, drone ship JRTI has at long last returned to sea and successfully recovered a Falcon 9 booster, this time marking the West Coast launch and landing debut of the Block 5 rocket. Photos of the drone ship and rocket’s return to port were some of the best ever seen, thanks largely to the port’s layout and narrow mouth, which allowed Teslarati photographer Pauline Acalin to put giant telephoto lenses and a unique top-down perspective to good use.

Iridium NEXT-7 thankfully brought an end to the understandable but still-painful practice of intentionally expending twice-flown Falcon 9 boosters in the ocean after launch. Thanks to Iridium-7’s new Block 5 booster, B1048, expending the rocket was out of the question, as it likely will be for most Block 5 launches in the future. A combination of several expendable missions and an unfortunate duo of recovery anomalies (a small fire after Koreasat 5A and the Falcon Heavy center core landing failure) led to JRTI sitting on the sidelines since October 2017, as a considerable subset of its critical thruster hardware had to be stripped in order to keep East Coast sister ship Of Course I Still Love You (OCISLY) operational for a handful of attempts in 2018.

Advertisement
-
-

Many of the months JRTI spent at berth were thus without the pod thrusters the drone ship needs to keep itself at the proper landing point once at sea. Still, JRTI departed the port with a full complement of four blue thrusters on the evening of July 22 and had a highly successful return-to-action. Sadly, it’s unclear how much SpaceX will need the vessel within just a month or two from today – after the final Iridium launch (NEXT-8) in November or December, perhaps all of SpaceX’s future Vandenberg launches will be lofting lightweight payloads that should allow the company to rely almost entirely on its brand-new rocket landing zone – conveniently colocated barely 1000 feet from the pad – for CA rocket recoveries.

F9 Block 5 shows off its upgraded exterior

Falcon 9 Block 5 booster (B1048) arrived at Port of Los Angeles on July 27 after landing at sea aboard drone ship JRTI. Photos captured by Pauline arguably show the best details yet seen of the rocket upgrade, ranging from titanium grid fins to extraordinary shots of its sooty-but-still-sorta-shiny Merlin 1D engines.

 

Myriad others provide an amazing sense of place with SpaceX technicians conducting thorough post-landing checkouts, carefully documenting the booster’s condition, and generally wrenching on a massive, orbital-class rocket that completed a suborbital jaunt to space just days prior.

Of particular note are detailed views of the silky black “highly flame-resistant felt” now covering Falcon 9’s interstage (the top segment), landing legs, octaweb section, and raceways (the black lines traveling up and down the rocket). Compared to beat-up, older Falcon 9s, B1048’s shielded components look barely worse for wear, and it would genuinely be difficult to determine if the rocket had flown before without the telltale soot fingerprint present after every Falcon 9 recovery.

 

The only mystery that still remains is what exactly Falcon 9 Block 5’s octaweb heat-shielding looks like, reportedly one of the most critical and research-intensive upgrades necessary for true rapid reusability and reliability through many, many flights. Now built largely of titanium bolted to the octaweb, among a number of other extremely heat-tolerant metals and materials and even active water-cooling in spots, the new heat-shield was designed to carry the brunt of the reentry heating Falcon 9 experiences with ease.

Advertisement
-
-

Perhaps we’ll get a glimpse of that yet-unseen heat-shield over the next few weeks and months. Many, many more launches to come, so stay tuned!


For prompt updates, on-the-ground perspectives, and unique glimpses of SpaceX’s rocket recovery fleet (including fairing catcher Mr Steven) check out our brand new LaunchPad and LandingZone newsletters!

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.

Advertisement
-
-

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.

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

Advertisement
-
-

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.

Advertisement
-
-

“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:

Advertisement
-
-

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.

Advertisement
-
-
Continue Reading