Connect with us

News

SpaceX prepares Starship, Super Heavy for milestone Raptor static fire tests

Starship S20 and Super Heavy B4 are fast approaching readiness for their first crucial tests - including multiple Raptor static fires. (NASASpaceflight - bocachicagal)

Published

on

SpaceX has scheduled a full week with as many as 30 hours of road and beach closures for Starship and Super Heavy testing and is working hard to prepare the first orbital-class ship and booster for several major challenges.

First rolled to SpaceX’s Starbase orbital launch site more than six weeks ago and stacked together for the first time on August 6th, the company has spent the last month putting the finishing touches on Starship 20 (S20) and Super Heavy Booster 4 (B4) – ranging from heat shield installation to plumbing and wiring. Perhaps most importantly, SpaceX has also installed some or all of the Raptor engines that are expected to support the ship and boosters’ first static fire qualification tests.

For a number of reasons, those static fires – and a few additional tests expected to precede them – could be huge milestones for SpaceX’s Starship program.

SpaceX appears to have begun finalizing the Raptor engines that will be aboard Super Heavy for its first major static fire testing. (NASASpaceflight – bocachicagal)

Earlier this month, after rolling Starship S20 to the launch pad for the second time and installing it on one of two suborbital launch/test mounts, SpaceX began the process of installing Raptor engines (again for the second time) on the rocket. Beginning with two center sea level-optimized Raptors, SpaceX then installed a Raptor Vacuum engine on Ship 20. The implication: when S20 fires up for the first time, it might be doing so with two kinds of Raptor engines – a first for the Starship program.

Since Raptor Vacuums first began static fire testing at SpaceX’s McGregor, Texas development campus around Q4 2020, the company has yet to fire up an RVac engine on a Starship prototype. Starship’s current design features three gimballing sea-level Raptors and three vacuum-optimized variants with much larger nozzles – all in close proximity inside a 9m-wide (30 ft) skirt.

S20 had six engines installed for the first time in Starship history on August 4th. (Elon Musk)
Those engines were removed when S20 returned to the launch site late last month but have been gradually reinstalled over the last two weeks. (NASASpaceflight – bocachicagal)

As such, the first Starship static fire with any combination of Raptor Center and Raptor Vacuum engines will be a significant milestone for SpaceX. Eventually, that will likely culminate in the first static fire(s) of a Starship (likely S20) with all six Raptors installed – a test that will effectively qualify that prototype for its first orbital launch attempt.

Meanwhile, things are arguably even more complex for Super Heavy. Aside from a single three-engine static fire completed by Super Heavy Booster 3 (B3), Starship’s first stage has never come close to a full-up static fire with all 29-33 Raptor engines installed. Whenever that occurs, Super Heavy will likely become the most powerful rocket ever tested and – like with Starship – will be more or less qualified for its first flight if the test goes according to plan.

Advertisement
Super Heavy B4’s first and second trips onto the orbital launch mount. (SpaceX/SPadre)

SpaceX already installed a full 29 Raptor engines on Super Heavy B4 last month. After returning to Starbase, those engines were removed and eventually reinstalled a few weeks later – albeit with a number of replacements. Now, having spent the last 11 days sitting on the orbital pad’s launch mount, SpaceX has begun to replace at least one of Booster 4’s 29 installed engines. It’s unclear why but the fact that SpaceX is replacing engines at the launch pad – instead of rolling Super Heavy back to the build site for the third time – is an encouraging sign that B4 is nearly ready for its first proof and static fire tests.

Due to all the recent activity, it’s almost impossible to tell whether Starship S20 or Super Heavy B4 will be first onto the figurative saddle for ambient pressure, cryogenic, and static fire proof testing. What is clear, though, is that SpaceX has five six-hour testing windows scheduled every day next week. Stay tuned for updates on the next steps for SpaceX’s first orbital-class ship and booster pair.

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.

Comments

News

Tesla Full Self-Driving (Supervised) v14.1.7 real-world drive and review

