fly316/PX4-Autopilot
7
0
Fork 0
mirror of https://gitee.com/mirrors_PX4/PX4-Autopilot.git synced 2026-10-20 03:13:33 +08:00
Code Issues Packages Projects Releases Wiki Activity

Fix all possible HTTP to HTTPS docs links (#25153)

Browse Source
This commit is contained in:
Hamish Willee
2025-07-03 18:09:58 +10:00
committed by GitHub
parent 375f421c61
commit 2c31e2bad5
84 changed files with 276 additions and 359 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/en/complete_vehicles_mc/index.md
+1 -1
View File
@@ -19,12 +19,12 @@ They may come either fully assembled or in parts.
This section lists vehicles that are sold fully assembled and ready to fly (RTF), with PX4 installed.
- [Teal One](https://tealdrones.com/teal-one/)
- [ModalAI Starling](../complete_vehicles_mc/modalai_starling.md)
- [ModalAI Sentinel](https://www.modalai.com/sentinel)
- [MindRacer 210](../complete_vehicles_mc/mindracer210.md)
- [NanoMind 110](../complete_vehicles_mc/nanomind110.md)
- [Amovlab F410](../complete_vehicles_mc/amov_F410_drone.md)
- [Teal One](https://px4.io/project/teal-one/) ([superseded](https://tealdrones.com/solutions/teal-2/))
## PX4 Compatible
docs/en/complete_vehicles_mc/px4_vision_kit.md
+2 -15
View File
@@ -8,7 +8,6 @@ The kit contains a near-ready-to-fly carbon-fibre quadcopter equipped with a _Pi
The guide explains the minimal additional setup required to get the vehicle ready to fly (installing an RC system and battery). It also covers the first flight, and how to get started with modifying the computer vision code.
:::warning
PX4 no longer supports the avoidance software described in this document:
@@ -16,7 +15,7 @@ PX4 no longer supports the avoidance software described in this document:
- [Path Planning Interface](../computer_vision/path_planning_interface.md), along with obstacle avoidance in missions, and safe landing.
A USB stick is included in the kit with an example of an obstacle avoidance feature implementation based on this software.
This example is intended as a reference only and serves to demonstrate the capabilities of the platform.
This example is intended as a reference only and serves to demonstrate the capabilities of the platform.
:::
::: tip
@@ -73,7 +72,6 @@ What's inside the PX4 Vision V1 can be found here in the [PX4 v1.13 Docs here](h
The PX4 Vision DevKit contains following components:
- Core Components:
- 1x Pixhawk 4 or Pixhawk 6C (for v1.5) flight controller
- 1x PMW3901 optical flow sensor
- 1x TOF Infrared distance sensor (PSK‐CM8JL65‐CC5)
@@ -94,7 +92,6 @@ The PX4 Vision DevKit contains following components:
- WiFi 802.11 b/g/n @ 2.4 GHz (attached to external antenna #1). Allows computer to access home WiFi network for Internet access/updates.
- Mechanical Specification:
- Frame: Full 5mm 3k carbon fiber twill
- Motors: T-MOTOR KV1750
- ESC: BEHEli-S 20A ESC
@@ -105,7 +102,6 @@ The PX4 Vision DevKit contains following components:
- Telemetry: ESP8266 connected to flight controller (attached to external antenna #2). Enables wireless connection to the ground station.
- A USB2.0 stick with pre-flashed software that bundles:
- Ubuntu 18.04 LTS
- ROS Melodic
- Occipital Structure Core ROS driver
@@ -133,7 +129,6 @@ In addition, users will need ground station hardware/software:
## First-time Setup
1. Attach a [compatible RC receiver](../getting_started/rc_transmitter_receiver.md#connecting-receivers) to the vehicle (not supplied with kit):
- Remove/unscrew the top plate (where the battery goes) using an H2.0 hex key tool.
- [Connect the receiver to the flight controller](../assembly/quick_start_pixhawk4.md#radio-control).
- Re-attach the top plate.
@@ -155,7 +150,6 @@ In addition, users will need ground station hardware/software:
Ensure propellers are removed before connecting the battery.
:::
1. Connect the ground station to the vehicle WiFi network (after a few seconds) using the following default credentials:
- **SSID:** pixhawk4
- **Password:** pixhawk4
@@ -171,7 +165,6 @@ In addition, users will need ground station hardware/software:
The vehicle should arrive pre-calibrated (e.g. with firmware, airframe, battery, and sensors all setup).
You will however need to calibrate the radio system (that you just connected) and it is often worth re-doing the compass calibration.
:::
- [Calibrate the Radio System](../config/radio.md)
- [Calibrate the Compass](../config/compass.md)
@@ -182,7 +175,6 @@ In addition, users will need ground station hardware/software:
:::
We recommend RC controller switches are define for:
- [Position Mode](../flight_modes_mc/position.md) - a safe manual flight mode that can be used to test collision prevention.
- [Mission Mode](../flight_modes_mc/mission.md) - run missions and test obstacle avoidance.
- [Return Mode](../flight_modes_mc/return.md) - return vehicle safely to its launch point and land.
@@ -190,7 +182,6 @@ In addition, users will need ground station hardware/software:
1. Attach the propellers with the rotations as shown:
![Motor Order Diagram](../../assets/hardware/px4_vision_devkit/motor_order_diagram.png)
- The propellers directions can be determined from the labels: _6045_ (normal, counter-clockwise) and _6045_**R** (reversed, clockwise).
![Propeller identification](../../assets/hardware/px4_vision_devkit/propeller_directions.jpg)
@@ -212,7 +203,6 @@ When the vehicle setup described above is complete:
:::
1. Check that the avoidance system has started properly:
- The _QGroundControl_ notification log displays the message: **Avoidance system connected**.
![QGC Log showing avoidance system has started](../../assets/hardware/px4_vision_devkit/qgc_console_vision_system_started.jpg)
@@ -309,7 +299,6 @@ To login to the companion computer:
1. Connect a keyboard and mouse to the _UP Core_ via port `USB2`:
![UP Core: USB2](../../assets/hardware/px4_vision_devkit/upcore_port_usb2.png)
- Use the USB-JST cable from the kit to get a USB A connector
![USB to JST cable](../../assets/hardware/px4_vision_devkit/usb_jst_cable.jpg)
@@ -323,7 +312,6 @@ To login to the companion computer:
The Ubuntu login screen should then appear on the monitor.
1. Login to the _UP Core_ using the credentials:
- **Username:** px4vision
- **Password:** px4vision
@@ -375,7 +363,7 @@ To integrate a different planner, this needs to be disabled.
```
The ROS workspace is placed in `~/catkin_ws`.
For reference on developing in ROS and using the catkin workspace, see the [ROS catkin tutorials](http://wiki.ros.org/catkin/Tutorials).
For reference on developing in ROS and using the catkin workspace, see the [ROS catkin tutorials](https://wiki.ros.org/catkin/Tutorials).
### Developing PX4 Firmware
@@ -385,7 +373,6 @@ You can modify PX4 itself, and [install it as custom firmware](../config/firmwar
- Select the _PX4 Vision DevKit_ airframe after loading new firmware:
![Airframe Selection - PX4 Vision DevKit](../../assets/hardware/px4_vision_devkit/qgc_airframe_px4_vision_devkit_platform.jpg)
## PX4 Vision Carrier Board Pinouts
Information for the PX4 Vision 1.15 can be found at [https://docs.holybro.com](https://docs.holybro.com/drone-development-kit/px4-vision-dev-kit-v1.5).