> 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/camera.md). # CAMERA GREMSY T3V3 ### **Q 1:** What kind of cameras does Gremsy T3PE support? It currently supports cameras with a maximum depth of 100 mm (measured from the center of gravity), a maximum height of 120 mm, and a maximum width of 152 mm. The maximum payload of T3 is 1.7 kgs (3.7 lbs). Gremsy T3 Camera Compatibility List (non-comprehensive list): * Sony A7S (mk I - II), * Sony A7R (mk I - IV) * Sony A9 ( mk I – II ) * Sony A6000 series * Fujifilm X-T series * Phase One iXM 50/10 (apply for 80mm lens or lower ) * Panasonic GH3, GH4, GH5, GH5s * Canon 5D Mk I, II, III, IV * Nikon D810, D800, Z series\ .... ### **Q 2:** Is it difficult to balance the gimbal and camera? * No. Changing the setup for different camera arrangements is quick and simple. * Learn more about our balance tutorial at: Updating… ### **Q 3:** Does Gremsy T3PE support HDMI signal? * Yes, Gremsy T3V3 allows you to transfer HDMI signal passthrough gimbal via 2 Micro HDMI ports. ### **Q 4:** Does Gremsy T3PE support trigger signal? * Exactly that the T3V3 provides 9 signal passthrough gimbal via AUX port, you can transfer the control signal from control module or flight controller to camera via gimbal. ### Q 5: Which trigger devices do you recommend? * Seagull #REC * Intelli-G long range --- # 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/camera.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.