I muddled through this for the first time today on a Copter I hadn’t flown in a while. I used v0.6.6 (v0.7.0 was released amidst my tuning sessions). A few thoughts:
It was frustrating to connect/reconnect multiple times, and often I found myself stepping backwards in order to re-trigger the dialog to download from the FC (like the autotune results). That was very clunky.
Likewise clunky was a repeated message that access was denied to the serial port in use for telemetry. Happened with SiK radios as well as over USB. Mission Planner had no trouble connecting, but the configurator refused multiple times. I confirmed the port was open and available more than once (i.e., not in use by another app like MP), but it stubbornly refused to connect pretty often (Windows 11).
The only template I found was the original Taycan, which is tiny by comparison to the Copter I was using, so I needed quite a bit of previous knowledge to arrive at the correct starting point(s). I was also using a Cube with heated IMUs, which significantly changes the first few steps.
Minor bug report: selecting a CAN GPS auto populates the associated parameters with “CAN1_” and “CAN2_” prefixes, which are in error. They should be “CAN_P1_” or similar.
The new harmonic notch web tool is pretty slick, but it could use some more detailed explanation of what you’re looking at and how to optimize. I think I did a pretty good job, and I arrived at a minimally configured notch that seems effective.
The online MagFit tool is awesome, but one of my attempts resulted in a prearm error stating the compass wasn’t calibrated (after updating with the results from MagFit). I couldn’t for the life of me figure out why that happened (all the calibration params seemed complete and valid). I flew another attempt, and it fixed itself up.
I already have some wind estimation data for this Copter, and it was easy to just fill in the known values and move on.
It got dark by the time I got to the sys id section, which is probably for the best. I have no idea what’s going on there. That’s a tuning regime I’ve never attempted. I’ll read up.
For what it’s worth, I attached my param files and associated config below (nothing past 42_system_id_roll.param was accomplished).
All in all, the Copter’s back in the air and flying well. There are a few details I’ve likely previously overlooked that were covered by this method, so that’s a plus. However, I think it’s got a long way to go before it’s user friendly enough to take a brand new user from zero to hero.
ReadyToSkyZD550.zip (500.0 KB)