Skip to main content

Tesla appears to be actively limiting the performance of their cars - Update: Tesla has confirmed and backed away

Tesla owners have noticed a change in the behavior of their cars, specifically in the performance models such as the P85 and the P90DL, where the performance of the cars doesn't seem to match previous or listed results.

User wk057 has done some pretty extensive reverse engineering, modifications, and looking into the internal systems of the car, including the battery pack. On TeslaMotorsClub what started as a thread about battery pack capacities not matching advertized amounts, rated amount of available energy doesn't even match the car's own reported energy, turned into a thread called Pack Performance and Launch Mode Limits. This thread has kicked off a bit of a firestorm as these performance limits weren't documented or disclosed.

It appears pretty clear that Tesla is counting the number of Launches (done through launch mode), as well as the number of Wide Open Throttle (WoT) events. When those counts go beyond some predefined values the car will reduce the amount of power available in order to protect the drivetrain and ensure long term reliability.

The Drive picked up the story, electrek posted 'Tesla confirms that it limits the power of performance vehicles after too many launches with ‘launch mode’' and people are tweeting to Elon for answers:

I'm hoping Tesla does the right thing for people that purchased the performance upgrades before these limits were disclosed and removes these limits while standing by their warranty.


Update 2016-01-17

It looks like Tesla is going to restore the car's performance with a future software update.

JonMc on TeslaMotorsClub.com posted:
JonMc, Yesterday at 7:41 PM
Hi everyone, 

Based on your input, we have decided to remove all software performance reductions tied to frequent max power usage. These changes will roll out with our next software update (in about three weeks).

We had put these reductions in place to proactively protect the powertrain from wear and tear. Instead, we will monitor the condition of the powertrain and let our customers know if service is needed so that we can take proactive steps, such as by replacing parts if necessary, to maintain the vehicle’s performance.

--Jon


electrek is also covering the response from Tesla inTesla listens to customers and walks back all software performance reductions tied to frequent use of max power and has more details about JonMc.
Labels:

Comments

Post a Comment

Popular posts from this blog

UTM (qemu on OSX) only boots into uefi shell after installing Ubuntu 22.10 (solved!)

I've been meaning to try out running Linux and Windows virtual machines on my x86 MacBook Pro using qemu . I've been using Parallels for several years. Parallels is a nice application and works well but I'm always getting bugged to purchase upgrades. Parallels provides free updates on minor version upgrades only, say 13.0 to 13.1. With so many prompts to purchase upgrades it feels like Parallels could release a bit more minor versions and a bit fewer major versions. Rather than just purchase an upgrade to Parallels I figured I'd try out qemu via the UTM application . UTM wraps qemu with a helpful gui and comes as a packages Mac application. And UTM supports both x86 and M1 systems (as qemu also supports these systems). Creating an Ubuntu VM with UTM didn't go as smoothly as with VirtualBox or Parallels but it was the settings I chose that messed me up. Here are two things I ran into when installing Ubuntu on UTM. #1. Configure the qemu instance to use a 'Display...
Post a Comment
Read more

Debugging an imprecise bus access fault on a Cortex-M3

This information may apply to other cortex series processors but is written from practical experience with the Cortex-M3. Imprecise bus access faults are ambiguous, as noted by the term "imprecise". Compared to precise bus errors, imprecise errors are much trickier to debug and especially so without a deep understanding of arm processors and assembly language. Imprecise and precise flags are found in the BusFault status register, a byte in the CFSR (Configurable Fault Status Register). BusFault status register bits The definition for imprecise and precise bits is: [2] IMPRECISERR Imprecise data bus error: 0 = no imprecise data bus error 1 = a data bus error has occurred, but the return address in the stack frame is not related to the instruction that caused the error. When the processor sets this bit to 1, it does not write a fault address to the BFAR. This is an asynchronous fault. Therefore, if it is detected when the priority of the current pr...
5 comments
Read more

Travelling on Spirit airlines out of Boston Logan airport? Here are some tips.

I attended CES 2017 in Las Vegas. Booking the trip late I ended up on Spirit airlines. It was both non-stop, making it six hours to Las Vegas from Boston, and affordable, less than $300 for a one way trip compared to around $700 with JetBlue. Here are some tips that might help you when travelling on Spirit from Boston Logan airport. Eat Spirit is located in the B-terminal, gates B-37 and 38, with its own TSA security checkpoint. While it does have restrooms and places to sit the food selection is limited to a single food stand. I'd recommend eating at the Legal C Bar (number 77 in the image below) prior to going through the terminal security checkpoint. The food and service there were great. Drink The water and other drinks are cheaper if you buy them at the food cart rather than on the flight. Seats The seats on Spirit don't recline. They do this to reduce weight, seat cost, seat maintenance costs, and so seats don't impact the free space of other passengers,...
1 comment
Read more