Those are still APM pics. Also, I know the physical connections are there but according to the wiki:
Hexas, Octos, and other multicopters
Not Yet Implemented. update is coming...
The question is coming when?
Yes, I was planning to put my APM2 onto a hexa model this week - perhaps the old output assignments hold (vs the new ones suggested on the wiki). I'll have a poke at the code and see...
Be great to get some confirmation though.
Iv dug around the code a little and cant really find any specific porting for hex or octo.
On APM1, motors are connected to 1-4; 7-8 and 10-11.
One needs to check whether ch 5&6 on APM2 controls a servo for camera stabilization.
If they do, then the connections are the same as APM1.
I have been flying the APM2 on my Hex for some time now and you use the same pinout as APM1. Octo is not supported yet. Be carfull when you do firmware updates as in the next couple of firmware updates the pin defigns will change to what is on the Wiki and you will have to change your motor pins then. Just a heads up !!!
Thanks Jack! Good to know to avoid fatalities ;)
Im busy putting together an octo and want to use APM2.
Im gonna have to wait for the software to catch up with the hardware :)
Thanks Jack - I guess there will be much wailing and re-soldering of PDB connections when the change happens! :)
Iv done away with the routing of esc signal via the pdb. Straight from the escs to the apm i think is better. Less connections, less to go wrong.
Just remove the + & - 5v from the sil connector, heat shrink over them and bobs your uncle...
Would it be better to just remove the +5v feed, and ensure the negatives are commoned? I power my APM+Radio from a dedicated 5v BEC.
Iv been wondering this exact same thing. I read somewhere its better to remove both + and -. But i wonder if it would be better to connect all the gnd to each other. Any input?
No soldering !!! just unplug the output on the board to ESCs and change the order.
Jack - ah, yes, fair point ;)