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.
Weird. It should feel unmistakably faster.
Went to service center today. Was told (the oft cited) 90 minutes. Instead took 2 hours 15 minutes. Used API and perf is still set for P3 . So I guess it didn't "take"? Haven't had a chance yet to do a good power tools run to confirm. Didn't leave SvC until after 5pm. Was commute time traffic so no really sustained accelerations.
I have a few questions:
1) Any guesses as to why sometimes the SvC thinks everything was fine even though it turns out the car was not properly uncorked? They said everything went fine and congratulated me on my uncorking. So obviously they thought it was all good. Wouldn't their equipment show otherwise?
2) Are there any examples here on the board where the API reported perf of P3 but in fact the car WAS uncorked (i.e. the API value wasn't yet updated?). I checked about 6 hours after the supposed uncorking. Didn't know if this get updated right away or if perhaps the vehicle data is only refreshed every 24 hours (or cached for some period of time) or something.
3) How have people who had been told that uncorking did happen convince the SvC that in actuality it didn't 'take'?
Thanks!
To my knowledge all the uncorking that hasn't taken eventually gets resolved. Tesla identified early that they need a good connection to make it work. Also, we know that the firmware has to be reinstalled after the changes in order to implement them. On some occasions the only reason the uncorking hasn't taken has been that the firmware didn't get installed or didn't take. One way to test this is to get Tesla to "push" the latest firmware back out to the car of someone that didn't take. Although unless you are really remote it is probably just easier to revisit the service center.
It might be that the API could report P1 before the firmware install and uncorking was complete, but I don't think the API could report P3 after a successful uncorking.
To my knowledge all the uncorking that hasn't taken eventually gets resolved. Tesla identified early that they need a good connection to make it work. Also, we know that the firmware has to be reinstalled after the changes in order to implement them. On some occasions the only reason the uncorking hasn't taken has been that the firmware didn't get installed or didn't take. One way to test this is to get Tesla to "push" the latest firmware back out to the car of someone that didn't take. Although unless you are really remote it is probably just easier to revisit the service center.
The service center doesn't need to push it but my understanding is that Tesla can "push" it to you to make your car reinstall the latest firmware, possibly saving you a trip to the service center.Also, they don't need to push the latest firmware. If there is no connection, they can simply redeploy the existing firmware.
The service center doesn't need to push it but my understanding is that Tesla can "push" it to you to make your car reinstall the latest firmware, possibly saving you a trip to the service center.
The Ranger is working on my car as I type (I'm not watching fwiw). He pushed the patch to my car early this morning and asked me not to apply it. Because my car is in a parking garage with no connectivity, he's going to move it out and said he only needs his laptop and his phone to complete the process. We'll see how it goes.
Well?
Here is the latest software update that goes in the opposite direction on performanceA software upgrade made this possible.