John Berry

@aniccia.bsky.social

983 Followers 202 Following

Changes in data collection Under the 2018 regulations, AVs were only required to provide crash reporting and disengagement reports to DMV for vehicles under a testing permit. AV companies with a deployment permit were not required to provide crash data or disengagement reports to DMV (crash data was still reported to DMV despite this, and under federal regulations, AV companies were also required to report crash data regardless of the state permit type). Under the new regulations, crash data is required to be submitted to DMV regardless of the permit type and in the same format as required by the federal government. If the federal government revokes its requirement to report crash data, AV companies will still be required to submit the crash report using the same format. AVs will no longer be required to report disengagement reports. “Disengagement” meant a deactivation of the autonomous mode when a failure of the autonomous technology is detected or when the safe operation of the vehicle requires that the autonomous vehicle test driver disengage the autonomous mode and take immediate manual control of the vehicle, or in the case of driverless vehicles, when the safety of the vehicle, the occupants of the vehicle, or the public requires that the autonomous technology be deactivated. Instead of disengagement reports, AVs will now be required to report vehicle immobilization data, braking events, dynamic driving task performance system failures, and total vehicle miles traveled. These reports will be required for vehicles with a testing or deployment permit, except for the breaking events, which must only be reported for vehicles with a testing permit. “Vehicle immobilization” means a stop on a public road in an active travel lane when the autonomous vehicle operating in a driverless configuration cannot continue the dynamic driving task and must be retrieved or requires the vehicle to be driven by a human driver at the scene or a remote driver. Vehicle immobilization…
Details on Dot’s Phased Rollout DoorDash’s deployment in Fremont is subject to an encroachment permit, ensuring compliance with municipal code and public safety standards. Based on DoorDash’s experience with autonomous delivery in other cities, they have a standardized Operating Plan and Incidence Response Procedure, and will have speed limitations. The current encroachment permit would extend for approximately one year, through March 2027. The initial service area includes the Downtown/City Center, Centerville, and Irvington areas of Fremont. Dot’s primary travel corridors are proposed to be Fremont Boulevard, Walnut Avenue, Mowry Avenue, Stevenson Boulevard, and Paseo Padre Parkway (see map). Phase 1A: DoorDash would only operate up to 3 robots for community engagement, testing and demonstration purposes, during which robots are chaperoned by local operators. Phase 1B: Based on the experiences and feedback from Phase 1A, an amended permit would be issued by Public Works to allow up to 30 robots to operate autonomously within the Service Area and with the capability to be operated remotely as needed. Phase 1B Primary Routes: Walnut Ave, Fremont Blvd, Mowry Ave, Stevenson Blvd, Paseo Padre Pkwy Phase 2: Continued ongoing operations and expansion of service would be subject to a separate review and approval process.
emilymbender on twitter: And now we are squarely in the ML techno-solutionism danger zone: It's established that it would be beneficial to have something that can do X with only Y input, but not that it's actually possible to do X with only Y input. 8:56 AM · Apr 6, 2022
My latest profile, which could have been titled Maxxed Out. What it’s like on the frontier of AI with @saranormous and her team at Conviction, who are very much in the thick of it.
“These robo taxis are going to be game-changing in reducing the number of vehicle miles traveled on our roads,” said Commissioner Moses Leib Duewel of District 9. Duewel said the robotaxis could provide travelers more alternatives to individually driven cars, which he saw as consistent with transit-oriented development.
r/waymo 19m ago u/onmytermsonly: Trusted Testers: Please Report Issues to the CPUC If you’re a Trusted Tester riding Ojai and have experienced any driving issues, safety concerns, door problems, or other complaints, please report them to the CPUC, not just through the Waymo app. Waymo is moving quickly to get Ojai approved for paid public service. Personally, the driving still feels worse than the Jaguar, and I’ve had multiple door problems. Reporting issues to the CPUC can help ensure Ojai isn’t approved for paid public rides until these problems are addressed.
A lot has happened this year. Our Zoox Explorers program launched in San Francisco, we expanded our public service in Las Vegas, rolled out crew service for our team in Austin and Miami, began testing in Dallas and Phoenix, partnered with Uber, and kicked off manufacturing our production-intent robotaxi. Thank you for following along on our journey.
Tatsuhiko Miyagawa @miyagawa on x: Waymo entered the wrong way and got stuck on a walkway causing total chaos on Bryant and 2nd SF
Chris Bonelli @BonelliSays on x: No, Gemini in Waymo does not allow riders to log in to their own Gemini accounts. 12:27 PM · Jul 29, 2026
Medrano says he became the sole operational manager of the Houston programme by mid-2024, after which Tesla roughly doubled his workload from 15 vehicles and operators to 38, spread across three round-the-clock shifts. He characterises this in the complaint as a “dangerous 38:1 operator-to-manager ratio,” far in excess of Tesla’s own “mandated 15:1 safety baseline.” The complaint also notes that other test cities had multiple safety leads while Houston had only Medrano to audit camera footage, run weekly ride-alongs, and investigate incidents across a fleet running continuously. The strain, Medrano says, led directly to a “breakdown in safety oversight and extreme exhaustion.” Test drivers, for their part, worked 60-80 hour weeks and stayed on-call through weekends, while Medrano describes his own state as “trying not to lose my absolute mind, from not sleeping or eating correctly.” The situation culminated in late March: on the 21st, he sent an SOS requesting time off; on the 30th, one of the test vehicles struck a member of the public. Medrano says he was so sleep-deprived when the emergency call came in that he “processed the phone call while physically asleep” and gave apparently unsafe guidance, later reporting no recollection of the exchange.
NHTSA ID Number: 26E035000 Manufacturer Waymo LLC Components ELECTRICAL SYSTEM Potential Number of Units Affected: 3871 Summary Waymo LLC (Waymo) is recalling certain 5th Generation Automated Driving Systems (ADS). The software may allow the vehicle to enter a closed freeway construction zone and continue driving at speed. Remedy Beginning June 16, 2026 Waymo updated the ADS software to detect when the vehicle is in and to avoid entering construction zones, free of charge. Waymo resumed vehicle operations on freeway June 25, 2026.
DMV Statement on Cruise LLC Suspension October 24, 2023 The California Department of Motor Vehicles today issued the following statement on the immediate suspension of Cruise LLC’s deployment and driverless testing permits: Public safety remains the California DMV’s top priority, and the department’s autonomous vehicle regulations provide a framework to facilitate the safe testing and deployment of this technology on California public roads. When there is an unreasonable risk to public safety, the DMV can immediately suspend or revoke permits. There is no set time for a suspension. The California DMV today notified Cruise that the department is suspending Cruise’s autonomous vehicle deployment and driverless testing permits, effective immediately. The DMV has provided Cruise with the steps needed to apply to reinstate its suspended permits, which the DMV will not approve until the company has fulfilled the requirements to the department’s satisfaction. This decision does not impact the company’s permit for testing with a safety driver. Today’s suspensions are based on the following: 13 CCR §228.20 (b) (6) – Based upon the performance of the vehicles, the Department determines the manufacturer’s vehicles are not safe for the public’s operation. 13 CCR §228.20 (b) (3) – The manufacturer has misrepresented any information related to safety of the autonomous technology of its vehicles. 13 CCR §227.42 (b) (5) – Any act or omission of the manufacturer or one of its agents, employees, contractors, or designees which the department finds makes the conduct of autonomous vehicle testing on public roads by the manufacturer an unreasonable risk to the public. 13 CCR §227.42 (c) – The department shall immediately suspend or revoke the Manufacturer’s Testing Permit or a Manufacturer’s Testing Permit – Driverless Vehicles if a manufacturer is engaging in a practice in such a manner that immediate suspension is required for the safety of persons on a public road.
Mullin’s legislation would require the National Highway Traffic Safety Administration, NHTSA, to establish minimum safety standards and protocols for how AV operators work with local public safety personnel. It would require AV companies to provide standardized emergency response protocols for first responders and create a 24-hour hotline for officials to communicate directly with AV companies during autonomous vehicle incidents. It would also direct NHTSA to establish a way for public officials to issue notices that digitally fence off certain areas for self-driven cars during an emergency.
Reddit post headline: Ojai's in Phoenix no longer free starting 7/29