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
  • Hardware Setup
  • Software Setup
  • Device Firmware
  • Delsys Software Setup
  • Peripheral Module Setup
  • Device Setup in Motive
  • Synchronization
  • Device Properties: Data Operation
  • Data Recording
  • Data Playback
  • Data Export
  • Troubleshooting
  • Troubleshooting

Was this helpful?

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

Delsys EMG Setup

Overview

Starting from Motive version 3.0 and above, the digital integration of Delsys Trigno Avanti systems is supported. Through this integration, electromyography (EMG) measurements from the Trigno Avanti EMG sensors can be recorded in Motive along with the tracking data. This page provides instructions on how to set up the Delsys Trigno Avanti platform along with the OptiTrack motion capture system.

Required Components

  • Prime series Ethernet camera system

  • eSync synchronization hub

  • Motive 3.0 or above

  • Delsys Trigno Avanti Platform with EMG sensors

  • Delsys Trigger Module for synchronization

  • Trigno EMGworks OR Delsys SDK server package version 3.5.8 or above.

  • Firmware on both the Trigno base station and the sensors must be updated. If the firmware is installed, use the Software Update Tool to install the latest firmware. For more information, please refer to the manufacturer documentation.

Notes

  • Supported Sensors: Integration is supported for Delsys Trigno EMG systems with Trigno Avanti sensors only.

  • Supported Data Channels: Data channels for EMG measurements will be reported in Motive. Data channels for the inertial measurement unit (IMU) and accelerometer are not supported.

  • Supported Device/Channel Count: Integration supports one Trigno base station with up to 16 EMG data channels. Additional devices and/or data channels above this limit cannot be integrated due to a restriction of the Delsys SDK.

  • Synchronization: Synchronization with the motion capture system requires the Delsys Trigger Module and the eSync synchronization hub. Supports triggered sync only.

  • Delsys Trigno Control Utility software must be running prior to launching Motive.

Hardware Setup

Below are two diagrams depicting two types of Delsys hardware setups. One without a NI-DAQ device, and one with a NI-DAQ device. When setting up a configuration without a NI-DAQ device, you'll use a Delsys Trigger Module. This will only allow the option for Trigger Synchronization. If you use a NI-DAQ configuration, however, you have the option to use either Trigger and Reference Clock Synchronization. For more information about synchronization, please scroll down to the Synchronization section of this page.

Software Setup

Device Firmware

Please make sure the firmwares on both the Trigno Base Station and the EMG sensors have been updated. You can check the firmware version using the Software Update Tool provided by Delsys. For more information, please refer to the user manual.

Delsys Software Setup

Before proceeding with integrating the EMG system into Motive, please make sure the required software for the Delsys Trigno Avanti sensor system is all set up on the host computer. This includes Trigno Control Utility software which will get along with the Trigno EMGworks or Delsys SDK Server package version 3.5.8. For the sensor to work in Motive they must first be configured and paired in the Delsys Trigno Control Utility (TCU) software.

Peripheral Module Setup

In order to integrate Delsys EMG 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.

Device Setup in Motive

Step 1. Launch Delsys Trigno Control Utility software

Make sure to launch the Delsys TCU software first. Make sure all of the sensors have been powered and paired in the TCU software. If the sensors are not detected here, they will not be detected in Motive.

Step 2. Start Motive

Once the sensors are detected and running in the Delsys TCU software, launch Motive. If the peripheral module is installed, Motive will attempt to connect to the Delsys system.

Step 3. Confirm connection

In TCU: If the TCU software is connected to Motive, it will indicate that it has connected to a remote client. As shown in the image below.

Step 4. Enable data channels

Data Channels:

  • Channel 1-16: These are the channels used for reporting raw EMG signals.

  • Channel 17-32: These are the channels used for reporting RMS envelope for the corresponding EMG signal. For example, channel 17 reports RMS envelope of the EMG signals coming through channel 1, and channel 18 reports RMS envelope for channel 2.

