A Short Introduction to Automotive Lidar Technology
viksnewsletter.com
viksnewsletter.com
I'm surprised that rotating scanners are still used. It's been twenty years since Velodyne built their first one. They work OK, but cost too much. I was expecting flash LIDAR or MEMS mirrors to take over. Continental, the auto parts company, bought the leading flash LIDAR company over a decade ago, but the volume market a big parts company needs never appeared.
Waymo is still using rotating LIDARs even for the little ones at the vehicle corners. Those need less range. There needs to be a cheap, flush-mounted replacement for those things. The location is too vulnerable. Maybe millimeter phased array radar mounted behind Fiberglas body panels. Waymo needs to solve that problem before they do New York.
The LIDAR on top may not be a problem. Insisting that it has to go away to "look like a car" is like insisting that cars had to have the form factor of horse-propelled buggies. Early cars looked like buggies, but that didn't last.
One big advantage of pulsed LIDAR over continuous is that the interference problem between identical units is much less. The duty cycle is tiny. Data from one pulse round trip is collected in less than a microsecond. Just put some randomization in the pulse timing and getting multiple conflicts in a row goes away.
The old Velodyne units were actually susceptible to damage if you left two units running right next to each other. I did hear a proposal at some point for a different but similar unit to use GPS time to sync the rotations of all the units we had live so they wouldn't be pointed at each other, but in practice it seemed to not be a huge issue.
BTW I once gave you guff about continuing to bring up Conti's flash LIDAR, and in retrospect I wish I hadn't, I really enjoy your contributions here.
I thought that was going to be the future, and that technology would get cheap. But it's still expensive to fab such devices.
Most automotive Lidar already operate in a “photon starved regime”, ~200-300 photons per return[0]. If you spread that over the entire scene, your snr drops quickly.
This forces you into 1550nm, and a large detector array and high power laser at 1550nm is extremely expensive.
As for MEMS, it’s been a while but I think FOV/steering angle range , steering speed and even maximum beam power were concerns
EDIT: my Lidar friend Jake reminded me that the appetizer size is also an issue with MEMS- smaller aperture = less light collected = lower SNR
[0] https://www.hamamatsu.com/content/dam/hamamatsu-photonics/si...
Translating: Normally you have a large single sensor per laser, which makes measurements at a very high rate. With flash lidar, you split the sensor up like an image sensor. In a normal image sensor, each pixel can collect light for a long time, but if you do that with lidar you have no distance resolution. The sensor is sitting idle 99% of the time, and you pay in sensitivity and accuracy.
Array sensors, MEMs, and phased arrays all struggle because they're all really good at small-angle differences, while the reason for scanning lidar is large-angle differences. Maybe one day we'll start making curved dies and it'll be easier to have a really wide FOV without needing multiple sensors.
They're even older than that. SICK have been pointing laser range finders into spinning mirrors since about 1995 - albeit mostly for industrial safety systems which can be quite price-insensitive.
There's a few things to know about LIDAR to understand why spinning lasers make sense.
First of all, anything emitting a cone of light encounters "inverse square dropoff" - where moving twice as far away means you get a quarter of the light, per unit area. This is most visible with flash photography at night - but it also applies to LIDARs. And in an automotive application, ideally you want to be able to sense things 100m away. Illuminating a laser spot is much more practical than illuminating everything.
Secondly, whatever light source you use has to be eye-safe. And sure, IR has safety advantages over visible light here - but a light source bright enough to illuminate things at a 100m distance would be very hard to make safe, even with the advantages of IR. As a scanning laser never lingers in one point for long, it can safely be much more intense.
The third thing to know is whatever light source you're using, you're in competition with the sun. Sometimes the sun is low in the sky and directly dazzling your sensors. Other times it's illuminating the same things you want to illuminate. This means you can't make up for a weak light source and inverse-square dropoff with clever signal processing.
And finally, the makers of these cars envisage a future where every single vehicle on the road is using this technology. So there's also a risk of the reflected returns of two different vehicles interfering with one another. Even rotating LIDAR can be vulnerable to it, but flash LIDAR is particularly vulnerable.
Meanwhile, automotive companies aren't scared of moving parts. A car has loads of spinning parts already; they have mastered the art of making spinning things that can keep spinning for thousands of hours.
Almost an understatement.
A typical car wheel hub with a 20-27 inch tire diameter has experienced around 75-100M full rotations by the time it reaches 100K miles.
Meanwhile, the engine probably has revolved ~5-10 times more during the same time.
Costs have dropped dramatically in the past 20 years and continue to do so.
> There needs to be a cheap, flush-mounted replacement for those things.
Why? Corners are the optimal mounting position for maximum visibility. It allows the car to -in-effect- see around corners in ways no centrally mounted sensor can.
> Waymo needs to solve that problem before they do New York.
What? Because of vandalism?
Also, having the sensors stick out from the corners makes the car's collision box and turning radius bigger. That doesn't help in any tight situation, but I imagine that's not that different between e.g. SF and New York. What is different is the sheer volume of cars and pedestrian activity.
Cruise had an accident where another vehicle knocked a pedestrian into a Cruise car, and the pedestrian was dragged. Cruise lost their California DMV autonomous license for that. So there's a good case for full perimeter coverage.
Humans don't have that. The same week as the Cruise incident, a NYPD tow truck dragged a pedestrian some distance because they were in a blind spot for the driver.
Cruise didn't lose the license because the car and/or human operator accidentally dragged a pedestrian (similar to the NYPD Truck). They lost their license because some time after the accident, Cruise employees fully aware of what transpired chose to cover up that part in their report of the accident to the state regulators. The state regulators found it out anyway.
[1] https://waymo.com/blog/2021/12/expanding-our-waymo-one-fleet...
It’s quite funny seeing the number of cars that have bumper skirts in NYC to help minimize damage from inevitable close encounters with other vehicles
https://news.ycombinator.com/item?id=33554679
Lidar obstacle detection algorithm from a Git repo leaked onto Tor
This is a drivable region mapping (obstacle detection) algorithm found in what appears to be a git repo leaked from an autonomous vehicle company in 2017. The repo was available through one or more Tor hidden services for several years.
The lidar code appears to be written for the Velodyne HDL-32E. It operates in a series of stages, each stage refining the output of the previous stage. This algorithm is in the second stage. It is the primary obstacle detection method, with the other methods making only small improvements.
The leaked code uses a column-major matrix of points and it explicitly handles NaNs (the no-return points). We've rewritten it to use a much more cache-efficient row-major matrix layout and a conditional that will ignore the NaN points without explicit testing.
This is an amazingly effective method of obstacle detection, considering its simplicity.
Asking for a friend...
The rating is for you to stick your eyes right up to it for a long period of time and still be fine
The National Highway Traffic Safety Administration (NHTSA) would have been my guess, but I'm not finding much there. They have a spec for LIDAR speed measurement devices, and one for the required sensors in vehicles, but nothing on the the output of said sensors.
> For manufacturers of laser products, the standard of principal importance is the regulation of the Center for Devices and Radiological Health (CDRH), Food and Drug Administration (FDA) which regulates product performance. All laser products sold in the USA since August 1976 must be certified by the manufacturer as meeting certain product performance (safety) standards, and each laser must bear a label indicating compliance with the standard and denoting the laser hazard classification.
https://www.lia.org/resources/laser-safety-information/laser...
https://www.fda.gov/radiation-emitting-products/home-busines...
https://www.fda.gov/about-fda/fda-organization/center-device...
I would like to see crash test dummy style research around vehicular LIDAR
What do I mean by that? lidar sends pulses of light and works out the difference between emission time and arrival time to work out how far the pulse has travelled.
The structured light sensor emits a pattern or dots, and any distortion of that can be used to compute the shape of an object.
[1] https://image-ppubs.uspto.gov/dirsearch-public/print/downloa...
iPhone 12 introduced a lidar sensor in the back.
Also the patent I linked was filed in 2020, after faceID was rolled out.
Is this true tough? Car radars are fixed. I guess a comparable lidar would be fixed too and have n points for n lasers.
A rovolving radar would have continuous resolution around while a lidar samples?
I thought the advantage of lidars were accuracy and being better at measuring heights of objects, where as radars flatten the view.
On boat radars it seems like the radar have really high resolution (can see much further than lidars) but have worse accuracy. I.e. things looks like blobs.
A lidar image at 50+ meters is very sparse.
The design is also flawed as it has to work with cameras anyway. The last thing you want is two systems arguing over what they see.
Sensor fusion is a thing. There are no two systems that “argue with each other”. I can’t believe the same old ignorant tropes are still making rounds.
Because the company has promised that existing Tesla owners would be able to use FSD.
Having to retrofit them to add LiDAR sensors would be cost-prohibitive.
And those don't translate across to the Optimus bot.
And based on what we've seen the results haven't improved enough to put them close to Waymo.
We know this because there have been public presentations about it.
And inventing groundbreaking new tech is so far the domain of academia and large, well funded R&D labs. And almost always shared.
Mercedes Drive Pilot: Uses a lidar (and a dummy unit) up front.
BMW Personal Pilot: Uses a lidar (and a dummy unit) up front
Honda SENSING Elite: Uses 5! lidars
They all use lidar, and some of the placement locations are downright hideous (Mercedes EQS). I think further development will require even more/better sensors, and manufacturers tend to agree on this point.
https://www.youtube.com/watch?v=xK3NcHSH49Q&list=PLVa4b_Vn4g...
Worth checking out, many cars are very bad.
FSD is a versatile level 2 system, but at best a prototype for level 3. If we are talking about prototypes, it has to be compared to prototypes from other manufacturers like this <https://www.youtube.com/watch?v=0uSph0asNsk> fully autonomous system from ... 11 years ago. The reason FSD is available to the average consumer is mostly a matter of philosophy, not technology.
That is hyperbole at best. I've test driven a Tesla with FSD and it worked flawlessly, such that I would have been perfectly safe taking my eyes off the road. Of course one test drive is not sufficient data to say one should trust the system all the time, but you are making the claim that it is never trustworthy which isn't true.
I have driven a number of level 2 cars on the motorway and almost all of them can do extended zero-intervention driving, but that does not make them safe. The failure rate compared to humans is still sky high.
Multiple independent FSD tests have shown that you need to take over several times an hour to avoid dangerous or illegal situations <https://electrek.co/2024/09/26/tesla-full-self-driving-third...>. The number will be lower on a motorway and you will sometimes have time to correct even if you are not looking, but the number of failures is still significant. If you take your eyes off the road, it is only a matter of time before you end up in a ditch.
I stand by my statement. The system is _never_ trustworthy enough to take your eyes off the road.
Since then, the consensus has been that without lidar, the systems would not meet safety standards. For example, the cars need to be able to detect fairly flat objects, such as pallets that have fallen onto the road, which are very difficult to see optically, especially in difficult lighting conditions. For this reason, and because the technology has come down in price, virtually everyone except Tesla, which is developing advanced driving systems, is using lidar.
This development is nearly a decade old. It is for this reason, combined with the overwhelming amount of Musk-related nonsense, that I objected so strongly.
If the goal is to make roads safer. Aiming for cheap is good, it means aiming for more people who can afford that safer car. If it's not safer than humans, it should not be on the road in the first place.
That "some kind of image processing unit" in humans has an awful lot of compute power and software.
If you remove $100k of sensors but have to add $200k of compute to run more advanced computer vision software, then it's a bad tradeoff to use only cameras, even if in theory that software is possible.
And yeah, as you mention, cameras don't really have the same level of range our eyes have and computers don't operate in the same way.
I think more practically cars have adding driver assistance feature for a while now - more cameras, blind spot monitoring, ultrasound for parking, lane drift indicators.
It is therefore not unreasonable to assume that adding more sensors is helpful (but even the old adage of more data is better than less would probably say that).
I'm not a fan of the camera-only approach and think Tesla is making a mistake backing it due to path-dependence, but when we're _only_ talking about this is _broadly theoretical_ terms, I don't think they're wrong. The ideal autonomous driving agent is like a perfect monday morning quarterback who gets to look at every failure and say "see, what you should have done here was..." and it seems like it might well both have enough information and be able too see enough cases to meet some desirable standard of safety. In theory. In practice, maybe they just can't get enough accuracy or something.
In certain conditions, yes. Humans drive terribly in dark and low light, something lidar excels in.
There's nothing similar in nature for a reason.
Assuming that all technology should imitate nature is a naive engineering principle. The solution should solve the problem within the given constraints.
Portable, energy efficient, light, doesn't need refined oil, tightly steers...
Boats and aeroplanes are terrible in comparison. They only work due to a huge network of global effort.
And horses don’t need roads like cars do and cars only work thanks to a huge network of global effort. What point are you trying to make? That we abandon planes until we can develop flight as efficient as nature? Abandoning LIDAR until we can develop visual light perception and processing equal to the human eye and brain?
Skimming the Wikipedia article[2], it seems like animals do use time of flight, but also Doppler shifting.
(As a side note, some animals have apparently evolved active countermeasures to echolocation!? It seems obvious in retrospect but incredibly cool.)
There's interesting research into the mechanisms of human echolocation [3], but it was over my head. My impression was that the jury is out as far as the precise mechanisms involved but that there's a lot of evidence to be considered, I'm sure someone with a better background would get more out of it than I did.
(I'm just curious about the mechanism, I agree that LIDAR has natural analogs.)
[1] Speed of sound * 25ms, 25ms being the rule of thumb I've memorized for the minimum interval for two sounds to register as distinct from each other. This is just folk wisdom I've picked up hacking on audio, so perhaps I'm mistaken.
[2] https://en.wikipedia.org/wiki/Animal_echolocation
[3] https://durham-repository.worktribe.com/preview/1375913/1963...
At the consumer end photogrammetry tends to just be so much cheaper that its preferred unless you really need defined accuracy at a high level of detail. Lidar tends to work currently much better in an industrial/professional context because its more accurate. Whether Lidar will make the jump to lower cost / consumer level is the big open question (and basically the same issue as for cars here)
The (supposed) "grave" was roughly human-sized and human-shaped, the ground was concave, sunken in and deepest at the center, and it was encircled with stones that were slightly larger than grapefruit.
The reason I suspect it's a grave is because I stumbled upon a very similar-looking thing at a historical site in Tooele county Utah named Mercur cemetery.
With Lidar I could prove/disprove my grave theory, correct?
There are options but the devices are limited (and the applications too)
Samsung S20 series are the last to have it (And I think the Plus is the best one for it)
Going a little older the Note 10 Plus as well (also an awesome phone)
Of the same vintage there are some other devices. You have to look at the ARCore device list and Ctrl F for "ToF" https://developers.google.com/ar/devices
As for applications that can take advantage of the ARCore depth mapping there's RTAB-Map and 3D Live Scanner
https://github.com/introlab/rtabmap/releases/tag/0.21.4 (You'd want the android30 build)
https://github.com/lvonasek/3DLiveScanner/releases/tag/v2022
RTAB-Map is more fleshed out, but has a bit of a learning curve. By far my preferred way of capturing a scan. Be sure to set the values up a little as the defaults are fairly reserved.
3DLiveScanner is more a shoot and done. You capture and it exports all in one with minimal settings to tweak. This was my go to forever before realizing RTAB-Map had builds that worked. It's very capabale for that it is and can get some really good scans setting the res to 2 or 1 cm.
Sample from the S20 Plus https://sketchfab.com/3d-models/polygonal-printer-f2855acc08...
https://sketchfab.com/3d-models/truck-in-the-bush-c2f9c1842e...
https://sketchfab.com/3d-models/3doggo-and-a-catscan-79f1f12...
Note 10 Plus was a big rougher but I don't know if I had found the size setting at that point https://sketchfab.com/3d-models/house-dd80af1455c74874951953...
As far as I'm aware there's nothing on the Android side slated to contain a ToF depth sensor.
Note: If you have a decent Android at the moment, ARCore by itself with dual cameras does surprisingly well for what it is.
Both of those applications will still do live on device scanning with only RGB cameras. 3DLiveScanner will just work if you want to try it.
RTAB-Map you have to go to Settings > Mapping > check Depth from Motion and then on the main screen very first item make sure ARCore NDK is set as the driver (See note above about tweaking the capture settings). The live scan will look a bit rough but if you capture as much detail as you can and let it process, results turn out much better after the processing.
[1] https://www.forbes.com/sites/bradtempleton/2024/10/30/waymo-...
If someone starts attacking safety systems physically I would expect they will get quite a bit of jail time.
Like fooling vending machines to give you soda. Nothing 'my teenage friend' lost sleep over.
We’re in the regime of throwing rocks at a freeway from a bridge to cutting brake lines as a prank. The attack surface here isn’t new and isn’t difficult to think through. Someone who can’t is going to be equally dangerous, machine or man.
I agree, as a former ECU programmer, though. I am terrified of drive by wire.
More like making the Google computer do silly things.
More comparable would be the prank of tying some soda tin cans in a string to the exhaust etc, in how I believe my scapegoat kids would see it.
I worked as a reaserch engineer at a uni playing with a 16 beam Velodyne when those were fancy.
Put it on a car for a demo day, drawing the dots in 3d and marking obstacles red, and during sun set there was artifacts with no obvious way to filter out.
Strangely, I was never able to recreate this. I think was some specific athmospheric condition.