LogoLogo
WebsiteSupportDownloadsForumsQuick LinksContact Us
v2.3
v2.3
  • OptiTrack Support Documentation
  • WHAT'S NEW
    • Unreal Engine: OptiTrack InCamera VFX
  • QUICK START GUIDES
    • Quick Start Guide: Getting Started
    • Quick Start Guide: Precision Capture
    • Quick Start Guide: Tutorial Videos
    • Quick Start Guide: Prime Color Setup
    • Quick Start Guide: Active Marker Tracking
    • Quick Start Guide: Outdoor Tracking Setup
  • HARDWARE
    • Cameras
      • Ethernet Cameras
        • PrimeX 41
        • PrimeX 22
        • PrimeX 13
        • PrimeX 13W
        • SlimX 13
        • Prime Color
      • USB Cameras
        • Slim 3U
        • Flex 13
        • Flex 3
        • V120:Duo
        • V120:Trio
        • V120:Duo and Trio Setup
        • Adjusting Global Origin for Tracking Bars
    • Prepare Setup Area
    • Camera Mount Structures
    • Camera Placement
    • Camera Network Setup
    • Aiming and Focusing
    • Camera Status Indicators
  • MOTIVE
    • Installation and Activation
    • Motive Basics
    • Calibration
      • Continuous Calibration
      • Calibration Squares
    • Markers
    • Assets
      • Gizmo Tool: Translate, Rotate, and Scale
    • Rigid Body Tracking
      • Aligning Rigid Body Pivot Point with a Replicated 3D Model
    • Skeleton Tracking
    • Data Recording
      • Data Types
    • Labeling
    • Data Editing
    • Data Export
      • Data Export: BVH
      • Data Export: C3D
      • Data Export: CSV
      • Data Export: FBX
      • Data Export: TRC
    • Data Streaming
    • Camera Video Types
    • Audio Recording
    • Motive HotKeys
    • Measurement Probe Kit Guide
    • Motive Batch Processor
    • Reconstruction and 2D Mode
    • Tracking Bar Coordinate System
      • Transforming Coordinate System: Global to Local
  • MOTIVE UI PANES
    • Application Settings
      • Settings: Live Reconstruction
      • Settings: General
      • Settings: Views
      • Settings: Assets
        • Skeletons
        • Rigid Body
      • Settings: Camera
    • Mouse and Keyboard
    • Assets Pane
    • Builder Pane
    • Calibration Pane
    • Control Deck
    • Data Pane
    • Data Streaming Pane
    • Devices Pane
    • Edit Tools Pane
    • Graph View Pane
    • Info Pane
    • Labels Pane
    • Log Pane
    • Marker Sets Pane
      • Marker Name XML Files
    • Measurement Pane
    • Probe Pane
    • Properties Pane
      • Properties Pane: Camera
      • Properties Pane: Force Plates
      • Properties Pane: NI-DAQ
      • Properties Pane: OptiHub2
      • Properties Pane: Rigid Body
      • Properties Pane: Skeleton
      • Properties Pane: Take
      • Properties Pane: eSync2
    • Reference View pane
    • Status Panel
    • Toolbar/Command Bar
    • Viewport
  • PLUGINS
    • OptiTrack Unreal Engine Plugin
      • Unreal Engine: OptiTrack Live Link Plugin
      • Unreal Engine: OptiTrack Streaming Client Plugin
      • Unreal Engine: HMD Setup
      • Unreal Engine: MotionBuilder Workflow
      • Unreal Engine VCS Inputs
    • OptiTrack Unity Plugin
      • Unity: HMD Setup
    • OptiTrack OpenVR Driver
    • Autodesk Maya
      • Autodesk Maya: OptiTrack Insight VCS Plugin
    • Autodesk MotionBuilder
      • Autodesk MotionBuilder Plugin
      • Autodesk MotionBuilder: OptiTrack Skeleton Plugin
      • Autodesk MotionBuilder: OptiTrack Optical Plugin
      • Autodesk MotionBuilder: OptiTrack Insight VCS Plugin
      • Autodesk MotionBuilder: Timecode Data
    • OptiTrack Peripheral API
    • External Plugins
      • Houdini 19 Integration
  • ACTIVE COMPONENTS
    • Active Components Hardware
      • Active Puck
      • CinePuck
      • BaseStation
      • Information for Assembling the Active Tags
      • Manus Glove Setup
    • Configuration
      • Active Batch Programmer
      • Active Hardware Configuration: PuTTY
      • Active Component Firmware Compatibility
    • Active Marker Tracking
      • Active Finger Marker Set
      • Active Marker Tracking: IMU Setup
  • SYNCHRONIZATION
    • Synchronization Hardware
      • External Device Sync Guide: eSync 2
      • External Device Sync Guide: OptiHub2
    • Synchronization Setup
    • OptiTrack Timecode
  • VIRTUAL PRODUCTION
    • Unreal Engine: OptiTrack InCamera VFX
    • Entertainment Marker Sets
    • PrimeX 41
  • MOVEMENT SCIENCES
    • Movement Sciences Hardware
      • General Motive Force Plate Setup
      • AMTI Force Plate Setup
      • Bertec Force Plate Setup
      • Kistler Force Plate Setup
      • Delsys EMG Setup
      • NI-DAQ Setup
      • Multiple Device Setup
      • Prime Color Setup
    • Movement Sciences Marker Sets
      • Biomechanics Marker Sets
      • Biomech (57)
      • Rizzoli Marker Sets
    • For Visual3D Users
  • VIRTUAL REALITY
    • VR Plugins
      • VR Unreal Engine
        • OptiTrack Unreal Engine Plugin
        • Unreal Engine: OptiTrack Live Link Plugin
        • Unreal Engine: OptiTrack Streaming Client Plugin
        • Unreal Engine VCS Inputs
      • VR Unity
        • OptiTrack Unity Plugin
      • VR OpenVR
        • OptiTrack OpenVR Driver
    • VR HMD Setup
      • Unreal Engine: HMD Setup
      • Unity: HMD Setup
      • Manually Calibrating the HMD Pivot Point
      • Sync Configuration with an HTC Vive System
    • Navigation Controller Guide
    • SlimX 13
    • Active Marker Tracking
      • Active Finger Marker Set
      • Active Marker Tracking: IMU Setup
    • Synchronization Hardware
      • External Device Sync Guide: eSync 2
      • External Device Sync Guide: OptiHub2
  • ANIMATION
    • Autodesk Maya
      • Autodesk Maya: OptiTrack Insight VCS Plugin
    • Autodesk MotionBuilder
      • Autodesk MotionBuilder Plugin
      • Autodesk MotionBuilder: OptiTrack Skeleton Plugin
      • Autodesk MotionBuilder: OptiTrack Optical Plugin
      • Autodesk MotionBuilder: OptiTrack Insight VCS Plugin
      • Autodesk MotionBuilder: Timecode Data
  • ROBOTICS
    • PrimeX 22
    • Outdoor Tracking Setup
  • DEVELOPER TOOLS
    • Developer Tools Overview
    • NatNet SDK
      • NatNet 4.0
      • NatNet: Class/Function Reference
      • NatNet: Creating a Managed (C sharp) Client Application
      • NatNet: Creating a Native (C++) Client Application
      • NatNet: Data Types
      • NatNet: Matlab Wrapper
      • NatNet: Migration to NatNet 3.0 libraries
      • NatNet: RebroadcastMotiveData Sample
      • NatNet: Remote Requests/Commands
      • NatNet: Sample Projects
      • NatNet: Unicast Data Subscription Commands
      • Latency Measurements
    • Motive API
      • Motive API: Quick Start Guide
      • Motive API Overview
      • Motive API: Function Reference
      • Motive API Camera Calibration
    • Camera SDK
      • Camera SDK Classes
        • Class: cCameraGroupFilterSettings
        • Class: cCameraGroupMarkerSizeSettings
        • Class: cCameraGroupPointCloudSettings
        • Class: cCameraModule
        • Class: cRigidBodySettings
        • Class: cRigidBodySolutionTest
        • Class: cTTAPIListener
        • Class: cUID
  • MARKER SETS
    • Full Body
      • Baseline (37)
      • Baseline + Hinged Toe (41)
      • Baseline + Hinged Toe, with Headband (41)
      • Baseline + 13 Additional Markers (50)
      • Biomech (57)
      • Conventional (39)
    • Full Body + Fingers
      • Baseline + Hinged Toe + Fingers (49)
      • Baseline + 11 Additional Markers + Fingers (54)
      • Manus Glove Setup
    • Upper
      • Baseline Upper (25)
      • Baseline Upper Body + Fingers (33)
      • Conventional Upper (27)
    • Lower
      • Baseline Lower (20)
      • Helen Hayes Lower (19)
      • Conventional Lower (16)
    • Hand and Fingers
      • Left and Right Hand (11)
      • Active Finger Marker Set
    • Rizzoli Marker Sets
    • Entertainment Marker Sets
    • Rigid Body Skeleton Marker Set
  • GENERAL TROUBLESHOOTING
    • Troubleshooting
    • Running Motive on High DPI Displays
    • Firewall Settings
