I've encountered a number of misclassified roads in Richmond.
NoVa too. At least part of Fairfax County Parkway here is treated as a non-divided road, when there is a grass median between the lanes.
You can install our site as a web app on your iOS device by utilizing the Add to Home Screen feature in Safari. Please see this thread for more details on this.
Note: This feature may not be available in some browsers.
I've encountered a number of misclassified roads in Richmond.
Please explain...Consider holding off, as 7.1 removes many autosteer and TACC features.
I've encountered a number of misclassified roads in Richmond.
bwa created a whole thread on this. Let's not rehash that here... Consider the differences in 7.1 and 7.0 when deciding whether to updatePlease explain...
This is a case where "perfect" may be impossible... There are certainly things that could conceivably go wrong: misidentified type of road, misidentified speed limit (I regularly get on 55 sign on Hwy26 read as 85 (YAY) and a 45mph two lane road where the car things we're in a 25 zone (BOOOO)). That said, in general it seems reasonable to assume that detection quality will go up over time. And I think it is hard to argue that what they are trying to do with the limit is reasonable...
I've seen that too, but it was always secondary roads misclassified as highways. Have you seen highways classified as secondary roads?
One of our local owners in Charlotte today had "restricted road" on a divided highway. I asked him to try again and submit a "bug report" via the car when he encounters it again. So it does happen.
NoVa too. At least part of Fairfax County Parkway here is treated as a non-divided road, when there is a grass median between the lanes.
bwa created a whole thread on this. Let's not rehash that here... Consider the differences in 7.1 and 7.0 when deciding whether to update
This looks like a lot of scare material and a lot of it isn't factual from what I've seen. It's pretty one-sided too.
I disagree that it is hard to argue that what they are trying to do is reasonable. I think it is reasonable.
The way the car displays the firmware release notes is actually pretty cool. It takes into account your particular vehicle's options and displays or hides particular parts based on your particular car. Would make it more difficult to do this in a PDF form or something since they'd have to whip one up for every configuration.
I've seen that too, but it was always secondary roads misclassified as highways. Have you seen highways classified as secondary roads?
Update from my awesome service advisor (thanks Karl, if you're reading this!)
"Just got word that they are starting the roll out this afternoon of 7.1 to California. It still may take a day or two for you to get but it is on its way."
Could you clarify, I'm not quite understanding correctly. The first sentence has me thinking you're making a left turn. The second makes me think you're using auto lane change.
Tesla is saying that right now, while Auto Steer is in beta, it is not safe for the software to be used on non-divided highways at all, and that we shouldn't do it. Even so, they are allowing it, with the limitation that the car can't go in excess of 5 MPH over the speed limit, and steer on its own, without the driver also engaging the accelerator pedal. That seems to me to be a pretty fair amount of leniency, considering Tesla is saying the system shouldn't be used under these conditions at all yet.
If you think 5 MPH over the speed limit is too slow to be safe, there's a simple answer: steer the car!
Awesome news!I was just at Burlingame talking to Andrew, the excellent advisor there. My car's touchscreen froze up and went blank yesterday (with reboots not helping) and they had to push a new firmware update to it after entering the diagnostic mode. Alas, Andrew could only push 7.0, 2.9.77 - he did indicate that California cars will start receiving 7.1 OTA in the next couple of days and to ping him for a specific push to my car if it doesn't come around.
But if they did that (make a PDF), I could print it out (yes, on *paper* which is way easier on the eyes, or my eyes anyway) and read it somewhere other than sitting in my car, in a more comfortable and appropriate reading position.
I agree that configuration-specific release notes are cool. They could dynamically generate a PDF for your car (as opposed to my car with different configuration) because they know all the options of every car.
Try that in Oregon with its weird speed signs: http://media.katu.com/images/110513_speed_limit_65_mph_sign.jpgUsing 7.1 for several hours yesterday and today on several different roads here in Virginia there were no misclassifications, even handling a road that changes from two lanes to four-lanes divided and then back. All speed limit readings were also correct.
Update from my awesome service advisor (thanks Karl, if you're reading this!)
"Just got word that they are starting the roll out this afternoon of 7.1 to California. It still may take a day or two for you to get but it is on its way."