4275 commits to master since this release.14852 commits to master since this release Blackbox flight recording! - Releases.Improved the performance of the dynamic notch filter hydra released this Changes since v2.4.1: Added support for feed forward to the PID controller. Latest Cleanflight Configurator >= v2.5.0-RC1 is required. 4026 commits to master since this release.For a list of other new features that were added see 'New Features' below hydra released this on
Please read the 'Important information when upgrading' section below. If you are using firmware 4.2, it is essential that you upgrade to this version, in order to get support for configuring the new features of 4.2. I think it's the colibri, but I dunno for sure yet.This release contains all of the changes necessary to support version 4.2 of the Cleanflight firmware.
I don't believe it is a cleanflight problem at this point but until I hook it to something else I can't know that for a fact. I have a different FC on the way so I'll be able to confirm for sure cleanflight is actually working and it's not a COM problem or something. boot mode again and flash the latest betaflight colibri when it plugs back in its a STM32virtual port again.Ĭlean flight only ever sees it at all if it's in boot as DFU. If I hold the button and plug in boot mode then clean flight does see the DFU and will let me flash with whatever I want, but, if I flash it with the latest cleanflight colibri, when it's done and I plug it back in, then the msg in the tool bar says the sub device not recognized, if I click it, it says usb device has malfunctioned. If I click it, It comes up n the devices and printers window, of I click that it says it's working. I did, and yes when I plug in the usb my computer sees it as an STM32 Virtual COM Port. However being new to both cleanflight and to the powercube I have no way to really know. My guess is that the firmware flashed fine and that's why the start up lights and sounds are different and that my problem lies in cleanflight and com ports or something. Tomorrow I plan to try all this on a different cmputer, beyond that I'm at a loss. I was stoked and ready to fly, now a day of chasing the internet later and I'm just frustrated.Īnybody have any idea if I'm having a cleanflight problem or a colibri problem? Now I get what sounds like a start up, a little esc song, a rapid chirp (with fast green light on fc) followed by slow red flashes then three beep beep beep(with red lights) then blue lights all around.
Cleanflight does exactly the same "failed to open serial port"Īlso, before I flashed it, when a battery was plugged in it would just beep beep beep. When I plug it back in I get some rapid green flashes, like two slow red and three faster red blinks and then all lights on FC go out. It appears to work just fine and promptly says sub device successfully disconnected. Finally, cleanflight does something and recognises It as DFU.ok, so I go to the firmware flasher, load local firmware I had downloaded earlier ( betaflight 2.8.1 hex file) and click flash. Then, with power off, I hold down the boot button and plug it in. Also tried it with the battery and without. Same thing, not connecting "failed to open serial port"ĭo all that over a couple times, no luck. I did the zadig thing, shut down everything and restarted.
Then I read the next section of the manual "cleanflight configurator issues" I had installed Google Chrome and the cleanflight app on my basic Windows 7 laptop yesterday.
Then I opened the pdf manual and followed the link for "Driver Installation" no problem.
Then I install it into a voodoo210 frame, plug in the motors, buzzer, and uart/sbus to my receiver. I plugged that in and checked my video, no problem. I spliced the appropriate wires and plugged in a lumenier tx and camera.
I changed the vxt to 12v and the cam to 5v as per the manual. Only thing I did to it was change the solder jumpers for video. Just got a powercube from getfpv day before yesterday.