Differences

This shows you the differences between two versions of the page.

--- searchwing-wifibroadcast [2020/05/01 10:07] – [Tests] wf68spef
+++ searchwing-wifibroadcast [2021/04/19 13:03] (current) – [Mavlink-Transport] swrm
@@ Line 7: / Line 7: @@
 There are various projects that use the WiFi broadcast code:
+  * [[https://github.com/svpcom/wifibroadcast | svpcoms wifibroadcast]] most promising implementation feature wise
+  * [[https://github.com/booo/openwrt-wifibroadcast | OpenWRT package for wifibroadcast and a custom implementation of wifibroadcast]]
   * [[https://github.com/rodizio1/EZ-WifiBroadcast|EZ-WifiBroadcast]]
   * [[https://github.com/OpenHD/Open.HD|Open.HD]]
@@ Line 50: / Line 52: @@
 * QGC: New connection with TCP on Port 5000 - receives telemetry
+source tx and rx commands: https://github.com/booo/wifibroadcast/ ?
+==== Mavlink Routing ====
+Captured data needs to be sent from companion (connected to fc) to gcs.
+On the companion there might be also ROS needing access to mavlink messages.
+On the gcs side the sent data needs to be handled. QGroundControl can't handle that captured data -> needs additional software.
+Routing of pakets (ros|captured data processing)<*>companion<->fc<->radio<->gcs<*>(qgroundcontrol|captured data processing)
+- <*> routing to multiple endpoints
+- radio is long distance rfd868 or similar
+Parallel to the radio connection there might be a long distance wifi connection.
+(images|captured data processing)<*>companion<->wifi<->gcs<*>(qgroundcontrol?|captured data processing)
+open question: route (encapsulated) mavlink pakets also over wifi?
+depending on that: combine of images / captured data on gcs side - how?
+==== Captured Data Workflow ====
+TBD.
 ===== Tests =====