finally decided to give the hexa a go, nice build (will post pics later), just having issues with getting all the motors going, I uploaded the hex via the APM software chose hexa as the frame, setup the radio and callibrate the ESC's. But here's where it gets weird, only motors 1-4 fire up leaving the final two beeping waiting for a PWM output. Don't have my CRO on me atm so I thought I'd put it out there and see if anyone else has had a similar problem and hopefully a solution.
Almost forgot to add, I'm using the second release APM1 with the 2560 processor with x-bee telemetry.
Did you solder the APM by yourself?
@Chris, Yes, I did solder it myself, in the electronics lab. I have measured the outputs and channels 5 & 6 are outputting a solid PWM output of 1500, the other channels all register from 990 to 2000 depending on the throttle input, all inputs are working and have been calibrated in both the APM software and I have done it via the CLI, inputs are no problem, just the outputs. It's almost as if the firmware was for a quad rather than the hex...
This is even more interesting as I have discovered that output pins 7 & 8 are behaving as if they are the proper 5 & 6, giving a scaled PWM output.
I'm flying the ArduCopter hexa every week. Works fine. Are you absolutely sure you clicked on the right firmware icon?
Wait: you are following the manual, right? Output channels 5&6 are for the pan-tilt camera, not motors.
See diagram here.
Ahh... right then...
it's the old case of don't follow logic, just follow the instruction manual... damn this lisdexia!
haha, thanks Chris