Yes but…
The problem was that the board heat target param, IMU 2, IMU 3 Temp cal enable param, etc were of no use to me. Because my board has only 1 IMU. So i did that.
So today I wasted 2 hours thinking that it’s being calibrated 
And now I will re run it.
I suspect the calibration is finished, and that is why it is no longer running.
Anyway, you need to upload the 02 file, and wait that it gets validated. Do not upload the 03 (yet).
The 03 gets automatically downloaded (not uploaded) once you provide the .bin file.
It doesn’t really take 2 hours to get to this temperature. Maybe under an hour. I think it’s definitely finished as the condition for the calibration to finish is less than 0.5 deg C rise in temperature in 10 mins
You enabled the tuning checkbox. But now you have to double click on the top bar somewhere where it says the label of the currently plotted fields, for example, click on Roll (deg). Then a dialog box appears and from there uncheck all the unwanted fields and check IMU temperature
Yes even I read that line in documentation. The fact was that no buzzer was connected to my FC and I thought the RGB light on Kakute will start behaving normally when calibration will complete. But that didn’t happen I think.
Currently, My Kakute has been once again sent to enjoy vacations in Antarctica and I will perform the calibration once again.
Okay, if you have LOG_DISRAMED set to 1, you can verify the data later and check if the calibration did indeed run
Or you could just look at the temp cal parameters, and if they are non-zero, it worked…
AMC has set LOG_DISRAMED to 1 already.
Please see that I have again now started the temperature calibration and in the messages tab, just after a minute of powering up the cold Kakute, this message appeared:
“TCAL[1]: Completed calibration tmin = 2.1 tmax= 12.3”
What does that even mean!?
I configured it so that this appears now:
I even have connected an active buzzer to Buzz+ and buzz- pins of Kakute but that buzzer never even beeped a single time from the power on of kakute
I fixed this problem by manually setting INS_TCAL1_MAX to something like 60 (a value greater than the max expected temperature your IMU will reach) and INS_TCAL1_MIN to something like -20 and then re-running the calibration. Not sure but maybe using the AMC will take care of this
In AMC, on IMU Temp calibration screen, only these parameters are available by default:
And in which, that TMAX parameter is deleted by me because N/A written in front of it.
I don’t think you are supposed to delete anything for normal reasons.
Anyway can you set those params like I told in MP and try again?
Press the Add button to re-add the INS_TCAL1_MAX or any other parameter that you want.
Yes. This time, I have selected, added everything we previously and will upload everything to Kakute H7 like a good boy
@amilcarlucas Have you seen this before? I compared the params from 03_imu_temp… against what was saved to the FC in MP and it all looked like it was there.
Do you have a gyro 3?
Probably not, delete that parameter.
Yes, the parameters are different and that is normal, You re-calibrated the IMU right?
This same error exactly also appeared in front of me when I uploaded all selected params.
It said that the board heat target, and INS TCAL3 ENABLE got failed to upload. And that’s very obvious too
Allister seems to have an accel3, so…
@Allister did you pressed retry?
Sometimes ArduPilot silently ignores parameter changes. It is a know bug in the ArduPilot parameter protocol. So it needs to retry to set the parameter correctly. AFAIK @peterbarker has been working in fixing this in the ArduPilot firmware.
MP and other GCS fail silently, AMC detects it and asks you if you want to retry.
