> For the complete documentation index, see [llms.txt](https://docs.k9rockettech.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.k9rockettech.com/open-development-platforms/vesc.md).

# VESC

The VESC is one of the most underrated open projects in our opinion. It is the ultimate brushless motor driver project, pushing the boundaries of squeezing the maximum performance out of brushless motors with just the drivers; employing clever controller design and software. We've been exploring VESC for our range of projects including the possibility of near-silent electric propulsion systems just by clever hardware implementation on the VESC platform. 

{% embed url="<https://vesc-project.com>" %}

## Real-world Demo

Benjamin Vedder is the creator and lead developer of VESC (Vedder ESC), and his channel is packed with technical information and demos. Watch his videos to learn more about some of the mind-blowing control of brushless motors he can manage just through software

{% embed url="<https://www.youtube.com/@BenjaminsRobotics>" %}


---

# 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://docs.k9rockettech.com/open-development-platforms/vesc.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.