searchwing-wifibroadcast

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
searchwing-wifibroadcast [2020/04/24 10:34] – [WiFI Broadcast] wf68spefsearchwing-wifibroadcast [2021/04/19 13:03] (current) – [Mavlink-Transport] swrm
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 26: Line 28:
 **We don't need a patched kernel to set the bitrate!** **We don't need a patched kernel to set the bitrate!**
  
 +[[https://wireless.wiki.kernel.org/en/users/Drivers/ath10k/debug#manual_bitrates_configuration|Manual bitrate configuration for ath9k/10k]]
  
 +===== Mavlink-Transport =====
 +
 +* optional: Simulate FC-MAVLink-Data on PC - using  Ardupilot SITL on UART output:
 +
 +see [[https://www.hs-augsburg.de/homes/beckmanf/dokuwiki/doku.php?id=multicamera_pixracer_connection#sitl_computer_simulated_pixracer_pi4|SITL]]
 +
 +* Pi Sender: Send data via wifibroadcast from Serial input port data - Mavlink Data from FC
 +
 +configure UART using for 9600 Baudrate (or checkout your telemetry for correct Baud):
 +
 +''stty -F /dev/ttyAMA0 9600'' 
 +
 +Send data:
 +
 +''./tx wlan0 < /dev/ttyAMA0'' 
 +
 +* Groundstation station receiver side: Receive wifibroadcast data and pipe into QGC:
 +
 +''sudo ./rx wlp0s29u1u2 2> /dev/null | nc -l 5000''
 +
 +* 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 =====
  • searchwing-wifibroadcast.1587717249.txt.gz
  • Last modified: 2020/04/24 10:34
  • by wf68spef