@peterbarker Peter, do you have any idea why the ROVER wiki does not expand its left sidebar TOC tree when an item is clicked....ie if on Full Parameters List, you should see the params grouped by name with an + button to expand them...like the other wiki sites....it doesn't for Rover....I suspect something in how that side bar is defined as a TOC tree in the index.html
now every wiki builds that left TOC differently, but only Rover does this
Hi @Hwurzburg, I was wondering if you could have a look at whether this commit (https://github.com/ArduPilot/ardupilot_wiki/commits/master/common/source/docs/common-commercial-support.rst) has perhaps caused the commercial support page to be moved or something? I can't get to it from ardupilot.org's Community / Commercial Support link
I've added a couple of pages to the Copter and Rover wikis that start to explain the BendyRuler and Dijkstra's path planning object avoidance. I created new pages and added them to the Advanced Configuration page but really we should probably make an Object Avoidance landing page and then link them from there. I can do that next week after the OpenPilot conf is over.
next call Tues PM/Wed AM 2300utc
What version of Ardupilot should the wiki adhere to? The situation is I've been working on obstacle avoidance and have been informed that Obstacle Avoidance is working in Auto mode in Copter 4.0. Whereas these pages http://ardupilot.org/copter/docs/copter-object-avoidance.html http://ardupilot.org/dev/docs/code-overview-object-avoidance.html state that it is not. I so I was wondering if the wiki should adhere to the latest stable version or dev version? or if there were different standards for the different wikis
Unfotunately we dont have versioning in the wiki....its a project we would like to do in the future...usually the wiki is behind even the stable release, but we are working to get it inline with beta releases....4.0 is close in that regard....however, the parameters list in the wiki ALWAYS reflects the latest master...something else we are working on...
@bromeara short answer: there are several proximity sensor based object avoidance modes in Copter....a slide/stop one for LOITER, an escaping one for ALTHOLD, and two path re-routing ones for AUTO (bendy and Dijkstra algorithms)...the first two are activated with AVOID_ENABLE, the path rerouting ones with OA_TYPE....
next call Tues PM/Wed AM at 2300UTC
I've created a new "Getting and Setting Parameters" page under the developer wiki's "MAVLink Interface" section. All feedback welcome especially from the likes of @peterbarker, @tridge or anyone else who has actually written code to read/write parameters (I never have!) http://ardupilot.org/dev/docs/mavlink-commands.html
(note the page linked above will update with the new "Getting and Setting Parameters" about 10min after this post)
next call Tues/Wed 2300UTC
not sure how to make the other one update though
new wiki page for setting up a Gremsy gimbal: https://ardupilot.org/copter/docs/common-gremsy-pixyu-gimbal.html
I wonder if the parameter descriptions on the wiki have stopped updating because it seems that ATC_RAT_RLL_FILT is listed but that doesn't exist in master anymore (https://ardupilot.org/copter/docs/parameters.html#atc-rat-pit-filt-ac-attitudecontrol-multi)
I'm not sure exactly how this works, but I think that's coming from here: https://github.com/ArduPilot/ardupilot/blob/master/libraries/AC_AttitudeControl/AC_AttitudeControl_Multi.cpp#L214
I've added some extra info at the bottom of the independent watchdog page. it's quite developer specific but might be helpful still. https://ardupilot.org/copter/docs/common-watchdog.html
Hopefully it's not too controversial but I've created a PR here to modify the top menu bar. ArduPilot/sphinx_rtd_theme#13
