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
RT @IndyAChallenge: Here is the ROS-based small-scale vehicle platform showing the ROS Visualization (Rviz) screen with multiple ROS nodes…
5 hours ago
DIY Robocars via Twitter
RT @IndyAChallenge: Here is Black & Gold Autonomous Racing's simulated racecar running a lap @IMS and showing the team's code overtaking ot…
5 hours ago
DIY Robocars via Twitter
5 hours ago
DIY Robocars via Twitter
RT @donkey_car: New Maintainers! Donkey Car 4.0 and more! Here is our September Newsletter! https://donkeycar.substack.com/p/september-donkey-newsletter?r=2ji2t&utm_campaign=post&utm_medium=web&utm_source=copy
6 hours ago
DIY Robocars via Twitter
RT @chr1sa: Kinda cool that we just hit 2,500 members of our Bay Area self-driving car racing league. More than 10k globally. Fast, cheap…
6 hours ago
DIY Robocars via Twitter
RT @chr1sa: Our next @DIYRobocars virtual AI car race is next Saturday. Compete from home using the @donkey_car simulator -- no physical ca…
yesterday
DIY Robocars via Twitter
RT @RoboticMasters: Students from @Sydney_Uni working hard on improvements and changes to @donkey_car simulator. @diyrobocars @adafruit…
yesterday
DIY Robocars via Twitter
Practice virtual race this Saturday; the real thing will be on Oct 3 https://www.meetup.com/DIYRobocars/
Wednesday
DIY Robocars via Twitter
Wednesday
Derrick Davies liked lisa TDrones's profile
Wednesday
DIY Robocars via Twitter
Sep 21
DIY Robocars via Twitter
RT @SahikaGenc: AWS DeepRacer & Hot Wheels Track https://youtu.be/4H0Ei07RdR4 via @YouTube
Sep 14
DIY Robocars via Twitter
Sep 8
DIY Robocars via Twitter
RT @davsca1: We are releasing the code of our Fisher Information Field, the first dedicated map for perception-aware planning that is >10x…
Sep 8
DIY Robocars via Twitter
RT @SmallpixelCar: How this works: 1)object detection to find cones in single camera image, 30 frames/sec on @NVIDIAEmbedded Xavier. 2)comp…
Sep 8
DIY Robocars via Twitter
RT @SmallpixelCar: Use two color cones to guide the robocar. No map needed, on onsite training needed. Just place the cones and it will fol…
Sep 7
More…