Cruise recalls entire fleet of cars after San Francisco crash

Table Of Content

• GM's Cruise is recalling 950 robotaxis after pedestrian collision
• Letters to the Editor: Automate everything? Driverless taxis mean more jobs taken from humans
• GM recalls all of its Cruise robotaxis to install improved software
• In another setback, Cruise updates software on 950 driverless cars to fix its ‘Collision Detection Subsystem’
• A software update was deployed to fix the issue that caused the San Francisco incident.
• Business
• GM Cruise recalls 300 robotaxis after crash involving bus

"We would need to see that this kind of AI system -- that works based on the experience -- is similar to the way a human behaves. The more experience a person has, the more, the better a person can react to the new scenarios," said Moayed Daneshyari. Cruise is now taking steps to get its robotaxis back on the road, after California's DMV forced the company to pause driverless rides in October. Fast forward to the beginning of April, and the National Highway Traffic Safety Administration (NHTSA) posted a recall report that is directly related to last month’s accident in San Francisco. Cruise spokesperson Hannah Lindow said in a written statement that the software issue has been resolved. “Cruise AVs are even better equipped to prevent this singular, exceptional event,” Lindow wrote.

GM recalls driverless Cruise vehicles after one of them dragged a pedestrian - CBS News

GM recalls driverless Cruise vehicles after one of them dragged a pedestrian.

Posted: Wed, 08 Nov 2023 08:00:00 GMT [source]

GM's Cruise is recalling 950 robotaxis after pedestrian collision

“Cruise determined that the collision was caused by an issue related to prediction of the unique movements of articulated vehicles in rare circumstances,” the company said in documents. The DMV and others have accused Cruise of not initially sharing all video footage of the accident, but the robotaxi operator pushed back - saying it disclosed the full video to state and federal officials. At issue is the Oct. 2 crash where a jaywalking pedestrian stepped into a busy intersection in San Francisco and was hit by a human-driven car. The pedestrian rolled onto the windshield for a few moments before she was flung into the path of the driverless car.

Letters to the Editor: Automate everything? Driverless taxis mean more jobs taken from humans

The “articulated” two-section bus slowed as it was leaving the stop and was hit by the self-driving vehicle. The company said in documents posted by the National Highway Traffic Safety Administration on Wednesday that with the updated software, Cruise vehicles will remain stationary should a similar incident occur in the future. The collision, along with Cruise's disclosures around it, led to California regulators stripping the company of its permits to operate driverless vehicles in the state, unless there is a human safety driver aboard. Previously, the company had grounded all of its driverless operations following the Oct. 2 collision during which a pedestrian was thrown into the path of the Cruise robotaxi by a human driver in a different car who hit her first. This recall happens just five weeks after a person was first thrown in front of a cruise vehicle during a hit-and-run crash and dragged 20 feet by the driverless vehicle as it attempted to move out of traffic.

GM recalls all of its Cruise robotaxis to install improved software

The company said in documents posted by U.S. safety regulators on Wednesday that with the updated software, Cruise vehicles will remain stationary should a similar incident occur in the future. NHTSA opened an investigation Oct. 16 into four reports that Cruise vehicles may not exercise proper caution around pedestrians. The complaints involved vehicles operating autonomously and “encroaching on pedestrians present in or entering roadways, including pedestrian crosswalks in the proximity of the intended travel path of the vehicles,” the agency said.

The Oct. 2 crash prompted Cruise to suspend driverless operations nationwide after California regulators found that its cars posed a danger to public safety. The state’s Department of Motor Vehicles revoked the license for Cruise, which was transporting passengers without human drivers throughout San Francisco. In March, the self-driving developer Pony.ai recalled three self-driving vehicles after it found that a software error caused the system to shut down unexpectedly while its vehicles were in motion. Cruise says in documents posted by NHTSA that it already has updated software in test vehicles that are being supervised by human safety drivers. While the department of motor vehicles did not elaborate on specific reasons for its suspension of Cruise’s license, the agency accused Cruise of misrepresenting safety information about the autonomous technology in its vehicles. The revocation followed a series of incidents that heightened concerns about the hazards and inconveniences caused by Cruise’s robotaxis.

A software update was deployed to fix the issue that caused the San Francisco incident.

Footage of the crash initially shared by Cruise with The Washington Post, other media outlets and the California Department of Motor Vehicles showed the driverless car stop as soon as it made contact with the pedestrian. "As our software continues to improve, it is likely we will file additional recalls to inform both NHTSA and the public of updates to enhance safety across our fleet." In certain rare circumstances, the Cruise ADS operating with the Subject ADS Software could inaccurately predict the movement of “articulated” vehicles. In such a circumstance, the ADS could inaccurately determine that the obstructed front section of the vehicle was continuing to move forward, and that the rear section of the vehicle would continue to move forward with the front section, even if the vehicle was decelerating. GM recently paused production of the Origin, a fully autonomous vehicle designed for Cruise to carry multiple passengers. The company is expected to resume production at a Detroit-area factory once Cruise resumes autonomous ride-hailing.

