Howto connect the R-XSR RX to a flight controller and fix issues. Short description on how to get uninverted SBUS and S.Port signals.
Affi Link R-XSR goo.gl/7MwSvt
Transcript
This is the schematic of the R-XSR. Taking a closer look at the connector, starting from the bottom. The pins are: GND, +5V. In the middle is the S.Port pin for telemetry data. 4th pin is SBUS from the R-XSR to the flight controller. Top Pin is for the redundancy function of the R-XSR. The Slave RX SBUS Out is connected to this "SBUS_IN" pin.
The signal coming from the R-XSR is an inverted signal. In case we need the uninverted SBUS and S.Port Signal, we cannot use the connector pins. We'll talk about that later what we can do, if the inverted signal does not work for you.
After connecting the R-XSR with the FC according to the wiring diagram schematic, we connect the FC to the PC. We start the flight controller configurator software. In this case Betaflight is used. We now open the "Ports" tab. Here we configure the UART for steering of the craft vie the SBUS protocol and the S.Port for telemetry data.
I have connected SBUS OUT from the RX to UART1. Therefore I activate the "Serial RX" switch, which is already preselected because that is the default setting. Everything else in this row stays disabled.
I have connected the S.Port pin of the R-XSR to UART6. Choose S.Port from the dropdown menu. Do not use FrSky here, that is a different protocol. Klick the "Save and Reboot" button to make the changes permanent.
We now switch to the configuration tab to check the RX Settings. In the Receiver Section we make sure, that "Serial Based Receiver" is chosen from the dropdown menu and the SBUS protocol is chosen. We make sure that in the "Other Features" selection the "TELEMETRY" switch is activated. Otherwise the TX will not receive the telemetry data from the FC. Without that switch on, the TX will still be able to receive the basic telemetry data from the R-XSR. Such as RSSI and RX Voltage. Press "Save and Reboot" to make the changes permanent.
To verify that everything is working, we change to the "Receiver" tab and move the levers on the remote control. The bars in this tab should move accordingly. Of course, the TX and RX have to be bound and the TX has to be configured for this to work. We can switch the channel map here. We can also check on the TX if the telemetry data is sent. If everything works, we are fine.
If nothing happens, it could mean that the remote control is not configured. Option 1 is to check if the remote control is properly configured and bound to the RX. Or the inverted signal does not work for you and we need the uninverted signal.
2nd option would be to try to invert/uninvert the signal via the software. In the CLI type "get inv" to see all options for inversion. We see SBUS inversion and telemetry inverted. We can switch that from the current setting to ON or OFF. As a remark, I have never tried that for myself successfully. It seems to depend on the used FC. However, i show you how this is done. Type "set sbus_inversion OFF" followed by Save. After the reboot, the settings are permanent. We can try that also for telemetry. It's worth a try.
If option 1 and 2 did fix the issue, we still have a 3r option: we can use the uninverted signals. Thankfully the R-XSR has dedicated soldering pads for the uninverted SBUS Signal, labeled B, and S.Port signal labeled P.
To use these pads to get the uninverted signals the pads are pretinned. The wires are stripped off the silicone isolation just a tiny bit and pretinned as well. With the pretinning, we can just hold the wire to the pad and heat it up to make a good connection, no additional tin is required. To make it even more robust, put some hot glue on the connections and cables and put heat shrink on the R-XSR. That should to the job.
I hope that works for you. If you have any questions feel free to leave a comment.
Drohnen360: goo.gl/m776bm
Instagram: goo.gl/yaJC57
Twitter: goo.gl/xFTsv4
Facebook: goo.gl/DXYtx9
25 дек 2017
