GM’s Cruise acquires Strobe to drop LiDAR costs for self-driving



Cruise, the self-driving car startup GM acquired last year, has acquired a startup of its own – Strobe, a LiDAR sensor maker that reduces an entire LiDAR array down to just one chip, which Cruise says will be instrumental in helping it reduce the cost of LiDAR on a per vehicle basis by nearly 100 percent.

The cost issue is a big one: LiDAR remains one of the single most expensive components in the autonomous vehicle stack, and it’s a bottleneck not just in terms of cost, but also in terms of manufacturing complexity and performance and reliability over time across all types of weather, as Cruise CEO Kyle Vogt notes in a Medium post announcing the news.

Vogt says that decreasing costs for autonomous vehicles will be key in deploying them across a range of different areas, including in the suburbs and outside of major cities, where currently the economics would make it difficult to deploy something like an autonomous ride hailing service.

Strobe’s LiDAR component

Strobe’s technology offers accurate measurement of both distance and velocity, Vogt says, and combined with radar, can provide information vital to decision-making for self-driving cars. Strobe will bring their team and founders to Cruise, and Cruise will work with both its new engineers and with GM resources to develop LiDAR tech along with GM’s Hughes Research Labs skunkworks team.

Velodyne is currently the industry leader in terms of LiDAR employed in self-driving vehicle technology, but many are trying to improve the cost, form factor and reliability of LiDAR parts. Another startup, Luminar, recently revealed the scale of its own operation, and it’s also announced that it’s working with Toyota Research Institute along with other select partners to add its capabilities to autonomous test vehicles on the road.



Source link

83 Comments
  1. June 23, 2018 | Reply
  2. June 28, 2018 | Reply
  3. July 2, 2018 | Reply
  4. July 2, 2018 | Reply
  5. July 3, 2018 | Reply
  6. July 3, 2018 | Reply
  7. July 3, 2018 | Reply
  8. July 3, 2018 | Reply
  9. July 3, 2018 | Reply
  10. July 4, 2018 | Reply
  11. July 4, 2018 | Reply
  12. July 4, 2018 | Reply
  13. July 4, 2018 | Reply
  14. July 5, 2018 | Reply
  15. July 5, 2018 | Reply
  16. July 6, 2018 | Reply
  17. July 6, 2018 | Reply
  18. July 7, 2018 | Reply
  19. July 7, 2018 | Reply
  20. July 7, 2018 | Reply
  21. July 7, 2018 | Reply
  22. July 9, 2018 | Reply
  23. July 10, 2018 | Reply
  24. July 10, 2018 | Reply
  25. July 10, 2018 | Reply
  26. July 10, 2018 | Reply
  27. July 11, 2018 | Reply
  28. July 11, 2018 | Reply
  29. July 11, 2018 | Reply
  30. July 11, 2018 | Reply
  31. July 13, 2018 | Reply
  32. July 13, 2018 | Reply
  33. July 13, 2018 | Reply
  34. July 13, 2018 | Reply
  35. July 13, 2018 | Reply
  36. July 13, 2018 | Reply
  37. July 14, 2018 | Reply
  38. July 14, 2018 | Reply
  39. July 14, 2018 | Reply
  40. July 16, 2018 | Reply
  41. July 16, 2018 | Reply
  42. July 16, 2018 | Reply
  43. July 16, 2018 | Reply
  44. July 16, 2018 | Reply
  45. July 16, 2018 | Reply
  46. July 17, 2018 | Reply
  47. July 17, 2018 | Reply
  48. July 18, 2018 | Reply
  49. July 18, 2018 | Reply
  50. July 18, 2018 | Reply
  51. July 18, 2018 | Reply
  52. July 18, 2018 | Reply
  53. July 19, 2018 | Reply
  54. July 19, 2018 | Reply
  55. July 19, 2018 | Reply
  56. July 20, 2018 | Reply

Add a Comment

Your email address will not be published. Required fields are marked *

%d bloggers like this: