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

# 6540 - KRC BEVAMETER DEVELOPMENT AND MOBILITY DATA COLLECTION

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

**Authors:** *Russell Alger, Peter Alger*

**Keywords:** Bevameter; Bekker-Wong; Vehicle Mobility; Traction; Sinkage

**Abstract:**

The Keweenaw Research Center (KRC) at Michigan Tech University has designed and built an automated Bevameter to measure in-situ soil strength and derive Bekker-Wong mobility parameters. Testing has been performed in a number of soils including high organic soils (peat), silts, sands, gravels, and lunar regolith at various moisture contents. A data set containing derived strength parameters is being built and results that are non-proprietary and non-controlled are shared with permission on the KRC website.

KRC has also performed several vehicle mobility tests both in the field and in the lab on the KRC single wheel tire tester. A large amount of this collected data is also available on the website with permission. All testing includes cone penetrometer, nuclear density, moisture, and surface friction when possible.

This paper will be an overview of the Bevameter and the data collected to date, as well as an overview of other mobility testing that has been performed.


---

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