Terminal Name

  • The terminal name in Motive correlates to the physical sensor ID given to a Trigno Avanti sensor in Delsys TCU.

Step 5. Enable device

Once you have enabled all of the desired data channels, enable the Trigno device from the Devices pane.

Step 8. Confirm incoming data in Graph pane

As a last step, use the Graph pane to check the EMG data coming through the enabled channels.

Graph Layout:

Synchronization

Setting up triggered sync

  1. If not already, connect the Delsys trigger module into the Trigno base station.

  2. Using a BNC cable, connect one of the output ports on the eSync into the Start Input of the triggered sync box.

  3. [Motive] Set the Type of the connected output port to Recording Gate.

  4. [Motive] Select Trigno device to access its properties.

  5. [Motive] Set the Triggered Sync setting to Device. Note that once Trigno is configured to the Triggered sync mode, EMG data will not be reporting until a recording is started to trigger the Delsys system.

Device Properties: Data Operation

Under Trigno device properties, you can set the following properties to perform data operations to the reported data.

Rectify Values

When enabled, all of the Raw EMG signal coming through channel 1~16 will be rectified and the absolute values of the measurements will be reported.

RMS Envelope Window

RMS is a common way to interpret EMG data. Motive performs RMS envelope calculation when reporting the data just for visualization purposes. For a complete EMG analysis, including additional data filtering for example, the Raw EMG signal should be processed through a separate data analysis software.Size of the RMS envelope can be changed by configuring the RMS Envelope Window property under Trigno device properties. This will set the number of samples used to calculate the RMS reported in Motive. Higher sample size will result in a smoother window and it needs to be adjusted based on the Trigno sampling frequency.

Noise Sample Size

Noise removal can be controlled by the Noise Sample Size property. Set this to 0 to completely disable noise removal.

Data Recording

Once Trigno system is detected in Motive and its channels are enabled, the reported EMG channel data will get recorded along with the motion tracking data. With the triggered sync setup explained above, motion capture system and the EMG system will be synchronized at the start of the recording and they will be running at their own sampling rates after the trigger point. Due to limitation of the triggered synchronization, it is recommended to keep the recordings relatively short.

The Delsys Trigno EMG device samples at a rate of 2000Hz natively, so oftentimes we are down sampling in Motive, and in rare cases, up sampling. We have found that sampling in Motive at a motion capture rate of 100Hz or 200Hz with a multiplier of 10 for the Delsys Trigno EMG device (making its sample rate at 1000Hz or 2000Hz respectively), has shown the best results. When running Motive at 120Hz, however, it has shown to have intermittent frame drops.

For consecutive recordings, please wait at least 5 seconds between each recording to allow the EMG system to get ready for the next recording trigger for proper sync. If not, the data may not get successfully recorded.

Data Playback

Graph Layout with Device Data Plots

  • Right-click on the graph view and set the desired layout dimensions.

  • On one of the graphs, right-click and under the Devices section, select the analog channels you wish to plot.

Data Export

CSV Export: When exporting tracking data into CSV, additional CSV files will be exported separately for each Trigno device in a Take. Each of the exported CSV files will contain basic properties and settings at its header, including device information and sample counts. The voltage amplitude of each analog channel will be listed. Also, mocap frame rate to device sampling ratio is included since analog data is usually sampled at higher sampling rates.

Note that the coordinate system used in Motive (y-up right-handed) may be different from the convention used in the biomechanics analysis software.

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

Troubleshooting

Q - Delsys Trigno Control Utility software not detecting the base station. Unable to synchronize USB communication.

A - This can happen if the version of the firmwares on the Trigno base station and the sensor is not compatibile with the version of the SDK being used (3.1.2). Please use the Delsys Software Update Tool and make sure the compatible version of the firmware is installed. We recommend using 2905 or 2906 firmware as they are most tested, but any newer versions of the firmware should work also.

Troubleshooting