Powered by GitBook
On this page
  • Overview
  • Requirements
  • Additional Information
  • Active Component Setup
  • 1) Download Active Batch Programmer
  • 2) Check the firmware version and existing configuration
  • 3) Configure the settings in the Active Batch Programmer
  • 4) Connect an active component
  • 5) Disconnect and connect remaining devices
  • Tag Attachment to Tracked Objects
  • Motive Setup
  • IMU's per BaseStation

Was this helpful?

Export as PDF
  1. ACTIVE COMPONENTS
  2. Active Marker Tracking

Active Marker Tracking: IMU Setup

Overview

This page provides instructions on configuring the active components, Active Tags and/or Active Pucks, that are equipped with inertial measurement unit (IMU) sensors. By fusing the optical tracking data of the active markers with the IMU data, Motive can further stabilize the rotational tracking of the Rigid Bodies and accommodate for tiny jitters throughout the tracking. This is recommended for applications where the stability of rotation tracking data is important, including tracking cameras in virtual production applications, tracking drones in low camera-count setups, and more.

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 configured, each Active Base Station can communicate with up to 7 IMU Tags/Pucks.

  • When needed, multiple Base Stations can be plugged into the same camera network; as long as they are communicating through a separate channel.

  • 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.

Active Component Setup

For the IMU data to be used for tracking in Motive, unique Uplink IDs must be assigned onto each IMU Tag or Puck using the active batch programmer program. Then, the Uplink IDs will need to be inputted under the properties of the corresponding Rigid Bodies in Motive. Please follow the steps below:

