> 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/bevels/quickstart.md).

# Bevel Quickstart

Axon Bevels Usage Tips

**Mechanical Specifications**

* Material: Hardened Steel
* Finish: Black Zinc Plated
* Hub Bevel Weight: 14g
* Pinion Bevel Weight: 3.5g
* Gear ratio: 52:18 (2.88:1) 
* Module: 0.8 
* Hub Bevel OD: 41.8mm
* Pinion Bevel OD: 15.6mm

**In the Box**

* 1x Pinion Bevel Gear
* 1x Hub Mount Bevel Gear

**CAD Download**

[Axon Bevels Hub Gear](https://cdn.shopify.com/s/files/1/0657/9182/0008/files/AXON-ROBOTICS_HUB_BEVEL.step?v=1693714737)

[Axon Bevels Pinion Gear](https://cdn.shopify.com/s/files/1/0657/9182/0008/files/AXON-ROBOTICS_PINION_BEVEL.step?v=1693714736)

## Spacing Bevel Gears

For bevel gears, the smoothest operation does not always occur at the nominal center-to-center distance. This can be due to:

* Axis Misalignment
* Runout 
* Tolerance Stack-up

To mitigate these issues, we recommend offsetting the Hub Bevel 0.5mm away from the center axis to allow some space between the teeth when they mesh.

<figure><img src="https://2269588985-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9eh1a50wToy49XgPSa8i%2Fuploads%2F7wNjKV1gHabnBtfUSOUO%2FAxon-Robotics_Bevels_Assembly_9mm.png?alt=media&amp;token=d7509b12-47fd-4a99-a304-d3d093b9d48e" alt="" width="375"><figcaption><p>Axon Bevels Recommended Center to Center Offsets</p></figcaption></figure>

<figure><img src="https://2269588985-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9eh1a50wToy49XgPSa8i%2Fuploads%2FNJpPv2Ig7hMR5o8BUpSi%2FAxon-Robotics_Bevels_Assembly_8.5mm.png?alt=media&amp;token=5a25cfa7-627e-42a6-b700-3dfd48717a3c" alt="" width="375"><figcaption><p>Axon Bevels Nominal Center to Center Offsets</p></figcaption></figure>

## Usage Examples

### Mecanum Drivetrain

<figure><img src="https://2269588985-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9eh1a50wToy49XgPSa8i%2Fuploads%2FHyKWMVFMkf0wvgFzZERw%2FAxon-Robotics_Bevels_Mecanum_Assembly.png?alt=media&amp;token=24fb3119-e065-429e-9fdd-a521309df735" alt="" width="375"><figcaption><p>Mecanum Wheel Power Transmission</p></figcaption></figure>

### Swerve Drivetrain

<figure><img src="https://2269588985-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9eh1a50wToy49XgPSa8i%2Fuploads%2FdfsUDcmw0FRjHO6xYMxm%2FAxon-Robotics_Bevels_Swerve_Assembly.png?alt=media&amp;token=c7978cbc-c1eb-47a1-a525-ea7b16c0ffa3" alt="" width="375"><figcaption><p>Swerve Module Power Transmission</p></figcaption></figure>

### Intake Power Transmission&#x20;

Coming Soon!

### Lift Power Transmission

Coming Soon!


---

# 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/bevels/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.