Connect with us

News

SpaceX wins US Air Force contract for Falcon Heavy launch

Published

on

In an unexpected bode of confidence in the nascent vehicle, SpaceX has competed for and won a $130 million US Air Force launch contract for the massive Falcon Heavy rocket. While not planned to occur until September 2020 at the earliest, the most critical aspect of this development is the fact that the USAF has apparently already certified Falcon Heavy for high-value military launches.

The almost knee-jerk certification of Falcon Heavy for USAF launches makes for an extraordinary contrast when compared with the certification of SpaceX’s Falcon 9 workhorse rocket, a tedious political minefield that took more than two years, led SpaceX to (successfully) sue the federal government, and forced the Air Force to critically reexamine its internal processes after they delayed SpaceX’s certification by six or more months. For that particular endeavor, the USAF required SpaceX to complete three successful Falcon 9 launches, while also preventing SpaceX from engaging in launch contract competitions until their launch vehicle was certified in May 2015.

Jump ahead to 2018 and SpaceX appears to have been allowed to compete for this particular mission – known cryptically as AFSPC-52 – before Falcon Heavy had so much as completed an integrated static fire test. The awe-inspiring rocket did, however, complete a nearly-flawless debut launch in February 2018, a mission that required the company’s Falcon upper stage to survive a lengthy (6+ hour) coast in orbit before igniting its Merlin vacuum engine for one final burn. Regardless of the specifics, many of which have likely been kept under wraps, the Air Force must have been quite impressed with the rocket’s debut performance, and Falcon Heavy has now – according to President and COO Gwynne Shotwell – been certified for USAF missions just four months later.

 

It’s somewhere between difficult and impossible to accurately compare the different payloads and launches of the Air Force Space Command (AFSPC), but SpaceX’s only competitor ULA was awarded a contract for the launch of two relatively different AFSPC payloads at an average (fixed) cost of $175 million per mission. Those satellites were likely much smaller than AFSPC-52 but they require direct insertion into geostationary orbit (GEO), whereas AFSPC-52 may instead be sent to a geostationary transfer orbit (GTO) before circularizing the orbit under its own power.

Advertisement
-
-

Still, SpaceX’s triple-booster Falcon Heavy launch contract will cost the USAF a slim $130m. It’s worth noting that the 2018 AFSPC-8 and -12 contracts awarded to ULA were for the company’s single-booster Atlas 5 rocket, with most of the draw coming from its admittedly advanced, efficient, and extraordinarily reliable Centaur upper stage, tasked with reigniting repeatedly to circularize the orbit of its valuable satellite payloads once in space.

While it requires far less rigor than the Air Force’s more secretive, national security-sensitive satellite launches, SpaceX’s second Falcon Heavy launchthis time with three highly-reusable Block 5 boosters – will also be conducted with the military branch as the primary customer. Known as Space Test Mission-2 (STP-2), Falcon Heavy will be tasked with carrying a stack of dozens of different smallsats to a variety of orbits. Of note, the vast majority of that mission’s payload comes in the form of a 5000-kilogram ballast mass, included because the mission was manifested on Falcon Heavy (instead of the operational Falcon 9) for the sole purpose of facilitating the rocket’s rapid certification for critical Air Force missions.

 

STP-2 is currently scheduled for no earlier than (NET) November 2018, while the third launch of Falcon Heavy – the commercial Arabsat 6A communications satellite – is tentatively targeted for December, although it’s almost guaranteed to slip into Q1 2019.

Follow us for live updates, peeks behind the scenes, and photos from Teslarati’s East and West coast photographers.

Teslarati   –   Instagram Twitter

Tom CrossTwitter

Advertisement
-
-

Pauline Acalin  Twitter

Eric Ralph Twitter

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 silences Robotaxi turn signals in sweeping but polarizing change

Published

on

Credit: Tesla

Tesla has started rolling out a broader change to the ride experience for its Robotaxi fleet by silencing turn signals, but the change is certainly polarizing.

Tesla has generally made it clear that its purpose-built ride-hailing platform, Robotaxi, will cater to the rider in nearly every way possible. This includes having climate preferences, music, and other personal settings loaded up in the car as the rider enters.

But Tesla is taking it a step further by muting turn signal chimes altogether, a change that appears to be a way to make the ride more peaceful:

However, there are a handful of people who are not thrilled about this change. Turn signals are a conditioned part of the human mind for those who ride in a car regularly.

Advertisement
-
-

Taking a turn without one feels strange and odd, and not hearing it click while activated could set off some alarms for riders, who might use the noise as confirmation that other drivers know of their intention to turn.

Turn signal noises are still audible in customer cars, so if you use FSD in your personal vehicle, you will still hear the turn signal.

The move is certainly one that is unique, but not one that separates it from other ride-sharing services. In a normal car, the clicking sound confirms to the driver that the blinker is active. In a fully driverless Robotaxi, that feedback serves no purpose for passengers, other than peace of mind.

Continue Reading

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