Connect with us

News

SpaceX ships Raptor to Texas for first Starhopper hover tests after fixing vibration bugs

SpaceX technicians work to install Raptor SN06 on Starhopper, the third time a full-scale engine has been attached to the rocket testbed. (NASASpaceflight - bocachicagal, 07/11/19)

Published

on

After a brisk week of no fewer than three lengthy static fire tests, SpaceX has effectively confirmed that a critical vibration-related fault was solved, delivering the company’s latest completed Raptor engine to Boca Chica, Texas earlier today.

SpaceX technicians are now in the process of installing the engine – believed to be Raptor SN06 – on Starhopper, a low-fidelity prototype meant to act as a sort of flying testbed for Starship technologies and a mobile test stand for Raptor test fires. According to SpaceX CEO Elon Musk, if Raptor SN06 is installed, successfully checks out, and supports Starhopper’s first untethered hover test within the next 3-7 days, he will deliver an updated presentation on SpaceX’s Starhip/Super Heavy launch vehicle and (hopefully) the company’s plans for the Moon and Mars around the end of July.

This Raptor is the third to be installed on Starhopper. The first engine (SN02) was installed in March 2019 and became the first Raptor to ignite as part of a vehicle meant to eventually fly. During a duo of more or less successful test fires, Starhopper strained against its tethers, lifting a few inches off the ground. Although it did technically mark Starhopper’s inaugural hop, Raptor SN02 also suffered damage during the tests that demanded its removal.

Starhopper’s first static fire test with Raptor SN02 occurred on April 3rd, 2019.

As recently noted by observant fans after Musk revealed that SpaceX had been dealing with a “600 Hz” vibration issue, the horn-like noise during shutdown actually happens to be in the 600 Hz range, with an additional spike at 300 Hz a likely sign of an issue with acoustic and/or mechanical resonance. With SN06, SpaceX engineers and test/production technicians have managed to rapidly implement a fix for that undesirable resonance, powering through several successful static fires with durations as high as 80+ seconds, approaching the propellant storage limits of SpaceX’s McGregor test facilities.

Raptor SN04?

Shortly after its static fire tests in Boca Chica, Raptor SN02 was removed. According to a source familiar with the test process, the engine was brought up to McGregor, TX and repaired before SpaceX technicians – urged by CEO Elon Musk – effectively ran the engine until it failed catastrophically. Some two months after its removal (early June), a new Raptor engine – this time believed to be Raptor SN04, effectively an inert test article – was installed on Starhopper for a handful of days.

Advertisement

SN04 was exclusively used to check fitment and verify Raptor’s thrust vector control (TVC) gumball capabilities – quite successfully, by all appearances. A few days after installation, it was removed and shipped elsewhere. Subsequently, Raptor SN05 was tested in McGregor with the hopes that it would be able to support the first Starhopper hover tests, but the vibration issue described by Musk caused damage or at least killed confidence that the engine (a single point of failure on Starhopper) was reliable enough to support hover tests.

Raptor SN06 thus entered our story, arriving at McGregor around July 4th. SpaceX’s world-class team of engineers and technicians demonstrated their famous speed and agility, firing up SN06 less than 24 hours after its arrival. This initial test showed nothing out of order and was followed by no less than 3-4 30-80-second static fire tests, all of which were more or less successful. Per Musk, things were looking good as of July 8th, and Raptor’s July 11th arrival at Boca Chica is a foolproof confirmation that the engine is healthy and ready for the Raptor family’s first true flight.

Starhopper stands stoically as technicians install a new Raptor (SN06) on its thrust structure. If all goes as planned, the unorthodox vehicle could begin hover tests as early as next week (July 15th). (NASASpaceflight – bocachicagal)

Stay tuned for coverage of SpaceX’s imminent Starhopper static fire and hover test campaign.

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 faces Full Self-Driving pushback in EU over ‘speeding’

Published

on

Credit: Tesla

A new report from Reuters claims that a transport authority in Sweden is pushing back against the approval of Tesla’s Full Self-Driving suite because it will travel over speed limits.

The report says the Swedish Transport Administration (TRV) recommends the European Union votes against FSD’s approval. TRV believes it should not be approved until Tesla disables FSD’s ability to speed.

TRV sent a letter to the European Union’s Technical Committee on Motor Vehicles (TCMV), which is set to meet on June 30 to discuss the potential approval of the Tesla FSD suite in the country. Tesla, which has received various approvals in Europe over the past two months, has not provided a comment.

Tesla Full Self-Driving gets first-ever European approval

Teslas operating on FSD do travel over the speed limit, depending on the Speed Profile that is chosen. Drivers have the ability to disengage FSD at any point; Tesla specifically states that those supervising the suite are responsible for its actions.

Let’s cut to the chase: humans operating any vehicle speed almost daily in the United States. Realistically, speed limits in the U.S. are more frequently treated as speed minimums. However, other countries are different, and driving behaviors are less aggressive.

TRV believes that “allowing automated systems to systematically exceed legal speed limits…risks undermining both the legal framework and the expected safety benefits of ​vehicle automation,” the report stated. It’s surprising that Tesla has not received this claim from other countries previously.

This could be a good argument to bring Max Speed back, the setting that previously allowed the driver to choose the absolute fastest the car would travel.

This would still put the responsibility of supervision in the hands of the driver. It would allow the driver to choose whether the car would travel over the speed limit or not, acknowledging that they set the speed, and if they get pulled over, there would be no ability to argue it.

However, it does not seem as if this is something Tesla will do, especially considering many U.S. drivers have requested the feature in an effort to eliminate speeding or at least tone it down. The company has not shown any interest in bringing it back.

