LogoLogo
WebsiteSupportDownloadsForumsQuick LinksContact Us
v2.3
v2.3
  • OptiTrack Support Documentation
  • WHAT'S NEW
    • Unreal Engine: OptiTrack InCamera VFX
  • QUICK START GUIDES
    • Quick Start Guide: Getting Started
    • Quick Start Guide: Precision Capture
    • Quick Start Guide: Tutorial Videos
    • Quick Start Guide: Prime Color Setup
    • Quick Start Guide: Active Marker Tracking
    • Quick Start Guide: Outdoor Tracking Setup
  • HARDWARE
    • Cameras
      • Ethernet Cameras
        • PrimeX 41
        • PrimeX 22
        • PrimeX 13
        • PrimeX 13W
        • SlimX 13
        • Prime Color
      • USB Cameras
        • Slim 3U
        • Flex 13
        • Flex 3
        • V120:Duo
        • V120:Trio
        • V120:Duo and Trio Setup
        • Adjusting Global Origin for Tracking Bars
    • Prepare Setup Area
    • Camera Mount Structures
    • Camera Placement
    • Camera Network Setup
    • Aiming and Focusing
    • Camera Status Indicators
  • MOTIVE
    • Installation and Activation
    • Motive Basics
    • Calibration
      • Continuous Calibration
      • Calibration Squares
    • Markers
    • Assets
      • Gizmo Tool: Translate, Rotate, and Scale
    • Rigid Body Tracking
      • Aligning Rigid Body Pivot Point with a Replicated 3D Model
    • Skeleton Tracking
    • Data Recording
      • Data Types
    • Labeling
    • Data Editing
    • Data Export
      • Data Export: BVH
      • Data Export: C3D
      • Data Export: CSV
      • Data Export: FBX
      • Data Export: TRC
    • Data Streaming
    • Camera Video Types
    • Audio Recording
    • Motive HotKeys
    • Measurement Probe Kit Guide
    • Motive Batch Processor
    • Reconstruction and 2D Mode
    • Tracking Bar Coordinate System
      • Transforming Coordinate System: Global to Local
  • MOTIVE UI PANES
    • Application Settings
      • Settings: Live Reconstruction
      • Settings: General
      • Settings: Views
      • Settings: Assets
        • Skeletons
        • Rigid Body
      • Settings: Camera
    • Mouse and Keyboard
    • Assets Pane
    • Builder Pane
    • Calibration Pane
    • Control Deck
    • Data Pane
    • Data Streaming Pane
    • Devices Pane
    • Edit Tools Pane
    • Graph View Pane
    • Info Pane
    • Labels Pane
    • Log Pane
    • Marker Sets Pane
      • Marker Name XML Files
    • Measurement Pane
    • Probe Pane
    • Properties Pane
      • Properties Pane: Camera
      • Properties Pane: Force Plates
      • Properties Pane: NI-DAQ
      • Properties Pane: OptiHub2
      • Properties Pane: Rigid Body
      • Properties Pane: Skeleton
      • Properties Pane: Take
      • Properties Pane: eSync2
    • Reference View pane
    • Status Panel
    • Toolbar/Command Bar
    • Viewport
  • PLUGINS
    • OptiTrack Unreal Engine Plugin
      • Unreal Engine: OptiTrack Live Link Plugin
      • Unreal Engine: OptiTrack Streaming Client Plugin
      • Unreal Engine: HMD Setup
      • Unreal Engine: MotionBuilder Workflow
      • Unreal Engine VCS Inputs
    • OptiTrack Unity Plugin
      • Unity: HMD Setup
    • OptiTrack OpenVR Driver
    • Autodesk Maya
      • Autodesk Maya: OptiTrack Insight VCS Plugin
    • Autodesk MotionBuilder
      • Autodesk MotionBuilder Plugin
      • Autodesk MotionBuilder: OptiTrack Skeleton Plugin
      • Autodesk MotionBuilder: OptiTrack Optical Plugin
      • Autodesk MotionBuilder: OptiTrack Insight VCS Plugin
      • Autodesk MotionBuilder: Timecode Data
    • OptiTrack Peripheral API
    • External Plugins
      • Houdini 19 Integration
  • ACTIVE COMPONENTS
    • Active Components Hardware
      • Active Puck
      • CinePuck
      • BaseStation
      • Information for Assembling the Active Tags
      • Manus Glove Setup
    • Configuration
      • Active Batch Programmer
      • Active Hardware Configuration: PuTTY
      • Active Component Firmware Compatibility
    • Active Marker Tracking
      • Active Finger Marker Set
      • Active Marker Tracking: IMU Setup
  • SYNCHRONIZATION
    • Synchronization Hardware
      • External Device Sync Guide: eSync 2
      • External Device Sync Guide: OptiHub2
    • Synchronization Setup
    • OptiTrack Timecode
  • VIRTUAL PRODUCTION
    • Unreal Engine: OptiTrack InCamera VFX
    • Entertainment Marker Sets
    • PrimeX 41
  • MOVEMENT SCIENCES
    • Movement Sciences Hardware
      • General Motive Force Plate Setup
      • AMTI Force Plate Setup
      • Bertec Force Plate Setup
      • Kistler Force Plate Setup
      • Delsys EMG Setup
      • NI-DAQ Setup
      • Multiple Device Setup
      • Prime Color Setup
    • Movement Sciences Marker Sets
      • Biomechanics Marker Sets
      • Biomech (57)
      • Rizzoli Marker Sets
    • For Visual3D Users
  • VIRTUAL REALITY
    • VR Plugins
      • VR Unreal Engine
        • OptiTrack Unreal Engine Plugin
        • Unreal Engine: OptiTrack Live Link Plugin
        • Unreal Engine: OptiTrack Streaming Client Plugin
        • Unreal Engine VCS Inputs
      • VR Unity
        • OptiTrack Unity Plugin
      • VR OpenVR
        • OptiTrack OpenVR Driver
    • VR HMD Setup
      • Unreal Engine: HMD Setup
      • Unity: HMD Setup
      • Manually Calibrating the HMD Pivot Point
      • Sync Configuration with an HTC Vive System
    • Navigation Controller Guide
    • SlimX 13
    • Active Marker Tracking
      • Active Finger Marker Set
      • Active Marker Tracking: IMU Setup
    • Synchronization Hardware
      • External Device Sync Guide: eSync 2
      • External Device Sync Guide: OptiHub2
  • ANIMATION
    • Autodesk Maya
      • Autodesk Maya: OptiTrack Insight VCS Plugin
    • Autodesk MotionBuilder
      • Autodesk MotionBuilder Plugin
      • Autodesk MotionBuilder: OptiTrack Skeleton Plugin
      • Autodesk MotionBuilder: OptiTrack Optical Plugin
      • Autodesk MotionBuilder: OptiTrack Insight VCS Plugin
      • Autodesk MotionBuilder: Timecode Data
  • ROBOTICS
    • PrimeX 22
    • Outdoor Tracking Setup
  • DEVELOPER TOOLS
    • Developer Tools Overview
    • NatNet SDK
      • NatNet 4.0
      • NatNet: Class/Function Reference
      • NatNet: Creating a Managed (C sharp) Client Application
      • NatNet: Creating a Native (C++) Client Application
      • NatNet: Data Types
      • NatNet: Matlab Wrapper
      • NatNet: Migration to NatNet 3.0 libraries
      • NatNet: RebroadcastMotiveData Sample
      • NatNet: Remote Requests/Commands
      • NatNet: Sample Projects
      • NatNet: Unicast Data Subscription Commands
      • Latency Measurements
    • Motive API
      • Motive API: Quick Start Guide
      • Motive API Overview
      • Motive API: Function Reference
      • Motive API Camera Calibration
    • Camera SDK
      • Camera SDK Classes
        • Class: cCameraGroupFilterSettings
        • Class: cCameraGroupMarkerSizeSettings
        • Class: cCameraGroupPointCloudSettings
        • Class: cCameraModule
        • Class: cRigidBodySettings
        • Class: cRigidBodySolutionTest
        • Class: cTTAPIListener
        • Class: cUID
  • MARKER SETS
    • Full Body
      • Baseline (37)
      • Baseline + Hinged Toe (41)
      • Baseline + Hinged Toe, with Headband (41)
      • Baseline + 13 Additional Markers (50)
      • Biomech (57)
      • Conventional (39)
    • Full Body + Fingers
      • Baseline + Hinged Toe + Fingers (49)
      • Baseline + 11 Additional Markers + Fingers (54)
      • Manus Glove Setup
    • Upper
      • Baseline Upper (25)
      • Baseline Upper Body + Fingers (33)
      • Conventional Upper (27)
    • Lower
      • Baseline Lower (20)
      • Helen Hayes Lower (19)
      • Conventional Lower (16)
    • Hand and Fingers
      • Left and Right Hand (11)
      • Active Finger Marker Set
    • Rizzoli Marker Sets
    • Entertainment Marker Sets
    • Rigid Body Skeleton Marker Set
  • GENERAL TROUBLESHOOTING
    • Troubleshooting
    • Running Motive on High DPI Displays
    • Firewall Settings
