Connect with us

News

Rocket Lab set for Electron’s 9th launch as work continues on reusability, new US launch pad

The 9th completed Electron rocket stands vertical at Rocket Lab's New Zealand-based LC-1 launch pad, October 2nd. (Peter Beck)

Published

on

Over the last several weeks, US spaceflight company Rocket Lab has posted major updates about its ongoing work on LC-2 – the company’s second orbital launch complex – and offered a number of glimpses behind the scenes of preparations for Electron’s 9th orbital launch attempt.

That attempt will be streamed by Rocket Lab and could occur as early as October 17th, delayed from the 15th due to unfavorable weather conditions.

Prior to announcing booster recovery efforts – much like SpaceX and the Falcon 9 – the company broke ground on their first US-based launch facility, to be located at the Mid-Atlantic Regional Spaceport in Wallops Island, Virginia. Launch Complex 2 (LC-2) will join the company’s lone orbital Launch Complex 1 (LC-1) – New Zealand’s first and only orbital launch site – and is meant to enable Rocket Lab to eventually reach a biweekly-to-weekly launch cadence with Electron.

In a statement posted to the company’s social media accounts, Rocket Lab proudly announced that it is working alongside Virginia Space teams to construct LC-2 and its associated Integration and Control Facilities. The future pad recently reached a major milestone as workers installed LC-2’s 66-ton Electron launch platform, to be followed soon after by the installation of the mount’s 44 foot tall (13.4m) strongback, itself weighing 7.6 tons. This marks the beginning of the end of construction efforts at the complex and Rocket Lab is still working towards completion sometime in December 2019. Inaugural pad testing and shakedown operations are expected to begin immediately after, followed by LC-2’s first Electron launch sometime in early 2020.

Rocket Lab nears completion with its second launch complex at Virginia’s Mid-Atlantic Regional Spaceport with the installation of a 66-ton launch platform that will support the Electron rocket for up to 12 launches a year. (Rocket Lab)

The US launch facilities will closely resemble Rocket Lab’s New Zealand pad both in appearance and operation: Electron will be rolled horizontally to the launch mount to be lifted vertical after installation on the strongback. A high-pressure water deluge system will protect the mount from Electron and deaden some of the acoustic energy created by the booster.

The strongback lifting Electron vertically at Launch Complex 1
Mahia Peninsula, New Zealand 2017 (Rocket Lab)

Although Rocket Lab is an American company headquartered in Huntington, CA, it has never launched from the United States. The addition of a second launch complex is expected to drastically increase Electron’s launch cadence, while also lowering the burden placed on companies who would otherwise have to transport spacecraft internationally. In a statement, David Pierce – director of NASA Goddard Space Flight Center’s Wallop Flight Facility – said that “the company’s Electron rocket helps fill a key national need for providing more – and more frequent – launch opportunities for small satellites, and NASA’s Launch Range at GSFC/Wallops, which has enabled commercial space operations for decades, is poised and ready to support these missions.”

Rocket Lab previously worked with NASA to support the Educational Launch of Nanosatellites (ELaNa)-19 mission in December of 2018. So far, Rocket Lab has supported many small companies by launching a total of 39 satellites to orbit. A launch facility located in the US will allow the company to expand its customer base and open up opportunities for more US government launch contracts.

The new US-based launch facility will allow Rocket Lab to expand its employee roster by hiring up to 30 new team members in positions supportive of launch operations including engineering, launch safety, and administration. Launch Complex 2 has been certified to fly Electron up to 12 times a year – specifically supporting government contracts – while Launch Complex 1 in New Zealand has been certified for up to 120 launches per year.

Electron’s 9th launch – nicknamed “As the Crow Flies” – is scheduled for liftoff no earlier than (NET) October 15th and will be a dedicated commercial mission for startup Astro Digital. It will serve as an orbital launch attempt for Astro’s “Corvus” satellite bus and will test the world’s most powerful small electric propulsion system. In a recent blog post, Rocket Lab Senior Vice President of Global Launch Services Lars Hoffman stated that “the mission is a perfect example of the tailored, responsive and precise launch service sought by an increasing number of small satellite operators.”

Advertisement
-
-

On October 4th, the 9th flight-qualified Electron rocket completed a routine wet dress rehearsal (WDR) – loading the vehicle with propellant and counting down to launch (sans ignition) – at LC-1. A few days later, Astro Digital’s spacecraft was integrated with a Curie-powered kick stage and encapsulated inside Electron’s carbon fiber payload fairing.

As of now, everything is smoothly on track for Electron’s ninth launch. Of note, the Flight 9 Electron booster is outfitted with a new telemetry system designed to gather a huge amount of data about the reentry environment the booster experiences, data that will be used to reinforce the booster and prepare for its first recovery attempts.

Due to the volume of data that will be produced, Electron will quite literally eject small data capsules that will then be recovered by boat in the Pacific Ocean. If all goes well and the data returned looks promising, Rocket Lab could attempt its first Electron recoveries – nominally grabbing the parasailing booster mid-air with a helicopter – at some point in early 2020.

Check out Teslarati’s newsletters for prompt updates, on-the-ground perspectives, and unique glimpses of SpaceX’s rocket launch and recovery processes.

Space Reporter.

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