Flip 32+ (Naze 32) Flight Controller Guide. Naze32 драйвер
Не подключается контроллер полета naze32, flip32 к CleanFlight? Установка драйверов и обновление прошивки12 Сен 2015, 19:47
Одна из самых распространенных проблем у новичков в начале работы с контроллерами naze32, flip32, это трудность с первоначальным подключением к программе по настройке CleanFlight.
Установка драйвера для контроллера
Перед началом работы с контроллером и программой CleanFlight необходимо установить драйвера серийного конвертера CP210x, если они еще у вас не установлены. Проверить нужно ли устанавливать драйвера очень легко. В программе CleanFlight вверху в выпадающем списке выбора COM порта должен присутствовать виртуальный COM порт, который создается при подключении контроллера к USB, а в списке установленных устройств в Windows должно быть уставлено подобное устройство:Если при подключении в списке присутствует неустановленное устройство, нужно установить драйвера.Драйвер можно скачать на официальном сайте производителя чипа серийного конвертора порта CP210x: Для Windows: здесьДля других платформ: здесь
После установки драйвера порт на котором подключен контроллер должен появится в выпадающем списке программы CleanFlight. Можно пробовать нажимать кнопку «Connect», но скорее всего в логе при попытке подключиться вы получите такую ошибку:2015-09-12 @ 18:44:50 -- Serial port successfully opened with ID: 32015-09-12 @ 18:45:00 -- No configuration received within 10 seconds, communication failed2015-09-12 @ 18:45:00 -- Serial port successfully closed
Все дело в том, что новые версии Cleanflight Configurator не всегда совместимы со старыми, устаревшими прошивками, которые могут быть залиты производителем при производстве платы. И именно поэтому программа не коннектится к вашему контроллеру и срабатывает таймаут подключения.
Чтобы этой проблемы не возникало необходимо обновить прошивку контроллера до последней доступной версии.
Как обновить прошивку CleanFlight
- Для начала необходимо вверху программы выбрать порт к которому подключен контроллер (обычно он выбирается автоматически программой).Если порт отсутствует, проверьте подключено ли устройство, горят ли на нем светодиоды питания и самое главное установлен ли драйвер серийного конвертера CP210x.
- Перейдите во вкладку «Firmware Flasher»
- В выпадающем списке выбора версии прошивки выберете последнюю доступную версию для вашего контроллера. Например для naze32, flip32 это будет версия «1.x.x NAZE дата выпуска». Галочки можно оставить не выбранными.
- Далее нужно нажать внизу на кнопку «Load Firmware [Online]».Отобразится сообщение о том что прошивка была загружена онлайн на ваш компьютер. (Loaded Online Firmware: (xxxxxx bytes))
- Теперь можно приступать к прошивке контроллера. Нажимаем кнопку «Flash Firmware», начнется загрузка в контроллер и проверка прошивки. После чего вы должны получить сообщение об успешной загрузке.
Прошивка успешно обновлена и теперь вы можете смело пробовать подключаться к контроллеру через кнопку «Connect».
На сайте работает система проверки ошибок. Обнаружив неточность в тексте, выделите ее и нажмите Ctrl + Enter.
Flip 32+ (Naze 32) Flight Controller Guide - Guides
The Flip32+ is one of the better quadcopter controller boards as it uses a 32bit controller with some great software, and its also rather small. This board uses the baseflight software which is gives this controller excellent performance right out of the box. Overall this is probably the best controller board for your miniquad. Below are some links to various manuals and also some great instructional videos.
In order to configure your Flip32 board you will need to install google chrome browser as the configuration software only runs on google chrome.
Flip 32 Board Connector Overview
Flip32 Board Versions
The Flip32 board comes in two versions, a regular Flip32 board, and a more expensive Flip32+ board… Depending where you buy them they may use various names for the two The only difference between the two versions is the fact that the more expensive board has two added sensors, a compass (magnotometer) and a pressure sensor (barometer). Other than that both boards are exactly the same in terms of other inputs and outputs. If you are unsure about what version to get, I would personally say the more expensive board is better as it allows for you to add extra things to your system later on such as GPS, and the pressure sensor means you can use the altitude hold function. That said both these sensors are not super important if you are planning to build a little FPV racing quadcopter, but overall there is not a high price difference between the fun fly and full versions in the case of the flip32 boards…
You can download the drivers for the Flip32 board here from silabs, there is also a link to do this from within the configuration tool
Being an open source project there are a some variations of software to choose from. The most popular version is baseflight but there has also recently been a fork called cleanflight which has the aim of using modern software practices to make the code easier to read/maintain and add new features. Fundamentaly both these firmwares are the same so feel free to try both and see which you prefer! I tend to prefer cleanflight firmware and it also has great up to date documentation.
For more information on updating the firmware on your Flip32+ please see the post below. If you try to connect to your board but get an error message saying:No configuration received within 10 seconds, communication failed
Then its most likely that you don’t have any firmware (or the correct version) on the board, so you will need to update the firmware.This is a quick guide showing you how to update the firmware on your flip32+ board. The first thing you need to do is download the latest drivers, firmware and configuration tool, you can get the links for these on the flip32 guide. If you try to connect to your board but get an error message saying: No configuration received within 10 seconds, communication failed Then its most likely that you dont have any firmware (or the correct version) on the board, so you will need to update the firmw…
There is no official manual for the flip32 board, however this post tries to cover some of the main topics that you will encounter with this flight controller. Since the best software to run on this flight controller is the cleanflight software the details on how to use the software do not depend on the actual hardware you are running it on. The only fundamental thing that is different between the flip32 and the naze 32 is the hardware layout.
However if you are looking for a more advanced manual you can also have a look at the naze32 manual (which is a board very similar to the flip32 but just with a slightly different board layout. naze32.pdf (1013.9 KB)
Flip32+ Motor Connection Order
How to connect everything to your flip32
This image might seem complicated at first, but it provides great detail on how you would go about connecting all the possible accessories to your flight control board, such as GPS, OSD, Bluetooth and your FPV gear.
Connecting FRsky Telemetry to your Flip32 board.
If you are using a FRsky R/C system with the flip32, its a great idea to enable telemetry via the softserial port which allows you to receive some infomration in real time from the flight controller on your Taranis radio. For more information please read our guide on how to connect Frsky Telemetry to your cleanflight flight controller.
Flip32+ Video Tutorials
The videos below show a complete walkthrough of how to setup and configure your flip32+ flight controller.The first video simply goes over the board and talks abit about the various pins and features. This video shows you how to install google chrome and the baseflight configuration tool. If you already know how to install this then you can skip this video This video shows you how to install the driver of the flip32+ and also how to install the firmware onto your flight controller board. This video shows you how to connect your flip32+ board to your receiver and also goes over some of the initial configuration settings to enable you to use your controller with a quadcopter The final video goes through some more configuration settings such as flight modes and other various settings. This videos goes over the motor spin direction and also the ESC calibration with your Flip32 flight controller.
This video shows you how to connect and setup a bluetoooth module for your flight controller. This video also goes over the details on how to setup and configure a bluetooth module for use with the flip32+.
Naze 32 Revision 6 Flight Controller Guide - Guides
The Naze 32 Rev 6 board has made some nice layout revisions such as finnaly having the USB board mounted on t he side for easy access on your miniquad al last!
Whats new in Revision 6?
- USB port has been moved to the right of the board so you dont need to mount the board sideways anymore!
- IMU sensors upgraded to MPU 6500 (Rev 5 uses older MPU 6050)
- Receiver connectors are no longer solder pads but common pin hole headers style. This means that you no longer need to directly solder your receiver wires to the flight controller. Also older revisions had issues of pads delaminating when board got too hot.
- Fully pin compatible with Rev 5 boards for accesories such as OSD.
- Integrated SBUS inverter, now you can connect your FRsky SBUS receivers directly with no extra inverter!
- Dedicated Spectrum Satellite port.
- Additional Flash memory so you can use blackbox recording directly. With the Acro version you get 2Mb (16Mbit) and the Full version you get 16Mb (128Mbit). To learn more check our guide on Naze 32 versions.
Here is a closeup of the auxillary connectors on the Naze 32 board which include an extra 3.3V output at 100mA, a I2C connector, the buzzer connector, and battery voltage monitor pins. One thing to note is that the Frsky Telemetry pins are shared by the UART 1 TX, which is in turn shared by the USB. So if your board is connected to your PC via USB you cannot use the UART 1 ports.
Typical Naze32 Connection diagram
The diagram below shows a fairly common setup on a FPV racing quadcopter using a CPPM receiver, optional GPS module, and an RGB LED bar.
Flashing Cleanflight onto Naze 32 Rev 6
Contrary to many forums it is definitely possible to load and run cleanflight easily on the Rev 6 Naze 32 boards that we sell. Once the board is connected to your PC the drivers should install automatically. Then launch the cleanflight GUI and write the latest firmware version to your board as shown below.
Connecting a RGB LED strip
Adding an RGB LED strip to your Naze 32 is one of the coolest features for FPV flying. Not only does it let you see your quadcopter easily, but you can also add smart features to your LED, so when you are turning left, the Left LED’s can flash. When you slow down the lights can glow bright red, just like a car brake lights.
Depending on your RGB LED strip power requirements you might need to connect it directly your battery, or BEC. In the diagram below the LED stip runs on 5V so we can power it directly from the ESC rail. The control signal plugs into RC 5 on your naze32.
Once connected you will need to configure the RGB LED strip in clenaflight. Here is a great video showing you how to do this.
Using integrated Black-box Recording to SPI dataflash
Since hte revision 6 of the naze32 boards include a built in blackbox recorder, it is very easy to get this working. Rather than re-writing everything here is a great video by Roberto Correia showing the process of enabling the blackbox via cleanflight CLI and how to view the logs after a flight.
Naze 32 Soft Serial
Since the Naze32 only has two hardware UART ports, of which one of them is used by USB. So this introduces some issues if you want to use a bunch of accesories with your Naze32. Fortunately you have the option of using softserial which emulates an extra two UART ports on RC pins 5,6,7,8. However if you enable soft serial you will not be able to use those ports for other things such as RC 5 for your LED bar. My suggestion is to use a CPPM receiver so that you can use the dedicated spare UART2 port for something like GPS.
Connecting a SBUS receiver
Is it possible to connect a SBUS receiver (such as the X4R-SB) directly to the Naze32 Rev 6 flight controller, but by doing so you will be using the UART2 ports and will not be able to use UART2 for other things such as GPS. However I would suggest you try to rather use a CPPM receiver (X4R-SB can be used in CPPM mode) as this will keep the UART ports free on your NAZE 32.
Connecting FrSky Telemetry
With the older D series receiver (like the D4R) connecting telemetry is fairly simple by connecting the green wire from your D4R to the telemetry pin on the flight controller.
Connecting Smart Port Telemetry
When it comes to the newer X-series FRsky receivers, telemetry connection is a little more tricky. To use this you will need to use the softserial feature on cleanflight. Doing so means that RC pins 5,6,7,8 will be used so you cannot use your RGB LED bar in addition to the smart port telemetry. For full details check our our guide on how to setup smart port telemetry on your flight controller.Using FrSky smart port telemetry on Naze 32 flight controllers is a little tricky to get working due to the limited number of UART ports available on the naze 32 flight controller with F1 processors. Using other naze 32 compatible flight controllers with F3 processors such as DoDo F3 make things abit easier. However if you do have a naze32 and want to use your X-series receiver (such as X4R) with telemetry here is what you need to do. There are two options, the first one which is better is t…
Connecting a GPS Module
If you are using a 10DOF or Full Naze 32 board then you can add a GPS module to use extra flight modes. Connecting it to the UART 2 ports is fairly easy and straight forward as shown in the image below. You will need to power the GPS module from the ESC rail.Once connected you need to enable it within the cleanflight GUI. The important thing is to make sure the baud rate is set correctly within cleanflight to match the baud rate on your GPS module. If you are not sure you can play around with teh various baud rate settings untill one of them works. However most modules run on 57600.
Once the serial port is configured, you will need to set the GPS settings in the configuration tab.
Naze 32 LED’s and their meanings
Each naze 32 has three LED’s on the board, one located close to the USB port to indicate if its powered or not. The other two are located next to the spektrum connector and are used to provide some details as to what is happening on your flight controller according to various flashing sequence:
- Red+Green + Blue on solid - device is in bootloader mode
- Green flashing - indicates the board is not armed (if you cant get your board to arm see below)
- Green on solid - the board is armed
- Green + Red on solid - board is armed and is in horizon / self level mode
- Red + Green flashing one after another - board is calibrating accelerometers / compass
I cant get my Naze32 to arm
It can be rather annoying to build and setup your quadcopter and when you arrive to go fly, it will not arm. So its always a good idea to check its working after setting it up before going out to fly. However from time to time it might not want to arm so here are a few common mistakes that prevent your Naze 32 flight controller from arming.
Make sure your radio is setup correctlyWhen you are setting up your cleanflight board, make sure that your radio settings are correct. This means to make sure the challens are are correctly assigned and not reversed (when you move the throttle stick upwards you see the throttle channel moving upwards on cleanflight). Also make sure the range is between 1000-2000, if not you will need to change either the settings on your radio, or use the cleanflight command line as discussed here
Make sure you have performed sensor calibration?If you have not yet calibrated your accelerometers, and compass (only on 10DOF boards) on your board. An easy way to do this is to make sure your multirotor is on a level surface, with battery connected. Then on your R/C controllor move the sticks to the appropriate positions as shown in hte image below for the Gyro and ACC calibration:
Check your throttle failsafeA common error is the PWM failsafe value that is set on cleanflight. Cleanflight has a failsafe to turn off the motors and disarm if it looses connection to your R/C controller. However sometimes this might be higher than your actual radio thottle idle value, so the failsafe would activate (requireing you to restart your board before it will allow you to arm again). So you will either need to change the throttle idle value on your radio, or change the value within cleanflight. But please make sure that you do set a failsafe and have configured this on your R/C receiver as you dont want your drone to fly away accidentally.