> For the complete documentation index, see [llms.txt](https://docs.holybro.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.holybro.com/peripherals/dlvr-airspeed-dronecan/overview.md).

# Overview

The Holybro DroneCAN Airspeed is an industrial-grade differential pressure measurement module designed for precision airspeed measurement in various UAVs, including planes, VTOLs, and other vehicles. Equipped with DLVR\_L10D digital Pressure Sensor and running ArduPilot AP-Periph Firmware, this module ensures accurate and reliable airspeed data across different flight conditions.

## Features

* **Wide Pressure Range**: Supports up to 2500 Pa and 226.8 km/h (141 mph) airspeed measurement.
* **High-Precision DLVR Sensor** : Based on ALLSENSORS® DLVR with CoBeam technology, providing high precision and low temperature drift.
* **High Accuracy:** Better than 1% accuracy across a wide temperature range, ensuring reliable and accurate readings in demanding application.
* **DroneCAN Protocol**: Compatible with both PX4 and ArduPilot platforms.
* **Aluminum Shell:** Durable and reliable construction.

## Specifications

* MCU: STM32G473CE, 170 MHz, 128KB RAM, 512KB Flash
* Sensor: DLVR\_L10D
* Pressure Range: 2500 Pa
* Burst Pressure: 75 kPa
* Airspeed Measurement: 0-226.8 km/h
* Accuracy: Error rate less than 1.0%
* Firmware: AP-Periph DroneCAN
* Communication Protocol: DroneCAN
* Compatible Flight Controllers: Any flight controller with a CAN interface running PX4 or Ardupilot firmware
* Working Voltage: 4.75\~5.25V
* Current Consumption: \~100mA
* Dimensions: 29 x 35.5 x 16.5 mm (module), 91.5 x 28 x 30 mm (Pitot tube)
* Weight: 38.3g (Includes Pitot tube and tubing)
* Operating Temperature: -20 to 85℃

## **Pinouts & Ports**

<figure><img src="https://2367252986-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLIgtGDAvVGkCKGOJb1bR%2Fuploads%2FEtMy7X3eIA6cA5Z49oiF%2FDLVR-Dimensions-02.jpg?alt=media&amp;token=f55504c5-262d-4072-8b71-9dd3601d22ef" alt=""><figcaption><p>CAN Port Pinout</p></figcaption></figure>

<figure><img src="https://2367252986-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLIgtGDAvVGkCKGOJb1bR%2Fuploads%2FUBE1EV4vri3RuZRiB9IK%2FDLVR-Dimensions-03.jpg?alt=media&amp;token=7fa1b2d9-9cad-46e0-a418-1e84e55b3f12" alt=""><figcaption><p>Sensor Port Definition</p></figcaption></figure>

### **CAN port**

| Pin    | Signal | Volt      |
| ------ | ------ | --------- |
| 1（Red) | VCC    | +5V Input |
| 2      | CAN\_H | +3.3V     |
| 3      | CAN\_L | +3.3V     |
| 4      | GND    | GND       |

### Dimensions

<figure><img src="https://2367252986-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLIgtGDAvVGkCKGOJb1bR%2Fuploads%2F3Y53UTfYz9tIwZeo3U11%2FDLVR-Dimensions-01.jpg?alt=media&amp;token=e01fdb72-19dd-4163-b9df-797ac9846605" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.holybro.com/peripherals/dlvr-airspeed-dronecan/overview.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.