Hi there.
One of the people that flashed your custom firmware and I must say I'm impressed by your work. Is just awesome.
I would only dare to ask if possible to add a minimal telemetry so that the TX is also aware of the RX.
As it is now, the TX kinda knows about binding, but after that it acts like there is no RX it is talking to. On my Turnigy i10 remote, the RX icon is with a red mark, like there is no RX.
Is it possible to make the TX knows about RX?
In some custom RX firmwares, like Fli10/Fli10+, the RX is doing a little trick, right after connecting with the TX it is sending for a short time (like half a second), a fake low RSSI signal, so the TX will buzz shortly, so you know both are paired right away.
Just curious, when doing the pairing, how is the TX knowing the RX was paired in code? I looked through the code and didn't find that place. When I put my TX in pairing mode, after the pairing is done, the TX menu for pairing is closing automatically.
Hi there.
One of the people that flashed your custom firmware and I must say I'm impressed by your work. Is just awesome.
I would only dare to ask if possible to add a minimal telemetry so that the TX is also aware of the RX.
As it is now, the TX kinda knows about binding, but after that it acts like there is no RX it is talking to. On my Turnigy i10 remote, the RX icon is with a red mark, like there is no RX.
Is it possible to make the TX knows about RX?
In some custom RX firmwares, like Fli10/Fli10+, the RX is doing a little trick, right after connecting with the TX it is sending for a short time (like half a second), a fake low RSSI signal, so the TX will buzz shortly, so you know both are paired right away.
Just curious, when doing the pairing, how is the TX knowing the RX was paired in code? I looked through the code and didn't find that place. When I put my TX in pairing mode, after the pairing is done, the TX menu for pairing is closing automatically.