Discussions

Problem Arming my Arducopter

Posted by Daniel Gru on June 28, 2011 at 2:38pm

Hey Guys,

i am having problems arming my copter, and after a few people have been very helpful in the chat and we still haven't found a solution, i thought i'd post my problem here:

 

I am on version AC 2.0.29.
I have setup my radio, the gps, the magneto, everything is working fine, getting good feedback in the missionplanner.

 

Now, i had the problem I couldn't arm the motors.... green LED on the IMU was constantly blinking.
After that, i recalibrated all the escs, that worked fine, everyone of the quads-motors spins up, when connected to the reciever directly.

Now, after the recalibration, I then tried arming with yaw right and even left (just in case channel is reversed).. but if i then add throttle, nothing happens...and the green led doesn't turn solid.
(Green LED is solid when the CLI switch is in CLI position, don't know if that is correct)


My radio values seem ok, throttle min is round about 1100, tried putting the trims to the very bottom, bringing it to 990, but still doesnt work.

Yaw values are normal to.
I am in stabilize mode, and the GPS has got a lock, everything in the flightdata screen on the missionplanner looks good too.

I went into the CLI and typed: "setup" and then "motors"... no writing appears in the terminal, but if i give full right roll, the left motor turns slowly and if i give full nick forwards the back motor turns slowly... no reaction on throttle, yaw or full nick backwards, full left roll..

I am lost, can someone please give me a hint?

Regards

Daniel

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

Join diydrones

Email me when people reply –
Follow

Replies

  • Daniel Gru June 29, 2011 at 4:21pm

    Thanks everyone, @chris: i had looked at the troubleshooting and tried everything off that list, but that didn't help... well, main thing is, everything is up and running now :)


    Regards

    Daniel

  • 3D Robotics
    Chris Anderson June 29, 2011 at 3:53pm
    Don't forget that there's a Troubleshooting Guide in the manual that covers this.
  • neil.elver June 29, 2011 at 3:49pm
    If you have to arm to the left then that is backwards yaw. One thing I forgot to mention that may be helpful is to notice if the blue led on the bottom board is blinking fast or sitting solid or blinking slow ( see the wiki to confirm as I've seen both slow and solid if not connected to radio. May be solid if no rx and blinking slow if rx but tx not on). Think of this like the network led on your router but as the comm between your rx and the apm board. If its not blinking fast its not getting radio signal.
  • Daniel Gru June 29, 2011 at 3:29am

    Guys i have not the faintest idea what has changed, but now it works...

    left it all lying around last night, today i went into setup and it said "still need to calibrate radio" (which it didn't say yesterday) after doing that all 4 motors reacted in the motortest and they now can be armed...

    Only thing, they are armed with yaw left instead of yaw right, does that mean i have to invert yaw-channel?


    Thanks for all your help

     

    Regards Daniel

     

  • Pieter van Woerkom June 28, 2011 at 4:27pm

    Arming not in CLI !  Switch away from the rc connectors. STABLE or SIMPLE mode and be aware of any Dual rate switch.

    I had an old program in my transmitter and flew with an other plane and hit the DR switch.

    After switching to my copter my DR was on 60% so it never got armed because te ardu was not calibrated at 60% but at 100%. After disengaging the DR it armed.

  • neil.elver June 28, 2011 at 4:22pm
    I would check your receiver outputs to be sure the assumed channels 1234 are mapped to the correct outputs/apm Ins. Use an old servo and be sure the numbers of what Chan number does what match the wiki. Your radio setup or mode can affect this. The motors command is working correctly in cli with no text output but should affect all 4 motors in the direction youre moving the right stick ( pitch and roll ) IIRC. I'd also try manually calibrating all escs which might get all 4 working in motors command.
This reply was deleted.

Activity