I usually fly my quad with a Taranis X9D plus so when I got my Inductrix Pro I decided to get a OrangeRX module to bind the two but that came with many problems so I returned it and settled for a stock radio (the MLP4DSM). The problem is, I follow all steps to bind and even get the red solid light (also white lights shine in front) but the quad does not respond! > Please help!

Regardless of which TX/RX combo you use you STILL NEED to plug the inductrix into your PC and use BetaFlight to assign a switch that will 'Arm' the quad so it will actually fly!

I'm sure I have explained this previously!?

Download google Chrome browser, go to play store and download BetaFlight, open Chrome and click the top right where it says 'Apps' then click on BetaFlight. Plug your Inductrix into your PC using a micro USB data (not charge) cable, and click connect, if it fails you must download drivers, try ImmersionRC driver pack (didn't work for me) and Zadig. If these driver packs don't help you will need to do some digging for individual drivers...

Power on your TX with the 'Bind' button pressed, press the bind button on your inductrix board, this should make the flashing LED on the RX stay on without flashing. This confirms that you have bound successfully. 

Once you are connected to BetaFlight with TX and Quad bound -

In the 'Receiver' tab in BetaFlight you see the bars moving with your stick inputs, right? Try switching your switches and see which AUX channels they correspond with...

Now change to the 'Modes' tab and click 'Add Range' under 'Arm' and from the dropdown box, select the corresponding AUX channel to the switch you want to use.
In the modes tab you can also select which flight modes you want available and which switches will activate them.

Chances are that (starting out at least) you will want to be able to switch between self levelling (Angle and Horizon modes) and Manual (Acro mode) which is probably the default mode for your FC. I strongly recommend using Angle mode first, just to get an idea of how fast your quad takes off and how it reacts to you. As soon as you feel like you are comfortable with throttle control, and you understand what the stick inputs are making the quad do... 

Angle and Horizon modes teach bad habits and become a crutch, much easier to learn proper control of the craft from the start, frustrating at the early stages but, trust me, its the only way to fly!



Just copied this (again) from a post of mine, in this thread a few days ago


I really hope you manage to get this thing in the air, hasn't this been going on for 2 months now..?

The MLP4DSM transmitter is only 4 channel (no switches). You will only be able to "stick arm" with that radio (throttle low, yaw high). If you plug a battery in, and it doesn't arm when you do that, you will need to check some settings in BetaFlight.

First, go to the receiver tab and (with battery plugged in) find the low value of your throttle. It may be something like 1084 or 1115, etc. You can't change that on your transmitter - it is what it is. There is a setting in betaflight called min_check. Now by default, min_check is set to 1100. You will NOT be able to stick arm if your lowest throttle value is above min_check, so you need to reset that value to be higher than your lowest throttle value.

To do that, go to the CLI, and type "set min_check=1125" (for example - you want something that is 5-10 points higher than your low throttle value shown in the receiver tab). Type "save". Note: if you don't have motor stop enabled, your props may start spinning as soon as you arm depending on your min_throttle setting.

If none of that works, you might check to make sure your quadcopter is level (and make sure you've calibrated the accelerometer).

(23-Aug-2017, 07:27 AM)Tom BD Bad Wrote: Regardless of which TX/RX combo you use you STILL NEED to plug the inductrix into your PC and use BetaFlight to assign a switch that will 'Arm' the quad so it will actually fly!

I'm sure I have explained this previously!?

Download google Chrome browser, go to play store and download BetaFlight, open Chrome and click the top right where it says 'Apps' then click on BetaFlight. Plug your Inductrix into your PC using a micro USB data (not charge) cable, and click connect, if it fails you must download drivers, try ImmersionRC driver pack (didn't work for me) and Zadig. If these driver packs don't help you will need to do some digging for individual drivers...

Power on your TX with the 'Bind' button pressed, press the bind button on your inductrix board, this should make the flashing LED on the RX stay on without flashing. This confirms that you have bound successfully. 

Once you are connected to BetaFlight with TX and Quad bound -

In the 'Receiver' tab in BetaFlight you see the bars moving with your stick inputs, right? Try switching your switches and see which AUX channels they correspond with...

Now change to the 'Modes' tab and click 'Add Range' under 'Arm' and from the dropdown box, select the corresponding AUX channel to the switch you want to use.
In the modes tab you can also select which flight modes you want available and which switches will activate them.

Chances are that (starting out at least) you will want to be able to switch between self levelling (Angle and Horizon modes) and Manual (Acro mode) which is probably the default mode for your FC. I strongly recommend using Angle mode first, just to get an idea of how fast your quad takes off and how it reacts to you. As soon as you feel like you are comfortable with throttle control, and you understand what the stick inputs are making the quad do... 

TURN AUTO LEVEL OFF!!!

Angle and Horizon modes teach bad habits and become a crutch, much easier to learn proper control of the craft from the start, frustrating at the early stages but, trust me, its the only way to fly!



Just copied this (again) from a post of mine, in this thread a few days ago


I really hope you manage to get this thing in the air, hasn't this been going on for 2 months now..?

What's the difference between a data and charge mini USB? Also I don't see a bind button on the Inductrix

(23-Aug-2017, 10:03 AM)sloscotty Wrote: The MLP4DSM transmitter is only 4 channel (no switches). You will only be able to "stick arm" with that radio (throttle low, yaw high). If you plug a battery in, and it doesn't arm when you do that, you will need to check some settings in BetaFlight.

First, go to the receiver tab and (with battery plugged in) find the low value of your throttle. It may be something like 1084 or 1115, etc. You can't change that on your transmitter - it is what it is. There is a setting in betaflight called min_check. Now by default, min_check is set to 1100. You will NOT be able to stick arm if your lowest throttle value is above min_check, so you need to reset that value to be higher than your lowest throttle value.

To do that, go to the CLI, and type "set min_check=1125" (for example - you want something that is 5-10 points higher than your low throttle value shown in the receiver tab). Type "save". Note: if you don't have motor stop enabled, your props may start spinning as soon as you arm depending on your min_throttle setting.

If none of that works, you might check to make sure your quadcopter is level (and make sure you've calibrated the accelerometer).

I can't figure out how to connect the drone to betaflight, clicking connect won't work and I don't know what board is in the Inductrix Pro

Hey Spiinner, I just realized that I said 'ImmersionRC' driver pack when its actually from 'ImpulseRC' sorry!

Neither Impulse RC or Zadig worked for me, I will try and tell you which drivers I downloaded, but I can't say for sure which it was that finally made it work, because I forgot that I needed to restart my PC after installing drivers..!

1st make sure that .Net framework is up to date, I attempted to install v.4, v.4.5 and v4.7 windows said a later version is already installed, but it may have helped?

CP210x is a driver from Silabs 

STM8 flasher virtual COM port driver

STM32 another virtual COM port driver

in this the guy updates the Inductrix FirmWare to betaflight 3.1.7 using FW options for a 'Naze' board

I hope at least some of this helps...