The company said no other crashes have happened due to the problem and that the same thing won’t happen again after the update. The company says in documents sent to the National Highway Traffic Safety Administration that it did the software update on March 25. In a statement Wednesday, the GM unit said that it did the recall even though it determined that a similar crash with a risk of serious injury could happen again every 10 million to 100 million miles without the update. In a statement on Wednesday, the GM unit said that it did the recall even though it determined that a similar crash with a risk of serious injury could happen again every 10m to 100m miles without the update. Except this code tells the cars how to behave without a driver, and they're trained based on the data from previous experiences. Around three weeks ago, a driverless Bolt rear-ended a San Francisco Muni bus, which resulted in some light damage for the Chevy and little to no damage for the much bigger municipal bus.

‘Sesame Street’ writers reach tentative contract deal, averting strike

While the California DMV didn’t elaborate on specific reasons for its suspension of Cruise’s license, the agency accused Cruise of misrepresenting safety information about the autonomous technology in its vehicles. While the Department of Motor Vehicles didn't elaborate on specific reasons for its suspension of Cruise's license, the agency accused Cruise of misrepresenting safety information about the autonomous technology in its vehicles. The revocation followed a series of incidents that heightened concerns about the hazards and inconveniences caused by Cruise's robotaxis.

The NHTSA says that on March 25, Cruise released a new software update for all the affected vehicles, which solved the problem. Cruise, which is General Motors’ autonomous taxi division, has recalled 300 of its self-driving Chevrolet Bolts for a fix that caused an embarrassing accident last month in San Francisco. The company said no other crashes have happened due to the problem and that the same thing won't happen again after the update. Cruise said it did the recall to be transparent and add to public understanding of the crash.

But it then pulled to the right to get out of traffic, pulling the person about 20ft (six meters) forward. One of Cruise’s driverless cars dragged the pedestrian, and the company initially misrepresented what happened during the Oct. 2 crash. DETROIT (AP) — General Motors’ Cruise autonomous vehicle unit has recalled 300 robotaxis to update software after one of them rear-ended a municipal bus in San Francisco. The Cruise initially stopped but still hit the person, and then pulled to the right to get out of traffic, dragging the person about 20 feet.

The company said it will “deploy the remedy” to its driverless fleet before it resumes driverless operations, although it is unclear when that will be. The company said in documents posted by U.S. safety regulators on Wednesday that with the updated software, Cruise vehicles will now remain stationary in similar cases. Cruise says in government documents posted Friday that the robotaxi inaccurately predicted how the bus would move as it pulled out of a bus stop on March 23. The "articulated" two-section bus slowed as it was leaving the stop and was hit by the self-driving vehicle. Cruise said in its NHTSA filing that the software update improves its self-driving software’s predictions, especially in situations like the one that led to the crash. The company said it has determined that if the vehicle involved in the June 3 incident had been running the current software, no crash would have occurred.

The state's Department of Motor Vehicles revoked the license for Cruise, which was transporting passengers without human drivers throughout San Francisco. The Oct. 2 crash forced Cruise to suspend driverless operations nationwide after California regulators found that its cars posed a danger to public safety. The California Department of Motor Vehicles revoked the license for Cruise, which was transporting passengers without human drivers throughout San Francisco. The state’s Department of Motor Vehicles revoked the license for Cruise, which was transporting passengers without human drivers throughout San Francisco.

Two other companies, Alphabet subsidiary Waymo and the robotic delivery company Nuro, have also received permits to deploy commercial self-driving services in California. In San Francisco, Waymo offers select members of the public paid rides with an employee in the car to monitor its technology. According to the Cruise filing with the NHTSA on Nov. 7, following the collision, Cruise found defects within its automated driving system software, specifically pertaining to its "Collision Detection Subsystem." Rival Waymo, which is owned by Google parent company Alphabet, continues to operate driverless fleets in and beyond California.

The DMV and others have accused Cruise of not initially sharing all video footage of the accident, but the robotaxi operator pushed back — saying it disclosed the full video to state and federal officials. The DMV and others have accused Cruise of not initially sharing all video footage of the accident, but the robotaxi operator pushed back – saying it disclosed the full video to state and federal officials. Cruise, the autonomous vehicle venture owned by General Motors, has issued a recall effecting 950 of its robotaxis following a pedestrian collision in San Francisco last month. “This issue could occur after a collision with a pedestrian positioned low on the ground in the path of the AV,” the company said.

Right now, Cruise’s service operates in 70 percent of the city between 10 pm and 6 am, except during rain or fog. The Detroit automaker had been expecting annual revenue of $1 billion from Cruise by 2025 — a big jump from the $106 million in revenue last year. The Detroit automaker had been expecting annual revenue of $1bn from Cruise by 2025 – a big jump from the $106m in revenue last year. A computer science assistant professor at Cal State East Bay says this recall means fixing code, just like an iPhone update.