Hey all. I'm a bit of a newbie at this game, having only played with glow fuel fixed wing RC's many years ago. All this electric stuff is doing my head in!
I purchased the ready soldered, and coded version of the Arducopter, and spent four hours putting it all together from all the pieces of conflicting instructions for different revisions all over the place. I failed to get Configurator tool to connect, but managed to run all the commands through the CLI steps successfully, and uploaded the Arducopter RC2 software.
Question is, when turn the quad on again, it does the usual beeps etc, but there is no throttle response.
In Mode 2, holding the throttle (left stick) down and to the right for several seconds does not arm the motors.
The A led shows solid green.I tested the TX/RX with servos, and it's all doing what it's meant to.
Any help would be much appreciated!
I'm sorry that I don't have an answer for you, but so you know you're not alone I do have a similar problem: rx/tx are bound and most stuff seems to be working as I can run each motor separately using the four tx sticks in the motor test mode in CLI, but I can't arm the motors in flying (non-CLI) mode, enabling the radio logging and dumping the logs after a failed attempt seems to suggest that *only* the throttle channel is making it through to the PWM input (unless the other channels just aren't logged when it's not armed ? haven't checked the code yet), that would certainly explain why I can't arm the motors.
The motor test seems to indicate that all channels are capable of being sampled correctly by the APM inputs, and I uploaded the radio test sketch from the ArducopterMega project and indeed that confirms that everything is working fine.
Sounds very much like we might both be running in to the same issue.
You wrote it fails to connect...
Stupid question, but, have you changed the Configurator connection timeout to 30s?