Tesla has approvals for FSD in Europe in Estonia, Lithuania, Denmark, the Netherlands, and Belgium.

Continue Reading

Elon Musk

Tesla teases greater Grok FSD integration and ‘Banish’ feature ‘in about 3 months’

Published

on

Credit: Tesla

Tesla is going to let you guide Full Self-Driving with Grok in 3 months, CEO Elon Musk confirmed on X.

The response from Musk, which revealed Tesla plans to allow drivers to effectively control the car and its navigation more explicitly using Grok, puts the feature for about September.

A Tesla owner said that Full Self-Driving is great, but owners should be able to “converse with Grok like we can with an Uber driver.” She then used examples like, “Grok, turn right here,” and “Drop us off right here, we’ll walk due to traffic,” and finally,” Drop at entrance first, then park far away.”

Coincidentally, the final piece of dialogue would also mean features like Banish are potentially on the way soon.

Banish is also referred to as “Reverse Summon,” and would enable the car to self-park while dropping occupants off at their destination.

This would be a great way to improve the overall experience while supervising FSD. Navigation is already a major painpoint that many owners complain about. Manual overrides when a maneuver is requested or canceled (like using the turn signal stalk to override a navigation route), do not always work.

The feature could be especially useful in street parking scenarios in a city, where spots are sometimes tough to come by. Many of us who grab dinner in a more populated area will park a street or two over from wherever we’re going, because sometimes you know that’s the best you will get. If a driver using FSD could say, “Hey Grok, turn right here on Queen St. and park in that open spot on the right,” it could save a lot of confusion FSD might have on its own.

Musk teased that a similar feature was “coming” back in February:

Tesla Full Self-Driving set to get an awesome new feature, Elon Musk says

It is certainly surprising that Tesla is doing it at this point. The company’s more recent moves have been more evident of taking control and inputs away from humans and putting them in the AI’s hands more frequently. The biggest example of this was taking away Max Speed in AI4 cars, giving us Speed Profiles, and not having any input on the fastest speed the car will travel.

Of course, giving navigation preferences to Grok is availble already in Teslas, but not at the drop of a hat. Instead, you can suggest a certain route at the beginning of your drive.

Here’s an example of that from December:

Finally, the original post that Musk responded to mentioned a parking preference after dropping off the occupants, which describes the Banish feature that Tesla has teased for years.

We’re not sure if Musk was responding more to the ability to guide the car with Grok, or whether he also was including Banish in the three-month prediction timeframe.

Continue Reading

News

Tesla Cybercab has one important piece that AI4 cars might need for FSD

Published

on

Credit: @tpgoebel | X

A close-up image of a Cybercab engineering vehicle in Peabody, Massachusetts, reveals a compact triangular side repeater camera housing equipped with an integrated washer mechanism.

This seemingly small hardware addition could prove to be one of the most critical components for achieving reliable, unsupervised Full Self-Driving (FSD) — not just for the dedicated Robotaxi but potentially for existing AI4-equipped vehicles as well.

The washer system’s importance cannot be overstated in Tesla’s vision-only autonomy approach. Cameras are the sole sensory input for the neural networks powering FSD, constantly interpreting the environment for safe navigation. In real-world conditions, however, lenses quickly accumulate rain, snow, mud, dust, or road spray.

Many of us Tesla owners, especially those who deal with any sort of winter weather at all, know the all-too-common alert that pops up when cameras are obstructed:

Even brief obstructions can drop perception confidence, trigger safety disengagements, or force the vehicle to pull over, although these are relatively rare. Instead, most of the time, the camera will need a wipe from the owner next time they stop the car.

But unlike human drivers who can manually clear their view, a Robotaxi operating 24/7 without a steering wheel or mirrors must maintain pristine vision autonomously. The Cybercab’s side repeater washer delivers targeted cleaning bursts precisely where needed for merging, lane changes, and blind-spot monitoring — functions that demand uninterrupted visibility from the external cameras:

This hardware directly tackles a known pain point in current FSD deployments. Owners frequently report camera-related alerts during inclement weather, which is understandable, but needs to be solved for a true autonomous experience.

For a production Robotaxi fleet aiming for high utilization and minimal downtime, robust washer systems represent a foundational reliability upgrade; essentially, they’re a must-have. Early sightings suggest the design may extend to rear cameras as well, creating a comprehensive cleaning architecture that keeps the entire vision suite operational in harsh environments.

Without it, even the most advanced neural nets struggle when their “eyes” are compromised.

What Does This Mean for AI4 Cars?

This Cybercab detail raises timely questions for AI4 cars already on the road. While Hardware 4 delivers superior compute and camera resolution compared to earlier versions, production models typically lack dedicated side and rear washers. Tesla has included them on Model Y robotaxis that it is using in the fleet:

Tesla Robotaxi has a highly-requested hardware feature not available on typical Model Ys

As Tesla refines unsupervised FSD for broader release, the gap in environmental resilience becomes evident. Software improvements can help mitigate issues, but they cannot fully replace physical cleaning in heavy rain or muddy conditions. Analysts and owners increasingly speculate that AI4 vehicles may eventually require similar washer retrofits — or a future AI4.5 variant — to match the Cybercab’s all-weather readiness and support the same level of autonomy.

As testing progresses, the Cybercab’s washer mechanism highlights Tesla’s pragmatic focus on real-world robustness. It may well become the hardware piece that determines how quickly and reliably FSD scales from prototypes to everyday vehicles.

Continue Reading