I think you know we look at this differently. So we may have to just agree to disagree.
The wiki is the tool to learn how to use ardupilot. And if you don’t know how to use ardupilot, how can someone write documentation on how to use it?
I don’t know what process the DEVs go through to release changes. But you wouldn’t expect a new linux command to be released without an accompanying MAN page.
Yes sir - this puts a greater strain on the people who volunteer to write ardupilot code.
But the way I see it - the job of a responsible user is to ask questions that help clarify how to ardupilot works and how to use it. If this sheds light on errors and omissions in the wiki - then the user has done their part in helping the DEVs improve their documentation.
You, yourself claim to want to contribute. I provided the instructions (that don’t require any Linux at all if you bothered to read them).
A wiki is a user-interactive system of information sharing by design.
I will continue to post the instructions where appropriate, even if you refuse to contribute in such a way, as you aren’t the only one reading these replies.
I didn’t understand your comment about “you need 1 for the reference” - I didn’t put two-and-two together to understand that you were referring to the INS_HNTCH_REF parameter.
I had noticed that the notch filter shows up as a single black line on my graphs - and in his video they show up as a line with some width in shadow. Peter explained the difference was the INS_HNTCH_REF parameter.
I’m sorry I wasn’t more astute in getting the meaning of your comment - and I appreciate your good catch!
Download the latest version of ArduPilot Methodic configurator, at the appropriate steps it contains links to the appropriate (of the many) webtool. There is no way to make it any simpler, expliciter or easier to use.