Connect with us

News

SpaceX fires up Starship and Super Heavy booster hours apart

Two rockets; two static fires; three hours. (NASASpaceflight - bocachicagal)

Published

on

SpaceX appears to have successfully fired up a Starship and Super Heavy booster hours apart, testing a total of three new Raptor 2 engines on the two rockets.

SpaceX says it completed a two-engine static fire with Starship 24 less than three hours after the company successfully ignited a Raptor 2 engine installed on a rocket prototype for the first time. That earlier test, performed by Super Heavy Booster 7, was also the first time SpaceX used its new Starbase orbital launch site to support a static fire test and the second-ever static fire of a Starship booster prototype. Had the company called it quits after Booster 7 survived its first intentional trial by fire, it would have still been an exceptionally successful day.

But SpaceX wasn’t done.

Instead, after Booster 7’s seemingly flawless single-Raptor static fire at 5:25 pm CDT, SpaceX loaded Starship 24 with a small amount of liquid oxygen and methane propellant and ignited two of the ship’s six engines around 8:18 pm. It was not initially clear how many engines were involved but a tweet from SpaceX later confirmed it was two. More likely than not, one of those engines was a sea level-optimized Raptor with a smaller bell nozzle and the other was a vacuum-optimized Raptor with a much larger nozzle.

Almost ten months ago, Starship 20 – SpaceX’s first potentially orbital-class Starship prototype – began static fire testing in a somewhat similar way. Its first day of static fires began with a single Raptor Vacuum engine and ended with a simultaneous RVac and sea-level Raptor test in October 2021. In some ways, SpaceX has been a bit less cautious with Starship 24, which is the second potentially orbital-class prototype to begin proof testing. Ship 24 already has all six Raptors installed, whereas Ship 20 only had four of six engines installed during its first static fire tests. SpaceX also took about three weeks to progress from Ship 20’s first static fire test to its first static fire of all six engines, whereas it appears that Ship 24 could potentially attempt its first six-engine test just a few days to a week later.

On the other hand, Ship 24’s path to its first static fire was substantially longer than Ship 20’s. Ship 20 completed its first static fire test(s) just 25 days after its first proof test, referring to the process of verifying that the prototype was in good working order before moving on to riskier testing with flammable propellant and intentional ignitions. Ship 20 also completed its first six-engine static fire 46 days after testing began. Ship 24, meanwhile, took 75 days to go from its first proof test to its first static fire – almost three times slower than Ship 20, a prototype that was essentially the first of its kind.

It’s possible that Ship 24’s upgraded Raptor 2 engines are partially or fully to blame. Instead of jumping straight into ‘hot’ Raptor testing like Ship 20, which began that particular campaign with a partial-ignition preburner test, SpaceX put Ship 24 through seven ‘spin-prime’ tests before its first static fire. For Raptor, spin-primes test the ignition step before preburner ignition, which is itself a step before main combustion chamber ignition (where the engine starts to produce meaningful thrust). Raptor startup procedures likely involve flowing high-pressure gaseous helium, nitrogen, or propellant (oxygen/methane) through the engine to spin up its turbopumps, ‘priming’ them for preburner and main combustion chamber ignition.

Advertisement
-
-

On Raptor 1, the preburners would ignite once a high enough flow rate was achieved, producing hot gas that the main combustion chamber would mix and ignite one last time to start the engine. In a recent interview with Tim Dodd (“The Everyday Astronaut”), CEO Elon Musk revealed that SpaceX was able to “remove torch igniters” from Raptor 2’s main combustion chamber (MCC). It’s unclear if that means that Raptor 2 now has zero MCC igniters, but a major change in the overall ignition process could explain why the start of Ship 24 and Booster 7 engine testing was so sluggish. So could the unintended explosion Booster 7 caused when SpaceX attempted to spin-prime all 33 of its Raptor 2 engines at once.

Regardless, SpaceX has finally crossed that particular Rubicon and, with any luck, Raptor 2 testing will begin to speed up on both Starship 24 and Super Heavy Booster 7. SpaceX has test windows scheduled on August 11th, 15th, and 16th. A warning distributed to Boca Chica, Texas residents on August 10th confirmed that the company intends to perform at least one more static fire test on the 11th.

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

Featured

Tesla finally got its Nevada Robotaxi Permit but with a few catches hard to miss

Nevada granted Tesla’s robotaxi permit, but capped the fleet at just ten vehicles for now.

Published

on

By

Concept art of a Tesla Cybercab in Las Vegas Strip as rendered via Grok

Tesla has received its robotaxi permit in Nevada, more than two months after regulators closed the public comment period on the company’s application. News of the approval surfaced Wednesday night when Tesla investor and longtime company watcher Sawyer Merritt posted a copy of the interim order, and the Nevada Transportation Authority’s own carrier registry now lists the permit, AVNC Permit 002 under Docket 26-05015, as active for Tesla Robotaxi, LLC.

