FRSky ACCST V2.1.x protocol support

Looks to be the FRSky ACCST V2.1.x protocol has been implemented with initial support for the Multiprotocol Module last days.

github.com/pascallanger/DIY-Multiprotocol-TX-Module

Is there any work planned to add support of this protocol version to Deviation? Is someone already working on this?

Looks to be there are potential issues with the Version 1.0 FRSkyX protocol in environments with high 2.4GHz traffic. In my understanding all the FRSky transmitter will not support V1.0 protocol anymore after the update to V2.1.x. All receivers need to be upgraded also to V2.1.x. There was also an intermediate V2.0.x which is not compatible with V2.1.x.

This is one more positive point for using Deviation since this can support both protocols with the same transmitter.

I made an pull request with initial support based on the code of the MPM. Many thanks to the MPM team for there work.

github.com/DeviationTX/deviation/pull/978

Now 4in1 supports FrSky R9. github.com/pascallanger/DIY-Multiprotocol-TX-Module/issues/303 . Can the deviationtx support the FrSky R9?

Looks to be the FrSky R9 protocol needs an extra RF module to work. This is actually not part of the available 4 in 1 module.

i have problems with an XM + receiver:
with accst 2.1 i can't bind,
with old fw i have several filesafe up close, and bad link further away,
is there a better firmware for this ficevente?
or fw for the radio? (jumper t8sg v2 plus Nightly Builds 2020-05-05 )

thanks

I tried all the available firmware, obviously not access.
nightly build 05 05 2020
all 2.1 (fcc lbt etc) don't bind,
170313 ... yes but it has failsafe problems nearby, and low link quality even far away.

maybe the problem is in the nightly build?

With nightly starting 5.5.2020 the XM+ should be able to bind in any mode. I tested all four options with multiple XM+ and R-XSR receivers. You may need to adjust your Freq-Fine setting. For me about -45 is an valid choice and the default of 0 is giving my very unstable bind and connection with some receivers. This value will be individual for each 4in1 module. Please read the instruction how to adjust this setting properly with original FrSky receivers. Not optimal setting here can lead to a short range of your connection and bad bind behavior.

thanks a lot mj666, i know freqfine ,, i check it often, and it's the first thing i tried. with firmware 170313 ... is -38, so I assume it is also for firmware 2.1, but has no intention of making the bind.

ahhhh ok!!!!
thanks

You should see the new settings for Version and Bind Mode in the protocol options for FrSkyX and use them to chose the ACCST version you want to bind to.

wooowww yessssss i see the new setting!!!
I will try to re install 2.1 in the receiver and see if it works!

I noticed that this time DFUSE USB UPGRADE can no longer see the radio in dfumode, the drivers are correct, I had to use deviationuploader.jar.

mj666 wrote: You should see the new settings for Version and Bind Mode in the protocol options for FrSkyX and use them to chose the ACCST version you want to bind to.

ok, I installed fw 2.1 on the XM+ it works!
i tried lbt and fcc.

I still have the same flaw: near failsafe, at this point I think it is the receiver with some flaw.
I will try to wash it well with alcohol....mah

the developers are fantastic to have found the solution to frsky's bad choices. thanks