Powered by GitBook
On this page
  • Overview
  • Required Components
  • Hardware Setup
  • Component Wiring (Kistler)
  • Software Setup
  • Kistler Software Setup
  • Peripheral Device Module
  • Kistler Configuration Profile
  • Force Plate Setup in Motive
  • Synchronization Configuration
  • Sync Configuration Steps: eSync 2
  • How to Validate your Synchronization
  • Device Settings Profile
  • Force Plate Data in Motive
  • Data Export
  • C3D Export
  • CSV Export
  • Data Streaming

Was this helpful?

Export as PDF
  1. MOVEMENT SCIENCES
  2. Movement Sciences Hardware

Kistler Force Plate Setup

PreviousBertec Force Plate SetupNextDelsys EMG Setup

Last updated 2 years ago

Was this helpful?

This page provides instructions on how to integrate a Kistler force plate system with an OptiTrack motion capture system.

Overview

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 2 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.

Analog Platforms

Analog force plate devices can only be implemented via DAQ devices. Incoming voltage signals can be detected through the data acquisition channels, but force plate related software features (vectors, position calibration, etc.) will not be supported in Motive for the analog platforms. Refer to the page for detailed instructions on integrating analog devices.

Starting from Motive 3.0, reference clock synchronization while in Live mode is supported.

