Servo Jitter – Resulting in a crash

I was recently flying my Tri in AUTO mode, flying a mission I had previously flown the day before, when to my horror it appeared to go completely nuts before free falling 100m to the ground. On review of the video from an onboard gopro you can clearly hear the yaw servo jittering before going crazy to the point that the  APM board went briefly into FailSafe mode then Disarmed in mid flight. ( not good )

I’ve been flying multirotors for a while now but have recently progressed / transitioned from a KK2 control board to the APM2.6. Over the last couple of months I’ve been working my way through the various flight modes and coming to terms with the seemingly endless functionality of Mission Planner.

Until now I’ve never had an issue with servo jitter ( on this setup or previous tricopers I’ve built ) so I’m a little confused as to just what might be causing the issue. So I guess what I’m looking for is a little guidance / wisdom on pining down the cause of the servo jitter. ( Having an unscheduled 100m free fall is not something I wish to repeat. )

Ive listed as much detail as I can on my current setup ( as it was on that day )


Frame: FliteTest – BatBone

Motors: NTM Prop Drive Series 28-26A 1200kv

ESC’s: HobbyKing 30A BlueSeries Brushless Speed Controller

Servo: Turnigy XGD-11MB Digital Mini Servo

Battery: Turnigy 2650mAh 4S 20C

Control Board:

 APM 2.6 Set Side Entry (external compass)

-3DR Radio Telemetry Kit - 915 Mhz


The power wiring is as per the documentation for using the Power Module and using power from one ESC to power the servo.


Power Module and using Servos with BEC power from one ESC

  • If you have a power module and you are using servos Remove JP1.
  • Provide APM and receiver power via the power module connected to the APM’s power module connector.
  • The BEC of a single ESC must provide sufficient power for all your servos.
  • When connecting your ESCs to the OUTPUT connector clip the BEC power leads on all but one of the ESC’s connectors.
  • Or connect only the ESC signal wires to the OUTPUT connector for all except one ESC.
  • And on that ESC connect all 3 wires to the OUTPUT connector.


I’ve included the log data from the APM and from the mission planner (as I had the telemetry link running at the time )

And a link to the gopro footage on youtube.

Many Thanks


2013-12-01 17-54-11.tlog

2013-12-04 20-31 27.log

2013-12-04 20-31 27.log.gpx

You need to be a member of diydrones to add comments!

Join diydrones

Email me when people reply –


  • It looks to me as if you had some sort of mechanical failure, like your ESC shorting. You mention it going into Failsafe, but the dataflash log doesn't show anything, no ERR entries. The data just stops high in the air.

    The attached plot of your altitude and voltage shows what was happening. Everything progresses well until about line 3969 where you are still at 14.51 volts. Then at line 4113, only 4 seconds later, you are at 13.65 volts. One second after that the data just ends. So something shorted out pretty substantially to bring your battery down like that. A look at your Current plot shows a big increase in current during that period too.

    Your Vcc doesn't look too bad to me which seems odd. Since you are powering your APM via a separate PM, even if the ESC blew, taking out power to the motors, power should remain to the APM. To me, this suggests a secondary failure in your main power wiring between the battery and the Power Module, possibly caused by a primary failure in your ESC. Perhaps your ESC blew and shorted, thus blowing out a weak solder joint near your battery?


This reply was deleted.


DIY Robocars via Twitter
DIY Robocars via Twitter
DIY Robocars via Twitter
May 13
DIY Robocars via Twitter
RT @f1tenth: Say hi to our newest #F1TENTH creation for @ieee_ras_icra next week in Philly. It’s going to be huge! 😎 🔥 @AutowareFdn @PennEn…
May 13
DIY Robocars via Twitter
May 11
DIY Robocars via Twitter
May 8
DIY Robocars via Twitter
RT @SmallpixelCar: Noticed my car zigzagged in last run. It turned out to be the grass stuck in the wheel and made the odometry less accura…
May 8
DIY Robocars via Twitter
RT @SmallpixelCar: Test my car. RTK GPS worked great. Thanks @emlid for their support.
May 8
DIY Drones via Twitter
RT @chr1sa: @kane That's @diydrones circa 2009. Still have a box of those Canon cameras that we used to strap into planes, just like this.…
May 3
DIY Robocars via Twitter
RT @chr1sa: Our next @diyrobocars race is going to be outside at a real RC racetrack in Fremont on May 28. Fully autonomous racing, head-to…
Apr 30
DIY Robocars via Twitter
RT @f1tenth: Our Spring 2022 F1TENTH course @PennEngineers is coming to an end with a head-to-head race as a big finale. So proud of our st…
Apr 26
DIY Robocars via Twitter
RT @DanielChiaJH: I wrote a thing! Throughout the development of my @diyrobocars car I've been using @foxglovedev Studio to visualize and d…
Apr 23
DIY Robocars via Twitter
RT @SmallpixelCar: My new car for high speed. Low body, everything ( @NVIDIAEmbedded Jetson Xavier NX, @emlid RTK GPS, IMC) under the deck…
Apr 23
DIY Robocars via Twitter
Apr 21
DIY Robocars via Twitter
RT @f1tenth: F1TENTH Race training setup @PennEngineers for our upcoming ICRA2022 @ieee_ras_icra competition. @OpenRoboticsOrg @IndyAChalle…
Apr 21
DIY Robocars via Twitter
RT @fatcatFABLAB: Proud to be hosting a restarted DIY Robocars NYC Meetup April 26. Come by if you want to talk about and race self-driving…
Apr 17