setting channel endpoints / range

Hello,
I had to flash the new firmware on the SP RACING F3 evo brushed DSM2 of my Fatbee FB90,
Previously I had some hard times trying to assign and set switches for ARM and FMOD using complex in the mixers; it works but I was not satisfied.
So I decided to assign a different switch for arming and also to use Expo&DR in the mixer instead of Complex for both ARM and FMOD, it works fine.

I'd like to set endpoints and range of every channel to 1000 and 2000 but I can't increase more than 1852. It's fine to go below 1000 using scale and subtrim in the DEVO but I can't increase more than 1852. I don't know which setting to change in CleanFlight or in the DEVO.

I also installed a buzzer some times ago, it was beeping when the board was unarmed, pretty useful when crashed flying fpv to find the quad. The buzzer sounds while arming or changing flight mod,etc... but no more when unarmed, I have to switch off the transmitter to make it sounds. Which command do I need to enter into the CLI tab to make it sounds when unarmed?

Last thing, my board is DSM2. Banggood says it's 6 channels but the mixer tab into the DEVO shows 7 channels. I tried to assign a switch to this channel 7 without result and no switch reacts when toggling in CleanFlight.

Thanks for your help.

Take a look at this and the referenced threads.

www.deviationtx.com/forum/3-feedback-que...sm2-not-bindin#61682

Happy flying!

All fixed, thank you.

Last thing, my board is DSM2. Banggood says it's 6 channels but the mixer tab into the DEVO shows 7 channels. I tried to assign a switch to this channel 7 without result and no switch reacts when toggling in CleanFlight.

I just spent several hours banging my head against this very thing. I'm running a makerfire f3 evo which the crazepony product page insisted was a 7 channel reciever. after much trial and error I found out that it only registers 6 channels as dsm2, but binding as dsmx it recognized the 7th channel in betaflight. I then had to update my devo 7e to the latest nightly build in order to fix an input lag issue and now i'm golden.

I don't know if that will help you, but I hope it does.

The DSM protocols go through some kind of weirdness at between 7 and 8 channels. There are Rx's that are either from Spectrum or licensed by them that deviation has issues talking to, meaning our DSM is buggy. The OrangeRx transmitters have similar problems, and IIUC some of them won't even talk to some of the OrangeRx Rx's across that boundary.

So chances are this is an issue with our reverse engineered DSM implementation and the Makerfire reverse engineered DSM implementation dealing with that oddness in different ways. Spectrum created DSM so - unless all the people reverse engineering it sit down and write up a standard - their implementation is the standard. So I'd suspect the problem is Deviation because of that long-standing bug documented in our manual. But I wouldn't be certain of it.