Active Batch Programmer
The Active Tag Batch Programmer provides a convenient way of programming multiple OptiTrack components including the Tags, Pucks, and the Base Stations. This page provides instructions on how to use this program to configure the components.
All Tags/Pucks are pre-configured for every set of devices that ships in the same order, and we also make sure none of the Labels overlap. Thus, users should not need to use this batch programmer in general.
The cases when you would need to reconfigure the active components are:
When you have purchased new Tags/Pucks to add to a system from a previous order.
When there is a need to change the RF communication channel to avoid interference.
Requirements
Motive version 2.2 to 2.3.1
IMU Active Batch Programmer
Base Station: Firmware 2.2.2 or above
IMU Active Tags/Pucks: Firmware 2.2.1 or above
Additional Information
When needed, multiple Base Stations can be plugged into the same camera network as long as they are communicating through separate channels.
To use the IMU components, all of the devices, including the Base Station, must have firmware version 2.x or above installed. Please follow the instruction below to check the firmware versions on each device.
If the installed firmware is an older version, please contact us for assistance with upgrading the firmware.
CinePucks on firmware version 3.x may require assistance from Support to configure.
Download
You can download the active batch programmer from the following link: Active Batch Programmer.
Configuration Steps
Step 1) Install Active Batch Programmer
Double-click on the downloaded EXE file to begin the installation. This will copy a shortcut to your desktop.
Step 2) Launch the batch programmer
Without any of the active components connected to the computer yet start the batch programmer from the shortcut on your desktop. When it loads up, you should see the following window:
Step 3) Configure settings
Read-Only Mode is selected by default when the program launches. Stay in Read-Only Mode to view the active device's current configuration; unchecking Read-Only Mode will apply the settings selected in the Active Batch Programmer to the connected device.
Before connecting anything, configure the settings first:
Set Marker Labels is selected by default. Labels are active IDs assigned to individual markers and are applied to all the markers on a single device as a group. It's important that there are no overlapping labels, or IDs, assigned to the same batch of active Tags/Pucks. The label group will increment as each new device is programmed. This setting is applicable to Active Tags/Pucks only.
If needed, individual markers can be turned off on a device using the Disable Markers setting.
Radio Frequency Channel (RF Channel)
Select the Set Radio checkbox and type in the RF Channel you wish to use (applicable range 11-26). The RF Channel for any Active Tag/Puck must match the RF Channel of the BaseStation you are using; use the same RF Channel for all the Active Tags/Pucks connected to the same BaseStation.
The Uplink ID property is applied to active devices only and is unique to each device. This number will increment as each new device is programmed.
Set LED Options
Select the Set LED Options checkbox to adjust the brightness.
Custom Brightness: enter any value between 0 and 100. The Default is 20.
Auto Brightness: sets the value to 0.
When reconfiguring marker labels, ALL of the Tags and Pucks need to be reconfigured in the same session, so that labels do not overlap with other components in the system.
Active labels on a batch of active components.
One batch of active components contain one Base Station and one or more sets of active markers, whether the markers are on the active Tags or the Pucks.
To each active device (Tags or Pucks), a labeling group will be assigned. A labeling group is a set of unique active marker labels that gets programmed to the active IR LEDs on either the Tag or the Puck.
As long as none of the active components are assigned with an overlapping labeling group number, the batch programmer will make sure a unique active label gets assigned to each marker in the batch. Once all of the settings are configured, we can now start programming the labeling groups.
Step 4) Connect the components
If you want the configuration above to be applied to your Active Tag or Puck, you first must deselect Read-Only Mode (just report existing configuration)
While they are powered off, connect a Tag or a Puck to the computer via a USB cable.
Step 5) Power on the component
Once connected, power on the Puck or the Tag and wait for it to be recognized in the batch programmer. Once it connects, it will be listed under the current batch section, and the configured settings will be programmed automatically. Monitor the Log while connecting the component to make sure the configuration gets applied successfully.
Step 6) Unplug and connect another component
Once a device is configured, disconnect it and connect the next device to apply the same settings and unique IDs. Repeat this for all of the active components that need to be configured.
Click the Start New Batch button to configure a different BaseStation and set of devices.
Step 7) Check to make sure all Tags/Pucks have been programmed
At the end, you should see all of the components in your batch listed in the programmer with unique labeling group number assigned to each of them.
Firmware Compatibility
Firmware Compatibility Chart
Below is a chart to see which versions are compatible with which BaseStations and Active Tags/Pucks. Essentially, it is a one-to-one correlation between Active hardware and firmware versions with some exceptions. For Active Tags specifically, it boils down to: if it doesn't have an IMU then it's compatible with 1.x. If it has the first version of an IMU, then it is compatible with 2.x. And, if it has an upgraded IMU, then it is compatible with 3.x.
BaseStation and Active Tag compatibility Simplified
If you have a 1.x BaseStation you would use it with a 1.x Active Tag/Puck, if you have a 2.x Active Tag/Puck you would use it with a 2.x BaseStation and so on. The exception being that a 2.x BaseStation is compatible with both 2.x and 3.x Active Tags/Pucks.
Last updated
