> 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/autopilot/pixhawk-6c-mini/pwm-signal-voltage-mod.md).

# PWM Signal Voltage MOD

The newest batch of Pixhawk 6C mini now supports switchable PWM signal voltage (3.3V or 5V). The modification requires the user to open the casing of the Pixhawk flight controller and be familiar with soldering.

{% hint style="warning" %}
Any damage caused during the modification is not covered by warranty
{% endhint %}

{% hint style="danger" %}
The current shipping 6C variants only support MAIN (I/O) PWM signal voltage level modification. AUX (FMU) PWM signal level cannot be changed.
{% endhint %}

{% hint style="danger" %}
The IMU daughter board is glued to the case; please be careful when removing the flight controller outer case during disassembly.
{% endhint %}

Once you remove the top half of the flight controller casing, you'll notice the ribbon connector with silicone glue along its sides. The connector isn't fully adhered, so it can be detached with a small amount of force. After removing the ribbon connector, you'll have safe access to the back side of the PCB for making modifications to the PWM signal voltage.

To switch the PWM signal voltage, bridge the 3v3 or 5v soldering pads on the PCB by applying solder to the pads. Make sure the unused pads are cleaned and not shorted.

### Early version modding procedure

For Pixhawk 6C mini, you have the option to change the PWM signal voltage for FMU outputs and IO outputs separately. Make sure the correct soldering pads are bridged to avoid any damage.

Pixhawk 6C mini-A (legacy) and mini-B have slightly different PCB designs. Follow the red square in the diagram below to locate the PWM voltage select soldering pad.

<figure><img src="https://2367252986-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLIgtGDAvVGkCKGOJb1bR%2Fuploads%2FUJodkCC1Et9gBbJJx2Qi%2Fimage.png?alt=media&amp;token=8cb85eaf-a9d2-4954-8084-d6a1bbe74bf5" alt=""><figcaption><p>Pixhawk 6C mini-A PCB</p></figcaption></figure>

<figure><img src="https://2367252986-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLIgtGDAvVGkCKGOJb1bR%2Fuploads%2FrbOUtl8iDRzolco5ci0p%2Fimage.png?alt=media&amp;token=9d719a76-931d-470d-a1de-0774ae064bc8" alt=""><figcaption><p>Pixhawk 6C mini-B PCB</p></figcaption></figure>

### Pixhawk 6C Mini-A RC00+

For 6C Mini-A with RC00 or newer PCB, the AUX (FMU) PWM output no longer supports 5V signal level modification. To change the MAIN (I/O) PWM signal voltage level to 5V, find the JP1 soldering pad and bridge the pads as highlighted in the diagram below.

{% hint style="info" %}
Avoid removing any nearby resistors or other components.
{% endhint %}

<figure><img src="https://2367252986-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLIgtGDAvVGkCKGOJb1bR%2Fuploads%2F5g2ZK63XOsnVf8zwHr2Z%2Fimage.png?alt=media&amp;token=5787a8f3-38b8-4e95-a27a-276d5d39dd12" alt=""><figcaption><p>RC00</p></figcaption></figure>

<figure><img src="https://2367252986-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLIgtGDAvVGkCKGOJb1bR%2Fuploads%2FoQp9N3FxDLmYqzUJDlaF%2Fimage.png?alt=media&amp;token=1d42b9ab-a0dd-4038-99d7-0fc417c4ed74" alt=""><figcaption><p>RC01</p></figcaption></figure>

### Pixhawk 6C Mini-B RC07+

For 6C Mini-B with RC07 or newer PCB, the AUX (FMU) PWM output no longer supports 5V signal level modification. To change the MAIN (I/O) PWM signal voltage level to 5V, find the JP1 soldering pad and bridge the pads as highlighted in the diagram below.

{% hint style="info" %}
Avoid removing any nearby resistors or other components.
{% endhint %}

<figure><img src="https://2367252986-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLIgtGDAvVGkCKGOJb1bR%2Fuploads%2FOdBCcAseWkXWpkst2o5R%2Fimage.png?alt=media&amp;token=c9f1f8a8-d323-4575-b18f-8c6d648db220" alt=""><figcaption><p>RC07</p></figcaption></figure>

<figure><img src="https://2367252986-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLIgtGDAvVGkCKGOJb1bR%2Fuploads%2F7PRbGsgp7Ljzbqkv0vwt%2Fimage.png?alt=media&amp;token=75f5d377-e119-457a-bcbe-753a87b2734b" alt=""><figcaption><p>RC08</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/autopilot/pixhawk-6c-mini/pwm-signal-voltage-mod.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.