Differences

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

--- visual3d:documentation:third-party:xsens:xsens [2024/10/24 14:22] – [Processing Xsens Data] wikisysop
+++ visual3d:documentation:third-party:xsens:xsens [2024/10/24 14:25] (current) – wikisysop
@@ Line 36: / Line 36: @@
 {{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.
@@ Line 58: / 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.)
-====Flexible Implementation====
+==== 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]].\\
+=====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).
@@ Line 72: / Line 80: @@
 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 ====