LogoLogo
WebsiteSupportDownloadsForumsQuick LinksContact Us
v3.2
v3.2
  • OptiTrack Documentation
  • WHAT'S NEW
    • What's New in Motive 3.2
  • QUICK START GUIDES
    • Quick Start Guide: Getting Started
    • Quick Start Guide: Prime Color Camera Setup
    • Quick Start Guide: Precision Capture
    • Quick Start Guide: Tutorial Videos
    • Quick Start Guide: Active Marker Tracking
    • Quick Start Guide: Outdoor Tracking Setup
  • HARDWARE
    • Cameras
      • Ethernet Cameras
        • PrimeX 120
        • PrimeX 41
        • PrimeX 22
        • PrimeX 13
        • PrimeX 13W
        • SlimX 13
        • Prime Color
        • VersaX 22
        • VersaX 41
        • VersaX 120
      • USB Cameras
        • Slim 3U
        • Flex 13
        • Flex 3
        • V120:Duo
        • V120:Trio
        • Adjusting Global Origin for Tracking Bars
    • Prepare Setup Area
    • Camera Mount Structures
    • Camera Placement
    • Ethernet Camera Network Setup
      • General Overview and Specs
      • Windows 10 Network Settings
      • Cabling and Load Balancing
      • Switch Configuration for PrimeX 120
      • NETGEAR ProSafe GSM7228S: Disabling the Broadcast Storm Control
      • White/Blacklisting Cameras
    • USB Camera System Setup
      • USB Camera Network Overview and Specs
      • V120:Duo and Trio Setup
      • Tracking Bar Coordinate System
        • Transforming Coordinate System: Global to Local
    • Aiming and Focusing
    • Camera Status Indicators
  • MOTIVE
    • Installation and License Activation
    • Motive Basics
    • Calibration
      • .mcal XML Calibration Files
      • Continuous Calibration
      • Continuous Calibration (Info Pane)
      • 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
    • Trained Markersets
    • IMU Sensor Fusion
    • 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
  • MOTIVE UI PANES
    • Settings
      • Settings: General
      • Settings: Assets
      • Settings: Live Pipeline
      • Settings: Streaming
      • Settings: Views
      • Settings: Mouse and Keyboard
      • Settings: Audio
    • Assets Pane
    • Builder Pane
    • Constraints Pane
      • Constraints XML Files
    • Calibration Pane
    • Data Pane
    • Devices Pane
    • Edit Tools Pane
    • Graph View Pane
    • Info Pane
    • Labels Pane
    • Log 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: Trained Markerset
      • Properties Pane: eSync2
    • Status Panel
    • Toolbar/Command Bar
    • Control Deck
    • Viewport
  • PLUGINS
    • OptiTrack Blender Plugin
      • OptiTrack Blender Plugin
    • OptiTrack Unreal Engine Plugin
      • Unreal Engine: OptiTrack Live Link Plugin
        • Quick Start Guide: Real-Time Retargeting in Unreal Engine with Live Link Content
        • Unreal Editor for Fortnite (UEFN): OptiTrack Plugin for Live Link Hub
        • Unreal Engine: Live Link Camera Stream Setup
        • Live Link Content: Active Puck Static Meshes
      • Unreal Engine: MotionBuilder Workflow
      • Unreal Engine: HMD Setup
      • Unreal Engine VCS Inputs
    • OptiTrack Unity Plugin
      • Unity: HMD Setup
    • OptiTrack OpenVR Driver
    • OptiTrack MATLAB Plugin
    • 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
      • Wired AnchorPuck
      • CinePuck
      • Wired 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
  • 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
    • Movement Sciences Marker Sets
      • Biomechanics Marker Sets
      • Biomech (57)
      • Rizzoli Marker Sets
    • For Visual3D Users
    • Prime Color Camera Setup
      • Prime Color Setup: Required Components
      • Prime Color Setup: Hardware Setup
      • Prime Color Camera Setup: Camera Settings
      • Prime Color Camera Setup: Prime Color FS Calibration
      • Prime Color Setup: Data Recording / Export
      • Prime Color Camera Setup: FAQ / Troubleshooting
      • Prime Color Camera Setup: Windows Network Settings
  • VIRTUAL REALITY
    • VR Plugins
      • VR Unreal Engine
        • OptiTrack Unreal Engine Plugin
        • Unreal Engine: OptiTrack Live Link Plugin
          • UE5.1 Live Link Retarget External Workaround
        • 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
    • SlimX 13
    • Active Marker Tracking
      • Active Finger Marker Set
    • 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
    • MoCap4ROS2 Setup
    • OptiTrack Robot Applications
    • Outdoor Tracking Setup
  • DEVELOPER TOOLS
    • Developer Tools Overview
    • Camera SDK
      • Class: cCameraModule
      • Class: cUID
    • Motive API
      • Motive API: Quick Start Guide
      • Motive API Overview
      • Motive API: Function Reference
      • Motive API Camera Calibration
    • NatNet SDK
      • NatNet 4.1
      • 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: Remote Requests/Commands
      • NatNet: Sample Projects
      • NatNet: Unicast Data Subscription Commands
      • Latency Measurements
    • VRPN Sample
    • Peripheral API: Glove Devices
  • SKELETON MARKER SETS
    • Full Body
      • Baseline (41)
      • Core (50)
      • Biomech (57)
      • Conventional (39)
    • Full Body + Fingers
      • Baseline + Passive Fingers (49)
      • Baseline + Active Fingers (57)
      • Core + Passive Fingers (54)
      • Core + Active Fingers (62)
    • Upper
      • Baseline Upper (25)
      • Conventional Upper (27)
    • Lower
      • Baseline Lower (20)
      • Helen Hayes Lower (19)
      • Conventional Lower (16)
    • Hand and Fingers
      • Left/Right Hand (4) Active
      • Left/Right Hand (10) Active + Passive
      • Active Finger Marker Set
    • Glove Device Setup
      • Manus Glove Setup
      • StretchSense Glove Setup
    • Rizzoli Marker Sets
    • Entertainment Marker Sets
    • Rigid Body Skeleton Marker Set
  • GENERAL TROUBLESHOOTING
    • Licensing Troubleshooting
    • Windows 11 Optimization for Realtime Applications
    • Network Troubleshooting
    • Troubleshooting Q&A
    • Running Motive on High DPI Displays
    • Firewall Settings