Required Components

  • Kistler Data Acquisition System

  • Kistler Force Plate

  • Control I/O, Sync breakout box

  • Prime series Ethernet camera system with the eSync 2 synchronization hub.

  • Motive 2.1 or above.

Hardware Setup

Component Wiring (Kistler)

Kistler Force Plate System Setup

Connect each force plate to the Data Acquisition device, and connect the USB uplink cable from the acquisition device to the host PC. For detailed instructions on setting up the Force Plate system with a host PC, refer to the Kistler documentation.

Camera System Setup

Wiring the eSync with the Data Acquisition device

Hot Plugging

Hot plugging is not supported with the integration. When a new device is connected to the system, you must re-start Motive to instantiate it.

Software Setup

Kistler Software Setup

Before integrating Kistler force plates into Motive, make sure all of the components required by Kistler system are set up on the computer. This includes BioWare software, the device driver (InstaCal), and other required software components. The force plate system must be recognized by Kistler's software before it can be used in Motive.

Once they are all installed, launch the BioWare software and register each force plate. During this process, you will input device information such as model number, serial number, and platform specs to configure the device setting. For more information, please refer to manufacturer documentation.

Peripheral Device Module

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.

For Kistler Customers

Kistler system also requires Microsoft Visual C++ 2010 Redistributable - x64 to be installed on the computer. If it is not already on the computer, you will get prompted to set this up during Motive installation process. Please make sure to have this installed as well.

Kistler Configuration Profile

After registering the force plate in BioWare, next step is to export out the device configuration XML file. In BioWare, go to the Setup → Save DataServer Configuration File to export out the configuration XML file. To add the Kistler force plates in Motive, this XML file containing the force plate information must be added to the Motive directory. Copy-and-paste the Configuration.xml file into the C:\ProgramData\OptiTrack\Motive\DeviceProfiles directory, and then rename the file to Kistler.xml. Once this is done, Motive should initialize the force plates that are detected by computer and that are registered within the XML file.

