How do I stream from Pegasus to Jack?

1. In Jack click Modules > Motion Capture > Devices and choose Vicon

2. Set the vicon Host field to (If everything is running on same PC and default output port set in Pegasus)

  • May need to change rotation so rigid bodies are in correct position in relation to the human model (added later)

3. Connect.

4. In the menu bar click Human > Create > Default Male.

5. In Menu Bar click Modules > Motion Capture > Tracking.

6. Click Add.

7. When a new dialogue appears, select the human model in the scene and click Add Pair.

8. Back in the Tracking dialogue click Constrain.

9. In the Vicon Dialogue click Start.

 The above will start streaming from Pegasus into Jack.

Still need help?

How do I configure LabView to connect to Vicon DataStream SDK?

Below you will find an explanation on how to get started with the Vicon Datastream SDK and Labview.

You will also need to download the LabVIEW.exe.config:


The LabVIEW.exe.config file needs to be placed in the root Labview folder for example:

C:\Program Files\National Instruments\LabVIEW 2017 this my change depending on your operating system and Labview version (2010, 2013, 2014 and 2017 supported).

More details with regards to the config file can be found on the National Instruments website:

National Instruments

Steps to Configure Labview

1. Install:

 Vicon DataStream SDK 1.7.1

2. Create a Folder on your PC to contain all your LabView Projects for example:

C:\Users\Public\Documents\08 ThirdParty Software\Labview\LabviewProjects

3. Copy all the DataStream SDK files from C:\Program Files\Vicon\DataStream SDK\Win64\dotNET and place in C:\Users\Public\Documents\08 ThirdParty Software\Labview\LabviewProjects

4. Launch LabView 2017 (64bit)

5. Select Create Project

6. Double click Blank Project

7. Save your Project in the C:\Users\Public\Documents\08 ThirdParty Software\Labview\LabviewProjects folder created in Step 2

8. In the Project select File > New VI

9. In the New pop-up Window select Blank VI

10. In the Block Diagram Panel, right mouse click > select Connectivity > .NET > Constructor

11. Place the .NET Constructor in the Block Diagram

12. In the Assembly, select Browse and in the Look in: option browse to C:\Users\Public\Documents\08 ThirdParty Software\Labview\LabviewProjects

13. Select ViconDataStreamSDK_DotNET.dll

