OK, so it's not a channel mapping issue on your QX7 either. Everything is configured as it should be so unless there is some kind of hardware issue with the R9 Mini receiver then I'm not sure what is causing your issue. I would certainly try re-binding just to rule out any weird binding issue.

What version of Betaflight are you running?

It might also be worth trying to use SBUS protocol by connecting the SBUS_OUT and S.Port pads of the R9 Mini to separate UARTs and configuring Betaflight accordingly to see if that works. If you do that, don't forget to also untick the "F.Port" option on your transmitter.

(28-May-2022, 11:11 AM)SnowLeopardFPV Wrote: OK, so it's not a channel mapping issue on your QX7 either. Everything is configured as it should be so unless there is some kind of hardware issue with the R9 Mini receiver then I'm not sure what is causing your issue. I would certainly try re-binding just to rule out any weird binding issue.

What version of Betaflight are you running?

It might also be worth trying to use SBUS protocol by connecting the SBUS_OUT and S.Port pads of the R9 Mini to separate UARTs and configuring Betaflight accordingly to see if that works. If you do that, don't forget to also untick the "F.Port" option on your transmitter.

I have put my SPort on a TX5 pad, my SBus on a Rx1 pad, unticked FPort in my qx7, put  serial rx on uart 1 and frsky telemetry on uart 5, selected RX serie and SBUS in the configuration tab....
Do i have to put another command in the CLI??

I don’t know why it’s broken but maybe I did a short circuit or something...
I think I’ll just buy myself a new RX.
Thank you so much for helping me

If you are using the the RX1 pad for the SBUS_OUT connection and the TX5 pad for the S.Port connection, the following CLI commands will configure that to work correctly (assuming there isn't a hardware issue with the R9 Mini receiver)...

(28-May-2022, 05:18 PM)SnowLeopardFPV Wrote: If you are using the the RX1 pad for the SBUS_OUT connection and the TX5 pad for the S.Port connection, the following CLI commands will configure that to work correctly (assuming there isn't a hardware issue with the R9 Mini receiver)...

Code:

serial 0 64 115200 57600 0 115200
serial 4 32 115200 57600 0 115200
set serialrx_provider = SBUS
set serialrx_inverted = OFF
set serialrx_halfduplex = OFF
save

IT WORRRKEDDDDDDDD !!!!!
Thank you so much

No problem I can only guess there is some kind of firmware bug with the F.Port implementation on the firmware version you have installed on the R9 Mini receiver and/or the R9M module and/or the ISRM module in your QX7. The only disadvantage of SBUS/S.Port is that you use up two UARTs and the latency is ever so slightly higher, but nothing you are likely to notice. You also don't get RSSI values natively sent to the FC directly from the receiver so you need to configure that manually.

Make sure you are getting all the telemetry sensors showing up by doing a delete and re-discover of all the sensors against the model on your QX7. If you are then it means that both the SBUS and the S.Port data connections are working.

If you want RSSI values displayed in the OSD you will need to configure the RSSI telemetry value to be sent back to the FC on a spare channel. JB's video below walks you through how to do that...



Happy flying

(28-May-2022, 05:37 PM)SnowLeopardFPV Wrote: No problem I can only guess there is some kind of firmware bug with the F.Port implementation on the firmware version you have installed on the R9 Mini receiver and/or the R9M module and/or the ISRM module in your QX7. The only disadvantage of SBUS/S.Port is that you use up two UARTs and the latency is ever so slightly higher, but nothing you are likely to notice. You also don't get RSSI values natively sent to the FC directly from the receiver so you need to configure that manually.

Make sure you are getting all the telemetry sensors showing up by doing a delete and re-discover of all the sensors against the model on your QX7. If you are then it means that both the SBUS and the S.Port data connections are working.

If you want RSSI values displayed in the OSD you will need to configure the RSSI telemetry value to be sent back to the FC on a spare channel. JB's video below walks you through how to do that...



Happy flying

I don't have all the telemetry sensors 

(28-May-2022, 08:25 PM)Litchi Wrote: I don't have all the telemetry sensors 

Make sure you have the TELEMETRY option switched on in the Configuraton tab.

If you do but you still aren't getting all the expected telemetry sensors showing up then with neither an F.Port or an S.Port connection from the R9 Mini working it is making me begin to suspect faulty hardware on the S.Port / F.Port circuit of the R9 Mini receiver. If you need or want FC telemetry data then you are probably going to have to get a new replacement receiver.

(28-May-2022, 11:51 PM)SnowLeopardFPV Wrote: Make sure you have the TELEMETRY option switched on in the Configuraton tab.

If you do but you still aren't getting all the expected telemetry sensors showing up then with neither an F.Port or an S.Port connection from the R9 Mini working it is making me begin to suspect faulty hardware on the S.Port / F.Port circuit of the R9 Mini receiver. If you need or want FC telemetry data then you are probably going to have to get a new replacement receiver.

For the time being, I will do without telemetry. But allow me to stress the huge big thanks I'd like to give you, as you have been crucial for me not giving up and you have been incredible in addressing the issue and finding a solution. Again you are the best.