Powered by GitBook
On this page
  • Overview
  • Switch Requirements
  • Power Budget and Camera Power Requirements
  • Redundant Power Supply
  • PoE Switch Types
  • SFP Module
  • Managed Features
  • VLANs Not Supported
  • Ethernet Cable Requirements
  • Cable Types
  • Electromagnetic Shielding
  • Tools for Cable Management
  • Camera Network Setup
  • Setup Steps
  • Ethernet Camera System Diagrams
  • eSync2
  • Final Steps

Was this helpful?

Export as PDF
  1. HARDWARE
  2. Ethernet Camera Network Setup

Cabling and Load Balancing

A guide to cabling and connecting your OptiTrack camera system.

PreviousWindows 10 Network SettingsNextSwitch Configuration for PrimeX 120

Last updated 1 month ago

Was this helpful?

Overview

PrimeX and SlimX cameras use Ethernet cables for power and to connect to the camera network. To handle the camera data throughput, cables and networking hardware (switches, NIC) must be able to transmit at 1 Gigabit to avoid data loss. For networks with color cameras or a large camera count, we recommend using a 10 Gigabit network.

For best performance, we recommend that all OptiTrack camera systems run on an independent, isolated network.

This page covers the following topics:

  • Switches and power load balancing.

  • Ethernet cable types and which cables to use in an OptiTrack system.

  • Recommended network configurations for small and large camera systems.

  • Adding an eSync2 for synchronization.

  • Checking for system errors in Motive.

Switch Requirements

