Well, after my previous troubles, I bought new batteries (5200 mAh), and the drone flew fine with them; I did about three or four flight of 10-11 minutes.
Today, the perfect day for autotune, after about 14 minutes and 50 seconds in flight (most part in autotune), the drone very suddenly fell out of the sky.
The battery monitor is set up, and should either land or RTL when the battery is low, but appartenly it didn’t, so either the battery monitor is not working or there is something else wrong. The drone did this with my old batteries also, but much sooner in flight (after about 7 minutes), and these batteries had only 2200mAh, so I still suspect a connection.
Something is strange with your battery voltage in the log. It’s off by a factor of about 1000. This might be why the low voltage protection didn’t kick in.
Furthermore, this craft was in no condition to run Auto Tune. Almost immediately it was producing failure to level error messages. PID’s at default and the notch filter is misconfigured.
You guys are right about the value BATT_VOLT_MULT parameter, but I did not touch that parameter ! In the docs it says clearly: " Note: This parameter is for advanced users", and hence, I didn’t touch it (I hardly understand what it does and I’m far from an advanced user ) !
It that value dependend or automatically filled in somewhere (default is 10.1 in my parameter list) ? Allister suggest 19.9 as a better start. Should I set it to 10.1 or 19.9 ? I also see other values in the description, so to avoid misunderstandings, this is the Pixhawk I’m using:
It worries me that there’s a wrong value in there, while I’m 110% sure I didn’t go near that parameter … Anyway, I’m glad you guys found something really wrong, so I can rectify it.
Now that I’ve read that procedure, I remember doing it without knowing it worked on that parameter, and I remember getting some “strange” values … That’s probably the cause.
) !