Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 06:14

    rmackay9 on master

    Rover: boat page echosounder li… (compare)

  • 06:12

    rmackay9 on master

    Common: move echologger link to… Common: add bluerobotics ping s… (compare)

  • Sep 17 21:37

    Hwurzburg on master

    Fix note format in heliquads (compare)

  • Sep 17 21:37
    Hwurzburg closed #2018
  • Sep 17 21:37
    Hwurzburg commented #2018
  • Sep 17 21:37
    Hwurzburg opened #2018
  • Sep 17 19:58

    Hwurzburg on master

    Fix spelling of "telemetry" Th… (compare)

  • Sep 17 19:58
    Hwurzburg closed #2016
  • Sep 17 19:58
    Hwurzburg commented #2016
  • Sep 17 19:57

    Hwurzburg on master

    Common: RC output update for tr… Common Wiki: fix mistake in tab… (compare)

  • Sep 17 19:57
    Hwurzburg closed #2017
  • Sep 17 19:57
    Hwurzburg commented #2017
  • Sep 17 15:49
    bnsgeyer opened #2017
  • Sep 17 15:30
    brunoolivieri commented #2016
  • Sep 17 15:29
    brunoolivieri labeled #2016
  • Sep 17 14:31
    larsks opened #2016
  • Sep 17 13:33
    MasterBoBo commented #1982
  • Sep 17 11:21
    brunoolivieri labeled #2015
  • Sep 17 06:40
    peterbarker commented #2015
  • Sep 17 06:40
    peterbarker opened #2015
Randy Mackay
@rmackay9
I've reworked the camera-and-gimbals section of the wiki to add indivual pages for the know camera triggers and geotagging options. http://ardupilot.org/copter/docs/common-cameras-and-gimbals.html
There's still a fair bit of work to do on the pages that describe how to trigger the camera during a mission. There's basically 4 pages that contain a lot of duplicate information.
oddvardm
@oddvardm
Hi There people. New to this and have a couple of questions. Need to use ardupilot with drone sim mode - AirSim. Need to get some directions on how to install and build it. Have read http://ardupilot.org/dev/docs/sitl-with-airsim.html?fbclid=IwAR0kM1Evl0IVu1tmhM_jsXjH7ne94_RtdbEDoCmIHOrnghLCeAZWpBu7qs4 but uncertain on what to do. Anybody willing to help?
Rajat Singhal
@rajat2004
@oddvardm Hi, what platform are you installing AirSim on, Windows or Linux?
Can you let us know where the instructions are unclear so that it can be improved
The installation process is time-consuming on both, especially if starting from the very bare minimum
oddvardm
@oddvardm
Hi Rajat. I have the standard environment up and running on a Windows maschine. I am fairly new to this environment so I am a little reluctant to stand by the claim that docs are sctchy. I will rather state that my knowledge is scetchy :-) I have two simulations set up. Blocks and MyLandscape (the same as in your video). I can explain my inteded use of the Airsim so that you (and others) can get a better feel of my intended use of it. I intend to build a multi user environment with a c++ SITL that will send drone tracking data to a UTM system (Unmanned Traffic Monitoring) system and need a cheap piloting system. After checking your work you have a keyboard interface but dont support the AirSim API's yet. However I think that it is just a matter of time before you do. In the docs you launch it with phython and I wonder if you will support C++ soon?
Rajat Singhal
@rajat2004

@oddvardm Yes, adding support for the Airsim APIs is one of the main goals, however currently I'm working on adding support for the Rover vehicle in AirSim
I do have a few ideas on how to go about adding that but haven't tried them till now

Re the setup, I'm not sure if I'm following it correctly, it's a multi-user (or multi-vehicle?) environment with an external connection to a Monitoring system
Any GCS can be used with this, I have used MAVProxy (which is the command line one in the video)
Yes, I'm using sim_vehicle.py to launch the vehicle, however you can directly launch the binary itself if needed
Dronekit is another API which could be used to control the drone, however it's also a python library