1) Download Active Batch Programmer

Use the following link to download the batch programmer used for 2.x firmware. Once downloaded, unzip the downloaded file and launch the EXE file.

  • Batch Programmer Download:

2) Check the firmware version and existing configuration

Before setting up the components, we will want to check the existing configurations on the Base Station, Tags, and/or Pucks. To check this, enable the ‘’Read-Only Mode’’ check box at the bottom-left corner of the active batch programmer, and then connect the devices one at a time via USB. Each time a new active component is detected, existing configurations including the firmware version will get listed under the Log section. If any of the settings do not meet the below requirements, you can re-configure them in the next step.

Important

When checking the configuration, make sure the Read-Only Mode is enabled. If not, the active batch programmer will upload the settings onto the new Tags that are newly detected by the computer. This could reset the existing configuration that is already on the device.

Firmware Version

RF Channel

Please make sure that all of the active components are communicating through the same channel. Check this and take a note of the channel value as this will also need to be inputted into Motive for IMU data. The RF channel can be set anywhere between 11-26.

Label

The Labels are active IDs assigned to each marker, and it's important that there are no overlapping labels, or IDs, assigned to the same batch of active Tags/Pucks. This setting is applicable to Active Tags/Pucks only.

After checking the settings, you can unplug the device and connect the next one to check the settings.

3) Configure the settings in the Active Batch Programmer

Now that we understand the existing configurations and what needs to be changed, we can configure the active components. To do this, disable the Read-Only Mode in the batch programmer, and settings configured in the IMU batch programmer will get applied to each newly connected device. Please note that this could also reset the existing configuration, thus, make sure to configure only the settings that need to be changed.

Configure Uplink ID

For IMU Tags or Pucks, unique Uplink IDs need to be assigned for each of them. For doing this, simply check the box next to the Uplink ID whenever we are configuring IMU Tags or Pucks.

RF Channel/Label

Uncheck the boxes next to "Set marker labels" and "Set radio options" unless they also need to be reconfigured.

All of the Tags/Pucks are pre-configured for every set of devices that gets shipped out 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 want to reconfigure the active components are: 1) When you have purchased new Tags/Pucks to add to the system from the previous order. 2) When there is a need to change the RF communication channel to avoid interferences.

In cases where marker labels or RF channels need to be reconfigured, enable the box next to the corresponding setting in the batch programmer. DO NOT check the box unless the settings need to be changed. When reconfiguring marker labels, ALL of the Tags and Pucks will need to be reconfigured at once, so that the labels do not overlap with other components in the system.

4) Connect an active component

