Flysky2A support is broken in v1.3.4.63

[caall99]

Flysky2A is broken in latest version, namely v1.3.4.63. This goes for both the internal module and external 4-in-1 module on the Jumper T16. Issue was made apparent when trying to bind to a Eachine Trashcan drone with Crazybee F4 Pro (with SPI Flysky2A receiver). The issue may exist in earlier versions, but v1.3.3.7 works perfectly with the same configuration.

Edit: removed mention of DSMX issues for now, as there are potential other issues at stake with my DSMX receiver.

[caall99]

I just confirmed its only the latest v1.3.4.63 that is having issues with Flysky2A. I rolled back to the previous version v1.3.4.31 and it works fine now.

[pascallanger]

What's not working ?

[caall99]

What's not working ?

It seems to bind, but keeps my drone in a permanent fail safe condition, with the drone reporting "RX LOSS" and the transmitter warning me on poor connection and/or no connection frequently. I am unable to have any succesful control response with the newest version. This is specifically Flysky2A.

[pascallanger]

Have you redone a bind?

[caall99]

I have tried to bind and rebind multiple times, changing receiver numbers and sub protocols. I don't know how else to explain other than what I wrote above... It binds perfectly, instantly and trouble free with every other version that I have tested - but, will not work with the latest v1.3.4.63. It cannot sustain a connection, and is in a constant fail safe state.

Something broke in these updates:
AFHDS2A/Gyro_Off/Gyro_On/Gyro_On_Rev
New sub protocols for BS4/BS6 surface receivers
AFHDS2A
Fix for CROSSOVER-RX

[pascallanger]

For the latest working version (I assume v1.3.4.31), can you try to select the same sub protocol you are currently using but instead use the one ending with "16"? (example: PWM,IBUS -> PWM,IB16). Does it work?

[caall99]

For the latest working version (I assume v1.3.4.31), can you try to select the same sub protocol you are currently using but instead use the one ending with "16"? (example: PWM,IBUS -> PWM,IB16). Does it work?

I just tried switching from PWM,IBUS -> PWM,IB16 on 1.3.4.31 and rebinding the drone. I pressed "Bind" on my transmitter and sent "bind_rx" in CLI of BetaFlight. It did bind, but it is stuck in "failsafe" and cannot see any control inputs on the Receiver tab of BetaFlight. This appears to be the same issue I was having in 1.3.4.63.

[pascallanger]

Ok it can mean 2 things:

• your receiver is not 16 (18) channels compatible "yet" and you must likely need a software update
• you haven't changed the RX lqi from channel 16 to 17 (or something like this check the doc)

[caall99]

Ok it can mean 2 things:

• your receiver is not 16 (18) channels compatible "yet" and you must likely need a software update
• you haven't changed the RX lqi from channel 16 to 17 (or something like this check the doc)

Sorry, but I don't see how this helps. My Rx is a built in SPI receiver on my AIO flight controller, I cannot upgrade software on it.

Why am I forced to change the LQI channel in v1.3.4.63, but not in v1.3.4.31? I don't use the 16 channel option sub protocol to make my Rx work in v1.3.4.31, why can't it be the same in v1.3.4.63?

[pascallanger]

Sorry, but I don't see how this helps. My Rx is a built in SPI receiver on my AIO flight controller, I cannot upgrade software on it.

By updating betaflight or whatever flight controller software you are using you will upgrade your RX since it is all in software. But that's probably not your issue, my guess is that you just need to change your config of lqi from 16 to 17.

Why am I forced to change the LQI channel in v1.3.4.63, but not in v1.3.4.31? I don't use the 16 channel option sub protocol to make my Rx work in v1.3.4.31, why can't it be the same in v1.3.4.63?

That's how it is, need to make things evolve to implement other features.
No one is forcing you to upgrade to the latest version, stay on 1.3.4.31 if you don't want to change anything.