Mavlink 2 support
RespawnDespair opened this issue · comments
Change library to mavlink v2 in all repositories and recompile.
Where will things like the mavlink library, mavlink header files, etc. be kept? A lib directory and an include one should be enough. Any builds would just point to those. You did a great job on the image_builder btw!!
@RespawnDespair
Is this related to MavLink 2.3 support from careyer/dino.de ?
Are you coordinated with them ?
I am happy to see this feature on the list. Please reach out to me if any help is needed. Introducing MavLink v2 was not just a matter of recompiling it with new headers. dino.de struggled a long time because there was a buffer overflow error somewhere after the recompile which resulted in a non working build. He hunted this down with a logic analyser for several days.
Also the concept of Ground- and AirSwitches nicely integrates with it and makes full use of the 24Channels that are read as an input from the Joytsick/Taranis.
For your convenience (and because it got confused with the russian image lately) I will once again include the link to the "dino.de" image with all MavLink related stuff already working: https://www.dropbox.com/s/yzavlwsfrcbys57/EZ-Wifibroadcast-1.6RC6_FlirOneG2_v0.9_omxh264_MavLinkv2_GPIO.img?dl=0
Maybe you can use it as a blueprint and template or simply to cross-check
Cheers!
Thank you very much, i have been asking around for that image!
Is there any way to reach dine.de directly?
@RespawnDespair : You are welcome! He also has a Github Account https://github.com/dino-de . He has little time now to code because of family reasons but he said he would be there and happy to answer any questions. Maybe you can invite him to the repository or something to get in contact? Otherwise I can shot him a message.
I'll contact him trough github. I'll analyze the image first and then see what questions remain.
Thanks!
Great! for the changes made to .profile you might want to search for the keywords "switch" or "switches" (this is the GroundSwitches mimic - in this image it switches between two video streams that are transfered in parallel in videofifo1 and videofifo5) and for "airswitches" (this is the GPIO mimic for the AirPi . in the image it switches the AirPi GPIOs 17 and 18 via the Channels 15 and 24 I believe.) Pretty straight forward. All the Mavlink stuff should be reflected by changes in the filesystem.
tested and works perfectly with the modified arducopter firmware by @dposea. Now the Ardupilot side can also support up to 16 channels instead of 8! Awesome!!! Also all ArduPilot specific functions now work like a charm because MAVlink2 includes plattform specific message types and extentsions.
I asked dino.de. It is totally fine for him if you ask him.... I can share his email when needed
It looks like you already picked up most of his code changes. I'm testing a different version of the rtl8812au driver using the image builder image from a few days ago. It was working on the airpi side to transmit video. I have not tried any other functions yet because I'm busy trying to build non chibios versions of ardupilot, and having problems. I think I understand the build system and it looks like they just replaced nuttx. You cant just check out something like plane 3.9 either. All of the submodules need to be checked out separately, but on the same day and close to the time of plane 3.9 (example) . Otherwise the code needed for the build doesn't match.
Mavlink2 is already in roor/wifi broadcast on bortek. It looks like wifibroadcast_rc was updated also.
I'm testing a different version of the rtl8812au driver using the image builder image from a few days ago. It was working on the airpi side to transmit video.
What version ? 5.3.4 ?
I have updated all repos to build using the latest Mavlink v2 libraries.
This is all in the 'staged' branche of the image builder.
I will release a new test image a.s.a.p.