Skip to main content

Lyft ramps up self-driving program

A year ago, Lyft submitted a report to the California Department of Motor Vehicles that summed up its 2018 autonomous vehicle testing activity in a single, short paragraph.

“Lyft Inc. did not operate any vehicles in autonomous mode on California public roads during the reporting period,” the letter read. “As such, Lyft Inc. has no autonomous mode disengagements to report.”

The 2019 data tells a different story. Lyft had 19 autonomous vehicles testing on public roads in California in 2019, according to data released earlier this week by the CA DMV. Those 19 vehicles, which operated during the reporting period of December 2018 to November 2019, drove nearly 43,000 miles in autonomous mode.

The report is the latest sign that Lyft is trying to ramp up its self-driving vehicle program known as Level 5. 

The CA DMV, the agency that regulates autonomous vehicle testing on public roads in the state, requires companies to submit an annual report that includes data such as total AV miles driven and number of vehicles. It also requires companies to report “disengagements,” a term that describes each time a self-driving vehicle disengages out of autonomous mode either because its technology failed or a human safety driver took manual control for safety reasons.

That’s still far below established AV developers such as Cruise and Waymo, which accumulated 831,000 and 1.45 million autonomous miles, respectively. And it makes up just a tiny sliver of the total autonomous miles racked up by the 36 companies that tested on public roads in 2019.

The total number of autonomous miles driven in 2019 rose 40%, to more than 2.87 million, thanks largely to a notable uptick in public on-road testing by Baidu, Cruise, Pony.ai, Waymo and Zoox. While the number of companies with testing permits grew to 60 in 2019, the percentage of companies actually testing on public roads fell to about 58%. In 2018, about 62% of the 48 companies that held permits tested on public roads.

Other companies scaled back public testing in California. Some moved public testing outside of California, others retracted due to the high cost. Others said they were opting to place great emphasis on simulation.

Still, the report shows Lyft is doing more than partnering with autonomous vehicle companies like Aptiv. Lyft and Aptiv launched a robotaxi pilot in January 2018 in Las Vegas. The program, which puts Aptiv vehicles on Lyft’s ride-hailing network, surpassed 100,000 rides this month. Human safety drivers are always behind the wheel and the vehicles do not drive autonomously in parking lots and hotel lobby areas.

Lyft’s Level 5 program — a nod to the SAE automated driving level that means the vehicle handles all driving in all conditions — was launched in July 2017. Today, Level 5 employs more than 400 employees in the U.S., Munich and London.

Testing on public roads in California began in November 2018 with a pilot program in Palo Alto that provided rides to Lyft employees in Palo Alto. The pilot provided on-demand rides set on fixed routes such as traveling between the Lyft office and Caltrain.

Since then, the company has expanded the scope and geography of the pilot. By late 2019, Lyft was driving four times more autonomous miles per quarter than it was six months prior.

Lyft is also testing on a dedicated closed-course track in East Palo Alto that it opened in November 2019. The company told TechCrunch it uses this facility, which can be changed to include intersections, traffic lights and merges, as test software prior to putting its vehicles on public roads.



from TechCrunch https://ift.tt/2I1Xh5J
Labels:

Comments

Post a Comment

Popular posts from this blog

How To Play Doom – And More – On An NES

Doom was a breakthrough game for its time, and became so popular that now it’s essentially the “Banana For Scale” of hardware hacking. Doom has been ported to countless devices, most of which have enough processing ability to run the game natively. Recently, this lineup of Doom-compatible devices expanded to include the NES even though the system definitely doesn’t have enough capability to run it without special help. And if you want your own Doom NES cartridge, this video will show you how to build it . We featured the original build from [TheRasteri] a while back which goes into details about how it’s possible to run such a resource-intensive game on a comparatively weak system. You just have to enter the cheat code “RASPI”. After all the heavy lifting is done, it’s time to put it into a realistic-looking cartridge. To get everything to fit in the donor cartridge, first the ICs in the cartridge were removed (except the lockout IC) and replaced with custom ROM chips. Some modifica...
Post a Comment
Read more

Try NopSCADlib for your Next OpenSCAD Project

Most readers of this site are familiar by now with the OpenSCAD 3D modeling software, where you can write code to create 3D models. You may have even used OpenSCAD to output some STL files for your 3D printer. But for years now, [nophead] has been pushing OpenSCAD further than most, creating some complex utility and parts libraries to help with modeling, and a suite of Python scripts that generate printable STLs, laser-ready DXFs, bills of material, and human-readable assembly instructions complete with PNG imagery of exploded-view sub-assemblies. Recently [nophead] tidied all of this OpenSCAD infrastructure up and released it on GitHub as NopSCADlib . You can find out more by browsing through the example projects and README file in the repository, and by reading the announcement blog post on the HydraRaptor blog . Some functionality highlights include: a large parts library full of motors, buttons, smooth rod, et cetera many utility functions to help with chamfers, fillets, precis...
Post a Comment
Read more

The Newbie’s Guide To JTAG

Do you even snarf? If not, it might be because you haven’t mastered the basics of JTAG and learned how to dump, or snarf, the firmware of an embedded device. This JTAG primer will get you up to snuff on snarfing, and help you build your reverse engineering skills. Whatever your motivation for diving into reverse engineering devices with microcontrollers, JTAG skills are a must, and [Sergio Prado]’s guide will get you going. He starts with a description and brief history of the Joint Test Action Group interface, from its humble beginnings as a PCB testing standard to the de facto standard for testing, debugging, and flashing firmware onto devices. He covers how to locate the JTAG pads – even when they’ve been purposely obfuscated – including the use of brute-force tools like the JTAGulator . Once you’ve got a connection, his tutorial helps you find the firmware in flash memory and snarf it up to a file for inspection, modification, or whatever else you have planned. We always apprec...
Post a Comment
Read more