> For the complete documentation index, see [llms.txt](https://aedrox.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://aedrox.gitbook.io/docs/flight-controller/interactive-blocks/ardupilot/osd.md).

# OSD

### ANALOG OSD 

<figure><img src="/files/IEBzUvBsxav86LQFUzr7" alt=""><figcaption></figcaption></figure>

To enable the OSD overlay, set parameter: `OSD_TYPE` to 1, reboot and reload parameters. This exposes the whole OSD parameter group.

{% hint style="info" %}
CONFIG > FULL PARAMETER LIST > OSD\_TYPE : 1
{% endhint %}

***

### DIGITAL OSD   (HD)

#### Configuration[¶](https://ardupilot.org/copter/docs/common-msp-osd-overview-4.2.html#id1)

To enable this, set the following parameters :

* **OSD\_TYPE = 3** if no integrated OSD is being used, or = 1 if an integrated OSD is present and the user wishes to have both OSDs.
* **SERIAL2\_PROTOCOL = 32** (MSP)
* **SERIAL2\_BAUD = 115**
* **MSP\_OPTIONS bit 0 = 0** (Do not EnableTelemetryMode) if the Air Unit is to be connected by both RX and TX input to the AutoPilot Serial port TX/RX. Set bit 0 = 1 (EnableTelemetryMode) if a standalone OSD unit connected only via a single wire from its RX input to the Serial ports’ TX. This is known as “push” mode.

{% hint style="info" %}
Mission Planners’ OSD setup screen supports HD OSD configuration. To enable it check **“HD Layout”** in Editor Options at the top right of the OSD screen you want to change.
{% endhint %}

<figure><img src="/files/KwyR4JecTYRDbgw7y3XY" alt=""><figcaption></figcaption></figure>

***

### OSD Layout

{% hint style="info" %}
CONFIG > ONBOARD OSD
{% endhint %}

The first tab define the global settings, other tabs allow to create different OSD layouts. \
To set a RC channel for screen switching, use parameter `OSD_CHAN`.

<figure><img src="/files/ZbACVzvrbtvCz9ndG1NJ" 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://aedrox.gitbook.io/docs/flight-controller/interactive-blocks/ardupilot/osd.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.