Feature request: Add support for MavLink v2 protocol version / remove 8Ch limit about dronebridge

[seeul8er]

Hi,
MAVLink v2 support is part of DroneBridge since day one. I never used the v1 libraries.
With the control module set to transparent pass through (option 5) the protocol does not matter. Any message sent will get forwarded to the FC and vice versa.

That must be a fairly new message (I think it did not exist some months ago). I will add support for it in the control module.

In fact there will be two ways of using it (like with MSP):

• 12ch support using to DroneBridge RC packet (MAVLinnk message generated on the UAV side)
• 14ch support when the message is generated on the ground

I know the MAVLink message supports up to 18 channels but I doubt that most people need more than 14 channels. More channels create more collisions and most of the stuff they want to achieve is possible using the communication module and single messages.

[careyer]

Hi Wolfgang!

Wow! Did not know that Dronebridge already uses the MavLink v2 Libraries. That is terrific news! 👍 However I am happy that there was at least something new to my message after all (the new messages for more channels). :-)

This will solve a lot of problems and inconveniences.
And YES 12Ch (Dronebridge RC-packets) and 14Ch (transparent pass-through) is way enough.
Thanks for taking the effort to implementing the new messages!

Cheers!
Thomas

P.S: I am wondering if it might be possible to combine this with #18 ? Especially smaller Flight Controls (e.g.: Pixracer) have only very limited AUX outputs meaning that you cannot pass-through/route the additional channels out of your FC for example to drive some physical actuators. These channels are simply stuck in your FC this way. :-/

Maybe with the Dronebridge RC-packet approach it is possible to declare somewhere (ini-File or App-Settings) that either all channels go to the FC or some upper channels (e.g. Chx-Ch12) are split off and drive GPIOs instead? Just a stupid idea..... I mean something like:

Something like:
#rc = mavlink
#max_mavlink_ch = 12
--> all 12 channels go to the FC

#rc = mavlink
#max_mavlink_ch = 8
--> 8 channels got to the FC ... channel 9,10,12 will drive predefined GPIOs instead

Hopefully you can comprehend my non-coder freestyle sniplet... hihi

[careyer]

@seeul8er : If you need help in testing or anything please reach out to me! Cheers!

[careyer]

Dear Wolfgang, I skimmed through your commits and as far from what I can tell this should be supported now, is that correct? Is there any way to test this already? Thank you very much and have a great weekend.
CheerS!

[seeul8er]

Posted a test image here
My flight controller died so everything besides the video is untested for now.

On the Ground side you need to set:
rc_proto=5

On the Air side you need to set:
serial_prot=5

Everything is the same as usual. It might only work with a flight controller that supports that (newer) feature. The FC firmware needs to be compiled with the newer kind of MAVLink libs.
Happy testing :)

[careyer]

AWESOME! Thank you very much... will download the image an start testing right away!