I suspect the problem with recognizing 120 km/h sign is that the numbers are too close together to fit the standard North American sign width. The number 2 in the middle takes more real estate than the number 1 in a 110 km/h sign.
But exactly the same realestate at the 0 in 100 so I don't buy that for a second. I can pretty much guarantee it's failing a sanity check somewhere in the code that tells it 120kph isn't a valid speed limit.
- - - Updated - - -
Not sure that's an obvious conclusion by any means; it's a projection of your frustration because they haven't acknowledged your reports.
I think Tesla is not unlike many technology companies with a large user base, where bug reports can frequently come in faster than engineering can deal with them. If your issue isn't fixed right away, it's probably because they've had to triage higher-priority problems, or this is actually harder/riskier to fix than it appears and they don't have a solution yet. No inside knowledge of Tesla here, just an educated guess based on having to make similar hard choices with limited time and resources.
I agree. but that's also why I don't think submitting more bug reports is likely to solve all our problems, and why I won't take a feature that is likely crippled by bugs when I don't think they are likely to do anything about fixing said bugs.
On a side note, I have also never heard of anyone else getting a similar issue resolved. So I'm not holding my breath, or my update.
- - - Updated - - -
Not directed at you specifically, but I don't see why a for-profit fledgling company like Tesla should take cash from their bottom line to pay outside companies for additional free services
You're looking at it all wrong. The outside company should be paying Tesla to make the vehicle capable of using the service, and Tesla has no obligation to provide a free account.
If they've gone to all the work of programming the app for all those services, why not have them in the list on all cars? You don't have to provide an account, leave that up to the owner if they want to use that service. There's zero downside to Tesla if they've already built the app.
- - - Updated - - -
My experience is different. I very seldom have errors here in Alberta (the Coquihalla in BC is a noted exception) and particularly on the unrestricted type roads listed by green1 I have no issues reading signs unless a sign is actually obscured by traffic. Most anomalies I see are in residential areas. I wonder if green1 should have his camera checked.
To clarify, when you are driving around town on a normal day, and you pass speed limit signs, they almost always get displayed immediately on your dash? for all speeds? If that truly is the case, I'll ask Tesla to check my camera, the reason I've dismissed it as a camera issue are 2 fold:
1) Lane marking recognition using the same camera is EXCELLENT, it's as good as my own eyes at seeing the lines (sometimes better) (note, I can still do a better job of inferring where they should be when obscured)
2) When I was briefly in the US 2 months ago it read 100% of speed limit signs accurately, but in Canada it's always been less than 50%, My assumption has been that it's something to do with our signs looking a little different (ie: ours read "maximum" and a number instead of "speed limit" and a number)