Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
searchwing-wifibroadcast [2020/04/24 18:22] wf68spef [Mavlink-Transport] |
searchwing-wifibroadcast [2021/04/19 13:03] (current) swrm [Mavlink-Transport] |
||
|---|---|---|---|
| Line 7: | Line 7: | ||
| There are various projects that use the WiFi broadcast code: | 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/rodizio1/EZ-WifiBroadcast|EZ-WifiBroadcast]] | ||
| * [[https://github.com/OpenHD/Open.HD|Open.HD]] | * [[https://github.com/OpenHD/Open.HD|Open.HD]] | ||
| Line 36: | Line 38: | ||
| * Pi Sender: Send data via wifibroadcast from Serial input port data - Mavlink Data from FC | * Pi Sender: Send data via wifibroadcast from Serial input port data - Mavlink Data from FC | ||
| - | configure UART using for 9600 Baudrate: | + | configure UART using for 9600 Baudrate (or checkout your telemetry for correct Baud):Ìý |
| ''stty -F /dev/ttyAMA0 9600'' | ''stty -F /dev/ttyAMA0 9600'' | ||
| + | |||
| + | Send data: | ||
| ''./tx wlan0 < /dev/ttyAMA0'' | ''./tx wlan0 < /dev/ttyAMA0'' | ||
| Line 47: | Line 52: | ||
| * QGC: New connection with TCP on Port 5000 - receives telemetry | * 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 ===== | ===== Tests ===== | ||
| * 20MBit/s in the basement in Neukölln, distance 50cm, two omni antennas with unknown dBi | * 20MBit/s in the basement in Neukölln, distance 50cm, two omni antennas with unknown dBi | ||
| * 4MBit/s on Tempelhofer Feld, distance ~ 200m, unpatched kernel, txpower maybe not at max, both sides small omni antennas with unknown dBi | * 4MBit/s on Tempelhofer Feld, distance ~ 200m, unpatched kernel, txpower maybe not at max, both sides small omni antennas with unknown dBi | ||
| + | * unkown MBit/s, max. distance ~ 1km, esp 201 with 1-3dBi omni, ground station Nanostation M2, unknown tx power on both sides, normal wifi, no wifibroadcasting | ||
| + | * [[https://www.hs-augsburg.de/homes/beckmanf/dokuwiki/doku.php?id=searchwing-flug-107 | Testflight with 8XX MHz]] | ||
| ===== TODO ===== | ===== TODO ===== | ||