But this also removed the limitation on the maximum possible PID loop speed imposed by the pre-selected legacy protocol (OneShot125) in earlier versions, resulting in the maximum possible PID loop speed for each MCU type being pre-selected. This means that the correct motor protocol has to be selected before the craft can be armed.
![cleanflight firmware for naze32 hex cleanflight firmware for naze32 hex](https://i.ytimg.com/vi/7_thojnzZTQ/mqdefault.jpg)
Some defaults have been changed, and some parameters are used in different ways, so previous tuning settings will not work well with Cleanflight 4.2
#Cleanflight firmware for naze32 hex update#
For this reason it is important that you update to the version 2.6.0 or newer of Cleanflight Configurator (installation instructions here) in order to get the latest version of your targets installed The latest release of Cleanflight Configurator, 2.6.0, contains the changes necessary to support this.
![cleanflight firmware for naze32 hex cleanflight firmware for naze32 hex](https://eecs.blog/wp-content/uploads/2019/02/cleanflight-flash-firmware.png)
It is intended for testing, and some things still need fixing and fine tuning.