Network switches form the backbone of an Ethernet-based OptiTrack camera system, providing the most reliable and direct communication between cameras and the Motive PC.

We thoroughly test and validate the switches we offer for quality and load balancing, and ship all products pre-configured for easy installation right out of the box.

For product specifications, please visit the section of our website. for additional information.

Power Budget and Camera Power Requirements

Switches also power the cameras. The total Watts a switch can provide is known as its Power (or PoE) Budget. The Watts needed to power all of the attached powered devices must be within the Power Budget for best performance.

The number of cameras any one switch can support varies based on the total amount of power drawn by the cameras. For example, a 65 W switch can run 4 PrimeX 13 PoE cameras, which require 15.4 W each to power:

4 x 15.4 W = 61.6 W

61.6 W < 65 W

If the total Watts required exceeds the Power Budget, cameras may experience power failures, causing random disconnects and reconnects, or they may fail to appear in Motive.

Network switches provided by OptiTrack include a label to specify the number of cameras supported:

Redundant Power Supply

Depending on which OptiTrack cameras are used, a switch may not have a large enough power budget to use every one of its ports. In a larger camera setup, this can result in multiple switches with unused ports. In this case, we recommend connecting each switch to a Redundant Power Supply (RPS) to extend its power budget.

For example, a 24-port switch may have a 370W power budget, supporting 12 PoE+ cameras that require 30W to power. If the same 24-port switch is connected to an RPS, it can now power all 24 PoE+ cameras (each with a 30W power requirement) utilizing all 24 of the ports on the switch.

PoE Switch Types

PoE switches are categorized based on the maximum power level that individual ports can supply. The table below shows the power output of the various types of PoE switches and lists the current camera models that require each power level.

PoE Type
Max Watts / Port
Cameras

PoE

15.4 W

PrimeX 13 or 13W, SlimX 13, SlimX 41, VersaX 41

PoE+

30 W

PrimeX 22, PrimeX 41 or 41W, Prime Color, VersaX 41N or 41W

PoE++

71 - 90 W (based on length)

PrimeX 120, SlimX 120, VersaX 120, 120N, or 120W

Power Requirements for External Devices

When calculating the number of switches needed, include the eSync2 (if used) and all BaseStations needed for the capture:

  • eSync2: 4.4W

  • BaseStation: 2.2W

  • Wired AnchorPuck: 22W

  • Wired CinePuck: 9W

SFP Module

A Small Form-Factor Pluggable Module (SFP Module) is a transceiver that inserts into an SFP port on the switch to allow the switch to accommodate different connection types than just the standard RJ45 Ethernet ports. This can include higher speed copper or fiber optic connections.

SFP modules work with specific brands and models of switches. Always confirm that the module is compatible with the switch before you purchase the SFP module.

Smaller systems may not need an SFP port to uplink camera data to Motive. OptiTrack offers an SFP module with switches intended for heavily loaded systems (i.e., those with larger camera counts or Prime Color Camera systems).

When SFP ports are not required, use any standard Ethernet port on the switch to uplink data to Motive.

Managed Features

Switches often include functions for managing network traffic that can interfere with the camera data and should be turned off. While these features are critical to a corporate LAN or other network with internet access, they can cause dropped frames, loss of frame data, camera disconnection, and other issues on a camera system.

For example, features such as Broadcast Storm Control may identify large data transmissions from the cameras as an attack on the network and potentially shut down the associated ports on the switch, disconnecting the camera(s) in the process.

OptiTrack switches ship with these management features disabled.

VLANs Not Supported

Ports on a switch can be partitioned into separate network segments known as Virtual Local Area Networks, or VLANs. Your IT department may use these to allow one switch to provide a virtually isolated network for the camera system and access to the corporate LAN and internet. This is not a supported configuration for an OptiTrack camera system.

OptiTrack does not support the use of VLANs for camera systems. If you are connected to a VLAN and are experiencing issues, we recommend truly isolating the camera system on its own switch.

Ethernet Cable Requirements

Cable Types

There are multiple categories of Ethernet cables, each with different specifications for maximum data transmission rate and cable length.

