> For the complete documentation index, see [llms.txt](https://docs.gyroflow.xyz/app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gyroflow.xyz/app/advanced-usage/using-external-gyro-source/esp-gyrologger.md).

# ESP-gyrologger

[esp-gyrologger](https://github.com/VladimirP1/esp-gyrologger) is an open source motion data logger by Vladimir Pinchuk. It's a firmware for the ESP32 and ESP32-C3 microcontrollers with a BMI270, BMI160 or MPU6050 gyro. It's small and light, so you can mount it on any camera that doesn't record motion data, and load its logs in Gyroflow.

* It's set up from a web page over its own Wi-Fi network, where you also change the settings and calibrate the accelerometer.
* You can also connect a button and a LED to start and stop the recording.
* You'll have to synchronize the logs with the video, see [Synchronizing external gyro source](https://docs.gyroflow.xyz/app/getting-started/basic-usage/synchronization.md#synchronizing-external-gyro-source).

## DIY

You can build one from an ESP32 or ESP32-C3 board with 4 MB of flash and a gyro module, connected with 4 wires. The [repository](https://github.com/VladimirP1/esp-gyrologger#how-to-flash-and-get-started-with-the-diy-version) has the wiring, the firmware download, the flashing steps and a video tutorial.

## Ready-made boards (PCBA)

There are PCB designs for a tiny dedicated board (EspLog, 11 x 14 mm) that you can order assembled from a PCB manufacturer:

* the original 4-layer design: [EasyEDA project](https://oshwlab.com/vladimir.pinchuk01/gyro-logger-esp32c3_copy)
* 2-layer designs, including one with a 4.5-30 V input: [esplog-hardware](https://github.com/VladimirP1/esplog-hardware) (KiCad 6)


---

# 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://docs.gyroflow.xyz/app/advanced-usage/using-external-gyro-source/esp-gyrologger.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.
