I actually got the list from a previous thread on this forum. There is a list I printed and laminated and put in my case. The main prep I'm back to doing and got lazy on is making sure I've prepped a level pad and will not initialize the H unless it's sitting level. I've gotten into the habit of removing camera post flight so it's not hanging all the time in storage and easier to pop SD card out to load into editor.
I'm currently shooting winter sunrises and going for hover shots where you can watch the mountains light up and clouds change hue. It requires starting in blue dawn through golden hour and can be over 30 mins of shooting to get the perfect minute. Before I commit to the camera, I pop the H up about 8' and raise the gear and watch for drift. If I see some, I'll land and calibrate the compass using facing north on my prepped level pad as my starting point.
The other day I got a shot from my own backyard but had a left yaw drift. I checked the hardware monitor and sure enough left stick is acting funny. It took three ST calibrations but I got the stick back to proper ballistics.
My point has been on this forum since I joined is that this machine is very complicated and overly smart to the point of lulling you into some assumptions that can be crash causing. You cannot cut corners on getting the starting information correctly into the IMU and compass and it's overly sensitive to outside factors. Unfortunately, there are some gaps in the suggested procedure and starting level is one of them.
I'm fully aware some may want to dispute my conclusions so here is some proof of the H behaving the way I want it to.
Sent from my iPhone using Tapatalk Pro