> For the complete documentation index, see [llms.txt](https://docs.optitrack.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.optitrack.com/activeio/activeio-hardware/activeio-tag8.md). # ActiveIO Tag8 A Quick Start Guide and specifications for the ActiveIO Tag8. ## Overview The ActiveIO Tag8 is a tag with 8 attached LED markers that can be used to track an individual asset. The ActiveIO Tag8 is a printed-circuit assembly (PCA) that lets users integrate OptiTrack's ActiveIO technology into motion-capture assets of their own making. It's the same technology built into other ActiveIO devices, including HMD Clips.
An ActiveIO Tag8 with attached LEDs visible.
## Quick Start Guide ### Requirements * Motive 3.5 or later. * ActiveIO BaseStation. See the [ActiveIO BaseStation page](/activeio/activeio-hardware/activeio-basestation.md) for instructions on setting up and using an ActiveIO BaseStation. ### Setup The ActiveIO Tag8 needs no assembly before use. ### Activation 1. The ActiveIO Tag8 can be powered by a battery via connector or by an outside power source via USB-C port. When the Tag8 is connected to a battery, press the Power Button to turn it on. If it's powered via USB, it automatically powers on. 2. Once powered, the ActiveIO Tag8 appears in Motive.
An ActiveIO Tag8 closeup with the power button and indicator LEDs identified and labeled.
### Operation The ActiveIO Tag8 needs no programming with a unique label. Once connected to Motive, all labeling is automatic. When a battery is connected, the Tag8 can charge the battery if it's connected to an outside power source via USB. ### Indicator LEDs When the Tag8 is connected to a battery, the lower right LED indicates battery strength and charging. * It appears solid blue when battery power is good. * It appears solid orange when the battery needs charging. * It blinks red when the battery is critically low. * It blinks green when charging. * It appears solid green when fully charged or no battery is installed. * It flashes red when a charging error occurs. * **Note:** IR marker LEDs become disabled until the connected battery is recharged. The upper left LED: * Blinks blue when the ActiveIO Tag8 is synced. * Breathes green when scanning. * Appears solid green if the Tag8 is in Continuous mode. The upper right LED: * Appears solid yellow when the Inertial Measurement Unit (IMU) needs calibration. * Appears solid green when the IMU is calibrated. ## Modes The ActiveIO Clip has two synced modes (Patterned and Always On) and one non-synced mode (Continuous). To switch between Patterned and Always On modes, a property is available in Motive. To switch between either of the synced modes (Patterned and Always On) and the non-synced mode (Continuous), double-click the power button, wait 1 second, then double-click it again. #### Patterned and Always On (Synced) Patterned and Always On modes are synchronized with the camera system through an ActiveIO BaseStation. Synchronization allows the IR markers to be as bright and visible as possible when needed while reducing power consumption overall. The upper left indicator LED on the Tag8 blinks blue when it's synced. **NOTE:** The two synced modes (Patterned and Always On), do not work with the previous generation Active BaseStation. The two synced modes differ as follows: * **Patterned:** Each IR marker LED flashes a unique identifying pattern. * **Always On:** All IR marker LEDs are on during camera exposure. #### Continuous (not Synced) Continuous mode is not synchronized and does not require an ActiveIO BaseStation. In Continuous mode, the IR LEDs emit constant light with no blinking and are not synced with the camera exposure. The markers can appear dimmer to the cameras than they do in the synced modes, and power consumption is increased. In Continuous mode, the upper left indicator LED on the Tag8 is solid green. ## Specifications
Technical drawing for an ActiveIO Tag8.
Electrical Attributes * **On/Off:** Button * **Power Input:** USB 5V * **Power Draw (@PSE):** 100 mA (Idle), 150 mA (Paired) * **Connector:** USB Type-C / 4 Pin Molex Header
Dimensions * **Width:** 30.5 mm / 1.2 inches * **Height:** 45.1 mm / 1.78 inches * **Distance Between Mounting Holes (Width):** 26.2 / 1.03 inches * **Distance Between Mounting Holes (Height):** 38 mm / 1.5 inches * **Depth of Board:** 1.7 mm / .07 inch * **Depth of Board with Components:** 7.1 mm / .28 inch
LEDs * **LED Markers:** 8 * **LED Indicators:** 3
RF * **Frequency:** 2.4 GHz * **FCC:** CISPR 32 CLASS A/2.4GHz Intentional Radiator * **FCC ID:** XPYNORAB2 PART 15 of FCC Rules
--- # 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.optitrack.com/activeio/activeio-hardware/activeio-tag8.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.