Replies to This Discussion

Permalink Reply by Luke Nyhof on June 3, 2012 at 9:38pm

Almost forgot to add, I'm using the second release APM1 with the 2560 processor with x-bee telemetry.

• ▶ Reply

3D RoboticsPermalink Reply by Chris Anderson on June 3, 2012 at 9:42pm

Did you solder the APM by yourself? 

• ▶ Reply

Permalink Reply by Luke Nyhof on June 3, 2012 at 10:24pm

@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.

• ▶ Reply

3D RoboticsPermalink Reply by Chris Anderson on June 3, 2012 at 10:27pm

I'm flying the ArduCopter hexa every week. Works fine. Are you absolutely sure you clicked on the right firmware icon?

• ▶ Reply

3D RoboticsPermalink Reply by Chris Anderson on June 3, 2012 at 10:31pm

Wait: you are following the manual, right? Output channels 5&6 are for the pan-tilt camera, not motors. 

See diagram here. 

• ▶ Reply

Permalink Reply by Luke Nyhof on June 3, 2012 at 11:42pm

Ahh... right then...

it's the old case of don't follow logic, just follow the instruction manual... damn this lisdexia!

haha, thanks Chris

• ▶ Reply