Has anyone come across or though of creating/modifying an ardupilot firmware that would allow capability for dynamic motor balancing while all props are installed without the hassle of disconnecting ESCs to isolate one specific motor? Similar concept to what we have now by utilizing APM2 as a pass-through device to allow comms between GPS and a Windows based U-Centre application.
Nil requirement to undo props wiring etc just temporarily swap out FW and utilize an interface ( preferably mission planner ) to select a specific motor at 50 % power setting while others remain dead; then read on board vibration data and then rotate prop around or add tape etc to achieve lowest vibration results. Thus process allows consistent power settings and consistent readings from existing on-board accelerometers in between your balancing tweaks. Then after all individual motors have been done, you would simply re-load your applicable quadcopter's firmware.
On previous projects I have utilized apps on cell phones and disconnected ESC or slaved in an ESC to spool up individual motors, etc. Yes there are various methods/solutions folks have tried to quantify vibrations and whether or not their fixes were successful at reducing vibes; e.g., LASER method.
Am I way out in left field with this idea; modify existing code to void flight parameters, GPS, etc ( maintenance mode vice flight ready ) and thus allowing selection of only arming one specific motor ( like 15 sec ) then reading log via Mission Planner?
Rej
Replies
maybe a cool idea for decomissioned APM's mounted onto an arm, - but using the actual ArduCopter controller is usually mounted to be vibration-damped, and that would reduce sensitivity, and may add resonating frequency for the mounts etc, not only register the vibration directly on the arm.
Good point Andre,,,,my logic was to test the system as close as possible to flight config with exception of only one motor in operation and whatever APM's accelerometers are sensing would establish if your balance tweaks are in favour or detrimental to the flight controller while also factoring in your flight controller's vibration dampening set up.
Down side to my idea is that it factors in only one motor and negates the in-flight interaction between all motors where at times some vibrations will either cnx out each other or greatly amplify one.
Dreaming of just Mission Planner selectable to run one motor and view the graph....the less tempering with connectors the greater benefit it is to the operational status of the system.