Connect with us

News

SpaceX aborts third Starship static fire attempt minutes before ignition

Signified by large, sustained venting, Starship SN9 aborted its third static fire attempt late on January 12th. (NASASpaceflight - bocachicagal)

Published

on

Perhaps just two or so minutes away from ignition, SpaceX Starship prototype SN9 aborted its third triple-Raptor static fire attempt late into the test window on January 12th

Already extended from 5 pm CST (UTC-6) to 8 pm CST, SpaceX only really started clearing the test facilities near the original end of the window and began loading its second fully-assembled Starship with liquid oxygen and methane propellant around 7 or 7:30 pm. At 7:58 pm, a local sheriff sounded a police siren to warn any local residents or workers of an imminent test – needed in the event of an explosion (“overpressure event”), which could turn shatter glass windows and pose a general hazard.

Now a well-worn, familiar process for unofficial Starship followers, the siren serves (however imprecisely) as an approximate T-10 minute marker for any kind of hazardous testing. Hoping to rectify two prior unsuccessful static fire attempts, Starship SN9 may have made it just 2-3 minutes away from a second ignition before an unknown issue caused SpaceX ground controllers or Starship itself to trigger an abort.

Rearing its head in the form of a large, simultaneous vent releasing pressure from Starship SN9’s methane and oxygen tanks, aborts are an equally familiar event for those that have followed along for the last year or two. Starships may have taken some spectacular leaps forward in 2020, but the program and the prototypes it is currently producing are still relatively immature and, in other words, not exactly refined, polished final products.

Advertisement
Boca Chica began delivering its first single-weld steel rings in December 2019. (NASASpaceflight – bocachicagal)
Twelve months later, Starship SN8 flew for almost seven minutes without issue, ultimately exploding on impact just 10-20 seconds prior to a planned landing. SN9 rolled to the pad less than two weeks after that. (SpaceX)

In 2020 alone, SpaceX destroyed Starship SN1 during pressure testing, toppled (and destroyed) SN3 with faulty test design, saw SN4 violently explode, and eventually flew Starships SN5, SN6, and SN8 – but not before multiple false-starts, aborts, and repairs. Through that hardware-rich process of trial and error, SpaceX managed to go from completing its first one-piece steel ring to the fully-assembled Starship SN8’s almost completely successful 12.5 km (7.8 mi) launch debut in twelve months.

While that sheer speed has been a huge boon for SpaceX, the company appears to have become more cautious in recent months with the introduction of the first full-height Starships – presumably each representing a more substantial investment and thus warranting additional risk-aversion. At the same time, Starship is clearly an extraordinarily complex launch vehicle and that complexity only grows as the program progresses, producing more and more complex prototypes that require equivalently complex testing.

Starship SN8 spent almost two months at the launch pad gradually completing several crucial tests before SpaceX ultimately cleared the rocket to attempt the program’s first high-altitude launch on December 11th. As of January 12th, Starship SN9 has been at the pad for three weeks. Meanwhile, Starship SN10 is practically ready to begin testing and SN11 could be made ready just a few weeks after that.

Starship SN9’s next (fourth) static fire attempt is now expected no earlier than Wednesday, January 13th, though that could quickly change depending on the severity of the problem that caused Tuesday’s abort.

Advertisement

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 reveals huge Cybercab detail in new guide for First Responders

Published

on

Credit: Tesla

Tesla revealed a major new Cybercab detail in a guide it released for First Responders, showing new territory in its beliefs and intentions for the ride-hailing-focused vehicle that entered production in April.

The First Responders Guide is released to give fire departments, paramedics, and other emergency personnel the proper guidance on what to do in the event of an accident, entrapment, or other situation that would require immediate attention.

On one of the pages of the First Responders Guide, Tesla revealed a stark detail about the Cybercab, which could help personnel enter the vehicle more easily in case of an emergency.

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

It shows Tesla has no intention of releasing any Cybercab units that were initially proposed for ride-hailing services for the general public with any manual controls, meaning a steering wheel or pedals:

“A Cybercab equipped with steering wheel, brake pedal, and an acceleration pedal is typically an engineering or test vehicle, and operates at SAE Level 2 autonomy. Cybercab is not typically equipped with a steering wheel or acceleration and brake pedals.”

