Desperate help needed for school drones!

[GeekTeach]

My students and I are trying to get a beecore based drone to work for an upcoming league tryout with our local schools. We ordered a bunch of equipment based on a previous league's build and have (we think) purchased everything as closely as possible to the old builds that worked. Our problem is that once bound (they DO bind) to our Flysky controllers, the throttle does not engage like it did with our previous drones on the same core/control board (beecore 2.0, link below). This same problem is happening with all 10 we ordered and have built. We have tried everything that we can easily find online and in the documentation of the controller to fix this issue including:

-Reset trim on all axis to center, throttle stick down fully. ONCE for a few seconds on various drones, the motors spun up, but then not again.
-Trying our old controllers, which are the same model but with the toggle switches installed at the top of the controller. These did not work and had the same issues arming the throttle.
-Switching the various controller settings using the "hold both sticks to the bottom left and turn on" procedures in the remote documentation.
-Tried with and without FPV camera installed in both the battery terminal configuration (sharing inputs with the board) and the dedicated pads/joins for cameras. The camera works in both, but still no change in the drone.
-Tried (and failed) to connect the beecore via USB to our PCs to no avail. Is Betaflight supposed to interface with the remote control or the drone board (beecore)?

We are on a timeline and have spent quite a bit of money getting these drones for the students and desperately need some help from those far more experienced than us. My students recorded a video showing what happens (and doesn't) when we bind and attempt to use the throttle (nothing) that will hopefully help. Thank you ahead of time to anyone who can give us some tips or things to try.

Video:
Apparently can't post until I hit three posts, will post ASAP

Remote Control:
FlySky - i4X 2.4G 4CH Transmitter

Control Board:
Eachine Beecore V2 - F3 with OSD - FlySky

 

[RENOV8R]

Yes, your Beecore will have a micro USB port to connect to your PC and interface with the Betaflight configurator. Your Beecore needs to be configured, so until you can connect, you're not going to be able to arm your quads.

Open Betaflight and connect your Beecore to your PC

Download and run the attached IRC Driver Fixer and hopefully within a few seconds, you'll get a message that says "drivers fixed"

At this point, you should be able to click on the "connect" button in the top right corner of the Betaflight configurator and get into the configuration pages. If this still doesn't work, try different USB cables and make sure it is a data transfer cable, not just a charging cable.

 

[GeekTeach]

This sounds like a plan, but there was no attachment that I could see; I'll break out my Google-Fu in the meantime to see if I can find it elsewhere by name. Thank you!

 

[GeekTeach]

ImpulseRC Driver, correct? It seems to be stuck at the "Searching for flight controller" step and not getting any further. I've seen a few people suggest that perhaps the cable is the issue, so I'll steal a few USB micros to try, but is there any other step I could be missing? Betaflight is open, drone is plugged in and flashing in pre-bind mode (all lights regular pulse), and ImpulseRC searching to no avail.

 

[RENOV8R]

Ok, this means you probably don't have the drivers installed. On the main Welcome page of Betaflight, you'll seethe links to download both the CP210x and STM VCP drivers. Download these drivers, then run the IRC driver fixer

 

[GeekTeach]

OKAY! Progress! We got connected in Betaflight and everything seems to be working fine. The motor tab allows us to turn up the throttle and the motors DO spin up. The throttle signal from the controller is recognized, but is not translating to the motors. We have taken some screenshots which I will attach. We have tried tinkering with the sliders and low/medium/high threshold but the drone still doesn't translate the throttle signal to actually running the motors. Of potential note, readymaderc support told us that we need to "arm" by holding the throttle stick down and to the right when we begin, but that did not appear to do anything. I'm sure we're missing something small.

 

[GeekTeach]

Also, thank you so much for your help and time!

 

[RENOV8R]

Not a problem. Looks mostly OK, however look at your modes tab and I see that you've added angle mode on AUX2 and the box is yellow which is good, means it's enabled and working! So you just need to do the same for arming mode, click the dropdown and set it to AUX 1. I'm not familiar with Flysky equipment but you'll just have to go into your radio and assign AUX1 to a 2-position switch of your choice. Be patient, we're getting close!

 

[GeekTeach]

So we have a controller with a switch in AUX 1, but we can't for the life of us figure out how to get that channel yellow. We can see the signal jumping from 1000 to 2000, but no yellow and no arming. In our fiddling, we seem to have also disabled the angle as well (turned grey).

 

[RENOV8R]

Here's a video to showu you how to set up an arming switch

 

[Dugdog47]

I have 7 quads all bound to one flysky controller so I should know this by heart but it's kinda confusing although there are plenty of videos explaining it.

Something like this:

You must go into the settings on your flysky controller and set channel 5 as "switch A" and channel 6 as "switch C" I believe it is.

Then you'll go into the modes tab in beta flight set your arm switch as "aux 1" and set angle mode/horizon mode as "aux 2"


A member here named @mozquito1 could confirm this.

 

[GeekTeach]

WE GOT IT! Thank you so much for your help! An combination of this video and some tinkering got it working and we used the backup/restore feature to update all ten of the drones. Thank you very much!

 

[GeekTeach]

We actually have the ultra-ghetto versions of the flysky remote controls without screens or settings, but we got it working with some screwdriving and pin shorting (to be replaced by toggles). Thank you!