> For the complete documentation index, see [llms.txt](https://docs.gremsy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gremsy.com/gimbals/gremsy-t3v3/getting-started/features.md).
# FEATURES
An intuitive hardware interface, including a variety of ports, has been relocated on the QR to quickly interface with multiple devices such as a third-party flight controller, remote control, auxiliary I/O, and power for your ideal system of cameras/accessories.
**HEATED & TEMPERATURE-CONTROLLED IMU**
The heated and temperature-controlled IMU sensor with advanced 6-point calibration allows reliable performance even in extreme weather. Temperature is maintained within 0.2 degrees Celsius accuracy.
**HIGH PERFORMANCE GIMBAL CONTROLLER**
The gMotion Controller, designed and made by
Gremsy, is based on a 32-bit high-performance ARM microprocessor providing fast
response and accurate calculation. Sensor
data and motor correction are updated as
fast as 2000 times per second to enable
incredibly smooth footage.
**CLEAN DESIGN—INTERNAL WIRING**
No exterior wires, more solid. This clean design helps the T3 overcome wind resistance with ease to bring out the best video quality while staying agile.
**BUILT FOR AERIAL WORK**
The T3 has a lot of nice features that enable
users to apply it not only for aerial inspection
and mapping but also for high end aerial
cinematography
---
# 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.gremsy.com/gimbals/gremsy-t3v3/getting-started/features.md?ask=&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.
