IMU Sensor Fusion
Last updated
Was this helpful?
v3.2
Last updated
Was this helpful?
An Inertial Measurement Unit (IMU) communicates coordinate data to Motive either through an Ethernet cable or through a connected BaseStation. When connected to an Active device containing an Inertial Measurement Unit (IMU), Motive is able to fuse the inertial and optical sources of data to produce more precise and accurate tracking.
The process of merging the IMU data with the optical data is known as Sensor Fusion.
First and foremost, ensure that your tracking volume is setup with optimal conditions and your Calibration is Exceptional.
Power on either a CinePuck or an Active IMU puck.
Set the puck on a level surface and wait until the puck is finished calculating its bias. See below for a description of the various indicator lights.
We highly recommend ensuring all markers can be tracked with minimal occlusions for the best results when pairing and aligning the Rigid Body to the IMU.
The Active Tag is displayed in the Devices pane. When selected, the tag's properties are visible in the Properties pane. These properties are read-only.
Right click the Rigid Body in the Assets pane and select Active Tags -> Auto-Configure Active Tag.
Attach the CinePuck to the cinema camera or the Active Puck to the object to be tracked. The sensor-fused Puck is now available for seamless and robust tracking.
This could mean that an IMU device is not present in the Rigid Body or it is not being recognized.
Check the Devices pane to see if the IMU Device is populated in the table with its Uplink ID.
If the device is not listed, use Active Batch Programmer to check the RF Channel and Uplink ID. If the device is set to the correct RF channel and an IMU does not appear, the active device may not have an IMU.
If the IMU Doesn't Fuse
Try rotating the Puck on more axes.
Check the label above the rigid body asset to see if it is collecting alignment samples. If the number of samples does not increase as you rotate the tracker, the optical data may not be reliable enough to calculate an alignment.
Unpair the IMU and complete the pairing and alignment process again.
Active Tag options are also available by right clicking a Rigid Body in the Viewport:
This option pairs and aligns the Rigid Body to the IMU Tag all at once. This is the recommended method when getting started as it is also the quickest.
Auto-Pair causes Motive to search for an IMU whose movements match the rigid body asset. Rotate the rigid body and Motive will find and pair it to the IMU automatically.
Once paired, this alignment status will be indicated in the 3D Viewport IMU visual. The asset name will display in the Devices pane Active Tag Paired Asset column, and in the Assets pane's Active Tag column.
This will remove a paired Tag from the Rigid Body.
Manually align the Tag to the Rigid Body after pairing. A minimum of 10 alignment samples are required; see the IMU label in the Viewport for the total number of samples currently collected.
Remove alignment from the Rigid Body while still paired to the IMU.
Sets the pivot orientation to reflect the orientation of the IMU (internal). Motive will recognize the physical orientation of the IMU within the Puck and adjust the Rigid Body pivot bone appropriately.
Other options are available by right-clicking the tag in the Devices pane:
Add selected devices to a new or existing group with the Add to Group option.
Removes the selected devices from all groups.
If manually pairing from the Devices pane:
Choose the Rigid Body you would like to pair to the selected Tag in the Devices pane.
If manually pairing from the Assets pane:
Choose the Active Tag you would like to pair to the selected Rigid Body in the Assets pane.
Right click the header of the Assets pane to add columns. For this IMU workflow, we recommend adding the Active Tag column. The Active Tag column will display the status along with the ID of the paired device.
Auto-pairing: This status appears while the auto-pair process is running on the device.
Paired: Indicates that the IMU is paired to the Rigid Body, but sensor fusion has not been performed yet.
Fused: The IMU is paired to the Rigid Body and sensor fusion has been completed.
None: The Rigid Body does not have an IMU or is not yet Paired, this column will display "None."
If the IMU label is enabled in the Rigid Body Properties, the Viewport will display the status of the IMU Sensor Fusion process.
After Auto or Manually pairing, the status label above the Rigid Body will display Rotate to Pair IMU.
Move and rotate the Rigid Body around to complete the alignment. The IMU label will display the status of the alignment as a fraction, i.e. 27/100.
The IMU is now successfully paired and aligned with the Rigid Body.
The Optical status at the end of the label indicates how many of the Rigid Body's markers can be seen and tracked within the volume.
Optical Good: most markers can be seen and tracked.
Optical: the minimum number of markers can be seen and tracked.
No Optical: either fewer than the minimum or no markers can be seen and tracked.
Tags recognized by Motive are listed in the Devices pane under the Active Tag section. Please see the section above for context menu options for this pane.
The Name identifies the type of tag, i.e., AnchorPuck, Wired CinePuck. For wireless devices, the Name is set to Tag ##:##, where the first set of numbers indicates the RF Channel and the second the Uplink ID. For example, Tag 22:02 is on RF Channel 22 and has an Uplink ID of 2.
When an Asset is paired to the Active Tag, this column displays the associated Rigid Body name, as shown in the Assets pane.
The Aligned column will show the Aligned status of the Active Tag.
The amount of time the LEDs are on for each frame. This setting applies only to Wired CinePuck and the Anchor Puck at this time.
This value should be aligned with the exposure of the cameras for maximum brightness.
The active pattern grouping currently applied to the device.
Click any tag in the Devices Pane to display its properties in the Properties pane. In Live mode, these properties can be edited for Wired tags. For wireless devices, these values are read-only.
For wireless devices, the RF Channel and Uplink ID can be changed using Active Batch Programmer.
Rigid Body properties that pertain to IMU specific workflows can be found under the Sensor Fusion section.
Display a label with the status of the Rigid Body's IMU in the 3D Perspective View. If the asset Label is enabled, the IMU state is appended to the asset name.
None - No visual is displayed.
Text - Descriptive text provides detailed information about the IMU state.
Icon - An icon-only visual is used.
The text label includes the following information:
Tag Name.
The status of Sensor Fusion:
Rotate to Align (##/100): this status indicates that more rotations are required to align the IMU with the Rigid Body.
Fused: Sensor Fusion completed successfully.
The minimum number of measurements required for the IMU to auto-align. Higher values may lead to fewer alignment errors, but each new sample will have less of an effect on the estimate than the previous sample.
Determines the rate at which the drift in the IMU data is corrected to optical. Higher values will lead to more responsive turning behavior, but more noise while stationary.
The number of frames over which drift correction can apply.
Determines the angle (in degrees) between the calculated drift correction and the current drift correction that will trigger correction. Impulse correction differs from standard drift correction, causing an immediate correction to optical. This is used primarily to prevent physical impacts to the IMU from causing degraded tracking.
After pairing a Rigid Body to an IMU Puck, an IMU Constraint with IMU information is created for the Rigid Body. The pairing process will also update the Constraint names based on the Puck type identified by Motive.
The IMU Constraint stores the alignment information from when the Align action is performed, using either Auto-Group Active Tag or by Manually Aligning.
Removing this Constraint will remove the pair and/or align information from the Rigid Body. Pair and align the tag again to re-adhere the sensor fusion data to the Rigid Body.
This column denotes the number of IMU packet drops that an IMU Tag encountered over 60 frames.
Max Gap Size is the number of frames between IMU data packets sent where the IMU packets were dropped. For example, in the image above on the left, the maximum gap is a 1 frame gap where IMU packets were either not sent or received. The image on the right has a gap of 3 frames where the IMU packets were either not sent or received.
The difference between the IMU rotation and the optical rotation after alignment. If this value exceeds 1 degree, it may indicate that the IMU and optical have become misaligned and should undergo the alignment process again.
Wireless pucks and CinePucks attach to the camera system using a BaseStation. The number of IMUs that can attach to a BaseStation is determined by the system frame rate and the divisor applied to the BaseStation. The table below shows the IMU maximum for common frame rates with a divisor rate of 1, 2, and in some cases 3.
60
26
54
83
70
22
47
71
80
19
39
62
90
16
36
54
100
14
32
49
110
13
29
44
120
11
26
40
130
10
24
140
9
22
34
150
9
20
160
8
19
30
170
7
17
180
7
16
26
190
6
15
200
6
14
23
210
5
14
220
5
13
21
230
5
12
240
4
11
18
250
4
11
As noted, the table does not include all possible frame rate and divisor combinations. If you are familiar with using Tera Term or PuTTy, you can determine the maximum number of IMUs for any specific frame rate and divisor combination not shown on the table.
Use PuTTy to change the divisor rate on the BaseStation.
Connect an IMU puck to PuTTy.
Attempt to set the ID of the puck to an unrealistically high value. This triggers a warning that includes the current number of slots available for the given frame rate.
Set the IMU puck ID to the highest available slot for the frame rate and confirm that it appears in Motive.
Bottom Right:
Orange
Powered ON and Booting
N/A
Top: Flashing Red/Green
Calculating bias. Please set on level surface.
N/A
Top: Fast flashing Green Bottom Right: Slow flashing Green
Bias has been successfully calculated and Puck is connected to BaseStation
N/A
Top: Solid Red then no light Bottom Right: Slow flashing Green
After powering on, the top light turns a solid red then turns off. This means that it is not paired to a BaseStation. The slow flashing Green indicates that it is still ON.
Please check your RF Channel on both devices to ensure they match.
Top: Solid Green then no light Bottom Right: Slow flashing Green
The puck is disconnected from the BaseStation WHILE powered ON.
Please check your BaseStation and ensure it is powered ON and receiving a signal from the network cable/switch.
Top: Fast Flashing Green Bottom Right: Orange
Battery power is below half.
Please connect device to power or let charge before continuing.
Bottom Right: Flashing Red
Battery is nearly depleted.
Please connect device to power or let charge before continuing.
Bottom Left: Red
Plugged in and charging.
N/A
Select the markers from the active device and create a Rigid Body Asset. Please see the the section of the Builder pane page for further instructions.
Move the active device slowly around at least 3 axes. The status will update in the the Properties pane, and the Alignment status in the Devices pane will display a circled wave: . The IMU label will also display the status in the Viewport.
Continue rotating the active device until the Alignment status in the Devices pane updates to a circled checkmark: . The IMU is now successfully paired and aligned with the Rigid Body.
Click the button at the top of the Devices pane to select from the list of available .
If the tag is unpaired, the circled x icon will appear.
If the tag is aligning with a rigid body, the circle with the wave icon will appear.
If the tag is paired and aligned, the green circle with green check icon will appear.
The tool on the Info pane is a troubleshooting aid for active devices. IMU status information is displayed in gray text when it falls within the user-established parameters set at the bottom of the pane. Magenta text indicates that values exceed the parameters.
