RSSI dbm was still good, LQ dropped to 70 and then RxLoss occured. FC is HM X1 with SPI receiver. Antenna connection was good visually (don't know the internal though)
TX is RM TX12-II Internal Elrs.
The quad flew normally for 2 batteries, this happened at the 3rd battery. Between batt 2 and 3, PID tuning was modified, but I can't recall which one.
What could be the culprit?
#HM Crux35 RxLoss at short range
16 messages · Page 1 of 1 (latest)
do you have VTX Admin set to a band/channel?
what versions do these devices have?
Version 2.5.0
that's the TX.. what about the whoop?
have you tried this in a much faster packet rate?
The whoop is SPI RX, I haven't check the betaflight version
Does it matter? I mean, faster packet rate will decrease the sensitivity limit right?
I just want to know whether it happens in other packet rates/rf modes
Ok, will try with other rate tomorrow. It's 21 o'clock here 😁
Having failsafe issues with an ELRS SPI FC? A few possible causes:
- Check antenna on FC for damage.
- Go into the ELRS lua, select VTX Administrator, and make sure Band is set to Off.
- Run the following commands in the CLI to help free up resources on the FC and prevent failsafes due to resource exhaustion:
set dshot_bitbang = off
feature -LED_STRIP
set cpu_overclock = 108MHZ
save
- Make sure dynamic power is enabled in the ELRS lua to avoid overheating your TX
- If your FC has an on-board VTX, run the minimum power you need and/or put VTX power on a switch so you can prevent the FC from overheating while the quad is stationary
Is there any issue regarding to VTX Admin in SPI FC?
there have been issues before that when vtx admin is set (Band is not Off), link drops happen
Only SPI FC or UART RX as well?
spi only
I see, I'll check it again
Xo offset is also more likely on an aio if they run hot