X220 binds but won’t arm

A

ALEC

Member
Okay so I’ve had issues with this quad for a while and I setup everything with betaflight and I’m upgraded to the most recent betaflight. When I power on the quad, it binds and the bind light turns off but when I raise the throttle the light starts to blink again. Please help
 
What bind light? Receiver or flight controller? What ESC protocol are you using? Have you done the routine Betaflight configuration such as enabling correct UART in ports tab, Serial RX and sBus chosen in Configuration tab? Switches setup in modes tab?
 
RENOV8R said:
What bind light? Receiver or flight controller? What ESC protocol are you using? Have you done the routine Betaflight configuration such as enabling correct UART in ports tab, Serial RX and sBus chosen in Configuration tab? Switches setup in modes tab?
Click to expand...
Can you explain what you mean by "Have you done the routine Betaflight configuration such as enabling correct UART in ports tab, Serial RX and sBus chosen in Configuration tab? Switches"?
I'm having an issue where everything is working but my arm switch wont work for some reason on my x220.
 
alex_. said:
Can you explain what you mean by "Have you done the routine Betaflight configuration such as enabling correct UART in ports tab, Serial RX and sBus chosen in Configuration tab? Switches"?
I'm having an issue where everything is working but my arm switch wont work for some reason on my x220.
Click to expand...
Yeah my issue is basically yours as well, arm switch
 
If everything's set up properly then it's probably just an ESC calibration issue. Do you have ESC protocol set to DShot600?
 
ALEC said:
Yeah my issue is basically yours as well, arm switch
Click to expand...
So I found my issue. It was that my throttle and my yaw had reversed themselves. If this is your issue then the quad wont arm because your idle throttle value will probably be 1500 which is above the minimum the quad allows to arm. You can check this by going to the 'reciever' tab in betaflight and moving your sticks and making sure they are set the right thing.
 
Usually it is the esc calibration in betaflight that causes this issue, but since the calibration itself presents some danger no one wants to announce the procedure on the internet.
 
I've told at least one person on facebook that the calibration is probably the issue, but it's one of those things you need to figure out how to do it safely.

There are you tube videos explaining the calibration process better than I can here lol.

Do the "motor tabs" calibration in betaflight.
 
Dugdog47 said:
I've told at least one person on facebook that the calibration is probably the issue, but it's one of those things you need to figure out how to do it safely.

There are you tube videos explaining the calibration process better than I can here lol.

Do the "motor tabs" calibration in betaflight.
Click to expand...
Exactly. I also think learning it the hard way by myself with looking up forums and youtube vids helped me. I definetly wont forget how to fix this.
 
Hold on, I haven’t gotten my issue figured out just yet, I’ve gone through every setup video I could but then I found one that said I couldn’t use the x220 with the dx9 transmitter could someone verify this please?
 
ALEC said:
Hold on, I haven’t gotten my issue figured out just yet, I’ve gone through every setup video I could but then I found one that said I couldn’t use the x220 with the dx9 transmitter could someone verify this please?
Click to expand...
That's not true at all. The wizard x220 uses the naze F3 board which is compatible with the dX9 spectrum receiver.
 
So I’m using the HobbyKing OrangeRx R615X DSM2/DSMX Compatible 6Ch 2.4GHz Receiver w/CPPM which side of the wizard do I plug this into and what port on the receiver should I plug into?
 
I'm fairly new at this too but it just so happens I'm doing research on the naze f3 board for a future build so here is what I recommend. First, make sure your board looks like this:
aeea540f1cefad386a8510031f51f281.jpg
Second, make sure your receiver uses the sbus/PPM signal.

If one and two check out, your receiver plugs into the port on the left.

As far as your particular receiver is concerned, I don't know much about those. I'm a flysky guy.
 
That DMX has its own port on that board.
Usuall just 3 pin jst. Then pick orange or dsmx in the drop down in config.
 
Last edited:
Ditch that f3 ASAP I know they are good & I've had one running 3 years.
But you can get an omnibus f4 SD PDB
For the same price. Or even an old omnibus V? Give you Alot better ride & more options. Filters etc.

Ibus or ppm is for flysky I range.
The evo does ppm Ibus sbus
Has the guy with the flysky done the firmware update.
 
mozquito1 said:
Has the guy with the flysky done the firmware update.
Click to expand...
Sup bro still ain't done the update on my eachine flysky clone I keep forgetting to order the usb cable lol.

As for the O.P. who is having trouble, the answer is here, you just need to do what is shown in the diagram I posted and click the correct drop down in the configuration tab in cleanflight.

BTW @mozquito1 why do you say ditch the f3? I thought they were good boards with the upgraded gyro?
 
Okay so what I got from all this is to plug my receiver into the front side of the eachine wizard and then into the aux 1 port on the the receiver and select the configurations tab and select the right receiver?

I’m not exactly in a situation to get a new flight controller just yet
 
I looked at my wizard just to be sure and actually, mine is plugged into the back, but I'm using Ibus, yours will be using Sbus so it might be different.

The answer is here somewhere though I guarantee it.
 
You must log in or register to reply here.
Back
Top