Connect with us

News

SpaceX sends “radically redesigned” Starship engine to Texas for hot-fire tests

As of September 2017, subscale Raptor engines had been cumulatively fired for more than 1200 seconds in just 12 months of testing. (SpaceX)

Published

on

SpaceX has shipped one of the first of a group of Starship engines known as Raptor, described last month by CEO Elon Musk as “radically redesigned”. A culmination of more than 24 months of prototype testing, the first flight-worthy Raptor could be ignited for the first time as early as February.

According to Musk, three of these redesigned Raptors will power the first full-scale BFR prototype, a Starship (upper stage) test article meant to conduct relatively low-altitude, low-velocity hop tests over the southern tip of Texas. Those tests could also begin next month, although a debut sometime in March or April is increasingly likely.

Effectively designed on a blank slate, Raptor began full-scale component-level tests in 2014 at NASA’s Mississippi-based Stennis Space Center, evolving from main injector development to oxygen preburner hot-fires in 2015. Soon after Raptor’s prototype preburner design was validated at Stennis, SpaceX moved testing to its privately-owned and operated facilities in McGregor, Texas, where Raptor static fire testing has remained since.

Advertisement
-
-

Just days before CEO Elon Musk was scheduled to reveal SpaceX’s next-generation rocket (BFR, formerly known as the Interplanetary Transport System or ITS) in September 2016, he announced in a tweet that propulsion engineers and technicians had successful hot-fired an integrated Raptor prototype – albeit subscale – for the first time ever. Just 12 months later, Musk once again took to the stage to announce an update to BFR’s design, while also revealing that prototype Raptor engines had already completed more than 1200 seconds (20 minutes) of cumulative hot-fire tests, an extremely aggressive and encouraging rate of progress for such a new engine.

Although Raptor undoubtedly borrows heavily from much of the same expertise that designed Merlin 1 and operated and improved it for years, that is roughly where the similarities between Raptor and M1D end. M1D, powered by refined kerosene (RP-1) and liquid oxygen, uses a combustion cycle (gas-generator) that is relatively simple and reliable at the cost of engine efficiency, although SpaceX propulsion expertise still managed to give M1D the highest thrust-to-weight ratio of any liquid rocket engine ever flown. Still, measured by ISP (instantaneous specific impulse), M1D’s inefficient kerolox gas-generator cycle ultimately means that the engine simply can’t compete with the performance of engines with more efficient propellants and combustion cycles.

While SpaceX’s Falcon 9 and Heavy rockets – powered by Merlin 1D and Merlin Vacuum – are more than adequate in and around Earth orbit, a far more efficient engine was needed for the company to enable the sort of interplanetary colonization Musk had in mind when he created SpaceX. Raptor was the answer. Ultimately settling on liquid methane and oxygen (methalox) as the propellant and a full-flow staged-combustion (FFSC) cycle, Raptor was designed to be extraordinarily reliable and efficient in order to safely power a spacecraft (BFS/Starship) meant to ferry dozens or hundreds of people to and from Mars.

An excellent NASASpaceflight article explores the engine’s journey from a blank sheet to integrated static-fire tests and offers a deeper explanation of the technical details.

Raptor enters a new era

For all the extensive and invaluable testing SpaceX has done with a series of prototype Raptor engines, the engines tested were subscale versions with around 30% the thrust of the c. 2016 Raptor and around 40-50% of the updated c. 2017 iteration, producing almost the same amount of thrust as Merlin 1D (914 kN to Raptor’s ~1000 kN). In September 2018, Musk described Raptor as an “approximately…200-ton (~2000 kN) thrust engine” that would eventually operate with a chamber pressure as high as 300 bar (an extraordinary ~4400 psi), requiring at least one of the FFSC engine’s two preburners (used to power separate turbopumps) to operate at a truly terrifying ~810 bar (nearly 12,000 psi).

Advertisement
-
-

Conveniently stood beside a Merlin 1D engine also ready for hot-fire acceptance testing, the Raptor engine spotted departing SpaceX’s Hawthorne, CA factory last week was reportedly immense in person, towering over an M1D engine. Raptor also featured a mass of spaghetti-like plumbing (complexity necessary for its advanced combustion cycle), with a significant fraction of the metallic pipes and tubes displaying mirror-like finishes. Most notable was an obvious secondary preburner/turbopump stack and the lack of any exhaust port, whereas M1D relies on a single turbopump and exhausts the gases used to power it. Raptor’s full-flow staged-combustion cycle uses separate oxygen and methane preburners to power separate turbopumps, significantly improving mass flow rate and smoothing out combustion mixing.

 

Unlike all previous hot-fired Raptors, those shipping now to McGregor, Texas are expected to be the first completed engines with a finalized design, arrived at only after a period of extensive testing and iterative improvement. They also appear to be full-scale, meaning that the test bays dedicated to Raptor will likely need to be upgraded (if they haven’t been already) to support a two- or threefold increase in maximum thrust.

SpaceX’s Starship hopper will need three finalized engines, meaning that the Raptor now in McGregor, Texas may not have been the first to arrive. Nevertheless, the shipment of full-scale hardware is always an extremely encouraging milestone for any advanced technology development program, while also foreshadowing the first imminent static-fires of the “radcally redesigned” rocket engine. With hardware now at the test site before January is out, a February test debut – one month behind a January debut teased by Elon Musk last December – is not out of the question.


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

Advertisement
-
-

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