The battery voltage is only showing 17V, yet you’ve mentioned you’ve got a 6s battery.
Has the calibration for the PM been done ?
If not any readings in the log relating to voltage and current are somewhat useless.
But it does show that current went suddenly up by about 5 times.
Sorry, my bad.
Been looking at to many logs lately. This was a log from someone else.
My original thought was that the combination of motors and prop size you’ve got is wrong for a 6s setup.
Looking at the correct .bin file this appears to be confirmed as there is very high current flow.
But given that you’ve mentioned you didn’t perform a PM calibration I can’t comment any further as I don’t know how reliable that data is.
The motor outputs are wildly oscillating hence the torched motor. Drop the rate P&I values in half to start and see if you can get a relatively stable hover. Need to know the thrust hover value to set the appropriate PSC parameters next.
We will add the reduction of P & I values to our checklist for the next test flight.
We are not using Dhot/Bdshot since we are not very familiar with these ESC protocols and usages/configurations. Although it is something that we will investigate in the future, after solving the main issue of the burning motors.
The next step after getting stable flight will be to configure the Dynamic Notch filter and you will want ESC telemetry or bi-directional Dhsot for that. Sticking with PWM now will just cause backtracking later. This are fundamentally initial configurations.
Lowered the P and I terms at both roll and pitch (from 0.135 → 0.07)
Used a 5S - 3300mah battery (we had previously used a 6S)
The copter took off without oscillations and climb to about 2 meters. A brief hover of 1-2 secs followed.
The pilot noticed that the throttle response is a bit laggy. It does not climb/descend at the rate he commands it to do.
1st find another Cloud service for logs. WeTransfer is terrible.
I don’t see that, they are at .10 and still too high because there is still oscillation in the outputs. Look for yourself I showed you how in the image above.
You need to hover for more than a few seconds. 30 seconds or more.
You didn’t set INS_LOG_BAT_MASK to 1 to log data for the Notch filter.
It’s not a good idea to switch to AltHold inside until you have established a MOT_THST_HOVER value.
The problem was solved by lowering the D terms (both for Roll and Pitch). The term right now is around 0.0002. Anything above that led to motor overheating, and abnormal attitude.
We performed the tuning with a 5S battery so the next step is to try 6S and re-do the whole tuning process.
Nothing to see in the 1st log accept oscillating outputs and massive vibration levels. The 2nd log is corrupt.
A D-term that low is not the solution to the problem. The rate Pitch and Roll P terms are still high so you are making no progress. Read the posts above.
We restarted the procedure with a 6S battery. We found some values that seem to work out fine so we headed out to try AltHold after configuring the Hover thrust.
Althold seemed to work relatively fine and tried Loiter also in which the drone flew really well and was easily controlled.
We then proceeded to log the IMU data and set the Harmonic Filters. Although there are some strange results. Below you can find an image of the accelerometers and gyro results. The amplitude is on the negative side. Can this be caused by the configuration of our quad? (X configuration and propellers are on the low side - motors are facing the ground). Also here is the log: https://drive.google.com/file/d/1ljy_uzUqvcymkZf7UV1KBX-Hc3Rj8rjW/view?usp=sharing
It’s not a bug it’s a feature. The 2nd PC probably had an older version of Mission Planner. In any case a log scale, which is what’s shows in your 1st post, is default. There is a “Magnitude” checkbox to change that.