> 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/power-module-and-pdb/power-module/using-analog-pm-with-pixhawk-5x-6x.md).

# Using Analog PM with Pixhawk 5X/6X

Pixhawk 5X/6X uses digital power module (such as PM02*D*, *D* stands for digital), if you would like to use it with an Analog Power Module, see below.

#### PX4

If you are have to use analog power module with Pixhawk 5X or 6X. With PX4 & QGC, you can use an [ADS1115 board](https://docs.px4.io/main/en/modules/modules_driver.html#ads1115) and wire it like this diagram and set the following parameters:

{% hint style="info" %}
These parameters are available in PX4 v1.14 with [Github PR](https://github.com/PX4/PX4-Autopilot/pull/21794), or you can build an FW with [these board config changes.](https://github.com/PX4/PX4-Autopilot/pull/21794/files)
{% endhint %}

* ADC\_ADS1115\_EN = 1 
* Save & Reboot
* BAT1\_A\_PER\_V = 36
* BAT1\_I\_CHANNEL = 1
* BAT1\_V\_CHANNEL = 0
* BAT1\_V\_DIV = 18.18

<figure><img src="https://2367252986-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLIgtGDAvVGkCKGOJb1bR%2Fuploads%2F2WNiaK3MLH6a4fUXJ4tQ%2FADC%20ADS1115%20Diagram.png?alt=media&amp;token=ff32d869-a889-4ce5-b6bc-7af8a4e0acd2" alt=""><figcaption><p>Sample wiring diagram</p></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/power-module-and-pdb/power-module/using-analog-pm-with-pixhawk-5x-6x.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.