This topic does not relate to official Ardupilot documentation / website.
Chris Rosser made a famous Ardupilot Tuning guide in Youtube/PDF that a lot of novice follow because it’s simpler and ardupilot documentation requires a much more reading and understanding of the topic. Unfortunately it have some issues, like confusion with notch filters configuration
INS_HNTCH_MODE = 3 (RPM)
Set RPM1_TYPE = 5 for bidirectional DShot
Set RPM1_ESC_MASK = 15 for all 4 motor
What other issues comes to your mind? Or it’s just generic simplification approach is a problem?
Here is a link to guide
My list of improvements:
Page 11
BetaFlightX 12 or BetaFlightXReversed 18 FRAME_TYPE might be more appropriate if move from BF
Page 20
Dshot600 is preferred but had no problems with 300 too
Page 24-25
Frame type from page 11 should set correct motor order, but checks must be made.
Page 26
Magfit mention might be +
Page 28
Fast and Medium attitude and Fast harmonic notch logging / Fast IMU
Page 29
INS_LOG_BAT_OPT=5 but 4 is enough as documentation suggest, also RAW gyro logging should be mentioned.
Page 35
INS_HNTCH_MODE=3 (RPM) should be replaced to (ESC Telemetry)
Page 36
RPM1_* parameters should be removed
Page 72
Note about autotune on bigger notes sometimes makes sense, agree that manual tuning is safer but more time consuming.
Pages 108-133 should be changed with 4.7 in mind
Else nice to have:
No things like ATC_THR_MIX_MAN or ATC_INPUT_TC mentioned
The issues are many. It’s unfortunate because his popularity and presentation style could really be great for AP. Unfortunately, he has ignored every attempt made to reach out and help correct the errors in his videos.
The issues list would be useful at least for novices, also for Chris. I think his biggest problem that his video have slides which is tricky to replace.
Anyway with version 4.7 his pdf guide need to be updated and it is good chance to fix.
I’m afraid many of us have effectively written it off. I hate that it is that way, but there have been more than several attempts at contact via various means, none of which have garnered response.
Should you wish to compile a list of issues, it’d be welcome in this topic, but I expect that it wouldn’t be as productive as you’d like.
I’d also like to be proven wrong, but I’m not going to put any more effort forth at this point in time.
Best advice is to avoid viral videos and stick to ArduPilot’s own documentation and resources. If you wish to spend money on configuration and tuning, spend it on a couple of professional consultation sessions with vetted experts rather than on unofficial “courses.”
As a start, I’d like suggest that we use this thread as a record of issues that folks find. Maybe Chris will read them and eventually get around to correcting his material. At worse, this could be our first stab at an errata, yeah?
I’ve gone ahead and renamed this thread as such and marked Mike’s list as the solution
.