<p>Since you connected power to the SBUS pad it is possible that the inverter that sits between the SBUS pad and the UART pin on the microcontroller is fried.</p>
<p>To get around this, I would suggest connecting SBUS to another RX pad. However, since SBUS is an inverted protocol, you will first need to get the uninverted signal somehow. There are two ways to do this with the XM+ (other SBUS receivers have similar methods). The first option is to solder the wire that goes to the RX pad to the leg circled in red in the image below.
<a href="https://i.sstatic.net/jqjhU.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/jqjhU.png" alt="Underside of XM+ receiver with uninverted SBUS pad circled in red" /></a>
<a href="https://www.getfpv.com/learn/fpv-diy-repairs-and-mods/get-uninverted-sbus-frsky-receivers/" rel="nofollow noreferrer">source</a></p>
<p>The other option is to build your own inverter using a transistor and two resistors.
<a href="https://i.sstatic.net/RfKby.jpg" rel="nofollow noreferrer"><img src="https://i.sstatic.net/RfKby.jpg" alt="SBUS inverter wiring diagram" /></a></p>
<p><a href="https://oscarliang.com/sbus-smartport-telemetry-naze32/" rel="nofollow noreferrer">source</a></p>
<p>The first option is probably the easiest if you feel confident enough to solder to that small pad, but it does come with an increased risk of damaging the receiver.</p>

CC BY-SA 4.0
2021-04-19T18:16:35.997Z
Wow! Thank you so much!!! I chose the first option and it worked perfectly. I've been working to fix that problem for weeks and your solution fixed it instantly. Thanks again!
drew.ss
CC BY-SA 4.0
2021-04-19T18:33:53.427Z
I'm just happy to help. Glad it worked!
Hannes Hultergård
CC BY-SA 4.0
2021-04-13T17:49:09.320Z
2021-04-13T17:49:09.320Z
Hannes Hultergård
<p>I'm very new to making drones, so sorry in advance for lack of proper terminology or if this is a dumb question. I've bound my xm+ to my transmitter (solid green light showing on receiver), but for some reason my inputs aren't showing up in betaflight. I have the correct serialRX activated on the correct UART (and have also tried both) and my receiver mode and serial receiver provider are set correctly (to serial based receiver and SBUS, respectively). This problem arose after I accidently connected my receiver to my flight controller backwards, and have already tried replacing the receiver, as I thought I might have fried my XM+, but that didn't solve the issue. Any help is much appreciated!!</p>

CC BY-SA 4.0
2021-04-12T06:55:44.460Z
Initially connected backward how so? Do you mean you just switched VCC and GND or did the accidental miswiring also make other incorrect connections?
ifconfig
CC BY-SA 4.0
2021-04-13T09:15:43.133Z
Which flight controller do you have? And where have you connected the receiver? SBUS can be a bit tricky on F4 flight controllers since it is an inverted protocol. It needs to be connected to a dedicated SBUS pad in that case. Did it work in this exact configuration before?
Hannes Hultergård
CC BY-SA 4.0
2021-04-13T17:03:58.697Z
@ifconfig I essentially turned the xm+ around when connecting. So I switched the power and the sbus connection, but the middle ground wire was still connected to the same spot
drew.ss
CC BY-SA 4.0
2021-04-13T17:08:30.517Z
@Hannes Hultergård I have the JHEMCU GHF411 Pro. The configuration I currently have it connected in is the same configuration as the one that worked before. There’s a pretty clear wiring diagram for the flight controller, which I properly followed.
drew.ss
<betaflight><transmitter><receiver><frsky-xm+>
XM+ bound to FRSKY x9 lite, but commands not showing up in betaflight
drew.ss
# XM+ bound to FRSKY x9 lite, but commands not showing up in betaflight

(Asked by: username_0 on 2021-04-10)

I'm very new to making drones, so sorry in advance for lack of proper terminology or if this is a dumb question. I've bound my xm+ to my transmitter (solid green light showing on receiver), but for some reason my inputs aren't showing up in betaflight. I have the correct serialRX activated on the correct UART (and have also tried both) and my receiver mode and serial receiver provider are set correctly (to serial based receiver and SBUS, respectively). This problem arose after I accidently connected my receiver to my flight controller backwards, and have already tried replacing the receiver, as I thought I might have fried my XM+, but that didn't solve the issue. Any help is much appreciated!!

**Tags:** betaflight, transmitter, receiver, frsky-xm+
> **Comments:**
> **username_1**: Initially connected backward how so? Do you mean you just switched VCC and GND or did the accidental miswiring also make other incorrect connections?  
> **username_2**: Which flight controller do you have? And where have you connected the receiver? SBUS can be a bit tricky on F4 flight controllers since it is an inverted protocol. It needs to be connected to a dedicated SBUS pad in that case. Did it work in this exact configuration before?  
> **username_0**: @ifconfig I essentially turned the xm+ around when connecting. So I switched the power and the sbus connection, but the middle ground wire was still connected to the same spot  
> **username_0**: @Hannes Hultergård I have the JHEMCU GHF411 Pro. The configuration I currently have it connected in is the same configuration as the one that worked before. There’s a pretty clear wiring diagram for the flight controller, which I properly followed.  

---

## 1 answers

### Answer by username_2 on 2021-04-13. Score: 2 | Accepted answer

Since you connected power to the SBUS pad it is possible that the inverter that sits between the SBUS pad and the UART pin on the microcontroller is fried.

To get around this, I would suggest connecting SBUS to another RX pad. However, since SBUS is an inverted protocol, you will first need to get the uninverted signal somehow. There are two ways to do this with the XM+ (other SBUS receivers have similar methods). The first option is to solder the wire that goes to the RX pad to the leg circled in red in the image below.
[![Underside of XM+ receiver with uninverted SBUS pad circled in red](https://i.sstatic.net/jqjhU.png)](https://i.sstatic.net/jqjhU.png)
[source](https://www.getfpv.com/learn/fpv-diy-repairs-and-mods/get-uninverted-sbus-frsky-receivers/)

The other option is to build your own inverter using a transistor and two resistors.
[![SBUS inverter wiring diagram](https://i.sstatic.net/RfKby.jpg)](https://i.sstatic.net/RfKby.jpg)

[source](https://oscarliang.com/sbus-smartport-telemetry-naze32/)

The first option is probably the easiest if you feel confident enough to solder to that small pad, but it does come with an increased risk of damaging the receiver.

> **Comments:**
> **username_0**: Wow! Thank you so much!!! I chose the first option and it worked perfectly. I've been working to fix that problem for weeks and your solution fixed it instantly. Thanks again!  
> **username_2**: I'm just happy to help. Glad it worked!  

---

