And what exactly is this "bug"?
When I board dies during firmware flashing it's obviously not a firmware bug as the firmware is not running at the time.

Another thing for those who think they have "bricked" KK2s...
Probably the only person who has reflashed a KK2 board more times than me is Kapteinkuk himself.

My development KK2 has been flashed at least 1000 times and still works fine, but it won't always flash. There are a number of scenarios that I found screw up the flash process.

While Lazy's flashtool works perfectly for me, it was much quicker for me during development to make a batch file that ran avrdude from the command line. No verify - double-click on the icon and burn.

Sometimes avrdude would just abort and exit as it tried to start the process, sometimes it would do this five times in a row, but I would just keep trying until it gave in.

On rare occasions it, or the driver would get all mixed up and removing and reconnecting my USBasp would solve the problem.

But one thing that would *really* piss off the programmer and/or avrdude was having a ground loop formed by externally power devices. For instance, while testing the battery monitor, I had a mains-powered power supply hooked up. I don't remember the specifics but that would lock up the programming in certain circumstances.

Similarly, having the ground clip of an oscilloscope lead attached would also bugger up the programming process on occasion.

In both the above cases, removing the external connection fixed the problem.

I don't think it is possible to "brick" a KK2 otherwise either I or Kapteinkuk would be sure to have done it by now.

For those with blank LCD screens - can you try flashing OpenAero2 on it to see if that works? You can always flash it back.

Early reports are that when the eeprom is corrupted on the KK2, you can get a blank screen. If you cannot properly do a factory reset, try flashing OpenAero2 first, to confirm that all is working. I'm fairly sure it's immune to a corrupted eeprom.

Another thing for those who think they have "bricked" KK2s...
Probably the only person who has reflashed a KK2 board more times than me is Kapteinkuk himself.

My development KK2 has been flashed at least 1000 times and still works fine, but it won't always flash. There are a number of scenarios that I found screw up the flash process.

While Lazy's flashtool works perfectly for me, it was much quicker for me during development to make a batch file that ran avrdude from the command line. No verify - double-click on the icon and burn.

Sometimes avrdude would just abort and exit as it tried to start the process, sometimes it would do this five times in a row, but I would just keep trying until it gave in.

On rare occasions it, or the driver would get all mixed up and removing and reconnecting my USBasp would solve the problem.

But one thing that would *really* piss off the programmer and/or avrdude was having a ground loop formed by externally power devices. For instance, while testing the battery monitor, I had a mains-powered power supply hooked up. I don't remember the specifics but that would lock up the programming in certain circumstances.

Similarly, having the ground clip of an oscilloscope lead attached would also bugger up the programming process on occasion.

In both the above cases, removing the external connection fixed the problem.

I don't think it is possible to "brick" a KK2 otherwise either I or Kapteinkuk would be sure to have done it by now.

For those with blank LCD screens - can you try flashing OpenAero2 on it to see if that works? You can always flash it back.

Early reports are that when the eeprom is corrupted on the KK2, you can get a blank screen. If you cannot properly do a factory reset, try flashing OpenAero2 first, to confirm that all is working. I'm fairly sure it's immune to a corrupted eeprom.

Reminds of the free flight board users that accidently selected to globally erase pages when re-flashing the board with tc's baseflight firmware. He wrote a "fix" firmware that had to be used before any other firmware could be flashed back on. The boards seemed to be "bricked" or "dead" but in reality were just not responding to the current fimware.

Now I know why alarm was not working for me
30minutes ... it is an eternity ... should be no more then 1 or 2 minutes

Tchuss

E_lm_70

Ps: cppm mode, once activated I would expect that the kk2 board does not read anymore the rx signal with kept the 4 independent channels, instead it work in the same way independently by the configuration .... strange .. tomorrow I will plug my rx with cppm support ... it would have been nice to read also rssi (ppm), since most of rx that support cppm also provide rssi

I just finished all testing... replaced the rear left esc and now temperatures are all equal for motor and escs.

Installing new firmware was a breeze on the pc, after giving up on the mac. Impossible to get the kk2 to show up on the mac.

With the new firmware, no adjustments had to be made to hover the tbs discovery i.e. 450 size. I also tried the cppm, which works but I could not get aileron to work after trying ch 5 to 8. what this could mean is only 4 ch works with my futaba anyways, therefore no auto level if I really wanted to use cppm. very cool firmware.

The CPPM algorithm decodes 8 channels. I did not get your problem, can you explain more?

Quote:

Now back to my original problem, if I fly smoothly it doesn't seem to have any motor cuts, but if i keep punching the throttle, I hear a sort of beep, like the motor is cogging/perhaps losing sync and it could be any motor that decides to cog and down it goes. I will replace the escs with f30a when I receive them and try again.

Mixed success with my firmware upgrade, but only negatives are due to me!

I got a huge amount of waggle on the yaw servo (analogue)

Have you set the LP to 50? If so, try 90 and up to 99.

Quote:

and played with the PI values, to no avail - simply because I really need to read bout how they work! I suspect the rear motor had started to de-mag due to overheating now - but that is my fault for flying too long without having dialed out the waggle I guess.

I'll research how to fine tune the PI before I try again - I'm sure I have seen some good guides on here. Plus, also look for a digital servo as I understand that may help?

When it flew, it felt a lot better than the original HK board, even with the waggle!

I was up last night till about 2:30 AM working on the KK2 flashing video, etc. and this message came up all of a sudden. This has to be a new feature programmed in by Rolf to placate our spouses who complain about us staying up all night long working on our multrotors. Is there a time adjustment on this?