Custom Frames--Get Rid of V and Replace it with Any Custom Frame

I've written an Excel worksheet that will generate add_motor_raw code for any 
quad, hex, or oct multi-copter.  It can serve as a basis for requirements 
(pseudo code) for altering Mission Planner or it can act as a stand-alone code 
generator for those wanting to fly more precisely with more advanced frames.

Why is this needed? Photography is big with multi-copters.  Cameras don't like 
to stare into propellers.  This means moving the camera & gimbal forward, which 
shifts the CG (and we should be flying around the CG not center-of-frame) or we 
can alter the standard X rotor design where the front two X rotors are spread 
further apart (similar to the V), or do both.  It is my understanding (may not 
be correct) that the V-frame isn't that special in that all it does is redefine 
the proportions of roll and pitch for each motor.  What's really big about the 
V-frame is that it is a part of Mission Planner and can be used to open the 
door to any custom multi-copter, quad, hex, or oct.

I'm looking for who I can collaborate with to perfect the Excel worksheet and 
then deliver it to the community or refine it so it can act as the requirements 
for altering the Mission Planner V option.

P.S.  My personal interest is that my camera multi-copter frame is an Oct-H, 
which is closer to the X than it is to the V.  I could just plow ahead on my 
own, but would rather contribute.

Original issue reported on code.google.com by forrestf...@gmail.com on 28 Feb 2013 at 1:49

adibpriatama / arducopter

Custom Frames--Get Rid of V and Replace it with Any Custom Frame #553