Delsys EMG box not connecting, error appearing in the Windows Device Manager:
How to wire the DAQ from the breakout wires Delsys EMG base station to DAQ:

PreviousKistler Force Plate SetupNextNI-DAQ Setup

Last updated 2 years ago

Was this helpful?

In Motive: If the sensor is connected, it will be reported under the panel and the Trigno device will be listed in the .

Open the in Motive and connected Trigno device will be listed. If you click on the on the device, and all of the available data channels will be shown in the pop-up. Click on the data channels and enable the ones that will be used.

The graph layout may need to be configured for plotting the EMG channel data. To create a new layout, click on the button in and select Create New Layout from the context menu. Once new layout is created, click on the icon to expand the sidebar, and click on the graph which you wish to plot the graphs onto, and check mark the EMG channels in the sidebar to start plotting the channel data onto the selected graph. Make sure Trigno device is selected under the Devices pane.

Synchronization of the Delsys Trigno EMG system with the motion capture system is accomplished through triggered sync. Triggered sync, in this situation, refers to the relationship between the Delsys Trigno EMG system and the motion capture system. Meaning, the motion capture system triggers the start of data sampling of the Delsys Trigno EMG system. Once triggered, both the motion capture system and the Delsys Trigno EMG system are truly aligned only during the first frame of recording then each move forward at their own individual sampling rates in an approximation of synchronization. Reference clock synchronization is more precise, however, it is not supported by Delsys systems. This is due to a limitation of the DelsysSDK. For more information regarding Deylsys SDK, please visit their SDK page .

Triggered sync can be set up by connecting one of the eSync outputs to the Delsys Trigger Module. For triggered synchronization, one of the outputs from the eSync will need to be configured to output a signal, and it will need to be connected into the Start Input on the trigger module. The connect input port on the trigger module will also need to be set to detecting a rising edge using the toggle switch on the module.

Refer to the Delsys documentation for more information on setting up the triggered sync using the trigger module:

[Motive] In Motive, select the eSync to access its properties from the .

Captured analog signals are recorded within the Take file and they can be played back in Motive. When in Edit mode, the integrated EMG device will be shown under the , and its Analog measurements can be plotted on the . You will need to configure the graph layout and enable plotting of analog channels:

Create a custom layout on the Graph View pane. → Create Layout.

Recorded EMG channel data can be exported into C3D and CSV files along with the mocap tracking data. You can just follow the normal the steps, and if the analog data exists in the TAK, they will also be exported.

C3D Export: Both mocap data and the analog data will be exported onto a same C3D file. Please note that all of the analog data within the exported C3D files will be logged at the same sampling frequency. If any of the devices are captured at different rates, Motive will automatically resample all of the analog devices to match the sampling rate of the fastest device. More on C3D files:

Please for any issues or questions that are not covered in this wiki page.

Log
Devices pane
here
https://www.delsys.com/downloads/USERSGUIDE/trigger-module.pdf
Properties pane
Devices pane
Graph pane
tracking data export
https://www.c3d.org/
contact us
Device driver needed linked here
Wiring configurations found here
Devices pane
Graph pane
ContextMenu dotdotdot.png
ContextMenu dotdotdot.png
ContextMenu dotdotdot.png
Graph Editor 20.png
Click image to enlarge.
Click image to enlarge.
Checking firmware versions on the base station.
Delsys Trigno Avanti sensors detected in the TCU software.
Two EMG sensors paired and operating in Trigno Control Utility software.
Sensor channels shown in the Devices pane. Click image to enlarge.
Sensor ID shown in the TCU software. Click image to enlarge.
Trigno device enabled.
Delsys trigger module layout snapshot from Delsys documentation.
eSync 2 configured to outputting recording gate signal.
Triggered Sync set to Device on Trigno properties.
Properties of Trigno Delsys listed under the Properties pane.
C3D export setting for applications using z-up right-handed coordinate systems.
Unable to synchronize USB communication warning.
Recording Gate