Force Platforms

From Software Product Documentation
Revision as of 15:21, 11 December 2019 by Wikisysop (talk | contribs) (→‎Filtering Force Platform Data)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
Language:  English  • français • italiano • português • español 

Force Platforms are commonly used for biomechanical analyses. So common that there is a fairly laissez faire attitude towards force platform data. Many users don't realize the complexity of computing the ground reaction force vector in the laboratory coordinate system (where it is actually needed for Inverse Dynamics calculations), and, therefore don't take the time that is required to ensure that the data are correct.

Issues related to force platform coordinates are described below, but we feel it is necessary to emphasize one topic above all others.

The location of the ground reaction force relative to the ankle is the biggest source of error in Inverse Dynamics analysis of gait. Surprisingly few laboratories, however, undertake the challenge of verifying the location of the force platforms within the 3D MoCap volume (see our CalTester Section), or verifying the scaling and offset parameters on the ANALOG signals. This reluctance to perform a straightforward test that takes little time continues to surprise us at C-Motion.


This topic refers to the representation of external forces and how these forces are included in the inverse dynamics calculations.

If you are searching for the computation of Forces and Moments, see the section on Inverse Dynamics.

The traditional force recorded for inverse dynamics of gait analysis is derived from a Force Platform.

Tutorial: Force Platforms

Force Structures

In recent years force sensors have been included in a variety of structures, such as Steps and Treadmills. Visual3D treats these forces as Force Structures, which are really structures attached to force platforms or to contiguous force platforms spaced in a grid.

Force Assignment

In order to include a force in the Inverse Dynamics calculations it is necessary to assign the force to a segment. In many cases, force platforms or force structures, Visual3D attempts to assign the forces automatically. Custom forces must be assigned manually.

Using the Force Assignments the user can specify a Custom Force.

Filtering Force Platform Data

The Ground Reaction Force is represented by 3 vectors: Force, Center of Pressure, and Free Moment. It is computed from the ANALOG signals recorded from the force platform, the calculations specified by the force platform manufacturer, and the location of the force platform in the laboratory. The Ground Reaction Force signal is stored in the FORCE folder in the Visual3D data tree. The Center of Pressure signal is stored in the COFP folder in the Visual3D data tree. The Free Moment signal is stored in the FREEMOMENT folder in the Visual3D data tree.

Here are some tips regarding filtering of force platform data:

  • If you filter the FORCE signals, you should filter the COFP and FREEMOMENT.
  • If you aren't using the COFP and FREEMOMENT for any calculations, however, it probably doesn't matter
  • If you filter the ANALOG signals and select the option to use PROCESSED ANALOGS (see section below), you don't need to filter the forces at all.
Our recommendation is to filter the ANALOG signals, and not to process the FORCE, COFP, and FREEMOMENT signals

Using Processed Forces

Under the settings menu there is an option

Use Processed Targets for Model/Segment/LinkModelBased items

If this is checked, Visual3D computes Kinetics and Kinematics using the data in the PROCESSED folder of TARGETS, FORCE, COFP, and FREEMOMENT.

If the PROCESSED folder does not exist, the ORIGINAL folder is used.

We do not recommend filtering the FORCE, COFP, and FREEMOMENT signals.
See next section for filtering the ANALOG signals

Using Processed Analogs to Compute Forces

Under the settings menu there is an option

Use Processed Anglogs for Ground Reaction Force Calculations

If this is checked, Visual3D computes FORCE, COFP, and FREEMOMENT from the PROCESSED ANALOG signals.

If the PROCESSED folder does not exist, the ORIGINAL folder is used.

Modify_Force_Platform_Parameters

Modify_Force_Structure_Parameters

Transforming from a sensor coordinate system to the LAB

FP Center of Pressure distance to Segment

Automatic force assignments are created based on the distance between the segment's center of mass and the force plate center of pressure. The distance between the segment and the center of pressure can be modified by going to Force - > Modify FP Center of Pressure distance to Segment.

The default value of 0.2m has proven to be an acceptable value, so users should refrain from modifying this value unless they have a very good reason.

Minimum_Force

Under the Visual3D Force Menu is an option to set a threshold for force platform/structure data.

Applying a threshold value to the force signals.

If the computed force is less than the minimum force, the force and freemoment are set to zero, the COP is set to DATA_NOT_FOUND

This value can also be set using the pipeline command Set_Force_Platform_Threshold. This command is listed under the Force category of the pipeline commands.

This threshold value is used to remove noise from the force signals. Often for instrumented treadmills this value must be set higher than for overground gait trials.

Force Platform Types

C3D_Parameters

FP_TYPE

FP_USED

FP_ZERO

FP_ZEROS

FP_ORIGIN

FP_CHANNELS

FP_CORNERS

Retrieved from ""