summer oxide
Yes, I know...
I found my old F3 whoop that I practically considered dead. Didn't even remember why. Motors worked fine to my surprise, and it would even arm at first. But when it would arm, it would throw an RXLOSS error a few seconds after.
I remembered that I broke the bind button on it, and that was likely making it act weird. So I cut the half-open button off, cleaned off the pads, and am now trying to bind it again, to no avail:
- Tried 3.5.7 and 4.1.1 Performance Edition
- Tried FrSky_D and FrSky_X in the configurator
- Tried D8 and D16 on the radio
- Made sure that the XJT module is flashed with ACCST V1 firmware, flashed it like 3 or 4 times
- Manually setting
feature RX_SPIin the CLI because the stock settings had it disabled for some reason
I got it to bind once, but then something weird happened with the receiver channel bars being gone and the RX status LEDs being off completely. Almost like with cloud builds but this can't be anywhere near that. Trying to change the receiver settings in this state with 3.5.7 leads to nothing being saved, when using 4.1.1 it saves but doesn't affect it at all
Me and @willow fern have never seen anything like this before, I thought I'd try here too... but it is probably a more esoteric issue
misty root
molten yew
