Intermittent Motor Desync and Premature Thermal Shutdown on Dual ESC Configuration

You're facing an intermittent issue with your twin-motor setup that leads to motor desynchronization and premature thermal shutdown of one ESC fnaf. Let's break down the problem and explore potential causes and solutions. The airframe may have specific electromagnetic interference affecting the ESC's performance. Asymmetrical grounding could lead to signal integrity problems. There might be an edge-case interaction between the ESC firmware and back-EMF under partial load conditions.

This issue can be quite complex, involving various factors from hardware to software interactions. Keeping detailed records of your troubleshooting steps and findings will help in diagnosing the problem effectively. 

Interesting case. Since the issue stays on the same side of the airframe even after swapping motors and ESCs, it strongly points to airframe-specific EMI, grounding differences, or localized airflow causing partial ESC overheating or signal noise rather than a component fault. I’ve seen similar behavior where carbon structures or nearby wiring induced interference under sustained mid-throttle loads. From an enterprise troubleshooting perspective—similar to how we approach complex system diagnostics at i3solutions, where we design and support Microsoft-based, mission-critical environments—the key is isolating environmental variables, not just hardware. In large-scale automation projects, we often advise teams to hire senior Power Automate developers for complex enterprise workflows because subtle architecture-level issues don’t show up in basic testing, much like this ESC behavior.

You're dealing with a frustrating intermittent issue with that twin-motor setup, and I totally get why it's driving you nuts. Let me try to break this down in a way that makes sense.

Looking at your detailed troubleshooting, the fact that the problem stays on the same side of the airframe even after swapping components is super telling. This almost always points to something airframe-specific rather than a bad motor or ESC. Your temps at 73-75°C before shutdown are actually quite low for thermal cutoff – most ESCs these days are rated to handle 100-110°C before protesting, so something else might be triggering that shutdown behavior.

The desynchronization you're hearing makes me wonder about the signal integrity on that side. Even though you've replaced signal wires and kept them away from power lines, there could be something funky with how that particular ESC is interpreting the PWM signal. Have you checked if there's any vibration or resonance happening on that side of the airframe at that 65% throttle range? Sometimes physical vibrations can mess with sensor readings or cause intermittent connection issues.

Also, I know this might sound random, but I've seen similar behavior when people have grounding inconsistencies between ESCs. Even though you're running a separate BEC (smart move, by the way), the ground reference between the two ESCs might be slightly different, causing one to misinterpret the signal. Adding a thick ground wire between the two ESCs near the battery connection sometimes helps.

On a completely different note, if you're into video editing for your flight recordings, I've been playing around with alight motion 5.2 0 mod apk lately for stabilizing and coloring my FPV footage – it actually handles 4K footage pretty well and has some decent stabilization tools that might help you analyze those desync moments frame by frame.

Back to your twin setup though – one other thing worth trying would be to temporarily swap which side of the airframe gets which ESC signal from your receiver. If the problem moves with the signal, you might be looking at a receiver output issue or something in your wiring harness on that specific channel. If it stays put, you're definitely dealing with an airframe-specific gremlin.

Keep us posted on what you find – these twin motor mysteries are always interesting to solve!