Force Plate Setup in Motive

1. Start Motive

2. Calibrate Cameras

3. Setup CS-400

4. Place CS-400 on force plate

Place the calibration wand on the force plate so that vertex of the wand is located at the right-hand corner of the side where the cable input is located (as shown in the image below). A correct placement of the calibration square is important because it determines the orientation of the force plate and its local coordinate axis within the global system. The coordinate systems for force plates are independent of the system used Motive.

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.

5. Set force plate position in Motive.

After placing the calibration square on the force plate, select the CS-400 markers in Motive. Right click on the force plate you want to locate, and click Set Position. When there are multiple force plates in a volume, you may need to step on the force plate to find which platform the calibration square is on. In Motive, uncalibrated force plates will light up in green and a force vector will appear when you step on the plate. Repeat step 4 and 5 for other force plates as necessary.

Referencing to the markers on the calibration square, Motive defines the location of the force plate coordinate system within the global coordinate system.

Motive uses manufacturer defined X, Y, and Z mechanical-to-electrical center offset when calculating the force vector and the center of pressure. For digital based plates, this information is available from the SDK and also stored in the plate's on-board calibration data.

6. Zero force plates.

After you have calibrated each of your force plates, remove the CS-400 from the volume. Right click one of your force plates in Motive and click Zero (all). This will tare the scale and set the current force on the plate data to 0. This will account for a small constant amount of measurement offset from the force plate. Remember that it zeros all of the force plates at once. So make sure there are no objects on any of the force plates.

7. Set sampling rate

Sampling rate of force plates is configured through the synchronization setup which will be covered in the following section.

Supported force plate sampling rates: Kistler plates support rates sampling rates between 10~2000 Hz. Make sure the synchronization is configured that the force plates sample at the supported speed.

Synchronization Configuration

There are two synchronization approaches you could take: Synchronization through clock signal or through recording trigger signal.

Synchronization via clock signal utilizes the internal clock signal of the eSync to synchronize the sampling of the force plates on per-frame basis. However, when there is another device (e.g. NI-DAQ) being synchronized to the clock signal frequency, the sampling rate cannot be set for each individual device. In that case, triggered sync must be used for synchronizing the initial recording trigger. Synchronization via trigger signal utilizes the recording trigger in Motive to align the initial samples from both systems. After the initial sync, both systems run freely at their own sampling rate. If the force plates are running at whole multiples of the camera system, the collected samples will be aligned. However, since the sampling clocks are not perfectly accurate, alignment of the samples may slowly drift over time. Thus, when synchronizing via recording trigger, it is better to keep the record times short.

When synchronizing through the eSync, use the following steps to configure the sync settings in Motive. This will allow both systems to be triggered simultaneously with reference to the parent synchronization device, the eSync.

Sync Configuration Steps: eSync 2

Reference Clock Sync Setup Steps

  1. Next, to the Clock Frequency section, input the sampling rate that you wish the run the force plates in. This clock signal will be eventually outputted to the force plate system to control the sampling rate. For this guide, let's set this to 1200 Hz.

  2. Once the clock frequency is set, apply the Input Divider/Multiplier to the clock frequency to set the framerate of the camera system. For example, if you set the Input Divider to 10 and the Input Multiplier to 2 with internal clock frequency running at 1200 Hz, the camera system will be running at 240 FPS. The resulting frame rate of the camera system will be displayed in the Camera Rate section.

  3. Next step is to configure the output signal so that the clock signal can be sent to the force plate system. Under the Outputs section, enable the corresponding output port of the eSync which the force plate system is connected to.

  4. Record Trigger → False

  5. Reference Clock Sync → True

  6. eSync Output Channel → output port used on the eSync.

eSync 2 Settings Tip:

Live Data

Starting from Motive 3.0, clock synchronization in Live mode is supported, and the force vector visualization will be available both in Live and Edit modes.

Triggered Sync Setup Steps

  1. Set up the output signal so that the recording trigger signal can be sent to the force plate system. In the Outputs section, enable and configure the corresponding output port of the eSync which the force plate system is connected to.

  2. Record Trigger → Device

  3. Reference Clock Sync → False

  4. eSync Output Channel → output port used on the eSync.

