> For the complete documentation index, see [llms.txt](https://manual.rush.sr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.rush.sr/readme/break-in-and-initial-setup/bedding-brakes.md).

# Bedding Brakes

It is very important to bed your brakes properly. The Rush SR is a very light car, but improper transfer of pad material to the rotors will lead to a very "wooden" brake feel and an inability to lock the tires under any pressure.

Note that the Rush SR does not have power brakes or ABS (like a Formula car!), so you will need to apply much more pressure than you are used to from a GT car. Don't worry, you'll get used to it, and start to appreciate the fine control your foot can do with manual braking.

With a new car, or new pads/rotors, the following procedure should be followed, and can be followed simultaneously with an [engine break-in](/readme/break-in-and-initial-setup/engine-break-in.md). It is useful to have a mostly empty track - do not slam on the brakes with people behind you!

1. Take the car out for an approx. 25 minute session.
2. During this session, go slow, and use the brakes as little as possible in the corners. Slowly build temperature in the brakes by using them in the straights, then let them cool.
3. Continue to increase brake pressure until you're at about 90% pressure. At this point, you should be about 15-20 minutes in. If you start to feel the brakes "going off", you're done with this step.
4. Now cool off your brakes. Do 1-2 laps with minimal braking, then head into the pits.
5. Once in the pits, DO NOT use the brakes to the extent possible, and let them cool completely (\~45min). Do not press them when the car is stationary as you risk depositing extraneous pad material.

Owners have also found this [Section 111 article](https://sector111.blogspot.com/2018/09/brake-pad-types-and-bedding-padsrotors.html) handy.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://manual.rush.sr/readme/break-in-and-initial-setup/bedding-brakes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.