This is a major development for those who continue to believe Tesla planned to release the Cybercab with any sort of manual controls so that passengers could take over if needed. However, when Tesla started manufacturing production versions of the Cybercab in Giga Texas earlier this year, they were spotted without a steering wheel or pedals.

It essentially confirms the company has no intentions of bringing manual controls to the car’s production versions. Some have argued that the likelihood of Tesla having something

There still are some Cybercab units out there with a steering wheel and pedals, and as Tesla said, these cars are engineering or test vehicles, which have Safety Monitors on board to help the car out of a precarious situation or emergency.

Continue Reading

News

Tesla Full Self-Driving v14 ‘Lite’ Release Notes: new capabilities and features

Published

on

(Credit: Megan Gale/Twitter)

Tesla released the Full Self-Driving v14 ‘Lite’ suite to owners of Hardware 3 or AI3 vehicles today, adding several new features to the vehicles that were once believed to be capable of unsupervised self-driving.

Now, Tesla has released this modified suite to older Tesla vehicles, adding plenty of new features and capabilities.

Here are the full release notes for the suite:

  • Distilled the intelligence from HW4 V14 into HW3. This allows HW3 to directly learn how to handle scenarios using HW4 V14 as a guide. This process unlocks the improvements that have been made to HW4 including Reinforcement Learning (RL) and offline models for HW3.
  • Improved both proactive and reactive responsiveness across a wide variety of categories including navigation handling, merges and forks, pedestrian interactions, traffic lights, and vehicle cut-in scenarios.
  • Improved general comfort in nominal scenarios through fewer false slowdowns, smoother steering and more consistent lane centering.
  • Introduced parking, unparking, and reversing capabilities.
  • Added Arrival Options for you to select where FSD should park: in a Parking Lot, on the Street, in a Driveway, or at the Curbside.
  • Speed Profiles are now available at all times, to further customize driving style preference.

These improvements, according to Tesla’s Head of AI, Ashok Elluswamy, help distill the driving behavior from AI4’s v14 series into both the camera and compute configurations of AI3.

Tesla Full Self-Driving v14 ‘Lite’ for older cars finally gets released

He added:

“It includes destination options and speed profiles on city roads, but more importantly significantly improved safety. We hope you’ll enjoy it, once the build ships wide.”

Tesla will continue to roll out the v14 Lite suite more widely in the coming weeks, the company said.

Continue Reading

News

Tesla Full Self-Driving v14 ‘Lite’ for older cars finally gets released

Published

on

tesla model 3 model y
Credit: Tesla Inc.

Tesla has finally released its Full Self-Driving v14 ‘Lite’ suite for older cars that equip the Hardware 3 or AI 3 chip, which have not been able to handle the newest versions of the company’s driver assistance software.

Tesla officially started releasing the v14 Lite suite to owners in the Early Access Program last night. The company’s Head of AI, Ashok Elluswamy, said that the rollout will continue over the next few weeks. The build distills the driving behavior from AI4’s v14 series into both the camera and compute configurations of an AI3 car.

It also includes a variety of new features that were available to AI4 cars running v14, including:

  • Start Self-Driving from Park
  • Arrival and Parking Options
  • Speed Profiles

The release is highly anticipated because those owners with AI3 vehicles were early adopters into the FSD platform and were promised that their cars would be capable of achieving Full Self-Driving.

However, Tesla CEO Elon Musk admitted during the company’s recent Q1 Earnings Call that these vehicles would not be capable of achieving unsupervised Full Self-Driving, which is what Tesla had originally said.

Owners were not pleased with this answer, or the idea that their commitment to buying the suite outright for thousands of dollars would not yield the ability to drive without operating the car. Tesla gave some solutions for this, including a discount on a new car, or an upgrade to an AI4 or AI5 self-driving computer and new, upgraded cameras.

Tesla owners do not seem pleased with these options, as they require giving the company more money.

Nevertheless, it is important to note that Tesla came through for owners here by releasing v14 Lite before the end of Q2, something it had promised owners during the previous Earnings Call. Tesla has had trouble keeping up with timelines, but this is a big achievement for the team.

Continue Reading