Devo10 + Cleanflight AIL stick problem

Hi,

I have a problem with my devo10 & cleanflight, and it makes me crazy!
I configured the devo, and the channels works well, except the AIL channel.... When I move the stick to the end left, the receiver unbind (orangerx R620X v2 sbus).
What could be the problem??

Video:
www.dropbox.com/s/ld7tgmbxbfwhqvs/VIDEO0169.mp4?dl=0

Your link expired so I can't watch the video. Have you tried setting the DSMX protocol option to turn on the OrangeRX support? This is a new option you can see if you move to the protocol button and press enter.

If I enter to the protocol button, only have on/off telemetry...

Video link:

www.dropbox.com/s/k6vtquxtbygmush/VIDEO0169.mp4?dl=0

Deleted.

I thought that looked like something else, but of course you're using Sbus...

I noticed in your ini file that you've extended the scale from -117 to 118. Have you looked at the CF rxrange command instead? For my CF/BF birds Devo seems to start at 1159 and go to 1841, so i use the CLI command to adjust them: rxrange 0 1159 1841. This allows CF to see the range as being 1000 to 2000, which seems to get along better with the GUI.

There may be value in updating to the nightlies as the DSMX protocols offer the OrangeRX option. You could also use the Devo v5.0 protocol updates release that just updates the protocols.

The scale (-117-118), is for adjust the cleanflight range (1000-2000).
I used the drone before, with my devo10, stock module without problem....I changed the pcb, installed 4in1, and got the error....
The strange thing is that it just happens, only in the AIL channel and in the stick travel end..

What version Deviation are you running?

v5.0.0

Did I remember to ask if you've calibrated the Devo sticks since you added the board? Can't hurt to try that.

There are four major processor players in this problem, and you've shown that the FCU and receiver seem to get along (because they work well with the old different transmitter system). So you've changed one of the other players and this came about; it seems to me that it must have something to do with how the transmitter is using the new 4-in-1.

Have you tried creating a new model from scratch, adding the mixer elements, for a basic 5 or 6 channel multi-rotor? Leave out anything that you don't need for basic flight. If this symptom shows up at that point it would certainly imply that you have found a very sneaky bug.

First, thanks for help Deal57.

I calibrated the stick, and no works.. Then, I create a new model, and it seems to work!!
What I do not understand, is why the other one does not work well?? The firmware update corrupt the ini?
What's wrong in the ini? What is the error??

Very glad to have it working! Yeah, I have seen this sort of thing, and it has happened to me. I never found out the reason, and eventually removed and replaced the old ini with no further issues.

So now that the basics are working, you can try to add in any differences with the old ini just one at a time. Maybe that will identify the bad actor. For myself, I would just get out and fly!

Happy flying!

The working .ini, is a old copy (pc copy)
.... and the two versions that I have in the devo10 works bad....but both worked well before....very strange!!

Thanks for help Deal57!!
Happy flights too!!