mirror of
https://gitee.com/mirrors_PX4/PX4-Autopilot.git
synced 2026-10-03 14:08:52 +08:00
[Docs] Fix links and tidy config (#25184)
* Fix links and tidy config * Add updated lock files
This commit is contained in:
@@ -35,7 +35,7 @@ The main hardware documentation is here: https://wiki.bitcraze.io/projects:crazy
|
||||
## Where to Buy
|
||||
|
||||
- [Crazyflie 2.0](https://store.bitcraze.io/collections/kits/products/crazyflie-2-0).
|
||||
- [Crazyradio PA 2.4 GHz USB dongle](https://store.bitcraze.io/collections/kits/products/crazyradio-pa): used for wireless communication between _QGroundControl_ and Crazyflie 2.0.
|
||||
- [Crazyradio PA 2.4 GHz USB dongle](https://store.bitcraze.io/products/crazyradio-pa): used for wireless communication between _QGroundControl_ and Crazyflie 2.0.
|
||||
- [Breakout deck](https://store.bitcraze.io/collections/decks/products/breakout-deck): breakout expansion board for connecting new peripherals.
|
||||
- [Flow deck](https://store.bitcraze.io/collections/decks/products/flow-deck): contains an optical flow sensor to measure movements of the ground and a distance sensor to measure the distance to the ground.
|
||||
This will be useful for precise altitude and position control.
|
||||
@@ -194,7 +194,7 @@ python cfbridge.py
|
||||
|
||||
::: info
|
||||
_Cfbridge_ by default tries to initiate the radio link communication on channel 80 and with crazyflie address 0xE7E7E7E7E7.
|
||||
If you are using [multiple crazyflies and/or crazyradios](https://github.com/dennisss/cfbridge/blob/master/index.md#advanced-swarming) in the same room and want to use a different channel and/or address for each, first connect the crazyflie with QGroundControl via a USB cable and change the syslink parameters (channel, address) in QGroundControl.
|
||||
If you are using [multiple crazyflies and/or crazyradios](https://github.com/dennisss/cfbridge/blob/master/README.md#advanced-swarming) in the same room and want to use a different channel and/or address for each, first connect the crazyflie with QGroundControl via a USB cable and change the syslink parameters (channel, address) in QGroundControl.
|
||||
Next, launch the cfbridge by giving the same channel and address as the first and second arguments respectively, e.g: `python cfbridge.py 90 0x0202020202`
|
||||
:::
|
||||
|
||||
|
||||
@@ -40,7 +40,7 @@ The vehicle can be purchased here: [Crazyflie 2.1](https://store.bitcraze.io/pro
|
||||
|
||||
Useful peripheral hardware includes:
|
||||
|
||||
- [Crazyradio PA 2.4 GHz USB dongle](https://store.bitcraze.io/collections/kits/products/crazyradio-pa): Wireless communication between _QGroundControl_ and Crazyflie 2.0
|
||||
- [Crazyradio PA 2.4 GHz USB dongle](https://store.bitcraze.io/products/crazyradio-pa): Wireless communication between _QGroundControl_ and Crazyflie 2.0
|
||||
- [Breakout deck](https://store.bitcraze.io/collections/decks/products/breakout-deck): Breakout expansion board for connecting new peripherals.
|
||||
- [Flow deck v2](https://store.bitcraze.io/collections/decks/products/flow-deck-v2): Optical flow sensor and a distance sensor for altitude and position control.
|
||||
- [Z-ranger deck v2](https://store.bitcraze.io/collections/decks/products/z-ranger-deck-v2): Distance sensor for altitude control (same sensor as the Flow deck).
|
||||
@@ -210,7 +210,7 @@ To connect Crazyflie 2.1 with crazyradio, **launch cfbridge** by following these
|
||||
|
||||
::: info
|
||||
_Cfbridge_ by default tries to initiate the radio link communication on channel 80 and with crazyflie address 0xE7E7E7E7E7.
|
||||
If you are using [multiple crazyflies and/or crazyradios](https://github.com/dennisss/cfbridge/blob/master/index.md#advanced-swarming) in the same room and want to use a different channel and/or address for each, first connect the crazyflie with QGroundControl via a USB cable and change the syslink parameters (channel, address) in QGroundControl.
|
||||
If you are using [multiple crazyflies and/or crazyradios](https://github.com/dennisss/cfbridge/blob/master/README.md#advanced-swarming) in the same room and want to use a different channel and/or address for each, first connect the crazyflie with QGroundControl via a USB cable and change the syslink parameters (channel, address) in QGroundControl.
|
||||
Next, launch the cfbridge by giving the same channel and address as the first and second arguments respectively, e.g: `python cfbridge.py 90 0x0202020202`
|
||||
:::
|
||||
|
||||
|
||||
@@ -12,19 +12,16 @@ You can find others on [px4.io](https://px4.io/ecosystem/commercial-systems/) an
|
||||
This section lists drone kits that are intended as platforms for further development.
|
||||
They may come either fully assembled or in parts.
|
||||
|
||||
- [ModalAI VOXL 2 Starling PX4 Development Drone](../complete_vehicles_mc/modalai_starling.md) - SLAM development drone supercharged by VOXL 2 and PX4.
|
||||
- [PX4 Vision DevKit](../complete_vehicles_mc/px4_vision_kit.md) - Multicopter used for PX4 computer vision development
|
||||
- ~[ModalAI VOXL 2 Starling PX4 Development Drone](../complete_vehicles_mc/modalai_starling.md)~ (Discontinued/superseded) - SLAM development drone supercharged by VOXL 2 and PX4.
|
||||
|
||||
## PX4 Preinstalled
|
||||
|
||||
This section lists vehicles that are sold fully assembled and ready to fly (RTF), with PX4 installed.
|
||||
|
||||
- [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
|
||||
|
||||
@@ -32,7 +29,6 @@ This section lists vehicles where you can update the software to run PX4.
|
||||
|
||||
- [Holybro Kopis 2](../complete_vehicles_mc/holybro_kopis2.md)
|
||||
- [Bitcraze Crazyflie 2.1](../complete_vehicles_mc/crazyflie21.md)
|
||||
- [BetaFPV Beta75X 2S Brushless Whoop](../complete_vehicles_mc/betafpv_beta75x.md) (discontinued)
|
||||
|
||||
## Custom PX4
|
||||
|
||||
@@ -40,8 +36,8 @@ This section contains consumer vehicles that run a _custom_ version of PX4 (supp
|
||||
These may or may not be updatable to run "vanilla" PX4.
|
||||
|
||||
- [Yuneec Typhoon H Plus](https://us.yuneec.com/typhoon-h-plus/)
|
||||
- [Yuneec Mantis Q](https://px4.io/portfolio/yuneec-mantis-q/)
|
||||
- [Yuneec H520](https://px4.io/portfolio/yuneec-h520-hexacopter/)
|
||||
- [Yuneec Mantis Q](https://px4.io/project/yuneec-mantis-q/)
|
||||
- [Yuneec H520](https://px4.io/project/yuneec-h520-hexacopter/)
|
||||
- [AeroSense Aerobo (AS-MC02-P)](https://px4.io/project/aerosense-aerobo/)
|
||||
|
||||
## See Also
|
||||
|
||||
@@ -381,7 +381,7 @@ The carrier board pinouts and other information are in the [downloads section](h
|
||||
## Other Development Resources
|
||||
|
||||
- [_UP Core_ Wiki](https://github.com/up-board/up-community/wiki/Ubuntu) - _Up Core_ companion computer technical information
|
||||
- [Occipital Developer Forum](https://structure.io/developers) - _Structure Core_ camera information
|
||||
- [Occipital Developer Forum](https://structure.io/developers/) - _Structure Core_ camera information
|
||||
- [Pixhawk 4 Overview](../flight_controller/pixhawk4.md)
|
||||
- [Pixhawk 6C Overview](../flight_controller/pixhawk6c.md)
|
||||
|
||||
|
||||
Reference in New Issue
Block a user