> 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/pwm-signal-voltage-mod.md).

# PWM Signal Voltage MOD

The newest batch (version RC09 and newer) of Pixhawk 6C 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="warning" %}
The current RC13 PCB design only supports MAIN (I/O) PWM signal voltage modification
{% endhint %}

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

<figure><img src="https://2367252986-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLIgtGDAvVGkCKGOJb1bR%2Fuploads%2FnFrtrLLuHjJXkHnY1Z3f%2Fimage.png?alt=media&amp;token=d7767671-2598-4524-8352-ed4f49892e20" alt=""><figcaption><p>RC09 PCB</p></figcaption></figure>

For RC12 PCB design, the process is more straightforward. Locate the JP1 soldering pad at the bottom left of the PCB. Bridge the JP1 pads for 5V and unbridge them to revert to 3.3V.

<figure><img src="https://2367252986-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLIgtGDAvVGkCKGOJb1bR%2Fuploads%2Ff9ITihWHv2iIjaaqI8iM%2FHF-A005-RC12_Bottom.png?alt=media&amp;token=814c2081-6528-4abe-aacf-ce5362387f7c" alt=""><figcaption><p>RC12</p></figcaption></figure>

For the RC13 PCB design, the AUX (FMU) PWM outputs no longer support 5V signal modification.

To change the MAIN (I/O) PWM signal level to 5V, find the soldering pads with JP1 silk print next to it. By default, the pads are not bridged, and bridging them will convert the MAIN (I/O) PWM signal level to 5V.

<figure><img src="https://2367252986-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLIgtGDAvVGkCKGOJb1bR%2Fuploads%2FViec53I8aNaLmgrEKAlh%2Fimage.png?alt=media&amp;token=1395d28a-772a-4b09-8a4a-32c3625ccd91" alt=""><figcaption><p>RC13</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/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.