visual3d_partner_integrations
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
visual3d_partner_integrations [2025/09/18 15:27] – [Jiku] wikisysop | visual3d_partner_integrations [2025/09/24 14:29] (current) – [PhaseSpace] wikisysop | ||
---|---|---|---|
Line 19: | Line 19: | ||
+ | ====Vicon==== | ||
+ | [[https:// | ||
+ | More on Vicon can be found on the, [[visual3d: | ||
+ | ^Vicon Plug-Ins^ | ||
+ | |[[visual3d: | ||
+ | |[[visual3d: | ||
+ | |[[visual3d: | ||
- | ====Vicon==== | + | ^Vicon Nexus^ |
+ | |[[visual3d: | ||
+ | ^Vicon' | ||
+ | |[[visual3d: | ||
+ | |[[visual3d: | ||
+ | |[[visual3d: | ||
=====Motion Capture Systems===== | =====Motion Capture Systems===== | ||
====BTS==== | ====BTS==== | ||
Line 73: | Line 85: | ||
====PhaseSpace==== | ====PhaseSpace==== | ||
- | [[https:// | + | [[https:// |
====Jiku==== | ====Jiku==== | ||
Line 96: | Line 108: | ||
Some force platforms are capable of moving during a trial. However, the C3D file format is designed to only accommodate static force platforms, making it difficult to incorporate dynamic platforms. This page provides guidance on how to handle a moving force platform within Visual3D, see here [[visual3d: | Some force platforms are capable of moving during a trial. However, the C3D file format is designed to only accommodate static force platforms, making it difficult to incorporate dynamic platforms. This page provides guidance on how to handle a moving force platform within Visual3D, see here [[visual3d: | ||
- | |||
- | |||
- | |||
====AMTI==== | ====AMTI==== | ||
- | [[https:// | + | [[https:// |
AMTI's data acquisition software also supports direct export of raw 3D force and moment data (Fx, Fy, Fz, Mx, My, Mz per plate) as a comma-separated .txt file. These files can be imported into Visual3D using the pipeline command [[visual3d: | AMTI's data acquisition software also supports direct export of raw 3D force and moment data (Fx, Fy, Fz, Mx, My, Mz per plate) as a comma-separated .txt file. These files can be imported into Visual3D using the pipeline command [[visual3d: | ||
In most workflows, motion capture software works in tandem with force plates, allowing for synchronized data collection and export of force signals within the C3D file, which can simplify the analysis process in Visual3D. | In most workflows, motion capture software works in tandem with force plates, allowing for synchronized data collection and export of force signals within the C3D file, which can simplify the analysis process in Visual3D. | ||
+ | |||
====Bertec==== | ====Bertec==== | ||
[[https:// | [[https:// | ||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
Line 145: | Line 148: | ||
* [[Visual3D: | * [[Visual3D: | ||
- | Note: To import EMG signals into a motion C3D file using [[Visual3D: | + | Note: To import EMG signals into a motion C3D file using [[Visual3D: |
====Delsys==== | ====Delsys==== | ||
- | [[https:// | + | [[https:// |
Visual3D has the following pipeline command that could be used to import EMG signals [[visual3d: | Visual3D has the following pipeline command that could be used to import EMG signals [[visual3d: | ||
Line 161: | Line 164: | ||
=====IMU===== | =====IMU===== | ||
====Movella (XSens)==== | ====Movella (XSens)==== | ||
- | [[https:// | + | [[https:// |
^Supported Integrations^ | ^Supported Integrations^ | ||
Line 167: | Line 170: | ||
|[[visual3d: | |[[visual3d: | ||
|[[visual3d: | |[[visual3d: | ||
- | |||
- | |||
- | |||
- | |||
====AiQ Synertial==== | ====AiQ Synertial==== | ||
+ | [[https:// | ||
Line 189: | Line 188: | ||
[11] [[https:// | [11] [[https:// | ||
[12] [[https:// | [12] [[https:// | ||
+ | [13] [[https:// | ||
+ | [14] [[https:// | ||
visual3d_partner_integrations.1758209228.txt.gz · Last modified: 2025/09/18 15:27 by wikisysop