![impulse rc driver fixer number of devices detected impulse rc driver fixer number of devices detected](http://mas.txt-nifty.com/3d/images/2009/09/13/2009091308.jpg)
However, there are also three target variations. There is the main target, MATEKF411SE which works as described on the Mateksys page. Some targets have more than one option for how they work. However, you can see all the main targets supported by iNav in the firmware flasher, which we will look at next. However, not all manufactures are as helpful as Mateksys. And with some flight controllers, the F405-WING being a prime example, the target is printed directly on the flight controller. Mateksys have got great documentation on their web site. In this example, I am using a Mateksys F405-WING. The first place to check is the manufacturer’s web site. In which case, we need to find the correct one to use. If your flight controller does not have iNav installed, you may find that the target shown here is not available in iNav. We don’t need the rest of the information. 3.1.0 – This is the version of the firmware that is installed on the flight controller.MATEKF405SE – This is the target that has been used.INAV – This is the firmware that is installed on the flight controller.Secondly is gives us the firmware and target installed on the flight controller.
![impulse rc driver fixer number of devices detected impulse rc driver fixer number of devices detected](https://usermanual.wiki/Sony/SonyPowerHdFxPdw700UsersManual286864.1566021711-User-Guide-Page-1.png)
We have validated that our flight controller is working. Firstly, that our flight controller is communicating with Configurator. What you should get back is similar to the following: INAV/MATEKF405SE 3.1.0 / 14:22:49 (688bff68) What we need to do now is type version in to the CLI and press enter. Unless your flight controller comes shipped with iNav 3.0, this will happen. Testing the flight controller and finding the targetĬhances are, when you plug in your USB cable and connect, Configurator will take you straight to the CLI page. If not, you may have a faulty flight controller. Hopefully by this point you have USB 3, for example, shown at the top of Configurator. If you still don’t see a USB number other than 1, and this is the first time you have plugged a flight controller in to this computer. Sometimes using a USB hub can cause issues. Ideally, you should use a USB port on the front or back of your computer (or side of your laptop). But even decent cables can go bad over time. Some cables are just dodgy from the get-go. The first thing I would check and change is the USB cable it’s self.
![impulse rc driver fixer number of devices detected impulse rc driver fixer number of devices detected](https://patentimages.storage.googleapis.com/US7027530B2/US07027530-20060411-D00002.png)
If only 1 is visible, there is some communications problem. If the number is 1, check the drop down list.
![impulse rc driver fixer number of devices detected impulse rc driver fixer number of devices detected](https://images-na.ssl-images-amazon.com/images/I/51AlOnB5M0L._SX326_BO1,204,203,200_.jpg)
Secondly, we can find out which target is installed.Ĭheck the connection box at the top of configurator. Firstly, if we see activity on the flight controllers LEDs, we can see that it’s communicating with our computer, and is working. This is going to allow us to do 2 things. The first thing we are going to do is open up iNav Configurator and plug the USB cable in to our flight controller. Before following this guide make sure you have installed the latest version of iNav Configurator. There are a few things that we should do before one drop of solder hits our flight controllers. It’s great to plan where you’re going to put things and to test out CG. Once we have our components, we can think about putting it all together. This article is coming from the perspective of a complete new build.