just verified that I have 2.3 version. Wonder if this is hung up in Apple approval cycle or Tesla not yet submitting.
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.
This used to be true, but not anymore. If you set the cruise to 48mph for instance, then tap the "all up" position, it will go to 50mph, then 55mph. Didn't used to--but does now.
Before the 6.2 update, I thought you couldn't change driver profiles (from one person to another) unless you were in park. I remember having to put the car in park to switch the driver profiles so my brother could see what changes.
Now, on 2.183 , a driver was able to change the driver profile from one user to another while going 50 km. Is that a bug? I would think it unsafe.
Odd, I'm on 6.2-2.4.213 and I was in the car yesterday on the freeway and did not notice this behavior for cruise control. I'm pretty sure actually that it still does the +/- 5mph thing, and not increment to the nearest 5mph. I'll go out tonight and try this behavior specifically and report back.
Looks like there must be a difference for TACC vs. pre-TACC. My "classic" 2013 Model S running .213 still works the way it always has - it goes +/- 5 mph relative to the speed you started - no stopping at even 5 mph increments.
The cruise control on my car operates the way it always has -- adds or subtracts 5mph from the current cruise control setting. It does not increment or decrement to the nearest 5mph, as the manual specifies it should. I submitted a bug report.
Geeze, I sure hope they keep this this way for older cars... the "stop at a 5mph increment" is so messed up to me. I want the controls to do specific and predictable things. If I do a "full up" I want to know that's going to add exactly 5mph to my current speed, not 1,2,3 or 4 mph depending upon my current speed to the next 5mph increment, and then +5 more from there. What a misguided idea this is. IMHO.
Geeze, I sure hope they keep this this way for older cars... the "stop at a 5mph increment" is so messed up to me. I want the controls to do specific and predictable things. If I do a "full up" I want to know that's going to add exactly 5mph to my current speed, not 1,2,3 or 4 mph depending upon my current speed to the next 5mph increment, and then +5 more from there. What a misguided idea this is. IMHO.
Just for completeness:I verified this on my way home today. With TACC set to 43 mph, one full upward deflection changed the set speed to 45mph. Doing it again changed it to 50mph.
I am on the .188 flavor of 6.2. I for one prefer this behavior. (I think most people tend to go 5 mph over the limit, though I have no evidence to back this up--just based on how fast people around me tend to travel).
Agree.Geeze, I sure hope they keep this this way for older cars... the "stop at a 5mph increment" is so messed up to me. I want the controls to do specific and predictable things. If I do a "full up" I want to know that's going to add exactly 5mph to my current speed, not 1,2,3 or 4 mph depending upon my current speed to the next 5mph increment, and then +5 more from there. What a misguided idea this is. IMHO.
Just for completeness:
[1] What speed did TACC think was the local speed limit?
[2] What is your offset for TACC relative to speed limit (in the settings)?
I was on an SJ to LA and back trip last weekend. In my early P85, CC goes up or down I 5mph increments only when full pushed. It doesn't stop at multiples of 5 on full push. I'm on .188. My biggest issue always has been that often it thinks I pushed it short once and then full once whenever I try to do a single full push. I end up with a 6mph change... Maybe I'm doing it pretty slow, but I've tried playing with it and that doesn't seem to matter.
Just woke up to the Tesla app notification that a software update is available.
Only had the car for a week--first timer.
Anyone download already?
what version are you currently on?
OK. I just ask because it might just be a minor update to bring you in line with the latest. I personally haven't gotten a notification, but I don't typically get SW updates early either.