Connect with us

News

SpaceX wants to unleash Starhopper but longer Raptor test fires come first

SpaceX has reportedly fired a Raptor engine for more than 40 seconds, a necessary step along the path to untethered Starhopper test flights. (SpaceX & NASASpaceflight/bocachicagal)

Published

on

According to SpaceX CEO Elon Musk, the next round of Starhopper activity will focus on removing the spacecraft prototype’s tethers and performing far more substantial hop tests.

Longer tests demand that SpaceX begins expanding the known performance envelope of its full-scale Raptor engine. Towards that end, longer-duration tests would need to be done at the company’s McGregor, TX development facilities to reduce risk, tests that Musk confirmed are already well underway. A recent Raptor static fire reportedly lasted no less than 40 seconds, more than enough time for a single-engine Starhopper to significantly expand both the maximum altitude and velocity of future hop tests. In support of the upcoming Starhopper test campaign, significant construction work is also ongoing at SpaceX’s Boca Chica test and development facilities.

Starhopper awaits its return to hop testing, April 24th. (NASASpaceflight – bocachicagal)

Unleashing the Hopper

During the months of March and April, SpaceX’s South Texas team effectively completed Starhopper and put the prototype through its first real tests. The process began with tank proof tests in which Starhopper’s tanks were filled with liquid nitrogen – relatively neutral and unreactive – to safely identify and repair any leaks, while also subjecting the vehicle to cryogenic temperatures. The proof testing also put the newly installed ground systems (GSE) and vehicle-pad connection hardware through their paces before moving to Starhopper’s nominal liquid oxygen and liquid methane propellant.

Following at least half a dozen or so wet dress rehearsals (WDRs) that saw Starhopper loaded with LOx and methane, SpaceX technicians analyzed the health of the prototype and soon began live tests with a Raptor engine installed. Designed to produce no less than 2000 kN (450,000 lbf, 205 mT) of thrust at full throttle, Raptor offers more than twice the max thrust of the latest variant of the Merlin 1D engine that powers Falcon 9 and Heavy (941 kN or 212,000 lbf). In other words, a single Raptor should be more than enough to lift Starhopper off the ground 150+ tons of propellant aboard.

In the above tweets, Musk indicates that Starhopper’s next step will be untethered hop tests powered by one Raptor engine. This is further supported by confirmation that Raptor completed its longest static fire test yet on April 27th.

After several unsuccessful test attempts, Starhopper completed two static fires (<10s combined) and hopped – tethered – a handful of feet off the ground on April 3rd and 5th, three weeks after Raptor was first installed. Days later, the lone Raptor engine was removed from Starhopper and shipped back to SpaceX’s Hawthorne, CA factory or McGregor, TX testing facilities for post-test analysis and inspection. In short, SpaceX used Starhopper as a sort of ad hoc test stand for the second serial Raptor (SN02) produced, completing two major acceptance tests simultaneously.

A handful of concise tweets published by Musk in the last few days of April implicitly confirmed that the next steps for Starhopper involved untethered flights off its South Texas pad, once again powered by a single Raptor engine. As both the prospective altitudes and flight times rise for future Starhopper tests, so do the risks posed to SpaceX’s adjacent facilities and the prototype itself. To minimize those risks and progress the Raptor program as a whole, SpaceX has been extensively testing the third serial Raptor (SN03) at its McGregor facilities. Instead of a rushed test regime similar to the one that almost completely destroyed Raptor SN01 less than two weeks after testing began, SN03 is participating in a more cautious and systematic series of tests.

Technicians work inside Starhopper’s LOx tank on April 22nd. (NASASpaceflight – bocachicagal)
While almost impossible to visualize the changes from a flat perspective, several dozen trucks of dirt and concrete were delivered to Starhopper’s pad last week. (NASASpaceflight – bocachicagal)

Confirmed by Elon Musk, this included significantly increasing the length of Raptor SN03’s latest static fires, culminating in an April 27th test that lasted ~40 seconds. Above all else, long test fires are necessary to demonstrate that Raptor can reliably operate for dozens of seconds at a time, given that any failure leading to a loss of thrust could cause Starhopper – basically a controlled explosive device – to fall out of the sky. The famous Musk/SpaceX ethos of moving fast and breaking things does not preclude a pragmatic attitude towards the destruction of facilities and prototypes that could take months and millions of dollars to rebuild.

