> For the complete documentation index, see [llms.txt](https://campus-rover.gitbook.io/lab-notebook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://campus-rover.gitbook.io/lab-notebook/fiiva/customize_tb3.md).

# customize\_tb3.md

## Pito Salas / April 2022

## Objective

When we customize a TB3 with bigger wheels or a larger wheelbase, it is necesary to update the software in the OpenCr board.

* The steps required by OpenCR when changing wheel size or distance between wheels can be summarized as follows
* change WHEEL\_RADIUS, WHEEL\_SEPARATION and TURNING\_RADIUS in turtlebot3\_burger.h
* Change the circumference of the wheel in turtlebot3\_core.ino. Here, the circumference can be calculated by 2Pi \* WHEEl\_RADIUS. The default value of the circumference of burger is 0.207.
* Install Arduino IDE on your PC and write the edited file (turtlebot3\_core.ino). Please refer to the following e-Manual for this detail. <https://emanual.robotis.com/docs/en/platform/turtlebot3/opencr\\_setup/#opencr-setup> 3.3. At the end of OpenCR Setup, there are instructions for using the Arduino IDE, click to expand and see the details.


---

# 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://campus-rover.gitbook.io/lab-notebook/fiiva/customize_tb3.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.