hi guys, I state that the car is currently working perfectly. However, I usually go to check the errors reported in the notification center although they are not active. I found 2 with the codes referred to in the subject of this post. I immediately opened the ticket with Tesla to ask for information, hoping for the usual answer they give lately: it is a software problem that will be solved with the next update instead no. They tell me to bring the car because after consulting with the parent company (I live in Italy) my car would be at risk ... I no longer remember the English term ... But it is something as the car would be have a road arrest I bring it to them and the first thing they do is charge the battery to 100% and put it under their detectors and for 18 hours left at 98% charge the diagnostics gave a negative result, i.e. at the moment they are groping in the dark On the other hand, they invented as an attempt to change a part which, to change it, would involve putting the car on the bridge, disconnecting and lowering the main battery, replacing the piece they believe is the cause and reconnecting it Needless to say, hearing this in front of a perfectly functioning car and without any sign of an anomaly, I immediately asked to take it back and while the piece arrives I meditate on it. Since sooner or later this piece will arrive and since they are not absolutely sure that this is the cause it is just an attempt they told me they are doing and If it is not that, they will have to continue further. Since at this very moment my car continues to go which is a beauty and indeed yesterday I tried the ludicrous + mode for the first time, I see no reason to subject my car to such stress To paraphrase it would be as if a person who once had a cough (the last error report dates back to 10 days ago) immediately had a bronchoscopy done. Perhaps first it is better to go through a tac what do you say? Here is the reason for my post: is there someone who has seen these error codes. And if so, what was the real cause? I would like to avoid having the car disassembled thanks let me know
I'd share your concerns with the Service Center. If they aren't asking for money, I would personally think Tesla just wants avoid problems and figure out what is going on. prevent a problem Let them know when you don't understand what they are trying to do. Ask them to explain. You might listen to the Q4 talk from today. Tesla goal is to work toward perfection in order to AVOID service calls. Elon/Tesla has often stated SERVICE will not be a profit center. Very different from other auto makers. The best service is not to need any service, right? Let us hope & help Tesla attain this goal. good luck, enjoy your new ride, have fun
Hi, Thank you for you suggestion but I have already shared my concern with the Service and they have told me that they have sent the log to Tesla and Tesla has replyed them to “try” to change a component attached to the main battery but if in this way the problem persists they will have to continue to investigate You have to know my car is quite new and I wouldn’t disassemble it part after part till they will find the solution . So the reason of my post is to try to look for someone else he has had the same error in the past to let me know how it has been resolved
I got the same issue f150 qnd w150 but my car is stopping charging frequently. And starting charging again by it self. Sone times 20 times in 12 hours . Some times charging is not starting again after being interrupted. Tms 2016 90D 150miles . Norway. Follow teslafromhell at snap and insta just started posting more will come ... stay tuned
Update .... Got email from service center just now . They say it software related and 2021.4 will fiks it . "Etter besøket ditt til Tesla Oslo Nord i dag 05.02.21 rundt kl. 07:30 har vi nå fått inn resultat av fjerndiagnostisering av din bil som viser at dette er en firmware feil som vil bli fikset ved firmware versjon 2021.4." This is on Norwegian. But lets see if its a fact that it will solve the problem . Yet to see.
Fine. It’s sound good. I was quite sure it was a software problem but now we have a confirmation In my opinion for me is already been solved with the version 2020.48.35 but let we see what will happen next days . I continue monitor the log Thanks for your sharing