bluerobotics / ardusub-gitbook Goto Github PK

https://www.ardusub.com/getting-started/installation.html#
we should point to QGC official links

After ArduPilot/ardupilot#14452 is merged, we'll need to update it

migrated from bluerobotics/retired-ardusub-docs#7

Good rundown at http://discuss.bluerobotics.com/t/rov-horizon-not-level/1056/2

Specifically, the formats supported.

Examples of how to interface with the rov using pymavlink:

Managing mavproxy inputs/outputs
Stopping mavproxy
Running script locally on ROV vs running on remote client.

• Serial connection
• UDP connection
• Camera tilt
• lights control
• mode change
• arming/disarming
• manual control
• read depth
• read attitude
• restart

per https://discuss.bluerobotics.com/t/very-remotely-controlled/2467

The pixhawk has a power management IC. The power supply is triple-redundant and will work for any combination of inputs on:

usb (required for comms)
power module input (required for power monitoring)
servo rail (required for camera tilt servo power, the other power inputs will power the cpu, but will not provide a servo power on this rail)
We recommend (and to a functional extent, require) using all three inputs.

To the logging page

• Merge #73
• Add Github token to travis
• Check if generated site is at https://docs.bluerobotics.com/ardusub-gitbook/
  if not, optionally:
  - [ ] Clear bluerobotics.github.io (it is "obfuscating" the bluerobotics.github.io/ardusub-gitbook for testing)
  - [ ] Check the page at http://bluerobotics.github.io/ardusub-gitbook
• Add domain to project settings
• Point DNS to gh-pages

It's not possible to follow the instructions with WSL and docker.
ArduSub-stable branch may be compatible only with Ubuntu 16.04 and not 18.04.
Also related to: #70

MANUAL_SLEW_RATE is not in the list.

https://discuss.bluerobotics.com/t/not-able-to-ping-bluerov2/5098
https://www.ardusub.com/getting-started/installation.html#raspberry-pi

This usually presents itself as no telemetry and no activity of the main LED

we don't overwrite the users mavproxy.params, and that means that users updating won't have the feature

Request an instruction page on how to set-up the ArduSub CC to a Pixhawk serial Telemetry port. I've tried to follow the post here (http://discuss.bluerobotics.com/t/ardusub-initial-setup/272/18), but somewhere failed along the way.

Reason: I have another peripheral that works best on the Pixhawk's USB port and I can't connect two peripherals to the USB port due to different baud requirements.

calibrations, configuring motor directions, channel assignments, etc.

https://www.ardusub.com/operators-manual/button-functions.html

vs

https://www.ardusub.com/operators-manual/button-functions.html

The dark grey circle on the right is not present in the first link.

See https://discuss.bluerobotics.com/t/how-to-start-buildnig-a-custom-frame-configuration/2986/8

putty is not needed, use webui terminal

Probably something like I did to ping-viewer docs but adjusted to gitbook

The function here is pretty obscure, add a detailed doc.

On page "Build ArduSub", the command:

ssh [email protected] "/home/pi/companion/RPI2/Raspbian/flash_px4.py --stdin" < ArduSub-v2.px4

points to the wrong location for flash_ps4.py. The command should read:

ssh [email protected] "/home/pi/companion/tools/flash_px4.py --stdin" < ArduSub-v2.px4

• updating firmware via companion and remote upload instructions
• wifi topside setup
• motor direction configuration
• troubleshooting
• parameter list
• joystick button functions
• wireless topside
• video recording
• command line

https://www.ardusub.com/developers/developers.html

@patrickelectric @Williangalvani @tcanabrava I'm not quite sure what to write down for supported Ethernet cameras here: https://github.com/bluerobotics/ardusub-gitbook/blob/ArduSub-Docs-Overhaul/introduction/hardware-options/required-hardware/camera.md

What are your thoughts?

broken links to stable/dev firmwares
Bug Page: Downloads · ArduSub GitBook

DESCRIBE PROBLEM WITH DOCS HERE

Bug Page: Pymavlink · ArduSub GitBook

Change flight mode example provided reads as if it will command vehicle mode to Stabilize - however when executed changes vehicle mode to Depth hold

discuss.bluerobotics.com/t/raspivid-tutorial-please/1370/

moved from https://github.com/bluerobotics/bluerobotics.github.io/issues/31

Conflict between docs and result:

https://discuss.bluerobotics.com/t/converting-bluerov2-to-auv/3859/3

Bug Page: Pymavlink · ArduSub GitBook

Pi ip address can now be changed via webui network page