docs(cubepilot): use CubePilot name and drop connector/standards note (#29828)

- Rename remaining Hex/HEX/ProfiCNC references to CubePilot, including
  page file names (old pages redirect).
- Use the CubePilot spelling consistently.
- Remove the note on the Cube Black page advising against it for
  standards and patent reasons.

Assisted-by: Claude:claude-opus-5-5
This commit is contained in:
Julian Oes authored and GitHub committed 2026-11-19 12:51:01 +13:00
1 parent 35223a381e
commit caf8944d5f
19 files changed
+133 -133

No files matched your search

+2 -2
View File
@@ -808,7 +808,7 @@
},
{
"type": "UrlToLocalSite",
"fileRelativeToRoot": "en\\gps_compass\\rtk_gps_hex_hereplus.md",
"fileRelativeToRoot": "en\\gps_compass\\rtk_gps_cubepilot_hereplus.md",
"link": {
"url": "https://docs.px4.io/v1.11/en/gps_compass/rtk_gps_hex_hereplus.html",
"text": "PX4v1.11 docs"
@@ -1598,7 +1598,7 @@
},
{
"type": "UrlToLocalSite",
"fileRelativeToRoot": "en\\gps_compass\\rtk_gps_hex_hereplus.md",
"fileRelativeToRoot": "en\\gps_compass\\rtk_gps_cubepilot_hereplus.md",
"link": {
"url": "https://docs.px4.io/v1.11/en/gps_compass/rtk_gps_hex_hereplus",
"text": "PX4v1.11 docs"
+3 -3
View File
@@ -158,7 +158,7 @@
- [Wiring Quickstart](assembly/quick_start_pixhawk4.md)
- [mRo Pixracer (FMUv4)](flight_controller/pixracer.md)
- [Wiring Quickstart](assembly/quick_start_pixracer.md)
- [Hex Cube Black (FMUv3)](flight_controller/pixhawk-2.md)
- [Cube Black (FMUv3)](flight_controller/pixhawk-2.md)
- [mRo Pixhawk (FMUv3)](flight_controller/mro_pixhawk.md)
- [mRo (3DR) Pixhawk Wiring Quickstart](assembly/quick_start_pixhawk.md)
- [Manufacturer-Supported Autopilots](flight_controller/autopilot_manufacturer_supported.md)
@@ -274,7 +274,7 @@
- [CUAV NEO 3X GPS (CAN)](gps_compass/gps_cuav_neo_3x.md)
- [Holybro DroneCAN M8N GPS (CAN)](dronecan/holybro_m8n_gps.md)
- [LOCOSYS Hawk A1 GNSS](gps_compass/gps_locosys_hawk_a1.md)
- [✘ Hex Here2](gps_compass/gps_hex_here2.md)
- [✘ CubePilot Here2](gps_compass/gps_cubepilot_here2.md)
- [Holybro M8N & M9N GPS](gps_compass/gps_holybro_m8n_m9n.md)
- [Sky-Drones SmartAP GPS](gps_compass/gps_smartap.md)
- [RTK GNSS](gps_compass/rtk_gps.md)
@@ -302,7 +302,7 @@
- [Septentrio AsteRx-m3 Pro](gps_compass/septentrio_asterx-rib.md)
- [Septentrio mosaic-go](gps_compass/septentrio_mosaic-go.md)
- [Trimble MB-Two](gps_compass/rtk_gps_trimble_mb_two.md)
- [✘ CubePilot Here+](gps_compass/rtk_gps_hex_hereplus.md)
- [✘ CubePilot Here+](gps_compass/rtk_gps_cubepilot_hereplus.md)
- [INS (Inertial Navigation/GNSS)](sensor/inertial_navigation_systems.md)
- [InertialLabs](sensor/inertiallabs.md)
- [MicroStrain](sensor/microstrain.md)
+3 -3
View File
@@ -66,11 +66,11 @@ Customized screws are supposed to be M2.5 with thread length inside Cube in rang
## GPS + Compass + Safety Switch + LED
The recommended GPS modules are the _Here_ and [Here+](../gps_compass/rtk_gps_hex_hereplus.md), both of which incorporate a GPS module, Compass, Safety Switch and [LEDs](../getting_started/led_meanings.md).
The recommended GPS modules are the _Here_ and [Here+](../gps_compass/rtk_gps_cubepilot_hereplus.md), both of which incorporate a GPS module, Compass, Safety Switch and [LEDs](../getting_started/led_meanings.md).
The difference between the modules is that _Here+_ supports centimeter level positioning via [RTK](../gps_compass/rtk_gps.md). Otherwise they are used/connected in the same way.
:::warning
The [Here+](../gps_compass/rtk_gps_hex_hereplus.md) has been superseded by the [Here3](https://www.cubepilot.org/#/here/here3) a [DroneCAN](../dronecan/index.md) RTK-GNSS that incorporate a compass and [LEDs](../getting_started/led_meanings.md) (but no safety switch).
The [Here+](../gps_compass/rtk_gps_cubepilot_hereplus.md) has been superseded by the [Here3](https://www.cubepilot.org/#/here/here3) a [DroneCAN](../dronecan/index.md) RTK-GNSS that incorporate a compass and [LEDs](../getting_started/led_meanings.md) (but no safety switch).
See [DroneCAN](../dronecan/index.md) for _Here3_ wiring and PX4 configuration information.
:::
@@ -129,7 +129,7 @@ Spektrum DSM, DSM2, and DSM-X Satellite RC receivers connect to the **SPKT/DSM**
The Cube cannot directly connect to PPM or PWM receivers that have an _individual wire for each channel_.
PWM receivers must therefore connect to the **RCIN** port _via_ a PPM encoder module,
which may be purchased from hex.aero or proficnc.com.
which may be purchased from [CubePilot](https://www.cubepilot.org/).
## Power
@@ -21,7 +21,7 @@ The boards in this category are:
- [Holybro Pix32 v6](../flight_controller/holybro_pix32_v6.md) (FMUv6C)
- [Holybro Pixhawk 5X](../flight_controller/pixhawk5x.md) (FMUv5X)
- [mRo Pixracer](../flight_controller/pixracer.md) (FMUv4)
- [Hex Cube Black](../flight_controller/pixhawk-2.md) (FMUv3)
- [CubePilot Cube Black](../flight_controller/pixhawk-2.md) (FMUv3)
- [mRo Pixhawk](../flight_controller/mro_pixhawk.md) (FMUv3)
## Discontinued
+3 -5
View File
@@ -1,4 +1,4 @@
# Hex Cube Black Flight Controller
# CubePilot Cube Black Flight Controller
::: warning
PX4 does not manufacture this (or any) autopilot.
@@ -6,12 +6,10 @@ Contact the [manufacturer](https://cubepilot.org/#/home) for hardware support or
:::
::: tip
The [Cube Orange](cubepilot_cube_orange.md) is the successor to this product.
We recommend however to consider products built on industry standards, such as the [Pixhawk Standards](autopilot_pixhawk_standard.md).
This flight controller is not following the standard and uses a patented connector.
The [CubePilot Cube Orange](cubepilot_cube_orange.md) and [CubePilot Cube Orange+](cubepilot_cube_orangeplus.md) are successors to this product.
:::
The [Hex Cube Black](https://docs.cubepilot.org/autopilot/the-cube) flight controller (previously known as Pixhawk 2.1) is a flexible autopilot intended primarily for manufacturers of commercial systems.
The [CubePilot Cube Black](https://docs.cubepilot.org/autopilot/the-cube) flight controller (previously known as Pixhawk 2.1) is a flexible autopilot intended primarily for manufacturers of commercial systems.
It is based on the [Pixhawk-project](https://pixhawk.org/) **FMUv3** open hardware design and runs PX4 on the [NuttX](https://nuttx.apache.org/) OS.
![Cube Black](../../assets/flight_controller/cube/cube_black_hero.png)
+1 -1
View File
@@ -72,7 +72,7 @@ PX4 _developers_ need to know the FMU version of their board, as this is require
At very high level, the main differences are:
- **FMUv2:** Single board with STM32427VI processor (Pixhawk 1 (discontinued), Holybro pix32 (discontinued), Pixfalcon (discontinued), Drotek DroPix (discontinued))
- **FMUv3:** Identical to FMUv2, but usable flash doubled to 2MB ([Hex Cube Black](../flight_controller/pixhawk-2.md),[CUAV Pixhack v3](../flight_controller/pixhack_v3.md),[mRo Pixhawk](../flight_controller/mro_pixhawk.md), [Pixhawk Mini (Discontinued)](../flight_controller/pixhawk_mini.md))
- **FMUv3:** Identical to FMUv2, but usable flash doubled to 2MB ([CubePilot Cube Black](../flight_controller/pixhawk-2.md),[CUAV Pixhack v3](../flight_controller/pixhack_v3.md),[mRo Pixhawk](../flight_controller/mro_pixhawk.md), [Pixhawk Mini (Discontinued)](../flight_controller/pixhawk_mini.md))
- **FMUv4:** Increased RAM. Faster CPU. More serial ports. No IO processor ([Pixracer](../flight_controller/pixracer.md))
- **FMUv4-PRO:** Slightly increased RAM. More serial ports. IO processor ([Pixhawk 3 Pro](../flight_controller/pixhawk3_pro.md))
- **FMUv5:** New processor (F7).
@@ -0,0 +1,88 @@
# CubePilot Here2 GPS (Discontinued)
::: warning
This has been superseded by the [Cube Here 3](https://cubepilot.org/#/here/here3)
:::
The _Here2 GPS receiver_ is an update to the Here GPS module from CubePilot.
Main features include:
- Concurrent reception of up to 3 GNSS (GPS, Galileo, GLOSNASS, BeiDou)
- Industry Leading -167 dBm navigation sensitivity
- Security and integrity protection
- Supports all satellite augmentation systems
- Advanced jamming and spoofing detection
<img src="../../assets/hardware/gps/here2_gps_module.jpg" />
## Where to Buy
- [Resellers](https://cubepilot.org/#/reseller/list)
## Configuration
Setup and use on PX4 is largely plug and play.
::: info
- If the GPS is _not detected_ then [update the Here2 firmware](https://docs.cubepilot.org/here-2/updating-here-2-firmware).
- If the GPS is detected but does not work, attempt the process outlined in [allocating node uavcan ID](https://docs.cubepilot.org/here-2/here-2-can-mode-instruction).
:::
## Wiring and Connections
The Here2 GPS comes with an 8 pin connector that can be inserted directly into the Pixhawk 2 `GPS` UART port.
The Pixhawk 3 Pro and Pixracer have a 6 pin GPS port connector.
For these controllers you can modify the GPS cable (as shown below) to remove pin 6 and 7.
<img src="../../assets/hardware/gps/rtk_here_plug_gps_to_6pin_connector.jpg" width="500px" />
Pin 6 and 7 are for the safety button - these can be attached as well if needed.
### Pinout
The Here2 GPS pinout is provided below. This can be used to help modify the connector for other autopilot boards.
| pin | Here2 GPS | pin | Pixhawk 3 Pro GPS |
| --- | ---------- | --- | ----------------- |
| 1 | VCC_5V | 1 | VCC |
| 2 | GPS_RX | 2 | GPS_TX |
| 3 | GPS_TX | 3 | GPS_RX |
| 4 | SCL | 4 | SCL |
| 5 | SDA | 5 | SDA |
| 6 | BUTTON | - | - |
| 7 | BUTTON_LED | - | - |
| 8 | GND | 6 | GND |
## Specification
- **Processor:** STM32F302
- **Sensor**
- **Compass, Gyro, Accelerometer:** ICM20948
- **Barometer:** MS5611
- **Receiver Type:** 72-channel u-blox M8N engine, GPS/QZSS L2 C/A, GLONASS L10F, BeiDou B11, Galileo E1B/C, SBAS L1 C/A: WAAS, EGNOS, MSAS, GAGAN
- **Navigation Update Rate:** Max: 10 Hz
- **Positionaing Accuracy:** 3D Fix
- **Time to first fix:**
- **Cold start:** 26s
- **Aided start:** 2s
- **Reacquisition:** 1s
- **Sensitivity:**
- **Tracking & Navigation:** -167 dBm
- **Hot start:** -148 dBm
- **Cold start:** -157 dBm
- **Assisted GNSS**
- AssistNow GNSS Online
- AssistNow GNSS Offline (up to 35 days)
- AssistNow Autonomous (up to 6 days)
- OMA SUPL& 3GPP compliant
- **Oscillator:** TCXO (NEO-8MN/Q)
- **RTC crystal:** Build in
- **ROM:** Flash (NEO-8MN)
- **Available Antennas:** Active Antenna & Passive Antenna
- **Signal Integrity:** Signature feature with SHA 256
- **Protocols & Interfaces:**
- **UART/I2C/CAN:** JST_GH Main interface, Switch internally.
- **STM32 Main Programming Interface:** JST_SUR
+1 -88
View File
@@ -1,88 +1 @@
# HEX/ProfiCNC Here2 GPS (Discontinued)
::: warning
This has been superseded by the [Cube Here 3](https://cubepilot.org/#/here/here3)
:::
The _Here2 GPS receiver_ is an update to the Here GPS module from HEX.
Main features include:
- Concurrent reception of up to 3 GNSS (GPS, Galileo, GLOSNASS, BeiDou)
- Industry Leading -167 dBm navigation sensitivity
- Security and integrity protection
- Supports all satellite augmentation systems
- Advanced jamming and spoofing detection
<img src="../../assets/hardware/gps/here2_gps_module.jpg" />
## Where to Buy
- [Resellers](https://cubepilot.org/#/reseller/list)
## Configuration
Setup and use on PX4 is largely plug and play.
::: info
- If the GPS is _not detected_ then [update the Here2 firmware](https://docs.cubepilot.org/here-2/updating-here-2-firmware).
- If the GPS is detected but does not work, attempt the process outlined in [allocating node uavcan ID](https://docs.cubepilot.org/here-2/here-2-can-mode-instruction).
:::
## Wiring and Connections
The Here2 GPS comes with an 8 pin connector that can be inserted directly into the Pixhawk 2 `GPS` UART port.
The Pixhawk 3 Pro and Pixracer have a 6 pin GPS port connector.
For these controllers you can modify the GPS cable (as shown below) to remove pin 6 and 7.
<img src="../../assets/hardware/gps/rtk_here_plug_gps_to_6pin_connector.jpg" width="500px" />
Pin 6 and 7 are for the safety button - these can be attached as well if needed.
### Pinout
The Here2 GPS pinout is provided below. This can be used to help modify the connector for other autopilot boards.
| pin | Here2 GPS | pin | Pixhawk 3 Pro GPS |
| --- | ---------- | --- | ----------------- |
| 1 | VCC_5V | 1 | VCC |
| 2 | GPS_RX | 2 | GPS_TX |
| 3 | GPS_TX | 3 | GPS_RX |
| 4 | SCL | 4 | SCL |
| 5 | SDA | 5 | SDA |
| 6 | BUTTON | - | - |
| 7 | BUTTON_LED | - | - |
| 8 | GND | 6 | GND |
## Specification
- **Processor:** STM32F302
- **Sensor**
- **Compass, Gyro, Accelerometer:** ICM20948
- **Barometer:** MS5611
- **Receiver Type:** 72-channel u-blox M8N engine, GPS/QZSS L2 C/A, GLONASS L10F, BeiDou B11, Galileo E1B/C, SBAS L1 C/A: WAAS, EGNOS, MSAS, GAGAN
- **Navigation Update Rate:** Max: 10 Hz
- **Positionaing Accuracy:** 3D Fix
- **Time to first fix:**
- **Cold start:** 26s
- **Aided start:** 2s
- **Reacquisition:** 1s
- **Sensitivity:**
- **Tracking & Navigation:** -167 dBm
- **Hot start:** -148 dBm
- **Cold start:** -157 dBm
- **Assisted GNSS**
- AssistNow GNSS Online
- AssistNow GNSS Offline (up to 35 days)
- AssistNow Autonomous (up to 6 days)
- OMA SUPL& 3GPP compliant
- **Oscillator:** TCXO (NEO-8MN/Q)
- **RTC crystal:** Build in
- **ROM:** Flash (NEO-8MN)
- **Available Antennas:** Active Antenna & Passive Antenna
- **Signal Integrity:** Signature feature with SHA 256
- **Protocols & Interfaces:**
- **UART/I2C/CAN:** JST_GH Main interface, Switch internally.
- **STM32 Main Programming Interface:** JST_SUR
<Redirect to="../gps_compass/gps_cubepilot_here2" />
+1 -1
View File
@@ -62,7 +62,7 @@ These have been tested by the PX4 dev team, or which are popular within the PX4
[RccnLabGNSS250]: https://docs.raccoonlab.co/guide/gps_mag_baro/gnss_v250.html
[LOCOSYS Hawk A1]: ../gps_compass/gps_locosys_hawk_a1.md
[Hb Micro M8N]: https://holybro.com/products/micro-m8n-gps
[CubePilot Here2]: ../gps_compass/gps_hex_here2.md
[CubePilot Here2]: ../gps_compass/gps_cubepilot_here2.md
Notes:
+2 -2
View File
@@ -32,7 +32,7 @@ It also highlights devices that connect via the CAN bus, and those which support
| [CUAV C-RTK2](../gps_compass/rtk_gps_cuav_c-rtk2.md) | F9P | ✓ | | [Dual F9P] | |
| [CUAV C-RTK 9Ps GPS](../gps_compass/rtk_gps_cuav_c-rtk-9ps.md) | F9P | RM3100 | | [Dual F9P] | |
| [CUAV C-RTK2 PPK/RTK GNSS](../gps_compass/rtk_gps_cuav_c-rtk.md) | F9P | RM3100 | | | ✓ |
| [CubePilot Here+ RTK GPS](../gps_compass/rtk_gps_hex_hereplus.md) | M8P | HMC5983 | | | |
| [CubePilot Here+ RTK GPS](../gps_compass/rtk_gps_cubepilot_hereplus.md) | M8P | HMC5983 | | | |
| [CubePilot Here3 CAN GNSS GPS (M8N)](https://www.cubepilot.org/#/here/here3) | M8P | ICM20948 | ✓ | | |
| [Drotek SIRIUS RTK GNSS ROVER (F9P)](https://store-drotek.com/911-sirius-rtk-gnss-rover-f9p.html) | F9P | RM3100 | | [Dual F9P] | |
| [DATAGNSS NANO HRTK Receiver](../gps_compass/rtk_gps_datagnss_nano_hrtk.md) | [D10P] | IST8310 | | ✘ | |
@@ -81,7 +81,7 @@ Notes:
- Where possible and relevant the part name is used (i.e. ✓ in the GPS column indicates that a GPS module is present but the part is not known).
- Some RTK modules can only be used in a particular role (base or rover), while others can be used interchangeably.
- The list may omit some discontinued hardware that is still supported.
For example [CubePilot Here+ RTK GPS](../gps_compass/rtk_gps_hex_hereplus.md) is discontinued and may be removed from the list in a future release.
For example [CubePilot Here+ RTK GPS](../gps_compass/rtk_gps_cubepilot_hereplus.md) is discontinued and may be removed from the list in a future release.
Check earlier versions if a discontinued module is not mentioned here.
## Positioning Setup/Configuration
@@ -0,0 +1,13 @@
# CubePilot Here+ RTK GPS (Discontinued)
<Badge type="info" text="Discontinued" />
::: info
This GPS is no longer available for purchase but is still compatible with PX4.
Usage documentation can be found in [PX4v1.11 docs](https://docs.px4.io/v1.11/en/gps_compass/rtk_gps_hex_hereplus)
:::
The **Here+ RTK GPS receiver** is a small, light and energy efficient [RTK GPS module](../gps_compass/rtk_gps.md), based on the u-blox M8P. Using RTK, PX4 can get its position with centimetre-level accuracy, which is much more accurate than can be provided by a normal GPS.
<img src="../../assets/hardware/gps/rtk_here_plus.jpg" />
+1 -1
View File
@@ -42,7 +42,7 @@ For use as a base station, the module has a USB-C connector
### Pinout
The Freefly GPS pinout is provided below.
For some autopilots, like the [Hex Cube](../flight_controller/pixhawk-2.md) and [PixRacer](../flight_controller/pixracer.md), all that is needed is a 1-1 8-pin JST-GH cable.
For some autopilots, like the [CubePilot Cube](../flight_controller/pixhawk-2.md) and [PixRacer](../flight_controller/pixracer.md), all that is needed is a 1-1 8-pin JST-GH cable.
| Pin | Freefly GPS |
| --- | ----------- |
+1 -13
View File
@@ -1,13 +1 @@
# HEX/ProfiCNC Here+ RTK GPS (Discontinued)
<Badge type="info" text="Discontinued" />
::: info
This GPS is no longer available for purchase but is still compatible with PX4.
Usage documentation can be found in [PX4v1.11 docs](https://docs.px4.io/v1.11/en/gps_compass/rtk_gps_hex_hereplus)
:::
The **Here+ RTK GPS receiver** is a small, light and energy efficient [RTK GPS module](../gps_compass/rtk_gps.md), based on the u-blox M8P. Using RTK, PX4 can get its position with centimetre-level accuracy, which is much more accurate than can be provided by a normal GPS.
<img src="../../assets/hardware/gps/rtk_here_plus.jpg" />
<Redirect to="../gps_compass/rtk_gps_cubepilot_hereplus" />
@@ -26,8 +26,8 @@ Additional technical information can be found at [Holybro Technical Documentatio
The module comes with both GH 10-pin & 6-pin cables that are compatible with the GPS1 & GPS2 ports on flight controllers that use the [Pixhawk Connector Standard](https://github.com/pixhawk/Pixhawk-Standards/blob/master/DS-009%20Pixhawk%20Connector%20Standard.pdf), such as [Pixhawk 6x](../flight_controller/pixhawk6x.md) and [Pixhawk 6c](../flight_controller/pixhawk6c.md).
It can also be used with Cubepilot Flight Controller.
The 10Pin - 6Pin cable allows users to connect the UM982 to `GPS2` port on Cubepilot and Holybro Autopilots.
It can also be used with CubePilot Flight Controller.
The 10Pin - 6Pin cable allows users to connect the UM982 to `GPS2` port on CubePilot and Holybro Autopilots.
The module can be used with one antenna or both antennas.
If it is used with only one antenna, the right/primary antenna connector must be connected.
+1 -1
View File
@@ -14,7 +14,7 @@ FMU generations 1-3 were designed as open hardware, while FMU generations 4 and
- FMUv1: Development board \(STM32F407, 128 KB RAM, 1MB flash, [schematics](https://github.com/pixhawk/Hardware/tree/master/FMUv1)\) (no longer supported by PX4)
- FMUv2: Pixhawk \(STM32F427, 168 MHz, 192 KB RAM, 1MB flash, [schematics](https://github.com/pixhawk/Hardware/tree/master/FMUv2)\)
- FMUv3: Pixhawk variants with 2MB flash \(3DR Pixhawk 2 \(Solo\), Hex Pixhawk 2.1, Holybro Pixfalcon, 3DR Pixhawk Mini, STM32F427, 168 MHz, 256 KB RAM, 2 MB flash, [schematics](https://github.com/pixhawk/Hardware/tree/master/FMUv3_REV_D)\)
- FMUv3: Pixhawk variants with 2MB flash \(3DR Pixhawk 2 \(Solo\), CubePilot Pixhawk 2.1, Holybro Pixfalcon, 3DR Pixhawk Mini, STM32F427, 168 MHz, 256 KB RAM, 2 MB flash, [schematics](https://github.com/pixhawk/Hardware/tree/master/FMUv3_REV_D)\)
- FMUv4: Pixracer \(STM32F427, 168 MHz, 256 KB RAM, 2 MB flash, [pinout](https://docs.google.com/spreadsheets/d/1raRRouNsveQz8cj-EneWG6iW0dqGfRAifI91I2Sr5E0/edit#gid=1585075739)\)
- FMUv4 PRO: Drotek Pixhawk 3 PRO \(STM32F469, 180 MHz, 384 KB RAM, 2 MB flash, [pinout](https://docs.google.com/spreadsheets/d/1raRRouNsveQz8cj-EneWG6iW0dqGfRAifI91I2Sr5E0/edit#gid=1585075739)\)
- FMUv5: Holybro Pixhawk 4 \(STM32F765, 216 MHz, 512 KB RAM, 2 MB flash, [pinout](https://docs.google.com/spreadsheets/d/1-n0__BYDedQrc_2NHqBenG1DNepAgnHpSGglke-QQwY/edit#gid=912976165)\)
+2 -2
View File
@@ -104,10 +104,10 @@ For more information see [Fast-RTPS to uXRCE-DDS Migration Guidelines](../middle
### Hardware Support
- Cubepilot Cube Orange+ - [PX4-Autopilot#20304](https://github.com/PX4/PX4-Autopilot/pull/20304)
- CubePilot Cube Orange+ - [PX4-Autopilot#20304](https://github.com/PX4/PX4-Autopilot/pull/20304)
- Unicore GPS: Support for Holybro Unicore UM982 GPS - [PX4-Autopilot#21214](https://github.com/PX4/PX4-Autopilot/pull/21214))
- VOXL2 Improved support - [PX4-Autopilot#21426](https://github.com/PX4/PX4-Autopilot/pull/21426)
- Cubepilot Cube Black detection: Fixed Cube Black vs. Pixhawk 2 detection with CAN1 connected - [PX4-Autopilot#21342](https://github.com/PX4/PX4-Autopilot/pull/21342)
- CubePilot Cube Black detection: Fixed Cube Black vs. Pixhawk 2 detection with CAN1 connected - [PX4-Autopilot#21342](https://github.com/PX4/PX4-Autopilot/pull/21342)
### Common
+1 -1
View File
@@ -54,7 +54,7 @@ Please continue reading for [upgrade instructions](#upgrade-guide).
- **[Feature]** Add power module selector for Auterion power modules ([PX4-Autopilot#22073](https://github.com/PX4/PX4-Autopilot/pull/22073))
- **[Lights]** Add LP5562 RGBLED driver ([PX4-Autopilot#21649](https://github.com/PX4/PX4-Autopilot/pull/21649))
- **[Holybro]** Enable EKF2 on KakuteH7 / KakuteH7v2 / KakuteH7mini ([PX4-Autopilot#21961](https://github.com/PX4/PX4-Autopilot/pull/21961))
- **[Cubepilot]** Add support for 4. variant of Orange+ ([PX4-Autopilot#22039](https://github.com/PX4/PX4-Autopilot/pull/22039))
- **[CubePilot]** Add support for 4. variant of Orange+ ([PX4-Autopilot#22039](https://github.com/PX4/PX4-Autopilot/pull/22039))
- **[3DR]** Control Zero Classic Support Improvements ([PX4-Autopilot#22971](https://github.com/PX4/PX4-Autopilot/pull/22971))
### Common
+1 -1
View File
@@ -78,7 +78,7 @@ An all-in-one design that simplifies installation, with an onboard infrared LED
### PMW3901-Based Sensors
[PMW3901](../sensor/pmw3901.md) is an optical flow tracking sensor similar to what you would find in a computer mouse, but adapted to work between 80 mm and infinity.
It is used in a number of products, including some from: Bitcraze, Tindie, Hex, Thone and Alientek.
It is used in a number of products, including some from: Bitcraze, Tindie, CubePilot, Thone and Alientek.
### Other Cameras/Sensors
+6 -6
View File
@@ -2,7 +2,7 @@
PMW3901 is an [optical flow](../sensor/optical_flow.md) ASIC that computes the flow internally and provides a difference in pixels between each frame.
It uses a tracking sensor that is similar to what you would find in a computer mouse, but adapted to work between 80 mm and infinity.
The PMW3901 is used in several products, including some from Bitcraze, Tindie, Hex, Thone, and Alientek
The PMW3901 is used in several products, including some from Bitcraze, Tindie, CubePilot, Thone, and Alientek
![Bitcraze Flow Deck](../../assets/hardware/sensors/pmw3901/bitcraze-flow.jpg)
@@ -17,7 +17,7 @@ The board name links to board-specific sections that include wiring and purchase
| ----------- | --------------------------------------------------------------------------------- | --------- | ---- | ------------ | ---- | ----------- | --------- | -------------- |
| Bitcraze | [Flow breakout](#bitcraze-flow-breakout) | SPI | Y | Y | - | 3 - 5 | 21x20 | 1 |
| Tindie | [PMW3901 Optical Flow Sensor](#tindie-pmw3901-optical-flow-sensor) | SPI | Y | - | - | 3 - 5 | AxB | - |
| Hex | [HereFlow PMW3901 Optical Flow Sensor](#hex-hereflow-pmw3901-optical-flow-sensor) | CAN | Y | Y | Y | 3 - 5 | AxB | 4 |
| CubePilot | [HereFlow PMW3901 Optical Flow Sensor](#cubepilot-hereflow-pmw3901-optical-flow-sensor) | CAN | Y | Y | Y | 3 - 5 | AxB | 4 |
| Holybro | [Holybro PMW3901 Optical Flow Sensor](#holybro-pmw3901-optical-flow-sensor) | UART | Y | - | - | 3 - 5 | AxB | - |
| Thone | [ThoneFlow-3901U](#thone-thoneflow-3901u) | UART | Y | - | - | 3 - 5 | AxB | - |
| Alientek | [ATK-PMW3901](#alientek-atk-pmw3901) | SPI | Y | - | - | 3.3 - 4.2 | 27.5x16.5 | 1 |
@@ -57,7 +57,7 @@ You can use the notch to find the orientation of the other boards in the same wa
| &nbsp; | &nbsp; |
| ---------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
| Tindie<br>![PMW3901 Tindie Notch][tindie_notch] | Hex Hereflow<br>![PMW3901 Hereflow Notch][hereflow_notch] |
| Tindie<br>![PMW3901 Tindie Notch][tindie_notch] | CubePilot Hereflow<br>![PMW3901 Hereflow Notch][hereflow_notch] |
| Thone<br>![PMW3901 Thoneflow Notch][thoneflow_notch] | Alientek (also has an arrow indicating the front!)<br>![PMW3901 Alientek Notch][alientek_notch] |
[tindie_notch]: ../../assets/hardware/sensors/pmw3901/tindie_notch.jpg
@@ -148,9 +148,9 @@ A screenshot showing the I2C pins (SLA, SLC, GND, and VCC) is provided below.
[PX4 configuration](#px4-configuration) and [mounting/orientation](#mounting-orientation) instructions are provided above.
## Hex HereFlow PMW3901 Optical Flow Sensor
## CubePilot HereFlow PMW3901 Optical Flow Sensor
The Hex [HereFlow PMW3901 Optical Flow Sensor](https://docs.cubepilot.org/flow-senor/here-flow) is a tiny board containing the PMW3901 flow module, VL53L1X distance sensor, and an IMU (used to synchronize the flow data with the gyro data).
The CubePilot [HereFlow PMW3901 Optical Flow Sensor](https://docs.cubepilot.org/flow-senor/here-flow) is a tiny board containing the PMW3901 flow module, VL53L1X distance sensor, and an IMU (used to synchronize the flow data with the gyro data).
An onboard microcontroller samples the three sensors and publishes two DroneCAN messages containing all the information needed for the flow and distance sensor calculations.
@@ -164,7 +164,7 @@ As for the other optical flow boards, we recommend that you use an [external dis
The diagram below shows how to connect the sensor to the Pixhawk 4 CAN bus.
![Hex PH4 Pinout](../../assets/hardware/sensors/pmw3901/ph4-hex-optical-flow.png)
![CubePilot PH4 Pinout](../../assets/hardware/sensors/pmw3901/ph4-hex-optical-flow.png)
In addition to any other configuration, you will need to set the parameter [UAVCAN_ENABLE](../advanced_config/parameter_reference.md#UAVCAN_ENABLE) to either 2 or 3, depending on your system: