Devo F7 DSMX Protocol help

I need some help. I've got my Devo F7 and I pulled the DSMX protocol from deviation-devof7-v5.0.0-0ac6094.zip and added it to my .fs file I created with buildfs.exe and now on my F7 I can bind the DSMX now but it will not bind to my beebrain v1.d. Am I missing someting my F7 will bind in DSM2 but the controls are completely wrong. If anyone can offer some help to get my beebrain to bind to my F7 I'd really appreciate it.

This is where you asked already I guess!

Ok, so is your beebrain even dsmx capable? You don't have the FRSky version do you? Forgive my ignorance but the Beebrain is what exactly? A receiver/flight controller combined? Got a link to it? newbeedrone.com/products/the-beebrain-v-...whoop-inductrix-quad

What does your beebrain control - Quad, Heli?

It sounds to me like all your channel assignments are wrong and the arm channel on the beebrain never gets a 'high' signal from your F7. So, make sure props are off first whenever dealing with arming issues, an uncontrollable quad at max throttle is bad news, especially indoors.
(Just checked what a beebrain is... I think you can leave the props on!!)

Can you connect the beebrain into a PC and monitor the reception from the F7?

If your throttle assignments are totally screwed you might be trying to arm while throttle is not 0 and most (good) FCs have a safety to prevent this.

Thanks for the response. Actually yes I can monitor the channels in betaflight. I can see the channels responding correctly to my controller.

In betaflight I can assign my arm switch and see the arm toggle.


But in the past when I've bound in the past I've never had to swap my throttle or rudder.

I wasn't sure if I actually made DSMX work correctly. Do you think I did? I saw another member that he had a similar issue but didn't mention the resolution.

Sorry beebrain is my FC for a quad similar to a inductrix or furibee. And it's dsmx.

Check this excellent tutorial on th FC setup for DSMX . If you haven't already, search for Cleanflight/betaflight model files in this forum.

It sounds like you are really close. The common issues are that the stick range isn't set right (see the CLI rxrange command) or the channel assignments got messed up (DSMX wants TAER). Let us know the results.

thwaitm - You we're right! I had changed my channel assignment on my transmitter and not BetaFlight. So my right stick was still seen as my throttle and is never at 0 - zero so arming was never gonna happen. I changed them back to default and corrected my channels in BetaFlight that resolved my power on warning that my throttle was not a zero.

Then yup my rxrange was off my throttle was at 1190 and my limit was 1100 so there was another issue.
I used the following to correct that issue:

Run these commands in the CLi:

get min_check "this will tell you your low throttle level. If your throttle is above this number when the the stick is all the way down your never gonna arm"

set min_check= "you can change your min throttle check number here"

*** I prefer to change my rxrange instead:

Use your minium and maximum range to correct positing of sticks. This helps when you can't arm if throttle is over 1100 in down position.

In the Cli use the follwoing command: rxrange
Your defaults should be:
rxrange 0 1000 2000
rxrange 1 1000 2000
rxrange 2 1000 2000
rxrange 3 1000 2000

I changed my values to the following:
rxrange 0 1159 - 1839
rxrange 1 1159 - 1839
rxrange 2 1159 - 1839
rxrange 3 1159 - 1839

These are the maximum and minimum travel of my sticks.

Hope this helps anyone else having arming issues. Thanks everyone for the help!

Glad you got it sorted out RubenRC.
Nice job on the fix report!