Rajat Singhal
@rajat2004
You could use ROS if C++ is needed, but that can a bit over the top
oddvardm
@oddvardm
Thank you Rajat. Multiple vehicles is my intent. Yep all clear. Will spend more time with the environment and check out your suggestions :-)
Henry Wurzburg
@Hwurzburg
@rmackay9 @brunoolivieri PRs now entered which eliminate all plane specific wiki build errors....now on to fixing common file errors used by plane....eating the elephant one bit at a time....
Bruno Olivieri
@brunoolivieri
@Hwurzburg I plan to help with that too, maybe starting with copter because that is what I fly. However, I wanted to expect a quick review of @rmackay9 in the table in issue # 1869 because I fear I misread any of the parameters.
Henry Wurzburg
@Hwurzburg
@brunoolivieri @rmackay9 All TOC issues (except one I dont know how to fix) in the common docs are resolved....I will now work on all the Rangefinder issues caused by creating multiple rangfinder params but not changing the parameter references in the common docs......yep, Bruno, good plan...that is why I tackled plane stuff first....if you can get all the copter specific build issues resolved that would be great...I'd start with the copter specific non-common TOC and missing doc ones first since it doesnt involve content, just doc refs...then the param refs...
Henry Wurzburg
@Hwurzburg
@brunoolivieri @rmackay9 All rangefinder errors (not requiring parameter code rework) are now eliminated....should be able to clean up all remaining Plane site errors tomorrow before I leave on vacation Tuesday....nice to only have a 1/4 screen of red now after a build of the site...can actually see when you make format/link errors on Wiki changes now!
Bruno Olivieri
@brunoolivieri
I did some separated PR for fix references errors in the Wiki. I did it separated because I have only web access right now. If it is annoying, please let me know in order to do not do it again. However, I also think it is easier or fast to the review and approval process.
Henry Wurzburg
@Hwurzburg
Super...thanks...I verified and built and merged most...one had an issue and another should fix another error in the same file....but a bunch of errors bit the dust today...thanks again....
Bruno Olivieri
@brunoolivieri
Great! Thanks!
Thien Nguyen
@hoangthien94
Hi all, I wish to add support for non-GPS flight with apriltag and ROS to ArduPilot wiki, based on the content of this blog.
I know that we already have http://ardupilot.org/dev/docs/ros-aruco-detection.html, which would be similar to the apriltag implementation in terms of system description, parameters for ArduPilot, how to do ground test and flight test; but would differ on the tag and ROS sides (the tag board, package installation, how to run all the nodes).
Thien Nguyen
@hoangthien94
So I think of two options:
  1. Create a new wiki page separated from the existing ros-aruco-detection page, maybe ros-apriltag-detection, uses similar title and content outline for consistency between the two wiki pages, only add changes where necessary.
  2. Modify current ros-aruco-detection page to include the new apriltag support, and change the title to something more inclusive like ros-fiducial-marker-detection
Thien Nguyen
@hoangthien94
Any advice or guidance would be greatly appreciated!
Francisco Ferreira
@OXINARF
@rmackay9 You have more experience with ROS, what you think of the above?
Rajat Singhal
@rajat2004
Is there any way to have links to headings within the same page itself?
Bruno Olivieri
@brunoolivieri
You can create a new landing page, and then, link to both as a toctree. I saw thien already did a PR, I can help whith this during the week.
Bruno Olivieri
@brunoolivieri
I think we have enough PRs for the next wiki meeting (at least some discussion is needed). I guess we said something as to do the meeting every 15 days and the last was august 13th. I think that would be handy a meeting next week on 27th.
Henry Wurzburg
@Hwurzburg
Should be on next Tue/Wed....update to leave at will go out this weekend...I will be back from vacation tomorrow evening
Update to list,rather
Henry Wurzburg
@Hwurzburg
Wiki call in 7 min
Randy Mackay
@rmackay9
yup
Henry Wurzburg
@Hwurzburg
@rmackay9 as of now, plane and copter wiki build with only the Holybro H7 board errors and the rangefinder param errors...the latter will disappear when @auturgy updates it when the H7 is announced, I assume....the former when we beta the new rangefinder code and release the delay merge on the PRs that update the wiki to match the current param list for rangefinder....
I got all the errors fixed in the Rover wiki (PR pending) except those caused by code issues involving parameter defintions...or things I dont understand...here is the list....it will take coding changes for many....and a discussion with @rmackay9 to make the changes in a few areas where I dont know what the proper description/param change would be:
Henry Wurzburg
@Hwurzburg
these params are double defined in code and need to be fixed
/home/henry/Desktop/ardupilot_wiki/rover/source/docs/parameters.rst:47214: WARNING: Duplicate explicit target name: "wp_speed".
/home/henry/Desktop/ardupilot_wiki/rover/source/docs/parameters.rst:47232: WARNING: Duplicate explicit target name: "wp_radius".
/home/henry/Desktop/ardupilot_wiki/rover/source/docs/parameters.rst:47250: WARNING: Duplicate explicit target name: "wp_overshoot"
 **these params do not exist...what replaces them?**