The ETA of future hop tests is unclear. For the time being, it appears that SpaceX’s South Texas facilities will be caught up in construction work for at least another week. Whether or not Raptor SN03 is next in line for installation on Starhopper, SpaceX will likely put it through several more long-duration static fires before moving ahead with untethered hop tests. All things considered, the rough Starship prototype is unlikely to restart powered testing for another two or so weeks. Stay tuned!

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

Elon Musk

We tested Tesla Full Self-Driving’s ability to let you text and drive

We decided to test it, and our main objective was to try to determine a more definitive label for when it would allow you to grab your phone and look at it without any nudge from the in-car driver monitoring system.

Published

on

Credit: Grok

On Thursday, Tesla CEO Elon Musk said that Full Self-Driving v14.2.1 would enable texting and driving “depending on [the] context of surrounding traffic.”

Tesla CEO Elon Musk announces major update with texting and driving on FSD

We decided to test it, and our main objective was to try to determine a more definitive label for when it would allow you to grab your phone and look at it without any nudge from the in-car driver monitoring system.

I’d also like to add that, while Tesla had said back in early November that it hoped to allow this capability within one to two months, I still would not recommend you do it. Even if Tesla or Musk says it will allow you to do so, you should take into account the fact that many laws do not allow you to look at your phone. Be sure to refer to your local regulations surrounding texting and driving, and stay attentive to the road and its surroundings.

The Process

Based on Musk’s post on X, which said the ability to text and drive would be totally dependent on the “context of surrounding traffic,” I decided to try and find three levels of congestion: low, medium, and high.

I also tried as best as I could to always glance up at the road, a natural reaction, but I spent most of my time, during the spans of when it was in my hand, looking at my phone screen. I limited my time looking at the phone screen to a few seconds, five to seven at most. On local roads, I didn’t go over five seconds; once I got to the highway, I ensured the vehicle had no other cars directly in front of me.

Also, at any time I saw a pedestrian, I put my phone down and was fully attentive to the road. I also made sure there were no law enforcement officers around; I am still very aware of the law, which is why I would never do this myself if I were not testing it.

I also limited the testing to no more than one minute per attempt.

I am fully aware that this test might ruffle some feathers. I’m not one to text and drive, and I tried to keep this test as abbreviated as possible while still getting some insight on how often it would require me to look at the road once again.

The Results

Low Congestion Area

I picked a local road close to where I live at a time when I knew there would be very little traffic. I grabbed my phone and looked at it for no more than five seconds before I would glance up at the road to ensure everything was okay:

Looking up at the road was still regular in frequency; I would glance up at the road after hitting that five-second threshold. Then I would look back down.

I had no nudges during this portion of the test. Traffic was far from even a light volume, and other vehicles around were very infrequently seen.

Medium Congestion Area

This area had significantly more traffic and included a stop at a traffic light. I still kept the consecutive time of looking at my phone to about five seconds.

I would quickly glance at the road to ensure everything was okay, then look back down at my phone, spending enough time looking at a post on Instagram, X, or Facebook to determine what it was about, before then peeking at the road again.

There was once again no alert to look at the road, and I started to question whether I was even looking at my phone long enough to get an alert:

Based on past versions of Full Self-Driving, especially dating back to v13, even looking out the window for too long would get me a nudge, and it was about the same amount of time, sometimes more, sometimes less, I would look out of a window to look at a house or a view.

High Congestion Area

I decided to use the highway as a High Congestion Area, and it finally gave me an alert to look at the road.

As strange as it is, I felt more comfortable looking down at my phone for a longer amount of time on the highway, especially considering there is a lower chance of a sudden stop or a dangerous maneuver by another car, especially as I was traveling just 5 MPH over in the left lane.

This is where I finally got an alert from the driver monitoring system, and I immediately put my phone down and returned to looking at the road:

Once I was able to trigger an alert, I considered the testing over with. I think in the future I’d like to try this again with someone else in the car to keep their eyes on the road, but I’m more than aware that we can’t always have company while driving.

My True Thoughts

Although this is apparently enabled based on what was said, I still do not feel totally comfortable with it. I would not ever consider shooting a text or responding to messages because Full Self-Driving is enabled, and there are two reasons for that.

The first is the fact that if an accident were to happen, it would be my fault. Although it would be my fault, people would take it as Tesla’s fault, just based on what media headlines usually are with accidents involving these cars.

Secondly, I am still well aware that it’s against the law to use your phone while driving. In Pennsylvania, we have the Paul Miller Law, which prohibits people from even holding their phones, even at stop lights.

I’d feel much more comfortable using my phone if liability were taken off of me in case of an accident. I trust FSD, but I am still erring on the side of caution, especially considering Tesla’s website still indicates vehicle operators have to remain attentive while using either FSD or Autopilot.

Check out our full test below:

Continue Reading

Elon Musk

Tesla CEO Elon Musk announces major update with texting and driving on FSD

“Depending on context of surrounding traffic, yes,” Musk said in regards to FSD v14.2.1 allowing texting and driving.

Published

on

Credit: carwow/YouTube

Tesla CEO Elon Musk has announced a major update with texting and driving capabilities on Full Self-Driving v14.2.1, the company’s latest version of the FSD suite.

Tesla Full Self-Driving, even in its most mature and capable versions, is still a Level 2 autonomous driving suite, meaning it requires attention from the vehicle operator.

You cannot sleep, and you should not take attention away from driving; ultimately, you are still solely responsible for what happens with the car.

The vehicles utilize a cabin-facing camera to enable attention monitoring, and if you take your eyes off the road for too long, you will be admonished and advised to pay attention. After five strikes, FSD and Autopilot will be disabled.

However, Musk announced at the Annual Shareholder Meeting in early November that the company would look at the statistics, but it aimed to allow people to text and drive “within the next month or two.”

He said:

“I am confident that, within the next month or two, we’re gonna look at the safety statistics, but we will allow you to text and drive.”

Today, Musk confirmed that the current version of Full Self-Driving, which is FSD v14.2.1, does allow for texting and driving “depending on context of surrounding traffic.”

There are some legitimate questions with this capability, especially as laws in all 50 U.S. states specifically prohibit texting and driving. It will be interesting to see the legality of it, because if a police officer sees you texting, they won’t know that you’re on Full Self-Driving, and you’ll likely be pulled over.

Some states prohibit drivers from even holding a phone when the car is in motion.

It is certainly a move toward unsupervised Full Self-Driving operation, but it is worth noting that Musk’s words state it will only allow the vehicle operator to do it depending on the context of surrounding traffic.

He did not outline any specific conditions that FSD would allow a driver to text and drive.

Continue Reading

News

Tesla Semi just got a huge vote of confidence from 300-truck fleet

The confidential meeting marks a major step for the mid-sized carrier in evaluating the electric truck for its regional routes.

Published

on

Credit: Tesla

The Tesla Semi is moving closer to broader fleet adoption, with Keller Logistics Group wrapping up a key pre-production planning session with the electric vehicle maker’s team this week. 

The confidential meeting marks a major step for the mid-sized carrier in evaluating the electric truck for its regional routes.

Keller’s pre-production Tesla Semi sessions

Keller Logistics Group, a family-owned carrier with over 300 tractors and 1,000 trailers operating in the Midwest and Southeast, completed the session to assess the Tesla Semi’s fit for its operations. The company’s routes typically span 500-600 miles per day, positioning it as an ideal tester for the Semi’s day cab configuration in standard logistics scenarios. 

Details remain under mutual NDA, but the meeting reportedly focused on matching the truck to yard, shuttle and regional applications while scrutinizing economics like infrastructure, maintenance and incentives.

What Keller’s executives are saying

CEO Bryan Keller described the approach as methodical. “For us, staying ahead isn’t a headline, it’s a habit. From electrification and yard automation to digital visibility and warehouse technology, our teams are continually pressure-testing what’s next. The Tesla Semi discussion is one more way we evaluate new tools against our standards for safety, uptime, and customer ROI. We don’t chase trends, we pressure-test what works,” Keller said. 

Advertisement
-->

Benjamin Pierce, Chief Strategy Officer, echoed these sentiments. “Electrification and next-generation powertrains are part of a much broader transformation. Whether it’s proprietary yard systems like YardLink™, solar and renewable logistics solutions, or real-time vehicle intelligence, Keller’s approach stays the same, test it, prove it, and deploy it only when it strengthens service and total cost for our customers,” Pierce said. 

Continue Reading