Tesla asked Nevada in June for authority to run up to 5,000 vehicles in Clark County within a year, however the permit the NTA issued is initially capping Tesla at ten fully autonomous vehicles and confines them to a defined geofence along the Las Vegas Strip corridor. Any expansion of that operating area, or any increase to the fleet size, requires the NTA’s approval first.

The order also sets rules that look more restrictive than what Tesla runs in Austin. Rides are barred on roads with posted speed limits above 45 miles per hour, pickups are off limits within a quarter mile of Harry Reid International Airport without separate authorization, and every vehicle has to carry visible “Robotaxi” markings while notifying riders before each trip that no one is driving. The order also requires “appropriate human supervision”, language that suggests Nevada isn’t ready to let Tesla offer the rides without a safety monitor that it has run in parts of Austin since January. As with standard protocol with robotaxi services, Tesla must report any accident, system failure, or vehicle that becomes stranded on a Nevada road within five business days.

Tesla is entering a market Nevada already knows well. Zoox, the Amazon owned robotaxi company, has run its own autonomous vehicle permit in the state since last year, building up to roughly 100 vehicles and 350,000 rides along the Strip. That history likely explains why the NTA started Tesla at ten cars rather than the fleet size the company asked for. The agency has a template for scaling a permit up once a company proves out its safety record.

Tesla’s Nevada application first surfaced in June, when the company filed for the permit alongside plans for a maintenance hub in southwest Las Vegas. The company has said it won’t meaningfully scale its robotaxi fleet anywhere until FSD v15 ships, expected in late 2026 or early 2027, which makes the ten vehicle cap less of a constraint today than it might look on paper. For now, Tesla has the legal right to start Nevada rides. Whether it starts before FSD v15 arrives is a separate question the permit doesn’t answer.

Continue Reading

Energy

Tesla launches Powerwall Lease for affordable home backup

Published

on

Credit: Tesla

Tesla Energy has introduced the Powerwall Lease in conjunction with Tesla Electric, making the service available in Texas. This new option delivers whole-home backup power using two Powerwall units for a net monthly cost of $35 after credits, accompanied by a low fixed electricity rate.

Under the lease terms, customers pay a one-time order fee of $100. The base lease payment for the two Powerwalls is approximately $122 per month during the first year, subject to a 3 percent annual escalator thereafter. Enrollment in a qualifying Tesla Electric Backup plan or Virtual Power Plant plan provides an $87 monthly credit.

This credit lowers the effective cost to roughly $35 per month plus applicable tax.

Installation of the standard system carries no additional charge. The package features Storm Watch for outage protection and allows complete management through a single Tesla application. The system supplies continuous whole-home backup capability.

The Powerwall system enables households to maintain electricity during severe storms that disrupt the utility grid. When outages occur, the batteries automatically provide seamless backup power to the home.

Tesla announces 100k Powerwalls are participating in Virtual Power Plants

Tesla Storm Watch monitors weather forecasts and ensures the units are fully charged ahead of anticipated severe weather events so that power remains available throughout the disruption, keeping lights, refrigeration, and other essential systems operating without interruption.

Availability is restricted to select Texas locations where retail electric choice exists. Participants must lease exactly two Powerwall units and maintain continuous enrollment with Tesla Electric. Solar panels cannot be included under this particular lease arrangement.

The monthly credit activates automatically once the system is installed, receives permission to operate, and enrollment is confirmed. To retain the credit, customers are required to stay enrolled in Tesla Electric and fulfill all program conditions.

Nonstandard installations that involve electrical upgrades or special permitting may lead to extra expenses and might impact eligibility for the credit, so be sure to check with either your installer or Tesla to ensure you will still qualify.

Continue Reading

News

Elon Musk teases Tesla Roadster unveiling once again

Published

on

tesla roadster
Credit: Tesla

Elon Musk continues to tease the unveiling event for the Tesla Roadster, a continuing trend that has grown into a bigger game of “When” for fans who have been waiting years for the car to finally enter production.

A video shared on X of the Joe Rogan Experience podcast that Musk appeared on last year, teasing the Roadster unveiling, was shared once again on the social media platform. The poster said the Roadster event will be “unforgettable.”

Musk agreed:

The timing is interesting because just yesterday, Musk said that we will be getting flying cars, and for years, Tesla has hinted that it could develop a SpaceX cold gas thruster package that would help the car float or fly for a short period of time.

It would be reasonable to assume Tesla’s major delays with this unveiling event are likely caused by the company’s need to break the rules and push the envelope on nearly everything. Last July, Lars Moravy, Tesla’s VP of Vehicle Engineering, said:

“Roadster is definitely in development. We did talk about it last Sunday night. We are gearing up for a super cool demo. It’s going to be mind blowing. We showed Elon some cool demos last week of the tech we’ve been working on and he got a little excited.”

The latest updates that Tesla has given us are that the Roadster is in design development, and it did have several potential dates for an unveiling event this year, including April. It was then pushed to August.

However, there are no clues as to when Tesla will be ready, and fans are certainly getting frustrated with the delays.

For what it is worth, Franz von Holzhausen told Jay Leno this week that the event would be “very soon.”

We sure hope.

Continue Reading