ReSynch

When two systems are synchronized by recording trigger signals (Recording Gate or Recording Pulse), both systems are in Free Run Mode. This means that the recording of both the mocap system and the force plate system are triggered simultaneously at the same time and each system runs at its own rate.

Two systems, however, are synchronized at the recording trigger but not by per frame basis. For this reason, alignment of the mocap data and the force plate data may gradually drift from each other for longer captures. But this is not a problem since the sync chain will always be re-synchronized each time recording in Motive is triggered. Furthermore, Takes in general do not last too long for this drift to take effect on the data.

How to Validate your Synchronization

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.

The 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 makes the data more obvious for validating the synchronization. Alternately, you can attach a marker on a 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 monitor the precise timing of the ball or the foot impacting the force plate and compare them between the mocap data and the force plate data.

The following is an example of validating good synchronization outcomes:

Device Settings Profile

All of the configured device settings, including the calibration, get saved on Device Profile XML files. When you exit out of Motive, updated device profiles will be saved under the program data directory (C:\ProgramData\OptiTrack\Motive\DeviceProfiles), and this file gets loaded again when you restart Motive. You can have this file backed up to persist configured eSync 2 and device settings. Also, if you wish to reset the device settings, you can remove XML files other than the default one from the folder, and Motive will load from the default settings.

Force Plate Data in Motive

Live Force Plate Data

Notes

  • The force and moment data reflects the coordinate system defined by the force plate manufacturer, which is typically the Z-down right-handed coordinate system. Note: This convention is independent of the global coordinate system used in Motive. Thus, the Fz components represent the vertical force. For more in-depth information, refer to the force plate specifications.

Data Export

We recommend the following programs for analyzing exported data in biomechanics applications:

C3D Export

C3D Axes

Common Conventions

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.

  • X axis in Motive should be configured to positive X

  • Y axis in Motive should be configured to negative Z

  • Z axis in Motive should be configured to positive Y.

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).

CSV Export

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.

Data Streaming

Number of Force Plates

Setup the OptiTrack camera system and place the force plate(s) at the desired location(s); ideally, near the center of the volume. See or page for details.

For accurate synchronizations, the must be used. The eSync 2 has signal output ports that are used to send out synchronization signals to child devices. Connect the BNC output ports of the eSync to sync input ports (Genlock/Trigger Input) of force plate amplifiers.Kistler force plates have a sync I/O breakout (Control I/O) accessory that connects to the amplifier. The eSync will connect to one of the inputs of this sync I/O box. For triggered sync, connect the output port of the eSync to the Trigger Input. For external clock sync, connect the output to the Sync Input of the sync I/O box.

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 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 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 , 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.

Open the and the .

In the , select the eSync among the listed devices. This will list out the synchronization settings in the properties pane for the selected eSync.

In the , under Sync Input Settings section, set the Source to Internal Clock.

Set the Output 1-4 → Type to .

Now that the eSync has been configured, you need to configure the force plate properties in Motive. While the force plate(s) is selected in Motive, access the Properties pane to view the . Here, set the following properties:

Once this is set, the force plate system will start sampling at the frequency of the clock signal configured on the eSync, and this rate will be displayed on the as well.

In Motive 3.0 and above, you can quickly configure eSync into biomech sync settings by right-clicking on the eSync from the and select one of the presets from the context menu. This will enable and set all of the eSync outputs to the Internal Clock and set the clock frequency.

Open the and the .

The final frame rate of the camera system will be displayed at the very top of the .

In the , select the eSync among the listed devices. This will list out the synchronization settings in the Properties pane for the selected eSync.

Set the Output 1-4 → Type to .

Now that the eSync has been configured, you need to configure the properties of the force plates. While the force plate(s) is selected in Motive, access the Properties pane to view the . Here, set the following properties:

Once this is done, the force plate system will synchronize to the recording trigger signal when Motive starts collecting data, and the force plates will free-run after the initial sync trigger. You can configure the sampling rate of the force plates by modifying the Multiplier values in to sample at a whole multiple of the camera system frame rate.

