@Albcem wrote:
I am in doubt about whether I should keep the flight controller (Pixhawk 1) active or passive for the initial flights of a naturally stable, CTOL fixed wing plane that is my own design.
I am perfectly aware that Arduplane is designed to simplify things, avoid problems and not to create them. However, in the hands of an inexperienced user, perhaps it is easy to shoot your own foot with so many parameters that may be set wrong triggering failsafe in the wrong moment or power systems misconnections that may lead to a brown out and a crash.
Alternatives I am considering for the maiden flight:
Keep Pixhawk as a passive vehicle flight data collection tool and connect all the servos directly to an independently powered RX
Set all servos to pass through or redirected to RCIN# channels through Pixhawk, but this will not protect me against a Pixhawk brown out
Use ArduPlane / Pixhawk as how they are intended to be used and drive the plane through Pixhawk with the benefits of the auto- stabilization, failsafe and autotune functions it provides. (Eventually, I will have to use them, so what not use them from day one?)
Any opinions and recommendations to minimize the risks of the maiden flight would he welcome?
Thanks
Posts: 6
Participants: 4