Yesterday I did some edits, namely enabling harmonic notch (which I had previously forgotten) and some other things like proximity
Then I upgraded to a new custom built FW (on Kakute F7 AIO it’s needed for CRSF telemetry to work)
I also saved the parameters to a new file on disk, like I do all the time when editing
Today when I wanted to fly it:
All the edits were gone (later confirmed by downloading params to disk again) - but I thought well, it flew ok with the old settings, so I’d test those again at least
Shortly after launch, the copter tilted to the right and threw a dozen errors at once
Is this an issue with this copter (which flew perfectly before), or does it more look like I simply caught a bad latest version with the custom FW builder?
Thanks!
Bonus question (not worth another thread I guess):
From the wiki: “Set INS_HNTCH_FREQ and/or INS_HNTC2_FREQ = below the hover frequency - you can easily determine this by performing a gentle hover and looking at the ESC telemetry data”
It occured to me that I never quite understood how to do that, so on my other (smaller) copters, INS_HNTCH_FREQ and INS_HNTCH_BW were simply left on default. But it would be interesting to know what value to look at and what calculation to make.
This is the file I saved along with the build (I guess it can be found in FW builder history by the hash, but I don’t know how) - is it plane? It’s very hot here so any kind of error can happen I guess…
The feature list looks incomplete though. Of course I will try again anyway. I just thought if I didn’t mistakenly select plane, could this be a bug in FW builder?
EDIT2: Finished in the meantime, will flash it later. Is there any way I can make sure at home that it will not do the things it did when I tried flying?
Of course, I just thought there might be a way to specificly check for all those errors I got yesterday - but on the other hand, strike that: I usually have almost no GPS reception indoors, so it wouldn’t be possible anyway.