Cable Type
Max Speed/Length
Max Bandwidth
Diameter

Cat6

10 Gb/s (55 m)

250 MHz

6.1 mm

Cat6a

10 Gb/s (100 m)

500 MHz

8.38 mm

Cat7/a

100 Gb/s (15 m*)

600 or 1000 MHz

8.51 mm

Cat8

40 Gb/s (30 m*)

2000 MHz

8.66 mm

*In general, the maximum cable length for an Ethernet cable is 100 m. While Cat7 and Cat8 cables can transmit data at higher rates, it reduces the maximum distance the data can travel before signal loss occurs.

  • Cat6a cables are recommended.

  • Cat5 or Cat5e cables run at lower speeds and are not supported.

  • Cat7 and Cat8 cables will work, but do not offer any added benefits to offset the increased cost.

What about fiber optic cables?

While fiber optic cables can transmit data over greater distances than Ethernet, they do not provide power and as such cannot be used to connect cameras.

A fiber optic connection can be used to connect to the Motive PC, but is not recommended unless the distance between the Motive PC and the switch is greater than 100 m.

Round vs. Flat

Round cables are better for long distances and high data transmission speeds. They are more insulated, easier to install without issues, and more durable, making them our recommended choice.

Flat cables should not be used on an OptiTrack network as they are highly susceptible to cross talk and EMI.

Electromagnetic Shielding

Electromagnetic shielding protects cables from cross talk, electromagnetic interference (EMI), and radio frequency interference (RFI), all of which can result in loss of data or stalled cameras.

Shielding also protects the cameras from electrostatic discharge (ESD), which can damage them.

Ethernet cables are categorized based on the type of shielding they have overall and whether individual twisted pairs are also shielded.

As more shielding is added to a cable, its flexibility decreases and its weight increases. These factors should be taken into account prior to purchasing cables and in planning the overall weight-load of the speed rail used to mount the cameras.

Overall shielding wraps around all of the twisted pairs, directly below the PVC jacket. This shield can be a braided screen (S), foil (F), or both (SF). Cables without an overall shield are designated with a (U).

Individual Twisted pairs can be shielded with foil (FTP), or left unshielded (UTP).

Examples of cable shielding types:

  • S/UTP: The cable has a braided screen overall, with no shielding on the individual twisted pairs.

  • SF/FTP: The cable has two overall shields: a braided screen over a foil shield. The individual twisted pairs are shielded with foil.

  • U/UTP: The cable has no overall shield or shields on the individual twisted pairs. We do not recommend using these type of cables in an OptiTrack camera system.

Unshielded cables (U/UTP) do not protect the cameras from Electrostatic Discharge (ESD), which can damage the camera. Do not use unshielded cables in environments where ESD exposure is a risk.

Tools for Cable Management

  • Gaffers Tape: This offers a good solution for covering a small run of wires on the floor.

  • Labels: Label both ends of each cable before connecting the PC and cameras to the switch(es). This will allow you to easily identify the port where the camera is connected.

  • Velcro Strips: These work best for cable bundling in flexible setups. While Velcro may take more effort to remove then plastic zip ties, they can be reused multiple times and create less clutter when changes are made to the setup.

  • Truss Cable Management Clip: This is a specialty product used for Truss cabling. Clips help with cable organization, but can be size restrictive for a large bundle of cables.

  • Wire Conduit: These products cover the entire cable bundle. They are size-restrictive and can be difficult to put on or take off.

  • Floor Cable Covers: This product offers the best solution for covering floor cables, however they can be quite bulky.

Camera Network Setup

In addition to camera count, the type of video being captured can affect the system's bandwidth needs. Reference video modes (Grayscale and MJPEG) and color video require significantly more bandwidth than object mode.

As noted above, always use 10 Gigabit shielded Ethernet cables (Cat6a or above) and a 10 Gigabit uplink switch to connect to the Motive PC, to accommodate the high data traffic. Make sure the NIC installed in the host PC can accommodate 10Gbps.

