visual3d:documentation:third-party:xsens:xsens
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
visual3d:documentation:third-party:xsens:xsens [2024/10/24 14:06] – wikisysop | visual3d:documentation:third-party:xsens:xsens [2024/10/24 14:25] (current) – wikisysop | ||
---|---|---|---|
Line 16: | Line 16: | ||
orientation, | orientation, | ||
- | =====Model Pose (position and orientation)===== | + | ===== Opening MVNX Files ===== |
- | There are two implementations of a Visual3D model for mvnx data. As users will likely want to use the same implementation each time an mvnx file is loaded, | + | MVNX files can be opened by going to File -> Open in Visual3D. |
- | the selection of models | + | |
- | {{FileOpenOptions.png}} | + | They can also be opened using the File_Open pipeline command. |
+ | |||
+ | |||
+ | =====Model Pose===== | ||
+ | |||
+ | Model Pose (position and orientation) of the multi-body model | ||
- | Legacy Mvnx Implementation | ||
Visual computes the model Pose using a "Link Model" that matches the Xsens link model. | Visual computes the model Pose using a "Link Model" that matches the Xsens link model. | ||
As of Visual3D version 2024.05.2, the user can choose one of two implementations of a model based on the mvnx file. | As of Visual3D version 2024.05.2, the user can choose one of two implementations of a model based on the mvnx file. | ||
- | To simplify the process | + | There are two implementations of a Visual3D model for mvnx data. As users will likely want to use the same implementation |
- | the user can specify which model should | + | the selection of models |
+ | |||
+ | {{FileOpenOptions.png}} | ||
+ | |||
+ | =====Legacy Implementation===== | ||
+ | When the file is opened, the user will be prompted for all the necessary model metrics to create the model. | ||
The model' | The model' | ||
Line 50: | 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.) | ||
- | === Download Files === | + | ==== Prop Sensors ==== |
+ | |||
+ | |||
+ | Visual3Dv2020.## | ||
+ | |||
+ | [[Visual3D: | ||
+ | |||
+ | |||
+ | =====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, | ||
+ | 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/ | ||
+ | |||
+ | |||
+ | |||
+ | ==== Download Files ==== | ||
* [[https:// | * [[https:// | ||
Line 80: | Line 119: | ||
- | ===== Opening MVNX Files ===== | ||
- | |||
- | As of Visual3Dv6, MVNX files can be opened by going to File -> Open in Visual3D. | ||
- | |||
- | 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. | ||
- | |||
- | ===== Processing Xsens Data ===== | ||
- | |||
- | ==== Trunk Graphic ==== | ||
- | |||
- | The default Xsens model points to the [[https:// | ||
- | |||
- | This means if the graphic does not appear in your model, you can download the graphic [[https:// | ||
- | |||
- | ==== Prop Sensors ==== | ||
- | |||
- | \\ | ||
- | Visual3Dv2020.## | ||
- | \\ | ||
- | [[Visual3D: | ||
visual3d/documentation/third-party/xsens/xsens.1729778761.txt.gz · Last modified: 2024/10/24 14:06 by wikisysop