News
SpaceX ships Starship’s 200th upgraded Raptor engine
A day after revealing the completion of the 200th Falcon upper stage and Merlin Vacuum engine, SpaceX has announced that it also recently finished building Starship’s 200th upgraded Raptor engine.
Starship – and Raptor, by extension – has yet to reach orbit and is likely years away from scratching the surface of the established success and reliability of the Falcon upper stage and MVac. But compared to MVac, Raptor is more complex, more efficient, more than twice as powerful, experiences far more stress, and is three times younger.
And Raptor 2 isn’t the first version of the engine. Before SpaceX shipped its first Raptor 2 prototype, it manufactured 100 Raptor 1 engines between the start of full-scale testing in February 2018 and July 2021. By late 2021 or early 2022, when Raptor 2 took over, the total number of Raptor 1 engines produced likely reached somewhere between 125 and 150 – impressive but pale in comparison to SpaceX’s Raptor 2 ambitions.
From the start, Raptor 2’s purpose was to make future Raptors easier, faster, and cheaper to manufacture. The ultimate goal is to eventually reduce the cost of Raptor 2 production to $1000 per ton of thrust, or $230,000 at Raptor 2’s current target of 230 tons (~510,000 lbf) of thrust. As of mid-2019, Musk reported that each early Raptor 1 prototype cost “more” than $2 million for what would turn out to be 185 tons of thrust (~$11,000 per ton). It’s not clear if that ever appreciably changed.
In response, SpaceX strived to make Raptor 2 simpler wherever possible, removing a large part of the maze of primary, secondary, and tertiary plumbing. In 2022, CEO Elon Musk confirmed that SpaceX had even removed a complex torch igniter system for Raptor 2’s main combustion chamber. All that simplification made Raptor 2 much easier to build in theory, and SpaceX’s production figures have more than confirmed that theory. Despite those simplifications, SpaceX was also able to boost Raptor 2’s thrust by 25% by sacrificing just 1% of Raptor 1’s efficiency.
Beginning with its first delivery in February 2018, SpaceX produced the first 100 Raptor 1 engines in about 36 months. In the first 11 to 12 months of Raptor 2 production, SpaceX has delivered 200 engines. That translates to at least six times the average throughput, but the true figure is even higher. In June 2019, Musk stated that SpaceX was “aiming [to build a Raptor] engine every 12 hours by end of year.” As is usually the case, that progress took far longer to realize. But in October 2022, a senior NASA Artemis Program official revealed that SpaceX recently achieved sustained production of one Raptor 2 engine per day for a full week.
Such a high rate – likely making Raptor one of the fastest-produced orbital-class rocket engines in history – is required because SpaceX’s next-generation Starship rocket needs a huge amount of engines. The Starship upper stage currently requires three sea-level-optimized Raptors and three vacuum-optimized Raptors, and SpaceX has plans to increase that to nine engines total. Starship’s Super Heavy booster is powered by 33 sea-level Raptors.
Orbital-class versions of Starship and Super Heavy have never flown, let alone demonstrated successful recovery or reuse, so SpaceX has to operate under the assumption that every orbital test flight will consume 39 Raptors. Even after the reuse of Super Heavy boosters or Starships becomes viable, taking significant strain off of Raptor demand, SpaceX wants to manufacture a fleet of hundreds or even thousands of Starships and a similarly massive number of boosters. To outfit that massive fleet, SpaceX would have to mass-produce orbital-class Raptor engines at a scale that’s never been attempted.
But it will likely be years – if not a decade or longer – before SpaceX is in a position to attempt to create that mega-fleet. If the Raptor 2 engines SpaceX is already building are modestly reliable and reusable, and it doesn’t take more than 5-10 orbital test flights to begin reusing Starships and Super Heavy boosters, a production rate of one engine per day is arguably good enough to support the next few years of realistic engine demand.
SpaceX’s first orbital Starship launch attempt could occur as early as December 2022, although Q1 2023 is more likely. SpaceX currently has permission for up to five orbital Starship launches per year out of its Starbase, Texas facilities and will likely try to take full advantage of that with several back-to-back test flights in a period of 6-12 months.
News
Tesla quietly flexes FSD’s reliability amid Waymo blackout in San Francisco
“Tesla Robotaxis were unaffected by the SF power outage,” Musk wrote in his post.
Tesla highlighted its Full Self-Driving (Supervised) system’s robustness this week by sharing dashcam footage of a vehicle in FSD navigating pitch-black San Francisco streets during the city’s widespread power outage.
While Waymo’s robotaxis stalled and caused traffic jams, Tesla’s vision-only approach kept operating seamlessly without remote intervention. Elon Musk amplified the clip, highlighting the contrast between the two systems.
Tesla FSD handles total darkness
The @Tesla_AI account posted a video from a Model Y operating on FSD during San Francisco’s blackout. As could be seen in the video, streetlights, traffic signals, and surrounding illumination were completely out, but the vehicle drove confidently and cautiously, just like a proficient human driver.
Musk reposted the clip, adding context to reports of Waymo vehicles struggling in the same conditions. “Tesla Robotaxis were unaffected by the SF power outage,” Musk wrote in his post.
Musk and the Tesla AI team’s posts highlight the idea that FSD operates a lot like any experienced human driver. Since the system does not rely on a variety of sensors and a complicated symphony of factors, vehicles could technically navigate challenging circumstances as they emerge. This definitely seemed to be the case in San Francisco.
Waymo’s blackout struggles
Waymo faced scrutiny after multiple self-driving Jaguar I-PACE taxis stopped functioning during the blackout, blocking lanes, causing traffic jams, and requiring manual retrieval. Videos shared during the power outage showed fleets of Waymo vehicles just stopping in the middle of the road, seemingly confused about what to do when the lights go out.
In a comment, Waymo stated that its vehicles treat nonfunctional signals as four-way stops, but “the sheer scale of the outage led to instances where vehicles remained stationary longer than usual to confirm the state of the affected intersections. This contributed to traffic friction during the height of the congestion.”
A company spokesperson also shared some thoughts about the incidents. “Yesterday’s power outage was a widespread event that caused gridlock across San Francisco, with non-functioning traffic signals and transit disruptions. While the failure of the utility infrastructure was significant, we are committed to ensuring our technology adjusts to traffic flow during such events,” the Waymo spokesperson stated, adding that it is “focused on rapidly integrating the lessons learned from this event, and are committed to earning and maintaining the trust of the communities we serve every day.”
News
Waymo scrutinized after self-driving taxis cause traffic jams during SF blackout
It’s not farfetched to speculate that it would have been a doomsday scenario for Tesla had FSD behaved this way.
A power outage across San Francisco over the weekend forced numerous Waymo self-driving taxis to stop at darkened intersections and cause traffic blockages in multiple locations across the city. The disruption left riders stranded, frustrated drivers blocked, and city officials stepping in as the Alphabet-owned company temporarily suspended service amid the widespread gridlock.
Needless to say, it would likely have been a doomsday scenario for Tesla had FSD behaved in a similar way, especially if fleets of its robotaxis blocked traffic for numerous drivers.
Power outage halts Waymo fleet
The outage knocked out electricity for tens of thousands of customers, leaving traffic signals dark across large parts of the city, as noted in a report from the New York Times. Waymo vehicles began stopping at intersections and remained stationary for extended periods, seemingly unable to operate. Tow truck operators worked through the night removing immobilized vehicles, while videos circulated online showing Waymos with hazard lights flashing as traffic backed up around them.
Waymo later confirmed that it had paused its Bay Area ride-hailing service after the San Francisco mayor’s office contacted the company about the congestion its vehicles were contributing to. Service began coming back online shortly after 3:30 p.m. local time, though some users still reported being unable to request rides. Waymo maintained that no injuries or accidents were reported during the outage.
Autonomous cars during emergencies
The incident surprised industry observers since autonomous vehicles are designed to function during signal outages and temporary connectivity losses. Waymo stated that its vehicles treat nonfunctional signals as four-way stops, but “the sheer scale of the outage led to instances where vehicles remained stationary longer than usual to confirm the state of the affected intersections. This contributed to traffic friction during the height of the congestion.” Experts suggested the problem may have been linked to the vehicles’ reliance on remote assistance teams, which help resolve complex situations the cars cannot handle independently.
“Yesterday’s power outage was a widespread event that caused gridlock across San Francisco, with non-functioning traffic signals and transit disruptions. While the failure of the utility infrastructure was significant, we are committed to ensuring our technology adjusts to traffic flow during such events,” the Waymo spokesperson stated, adding that it is “focused on rapidly integrating the lessons learned from this event, and are committed to earning and maintaining the trust of the communities we serve every day.”
News
Tesla aims to combat common Full Self-Driving problem with new patent
Tesla writes in the patent that its autonomous and semi-autonomous vehicles are heavily reliant on camera systems to navigate and interact with their environment.
Tesla is aiming to combat a common Full Self-Driving problem with a new patent.
One issue with Tesla’s vision-based approach is that sunlight glare can become a troublesome element of everyday travel. Full Self-Driving is certainly an amazing technology, but there are still things Tesla is aiming to figure out with its development.
Unfortunately, it is extremely difficult to get around this issue, and even humans need ways to combat it when they’re driving, as we commonly use sunglasses or sun visors to give us better visibility.
Cameras obviously do not have these ways to fight sunglare, but a new patent Tesla recently had published aims to fight this through a “glare shield.”
Tesla writes in the patent that its autonomous and semi-autonomous vehicles are heavily reliant on camera systems to navigate and interact with their environment.
The ability to see surroundings is crucial for accurate performance, and glare is one element of interference that has yet to be confronted.
Tesla described the patent, which will utilize “a textured surface composed of an array of micro-cones, or cone-shaped formations, which serve to scatter incident light in various directions, thereby reducing glare and improving camera vision.”
The patent was first spotted by Not a Tesla App.
The design of the micro-cones is the first element of the puzzle to fight the excess glare. The patent says they are “optimized in size, angle, and orientation to minimize Total Hemispherical Reflectance (THR) and reflection penalty, enhancing the camera’s ability to accurately interpret visual data.”
Additionally, there is an electromechanical system for dynamic orientation adjustment, which will allow the micro-cones to move based on the angle of external light sources.
This is not the only thing Tesla is mulling to resolve issues with sunlight glare, as it has also worked on two other ways to combat the problem. One thing the company has discussed is a direct photon count.
CEO Elon Musk said during the Q2 Earnings Call:
“We use an approach which is direct photon count. When you see a processed image, so the image that goes from the sort of photon counter — the silicon photon counter — that then goes through a digital signal processor or image signal processor, that’s normally what happens. And then the image that you see looks all washed out, because if you point the camera at the sun, the post-processing of the photon counting washes things out.”
Future Hardware iterations, like Hardware 5 and Hardware 6, could also integrate better solutions for the sunglare issue, such as neutral density filters or heated lenses, aiming to solve glare more effectively.
Tesla quietly flexes FSD’s reliability amid Waymo blackout in San Francisco
Waymo scrutinized after self-driving taxis cause traffic jams during SF blackout
