Hmmm.... I hope it doesn't start doing strange stuff like that in flight!

On a related note, I ended up chasing a fault recently that turned out to be caused by the USB cable I was using. I had connected my flight controller to my laptop with this cable and set it up. Then I carried on with my build and tried to connect to the flight controller again and nothing - "connection failed" from the Betaflight configurator every time.

I could see in my computer's log that it detected the serial port when I plugged the cable in, but I just couldn't get a connection.

As I knew it was a good flight controller, I grabbed the high quality USB cable that I normally use and connected with that instead. Instantly, the problem was solved and I could connect again.

The offending cable now has a label with "Charge Only" attached to it so that I don't mistakenly use it again as a data cable!

(03-May-2017, 06:23 PM)unseen Wrote: Hmmm.... I hope it doesn't start doing strange stuff like that in flight!

On a related note, I ended up chasing a fault recently that turned out to be caused by the USB cable I was using. I had connected my flight controller to my laptop with this cable and set it up. Then I carried on with my build and tried to connect to the flight controller again and nothing - "connection failed" from the Betaflight configurator every time.

I could see in my computer's log that it detected the serial port when I plugged the cable in, but I just couldn't get a connection.

As I knew it was a good flight controller, I grabbed the high quality USB cable that I normally use and connected with that instead. Instantly, the problem was solved and I could connect again.

The offending cable now has a label with "Charge Only" attached to it so that I don't mistakenly use it again as a data cable!

It can happen, but in my case is something else, since the board stop responding to any cable or even battery when it suddenly goes to "brick mode" without any specific reason like touching wiring, something that could cause a short circuit.

I already ordered a new one, Naze32 Rev6 instead and a CC3D also.

By the way, for beginners, is there any big difference on any of these boards  types (CC3D vs Naze32) both or F3, I couldn´t find any specific big difference to define what would work best for the stage I am now (Beginner) 
I found this: https://oscarliang.com/naze32-vs-cc3d-better/ but with all honesty not much in terms of the way both will do the job, maybe because they are very similar once they are installed and the differences are more about the way to do it and how you configure.
Looks like the big difference are the different connectors and how easy is to get it working.

Thanks

There is one significant difference between the Naze32 and the CC3D and that is how the gyro/accelerometer is connected to the microprocessor. On the Naze32, it is connected via an I2C bus and on the CC3D via an SPI bus. SPI is much faster than I2C and allows the microprocessor to fetch data from the gyro at the maximum supported rate of 8KHz compared to just 2.6KHz for I2C.

A faster sampling rate has been proved to give the firmware a better 'feel' for what is happening and results in more precise control of the quad and a more locked in feel.

However, the advanced algorithms used in the latest releases of Betaflight and Cleanflight to take advantage of high sampling rates come at the cost of more intensive and demanding processing and this is where both the Naze32 and the CC3D have a problem.

Both flight controllers use the STM32F1 microprocessor. The F1 uses the Arm Cortex M3 CPU core and cannot directly deal with calculations that use floating point numbers, so any calculations that need floating point are done in code rather than hardware. This limits the performance that can be achieved.

Modern flight controllers use the STM32F3 microprocessor. This uses the next generation Arm Cortex M4 CPU core. The M4 is more advanced and also has a floating point unit to handle floating point numbers directly in hardware. With the F3, the firmware can use the full speed of an SPI connected gyro and all the latest algorithms without even breaking a sweat.

The F3 also offers more UART ports to connect things like receivers, OSDs, GPS units etc, and can deal with normal or inverted signals without the need for external hardware.

For any build that you might make today, the F1 based boards are not recommended. The major firmware projects are already considering dropping support for F1 boards in the near future.

The article that you linked to on Oscar's site is from February 2015 - over two years ago - and a lot has changed in the evolution of both flight controller hardware and the firmware that runs them since then.

I don't even bother with F3 boards now. I'm testing this no-name F4 board right now and so far it's performing flawlessly. Can't beat it for 25 bucks!
http://www.getfpv.com/flight-controllers...oller.html

I still use the cc3d's and they work fine within the limits, but F1 boards in general are not worth buying anymore, as you can get F3 or even F4 for almost the same price.

TL;DR: what renov8r said