14. The .NET Constructor in the Block Diagram will now display ViconDataStreamSDK_DotNET(

Still need help?

Which digital plug-ins(*.vdd) are supported in Nexus?

The following companies provide digital plug-ins for there devices to work in Nexus 2.1.1 and Nexus 1.8.5:

Device Company
EMG Delsys
Force Plates AMTI
Kistler by Prophysics
Analog Card NIDAQ by Prophysics

Please contact the above companies for the latest versions.

Still need help?

What is proDAQ?

proDAQ is a plug-in developed by Prophysics AG that allows a National Instruments Data Acquisition (DAQ) board to stream data directly into Nexus thus allowing analog data to be streamed and captured without a Lock or Giganet LAB.

Still need help?

Which version of Nexus supports the proDAQ Plug-in?

The proDAQ Plug-in is supported in the current release versions of Nexus 2 and Nexus 1.8.5.

If you are running an earlier version of Nexus 1 you can either update to the current release version of Nexus, 1.8.5, or you can contact Prophysics AG at for an earlier version of the proDAQ Plug-in.

Still need help?

Where can I find the proDAQ Plug-in for Nexus?

To download the proDAQ Plug-in please contact Prophysics AG at:

Still need help?

How can I license the proDAQ Plug-in?

After installing the proDAQ plug-in, launch Nexus. You will be prompted to obtain a licence for the plug-in. You need to enter your name, email and affiliation, and send off a Prophysics Licence Request (PLR) file to

Still need help?

What is proEMG?

proEMG software is designed to make the acquisition and processing of EMG signals easy. There are three version of proEMG; proEMG Lite, proEMG Stand-Alone and proEMG Vicon Plug-ins. The proEMG Vicon Plug-in implements all the advanced processing functions available in the proEMG Stand-Alone as plug-ins accessible from the Vicon Nexus and Vicon Workstation pipelines. The actual data capture is done with the Vicon software.

Still need help?

Which version of Nexus supports the proEMG Plug-in?

The proEMG Plug-in is supported in the current release versions of Nexus 2 and Nexus 1.8.5.

Still need help?

How can I license the proEMG Vicon Plug-in?

After installing the proEMG Vicon plug-in, launch Nexus and run either the proEMG Automatic Processing or proEMG Processing Window pipeline operations. During this process you will be prompted to obtain a licence for the plug-in.

You need to enter your name, email and affiliation, and send off a Prophysics Licence Request (PLR) file to

Still need help?

Where can I find the proEMG installer?

To download the proEMG installer please contact Prophysics AG at

Still need help?

Which Basler drivers are supported in Nexus 2?

If Basler digital cameras will be connected to Nexus 2.6, ensure you have updated to the Basler Pylon5 SDK and drivers (v5.0.0), which are available from the Vicon website.

If you are using an Intel i340, i350 or i210 network card, when you install the drivers, select the option for Filter drivers, not Performance drivers


The Pylon5 driver supports:

  • Basler GigE cameras under both Windows 10 and Windows 7.
  • Basler FireWire cameras (A600 series) under Windows 7 only.
Still need help?

What is the Oxford Foot Model?

The current release version of Nexus 2 includes the Oxford Foot Model.

The Oxford Foot Model was developed and validated by the Nuffield Orthopaedic Centre in collaboration with Oxford University. The Vicon implementation of the Oxford Foot Model provides users with an easy-to use plug-in which can be included in the processing pipelines of Nexus 1.

The Oxford Foot Model Plug-in is designed to fit straight into the pipeline with the usual gait plug-ins such as the Woltring Filter, Gait Cycle event detection, and Plug-in Gait.

The Oxford Foot Model Installer and Release Notes can be downloaded from the associated pages below.

Still need help?

What is the sequence of rotations/ order of graph output for the Oxford Foot Model? What are positive/negative values?

Hindfoot and forefoot graphs are output in the sequence:
1. Sagittal plane; 2. Transverse plane;  3. Frontal plane.

Positive is dorsiflexion, inversion/supination, internal rotation/adduction. 

Still need help?

Can the Oxford Foot Model be used in contexts other than walking?

 It has been used in running, stair climbing and jumping. You just need to make sure camera spatial and temporal resolution are adequate and markers are stuck on well! 

Still need help?

Does the Oxford Foot Model output global angles?

Yes, for the tibia (TIBA) and hindfoot (HFTFL).  

You need to make sure the $TravelDirectionX parameter is correct (“1” when x represents walking direction and “0” when y represents walking direction)

Still need help?

In the Oxford Foot Model what do you use the hindfoot and forefoot flat options for?

Generally the “forefoot flat” option is not being used as most children in particular don’t stand with their forefeet flat on the floor. “Hindfoot flat” can be use if they can stand with heels down. If using PlugInGait in conjunction with the foot model, then it is necessary to rerun the PlugInGait model after the foot model in the static trial, as a new HEE marker is created by the foot model code to be used by the PlugInGait model (since the HEE marker cannot be placed in the correct position due to other markers being present on the calcaneus). The original HEE marker position is maintained as the Hindfoot segment origin.

Still need help?

In the Oxford Foot Model what is the arch height index?

The arch height index is calculated as the perpendicular distance of the P1M marker from the plane defined by D1M, P5M and D5M divided by foot length (TOE – HEE). The midfoot is considered as a linking mechanism and is currently not directly modelled.

Still need help?

Why is the knee rotation graph different in the Oxford Foot Model compared to Plug-in Gait?

The Oxford Foot Model code uses the “torsioned” tibia to calculate knee angles (ie taking tibial torsion into account) whilst the Plug-in Gait model uses the “untorsioned” tibia (ie knee rotation is zero in the static trial).

Still need help?

Is tibial torsion included in the Oxford Foot Model?

Yes, the model won’t run without a value in the “tibial torsion” field. This can be manually entered or else calculated in your normal way.

Still need help?