> For the complete documentation index, see [llms.txt](https://2025.istvs.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://2025.istvs.org/submissions/papers/4335.md).

# 4335 - EXTENDED BRUSH MODEL FOR USE WITH GRAVELLY TERRAIN

{% hint style="info" %}
Paper presented at ISTVS 2025 | 55th Conference of the International Society for Terrain-Vehicle Systems <https://doi.org/10.56884/>
{% endhint %}

**Authors:** *Devon Cox, P. Schalk Els*

**Keywords:** Extended brush tyre model; Off road mobility; Agricultural tyres; Tyre soil interaction; Model validation

**Abstract:**

This paper presents the development of a physics-based brush tyre model extended for applications beyond conventional smooth surfaces. The research addresses limitations in existing tyre models when simulating vehicle dynamics on non-smooth, hard terrain. A comprehensive literature survey informed the methodological approach, which combines a physics-based brush model with empirical tread and soil models implemented in MATLAB. Initial validation results demonstrate promising performance, indicating that the combination of empirical soil characterization with the physics-based brush model effectively predicts tyre forces on non-smooth terrain. The model provides a framework for predicting traction limits in off-road conditions, expanding the simulation capabilities for vehicle dynamics on complex surfaces.


---

# 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://2025.istvs.org/submissions/papers/4335.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.