Setup Steps

Connect the Motive PC

Start by connecting the Motive (host) PC to the camera network's PoE switch via a Cat6a Ethernet cable. When the network includes multiple switches, connect the host to the aggregator switch.

If the computer used for capture is also connected to an existing network, such as a Corporate LAN, use a second Ethernet port or add-on NIC to connect the computer to the camera network.

When the Motive PC is connected to multiple networks, disable all Windows Firewall settings while using the mocap system.

DO NOT connect any third-party devices to the camera network.

Connect the Ethernet Cameras to the PoE Switch(es)

Connect Other System Devices

Connect any BaseStation(s) needed for the active devices directly to the aggregator switch, if used.

When the network includes multiple switches, connect the eSync2 to the aggregator switch. See the section below for more details on connecting the eSync2.

Power the Switches

The switch(es) must be powered on to power the cameras. To completely shut down the camera system, power off the network switch(es).

For best performance, do not connect devices other than the computer to the camera network. Add-on network cards should be installed if additional Ethernet ports are required for the Motive PC.

Ethernet Camera System Diagrams

These configurations have been tested for optimal use and safety. Deviating from them may negatively impact system performance.

Adding a Second Switch

A second switch can be connected to the primary switch via an uplink port, with the primary serving as the aggregation switch for the camera network. This is the only configuration where two camera switches can be daisy-chained together.

If additional switches are needed, a separate aggregation switch is required, so each switch has a direct connection to the aggregator. Please see the Multiple PoE Switches (High Camera Counts) tab for more details.

Uplink Switch: For systems that require multiple PoE switches, connect all of the switches to an uplink aggregation switch to link to the host PC. Ethernet ports on the aggregation switch can be used to connect cameras.

The switches must be connected in a star topology with the uplink switch at the central node, connecting to the Motive PC.

NEVER daisy chain multiple PoE switches in series; doing so can introduce latency to the system.

eSync2

External devices can include timecode inputs such as Video Genlock or Precision Time Protocol, or output devices such as force plates or NI-DAQ devices.

Only one eSync2 is needed per system. When one is used, it is the master in the synchronization chain.

With large camera systems, connect the eSync to the aggregator switch via a standard Ethernet port for more stable camera synchronization.

The eSync2 includes a 12V power cable to power the sync hub separately if the aggregator switch doesn't support PoE.

Final Steps

If you're unsure if you need an switch with an SFP port and an SFP module, please reach out to either our or teams.

The number of cameras in the system determine how the network is configured. The show the recommended wiring setup for either a small or large camera system.

Using Cat6a or above cables, connect the individual cameras to the Ethernet switch based on the scheme established when designing the camera network.

Use an synchronization hub to connect external devices such as force plates or Video Genlock to the camera network. The eSync connects to the PoE switch using an Ethernet cable.

The is a synchronization hub used to integrate external devices to an Ethernet-based mocap system. The set the timecode, input trigger, and other settings to ensure all devices on the camera network are in sync.

All of the connected cameras should now be listed in the and display in the when you start Motive. Make sure all of the connected cameras are properly listed in Motive.

Open the status and verify there are no current errors. The example below shows the sequence of errors that occur when a camera is disconnected. Look also for dropped frames, which may indicate a problem with how the system is delivering the camera data. Please refer to the for more details.

Sync and Networking Accessories
Contact Sales
Sales
Support
eSync2
eSync2
eSync2 properties
Devices pane
3D viewport
Log pane
troubleshooting section
diagrams below
power budget and load balancing
Power Requirements Label from an OptiTrack-supplied Switch.
Click image to enlarge.
An Ethernet PoE/PoE+ Gigabit switch.
An example of an SFP module.
Always use Round Cat6 or Cat6a cables.
Diagram showing the different networks that may be available on a Motive PC.
Connecting a network with a single switch.
Click image to enlarge.
The eSync 2 output and input ports descriptions
Devices Pane with 4 Tracking Cameras installed.
Status Log Pane with errors.