On an hour-long drive, we tested v14.1.7 and tested its new capabilities, which are mostly overall performance and smoothness fixes rather than integrations of new features that are unknown to routine FSD users.

Published

on

tesla interior operating on full self driving
Credit: TESLARATI

Tesla started rolling out its Full Self-Driving (Supervised) v14.1.7 suite last night to owners, and there are several improvements to note within the new update that are at least the start of fixes to highly-mentioned issues.

On an hour-long drive, we tested v14.1.7 and tested its new capabilities, which are mostly overall performance and smoothness fixes rather than integrations of new features that are unknown to routine FSD users. However, there are a handful of shortcomings that are still present within the suite, which are not something that will be fixed within the span of a single update.

For what it is, Full Self-Driving does an excellent job of navigating — once you get it on its correct path. Our issues tend to be confined to navigation, routing, and the decision-making process that has to do with the way the car wants to get you to your destination. There were five things that happened on our first drive with v14.1.7 that are worth mentioning. The full drive will be available at the bottom of this article.

Navigation and Routing Still Seems to Be a Major Challenge

In past content, we’ve discussed the issues with routing and navigation, and how a Tesla chooses its path. Most noticeably, these issues occur in the same areas; for me, it’s my local Supercharger. My 2026 Model Y with AI4 continues to pick less-than-optimal routes out of the Supercharger, and in this instance, it actually chose to turn down a road, pull over, and give me the wheel, essentially asking, “Hey, can you get me on the right track here?”

This is still my biggest bone to pick with FSD, even more so than some of the bonehead moves it’s made in tougher scenarios (mostly parking lots with very limited visibility due to shrubs being planted in the worst possible locations). It’s rare that it happens, but this particular Supercharger has been a true thorn in the side of my Tesla.

This is not an issue that is confined to v14.1.7, or even v14 in general. Unfortunately, it is an issue that has persisted throughout my ownership experience, as well as during Demo Drives.

Stuttering and Hesitation at Intersections was Non-Existent

There was some confusion regarding my language in a recent article where I stated Tesla is confronting the issues that have been reported regarding the “stabbing” with braking.

“Tesla began the v14.1.4 launch last night, which included minor improvements and addressed brake-stabbing issues many owners have reported. In my personal experience, the stabbing has been awful on v14.1.3, and is a major concern.

However, many things have improved, and only a couple of minor issues have been recurring. Many of the issues v13 addressed are no longer an issue, so Tesla has made significant progress.”
It has undoubtedly improved, but it is not resolved.

With that being said, I did not feel a single example of hesitation, stabbing, or stuttering at a single intersection or instance when it has been present in the past. CEO Elon Musk said it would be fixed with v14.2, so it seems like Tesla is well on its way to resolving it.

Proper Handling of Crosswalks

It’s crazy how many people still do not stop for pedestrians at clearly-marked crosswalks. I had two instances of it happen during the drive, with FSD stopping for those pedestrians both times.

Human drivers did not stop either time:

Handled Merging onto a Highway with an Inconsiderate Driver Well

Routinely, drivers will get over into the left lane, if they are able, to allow merging traffic to safely enter the freeway. It does not always happen this way, and it’s not required by law.

Not exclusive to v14.1.7, as many past iterations would have done this as well, but it was nice to watch the vehicle slow down to let that traffic pass. It then entered the freeway safely, and the entire maneuver was well done.

Took an Appropriate Move with Oncoming Foot Traffic and Debris in a Tight Alleyway

This was probably the most on-edge I was during the drive because: 1) FSD chose to take an unnecessary alleyway, and 2) there was a box and oncoming pedestrians.

The car was aware of everything that was going on. In order to avoid the box, it would have had to turn toward the pedestrians, and in order to avoid the pedestrians, it would have had to turn into the box.

It chose to wait patiently, and after the pedestrians were past the car, FSD chose to proceed.

Closing Thoughts

