Configuring DroneCAN and Remote ID on Pixhawk/ArduPilot

Integrating DroneCAN and Remote ID into your UAV setup using the Pixhawk/ArduPilot platform offers an innovative solution to enhance data communication and comply with emerging regulations. This guide will delve into the specifics of DroneCAN, an advanced CAN bus protocol, and Remote ID, which fulfills legal requirements for UAV operation. We will cover technical specifications, wiring configurations, and ArduPilot parameters needed for seamless operation.

Understanding DroneCAN

DroneCAN (formerly known as UAVCAN v1) is a robust communication protocol designed to replace PWM signal transmission for various UAV peripherals. Operating over a Controller Area Network (CAN) bus, it supports a range of devices with a data rate of 1 Mbps. Unique node IDs for each component enhance system organization and communication reliability.

Why Choose DroneCAN?

Switching from PWM to DroneCAN offers numerous advantages:

• Bidirectional Communication: Unlike PWM, DroneCAN allows real-time feedback from devices, such as RPM data from Electronic Speed Controllers (ESCs) and temperature readings.
• Reduced Wiring Complexity: By utilizing a daisy-chain configuration, multiple devices can be connected with minimal wiring effort.
• Error Detection: The protocol comes with built-in error-detection mechanisms, ensuring data integrity across communication lines.

Supported Peripherals

DroneCAN is compatible with a variety of UAV peripherals, including:

• Electronic Speed Controllers (ESCs) with bidirectional feedback, eliminating the need for separate current sensors
• Here3 and Here4 GPS modules
• Airspeed sensors
• Power modules for monitoring battery performance
• Servo outputs for controlling mechanical systems

Wiring and Connection

To correctly set up a DroneCAN network, specific wiring requirements must be followed:

• Cabling: Use twisted pair cables specifically designed for CAN bus communication to reduce electromagnetic interference.
• Termination Resistors: Place 120-ohm termination resistors at both physical ends of the CAN bus to optimize signal integrity and prevent data loss.

ArduPilot Configuration

The following parameters must be set in ArduPilot to enable and configure DroneCAN functionality:

Node ID assignment for each connected device can be handled automatically by ArduPilot or manually using the Mission Planner’s CAN tool. This feature ensures that each device on the bus has a distinct identifier, allowing for efficient communication and management.

Testing Connectivity

Once the initial setup is completed, testing the connectivity of the DroneCAN devices is crucial. Here’s how to check:

1. Connect the Pixhawk to Mission Planner.
2. Go to the Data screen and select the DroneCAN tab.
3. Make sure all devices are listed under the connected nodes.

Understanding Remote ID

As of September 2023, compliance with Remote ID regulations is mandatory for UAV operations in the USA (with similar regulations under EASA in the EU). Remote ID enhances safety and accountability by broadcasting the identification of a UAV and its operator location during flight.

Remote ID Overview

ArduPilot versions 4.2 and higher provide integrated support for Remote ID through the OpenDroneID framework. This functionality can be activated via a serial connection or over a DroneCAN node, making it a versatile option for various hardware configurations.

Connection Options

For setting up Remote ID, users can choose between two main connection types:

• UART Serial: Use a dedicated SERIAL port on the Pixhawk to connect Remote ID hardware.
• DroneCAN: Leverage the CAN bus to connect your Remote ID module, enhancing the overall system integration.

Broadcasting Features

Remote ID systems typically broadcast data using Bluetooth 5 Long Range and WiFi beacons simultaneously. This dual-mode broadcasting ensures that the UAV’s information is accessible by a wide range of devices, enhancing situational awareness for operators and authorities alike.

Supported Remote ID Hardware

Several hardware platforms are compatible with the Remote ID functionality in ArduPilot:

• Cube ID / Cube ID_CAN
• Holybro Remote ID
• mRo RemoteID
• ESP32-S3/C3 with ArduRemoteID firmware
• BlueMark DroneBeacon

ArduRemoteID Firmware

The ArduRemoteID firmware is an open-source implementation for the ESP32 platform. It features AES-GCM 256-bit security encryption, which guarantees the confidentiality and integrity of transmitted data. The firmware can be configured to lock user keys, providing an additional layer of security against tampering.

Configuration in Mission Planner

The configuration for Remote ID can be managed through the Mission Planner software as follows:

1. Open Mission Planner and connect to your UAV.
2. Navigate to the DATA screen.
3. Select the Drone ID tab.
4. Set the UAS ID and the operator’s location details as required by regulations.

Serial Parameters for Remote ID

If using a serial connection for Remote ID, specific parameters need to be defined within ArduPilot:

Conclusion

This guide provides a comprehensive overview of configuring DroneCAN and Remote ID for the Pixhawk/ArduPilot platform. By following the specified wiring, configuration steps, and leveraging the benefits of both protocols, you can enhance your UAV’s operational performance and regulatory compliance. Whether you’re working on academic research or practical UAV applications, the integration of these technologies offers a pathway to sophisticated and reliable drone development.

Frequently Asked Questions

1. What is DroneCAN and why is it preferred over PWM?

DroneCAN is a CAN bus protocol that allows for bidirectional communication between devices in a UAV setup, providing real-time data feedback and reducing wiring complexity compared to traditional PWM.

2. How do I wire my UAV for DroneCAN?

Utilize twisted pair cables for your CAN bus connections and install 120-ohm termination resistors at each physical end of the bus for optimal signal integrity.

3. What are the benefits of integrating Remote ID into my UAV?

Integrating Remote ID into your UAV enhances safety and compliance with regulations by broadcasting identification information, promoting accountability during flight operations.

4. How can I check if my DroneCAN devices are communicating properly?

Connect your Pixhawk to Mission Planner, navigate to the DroneCAN tab in the Data screen, and verify that all connected devices are listed and functioning correctly.

5. Can I change the UAS ID in the Remote ID configuration?

Yes, you can adjust the UAS ID in the Drone ID tab of the Mission Planner under the DATA screen as needed to comply with regulations.

For further information, refer to the official ArduPilot documentation and explore the GitHub repository for additional resources and community support.

Sources & References

• ArduPilot: Remote ID Documentation
• GitHub: ArduRemoteID Firmware
• DroneCAN Protocol Specification
• ArduPilot: DroneCAN Setup
• OpenDroneID on GitHub

DroneCAN Parameter Quick Reference

DroneCAN is the CAN bus-based protocol used by ArduPilot for peripherals such as ESCs, Here3/Here4 GPS units, airspeed sensors, power modules, and servos. A typical DroneCAN bus runs at 1 Mbps, uses unique node IDs for each device, and should be wired as a twisted pair with 120-ohm termination resistors at each end of the bus.

In Mission Planner, configure these values through the full parameter editor or the CAN configuration tool. After enabling CAN_P1_DRIVER and setting CAN_D1_PROTOCOL to DroneCAN, connect the DroneCAN device chain, confirm proper 120-ohm termination at both ends, and verify that each device appears with a unique node ID. For DroneCAN GPS setups such as Here3 or Here4, set GPS_TYPE and, if used, GPS_TYPE2 for the connected rover GPS modules.

Remote ID Module Comparison

ArduPilot 4.2 and newer supports the OpenDroneID standard for Remote ID. Remote ID hardware can connect through a serial UART or DroneCAN interface, and supported modules broadcast using Bluetooth 5.x and WiFi Beacon simultaneously. Configuration is handled in Mission Planner under DATA and then the Drone ID tab.