5 ms·
Model 3 owner here. Having same issue as back in March. No AP, no FSD and most frustratingly, no cruise control. Multiple TS steps over phone with no resolution
by nemosaltat 7y ago
Model 3 owner here. Having same issue as back in March. No AP, no FSD and most frustratingly, no cruise control. Multiple TS steps over phone with no resolution. The earliest appointment was months out so I drove into a service center. A frazzled, yet personable, tech assured me that the issue was NOT from the recent FW update but rather a hardware malfunction with the left repeater. I pressed for details- is it wiring, hardware, physical damage? He couldn’t tell me, but insisted that it had nothing to do with the previous FW update and that another FW update wouldn’t resolve it
Tech scheduled a service appointment for 4-13, much better than I could find in the app. On 4-4 Tesla pushed a FW update, which I guess is pretty common before a service appointment. On 4-5, a Tesla rep reached out and said the issue WAS in fact, with the original FW update and that the more recent FW update had resolved:
“Hello Sam,
We have reviewed your vehicle logs and alerts. At this time we do not see any issues with the Autopilot system as well as you confirming that the system is operating as designed. Since this is the case there will be no need for you to come in for your scheduled appointment. While there is no way to say that you will never have an issue again, at this time there is no issue that needs correction. If you do have an issue in the future you are always welcome to create another appointment with your concerns.”
I responded:
“Ok- I’d still like to understand what happened. It is generally acceptable that the universe is getting more disorderly. It is perfectly acceptable that something goes wrong and we don’t know why. It’s significantly less understandable, that the issue mysteriously resolves it self. Does that make sense?”
Tesla Response:
“Hi Sam,
It was found to be a software bug in the last update that was performed causing your cruise control not to function. That was resolved in the last update you performed.”
The rep then canceled the 4-13 appointment without further explanation or communication.
The issue returned yesterday (5-13) and now the earliest appointment is mid June.
Cruise control existed in 1958. I get that Tesla has “tight integration” but the lack of a fall back/degraded performance mode seems ridiculous. This is before considering the lack of NoAP and FSD, which adds insult to injury- Those features represented nearly 15% of the vehicle cost in my case ($8,000 upfront).
Convenience in LA traffic was a primary consideration when purchasing the Tesla. The lack access to purchased features is irritating, but I knew they were bleeding edge. The further loss of a ubiquitous feature like cruise control is even more irritating. Tesla’s handling of the situation feels ridiculous.
- zaroth 7y agoThis report is both impressive and frustrating. I’m sorry your AP is not functioning and their fix was not permanent, that must be incredibly frustrating as a huge benefit of the car is the AP system. At the same time, it is pretty amazing they are remotely logging into your car to review system logs and diagnose the issue, and then pushing firmware updates to try to remedy the problem. There may be no choice but to drive back to the service center to try to get a quicker response from Tesla. At some point if they can’t fix it there could be a remedy under the lemon law — they only get 3 chances and a certain number of days AFAIK. I can understand how a single fault could disable the adaptive cruise and likewise all of AutoPilot functionality. But Tesla is expected to be able to fix the issue promptly.
- fucking_tragedy 7y ago> At the same time, it is pretty amazing they are remotely logging into your car to review system logs and diagnose the issue, and then pushing firmware updates to try to remedy the problem. It really isn't if it didn't fix the problem and they used it as an excuse to not follow up with their scheduled appointment. This would be like if I was fixing a bug, SSH'd into a live instance, didn't fix anything, then filed the ticket as "fixed" and refused to follow up on it. That's not amazing, that's pretty sketchy.
- zaroth 7y agoBut that's not what happened. nemosaltat didn't provide a complete chronology, but did say they had a service appointment on 4-13, received a FW update on 4/4, and a rep contacted them on 4/5 saying they reviewed the logs and the new FW fixed the issue. Then nemosaltat responded to Tesla; > Ok- I’d still like to understand what happened....It’s significantly less understandable, that the issue mysteriously resolves it self... Tesla responded, > It was found to be a software bug in the last update that was performed causing your cruise control not to function. That was resolved in the last update you performed. Then, > The issue returned yesterday (5-13) and now the earliest appointment is mid June. So the issue was fixed, and then it returned. It's unfortunate but hardly sketchy.