Each approach comes with different trade-offs suited to different use-cases. In the case of the iPhone rear camera, I believe the approach used is single-frame pulsed Lidar using a VCSEL (vertical cavity surface-emitting laser), a dot-grid diffuser, and SPAD (single photon avalanche diode) CMOS camera.
Basically, a shifting grid of dots at a very specific wavelength is projected outwards from the laser, and an unbelievably, photon-level sensitive camera tuned to that precise wavelength measures how long each dot takes to come back after it's emitted. In this way, Time of Flight can be measured and a precise distance determined.
This system provides incredibly high resolution at a moderate distance (in this case, 5m or so) at a moderate cost.
For a car, this system wouldn't be very plausible due to range, resolution, and output power constraints. The size of laser required to emit a coherent dot matrix which could reflect at a long distance would grow to an extreme degree, the noise floor of the SPAD would eventually render the system useless, and the amount of data required to produce a higher resolution dot cloud would become quite challenging, as these systems generally need to be heavily filtered and sub-sampled, so an enormous amount of input data processing is required to produce a reasonable output.
The main reason that Tesla don't use Lidar is that they decided to bet on optical (IMO, foolish), but the reason they decided to bet on optical is complex and definitely in no small way cost driven. They couldn't just slap an array of iPhone sensors (I believe they're Sony-manufactured) on a Tesla and call it good.
There are several reasons why they would not just add new sensors even if they are in some/all ways superior:
* Tesla special cases different driving situations. This makes sense as a product company seeking to sell consumers on solutions to each situation as a feature but means they need to re-implement each situation individually when the sensors change rather than just swapping out some generic distance detector net. You can observe this from the loss of features when Tesla went full Vision over the last two years.
* Adding new sensors adds new errors which leaves you to chose between ignoring danger conditions present in only one sensor as possible errors or greatly increasing safety stops etc (some of which would be genuine previously undetected dangers). Because of Tesla's engineering culture the prudent second option or a sensible middle ground would be impossible to make since they would fail from a user experience point of view at the first false stop during a demo to the big man and then be forever poisoned (imho).
* Tesla has always been pursuing a full vision only solution on the reasonable assumption that if humans can do it then eventually computers will too. The only disagreement with that strategy is when exactly that will/should be.
There's no way you can argue it was done in good faith when it was an arbitrary transition where some functionality hadn't even been solved yet and was disabled if your car didn't come with ultrasonic sensors. And to add to the comical levels of disregard for buyers, the official advice for finding out if your order would have ultrasonic sensors was: "Look for the 12 sensors on your vehicle", ie you didn't know until you paid and it was a roulette wheel.
You don't know how manufacturing works, especially in a post-COVID world.
Tesla almost certainly couldn't source the ones they were using: That mystical "chip shortage" is a general component shortage.
https://gmauthority.com/blog/2021/12/these-chevy-models-get-...
-
Now it's not like there are no ultrasonic sensors to be had, but they would have had to pay for tooling changes, design verification, assembly changes... easily 10s of millions of dollars for what you're brushing off as "the price of a $10 sensor"
Their options were remove the sensors and be transparent about why, or throw up a smoke screen with idle gibberish about vision was definitely better despite needing to cut features that had been practically solved nearly a decade earlier. Guess which they chose.
> Price was a factor for not using the larger, longer range lidars though since that cost more than planned price of the vehicle ~10 years ago.
Good thing I didn't say or remotely imply that?
Overall I think your type of blustering works better on people not working in the AV field.
No, sorry that cannot be left as is.. I see your arguments but they are pulled of thin air, or is there any source that reasoning actually happened there. If fusion done right, this will never increase but decrease errors.
> they would fail from a user experience point of view at the first false stop during a demo to the big man and then be forever poisoned (imho).
And failing on the first situation that a second sensor set would have clearly prevented can easily be argued the same.. this is a strawman.
I live near Waymo and see the cars all the time - they do have huge things on top but the weather in Santa Monica is also very good. Not sure if I have seen them ever driving in the rain?
At the same time advancements also happen at the multi-model side, not fusing different deep learning outputs afterwards but right in the one model (not judging if that is a good idea... but the steps taking currently seem to get bigger and better).
Lastly, also camera has degraded performance under certain weather conditions.. some even say our eyes can be prone to that! :D
So that's just all the challenges that need to be taken. Yes, humans can drive with their eyes only, but is that perfect? Sometimes we e.g. would also benefit greatly from radar/lidar, as e.g. in dark conditions our judgement of distances is really flawed.
Refresh rate of some of this already aged car lidars was like 10 Hz, good enough I'd say? And it is truly amazing what details one can get out of those when getting close and move around in those point clouds.