> For the complete documentation index, see [llms.txt](https://docs.axon-robotics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.axon-robotics.com/servos/quickstart.md).

# Servo Quickstart

Received your servos? Don't know what to do? Look no further

### Unboxing

All servos come configured ready to use out of the box. Also included in the box is an aluminum servo horn, and a bag with some mounting accessories. However, to unlock the full potential of MK2 series servos, you will need the [Programmer MK2](/servos/programmer.md)

### Usage

#### 4.8v operation

They are directly compatible with the REV Robotics Control or Expansion Hub and can be used just like any other servo.

{% hint style="warning" %}
Axon servos have a stall current greater than the REV Robotics Control hub and Expansion hub can supply. Make sure to lower the maximum power of your servos if you plan on using them in this configuration.
{% endhint %}

#### 6.0v operation (recommended)

To get the most performance out of your Axon servos, we recommend using the REV Robotics SPM, Servo Hub, or other similar power injector. This bumps the voltage from 4.8V to 6V and mostly eliminates the concern surrounding current limitation.


---

# 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.axon-robotics.com/servos/quickstart.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.