Arducopter motors not arming: Solution + Win

This-Thread-is-full-of-WIN.jpg?imageSize=Medium&generatorName=PIP-BOY

Two Saturdays ago I spent the afternoon assembling and configuring my first arducopter - yay (all stock - frame, motors, ESCs, boards, Turnigy 9x radio).  I was surprised at how quickly it all came together (approximate build/soldering time 2-3 hours). 

 

Then I got around to 'arming the motors' and I got stuck... real bad.  I loaded and reloaded the code(RC2) ran Configurator and CLI many times, calibrated and recalibtated ESCs.  I disassembled and reassembled everything. I broke out the multimeter, oscilloscope, spectrum analyzer and the like. I ran through every conceivable mode and setting on my Tx and even took it apart. 

 

As a last resort I came to to this forum (I like to troubleshoot and dissect problems the hard way first).

It took me about two weeks - I read through almost every forum discussion relating to arducopter motors and configuration - several hundred pages.  I observed a common theme - almost all threads on motors not arming contain comments with basic instructions/troubleshooting tips from the manual and wiki.  95% of these conversations end with the thread's author resolving to buy new hardware or keep trying - no solutions anywhere to be found. 

 

After countless hours of reading I came upon a single comment (I've forgotten the member's name now and can't go back in my search history b/c I just updaed to Firefox 4 - but thank you whoever you are) that solved my problem:

 

In order to arm the motors using my radio  (Turnigy 9x aka Eurgle, FlySky, iMax, etc - an inexpensive but popular model here) I had to hold my throttle AND yaw controls down and to the right (throttle is on the right and yaw to the left in default mode 1 on Turnigy 9x).

 

Again, if your motors are not arming properly, try moving the yaw stick to the lower right position along with the throttle to arm.

 

A word of caution: I still don't know if there is a better solution to all this, but my maiden flight consisted of the quad doing a violent violent backflip and snapping two props.  This is because I returned my throttle to the neutral position before the yaw, completing the arming process with quad responding to the yaw stick posiion.  My solution is to move yaw to the center position then let the throttle go.

 

I kept a pretty detailed step by step build log with a few observations and tips that might help with first builds - I'll get around to posting it eventually.  Also, a few tools and materials not listed in manual or included in the kits (most notably single fem to fem connectors and a GPS cable long enough to reach the top of the dome).

 

Hope this helps and any input is appreciated - happy flying!

 

 

 

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

Join diydrones

Email me when people reply –

Replies

  • Thanks! That helped a lot! But I still can't arm my heli, unless I use mission planner. Maybe if somebody here knows the logic of arming i.e. what PWM values in what channels makes it arm/disarm, I believe it would really be of use for us.

  • 3D Robotics
    Ah--you're flying Mode 1! ArduCopter is designed for Mode 2 (the standard in North America). We'll have to make that clear in the documentation. Thanks for the heads up!
  • That is a standard safety on most (all?) radios.BTW the standard dis-arm is to hold the throttle to the bottom left for several seconds.
This reply was deleted.

Activity

DIY Robocars via Twitter
May 15
DIY Robocars via Twitter
May 14
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. https://t.co/EkQ6qmjmWR
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
More…