Closed Yes21 closed 6 years ago
Is this related to "do not set bitrate for Ralink, Mediatek, Realtek, done through tx parameter",except for ath9k_ht drivers? https://github.com/bortek/EZ-WifiBroadcast/blob/26514f7d6d7f7ec42e3d16e98a4b164f6bd4870e/wifibroadcast-scripts/profile#L307
@zipray
Is this related to "do not set bitrate for Ralink, Mediatek, Realtek, done through tx parameter",except for ath9k_ht drivers?
Where did you find this advice ?
@zipray Ok, Thanks.
I create a new issue in order to share our experiences about the mysterious behavior of uplink telemetry. I did many testings for a week, and had many difficulties to have reproducible results :
My different use cases are following :
In any use cases did the uplink telemetry work at the first time ... After many tries, I've noticed that I had to reboot the groundPi one or two times until uplink telemetry could perfectly work (changing flight modes, arming, doing calibrations, uploading waypoints) !!
The problem (uplink telemetry never works at the first time) and the "solution" (reboot the groundPi one or two times) are reproducible for me independently of the connection mode (wifi hotspot, USB tethering, Ethernet hotspot), and of the EZ-WBC version (1.6RC6 or 2.0beta).
Is anybody able to reproduce this "solution" ? ... and to explain it ?
Ps: : As I can't see any behavior difference for uplink telemetry between 1.6RC6 and 2.0beta, I can't confirm that 2.0beta has Mavlink2 support ...