Given AP2 runs a lowered frame rate and cropped camera images due to processing limits, it seems reasonable that they would not reduce available processing capability further by including speed limit NN code.
HW3 has much more capability, but speed limit detection is not a gating feature for FSD.
I respectfully disagree. Around where I live speed limits change often and when a 45mph road becomes 35 mph, and FSD drives at 45 mph or the +5offset I've set, then we are doing 50mph on a stretch that is actually 35 mph after the limit change.
And yes, we can argue the driver is responsible, etc., etc., but apart from eventual actual FSD, what FSD features offer now is to reduce the workload for the driver. Reliably knowing the last posted speed limit the car saw would be a more useful FSD feature for me than the current implementation of stop signs and traffic signals.
Since FSD inherently uses the speed limit as a basis for setting the speed, I'm inclined to believe that sooner or later they will really need to figure out a way to offer speed limit sign recognition.
Also, I know Tesla and MobileEye had a not so pleasant falling out but the good news is this is no longer between Tesla and MobileEye but Tesla and Intel. Hopefully they can work something out to roll this feature out. I'm thinking of a nice and tidy cross licensing agreement for each other's patents.
The nuclear option would be to move to quash this BS speed limit sign recognition patent altogether. MobileEye/Intel can't be allowed to essentially collect a tax for any vehicle that reads speed limits as required by law.
Last edited: