> 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/ms4525do-and-ms5525dso-i2c-airspeed-sensor.md).

# MS4525DO & MS5525DSO I2C Airspeed Sensor

## Ardupilot quick start guide

{% hint style="info" %}
Airspeed sensors are best paired with fixed-wing type airframe
{% endhint %}

In MissionPlanner, set *ARSPD\_TYPE* to *1* for MS4525 or *4* for MS5525. *Write Parameters* and power cycle the flight controller. 

Once configured, you should see airspeed data on the main UI or the status list:

![](https://2367252986-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLIgtGDAvVGkCKGOJb1bR%2Fuploads%2FjOrzEImSEgpSPOASvECD%2Fimage.png?alt=media\&token=7bacc974-146e-43f8-ad23-2a984a628b8e)

{% embed url="<https://ardupilot.org/plane/docs/calibrating-an-airspeed-sensor.html#calibrating-an-airspeed-sensor>" %}
Calibration guide
{% endembed %}

{% embed url="<https://ardupilot.org/copter/docs/common-airspeed-sensor.html>" %}
Ardupilot airspeed wiki
{% endembed %}

## PX4 quick start guide

In QGC, set *SENS\_EN\_MS4525DO* or *SENS\_EN\_MS5525DS* to enable. *Reboot Vehicle* or power cycle the flight controller.

<figure><img src="https://2367252986-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLIgtGDAvVGkCKGOJb1bR%2Fuploads%2F9xAq4iejv2T5H8po3pbp%2Fimage.png?alt=media&amp;token=5fa66547-95f9-4c6a-bc45-d236063c7c6d" alt=""><figcaption></figcaption></figure>

Once set, you should see the airspeed reading on the main interface:

<figure><img src="https://2367252986-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLIgtGDAvVGkCKGOJb1bR%2Fuploads%2FpQEAv20cfGjFtzALtEGf%2Fimage.png?alt=media&amp;token=ff26adb5-23d3-4e32-affd-19a1727a895a" alt=""><figcaption></figcaption></figure>

Make sure to calibrate the airspeed sensor for accurate reading.

<figure><img src="https://2367252986-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLIgtGDAvVGkCKGOJb1bR%2Fuploads%2Ft6PM1F4KUO6dLwwPUxcY%2Fimage.png?alt=media&amp;token=e36e1b14-3514-4a75-8908-13e13fc879a6" alt=""><figcaption></figcaption></figure>

{% embed url="<https://docs.px4.io/main/en/sensor/airspeed.html>" %}
PX4 airspeed sensor guide
{% endembed %}


---

# 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/ms4525do-and-ms5525dso-i2c-airspeed-sensor.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.