CubePilot Here4 RTK GNSS (DroneCAN)
The CubePilot Here4 is a dual-band (L1/L5) RTK GNSS module that connects to the flight controller via DroneCAN. It integrates a u-blox NEO-F9P receiver, an RM3100 compass, a barometer, an IMU and RGB LEDs.
WARNING
CubePilot has issued safety service bulletins for the Here4, including a mandatory bootloader update before further flight (SB_0000010). Check the bulletins before flying (see Firmware).
Variants
- Here4 Base: RTK base station with an external antenna connector, for use with QGroundControl.
- Here4 Blue: Here4 with integrated Bluetooth Remote ID (CubeID).
Where to Buy
Hardware Specifications
From the CubePilot Here4 manual:
- GNSS receiver: u-blox NEO-F9P, dual-band (L1/L5)
- Constellations: GPS, GLONASS, Galileo, BeiDou, QZSS
- Processor: STM32H757, running CubePilot's AP_Periph based firmware
- Compass: RM3100
- IMU: ICM42688
- Barometer: MS5611
- Interface: DroneCAN, two CAN ports (only one supported by the current firmware, see Wiring)
- Working temperature: -40 °C to +85 °C
- Size: 16 x 68 mm
- Weight: 60 g (with cable)
Hardware Setup
Wiring
Connect the Here4 to the CAN1 or CAN2 port of the flight controller using the supplied 4-pin CAN cable. For more information, refer to the CAN Wiring instructions.
WARNING
The Here4 has two CAN ports, but the current firmware only supports one of them: the port whose cable has green, blue, white and grey wires. If the other port is used, the Here4 does not appear on the bus. uavcan status then reports TX frames and an equally growing number of HW errors, with no RX frames and no online nodes.
Mounting
Mount the module as far away from other electronics as possible, with its direction marker pointing towards the front of the vehicle.
PX4 Configuration
- Set UAVCAN_ENABLE to
2(Sensors Automatic Config), or3if you also use DroneCAN ESCs, and reboot. - The Here4 is assigned a node ID via dynamic node allocation, and its GNSS and compass are used without further configuration.
- To also use the Here4 barometer:
Enable UAVCAN_SUB_BARO in PX4.
Enable the barometer on the Here4 itself, where it is disabled by default. Set its
BARO_ENABLEparameter to1and save it to the node, either in the QGroundControl parameters of the Here4 component, or from the MAVLink Shell:shuavcan param set <node-id> BARO_ENABLE 1 uavcan param save <node-id>Then power cycle the Here4.
You can check that everything is detected with uavcan status. The Here4 should be listed under Online nodes with mode OPERAT, and the gnss, mag and (if enabled) baro sensors should each show a channel bound to its node ID.
DroneCAN configuration in PX4 is explained in more detail in DroneCAN > PX4 Configuration. For RTK setup see RTK GNSS.
Firmware
CubePilot publishes the Here4 firmware and release notes at GNSSPeriph-release.
PX4 can update the Here4 from the SD card, as described in DroneCAN > Firmware Update:
- Copy
Here4_FW.binfrom the release archive to the SD card. - Reboot with the Here4 connected. PX4 moves the file to
/fs/microsd/ufw/1043.bin(1043 is the Here4 board ID) and updates the Here4 if its firmware differs. During the updateuavcan statusshows the Here4 with modeSW_UPD, and thenOPERATagain once it has completed.
You can check the installed version with listener device_information: firmware_version shows the major and minor version followed by the git hash of the build in decimal (DroneCAN does not report the patch version).
If the Here4 stays in SW_UPD without completing, remove the file from /fs/microsd/ufw/ and update the Here4 with CubePilot's tools instead (see the bulletin below).
According to SB_0000010, a Here4 with the updated bootloader breathes blue at boot. If yours does not, follow the bulletin: update the firmware, then set the Here4 parameter FLASH_BOOTLOADER to 1 to update the bootloader.
See Also
- CubePilot Here4 Manual (docs.cubepilot.org)