Connect with us

News

SpaceX’s Falcon 9 wins launch of an asteroid-attacking NASA spacecraft

Published

on

Just minutes before SpaceX began fueling Falcon Heavy for its commercial launch debut, NASA announced that the company had won a contract for its Double Asteroid Redirection Test (DART) mission, to be launched by Falcon 9 for the low cost of $69M.

Designed to cost less than $250M total, the DART mission will aim to be as light and fast as possible, using a dedicated Falcon 9 to send the ~600 kg (~1300 lb) spacecraft and its Italian companion cubesat on an ~11 million kilometer (~7M mi) journey to the binary asteroid Didymos. The ultimate purpose of DART is to effectively prove out both technologies and physics that could be used in the future to defend Earth from asteroids known to be on a collision course.

If all goes as planned during DART’s imminent design review milestones and hardware integration, Falcon 9 could launch the spacecraft towards the Didymos asteroid system in June 2021 for an October 2022 arrival. That “arrival” would involve DART impacting Didymos-B – the smaller of the pair at 163 m (535 ft) across – at a relative velocity of more than 6 km/s (3.7 mi/s). Nicknamed Didymoon, Didymos-B effectively orbits Didymos-A. At that speed, the ~600 kg probe will create an impact with the equivalent explosive force of nearly two and a half tons of TNT, the purpose of which is to determine just how much the sheer kinetic energy of impact can modify a small body’s orbit around the main asteroid.

Estimates from the spacecraft’s mission managers expect Didymoon’s orbit to be shifted by about 1% as measured by the time it takes to orbit Didymos-A, from ~11.9 hours to ~11.8 to 12.0 hours. This is a very small change but one that should – in theory – be easily measurable by telescopes on Earth, despite the fact that Didymoon has been estimated to have a mass of approximately 3.5 million metric tons (7.6 billion pounds), approximately seven million times heavier than DART. In short, NASA is going to functionally bomb an asteroid moon to see if humans might be able to use kinetic impactors to gently ‘boop’ threatening space objects off of the offending trajectory years or even decades in advance.

Despite the inherently destructive, single-use nature that DART’s impactor status bestows, current plans thankfully include an Italian cubesat known as LICIACube. The small copassenger will deploy two days before impact to fully exploit the scientific value of DART’s demise with high-quality photos of the event and aftermath. LICIACube will be traveling the same speed and thus won’t be able to enter orbit around the asteroid system, but a European Space Agency (ESA) mission known as Hera plans to do just that in the mid-2020s to better characterize Didymos and the crater (hopefully) made by DART.

Aside from the mission itself, DART serves as a technology demonstration platform for NASA. It will mark the first in-space use of the NASA-built NEXT-C ion thruster and powerpack, as well as the first standalone use of Roll-Out Solar Array (ROSA) deployment mechanism (shown above being tested on the ISS). Even more intriguing is a proposed transformational solar array planned at one point for DART, a flexible combination of advanced solar cells (~33% efficient) and mirror concentrators that could feed a spacecraft five times as much power for a given solar array area and distance from the sun. It’s unclear whether this will make it into DART’s final design but it still appears to be on the table as of January 2019. According to the contracted manufacturer, DART’s solar array will produce ~6.6 kW, while rough estimates suggest that the solar array will have an area of 16 m^2 (170 ft^2). Relative to the simplicity of the deployment mechanism and small size of DART (~600 kg total), this is an incredible amount of accessible power.

The most recent render of the NASA/APL DART spacecraft. (NASA/APL)
Falcon 9 B1045 rolls out to LC-40 ahead of SpaceX’s first dedicated NASA payload, the TESS exoplanet observatory. (SpaceX)

Getting to orbit

For NASA’s SpaceX launch contract, the agency will pay just $69M, barely 10% above Falcon 9’s bare-minimum list price of $62M. It’s safe to assume that the timing of the contract award – days after SpaceX abruptly dropped an official protest of ULA winning a ~$150M NASA contract – might not be coincidence. Regardless, SpaceX’s decision to bid so low for a NASA launch does lend some serious credence to the company’s protest that ULA’s contract for the mission – NASA’s LUCY asteroid explorer – was “vastly more [expensive]” than the bid SpaceX submitted.

Weighing just ~600 kg (~1300 lb) wet, DART could end up launching with additional copassengers on Falcon 9, although there is a precedent set by NASA’s ~360 kg TESS and Taiwan’s Formosat-5 for SpaceX giving tiny spacecraft dedicated launches. Additionally, it’s possible that DART will launch on a flight-proven Falcon 9 Block 5 rocket, given the likelihood that NASA will have certified flight-proven SpaceX vehicles for almost any launch by 2021.

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

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