Main Page → AMTI Force Plate Setup
This page provides instructions on integrating an AMTI Force plate system with an OptiTrack motion capture system.
When a motion capture system is used in conjunction with force plates, they work together as an efficient tool for various research applications including biomechanical analysis, clinical gait analysis, physiology research, sports performance research, and many more. An OptiTrack motion capture system can synchronize with force plates to obtain both kinematic and kinetic measurements. Note that force plate integration is supported only with a Prime camera system using the eSync synchronization hub. This page provides quick guidelines for setting up and configuring force plates — with digital outputs — along with the OptiTrack motion capture system.
For detailed information on specifications and configurations on the force plates, refer to the documentation provided by the force plate manufacturer.
In order to integrate force plate systems with Motive, you will need to setup the required drivers and plugins. Motive installer is packaged with the Peripheral Device module which can be added. During the Motive installation, a list of program features will be shown in the Custom Setup section. Here, change the setting for the Peripheral Device module, as shown in the below image, so that the module is installed along with Motive Files.
Note : Even if you are not using NI-DAQ, it is still necessary to install NI-DAQmx drivers that come up next in the installer.
Installation Note: For integration into Motive, the NI-DAQmx 15.1.1 or later runtime driver must be installed. If you are already using an older version of the NI-DAQmx runtime and Motive is having problems recognizing the connected device, update the driver or uninstall and re-install the packaged version of the driver before contacting Support. In Motive, you can inspect device connection status via the Status Log panel which can be accessed under the View tab in Motive.
Notes on NI-DAQmx version 19.x: There is a known issue with the latest NI-DAQmx version (19.x) where it crashes Motive on startup. If you have this version of the driver installed, please reinstall with the recommended version (15.1.1) provided with the Motive installer.
If the hardware and software for the force plates are configured and successfully recognized, Motive will list out the detected force plates with number labels (1, 2, etc..). Motive will notify you of incorrect or nonexistent force plate calibration files. When the devices are successfully instantiated in Motive, the Status Log will indicate that the device has been created and loaded.
Calibrate the capture volume as normal to get the orientation of the cameras (see the Quick Start Guide or Calibration page for more information). The position of the force plate is about the center of the volume, and when you recalibrate or reset the ground plane, you will need to also realign the position of your force plates for best results.
On the CS-400 calibration square, pull the force plate alignment tabs out and put the force plate leveling jigs at the bottom. The leveling jigs align the calibration square to the surface of your force plate. The alignment tabs allow you to put the CS-400 flush against the sides of your force plate giving the most accurate alignment.
AMTI Force Plates
AMTI force plates use the right-hand system. The long arm of CS-400 will define the Y axis, and the short arm will define the X axis of the force plate. Accordingly, Z axis is directed downwards for measuring the vertical force.
To view and confirm the live force plate data, open the editor from the Timeline Pane. Then, open the Project Pane (or Cameras Pane) and select one of the force plates. A list of available channels will appear under each force plate instance. Here, you can confirm that your force plates are working properly. Select Fx, Fy, Fz, Mx, My, or Mz channels to view the live force plate data from the timeline. Multiple channels can be displayed at once. When both reconstructed markers and force plate channels are selected, the force plot will be sub-sampled in order to be plotted along with trajectory data.
If you wish to double check the force plate position calibration, you may create a long trackable rigid body and use it to apply force against force plate. If the force plate location is precisely calibrated in Motive, the force vector will go right through the rigid body.
After these configurations have been applied, the force plate data and the motion capture data will be synchronized via triggering. The settings should look similar to the following:
If you are using an Ethernet system without an eSync, ignore the synchronization configuration options. From the Cameras Pane, make sure that that the force plate sampling rate is a multiple of the tracking frames per second (fps), ex 100fps and 1000fps. Motive will alert you if the sampling rates for cameras and force plates disagree.
Without a master synchronization device, recording for the camera system and the force plates will not be triggered exactly at the same time. This can cause problems for longer takes because the sampling timing for mocap data and the force plate data will eventually deviate from each other. If you want your system to be timed perfectly, we recommend synchronizing through the eSync 2.
When the force plate sampling rate is not set to an integer multiple of the camera frame rate, force plate data may record improperly; which is shown in the following screenshot.
Before you start recording, you may want to validate that the camera and force plate data are in sync. There are some tests you can do to examine this.
First method is to record dropping a retroreflective ball/marker onto the platform few times. The bouncing ball produces a sharp transition when it hits the surface of the platform, and it make the data more obvious for validating the synchronization. Alternately, you can attach a marker on tip of the foot and step on and off the force plate. Make sure that your toe — closest to the marker — strikes the platform first, otherwise the data will seem off even when it is not. You can then compare when the motion capture data says the ball or foot made contact with the force plate to when the force plate says it made contact. ↑
The following is a example of validating good synchronizations using these methods:
The following is a example of validating bad synchronizations using these methods:
We recommend the following programs for analyzing exported data in biomechanics applications:
Since Motive uses a different coordinate system than the system used in common biomechanics applications, it is necessary to modify the coordinate axis to a compatible convention in the C3D exporter settings. For biomechanics applications using z-up right-handed convention (e.g. Visual3D), the following changes must be made under the custom axis.
This will convert the coordinate axis of the exported data so that the x-axis represents the anteroposterior axis (left/right), the y-axis represents the mediolateral axis (front/back), and the z-axis represents the longitudinal axis (up/down).
Force plate data and the tracking data can be exported into CSV files as well. When a Take file is exported into a CSV file. Separate CSV files will be saved for each force plate and it will contain the force, moment, and center of pressure data. Exported CSV file can be imported for analysis.
To stream tracking data along with the force plate data, open the Data Streaming Pane and check the Broadcast Frame Data, and make sure that you are not streaming over the camera network. Read more about streaming from the Data Streaming workflow page.
Motive can stream the tracking data and the force plate data into various applications — including Matlab — using NatNet Streaming protocol. Find more about NatNet streaming from the User's Guide included in the download.
Number of Force Plates