Noob, working with pre-built blue-arduplane. I’m a year into my custom project.
In terms of frame architecture, the craft I'm building is a twin-engine delta-wing (w elevons), but specialized for a low-speed remote research application. Presently trying both Mission Planner and QGroundControl: I’ve got working GPS and telemetry reporting via 3DR 915MHz to my laptop GCS.
To reduce its energy consumption, I want to try controlling this low-speed craft using the telemetry radio via a HOTAS joystick with the GCS. I’ve gone through the joystick calibration procedure in Mission Planner and QGC, but I’ve yet to get a response from my craft's servos or motors.
Peripherally, but perhaps informative to this problem, I took a whack at interpreting the blue-arducopter startup-on-boot instructions for blue-arduplane and tried integrating Mirko's added instruction note regarding turning-on the servo rail, but using the systemd approach, as in the attached file.
Joystick Telemetry.pdf (300.3 KB)
It's not clear that creating and modifying those files had any effect, but ultimately what I generated did not result in auto-startup of blue-arduplane or power to the servo pins.
Anyway, when I enable the joystick in MP and try to arm the (propeller-less) craft, I get the message that MAVlink has rejected the command. QGC reports that this control-via-telemetry is a non-default behavior, and that what I'm up against is a need for MANUAL_CONTROL support in MAVlink. Basing a search on that, I find that ArduSub has integrated this functionality, but not the other ArduPilot platforms.
Can I simply ask for this to be integrated as a regular option in blue-arduplane, or is this functionality not sufficiently general-purpose to qualify for that treatment?
Have I reached the point where in fact I do have to delve into the code base and compile my own?
I'd humbly appreciate a "road map"... or any guidance really, so I don't waste a lot of time on this hurdle.