Main Page → Motive Documentation → Synchronization → External Device Sync Guide: eSync
This page provides general instructions on how to use the eSync for synchronizing external devices.
The eSync is a synchronization hub that allows advanced users to integrate external systems into OptiTrack motion capture systems. With proper sync chain setups, you can have another (parent) system control the mocap system, or have the mocap system control other (child) systems, or both. Note that the setup may change depending on the type and number of the external devices as well as the characteristics of the communicated sync signals. Use this guide for understanding the general idea of how external devices are implemented and apply the knowledge for your needs.
External Device Synchronization
With the eSync, Prime series mocap systems can work together with other systems to perform precisely synchronized operations and data collections. This offers benefits in a wide range of applications. Reference video cameras, NI-DAQ devices, Force Plates, and recording triggers are examples of commonly synchronized external devices.
The eSync synchronization hub has multiple sync input and output ports. In general, a parent device connects to the input ports for controlling the mocap system, and the child devices connect to output ports to be controlled by the mocap system. Once the devices are connected to the eSync, the input and output signal characteristics need to be specified and configured under the eSync's device properties in Motive.
Configurable in Motive
This is further explained in the later section.
Configurable in Motive
For general instructions on setting up the mocap system, refer to the Hardware Setup pages. This guide assumes the camera system and the eSync have been already set up.
Step 1. Before setting up, draw out the schematic of which devices will be the parent or the child of the synchronization chain in respect to the mocap system.
Step 2. Connect the external devices
Step 3. Launch Motive. The eSync should get listed under the Devices pane.
Step 4. [Motive] Open the Properties pane and select the eSync in the Devices pane to access its properties.
Step 5. [Motive > Properties: eSync] Under the Sync Input Settings: Source section, use the drop-down menu to pick a desired sync source for the camera system to synchronize to. Read more under the Input Source Setup section of this page.
Step 6. [Motive > Properties: eSync] Configure the input divider/multiplier settings, and/or the clock frequency settings (for Internal Clock only), to set the camera rate. The final frame rate of the camera system will be displayed next to Camera Rate property or in the Devices pane.
Step 7. [Motive > Properties: eSync] Configure the Outputs. Output ports of the
eSync are used to tell connected child devices what Motive is doing. Read more under the Output Signal Setup section of this page.
Step 8. [Motive > Properties: eSync] If you wish to set up a recording trigger device, connect it to one of the input ports and designate the port under the Recording Trigger section of the eSync properties. Read more under the Recording Trigger Setup section of this page.
Step 9. [Motive > Properties: eSync] Lastly, check the Monitor section and make sure all signals are detected properly.
Once you have connected the external devices to the eSync, the first step is to select and configure the sync source under the eSync properties. The selected source will become the parent sync of both the camera system and other external devices. There are multiple sync source options to choose from under the drop-down menu. Ultimately, only one sync source will be selected and used to synchronize the cameras and subsequent child devices for any particular configuration.
When you are done changing the settings, press Apply to set the configured sync method.
The first step is to define a parent sync source for the camera system. This is configured in the Sync Input → Source entry under the eSync properties:
Once the input source is set, next step is to define an appropriate trigger event. Under the Sync Input → Input Trigger option, pick a signal morphology (Either Edge, Rising Edge, or Falling Edge) for the desired trigger event. Note that the suitable event will vary depending on characteristics of the received signal and how you want the system to synchronize with it. The following diagrams show how the camera system responds to received signal triggers. When configured properly, the camera system will expose in respect to the sync signal from the parent device.
Every rising edge of the sync input signal defines either the start or the end of a frame, consecutively.
Every falling edge of the sync input signal defines either the start or the end of a frame, consecutively.
Every rising or falling edge of the sync input signal defines either the start or the end of a frame, consecutively. When using both of the edges as the input trigger, the input signal must have 50% duty cycle for the cameras to synchronize properly.
The frame rate of the camera system gets determined by the selected sync input source. When the frequency of the sync source is higher than the supported frame rate, input dividers and multiplier can be applied to adjust the signal frequency for synchronizing the camera system. The final framerate will be calculated and displayed at the bottom, Sync Input → Final Frame Rate, and you can monitor this rate while you apply the adjustments. When the customized sync configurations are applied at the end of the setup, the cameras will start to capture at this final frame rate.
In case if you need to delay the camera exposure from the input trigger, there is a sync offset can be applied. Click on the icon at the top, and click Show Advanced to view the advanced settings and you can set the Sync Offset (in microseconds) to apply the delay. This is typically used to synchronize other infrared systems with the camera system to avoid IR interference to each other.
Camera exposures are always positioned at the center of every frame periods, and the precise moment of the camera exposure does not exactly coincide with the trigger event. When synchronizing the camera exposure timing with the sync input signal triggers, make sure this gap is taken into account. To precisely align the input signal trigger with the exposure timing, an offset delay, in microseconds, of half of the frame period plus half of the camera exposure must be applied in the Sync Input → Sync Offset (us). The camera exposure is measured in microseconds on the Ethernet cameras.
The eSync 2 has total 4 output ports (3.3 V). If you want to setup the camera system to be a parent of other systems, connect the child devices into the Output ports of the eSync for receiving the reference sync signals. Once the devices are connected, you can configure the output signal source under the eSync properties. Know what type of sync signals are expected by the child devices, and configure the sources accordingly so that appropriate signals are outputted.
The eSync can output the following types of signals:
Note: All output signals can be inverted by setting the Output → Polarity to Inverted.
Gated Output Signal (eSync):
Exposure Time/Gated Exposure Time output signals indicate when the cameras are exposing.
When the Output:Type is set to Exposure Time, a high voltage (3.3V) signal will be outputted from the corresponding output port whenever the camera system is exposing, or shuttering, in the Live Mode. The Gated Exposure Time signal works similarly, but the signal will be sent out only when Motive is recording.
Recording gate/pulse output signals can be used to tell the child device when Motive is recording or not. When configured to Recording Gate, the eSync 2 will output a constant high voltage signal when Motive is recording. When configured to Recording Start/Stop Pulse, the sync hub will output a pulse signal when Motive either starts or stops recording.
When configured to Gated Internal Clock, the eSync outputs its internal clock signal while Motive is recording. The internal clock signal has a 50% duty cycle with the signal frequency defined under the Sync Input → Clock Freq (Hz) section.
With the eSync, external triggering devices (e.g. remote start/stop button) can integrate into the camera system and set to trigger the recording start and stop events in Motive. Such devices will connect to input ports of the eSync and configured under the Record Triggering section of the eSync properties.
By default, the remote trigger source is set to Software, which is the record start/stop button click events in Motive. Set the trigger source to the corresponding input port and select an appropriate trigger edge when an external trigger source (Trigger Source → isolated or input) is used. Available trigger options include Rising Edge, Falling Edge, High Gated, or Low Gated. The appropriate trigger option will depend on the signal morphology of the external trigger. After the trigger setting have been defined, press the recording button in advance. It sets Motive into a standby mode until the trigger signal is detected through the eSync. When the trigger signal is detected, Motive will start the actual recording. The recording will be stopped and return to the 'armed' state when the second trigger signal, or the falling edge of the gated signal, is detected.
Note: For capturing multiple recordings via recording trigger, only the first TAK will contain the 3D data. For the subsequent TAKs, the 3D data must be reconstructed through the post-processing reconstruction pipeline.
› Q : I have set up a custom synchronization chain from a mocap system (parent) to a third-party device (child) that uses a third-party software package to operate, but somehow I am seeing a timing offset between the two recorded data sets. What's happening here?
A: The observed offset is likely due to a time delay from the third party system receiving the signal and initiating the recording. This is a common source of confusion especially for syncing devices that runs on third-party software packages.
The eSync and the OptiHub can be configured to output signals at specified events (e.g. exposure timing, recording pulse, etc.). However, this configuration solely will not accomplish precise synchronization of the two systems because it does not take account of the time delay it takes for the third party system to receive and react to the signal.
To achieve fully precise synchronization, please follow our device specific sync setup guides, if applicable, or take this offset into consideration.