> 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-t3pe/control.md). # CONTROL GREMSY T3V3 ### **Q 1:** What kind of control does Gremsy T3PE support? * Gremsy T3PE mainly support for Skynode FC and Auterion remote controller system. ### **Q 3:** Does Gremsy T3V3 support M600 (A3 + Lightbridge 2)? * Yes, it supports single and dual operation via M600 (A3 + Lightbridge 2) Please refer to the category – M600 on your left for more information. ### **Q 4:** Does Gremsy T3PE support Pixhawk FC? * Yes, it supports single control, automission via Mavlink command of Pixhawk Please refer to the category – Pixhawk on your left for more information. ### Q 5: Can I use the Herelink to control drone and Gremsy T3PE in single operation? * Yes, you can control the T3P3 directly form Herelink SBUS output or the combination with the Skynode/Cube FC --- # 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-t3pe/control.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.