Crash during Autotune: CUAV X7+ Flip & Vibration Log Analysis

I experienced a crash while performing Autotune on a CUAV X7+ running the latest firmware. The drone flipped unexpectedly. Could you please help me analyze the logs to determine if this was caused by gyro noise or another issue?https://drive.google.com/drive/u/0/folders/1eebj3bch4JSViWDy0sU-W9vDCCtcuNRa

Remove the access requirement for the link.

Also tell us what components you’re using. Motors, props, ESC, Frame. Etc.

  1. Motors: T-Motor MN501-S 300KV
  2. ESC: Hobbywing 40A
  3. Propellers: 24-inch foldable
  4. Flight Controller: CUAV X7+
  5. Total Weight: 5600g (5.6 kg)

Looks like motor 4 failed.

Check the motor, ESC, wires, prop.

1 Like

Suggest you get current logging working.

@dkemxr @Allister thank you for the reply.

Post-crash diagnostics involved a comprehensive motor spin-up test and ESC signal verification; all actuators were confirmed and to be operating nominally. Analysis indicates that a mechanical or electrical failure of Motor 4 would typically trigger a ‘Potential Thrust Loss’ error within the flight controller logs or in messages. However, the data reflects no such anomaly, suggesting the motor was responsive up to the moment of impact.

I’m not sure what the trigger is, but we don’t always see the “thrust lost” message.

Consider the possibility of a desync, or intermittent problem such as a bad solder joint or connection.

1 Like