I have attached my CLI dump from from 1.13 as well as the dump immediately after flashing to 2.3.2 (without pasting the 1.13 settings). I have no problem starting from scratch on the new firmware and redoing all of my settings if that's what it takes.
In order to regain my settings from 1.13 I'm doing a manual dump (copy/paste) from CLI. Here are the build specs:Įmax MT2204 motors w/ BL Heli 12A ESCs (this is the Power Pack E from about 1.5 years ago)
Maybe I'll just be stuck at 1.13 and an old version of CF configurator if I want to keep this thing in the air? Reverting back to 1.13 of Naze firmware + my old settings and all is well. In both cases the board indicates a solid red LED and a slow blinking green LED. No response from Taranis receiver here either.
No response from the motors tab even if I use the ESC calibration sequence (master at full power, plug in battery, no audible esc noise)Ģ) When I am not connected to Cleanflight via USB and plug in a battery I get some an initialization beeps from the board, but not the ESCs. Unfortunately, I run into the same issue.ġ) When successfully connected to the board via USB I plug in a battery and get no audible initialization from the board OR escs. I get a programming failure if "no boot sequence" is checked. I have tried to flash firmware with and without "full chip erase" selected. I've confirmed that Firmware 2.3.2 is loaded to the board as indicated in the upper left of the CF banner. After your comment, I've updated it to 2.4 and repeated the firmware flashing process. Is this board not compatible with the newest Cleanflight Firmware? Is there something I'm missing here? Any help would be greatly appreciated. Battery is plugged in, props are off, Naze is successfully connected to CF I've tried pasting all of my 1.13 settings into 3.2 and this doesn't fix it.
I get no ESC initialization beeps upon start up either. The motor control tab doesn't work and I also get no input from my Taranis. I'm able to flash the firmware fine (jumping boot pads, flashing in CF), however I get no motor control.
Also, I'd like to do some PID tuning and Cleanflight configurator is telling me I need to upgrade the firmware in order to use the setup tab. It works fine with Version 1.13 firmware, but I'd like to upgrade to the newest (3.2) firmware since it's been a good 1.5 years since I worked on this thing. I'm reviving the guts of my old Versacopter with the Naze32 Rev 6 board. I was using Cleanflight / SPRACINGF3EVO 2.1.0 with the FRF3_EVO_BRUSHED Flight Controller.I apologize if this has been answered, but I've used the search function and have not found my answer This is same configuration that I used when I downgraded to 2.0.5 - actually I downgraded, entered defaults and then applied this set of parameters (though rc_expo_yaw was called rc_yaw_expo prior to 2.1.0 - so I had to change that).
I've attached the output produced by diff for the 2.1.0 setup I was using - see parameters.txt. C - Video Links D - Forum post links E - Version InformationĬonfigurator: v2.1.0 or commit SHA E - Other information The craft flies fine - but the continuous beeping drives one to land it and stop. B - Steps To RepeatĪrm the QX95 - apply throttle, once the the propellers start spinning the armed-but-no-throttle beeping stops but once enough throttle is applied that the craft takes off a very similar but slightly more erratic beeping starts. So the beeping seems to be the result of some change introduced in 2.1.0. I assumed that I'd got something wrong when connecting up the buzzer (a Matek WS2818B combined buzzer and LED strip) so I took it home and checked everything but couldn't find any issue.Īs I'd had the same setup working without issue on another QX95 running Cleanflight 2.0.X I eventually downgraded to 2.0.5 and this resolved the problem. it wasn't just erratic occasional beeping. It was very slightly more irregular than the armed-but-no-throttle sound but still fairly regular, i.e. When I took it out for its first flight I found that it beeped continuously during flight - the beeping was similar to the armed-but-no-throttle beeping sound, i.e. I used a parameter set that had worked perfectly with a previous QX95 running 2.0.X versions of Cleanflight. I upgraded a new Eachine QX95 to 2.1.0 and added a buzzer.