DI_a138 - Front motor disabled - Ok to drive

[dalton108]

Dammit! Not this shit, again! Right after supercharging. I’m hoping it clears again like it did last time. ?

On 2025.8.7. Hopefully this is fixed in 2025.14.1?

Sponsored

 

[Docedward]

Dammit! Not this shit, again! Right after supercharging. I’m hoping it clears again like it did last time. ?

On 2025.8.7. Hopefully this is fixed in 2025.14.1?

Is this only happening after supercharging (Tesla site, not at home)? Is this occurring only after LONG supercharging like 20-80%+? I have little faith in my CT lately and need to avoid any more SC trips. Wondering if there is perhaps a way to avoid this by maybe shorter supercharge sessions until a software update?

Also, are you preconditioning the battery? Just checking all the boxes. Really have no need for this- like all of us.

 

[dalton108]

Is this only happening after supercharging (Tesla site, not at home)? Is this occurring only after LONG supercharging like 20-80%+? I have little faith in my CT lately and need to avoid any more SC trips. Wondering if there is perhaps a way to avoid this by maybe shorter supercharge sessions until a software update?

Also, are you preconditioning the battery? Just checking all the boxes. Really have no need for this- like all of us.

It’s a known bug and it only happens after supercharging. I don’t think that it has (across all the examples described on the thread) ever happened with anybody charging at home. I always pre-condition. Today my session was from 43 to 85 because I’m getting ready to do some towing in town so that’s gonna burn off.

I don’t know if it’s happened to anyone charging to a lesser state of charge on the top end. But I don’t think it’s a determining factor.

The only variant on this is I’ve seen is that in some people’s case they are actually having a real fault and having to have motors or switches replaced - not just a software glitch like mine. Also we’ve seen variation in how long it’s taking some people to clear the fault - days in some cases.

Fortunately for me, just like last time a power down i.e. “power off” from the safety menu cleared the issue.

Last time it was a 15 minute shutdown, this time I did 30; same result, I’m back in business.

 

[noobla3]

Dammit! Not this shit, again! Right after supercharging. I’m hoping it clears again like it did last time. ?

On 2025.8.7. Hopefully this is fixed in 2025.14.1?

OK, this just happened to me this morning. Was Supercharging starting at around 19% SOC and I stopped at 40%. Drove off and heard some weird noise and saw the message. I did precondition for like 10 minutes before charging.

I did noticed that I was charging at 75kW even when the car on stall A left. So was it capped? (V2 Supercharger).

Added this to an existing service request.

EDIT: mine is the front motor. (Dl_a138). Read up thread a bit more and yes, I preconditioned and did notice the motor whine was louder during it.

 

[noobla3]

How do we determine whether this is a “software” glitch and not real needing a motor replacement?

And did this bug really disable the front motor?

 

[dalton108]

How do we determine whether this is a “software” glitch and not real needing a motor replacement?

And did this bug really disable the front motor?

if it resets after sleeping like mine and others software. If it doesn’t you’ll know because you’ll have to take the truck in.

 

[noobla3]

if it resets after sleeping like mine and others software. If it doesn’t you’ll know because you’ll have to take the truck in.

If it was indeed a software glitch, did it disable the front motor?

 

[Docedward]

I’m not really confident in the consistency of SC diagnostics and decisions. I see many issues with varying responses depending on the SC. I know for me, I had a breakdown with major errors that the soft and hard rested did not work on BUT when it sat at the SC the alerts all disappeared (after 4 days of no action). They decided to replace the main computer because on further the diagnostics, there was an out of spec resistance showing (overheated). I honestly don’t think A and B were related. This “n of 1” experience has further tainted my view of Tesla SC and the Cybertruck. It’s simply too new and too many issues for them to track well.

Did these motors really need replacing? Do they still? How are they related to superchargers causing motor failures?

 

[dalton108]

If it was indeed a software glitch, did it disable the front motor?

I have a tri-motor and my image clearly shows it’s the rear left and right motors that are being disabled, and yes in all cases the effected motors will be disabled.

if it’s just software that will reset; if not, it won’t. There’s extensive discussion about these symptoms above and I believe in another thread that someone linked above.

 

[Maaz]

Wow, is this effecting all
Cybertrucks or just Foundation?

 

[noobla3]

Wow, is this effecting all
Cybertrucks or just Foundation?

Believe there was a non FS earlier in this thread.

 

[d9271]

Had this happen to he today after a 40min SC on 2025.8.7…cleared after sitting for two hours ..scroll reboot didn’t help …my XP100 with over 370k miles feels more reliable than my FS AWS 37xx VIN with 3800 miles only ..this car actually seems as buggy as an early 13k VIN S I had from 2012 …hopefully this is purely software bug and not anything mechanical …

 

[dalton108]

Had this happen to he today after a 40min SC on 2025.8.7…cleared after sitting for two hours ..scroll reboot didn’t help …my XP100 with over 370k miles feels more reliable than my FS AWS 37xx VIN with 3800 miles only ..this car actually seems as buggy as an early 13k VIN S I had from 2012 …hopefully this is purely software bug and not anything mechanical …

Yes, scroll wheel doesn’t work; but if you go into the safety menu and power off, I believe that this is more effective at resetting the fault and will get you going again faster. That has been my experience and someone else reported the same prior to me experiencing the issue or trying it.

 

[sycamore22]

Message only showed up once for me. Service replaced the front drive inverter. All fixed!

 

[noobla3]

Message only showed up once for me. Service replaced the front drive inverter. All fixed!

Did the message go away after a while? Apparently there’s a bug that causes that message.

Sponsored