edgeflyer30
New User
I have several FRsky V2 access rxs such as sr10 pro. All bound before I did an isrm update ( through ethos suite) on my FRsky X20 (not x20r s or pro) to 3.0.3. I did this because I purchased a FRsky rf007 flight controller with built in Archer Plus RS. It's updated firmware is 3.0.3.
Now... Not only does the Rx in the rf007 refuse to register or bind, neither do my V2 rxs.
So I took back the X20 to 2.0.2 from a backup. Then installed Accst firmware for the archer plus rs using a file from frsky-rc.com
Now my old rxs bind in Access again.
And the RF007 can bind using Accst. But in rotorflight installed in the RF007 with default settings serial Rx on the internal uart and receiver type futaba s bus I get no stick response. Also tried FRsky Fbus protocol with no difference. Invert/ non invert signal no difference.
What a mess! Going off FRsky! Maybe back to ELRS with an external module.
Now... Not only does the Rx in the rf007 refuse to register or bind, neither do my V2 rxs.
So I took back the X20 to 2.0.2 from a backup. Then installed Accst firmware for the archer plus rs using a file from frsky-rc.com
Now my old rxs bind in Access again.
And the RF007 can bind using Accst. But in rotorflight installed in the RF007 with default settings serial Rx on the internal uart and receiver type futaba s bus I get no stick response. Also tried FRsky Fbus protocol with no difference. Invert/ non invert signal no difference.
What a mess! Going off FRsky! Maybe back to ELRS with an external module.