/home/henry/Desktop/ardupilot_wiki/rover/source/docs/rover-tuning-navigation.rst:36: WARNING: undefined label: speed_turn_gain (if the link has no caption the label must precede a section header)
/home/henry/Desktop/ardupilot_wiki/rover/source/docs/speed-turn-parameter-tuning.rst:18: WARNING: undefined label: speed_turn_gain (if the link has no caption the label must precede a section header)
/home/henry/Desktop/ardupilot_wiki/rover/source/docs/speed-turn-parameter-tuning.rst:26: WARNING: undefined label: speed_turn_dist (if the link has no caption the label must precede a section header)
/home/henry/Desktop/ardupilot_wiki/rover/source/docs/steering-mode.rst:13: WARNING: undefined label: speed_turn_gain (if the link has no caption the label must precede a section header)
**these params are not in new rangefinder params...what replaces them?**
/home/henry/Desktop/ardupilot_wiki/rover/source/docs/rover-object-avoidance.rst:24: WARNING: undefined label: rngfnd_triggr_cm (if the link has no caption the label must precede a section header)
/home/henry/Desktop/ardupilot_wiki/rover/source/docs/rover-object-avoidance.rst:25: WARNING: undefined label: rngfnd_turn_angl (if the link has no caption the label must precede a section header)
/home/henry/Desktop/ardupilot_wiki/rover/source/docs/rover-object-avoidance.rst:26: WARNING: undefined label: rngfnd_turn_time (if the link has no caption the label must precede a section header)
/home/henry/Desktop/ardupilot_wiki/rover/source/docs/rover-object-avoidance.rst:27: WARNING: undefined label: rngfnd_debounce (if the link has no caption the label must precede a section header)
  **this param needs to be renamed in code...its currently SAIL_SAIL_NO_GO_ANGLE!**
/home/henry/Desktop/ardupilot_wiki/rover/source/docs/sailboat-configure.rst:36: WARNING: undefined label: sail_no_go_angle (if the link has no caption the label must precede a section header)
is ch 7 a fixed aux channel?...there is a aux_channel param....will RCx_OPTIONS replace this soon? have to understand those two params to fix this
/home/henry/Desktop/ardupilot_wiki/rover/source/docs/common-rcmap.rst:52: WARNING: undefined label: rover:learn_ch (if the link has no caption the label must precede a section header)
dont know how to fix this...tried many times
/home/henry/Desktop/ardupilot_wiki/rover/source/docs/common-vio-tracking-camera.rst:94: WARNING: Could not lex literal_block as "python". Highlighting skipped.
/home/henry/Desktop/ardupilot_wiki/rover/source/docs/common-vio-tracking-camera.rst:136: WARNING: Could not lex literal_block as "python". Highlighting skipp
Henry Wurzburg
@Hwurzburg
Update...to anyone following above....PR to code base for WP_xxxx dups submitted....."SAIL_SAIL_NO_GO_ANGLE" fix merged in code...Randy will work on new rover-object-avoidance for next release...wiki PR submitted for speed_turn_gain/dist and learn_ch errors...Randy might look at the code block error...
I've created a "Reference Frames" section in the Copter wiki. It's got two frames in there to start with. Rover has a similar section on it's wiki
To be consistent I think we should probably do something similar for Plane. Plane's wiki has similar kinds of info
MasterBoBo
@MasterBoBo
Hi there, I'd like to help to maintain ardupilot_wiki, preferably to translate wiki into Chinese. What should I do ?
Luis Vale Gonçalves
@lvale
it is linked from this page http://ardupilot.org/copter/index.html
MasterBoBo
@MasterBoBo
@lvale Thx
MasterBoBo
@MasterBoBo
I've read the content on http://doc.cuav.net/tutorial/copter/, It's mainly focused on multirotor vehicles, I've already translated traditional-helicopter-tuning part from http://ardupilot.org/copter/docs/traditional-helicopter-tuning.html to Chinese
I've made a pull request on github and I am happy to provide the document to CUAV or anybody to help with the build of wiki.
Henry Wurzburg
@Hwurzburg
update to PR status ArduPilot/ardupilot_wiki#1756.
next call Tues PM/ Wed AM at 2300GMT
Henry Wurzburg
@Hwurzburg
wiki call in 5min
Henry Wurzburg
@Hwurzburg
@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
Henry Wurzburg
@Hwurzburg
even though they all use the same common-advanced-parameters file to call the full parameter list and its the same <parameters> link to that wikis parameters.rst file
now every wiki builds that left TOC differently, but only Rover does this