Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FrSkyX2/D16 bug: binding an XM receiver won't work anymore since 1.3.3.33 #987

Open
egonl opened this issue Jun 6, 2024 · 2 comments
Open

Comments

@egonl
Copy link

egonl commented Jun 6, 2024

While binding a FrSky XM or XM+ receiver works fine in 1.3.3.20, I can't get a successful bind in 1.3.3.33 or 1.3.4.0.

Steps to repeat:

  • Flash 1.3.3.33 or 1.3.4.0
  • Power up the XM while holding the bind button. The LED stays solid red
  • Press Bind on the transmitter
  • The LED stays solid red. If binding is successful, it should start blinking.

Equipment used:

  • FrSky XM ACCST 2.1.2 FCC
  • Taranis Q X7 on OpenTX 2.3.15
  • iRangeX IRX4+ with Multiprotocol 1.3.3.33 or 1.3.4.0
@rogerq
Copy link

rogerq commented Aug 22, 2024

I confirm this issue exists even on EU LBT version.
I suspect the commit that updated bind sequence to support newer receivers like Archer series broke XM+

commit a41123d "FrSky Archer Bind"

@frankiearzu
Copy link
Contributor

Same issue, bind with older version of the MM firmware, but not with the latest one.. I agree with @rogerq that the point where is broke is on the "FrSky Archer Bind" changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants