Connect with us

News

SpaceX Falcon 9 launch up next after ULA spy satellite mission hits snag

The United Launch Alliance Atlas V 531 is pictured on the launchpad of SLC-41 ahead of a scrubbed launch attempt. (Richard Angle)

Published

on

On Wednesday, November 3, a United Launch Alliance (ULA) Atlas V 531 rocket was set to launch the NROL-101 mission – a classified payload for the National Reconnaissance Office (NRO) of the United States government – from Space Launch Complex 41 (SLC-41) at Cape Canaveral Air Force Station. At neighboring Space Launch Complex 40 (SLC-40) a SpaceX Falcon 9 stood ready and waiting to launch a US military GPS satellite just a day later.

Ultimately, due to an anomaly with launchpad ground support equipment, the ULA launch attempt of the Atlas V NROL-101 mission was scrubbed Wednesday evening. Admittedly, the weather did not look promising either with ground winds remaining a concern throughout the countdown window.

With an hour and forty-seven minutes to go – just five seconds after a planned fifteen-minute hold was released – the launch teams announced that an anomaly had been discovered with “a ground valve issue with the liquid oxygen system for the Atlas V first stage.” The discovery initiated an immediate stop to the countdown and launch teams entered into an unplanned hold that would delay the targeted launch time.

At first, ULA conducted remote troubleshooting, but the anomaly was not remedied and a return-to-pad team would be required to enter the secured launchpad to physically investigate.

The United Launch Alliance Atlas V 531 rocket is stacked with the classified NROL-101 payload for the National Reconnaissance Office and the United States Space Force at Space Launch Complex 41 of the Cape Canaveral Air Force Station. (Richard Angle)

An anomaly team was deployed to investigate the valve that was restricting the flow of liquid oxygen (LOx) to the first stage of the Atlas V rocket. The hold remained for over an hour allowing the propellant lines to warm to a temperature that would be needed to be re-cooled prior to resuming the countdown.

Eventually, the return-to-pad team was able to evacuate the pad securing it for launch once again. Chill-down procedures to return the propellant lines back to an operational temperature began but were halted almost immediately. The anomaly had not been completely rectified and not enough time remained in the launch window to re-address it and re-chill the propellant lines. This led to the scrubbed launch attempt.

Typically, a scrubbed ULA mission for the NRO means that a neighboring SpaceX mission has to wait until the problem is fixed and ULA gets its rocket off of the nearby launchpad. However, that was not the case with Wednesday’s scrub. ULA stood down for a 48 hour recycle – rather than a typical 24 hour recycle – to attempt to launch the Atlas V 531 again on Friday, November 6.

This cleared the way for SpaceX to keep its targeted launch date of Thursday, November 5 during a launch window that extends approximately fifteen minutes from 6:24 – 6:39 p.m. EST (2324-2339 UTC) from SLC-40.

Advertisement
-
-
The payload fairing of the SpaceX Falcon 9 sports the mission artwork of the previous GPSIII-SV03 mission from June 30, 2020. (Richard Angle)

Following a successful static fire test of all nine Merlin 1D engines, SpaceX will attempt to launch the GPSIII-SV04 satellite for the United States military for a second time on Thursday, November 5.

The previous launch attempt on Friday, October 2 was thwarted at T-2 seconds due to anomalous engine start-up behavior. The unexplained early start-up of two Merlin 1D engines was eventually determined to be caused by “unexpected pressure rise in the turbomachinery gas generator” as explained by SpaceX CEO Elon Musk.

The engine anomaly prompted a thorough investigation of all Merlin 1D engines on the launch vehicle, as well as, a thorough investigation of the engines on two Falcon 9 launch vehicles designated for future NASA missions – the first operational rotation mission of the Commercial Crew Program, Crew-1, and the launch of the NASA and European Space Agency Earth-observation satellite, the Micheal Freilich Sentinel-6. Engines were eventually replaced on all three Falcon 9 launch vehicles.

A live hosted webcast of Thursday’s launch attempt will be provided on the company website and is expected to be available for viewing approximately fifteen minuted before liftoff.

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

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