ExpressLRS Sudden LQ drop and RX loss at strong RSSI-dBm C++
As discussed on Discord a new issue for the record.
On two different occasions we encountered a sudden LQ drop and RX loss, while at close range with strong rssi-dBm. During these occasions my buddy and I where both in the air. (Only one affected at that moment.) The LQ drop goes in steps to zero and the link gets disconnected. In both cases the link reestablished itself with an LQ of 100.
Next flight, using a fresh LiPo, all is fine and we can fly together for 4KM out without issues. We fly both an AR.Wing 900 with iNav 3.0.2 installed. Both have an HM EP1 installed with ExpressLRS version 1.1.0 (The EP1's installed do NOT have the SDG regulator.)
Our 2.4GHz gear: I'm using a DIY 2400 TX (JR-Bay) My buddy uses the HM ES24TX (JR-Bay) We both have a Taranis QX7S with OpenTX v2.3.14 installed. (Both have the TBS inverter mod installed.)
We also often fly our ExpressLRS quads together, running Betaflight v4.2.9, without issues. (Both HM EP1's.)
Below the DVR recording of the events.
https://streamable.com/l9rva7 https://streamable.com/t3mk1y
If there is any more info needed, just ask.
6 Answer:
Excellent, thanks for the post with all the details in one place. This has all the symptoms of a Nonce sync slip, although I do not understand how not only can it happen once (which I never see) but happens over and over. I am going to try to update my long-run testing procedure for roughly the same LQ/RSSI conditions and to watch specifically for this behavior.
Here was the test I've run (all on master): * Pair 1: Q X7 with invertermod OpenTX 2.3.14 + SIYI FM30 (no antenna) 10mW 150Hz 1:8 / BetaFPV RX + Betaflight 4.2. Transmitter 10m away with RSSI around -70, LQ 90-100. Quad was "armed", to lock us out if the connection ever failsafes. * Pair 2: FR Mini as TX 10mW 150Hz 1:8 / EP2. Transmitter sitting right next to Pair 1's receiver for maximum interference.
Test was run for 18 hours. No LQ less than 75 was ever experienced (that's where the warning level was set) but I personally never saw anything less than 90 LQ in OpenTX telemetry.
Possible conclusions: * We don't have this issue on master * We don't have this issue on STM32 transmitters paired with ESP receivers * I'm just unlucky
I do not have an ESP32-based Team2.4 TX to test with so I can't think of anything else I can try.
If it makes any difference, my TX is always set at 250Hz, TLM 1:32. Advanced telemetry is enabled and 23 sensors are recorded.
Probably not related, but can you flash iNav 3.0 on that FC? We got unlucky twice when iNav 3.0 was in use. ¯_(ツ)_/¯
I wouldn't think the FC would come into play at all, since we're reporting the receiver LQ and I can't think of anything the FC can do to influence our received LQ. You're not running any sort of Lua script for telemetry are you?
.... You're not running any sort of Lua script for telemetry are you?
For sure not, banned Yaapu and the like a long time ago. I know the QX7S is very resource limited...
Here was the test I've run (all on master):
- Pair 1: Q X7 with invertermod OpenTX 2.3.14 + SIYI FM30 (no antenna) 10mW 150Hz 1:8 / BetaFPV RX + Betaflight 4.2. Transmitter 10m away with RSSI around -70, LQ 90-100. Quad was "armed", to lock us out if the connection ever failsafes.
- Pair 2: FR Mini as TX 10mW 150Hz 1:8 / EP2. Transmitter sitting right next to Pair 1's receiver for maximum interference.
Test was run for 18 hours. No LQ less than 75 was ever experienced (that's where the warning level was set) but I personally never saw anything less than 90 LQ in OpenTX telemetry.
Possible conclusions:
- We don't have this issue on master
- We don't have this issue on STM32 transmitters paired with ESP receivers
- I'm just unlucky
I do not have an ESP32-based Team2.4 TX to test with so I can't think of anything else I can try.
Are there differences on master vs 1.1.0? I have pretty much same symptoms on r9. I could give a try in master and retest the interference thing.
Read next
- Form - Enter key to submit form - JavaScript react-final-form
- Support 'transparent' as a acceptable color. - Java react-native-bootsplash
- /var/lib/dpkg/info/vernemq.postinst: line 11: syntax error near unexpected token `else' - Erlang vernemq
- Difference in puppet-lint behavior between `pdk validate` and `rake lint` - Ruby pdk
- http-ui only binds to localhost (127.0.0.1) - bettercap
- tdesktop Bug with opening context menu in KDE system tray - Cplusplus
- MyAccount :: Order Details :: Order Details by Order Number - PHP magento2
- .collect-file pollution in /tmp - Groovy nextflow