IMU Sensor Fusion
Last updated
Last updated
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 each indicator light.
Select the markers from the active device and create a Rigid Body Asset.
It is highly recommended to make sure all 8 markers can be tracked with minimal occlusions for the best results when pairing and aligning the Rigid Body to the IMU.
Right click on the Rigid Body in the Assets pane and select Active Tags -> Auto-Configure Active Tag.
Move the CinePuck or IMU Active Puck slowly around at least 3 axes until you see 'IMU Working [Good Optical] %'. You have now successfully paired and aligned your CinePuck with your Rigid Body.
Attach your CinePuck to your cinema camera or your regular IMU Active Puck to an object of your choosing.
Enjoy your sensor fused Puck for seamless and robust tracking.
Motive can automatically recognize a CinePuck and after pairing and aligning a Rigid Body to an IMU Tag, will change the name of the Rigid Body to CinePuck_G### along with its marker constraints.
The options below can be found both by right clicking a Rigid Body in the Assets pane or by selecting the Rigid Body in the 3D Viewport and right clicking to open the context menu.
The Devices pane has a few redundant options as well under the Active Tag section.
This option will pair and align the Rigid Body to the IMU Tag all in one go. This is the quickest and most preferable option when first getting started.
This will set the Puck to search for an IMU pair. Once paired, this will be indicated in the 3D Viewport IMU visual as 'IMU Paired', 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.
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.
This allows you to manually align your Tag to your Rigid Body after you have paired.
This allows you to remove alignment from your Rigid Body while still paired to the IMU.
If you would like your Pivot orientation to reflect the orientation of your IMU (internal), you can select Orient Pivot to IMU. Motive will recognize the physical orientation of the IMU within the Puck and adjust the Rigid Body pivot bone appropriately.
From the existing Assets pane, you can right click to add columns. For this IMU workflow, you can select Active Tag. The Active Tag column will display either the Paired or fully Paired and Aligned IMU Tag to the Rigid Body Asset. If the Rigid Body is non IMU or is not yet Paired or Aligned, this column will display 'None'.
In the 3D viewport, just like Labels, you can view the status of the Rigid Body.
After either Auto or Manually pairing, the status above your Rigid Body will report 'Searching for IMU Pair'. After moving and rotating your Puck around this should change to 'IMU Paired'.
If it does not, this could mean that an IMU device is not present or is not being recognized. Please check the Devices pane to see if the IMU Device is populated in the table with its Uplink ID. If you are unable to find the Device, please check your RF Channel and Uplink ID using the Active Batch Programmer.
After your Rigid Body has successfully paired with the IMU Tag, the status will change to IMU Paired [Optical] %.
Once you have either Auto-Configured or Manually Paired and Aligned an Asset, you should see 'IMU Working' appear over your Asset in the 3D viewport.
If you're having issues seeing 'IMU Working,' you may need to rotate the Puck in more axes or try Pairing again and Re-align.
Good Optical: Denotes most markers can be seen and tracked within the volume.
Optical:
Denotes that the minimum markers can be seen and tracked within the volume.
No Optical:
Denotes either below the minimum or no markers can be seen and tracked within the volume.
%:
Percentages denote the amount of IMU packets that an IMU Tag is successfully delivering for every 100 frames. 100% indicates all packets are going through; 80% indicates 20% of IMU packets were dropped.
Tags that have come into Motive can be viewed in the Devices pane under the Active Tag section. Please see above for context menu options for this pane.
By default the Name is set to 'Tag XX:XX'. The XX:XX format denotes the RF Channel and Uplink ID respectively. i.e. Tag 20:00 is on RF Channel 20 and has an Uplink ID of 0.
When an Asset is paired, this will show the Rigid Body name that will be the same as shown in the Assets pane.
The Aligned column will show the Aligned status of the Active Tag.
Properties for both the IMU tag by itself (when selected from Devices pane) and for the sensor fused Rigid Body (when selecting the Rigid Body from either the Assets pane or 3D Viewport) can be found in the Properties pane.
The Active Tag does not have any editable properties but does display a few Details and General properties.
Rigid Body properties that pertain to IMU specific workflows can be found under the Visuals section.
This dropdown allows you to choose how you would like the IMU State to appear in the 3D viewport.
None - No visual in the viewport
Text - Text visual in viewport
Icon - Icon only visual in viewport
After pairing a Rigid Body to an IMU Puck, an IMU Constraint with IMU information will be created for the Rigid Body. This along with an update to the names of Constraints based on what Puck type is identified by Motive.
As stated above, the IMU Constraint is created when the IMU Tag is paired to a Rigid Body. This not only stores the information after pairing, but also alignment information when the Align action is performed by either Auto-Configure Active Tag or by Manually Aligning.
If this Constraint is removed, this will remove the pair and/or align information from the Rigid Body. You will need to perform another pair and align to re-adhere the sensor fusion data to the Rigid Body once more.
The Info pane Active Debugging is used as a troubleshooting tool to see the amount of IMU data packets dropped along with the largest gap between IMU data packets being sent.
When either column exceeds the Maximum settings, the text will turn magenta depending on the logic setup in the Maximum settings at the bottom of the pane.
This column denotes the number of IMU packet drops that an IMU Tag is encountering over 60 frames.
Max Gap Size denotes the number of frames between IMU data packets sent where the IMU packets were dropped. i.e. 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 288 frames where the IMU packets were either not sent or received.
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.
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.
BaseStations have 16 radio frequency (RF) channels available for use (11-26). When adding more than one BaseStation to a system, the IMU count is simply the maximum number of IMUs multiplied by the number of BaseStations (up to 16). For example, in a system with 4 BaseStations running at 90Hz and a divisor rate of 3, the number of allowable IMUs would be 216 (54*4=216).
If the tag is unpaired, the circle x icon will appear.
If the tag is pairing, the circle with the wave icon will appear.
If the tag is paired, the green circle with green check icon will appear.
| Frame Rate | Divisor Rate 1 | Divisor Rate 2 | Divisor Rate 3 |
|---|---|---|---|
| Color | Description | Troubleshooting |
|---|---|---|
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
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
