Hi everyone!

After enjoying my tiny whoop a few months finally I bought a Diatone Roma F5 6S. But my XM+ won't bind to the tx16s. Before soldering the XM+ to my Roma F5's FC, I flashed the "XM+_ACCST_2.1.2_LBT_RSSI16" firmware to the XM+. I tried with "FrskyX2 LBT(EU)" protocol on the tx16s since the information here says: "FrSky receivers running ACCST v2 firmware should use the FrSkyX2 protocol - they are not supported by this protocol." I tried other protocols too. When I keep the tiny button on XM+ pressed and plug in the battery, both green and red lights light up solid. So, no solid green and flashing red light as it should be. What could be the problem?

Apart from this problem, the quad makes a short popping noise the moment I plug in the battery. I can't determine where it comes from but it sounds like it comes from the XT60 plug. Is that possible? After plugging and unplugging the battery many times I noticed that more and more black marks started to appear on the XT60 plug of the battery. Is that normal?

Thanks for your help.

Try flashing the receiver with the FCC 1.3V ACCST firmware. Then using just the normal ASSCT protocol on the RM.

As for the sound, it is coming from the XT60. it is the sound created by the electric arc. You can replace the XT60 with an antispark one if the pop makes you uneasy.

(19-Mar-2021, 05:22 PM)voodoo614 Wrote: Try flashing the receiver with the FCC 1.3V ACCST firmware. Then using just the normal ASSCT protocol on the RM.

As for the sound, it is coming from the XT60. it is the sound created by the electric arc. You can replace the XT60 with an antispark one if the pop makes you uneasy.

Thanks for the reply.

The only older firmware on the website is called "XM+FCC170313-RSSI16". Would this one be OK?

I don't mind the pop as long as it doesn't mean something is wrong. I just didn't know if it (black marks and sound) is common and nothing to worry about.

Yes, try that firmware.

I tried it and it is working now. And I also discovered that the connection drops if the radio is to close to the receiver. I wonder if that's why it didn't bind when I had the newer firmware. But I guess not, because the radio and the receiver were close also when I tried with the older firmware and the bind has been successful.

The connection will drop at very close range. That is normal. Glad it worked.