> 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-basestation.md).
# ActiveIO BaseStation
This page provides specifications for the ActiveIO BaseStation and information on its use.
The BaseStation is the ActiveIO hardware component that links other ActiveIO components to Motive. Using a radio frequency, or RF, channel between 11-26, the ActiveIO BaseStation synchronizes OptiTrack cameras with ActiveIO Tags, Pucks, Clips, Calibration Wands and Squares. Once the BaseStation receives the signal from the active component, it sends that data to the Motive computer along the camera network. This lets Motive recognize Active Pucks, Tags, and other devices even with significant occlusion of the LED markers, which is not the case with passive markers.
If you use ActiveIO Tags, Pucks, Clips, or other devices, at least one ActiveIO BaseStation is required per tracking system.
For larger volumes, the approximate range from BaseStation to Tags or Pucks is 100 feet.
{% hint style="info" icon="comment-question" %}
#### Can I use ActiveIO and Active Classic hardware together?
You can use ActiveIO and Active Classic devices in a single instance of Motive, with the ActiveIO devices connected to an ActiveIO BaseStation and the Active Classic devices connected to an Active Classic BaseStation.
{% endhint %}
## BaseStation Specifications
## BaseStation Load Capacity
An ActiveIO BaseStation can support as many as 70 ActiveIO devices.
## ActiveIO BaseStation Properties
As shipped, ActiveIO BaseStations connect to the OptiTrack system without additional configuration by the user.
* In the [Devices pane](/motive-ui-panes/devices-pane.md), select the ActiveIO BaseStation.
* The [Properties pane](/motive-ui-panes/properties-pane.md) displays the device name, serial number, and frame rate.
Click the menu button in the top right corner of the Properties pane to view Advanced device information.
{% hint style="info" icon="memo-pad" %}
#### Notes Property
The Advanced Properties include the user-editable Notes field. Use this freeform-text field to identify devices in the manner that best suits your workflow.
{% endhint %}
## **BaseStation Lightbar**
The Lightbar on the bottom front of the ActiveIO BaseStation indicates the device status.
*Note: Behavior of the Lightbar on the ActiveIo BaseStation is controlled by firmware and is subject to change.*
Off
Status: Powered & Awaiting Connection
When the ActiveIO BaseStation is first plugged in, the LED light bar is off until it receives commands from Motive and has successfully authenticated via the security key. If it is not successful in connecting to the network, but receiving power, it will remain off.
Slow Flashing Cyan, No IR
Status: Idle
Powered and connected to the network, but Motive is not running.
When powered on but not connected to Motive, the ActiveIO BaseStation flashes between cyan lights (above) and no lights (below)
Solid Green
Status: Receiving Data
The ActiveIO BaseStation is receiving / sending data.
Cycle Cyan
Status: Firmware Update
Firmware is being written to flash.
Cyan LEDs turn off from left to right while the device uninstalls the existing firmware, then the cyan LEDs return from left to right while the firmware is written. A single green LED flashes across the entire bar when the update is complete.
---
# 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-basestation.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.
menu button in the top right corner of the Properties pane to view Advanced device information.