Once we have configured the settings in the batch programmer, connect Active Tags or Pucks one at a time and the programmer will apply the configured settings to the newly connected device, and it will also make sure that the IDs do not overlap in the same batch. Once the settings get applied the details will get listed under the Log.

It’s recommended to note the assigned Uplink IDs for each Tag/Puck so that we can track down the settings easily when needed.

5) Disconnect and connect remaining devices

Once a device is configured, disconnect 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.

Tag Attachment to Tracked Objects

When using an IMU Active Tag to create a custom Rigid Body, please make sure both the PCB board of the tag and the LEDs are securely attached and rigidly constrained to the object. The IMU sensor fusion will not work correctly if either the markers or the tag are not secured to the rigid object.

Motive Setup

Now that each of the IMU Tags/Pucks has been assigned with an Uplink ID, the next step is to input this ID into the properties of the corresponding Rigid Bodies in Motive. Also, the RF channel configured for each active component will need to be inputted as well. Follow the below steps to assign Active Tag ID and Active RF Channel property for each Rigid Body:

1) Launch Motive

Make sure the configured Active Base Station is connected to the camera system and launch Motive.

2) Power the IMU Tag/Puck

Click the power button on the Tag/Puck to start the device. When the Tag/Puck first initializes, the status LEDs will start blink in red and orange rapidly. This indicates that the IMU sensor is attempting to initialize. At this stage, keep the IMU Tag/Puck stationary until the status LED blinks in green indicating that it has completed the initialization.

Note: Do not hold down on the power button when powering up the Tag/Puck as it will put the device into a boot mode. When in boot mode, it will not track in Motive and two of the LEDs will light up in orange. If this happens, hold down on the power button again to turn off the Tag/Puck and restart it with just a single click on the button.

3) Create a Rigid Body

Select the active markers associated with a Tag/Puck and create a Rigid Body.

4) Access advanced rigid properties

5) Input IMU Properties: Active Tag ID and RF Channel

Scroll down to find the IMU section and input the "Uplink ID" value for the corresponding Tag/Puck into. Additionally, input the "RF Channel" used the the corresponding Base Station. Once this is completed the Rigid Body should have the correct properties set to use the IMU in the tag. You can also adjust the Sensor Fusion property to balance the contribution between optical tracking data and IMU data for the Rigid Body solve.

6) Check the status

At this point, the IMU Tags and Pucks are ready to be used. The color of the Rigid Body indicates the status of the IMU data stream.

Connected
Calibrating
No Incoming Data
Status

iewport

When the color of Rigid Body is the same as the assigned Rigid Body color, it indicates Motive is connected to the IMU and receiving data.

If the color is orange, it indicate the IMU is attempting to calibrate. Slowly rotate the object until the IMU finishes calibrating.

If the color is red, it indicates the Rigid Body is configured for receiving IMU data, but no data is coming through the designated RF channel. Make sure Active Tag ID and RF channel values mat the configuration on the active Tag/Puck.

Description

Confirm IMU Tracking

It may be helpful to double-check to confirm that IMU is working properly. To do this, access the properties of the IMU Rigid Body, set the Min Marker Count Rigid Body property to 2, and set the Tracking Algorithm to Marker Based. Then, cover up all of the active markers on the Tag/Puck except for two, and make sure that Motive is still able to track the Rigid Body rotation.

IMU's per BaseStation

BaseStations are only capable of hosting a finite number of IMUs based on the speed of the framerate in Motive.

You can, however, have an unlimited number of active tags associated with a BaseStation if you are not using the IMU data.

Below is a table depicting how many IMUs are able to connect per a single BaseStation at varying framerates. BaseStations have 16 radio frequency (RF) channels for use (11-26). Therefore, when adding more than one BaseStation to a system, the IMU count is simply the number of IMUs below multiplied by the number of BaseStations up to 16. For example, if you have 4 BaseStations and you're running at 90Hz, the number of allowable IMUs would be 60 (15*4=60).

PreviousActive Finger Marker SetNextSYNCHRONIZATION

Last updated 2 years ago

Was this helpful?

In order to use IMU Tags/Pucks, all of the active components must have firmware version 2.2.x or above installed. Please check the firmware version on the active components. If the installed firmware is an older version, please for assistance with upgrading the firmware.

Open the and select the Rigid Body. Reveal the advanced properties by clicking on "..." menu at the top-right and selecting Show Advanced.

OptiTrack Downloads: Active Batch Programmer
contact us
Properties pane