> For the complete documentation index, see [llms.txt](https://tempdocs.zerog.one/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tempdocs.zerog.one/projects/mercury-one.1/introduction.md).

# Introduction

## <mark style="color:red;">MERCURY ONE.1</mark> <a href="#mercury-one1" id="mercury-one1"></a>

<table data-card-size="large" data-view="cards" data-full-width="false"><thead><tr><th>Difficulty</th><th>Language</th></tr></thead><tbody><tr><td>Moderate to experienced</td><td>English</td></tr></tbody></table>

## <mark style="color:red;">What's this project about?</mark>

The Mercury One.1 upgrade transforms your current Ender 5(Pro/Plus) into a CoreXY system. This provides an improvement over the Cartesian system, which relies on V-rollers that may lack precision and demand considerable maintenance. Additionally, the CoreXY system is optimized for higher speeds, enhancing your 3D printing experience and quality.

### <mark style="color:red;">Who's this project for?</mark> <a href="#whos-this-project-for" id="whos-this-project-for"></a>

If you’re an Ender 5, Ender 5 Pro, or Ender 5 Plus owner who is dissatisfied with print quality, speed, or encountering other issues, consider this upgrade. Whether you’re interested in learning how to modify printers or simply seeking an enjoyable new project, this is the perfect opportunity for you!

## <mark style="color:red;">What machines does this run on?</mark>

We support the Ender 5, Ender 5 Pro, and Ender 5 Plus frames when upgrading to Mercury One.1. To install this upgrade, you will need to remove the X and Y motion system from the existing frame.\ <mark style="color:red;">**Please note**</mark>**&#x20;that some&#x20;**<mark style="color:red;">**soldering or wire extension may be necessary**</mark> during this process.

### <mark style="color:red;">Difficulty</mark> <a href="#difficulty" id="difficulty"></a>

We consider this build to be easy to moderate in difficulty. However, the more challenging aspects might be the firmware and wiring. As of now, we haven’t written any configuration for Klipper, and some wires may need to be remade or extended.


---

# 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://tempdocs.zerog.one/projects/mercury-one.1/introduction.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.
