HAS-Motion Software Documentation

User Tools

Site Tools

You are here: Main Page » visual3d » documentation » third-party » XSens
visual3d:documentation:third-party:xsens:xsens

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
visual3d:documentation:third-party:xsens:xsens [2024/10/24 14:12] – wikisysopvisual3d:documentation:third-party:xsens:xsens [2024/10/24 14:25] (current) – wikisysop
Line 21: Line 21:
  
 They can also be opened using the File_Open pipeline command.  They can also be opened using the File_Open pipeline command. 
-When the file is opened, the user will be prompted for all the necessary model metrics to create the model.+
  
 =====Model Pose===== =====Model Pose=====
Line 36: Line 36:
 {{FileOpenOptions.png}} {{FileOpenOptions.png}}
  
-====Legacy Implementation====+=====Legacy Implementation===== 
 + 
 +When the file is opened, the user will be prompted for all the necessary model metrics to create the model.
  
 The model's root, which is the pelvis, has both an orientation and a position (all 6 degrees of freedom). Visual3D then work through model's chain (assuming a ball and socket at all joints) using the .mvnx segment orienation variables to compute the joint angles. This give us the position and orientation (POSE) of the entire model. The model's root, which is the pelvis, has both an orientation and a position (all 6 degrees of freedom). Visual3D then work through model's chain (assuming a ball and socket at all joints) using the .mvnx segment orienation variables to compute the joint angles. This give us the position and orientation (POSE) of the entire model.
Line 56: Line 58:
 If you take the first derivative of the ProxEndPos KINETIC_KINEMATIC variable it will not exactly equal the ProxEndVel KINETIC_KINEMATIC variable which come from the .mvnx Translational Velocity of the Origin. The idea is to use the Xsens data for velocity, acceleration and kinetic calculations even if it is slightly inconsistent with the derivative of the Pose data. (This data is assumed to be more accurate measure of velocity and acceleration then taking the derivatives of which amplifies noise.) If you take the first derivative of the ProxEndPos KINETIC_KINEMATIC variable it will not exactly equal the ProxEndVel KINETIC_KINEMATIC variable which come from the .mvnx Translational Velocity of the Origin. The idea is to use the Xsens data for velocity, acceleration and kinetic calculations even if it is slightly inconsistent with the derivative of the Pose data. (This data is assumed to be more accurate measure of velocity and acceleration then taking the derivatives of which amplifies noise.)
  
-====Flexible Implementation====+==== Prop Sensors ====
  
-=== Download Files ===+ 
 +Visual3Dv2020.## supports reading MVNX files with one prop sensor. The sensor will be loaded automatically as a segment (ex. PR1). If more props are required to process your data, please contact C-Motion. When using an Xsens prop in Visual3D, all information is loaded automatically and no further steps are required. A sample MVNX file with a prop can be downloaded **[[https://www.has-motion.com/download/examples/Xsens/Xsens_Prop_Example.zip|here]].**\\ 
 + 
 +[[Visual3D:Documentation:Third-Party:XSens:XSens_Prop|This tutorial explains how to adjust the location of the prop segment and assign a graphics object to the prop using a script]].\\ 
 + 
 + 
 +=====Flexible Implementation===== 
 + 
 +Unlike the legacy implementation when the file is opened, the user will not be prompted for the anthropometric data (i.e. mass and moment of inertia).  
 +Instead default values are used, which can later be modified by the user. 
 +Our thinking was that users that are only interested in kinematics do not want to be prompted for unnecessary information every time a file is loaded. 
 + 
 +In this implementation, the information in the mvnx file is used to create 4x4 ROTATION signals similar to the output from markerless tracking systems like Theia3D, and Kinatrax, 
 +and is consistent with the ROTATION signals created from bvh files (Fujitsu implementation of bvh). 
 + 
 +Using model based information in the mvnx file, a model is created automatically from the ROTATION signals. 
 + 
 +In this implementation the Kinetic_Kinematic variables are created consistently with the other ROTATION based models. 
 + 
 +Unlike the legacy implementation the segment pose is explicitly defined. 
 + 
 +==== Prop Sensors ==== 
 + 
 +If a prop sensor exists in the mvnx file, a ROTATION matrix is created form the prop pose.  
 + 
 +The user can create/modify a segment definition using this pose 
 + 
 + 
 + 
 +==== Download Files ====
  
   * [[https://www.has-motion.com/download/examples/Xsens/MVNX_Files.zip|Sample MVNX files]]   * [[https://www.has-motion.com/download/examples/Xsens/MVNX_Files.zip|Sample MVNX files]]
Line 88: Line 119:
  
  
- 
-===== Processing Xsens Data ===== 
- 
-==== Prop Sensors ==== 
- 
-\\ 
-Visual3Dv2020.## supports reading MVNX files with one prop sensor. The sensor will be loaded automatically as a segment (ex. PR1). If more props are required to process your data, please contact C-Motion. When using an Xsens prop in Visual3D, all information is loaded automatically and no further steps are required. A sample MVNX file with a prop can be downloaded **[[https://www.has-motion.com/download/examples/Xsens/Xsens_Prop_Example.zip|here]].**\\ 
-\\ 
-[[Visual3D:Documentation:Third-Party:XSens:XSens_Prop|This tutorial explains how to adjust the location of the prop segment and assign a graphics object to the prop using a script]].\\ 
  
  
  
  
visual3d/documentation/third-party/xsens/xsens.1729779175.txt.gz · Last modified: 2024/10/24 14:12 by wikisysop