Overall, we’re very impressed with v14.1.7, and we think this is Tesla’s best iteration of the FSD suite yet, as it should be since it’s the newest version available. Tesla’s attention to detail regarding the brake stabbing is really well done, and it seems evident that a complete fix is on its way.

Other than the navigation issue at the very beginning, which was not an intervention, at least in my opinion, this was a really successful drive.

Continue Reading

Elon Musk

Elon Musk debunks report claiming xAI raised $15 billion in funding round

xAI also responded with what appeared to be an automated reply, stating, “Legacy Media Lies.”

Published

on

Credit: xAI

Elon Musk has debunked a report claiming his AI startup xAI had raised $15 billion from a funding round. Reports of the alleged funding round were initially reported by CNBC, which cited sources reportedly familiar with the matter.

CNBC’s report

The CNBC story cited unnamed sources that claimed that the new capital injection would help fund GPUs that xAI needs to train its large language model, Grok. The news outlet noted that following the funding round, xAI was valued at $200 billion. 

Artificial intelligence startups have been raising funds from investors as of late. OpenAI raised $6.6 billion in October, valuing the startup at a staggering $500 billion. Reuters also reported last month that OpenAI was preparing for an IPO with a valuation of $1 trillion. Elon Musk’s xAI is looking to catch up and disrupt OpenAI, as well as its large language model, ChatGPT, which has become ubiquitous.

Elon Musk and xAI’s responses

In his response on X, Elon Musk simply stated that the CNBC story was “false.” He did not, however, explain if the whole premise of the publication’s article was fallacious, or if only parts of it were inaccurate. 

Amusingly enough, xAI also issued a response when asked about the matter by Reuters, which also reported on the story. The artificial intelligence startup responded with what appeared to be an automated reply, which read, “Legacy Media Lies.”

Advertisement

xAI, founded in July 2023 as an alternative to OpenAI and Anthropic, has aggressively built out infrastructure to support its flagship products, including Grok and its recently launched Grokipedia platform. The company is developing its Colossus supercomputer in Memphis, which is heralded as one of the world’s largest supercomputer clusters.

Continue Reading

News

Tesla reportedly testing Apple CarPlay integration: report

Citing insiders reportedly familiar with the matter, Bloomberg News claimed that CarPlay is being trialed by the EV maker internally.

Published

on

Credit: Tesla

Tesla is reportedly testing Apple’s CarPlay software for its vehicles, marking a major shift after years of resisting the tech giant’s ecosystem. 

Citing insiders reportedly familiar with the matter, Bloomberg News claimed that CarPlay is being trialed by the EV maker internally. The move could help Tesla gain more market share, as surveys have shown many buyers consider CarPlay as an essential feature when choosing a car.

Not the usual CarPlay experience

Bloomberg claimed that Tesla’s tests involve a rather unique way to integrate CarPlay. Instead of replacing the vehicle’s entire infotainment display, Tesla’s integration will reportedly feature a CarPlay window on the infotainment system. This limited approach will ensure that Tesla’s own software, such as Full Self-Driving’s visuals, remains dominant. 

The feature is expected to support wireless connectivity as well, bringing Tesla in line with other luxury automakers that already offer CarPlay. While plans remain fluid and may change before public release, the publication’s sources claimed that the rollout could happen within months. 

A change of heart

Tesla has been reluctant to grant Apple access to its in-car systems, partly due to Elon Musk’s past criticism of the tech giant’s App Store policies and its poaching of Tesla engineers during the failed Apple Car project. Tesla’s in-house software is also deemed by numerous owners as a superior option to CarPlay, thanks to its sleek design and rich feature set.

Advertisement

With Apple’s retreat from building cars and Elon Musk’s relationship with Apple for X and Grok, however, the CEO’s stance on the tech giant seems to be improving. Overall, Tesla’s potential CarPlay integration would likely be appreciated by owners, as a McKinsey & Co. survey last year found that roughly one-third of buyers considered the lack of such systems a deal-breaker.

Continue Reading

Trending