> 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/payloads/vio/tracking-and-ai-object-detection/types-of-tracking.md). # Types of Tracking ### **1. Overview** * The Vio payload supports two type of objects for tracking: undefined objects and trained objects. * With "undefined object" mode, the user can track whatever they see in the view of the camera (both EO and IR). The selection can be finished by moving the gimbal targeting the object (at the center view), then sending the "trigger" command by using the remote. * With "trained object" mode, the user can see all the detected objects in the view of the camera (humans and cars are ready for now). The tracking will start after the user selects the interest object and sends the "trigger" command by using the remote. * The tracking on the Vio payload is active tracking, which means the result of the tracking algorithm will be sent to the gimbal for following the object when it is moving.

### **2. Select Tracking Type** * Using the camera settings menu, section "Tracking Mode" * Select from the PayloadAssistant app --- # 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/payloads/vio/tracking-and-ai-object-detection/types-of-tracking.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.