Welcome to Tesla Motors Club
Discuss Tesla's Model S, Model 3, Model X, Model Y, Cybertruck, Roadster and More.
Register

Multiple GTW Errors After Extensive Repair - Unable to Charge - 20 MX Performance

This site may earn commission on affiliate links.
Hi guys

Any help or feedback is greatly appreciated. Long story short I purchased a wrecked (rear end damage) clean title 20 MXP to repair and drive. I am in the repair business, and the repair itself went fairly smoothly although it was an extensive repair. The car was dead when I purchased (pyro fuse), I did not power it up due to the airbag deployment. After the repair, it powered up but is giving multiple error codes shown below.

GTW_f281 - Software update required
GTW_f210 - Service is required
GTW_f209 - Unable to charge
GTW_f208 - Unable to start vehicle
GTW_f015 - Software update required

The car sat after the accident for a bit, and then sat in my shop while being repaired for a total of 6 months or so. It is showing a range of 37 miles remaining. I have replaced the 12V battery. I was careful to check for short or wire damage when disassembling and reassembling. The only module replaced was the charge port housing/module. Safety Restore cleared the crash data from the SRS module. Initially it was trying to download an update, but it seemed to have failed to install. I repeatedly get the "update did not complete successfully. Please wait for a new update to be sent to your car" popup.

My next troubleshooting step is determining whether it is a hardware or software issue. Hoping someone here may have insight into that. I have a Toolbox 3 cable on order and that will be my next step.

Thanks in advance
 

Attachments

  • IMG_6838.jpg
    IMG_6838.jpg
    466.4 KB · Views: 922
Figured I would add a little more info. I will continue to update the thread in case anyone else has a similar issue.

Firmware v10.2 2021.4.18.2
Unable to enter service mode from the screen.
I do hear contactors opening and closing, car remains powered up when 12V is disconnected so there is some HV.
Charge port will open and close, when charger is connected display reads charging stopped. Pressing start charging has no effect.
I have done several wheel change hard resets, no effect.

Unfortunately waiting a week or so for toolbox cable. I would like to try a gateway reboot and see if there is any change.
 
Not sure this will help, but the deepest reboot is changing the the wheel size on the screen. One time our 2020 wouldnt go into drive. Changing the wheel size rebooted something and we were able to proceed. Also I had an upgrade that kept failing. I did a wheel size reboot followed by a user initated software update and it took.
 
  • Like
Reactions: HackFL
Thanks for the tip!

I did make some progress on it for anyone encountering similar issues. Another user pointed me in the direction of the modules I changed out. I swapped them with the original from the door and swapped circuit board from original charger port and was able to start it but was still having charging issues.

It turns out even with the HV cover in place on the rear of the charger port the red safety lock MUST be pushed all the way in and locked, as there is a sensor on the board inside to detect it. If it's not locked you will get charge port codes. Hope this helps someone. Charging now :cool:
 
I'm having similar issues after replacing the HV battery on my model s, nearly the same error codes, battery was at 37% for a moment but now it shows 0% and I'm having no luck solving the issue. Where exactly is this red safety lock located?
 
Hi, I wanted to refresh the thread as I don't see anything similar elsewhere.

Backstory: salvaged tesla s 100D, added to tesla app, can't start, won't recognize the keys thus can't open gateway, phone app start is allowed but does nothing, vechicle off all the time and drive rails off.

Before changing the pyro fuse I changed charger & cables to EU, modem to EU (got LTE straight away).

I lost 1 day subscription to toolbox and wasn't able to complete most routines, the antennas routines all failed, reading dtc failed with errors, literally it was useless without gateway open.

Any ideas what to do? It got me thinking it might be gateway problem (maybe the BCM failed) and won't connect to most systems?

I will be thankfull for any answers.
 

Attachments

  • 412500852_1342017036675790_2572661390265811264_n.jpg
    412500852_1342017036675790_2572661390265811264_n.jpg
    53.7 KB · Views: 63
  • 412309505_307255138366472_7175261271439419856_n.jpg
    412309505_307255138366472_7175261271439419856_n.jpg
    71.8 KB · Views: 57
  • 412234277_880333686973616_2398390295998200861_n.jpg
    412234277_880333686973616_2398390295998200861_n.jpg
    54.5 KB · Views: 66
  • 412393224_1330494190848380_4513250170711804246_n.jpg
    412393224_1330494190848380_4513250170711804246_n.jpg
    75.5 KB · Views: 75
Hello Papito. were you able to solve the problem? I'm having the similar problem right now. In my case it seems to be because a software update was installed in the vehicle. The air suspension was not updated because there are errors in the control units. In my case the air suspension was locked due to a crash event (TAS_a025). This probably prevented the update in the TAS. For this reason, there is now a mismatch error (GTW_f321) (incorrect software version in the TAS), which in turn causes the error GTW_f208. I think it can be solved with Toolbox. But what I still don't understand is how I can unlock the gateway without starting the vehicle so that I can work on it with Toolbox. The gateway cannot be unlocked due to the GTW_f208 error. I haven't tried working with toolbox on the vehicle yet but I suspect I will fail if the gateway is not unlocked.