I am having an issue binding an XM+ transmitter to my Jumper T12 pro.

Jumper T12 pro OpenTX version 2.3.5
FCC and LBT version XM+ ACCST 2.1.2.

So right off the bat the XM+ would not go into binding mode, both red and green were solid lights. After a lot of research I found I needed to flash the firmware on the receiver so I did and it seemed successful but still no binding I tried both versions of the firmware and even changed between D16, D8 and the EU version of my module mode. One video I watched binded with the green light solid so I tried that as well with no luck, but most videos and info show if the green light does not blink it will not bind. I also read that someone tried alkaline batteries, where mine are 18650s, don't have the equipment to try that yet. Have made sure to fully charge the batteries.

Admittedly this is my first time trying to bind a receiver, I did bind it to a JJRC santa drone with no issues, but I am at a loss here. If I flash the reciever and put it into bind mode without turning on the transmitter will the green light flash? Any suggestions on this will be greatly appreciated and tried. I am using a 3.7 350 MAH batter with the receiver and I had it installed in the drone as well. My soldering skills are decent enough and I've soldered and unsoldered with same results so I don't think it's the connection. And flashing it seems to work find so i think the current solder job is good.


EDIT - Solution- There are two versions of the XM+ V1 and V2, V2 requires FrSky X2 which may require a module firmware update(module not radio) and even then depending on the version the receiver has versions as well. I had to update my module firmware and downgrade my receiver firmware and in the end everything worked out. Thank you all for the assistance.

Originally Posted by WolfSpring

I am having an issue binding an XM+ transmitter to my Jumper T12 pro.

Jumper T12 pro OpenTX version 2.3.5
FCC and LBT version XM+ ACCST 2.1.2.

So right off the bat the XM+ would not go into binding mode, both red and green were solid lights. After a lot of research I found I needed to flash the firmware on the receiver so I did and it seemed successful but still no binding I tried both versions of the firmware and even changed between D16, D8 and the EU version of my module mode. One video I watched binded with the green light solid so I tried that as well with no luck, but most videos and info show if the green light does not blink it will not bind. I also read that someone tried alkaline batteries, where mine are 18650s, don't have the equipment to try that yet. Have made sure to fully charge the batteries.

Admittedly this is my first time trying to bind a receiver, I did bind it to a JJRC santa drone with no issues, but I am at a loss here. If I flash the reciever and put it into bind mode without turning on the transmitter will the green light flash? Any suggestions on this will be greatly appreciated and tried. I am using a 3.7 350 MAH batter with the receiver and I had it installed in the drone as well. My soldering skills are decent enough and I've soldered and unsoldered with same results so I don't think it's the connection. And flashing it seems to work find so i think the current solder job is good.

I know the specs on xm+ say 3.7v but I'd try with a higher voltage, just in case.

I tried a 9volt and I tried using the 3S battery in the quad. My big question is if there is nothing else going on and you put the receiver in bind mode without any transmitter will the lights flash or stay solid? I have one other thought, is there anyway it could be the internal battery and the transmitter is not memorizing the bind? I don't see how that is possible, but I have to reset the failsafe every few times I turn on the transmitter, but it keeps all other settings. I did buy it used and it has worked great on the simulator and the other drone, but this receiver it doesn't seem to like.

The XM+ is rated for 3.7V~10V input power. If you applied a 3S directly to it, you may have damaged it. Generally, apply 5V to an Rx.

The XM+ needs the FCC firmware (not EU), with ACCST V1, not V2 or ACCESS, to bind to most multiprotocol Tx's, like the jumper. On the Tx, you're binding it in D16 mode. Binding procedure is dirt simple:

- Place Tx in Bind Mode.
- Hold the bind button on the XM+ and power it.
- Once bound, it should be a solid green, and blinking red LED's.
- Take the Tx out of Bind Mode if it's still in it.
- Power cycle the XM+, and confirm it's connected to the Tx.

If you haven't damaged anything by applying more than 10V power to the XM+, you're most likely dealing with a firmware issue. You need a FCC firmware, that is ACCST V1, not V2, not ACCESS. Tx needs to be in D16 mode.

Good luck.

Originally Posted by Ace12GA

The XM+ needs the FCC firmware (not EU), with ACCST V1, not V2 or ACCESS, to bind to most multiprotocol Tx's, like the jumper. On the Tx, you're binding it in D16 mode. Binding procedure is dirt simple:
Good luck.

This is simply not correct. The MPM fully supports all 4 of the common ACCST variants. Only ACCESS is not supported (and FrSky no longer supports the ACCESS firmware on the XM+ either, because it's not capable of running 7ms frame rates which are required for ACCESS aside from the initial v1.0 firmware)

To bind ACCST V1, pick FrSky and either D16 (for FCC) or LBT (EU) for LBT
To bind ACCST V2, pick FrSky X2 and either D16 (for FCC) or LBT (EU) for LBT

Than you all for the info.

I did not directly apply it to the 3S I had it soldered to the FC I think it's 5V.

As far as the protocol I was trying to upgrade my module firmware last night and running into issues. I did not see FrSkyX2. I flashed the XM+ with the FCC version and the LBT EU multiple times trying the different protocols to go with each on the radio. I will look into the X2 a little more today as that could be the problem.

My biggest confusion that a video has sent me in a rabbit hole is this.
All things being correct if you place the receiver into bind mode are both lights going to be solid or will one be flashing? One video and a forum post said if both were solid you have a firmware issue and have to switch/update it on the receiver I don't see how that is possible if the radio isn't even turned on how a receiver knows it has the wrong firmware...

When the XM+ binds successfully, you end up with a solid green LED and a flashing red LED. Once you power cycle and it connects to the Tx, I honestly forget what it does, but you get some activity from the LED's then too. I believe if you get 2 solid LED's, it's failed to bind. It won't stay in bind mode indefinitely, so when it drops out of bind mode, but is not bound, I believe you get the solid LED's.

I actually have a brand new XM+ here somewhere, I'll go through the binding process after work, and see what it does.

Originally Posted by mawz

This is simply not correct. The MPM fully supports all 4 of the common ACCST variants. Only ACCESS is not supported (and FrSky no longer supports the ACCESS firmware on the XM+ either, because it's not capable of running 7ms frame rates which are required for ACCESS aside from the initial v1.0 firmware)

To bind ACCST V1, pick FrSky and either D16 (for FCC) or LBT (EU) for LBT
To bind ACCST V2, pick FrSky X2 and either D16 (for FCC) or LBT (EU) for LBT

I think this is going to be the issue right here. I think I need to upgrade my firmware on my module watching the videos and seeing what version firmware they have it's either newer than mine r the videos is much older and probably the V1 XM+. I read something on multi protocol and said 64 should be FrSKy X2 and my 64 is blank so an upgrade will probably add it.

One step closer. I was able to upgrade the firmware to the module and switched to FrSky X2 and now when I attempt to bind the green light goes off and the red light stays solid, but still no bind. I am going to read and research the new issue, but this was the farthest so far so thank you all so much.

We have a winner! I had to revert the receiver firmware back to 2.1.0 and everything works just like it should. Took a second though as my receiver was to close to the transmitter and having issues. Than you all again!