Ouster's new digital Lidar – 128 beams, ultra-wide view
ouster.com
ouster.com
Lidar uses very short pulses and very low power and is very safe even en masse.
If it's not visible I'm not sure that your eye will react quickly enough to prevent damage.
Due to optical aberration wavelengths outside of visible range don't get focused the same way as visible light. This means that the energy is spread over larger area.
Also, both UV and IR light is absorbed in a different way. UV tends to be absorbed much faster than visible light so that little of it reaches the retina while for IR opposite is true, the eye is more translucent to IR and only a portion of it is absorbed at retina and a lot of it tends to pass through it.
What it means is that, while a source of visible light is very well focused on the retina and absorbed in very small volume of retina cells, UV and IR are spread over larger area and then large part of it is absorbed somewhere else.
Still it doesn't mean IR or UV beams aren't dangerous. It is just that you can't directly compare beams by their power.
The way I understand it the main danger is that, since people may not see the IR or UV beam very well, there might be no involuntary response to close the eye.
Thank you to all involved.
If anyone can point me to the generalized best studies for safety margins and laser energy, please post links -- it's pretty relevant to a lot of AR designs to use laser projectors, and it is of course relevant to the lidar self driving cars at question.
I wonder how much we have to blame ITAR restrictions on >1555nm lasers for things like this not being more eye-safe on a by-wavelength basis.
I tried looking up information about this (restriction details, otherwise feasible uses beyond that wavelength, etc) but it's hard for an outsider to quickly make sense of. Any chance you could elaborate?
The main section on lasers starts on page 47. The rules are very complicated. See 6A995 d and f.
Lasers are also covered in other sections like 6A205. (I'm amused by Raman shifters being covered-- they're literally just pressurized tubes with hydrogen and mirrors at the end-- I can't imagine anyone qualified to use one couldn't have one fabricated pretty much anywhere).
I'm concerned once these become more prevalent on all cars or whatever else we stick these on. Curious if there's any studies on if it affects our eyes in anyway.
Unless those heat lamps that also produce visible light damage the eye, I don't see how 865nm lidar could do it if the power is low.
I’d be absolutely shocked if biological systems were somehow different.
However, when there are many 865 nm lidars around, each one gets focused to a different spot in your retina, so it is not any more likely to cause damage than a single lidar. Thanks to the low power of the Ouster lidar, it is Class 1 eye-safe at any distance.
If there were a hundred high-power 1550 nm lidars all pointed at the surface of your eyeball, however, I wonder if it would be more likely to cause damage?
> The OS2 lidar sensor: a long-range sensor with up to 128 lines of resolution
> Two new 32 channel sensors: both an OS0 and OS2 version
> Price: Starts at $16,000 with volume discounts available
I would LOVE to get my hands on this tech. Maybe in 5-10 years when the price comes down to commodity level for hackers to play around with. :-)
Since LIDARs impact airflow over the top of a car, is there a way to make LIDARs less spherical and more triangular or elliptical? How would that impact the scans and can that impact be corrected/recalibrated mathematically?
Also, Ouster runs a sponsorship program that gives deeply discounted or free sensors to cool projects. If you have a cool idea, shoot me an email: derek.frome at ouster dot io
This is very nice, if I only I had a cool project, I just have lukewarm ones!
[1] blensor.org
Does it support Kinect v1 and changing the orientation using the built-in motors?
I also have a few projects using photogrammetry reconstruction of convention booths using 2D images. I've been interested in adding in lidar/pointcloud cameras...
https://www.bhphotovideo.com/c/product/1453431-REG/lg_hf80la...
it's 1080p of resolution in lighting from two angles at 60 fps for like ~100-200 W. if you had some good cameras and some clever and fast software you could use this thing to illuminate anything you need to know about -- a high frequency light probe. i don't think you need coherent light at all or phase control, you'd just like timing control so you can strobe between left and right lights and use the variation to better characterize objects.
whole system seems doable in budgets of ~$8k hardware (total guess...)
Alas, the price of these devices has to come down at least one order of magnitude. Maybe even two. Still, I am really thankful that other companies (since Tesla has no interest in it) are considering and further developing LIDAR.
Tesla cars have radar which can see through any weather condition and detect transparent surfaces, invisible to LIDAR.
I'm curious why there is such an apparently long delay?
Like I said I was just speculating about why OP specifically mentioned 10-100ms. the light does indeed travel pretty quickly (although, as anybody in the radar/lidar industry will tell you, not nearly quickly enough!), however the round trip time is just the minimum latency you have to eat to get any information about your target. Once you have light coming back, you need to integrate for some about of time to achieve your desired SNR. That time could be very small, or it could be infinite if there are no photons coming back. Let's randomly say that you're using a RADAR with a Tx bandwidth situated such that the round trip time is 1us, and that your target range is s.t. the beat frequency of the return is 1kHz. Your job is to estimate that frequency, so you have to observe the waveform (by integrating samples for an FFT, typically) for at least one cycle of the RF wavelength. That would require that you wait 1us for the light to fly, and then wait another 1ms for the RF to cycle once. So your measurement latency is ~1ms. Now that's not 100ms, but perhaps you need more than one cycle to give a good estimate of the frequency, and then even more because the target is faint and there aren't many photons coming back. You could possibly arrive at some much higher number, like 10-100ms.
I'm not sure if that was OP's point, but that's all I'm saying ;-)
I think Google's own unit has 8 stored returns.
Simply depends on what wavelength of light you use.
Water-absorbing frequencies are nice because the atmosphere then shields most light, giving you nice SNR from your laser illumination. But better sensors could work around this, using other frequencies that can 'see' through fog.
It's certainly a technological limitation of current systems, but it's not an inherent limitation.
A $100k fully autonomous taxi would print money over its service life (right now they have remote safety drivers on standby).
The question is how quickly they can expand their currently tiny geofenced area.
Just because LIDAR doesn't make sense for the Model 3 today, doesn't mean it should be entirely discounted.
This is single unit pricing. Volume discounts apply. Still work to do to get this in every honda civic, but it is possible with our technology.
Lots of things could fix this, less beam divergence, custom signals processing on multiple returns. But out of the box, it’s this statement does not hold true.
For vehicle applications specifically probably worth looking into what they use on autonomous vehicles at mine sites imagine that tech probably useful in agriculture. For example Pilbara here in Australia large autonomous fleets in very dusty conditions.
-4f (-20c) is cold, the cabin of the car is heated to well above that. Just heat the lidar as well.
Even automotive cameras have built in heaters to allow them to operate lower than -20C. Nothing preventing adding the same functionality to our sensors.
This couldn't be further from the truth. You can design the VCSEL cavity and top and bottom mirrors for peak efficiency at any temp, including very high temps. I wonder what we did...
Compared to the side emitter diode lasers used in legacy spinning lidar, VCSELS are cheaper, more efficient, more reliable, longer life, and better quality light sources to boot.
VCSELs have a smaller current aperture and the current density is higher than in an edge emitting laser. As the reliability is a function of the junction temperature and the current density, VCSELs operating at high temperatures have significantly reduced lifetime compared to an edge emitting device due to the high current density.
See for example slide 5 which shows how lifetime scales as a function of temperature and current density. For high reliability your devices need to have low current density.
http://www.ieee802.org/3/NGAUTO/public/adhoc/Kropp_NGAUTO_03...
From a pure temperature point of view mines are very easy with a known operating temperature and low fluctuations.
The bigger issue is hot weather; electronics and lasers work well (often more efficiently) at cold temps, and the electrical power running through them self-heats the components. The problem arises when the environment is already hot, and the components still self-heat. This is a particularly large problem for LiDAR, where lasers are very sensitive to temperature and typically use some sort of thermoelectric controller to keep the laser itself at a precise constant temperature. But these thermoelectric devices are inefficient at cooling and lose control (go into thermal runaway) when things get too hot. Automotive component thermal specs (AEC-Q100) require operation (and start-up) at -40C up to anywhere from 70-150C depending on grade. Ouster's -10/-20C to 50C range actually relies on an external base heatsink being used, which they never picture and makes the sensor significantly heavier and larger. These sensors are a far cry from being ready for automotive use.
We didn't claim these were auto rated parts... that being said, our temp spec is in line with the industry, and we're dead set* on reaching auto temp spec in a future iteration of the product.
Our shock, vibe and ingress specs are far better than the competition and pass most auto specs already though. Ruggedness like this was unheard of in spinning lidar even two years ago.
*I believe our internal thermal design group is "cultofthelavapeople at ouster dot io".
I'm getting ready to start a hobby project that involves scanning the interior surfaces of a house. Ideally the accuracy would be at least 1/16" (1.5mm), including any scan-stitching required because the sensor had to be moved around.
I've seen a few promising products, but none stands out as a perfect match.
Working on time-of-flight Stereo camera in my spare time. Few centimeter error is very normal. It was shocking at the beginning, but I now understand why bin picking is still hard task.
Perhaps my Google-Fu is weak today, but I'm only finding research / military projects.
https://www.boschtools.com/us/en/boschtools-ocs/laser-measur...
They have 1-2mm accuracy and quite good precision, particularly if your environment is stable (temperature, movement, lighting). These modules use an interferometry approach rather than time of flight to achieve their accuracy.
Several of them have a Bluetooth interface which you could reverse-engineer. The work then would be creating a turret to rotate the unit around a known centerpoint and take a bunch of samples. It'd be slow, but it works.
There are also a bunch of modules available on Alibaba for a few tens of dollars that have serial interfaces and seem to have similar performance - they often have 10s of Hz sample rates, so you could speed up scanning quite a lot. They exhibit similar accuracy to the boxed units I've bought, but require you to be comfortable with things like SPI and soldering.
Angular accuracy 18” Range accuracy 1.0 mm + 10 ppm 3D point accuracy 1.9 mm @ 10 m 2.9 mm @ 20 m 5.3 mm @ 40 m
(disclaimer: I work for Leica)
Lidar sensors can interfere with each other, and a certain industry-standard company is famous for having terrible problems with this issue, but there are engineering solutions to this problem. FMCW is a popular choice, and gives the benefit of providing instantaneous velocity readings. Of course, due to the Heisenberg uncertainty principle, this means you also get worse distance estimation. There are other ways to engineer around the interference problem as well.
https://www.laserfocusworld.com/home/article/16556322/lasers...
> Lidar sensors can interfere with each other
Then it's not really like 20 cameras looking at the same object. Mostly due to the fact that cameras are passive observers and not really emitting much. And if they do, it's light and it won't really affect the others because they all benefit from it (within reason).
I'm reasonably certain that such issues will still appear in productive use in the future but will get fixed at the time, not in labs today.
A good lidar sensor won't have issues with interference.
Maybe I can add a little color to my original comment this way: most lidar sensors today, including some very expensive ones from supposedly reputable vendors, are not very good. In my experience, it is more often a manufacturing problem than a design problem (this varies more by company than it does by technology).
a) Have identical laser wavelength. Not just '905nm' or '1550nm', but _precisely_ the same wavelength. This is very hard to do even if you try.
b) Have a coincident beam path. Again, this needs to be very precisely aligned.
c) Have an overlapping coherence area. This is a bit technical, but it is a higher bar than just having spots spatially overlapping.
d) Have coherent+matching phase fronts at the detector. Again this is a fairly technical subject these properties vary along the beam path, and transversely. This also vary in time, temperature and many other things. The source lidar is able to 'interfere' with itself (in other words, get a signal), because it compensates for all of these effects with a local copy of the outgoing laser light. Other lidars' outgoing beams will in general, even for 100 cars, not be 'synced up' in this way.
Moreover, those conditions are just the intrinsic interference rejection properties of coherent lidars. Layered on top of that is that two lidars need to be using the same type of modulation, bullseye each other as they scan around the FOV, and provide enough photons to actually contribute to the signal. Then, if you satisfy all of those prerequisites, the interfering lidar also needs to overcome any heuristic/algorithmic rejection of spurious signals. Finally, if all of those conditions match up and you get a signal to punch through, and it's strong enough to over come the true signal, and you can't tell that it's an erroneous signal, then it will result on one bad/missing point in a frame of thousands of points, present for one frame.
You're correct, however, that there is a saturation issue. If you just DOS the photo diodes with photons you can potentially prevent any signals from getting through. But again, this isn't super easy to do. The detectors will almost certainly be balanced, not single ended, and AC coupled. So you really have to blast the photo diode, effectively bringing it up to it's damage threshold so it is just flooded with current and can't do anything, and/or just breaks. The raw laser light doesn't do much, both because the DC signal is rejected and because the balanced detectors will reject common mode signals (clearly you know this already). You also have the same issue with needing to shine into a very narrow field of view, at the right time, for long enough to matter.
Also balanced detectors have something called common mode rejection. This is not infinite. In high volume applications it’s difficult for this to be >25dB but you can buy some devices >35dB.
Given that Lidar dynamic range is ~100dB you will definitely see the DC. I’ve not thought about this too much but it seems like an issue for the AGC as your demodulator won’t be bothered by it.
Certainly the balanced detectors will have finite CMRR. In general you definitely have to make a good detector but it doesn't need to reject to 100dBc. A photodiode might have 100dB of dynamic range, but most likely your RF front end does not, and more importantly for most applications you will be dominated by photon shot noise, so you don't need to push common mode signals all the way to your electronic noise floor. 35dB of rejection works wonders.
As someone outside of the industry, what's the company that has problems with interference?
This isn't how the Heisenberg uncertainty principle works. For macroscopic objects, the effects are completely dwarfed by other phenomenon. Keep in mind that Planck's constant is 10^{-33} meters.
[0] https://en.wikipedia.org/wiki/Uncertainty_principle#Signal_p...
But in summary, the uncertainty principle as encountered in quantum mechanics has ~nothing to do with a trade off between range accuracy and range uncertainty. It's possible that it could come into play in a very detailed treatment of FMCW lidar SNR, in the context of counting return photons, but also not generally necessary there. The time-frequency uncertainty plays a role in that the range and velocity resolution both get better the longer you stare at a signal. So for a given amount of reflected light, at a given range/velocity, there is a fundamental lower bound to how long you must integrate to a) get a signal at all and b) achieve a desired precision.
He and Dr. Marcolli have a bunch of interesting stuff on their websites if you like this sort of stuff.
The underlying math is the same, and there's a principle of complementarity that describes other pairs of quantities that need to be traded against one another.
This is subject to the Birthday Paradox, right?
There's a good explanation in the post about what we mean by digital lidar, but the tl;dr version is we use silicon CMOS chips for lasers and detectors vs analog components like side emitting lasers and APDs used by legacy lidar providers.
Solid state is a bit of a buzzword, and most "solid state" lidar sensors actually have small, delicate moving parts inside. Solid state sensors are aimed primarily at consumer vehicles, which are still many years away.
The benefit is (at least in theory) easier integration into the vehicle fascia and (again, in theory) higher reliability vs legacy spinning lidar, which are quite unreliable in the real world.
Ouster's digital lidar sensors are much more reliable than the legacy analog spinning lidar sensors, and much more compact - and therefore easier to integrate.
IOW, no one is sure if it actually will
We make a point of this because legacy spinning lidar is unreliable. But it's unreliable because of the analog design, not because spinning is inherently unreliable.
I realize a solid state lidar may be a very challenging prospect but it would be a huge selling point!
Some transceivers have a FIT rate of ~300FIT so if that’s the case your rel will only be 3 years.