For free run sync setups, sampling rates of force plates can be set from the , but the sampling rate of force plates must be configured to a whole multiple of the camera system's framerate. By adjusting the Rate Multiplier values in the , sampling rates of the force plates can be modified. First, pick a frame rate of the camera system and then adjust the rate multiplier values to set force plates to the desired sampling rate.

However, this could be an issue when live-streaming the data since recording is never initiated and two systems will be synchronized only when Motive first launches. To zero out the drift, the ReSynch feature can be used. Right-click on force plates from either the or the , and select Resynch from the context menu to realign the sampling timing of both systems.

Force plate data can be monitored from the . You will need to either use a provided Force Plate Forces layout or configure a custom graph layouts to show force plate data. To view the force plate data, make sure the corresponding force plates are selected, or selection-locked, in Motive.

If you are configuring your own force plate graph layout, make sure the desired force plate data channels (Fx, Fy, Fz, Mx, My, or Mz) are selected to be plotted. Then, when you select a force plate in Motive, and the data from the corresponding channels will be plotted on the graphs. 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. For more information about how to configure graph layouts, read through the page.

Motive exports tracking data and force plate data into C3D files. Exported C3D files can then be imported into a biomechanics analysis and visualization software for further processing. See the or page for more information about C3D export in Motive. Note that the coordinate system used in Motive (y-up right-handed) may be different from the convention used in the biomechanics analysis software.

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 workflow page.

Motive can stream the tracking data and the force plate data into various applications — including Matlab — using protocol. Find more about from the User's Guide included in the download.

At the time of writing, there is a hard limit on the maximum number of force plate data that can be streamed out from Motive. Please note that only up to 8 force plate data can be streamed out from Motive and received by a application.

Quick Start Guide
Hardware Setup
eSync 2 synchronization hub
Log pane
Quick Start Guide
CS-400 calibration square
Devices pane
Properties pane
Devices pane
Properties pane
force plate properties
Devices pane
Devices pane
Devices pane
Properties pane
Devices pane
Devices pane
force plate properties
Devices pane
Devices pane
Devices pane
Graph View pane
Graph View pane
Visual3D
The MotionMonitor
MATLAB
Data Export
Data Export: C3D
Data Streaming
NatNet SDK 4.0
NI-DAQ Setup
Devices pane
NatNet streaming
NatNet Streaming
Diagram for Prime Camera System with integrated force plates. (*) Some force plates don't have external amplifiers, but instead, have their amplifiers integrated within the platform. In this case, connect sync cables and the USB cables directly to the host PC. Click image to enlarge.
The eSync 2 output and input ports.
Sync cable connected to the Sync Input port of the sync breakout box for external clock sync. The other end connects to one of the output ports on the eSync 2.
Cable connection into the DAQ box.
Kistler Device is detected as USB-2533 under device manager after installing the driver.
Each force platform need to be added in the BioWare software to run the force plates.
Motive force plate representation in Perspective view.
Motive with force plates and camera calibration.
CS-400 calibration square with force plate force plate parts.
Calibrated force plate position and orientation. X and Y axis is shown.
Force plate with CS-400 aligned properly.
Setting the position of a force plate in Motive. The number label on the force plate is inverted because the force plate position and orientation has not been calibrated yet.
Set the force plate data to zero for more accurate data.
Applying Biomech preset settings.
Example eSync 2 properties for triggered sync.
Example force plate properties for triggered sync.
Re-aligning initial sampling timing of the force plate.
Good synchronization
Graph of live force plate data.
Graph view pane layout configuration.
C3D export setting for applications using z-up right-handed coordinate systems.
Configuring force plate sampling rate from .
Example eSync 2 properties for clock sync. Make sure the eSync 2 is selected in the .
Example force plate properties for clock sync. Make sure the Force Plate is selected in the .
Default force plate layout selected from the dropdown menu located at top-right corner of the .
biomechanics analysis software.
biomechanics analysis software provided by
Devices pane
Properties pane
Properties pane
Graph pane
The MotionMonitor
Visual3D
C-Motion
perspective view
Internal Clock
Recording Gate