> For the complete documentation index, see [llms.txt](https://docs.cartographer3d.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cartographer3d.com/original-plugin/firmware-archive/manual-methods/switching-between-can-and-usb-operation-v3-only.md).

# Switching between CAN and USB Operation (v3 only)

Switching your probe between USB and CAN modes, simply, requires you to reflash the firmware suitable for the mode of operation you wish to use.

When doing this, it is VITAL that you flash not only the Cartographer Firmware, but also the modified Katapult bootloader as well.

My recommendation would be for you to do this via your computer, using the STM32CubeProgrammer, [follow our guide on updating the firmware via DFU Mode](/original-plugin/firmware-archive/manual-methods/cartographer-with-input-shaper/update-via-dfu-mode.md).

{% content-ref url="/pages/wulGU7niKROq4FSGXyfW" %}
[Update via DFU Mode](/original-plugin/firmware-archive/manual-methods/cartographer-with-input-shaper/update-via-dfu-mode.md)
{% endcontent-ref %}

Any questions or issues, please feel free to join our [Discord server,](https://discord.gg/HjJbdbVrJM) where we will be happy to provide help and support.


---

# 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.cartographer3d.com/original-plugin/firmware-archive/manual-methods/switching-between-can-and-usb-operation-v3-only.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.
