Current Behavior
RXLOSS and twitches
Steps to Reproduce
- compile the firmware on Windows11
- flash both TX and RX to privacylrs3.5.3
- fly normally
Possible Solution (Not obligatory)
Details
I definitely love the initiative! I wish I could give more information, but we have what we have. Two 5 inch quads, both use different FCs and ESCs, but identical ELRS RX model, same type of antenna. Two different radios. All TX and RX are flashed with privacylrs3.5.3. TX are set to 50Hz, 50mW, telemetry ratio standard, switch mode wide, link mode normal. RX set to follow TX power settings. In Betaflight, the corresponding RC_LINK profile is applied (50Hz, freestyle). Any combination of RX-TX regardless of location-distance-power exibit the same behavior: multiple rxloss, few times per minute there is a freeze of RC commands, which sometimes turns into a twitch of all stick inputs to different values for duration up to 200 ms or longer, some of the longer ones resulting in entering failsafe stage1 (set angle mode and throttle). The one at the end of the log caused a crash. If TX is set to dynamic power, it correctly detects rxloss and bumps up the power and rolls it back, but it makes no difference anyway.
Then I made a single change, flashing the official 3.5.3 to one TX-RX pair,. After that there is not a single rxloss, let alone any of the problems above. I hope this helps, I wish we all have encrypted telemetry.
Maybe there's something I'm doing wrong? I do not have a lot of experience with FPV and just started the hobby.
privacylrs3.5.3:
official 3.5.3:
Your Environment
The compilation didn't succeed out of the box, so I made a change to src/targets/common.ini, swapped the NimBLE-Arduino and ESP32-BLE-Gamepad lines in lib_deps definition.
I flew 10-300 meters distance, different locations, but the problem behavior is the same.
- TX hardware: Jumper AION Nano 2.4GHz TX
- RX hardware: GEPRC Nano 2.4GHz PA100 RX
- Handset model: Jumper T-pro
- EdgeTX 2.11.1
- ExpressLRS version (TX & RX MUST MATCH): 3.5.3
- Packet Rate: 50Hz
- Telemetry Ratio: std
- user_defines:
Current Behavior
RXLOSS and twitches
Steps to Reproduce
Possible Solution (Not obligatory)
Details
I definitely love the initiative! I wish I could give more information, but we have what we have. Two 5 inch quads, both use different FCs and ESCs, but identical ELRS RX model, same type of antenna. Two different radios. All TX and RX are flashed with privacylrs3.5.3. TX are set to 50Hz, 50mW, telemetry ratio standard, switch mode wide, link mode normal. RX set to follow TX power settings. In Betaflight, the corresponding RC_LINK profile is applied (50Hz, freestyle). Any combination of RX-TX regardless of location-distance-power exibit the same behavior: multiple rxloss, few times per minute there is a freeze of RC commands, which sometimes turns into a twitch of all stick inputs to different values for duration up to 200 ms or longer, some of the longer ones resulting in entering failsafe stage1 (set angle mode and throttle). The one at the end of the log caused a crash. If TX is set to dynamic power, it correctly detects rxloss and bumps up the power and rolls it back, but it makes no difference anyway.
Then I made a single change, flashing the official 3.5.3 to one TX-RX pair,. After that there is not a single rxloss, let alone any of the problems above. I hope this helps, I wish we all have encrypted telemetry.
Maybe there's something I'm doing wrong? I do not have a lot of experience with FPV and just started the hobby.
privacylrs3.5.3:
official 3.5.3:
Your Environment
The compilation didn't succeed out of the box, so I made a change to
src/targets/common.ini, swapped theNimBLE-ArduinoandESP32-BLE-Gamepadlines inlib_depsdefinition.I flew 10-300 meters distance, different locations, but the problem behavior is the same.