0
  • No products in the cart.

NEXUS

Data capture software for clinical gait, biomechanics and sports science customers

Download

All-inclusive modeling and processing tool for movement analysis

With a host of automated features, intelligent processing and flexible controls, Nexus allows you to turn a spotlight on your research.

View datasheet

Nexus 2
new features

Capture precise and repeatable data

To give you significant speed and accuracy improvements when processing your data, labeling in Nexus is intelligent. The new data-processing engine also allows real-time subject calibration feedback and automatically initializes the labeling of your subject – no need to label manually.

Powerful modeling both native and compatible

Whether your modeling needs are for quick in-class tuition or for comprehensive research pipeline integration, Nexus has the solution for your needs. Nexus has direct native pipeline integration allowing you to processing your data using scripts created in Vicon Bodybuilder, Python, MATLAB, and now Vicon ProCalc.

Automatic quality assessment

By automatically detecting gaps and labeling quality in your data, Nexus 2 presents an informative, visual overview of your trial. The expanded set of gap filling options and automatic donor selection allows for quick data correction if needed.

Real time

Nexus uses our core intelligent algorithms, making it the most robust, repeatable and reliable real-time labeling and skeletal solving solution available for biomechanics. But real time is much more than labeling and solving. Our easy-to-set-up wizard bio-feedback features, allow the user and the subject to understand what is happening in the mocap volume from beyond the PC: whether that’s by audio signals, TTL logic controls of other devices, or simply driving graphical kinematic displays.

Customize your workflow

The Biomechanics Workflow builder creates a series of steps to combine data collection and offline processing. It also makes it simple to get started with the SCoRE and SARA Functional Calibration.

Manage your data

ProEclipse is the data management system for Vicon clinical gait analysis, biomechanics and sports science software users. With improved database navigation and intelligent search functionality, ProEclipse will enable you to find your data with ease.

New for 2.10 - Blue Trident IMU integration

Add inertial sensors into the optical world. Vicon IMUs can be added into your environment as digital devices, allowing you collect synchronized optical and inertial data in one platform.

TECHNICAL INFORMATION

SPECIFICATION

DOCUMENTATION

DOWNLOADS

FAQS

What is the recommended PC specification to run my Vicon Nexus System?

Vicon recommends the following three specifications for use with your Vicon Nexus System. If you are using an older version of Vicon software, please contact Vicon to ensure there are no issues or driver limitations if you are upgrading your PC. Your choice depends on your application requirements and the size of your system.

Please note the following:

  • Windows 10 (64bit) Tested and Supported OS
  • .NET Framework 4.5 above
  • 2 GB NVIDIA Quadro P620 Tested and Supported Graphics Cards
  • INTEL ETHERNET i350/i340 T4 SERVER ADAPTER RJ45 PCI−E and INTEL ETHERNET i210−T1 GBE NIC Tested and Supported Network Cards (NIC)
  • Corsair Neutron GTX CSSD 240GB 2.5 OR Samsung SSD 850 EVO 250GB – Tested and Supported

Standard PC:

Dell Precision XL Tower 5820
Intel Xeon Processor W-2123 (3.6GHz, 3.9GHz Turbo, 4C, 8.25M Cache)
16GB (2x8GB) 2666MHz DDR4 RDIMM ECC
2 x 2TB 3.5inch Serial ATA (7,200 Rpm) Hard Drive
Non RAID
8x Slimline DVD+/-RW Drive
2 GB NVIDIA Quadro P620
Windows 10 Pro English
INTEL ETHERNET i350 T4 SERVER ADAPTER RJ45 PCI−E – to connect Vicon System

Dual Video PC:

Dell Precision XL Tower 5820
Intel Xeon Processor W-2123 (3.6GHz, 3.9GHz Turbo, 4C, 8.25M Cache)
16GB (2x8GB) 2666MHz DDR4 RDIMM ECC
2 x 2TB 3.5inch Serial ATA (7,200 Rpm) Hard Drive
Non RAID
8x Slimline DVD+/-RW Drive
2 GB NVIDIA Quadro P620
Windows 10 Pro English
1 Samsung EVO 860 SSD 250GB 2.5 inch – to write video data
1 off INTEL ETHERNET i350 T4 SERVER ADAPTER RJ45 PCI−E – to connect Vicon System and Video Cameras

Quad Video PC:

Dell Precision XL Tower 5820
Intel Xeon Processor W-2123 (3.6GHz, 3.9GHz Turbo, 4C, 8.25M Cache)
16GB (2x8GB) 2666MHz DDR4 RDIMM ECC
2 x 2TB 3.5inch Serial ATA (7,200 Rpm) Hard Drive
Non RAID
16x Slimline DVD+/-RW Drive
2 GB NVIDIA Quadro P620
Windows 10 Pro English
2 Samsung EVO 860 SSD 250GB 2.5 inch – to write video data
1 off INTEL ETHERNET i350 T4 SERVER ADAPTER RJ45 PCI−E – to connect Video Cameras
1 off INTEL ETHERNET i210−T1 GBE NIC – to connect Vicon System

What operating system (OS) can I use with my Vicon Software?

Current release version Windows 10 Windows 7* Linux OSX
Shōgun 1.2.1 64 bit 64 bit* x x
Nexus 2.9.2 64 bit 64 bit* x x
Tracker 3.7.0 64 bit 64 bit* x x
Polygon 4.4.5 64 bit 64 bit* x x
CaraLive 1.3.0 64 bit 64 bit* x x
CaraPost 1.2.0 64 bit 64 bit* x x
Pegasus 1.2.1 64 bit 64 bit* x x
ProCalc 1.3.0 64 bit 64 bit* x x
ProEclipse 1.3.1 64 bit 64 bit* x x
DataStream SDK 1.8.0 64 bit 64 bit* 64 bit 10.11
Bodybuilder 3.6.4 64 bit 64 bit* x x

Please do note:

  1. Recommended and fully supported in Windows 10 (64bit) — with .NET Framework 4.5 and above
  2. * Although Vicon Software may install and function under other Microsoft Windows operating systems
    (Compatibility tested only Windows 7 (64bit) — with .NET Framework 4.5) , this is not officially supported or recommended by Vicon.
    After January 14, 2020, Microsoft will no longer provide security updates and support for PCs with Windows 7. If you continue to use Windows 7 after support has ended, your PC will still work, but it may become more vulnerable to security risks.
  3. For Legacy version please contact Vicon Support

How do I set up my network card?

1. Open the Network and Sharing Center and navigate to Change Adapter Settings. Vicon Vantage/Vero cameras are designated to one port.  For each Vue (or Bonita Video) camera connected, there will be additional network port used.

2. Right click on the proper port and go into the Properties. The Local Area Connection Properties window will open. Make sure only Internet Protocol Version 4 (TCP/IPv4) is selected.

3. Select Internet Protocol Version 4 (TCP/IPv4) from the list and select Properties to assign the proper IP address.

a .Vantage/Vero cameras will have the following IP Address: 192.168.10.1 and Subnet Mask of: 255.255.255.0

b. The first VUE camera will have the following IP Address: 192.168.10.2 and Subnet Mask of 255.255.255.0

c. Any additional VUE cameras the last IP value is incrementally increased by one. For example, the second VUE camera will be 192.168.10.3.

Select OK to close out of the Internet Protocol Version 4 (TCP/IPv4) Properties.  And OK again to close out of the Local Area Connection Properties.  This will make sure all changes have been saved.

4. Feel free to rename the network port so it is easily identifiable. Such as ViconMX, VUE1 or VUE2

For further assistance please refer to the Configuring Ports section of the PCSetupforViconSystems.pdf found in Downloads > Documentation

Download Nexus

Download File

Nexus_2.9.3

File Name: Nexus_2.9.3.120183h.zip

Vicon Nexus: Vicon’s all-inclusive modeling and processing tool for movement analysis.

With a host of automated features, intelligent processing, and flexible controls, Nexus 2 lets you focus on your research and not on your software.

Nexus 2.9.3 is a patch release, which addresses CGM2 issues reported since Nexus 2.9.2. Nexus 2.9.3 incorporates CGM2 version 3.2.13.

New features:
1) Bones added to the CGM2 MKR file.
2) MKR file exports after CGM2 operation.

Addressed issues:

  • Updated CGM2 to version 3.2.13.
  • CGM2 global angle outputs corrected.
  • Trials located in paths with non-ASCII characters now process correctly.

 

Requirements

  • Licensing: Nexus 2.x Safenet license.
  • IMU sensors are ONLY supported for Windows 10 (64-bit).
  • IMU sensors require the following driver to be installed: CP210x USB to UART Bridge VCP Drivers. (Driver link: https://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx)
  • IMU improvements – To access new IMU frequency modes, the Blue Thunder sensor requires firmware 1.3. Users are required to update the Blue Thunder sensor firmware using the IMU Research app. This app is currently under review by Apple for release.
  • Supported OS(s): Fully supported under Windows 10, works under Windows 7.
  • Recommended and fully supported – Windows 10 (64-bit), with .NET Framework 4.5 and later.

Nexus_2.9.2

File Name: Nexus_2.9.2.118349h.zip

Vicon Nexus: Vicon’s all-inclusive modeling and processing tool for movement analysis.

With a host of automated features, intelligent processing and flexible controls, Nexus 2 lets you focus on your research and not on your software.

Nexus 2.9.2 is a patch release for Vicon Nexus, which addresses issues reported since Nexus 2.9.1.

Addressed Issues:

  • T-Series indicator light now flashes during calibration to indicate progress.
  • Video calibration activates when you click Calibrate.
  • When in event ID mode, selecting the next event does not deselect the video display.

Requirements

  • Licensing: Nexus 2.x Safenet license.
  • IMU sensors are ONLY supported for Windows 10 (64-bit).
  • IMU sensors require the following driver to be installed: CP210x USB to UART Bridge VCP Drivers. (Driver link: https://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx)
  • IMU improvements – To access new IMU frequency modes, the Blue Thunder Sensor requires firmware 1.3. Users are required to update the Blue Thunder sensor firmware using the IMU Research app.
  • Supported OS(s): Fully supported under Windows 10, works under Windows 7.
  • Recommended and fully supported – Windows 10 (64-bit), with .NET Framework 4.5 and later.

Nexus _2.9.1

Abstract

File Name: Nexus_2.9.1.117599h.zip

Vicon Nexus: Vicon’s all-inclusive modelling and processing tool for movement analysis.

With a host of automated features, intelligent processing and flexible controls, Nexus 2 lets you focus on your research and not on your software.

Nexus 2.9.1 is a patch release for Vicon Nexus, which addresses issues reported since Nexus 2.9.

Addressed Issues:

  • CGM2 (Conventional Gait Model 2) addressed the inversion of boolean parameters upon the model execution.
  • Kistler digital force plates are correctly read by Nexus in Offline mode.
  • Using Auto Initialize for subject calibration markers only will apply the scaled values.
  • For T-Series cameras, the light indicator will only be present if the camera is selected.
  • Retarget Processing Output Level removed.

Requirements

  • Licensing: Nexus 2.x Safenet license.
  • IMU Sensors are ONLY supported in Windows 10 (64-bit).
  • IMU Sensors require the following driver to be installed: CP210x USB to UART Bridge VCP Drivers. (Driver link: https://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx)
  • IMU Improvements – To access new IMU frequency modes the Blue Thunder Sensor requires firmware 1.3. Users are required to update the Blue Thunder Sensor firmware using IMU Research app. This app is currently under review by Apple for release.
  • Recommended and fully supported – Windows 10 (64bit) — with .NET Framework 4.5 and above.

Nexus _2.9.0

Abstract

File Name: Nexus_2.9.0.116558h.zip

Vicon Nexus: Vicon’s All-inclusive modelling and processing tool for movement analysis.

With a host of automated features, intelligent processing and flexible controls, Nexus 2 lets you focus on your research and not on your software.

Nexus 2.9.0 is a general release for Vicon Nexus. This update introduces a native Conventional Gait Model 2.

New Features:

  1. Native Conventional Gait Model 2.
  2. Hybrid CAST Visual3D Labeling Template.
  3. Data Quality Information in the Data Management Pane.
  4. Ability to calculate residual analysis for your devices using a pipeline operation.
  5. Foot strike counter viewable in the video camera window.
  6. Visualise model outputs in Polygon when using functional VSTs to compare with Plugin Gait outputs.
  7. Load view type when in event identification mode.
  8. Timebar event identification includes optionable settings to zoom or not to zoom into the timebar.
  9. Delay compensation executable via a pipeline operation.
  10. Delete timebar events from only one context via the timebar or using a pipeline operation.
  11. Mirror the video camera in the camera view.
  12. Quick Report will normalise and overlay all traces from one trial.
  13. Run a Monitor in a pipeline.
  14. SDK command to identify active subjects.
  15. Auto-scale the calibration L-frame when setting the origin.
  16. Additional toast pop-up control settings.
  17. GetDeviceDataFrom API Function.

Addressed Issues:

  • The 3D orthogonal view will display markers to match the default view parameter.
  • The 3D view will no longer flip the force plate number displays when zooming out.
  • Advance parameters added to the video view settings.
  • Adding a segment to Plug-in Gait will not remove the existing parameterization.
  • Offline grayscale circle fitting turns off correctly when disabled.
  • Control card error message updated.
  • Blank ‘start frame’ value in ‘load range’ will be treated as invalid when using ‘show trial loading options’.
  • The ‘load frames from the range’ option in ‘trial loading options’ displays start and end frame correctly.
  • AGW (advance gait workflow) Static Trial type will open only if AGW lower body workflow is selected.
  • Large operations save to history.
  • Repeatably executing auto-initialize subject will not shrink the labeling skeleton.
  • Contexts are refreshed within the timebar when moving between trials.
  • Nexus buffer efficiency improved.
  • Plugin Gait ground reaction force outputs display correct forceplate units.
  • Using drag and drop for a Subject, requires an active session to display.
  • Quick Report update to allow the ability to load trials using the same name.
  • When masking, only the selected cameras will set their LEDs to cyan.
  • Selecting a marker will display the whole trial trajectory in the graph view.
  • Updates to reading XML marker node errors.
  • Fix the calculation of progression frame when using short (<20 frames) static trials.
  • Non-zeroed force plates will correctly assign kinetic gait cycles to the timebar.
  • Real-time detected events will appear on the timebar when capturing in simple capture mode.
  • AGW (advance gait workflow) combined processing operation parameter is corrected to default settings.
  • Searching for modelled markers using MATLAB or Python, will no longer generate a virtual marker if the marker position as changed.
  • Identification of events correctly occurs when using a Boolean AND monitor whilst scrolling through a trial.

Requirements

  • Licensing: Nexus 2.x Safenet license.
  • IMU Sensors are ONLY supported in Windows 10 (64-bit).
  • IMU Sensors require the following driver to be installed: CP210x USB to UART Bridge VCP Drivers. (Driver link: https://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx)
  • IMU Improvements – To access new IMU frequency modes the Blue Thunder Sensor requires firmware 1.3. Users are required to update the Blue Thunder Sensor firmware using IMU Research app. This app is currently under review by Apple for release.
  • Recommended and fully supported – Windows 10 (64bit) — with .NET Framework 4.5 and above.

Nexus_2.8.2

Abstract

File Name: Nexus_2.8.2.114586h.zip

Vicon Nexus: Vicon’s All-inclusive modelling and processing tool for movement analysis.

With a host of automated features, intelligent processing and flexible controls, Nexus 2 lets you focus on your research and not on your software.

Nexus 2.8.2 is a patch release for Vicon Nexus, which addresses issues reported since Nexus 2.8.1.

Addressed Issues:

  • Ability to load Quick Reports without the presence of the Plug-in Gait Model.
  • Improvements in adding a trial to Quick Report using the Batch Process.
  • Quick Report correctly displays model outputs for later trials that are not present in earlier imported trials.
  • Updates to calculating the Plug-in Gait Thorax Centre of Mass.
  • Updates to Timebar viewing options and settings, including when adding custom contexts via the SDK and display colours.
  • Video Calibration mode will no longer automatically overwrite dirty system configurations
  • Corrected an intermittent picking offset in the 3D workspace.
  • Data capture will no longer be interrupted when pausing/unpausing the 3D workspace.
  • Improvements to sending and reading DataStream data.
  • Improvements to saving long data capture trials to C3D files.
  • SDK GetSubjectNames will no longer report Quick Report Subjects in the outputs.
  • Before and Stop After settings for data capture are properly persisted when these options are disabled.
  • Capture volume will not be set to target volume settings upon a fresh install.
  • Additional log error message information will be provided when the functional calibration fails to execute.

Requirements

  • Licensing: Nexus 2.x Safenet license.
  • IMU Sensors are ONLY supported in Windows 10 (64-bit).
  • IMU Sensors require the following driver to be installed: CP210x USB to UART Bridge VCP Drivers. (Driver link: https://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx)
  • IMU Improvements – To access new IMU frequency modes the Blue Thunder Sensor requires firmware 1.3. Users are required to update the Blue Thunder Sensor firmware using IMU Research app. This app is currently under review by Apple for release.
  • Supported OS(s): Fully supported under Window 10, work in Windows 7.

Nexus _2.8.1

Abstract

File Name: Nexus_2.8.1.111866h.zip

Vicon Nexus: Vicon’s All-inclusive modelling and processing tool for movement analysis.

With a host of automated features, intelligent processing and flexible controls, Nexus 2 lets you focus on your research and not on your software.

Nexus 2.8.1 is a patch release for Vicon Nexus, which addresses issues reported since Nexus 2.8.

Addressed Issues:

  • Pipeline operations allow the use of custom marker names to detect forceplate events, autocorrelate events, and calculate gait cycle parameters
  • Improvements to Nexus when loading X2D files
  • Rendering issue when reordering graphs resolved in Quick Report
  • Realtime Event Detection Monitor saves events to offline correctly
  • Using Boolean Monitors with OR statements
  • Data occlusions in model outputs will persist in the C3D files
  • Video calibration correctly draws the thresholded grayscale
  • Improvements to the video grayscale data alignment

Requirements

Licensing: Nexus 2.x Safenet license.

IMU Sensors are ONLY supported in Windows 10 (64-bit).

IMU Sensors require the following driver to be installed: CP210x USB to UART Bridge VCP Drivers. (Driver link: https://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx)

IMU Improvements: To access new IMU frequency modes the Blue Thunder Sensor requires firmware 1.3. Users are required to update the Blue Thunder Sensor firmware using IMU Research app. This app is currently under review by Apple for release.

Supported OS(s): Fully supported under Window 10, work in Windows 7.

Nexus _2.8.0

Abstract

File Name: Nexus_2.8.0.111014h.zip

Vicon Nexus: Vicon’s All-inclusive modelling and processing tool for movement analysis.

With a host of automated features, intelligent processing and flexible controls, Nexus 2 lets you focus on your research and not on your software.

Nexus 2.8. is a point release for Vicon Nexus, which includes improved accessibility of biomechanical models within Nexus and available functionality of IMeasureU Blue Thunder Sensors within Nexus.

New Features:

  1. Plug-in Gait Model has segmental center of mass outputs
  2. Improved Nexus Python SDK integration
  3. Improvements to working with IMUs within Nexus including a new IMeasureU Tab, new frequency modes (3-axis 1000Hz and 9-axis 500Hz).
  4. Ability to calculate step width and limp index
  5. Close trials using the SDK
  6. Firmware notifications
  7. Updates to Vicon software

Addressed Issues:

  • Device data is no longer cleared when you run a post-capture pipeline.
  • An error in selecting the ProCalc Operation Scheme parameters has been resolved.
  • Inconsistent BodyBuilder kinetic results between raw data and C3D data has been resolved.
  • Corrected sign on the normalized ground reaction force components when walking along the Y-axis.
  • Generic analog data devices are now permitted to contain multiple outputs of the same type.
  • NexusSegment objects for MATLAB have been improved to match the definitions used by Bodylanguage.
  • Improved over-rotation correction for joint and segment outputs.
  • Force plate footstrike indicators are now displayed in the order of the force plate IDs.
  • Dynamic Plug-in Gait no longer creates joint angle data for missing segments.
  • Exporting an MOT file now generates free moments.
  • Improvements to AMTI digital forces plates when butterflies are enabled within Nexus.
  • Improvements to hotkeys Ctrl+[ and Ctrl+] when clicking Go Live.
  • Offline playback via the DSSDK has been resolved.
  • Auto-correlated time bar events are now retained for long treadmill trials containing more than 255 events.
  • Kin Fit Kinematics Euler_XYZ and SegmentGlobal Euler_XYZ angles now match.
  • Improvements to third-party video transfer.
  • You can now create a model output with both Velocity and Angular Velocity component types.
  • When exporting IMUs via ASCII export, if no unique name is provided the device user ID will be added to the column headers.
  • Export motion file (.mot) no longer creates multiple files for trials with multiple force plates.
  • Third-party force plates settings will be retained when switching between system files.
  • The Export TRC pipeline operation now enables you to exclude the subject name in the header if required.

Requirements

Licensing: Nexus 2.x Safenet license.

IMU Sensors are ONLY supported in Windows 10 (64-bit).

IMU Sensors require the following driver to be installed: CP210x USB to UART Bridge VCP Drivers. (Driver link: https://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx)

IMU Improvements: To access new IMU frequency modes the Blue Thunder Sensor requires firmware 1.3. Users are required to update the Blue Thunder Sensor firmware using IMU Research app. This app is currently under review by Apple for release.

Supported OS(s): Fully supported under Window 10, work in Windows 7.

Nexus _2.7.1

Abstract

File Name: Nexus_2.7.1.107809h.zip

Nexus 2.7.1 is a patch release for Vicon Nexus. This update introduces support for the Vicon Lock Lab.

Nexus 2.7.1 also corrects an issue with camera calibration that could result in calibrations taking longer (more frames). This was particularly evident during video calibrations.

Other fixes:

  • When running PIG MatLab with KADs, Thigh Rotations no longer revert to zero.
  • Corrected an issue that prevented Python arguments from being passed from Nexus to the system Python
  • Loading of long trials has been made more reliable.
  • Large trial processing histories no longer cause Nexus to hang when loading the trial.
  • When saving a trial, Nexus 2.7.1 corrected an issue where the heading ‘Processing’ would not be correctly written into the C3D file.

Requirements

  • Nexus 2.x Safenet license
  • IMU Sensors are ONLY supported in Windows 10 (64bit)
  • IMU Sensors require the following driver to be installed: CP210x USB to UART Bridge VCP Drivers. (Driver link: https://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx)

Nexus _2.7.0

Abstract

File Name: Nexus 2.7.0.106412h.zip

Vicon Nexus: Vicon’s All-inclusive modeling and processing tool for movement analysis.

With a host of automated features, intelligent processing and flexible controls, Nexus 2 lets you focus on your research and not on your software.

Nexus 2.7 is a point release for Vicon Nexus that adds functionality and address issues reported since the launch of Nexus 2.6. Nexus 2.7 is also the first version of Nexus that support Vicon’s new IMU sensors.

A highlighted list of feature additions and addressed issues can be found below.

Nexus 2.7 New Features

  1. Support for Vicon IMU Sensors
  2. Gait Cycle Visualization on the Nexus Timebar
  3. Display Variable Components in Quick Reports
  4. New Calibration Feedback Options i. Export Calibration Results as a CSV ii. Compare Calibrations iii. Set Calibration Threshold Values iv. Sort Calibration Columns
  5. A New Updated Log Notifications System
  6. ProCalc Pipeline Operation
  7. High pass filter Operation
  8. User Saved Sound Configurations
  9. Firmware Notifications
  10. Plug In Gait Joint Centres can now be Visualized
  11. Protect System Configuration Files (Read-Only)

Other Feature Additions:

  • Automatically show the monitors pane when a new monitor is added
  • Hotkey for gap fill – cyclic fill
  • Refresh subject from disk
  • New link to the Nexus model directory
  • Ignore the set reconstruction volume during calibration and set origin
  • Dikablis: prevent adding a calibration point when not in KinFit mode
  • Save/Load VSTs
  • SDK Version Info
  • Centre camera view on camera centre point

Issues Addressed:

  • Monitors correctly reinitialized when a new trial is loaded
  • Subjects now properly cleared when browsing to a non-session location
  • Increased storage capacity above 255 for modeled markers in C3D files
  • Corrected an issue displaying timecode when loading a cropped C3D without raw data
  • Matlab PiG no longer crashes when output values are indeterminate
  • Trial captures will not be abandoned when using capture before start with subsampled video
  • Graph horizontal range no longer becomes spontaneously unlocked
  • Nexus is more robust when opening an invalid C3D file

Known Issues:

  1. When collecting IMU sensor data at higher frequencies (500Hz), exceptionally long trial ( >30 mins) may show less reliable optical – IMU frame alignment.
  2. IMU sensor may require a manual re-connect in Nexus if they are out of communication range (Bluetooth) for an extended period.
  3. If streaming preview frame from an IMU sensor are not available at the time a trial capture is started, then data for that sensor may not be available in the trial.

Requirements

  • Nexus 2.x Safenet license
  • For the ProCalc pipeline operation – ProCal 1.2 must be installed.
  • IMU Sensors are ONLY supported in Windows 10 (64bit).
  • Nexus Recommended and fully supported in Windows 10 (64bit) — with .NET Framework 4.5 and above.
  • Nexus Compatibility tested in Windows 7 (64bit) — with .NET Framework 4.5.
  • 2 GB NVIDIA Quadro K620 Tested and Supported Graphics Cards.

Basler video cameras and Nexus 2.7

If Basler digital cameras will be connected to Nexus 2.7, 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.

Nexus _1.8.5

Abstract

File Name: Nexus_1.8.5.61009h_x86.zip

Nexus 1.8.5 addresses a single issue discovered following the release of 1.8.4 where force plate date collected via a digital plug-in will not correctly be written into the C3D file.

Requirements

  • A license for Vicon Nexus 1.x
  • Supported Hardware – Vicon MX-Series, F-Series, T-Series, Bonita, Bonita Video, Basler Video
  • Window 7 OS and supported hardware components : i340 Network card, M4 SSD hard drives(for Video Cameras).
  • Basler video cameras require Basler drivers 2.35

FAQs

Which Vicon systems are supported in Nexus 2?

Before you install Nexus 2, note the following limitations on supported systems:

  • Nexus only captures data from Vicon systems (including Vantage, T-Series, Bonita cameras and units).
  • Nexus 2 does not support connection to the Reference Video System (Nexus Slave application).

What are the reference video options for Nexus 2?

Nexus 2 supports the following reference video options:

  • Vue Camera – seamless integration via POE (require Intel i340 T4 or i350 T4 network card)
  • Bonita Video – seamless integration via POE or Giganet (require Intel i340 T4 or i350 T4 network card)
  • Basler Camera – download the appropriate Pylon driver (A601fc and m, A602fc and m, pia 1000-60gc, pia 640c and m)
  • Firewire IEEE 1394 Camcorder – the camcorders are supported as long as they are automatically detected within Windows. It is recommended that a four port firewire card is used instead of the onboard firewire card.

What is Link Aggregation and how do I set this up in my Vicon System?

Link aggregation is used to describe various methods for using multiple parallel network connections to increase throughput beyond the limit that one link (one connection) can achieve. Link aggregation is supported in Tracker 1.3+, Nexus 1.8.5+, Blade 2+.

When setting up Link Aggregation ensure that you have the correct Network cards (Intel i340-T4 or the Intel i350-T4 cards) installed on your capture PC. Once you have the correct Network card(s) follow these steps:

1. Make sure your three network ports have fixed IP addresses 192.168.10.1, 192.168.10.2 and 192.168.10.3. A maximum of nine NICs are allowed (192.168.10.1 – 192.168.10.9 inclusive).

2. Connect the 192.168.10.1 and 192.168.10.2 ports to one Giganet/Power over Ethernet switch (POE) and 192.168.10.3 to the other Giganet/POE. You will need an extra cable connecting your Giganets/POEs.

3. Run Tracker/Nexus/Blade, set your workspace to Camera and select all the cameras in the System pane (you will need to expand Vicon Cameras). Please do note that there might be slight differences between the three applications.

4. Turn the Giganet/POE connected to 192.168.10.3 off then select all the cameras that just went red in the System pane.

Select the Destination IP Address drop-down and select 192.168.10.3.

5. Select the remaining (green) cameras then scroll down their Properties, select the Destination IP Address drop-down and select 192.168.10.2.

6. Turn the Giganet/POE connected to 192.168.10.3 back on. Select all the cameras in the System pane.

Save your System configuration.

How do I solve a Force Plate calibration file not loading into Nexus?

When you add a force plate in Nexus, you are also required to install the Calibration File into the appropriate dialogue box. The Calibration file generally comes with the device from the manufacturer. This can be a .Plt file or an .acl file for AMTI plates.

There may be occasion when the file located does not populate the drop down box on selection within Nexus.

In this instance, you may need to hand edit the file to remove any white space or extra characters, such as Commas and Carriage returns, in order for it to be read by Nexus.

Open the file in a text editor, and remove any white space and/or extra characters not required.

   

Where can I find the latest Software documentation?

You can find the latest documentation for all current versions of software at here:

DOCUMENTATION HOME

Vicon Core Software will also install documentation/help guide when you install the software.

Once installed, launch the software and select Help > View Installed Help

The following software will install Help:

Nexus 2, Shōgun, Tracker 3, Blade 3, Pegasus, CaraLive, CaraPost, Polygon 4

What are the new features in Nexus 2?

New features and updates in Vicon Nexus 2.8

Nexus 2.8 introduces the following new features and updates.

  • Plug-in Gait Model has segmental center of mass outputs
  • Improved Nexus Python SDK integration
  • Improvements to working with IMUs within Nexus including a new IMeasureU Tab, new frequency modes (3-axis 1000Hz and 9-axis 500Hz)
  • Ability to calculate step width and limp index
  • Close trials using the SDK
  • Firmware notifications
New features and updates in Vicon Nexus 2.7

Nexus 2.7 introduces the following new features and updates.

  • Cycle visualization in the time bar
  • Display selected components in Quick Reports
  • Improved feedback for camera calibration
  • Enhanced Log notifications
  • New ProCalc pipeline operation
  • Stream and capture IMU data
New features and updates in Vicon Nexus 2.6

Nexus 2.6 introduces the following new features and updates.

  • Create Quick Reports
  • Improved Event Detection
  • Updated Data Management
  • Automatic camera numbering
  • Quick Capture Mode
  • Combined force plate outputs
  • Video file transfer displays a file counter
  • Visual feedback in Resources pane on bumped cameras
  • Region of Interest frame specification
New features and updates in Vicon Nexus 2.5

Nexus 2.5 introduces the following new features and updates.

  • Create custom timebar events
  • Subject Viewer pane
  • Enhanced feedback on data quality
  • Gait Deviation Index (GDI) score now available
  • Display of additional gap filling information
  • New video file transcode pipeline operation
  • Manage Vicon Control authorizations
  • Ability to delete model outputs
  • Update custom VST values
  • Auto-hide the Communications pane
New features and updates in Vicon Nexus 2.3

Nexus 2.3 introduces the following new features and updates.

  • Auto Start Stop Capture
  • Auto Crop Trial
  • Automated Assessment of Foot Strikes
  • Automated Gap-Filling
  • Export the 3D Workspace to AVI
  • Cyclic Pattern Fill
  • Processing History
  • Sensor Windowing Display
  • Select Transferred/Non-transferred files
  • Hotkeys for Start/Stop Capture
  • Select/Deselect All Pipeline Operations
  • Sweep Select for Manual Masking
  • Subject Parameters – Set All to Default
  • Progress Bar for Matlab operations
New features and updates in Vicon Nexus 2.2

Nexus 2.2 introduces the following new features and updates.

  • Native Oxford Foot Model
  • Greater choice of joint types
  • Advanced MATLAB modeling
  • Compatibility with Vicon Vantage systems
  • Support for Vicon Lock+ control units
  • Compatibility with Vicon Control
New features and updates in Vicon Nexus 2.1

Nexus 2.1 introduced the following new features and updates:

  • Compatibility with Vicon Lock
  • Additional video standards and timecode options
  • Support for mixed Vicon Bonita and T-series systems
  • Cross-plate foot strike feature
  • Improved system calibration refinement
New features and functions in Vicon Nexus 2.0

The following new features were introduced in Nexus 2.0:

  • Updated user interface
  • Updated licensing: VAULT – SafeNet
  • Active Communications window
  • Enhanced database navigation and search
  • Updates to Pipeline operations
  • Automated data quality feedback tab
  • New processing engine and improved labeling
  • Biomechanics workflow
  • MATLAB interface
  • Python interface

What Gap Filling Algorithms are used Nexus 2?

There are four gap filling options available in Nexus 2.

Woltring (Quintic spline)

This has slightly different behaviour for the pipeline operation compared to the manual fill.

Both versions generate a quintic spline using valid frames around the gap as seed data. The gap is filled using the interpolated values from the spline. If there are insufficient frames surrounding the gap, the fill is rejected.

Pipeline

Searches backwards and forwards from the gap looking for (Number of Gap Frames / 2) + 5 consecutive valid frames on each side, but will accept a minimum of 5 valid frames on either or both sides if the preferred range is not available. Searches the entire length of the clip looking for the valid frame ranges.

Manual

Searches up to (Number of Gap Frames / 2) + 5 frames backwards and forwards from the gap. Requires a minimum of 10 valid frames in this range – these are not required to be consecutive.

Pattern

Manual fill operation only.

Generates linear interpolations between the valid frames either side of the gap and between the same frames in a donor trajectory. The interpolated value in the gap trajectory is then offset by the difference between the interpolated and true values in the donor trajectory. Mathematically:

Let F(t) be the value in the position of the trajectory to fill at frame t, and D(t) that of the donor trajectory. Let t0 and t1 be the valid frames before and after the gap, respectively. Then if we define the interpolated position V of trajectory Gat frame t as:

V(G(t)) = ( G(t1)-G(t0) ) * ( t – t0 ) / ( t1-t0 ) + G(t0)

then:

F(t) = V(F(t)) – V(D(t)) + D(t)

Rejects the fill if the donor trajectory has any invalid frames within the gap region, or if the donor or fill trajectory are invalid at either t0 or t1

Rigid Body

Takes a number of trajectories and assumes these move as a rigid body. The gaps in the selected trajectory are filled as if this trajectory is also a part of the same body. Manual filling is restricted to 3 donor trajectories and fills gaps in a single trajectory; the pipeline operation will use as many donor trajectories as possible, and will attempt to fill the gaps in each selected trajectory using all the other selected trajectories as donors.

Define the state at frame t as an (n x 3) matrix M(t) whose rows are the position vectors of the donor trajectories, P(t) as the position of the fill trajectory, and tx as a reference frame in which the positions of the donors and fill trajectory are all known.

We transform M into M by subtracting the mean value of the column i from each row entry M(t)(i,j):

M(i,j) = M(i,j) – O(j), where O(j) = ( (i=1->n) ∑ M(i,j) / n )

We then create a covariance matrix C = M(tx)’ M(t) and perform an SVD such that C = U S V*

We take L to be the the identity matrix, except that if det( V U* ) < 0, then L(3,3) = -1. Then we can generate a rotation matrix R(tx) = V L U* (This is effectively the Kabsch algorithm to find the optimal rotation between two point clouds)

The interpolated position at frame t based on reference frame tx is then defined as:

G(t, tx) = R(tx) ( P(t) – O(tx) ) + O(t)

and

F(t) = ( G(t, t1) – G(t, t0) ) * ( t – t0 ) / ( t1 – t0 ) + G(t, t0)

where t0 and t1 are the valid frames before and after the gap, respectively.

The fill is rejected if there are fewer than 3 valid donor trajectories at any frame t0 <= t <= t1, or if the trajectory to fill is invalid at t0 or t1.

Kinematic

Determines the fill based on the position and orientation of a segment. The manual operation operates on a single selected trajectory, while the pipeline operation attempts to fill gaps in all trajectories associated with the selected segment.

The mathematics of this operation are simply:

G(t, tx) = R(t) R(tx)’ ( P(t) – O(tx) ) + O(t)

and

F(t) = ( G(t, t1) – G(t, t0) ) * ( t – t0 ) / ( t1 – t0 ) + G(t, t0)

where R(t) is the rotation matrix defining the orientation of the segment in the world at frame t, O(t) is the origin position of the segment at frame t, and t0 and t1 are the valid frames before and after the gap, respectively.

The fill is rejected if there are no kinematics for the selected segment at any frame t0 <= t <= t1, or if the trajectory to fill is invalid at t0 or t1.

How do I configure force plates for analog capture in Nexus?

To configure force plates for analog data capture:

1. Go to the Resources pane > Systems tab, click the Go Live button.

2. In the System tab, right-click the Devices node, point to Add Analog Device and select the proper force plates.

The selected force plate node automatically expands to display the newly created device. If the appropriate type is not displayed, contact Vicon Support.

3. In the Properties section at the bottom of the System resources pane, select Show Advanced.

4. In the General section

  • Either load the manufacturer’s Calibration File.
  • OR, enter the Calibration Matrix 6×6 Matrix values manually

5. In the Source section

  • From the drop-down list, select a Source to which the device is attached (i.e. Lock+ or Giganet MX)
  • Select the appropriate pins for the force plate channels.
  • Select the Gain for the Source from the choice of gains available for the Lock+.

Please Note: Expand force plate node to expose the Force, Moment and CoP (Center of Pressure) channels. A Green Arrow indicated a connected source device and a Yellow yield indicates that a channel has not been assigned a pin.

6. In the Dimensions section, add in values from force plate manufacturer’s manual if not already entered

7. In the Positions section, position the force plate in respect to the wand and the origin of the plate.

8. In the Orientation section, orient the plate so it makes sense in respect to your capture volume.

9. In the Origin section, add in values from force plate manufacturer’s manual if not already entered.

10. To tare the force plate at zero load:

  • Complete a hardware zero with the force plate Amplifier, if possible.
  • Click the Zero Level browse button and enter the matrix properties.
  • You can also tare the force plate by right-clicking on the force plate name in the System resources tree and selecting Zero Level.

11. In the capture volume, have someone step onto the force plate. You should see the force vector display in real time.

  • Switch to a Graph View pane. If necessary, select Components from the Graph Type drop-down list. A real-time graph of the Force output is displayed. Verify that the vertical (Fz) force component is equal to [known mass * 9.81].

For further details on configuring analog force plates, please refer to the Configure Force Plates section of the installed Nexus Help.

How do I load large trials into Nexus?

To facilitate working with very large unprocessed data files, you can choose which files will be loaded (.x2d camera data and/or .x1d analog data), and how many frames of the trial are loaded.

To do this click Show Trial Loading Options on the ProEclipse/Data Management toolbar at the top right of the ProEclipse/Data Management window. A new area will appear called Raw Data Loading Options

How to work with large trial data:

1. In order to select only required frames, in the Raw Data Loading Options area, select Load Range From and type the frame to start from in the first box and the end frame in the second box.

2. If required, choose whether to load both MX centroid/grayscale data (X2D) and raw analog data (X1D) files, or only one of these options.

3. Process the file(s) as normal.

Only the selected range and files will be processed, it is recommended that you save the section under a new name using File | Copy As…

What are the requirements for MATLAB and Nexus 2?

Vicon Nexus 2 is compatible with, and has been tested with MATLAB R2013b. Nexus may function with other versions of MATLAB, but other versions have not been extensively tested by Vicon.

To use MATLAB with Vicon Nexus 2, ensure that, in addition to installing MATLAB, you install .NET Framework version 4.5

How do I get started with MATLAB Modeling?

To set MATLAB path:

Once Nexus, MATLAB and the appropriate .NET Framework version are installed, you will want to set the path.

Windows 7: Go to the Start Menu > All Programs > Vicon > Nexus 2.X > Set MATLAB Path.

Windows 10:  Start > All Apps > Vicon > Set MATLAB Path

This will give MATLAB access to the Nexus scripting functions.

To Configure MAT for scripting with Nexus:

Within MATLAB, create an instance of the ViconNexus object to get access to its methods; type the following line in the Command Window:

vicon = ViconNexus()

To obtain MATLAB Command List:

To see which functions you have access to write the following line in the Command Window:

vicon.DisplayCommandList()

To obtain MATLAB Command Help:

If you need guidance for the use of any of the displayed functions you can run either of the following lines in the Command Window.

vicon.DisplayCommandHelp('commandName')

For example:

vicon.DisplayCommandHelp('GetTrajectory')

OR

help commandName

For example:

help GetTrajectory

To troubleshoot MATLAB Scripts:

To troubleshoot or run your script, you must have a trial open within Nexus

For further information please see the installed or online help guide.  This can be found under the Help tab within Nexus.

Nexus MATLAB troubleshooting

You can find the latest MATLAB troubleshooting tips here:

MATLAB TROUBLESHOOTING

Solutions include:

  • Nexus unresponsive when running script
  • MATLAB Error when constructing an instance
  • Generic type error

and many more.

How can I access the Python Command List and Help for Nexus 2?

To launch Python:

1. Click Start and point to All Programs (or press the Windows key) and then start to type Python.

2. Click the Python symbol.

3. To automatically configure Python for scripting with Nexus, at the command prompt, enter the following:

import ViconNexus
vicon = ViconNexus.ViconNexus()

To obtain Python Command List:

Ensure you have launched and configured Python as described above, then at the Python command prompt, enter:

vicon.DisplayCommandList()

To obtain Python Comman Help:

To obtain help on each command that you can use with Nexus, at the Python command prompt, enter:

vicon.DisplayCommandHelp(’commandName’)

Where commandName is the command for which you want to display help.

For example, the following command displays help on GetTrajectory:

vicon.DisplayCommandHelp(’GetTrajectory’)

Help on GetTrajectory is displayed.

How can I view VVid files outside of Nexus?

VVID files can be viewed by using the VVID Viewer.

The VVID Video Viewer is a tool that allows users to view Nexus’ propriety raw video format – VVID.

This file can be downloaded from the Downloads > Utilities and SDKs section.

What are the required subject measurements for Plug-in Gait?

The measurements required for both upper and lower body models include mass, height, leg length, knee width, ankle width, shoulder offset, elbow width, wrist width, and hand thickness.

These measurements should all be entered in either kilograms or millimetres. All lengths or distances will be required in millimetres. The measurements for inter-ASIS distance, ASIS-trochanter distance, and tibial torsion are all optional entries. If they are not entered in, the model will calculate them.

Here are the precise required measurements for the model:

Mass: The mass of the subject in Kilograms (2.2lb=1kg)

Height: The height of the subject.

Leg length: Measured from the ASIS to the medial malleolus. If a patient cannot straighten his/her legs, take the measurement in two pieces: ASIS to knee and knee to medial malleolus.

Knee width: Measurement of the knee width about the flexion axis.

Ankle width: Measurement of the ankle width about the medial and lateral malleoli.

Shoulder offset: The vertical distance from the center of the glenohumeral joint to the marker on the acromion clavicular joint. Some researchers have used the (anterior/posterior girth)/2 to establish a guideline for the parameter.

Elbow width: The distance between the medial and lateral epicondyles of the humerus.

Wrist width: Should probably be called “wrist thickness.” It is the distance between the anterior (palm side) and posterior (back) side of the wrist in the anatomical position.

Hand thickness: The distance between the dorsal and palmar surfaces of the hand at the point where you attach the hand marker.

The following measurements are optional and/or calculated by the model:

Inter-ASIS distance: The model will calculate this distance based on the position of the LASI and RASI markers. If you are collecting data on an obese patient and cannot properly place the ASIS markers, place those markers laterally and preserve the vector direction and level of the ASIS. Palpate the LASI and RASI points and manually measure this distance, then input into the appropriate field.

Head Angle: The absolute angle of the head with the global coordinate system. This is calculated for you if you check the option box when processing the static trial.

ASIS-Trochanter distance: The perpendicular distance from the trochanter to the ASIS point. If this value is not entered, then a regression formula is used to calculate the hip joint center. If this value is entered, it will be factored into an equation which represents the hip joint center.

Tibial torsion: The angle between the ankle flexion axis and the knee flexion axis. The sign convention is that if a negative value of tibial torsion is entered, the ankle flexion/extension axis will be adjusted from the KAD’s defined position to a position dictated by the tibial torsion value.

Thigh rotation offset: When a KAD is used, this value is calculated to account for the position of the thigh marker. By using the KAD, placement of the thigh marker in the plane of the hip joint center and the knee joint center is not crucial. Please note that if you do not use a KAD, this value will be reported as zero because the model is assuming that the thigh marker has been placed exactly in the plane of the hip joint center and the knee joint center. This value is calculated for you.

Shank rotation offset: Similar to the thigh rotation offset. This value is calculated in a KAD is present and removes the importance of placing the shank marker in the exact plane of the knee joint center and ankle joint center. If you do not use a KAD, these values will be zero. This value is calculated for you.

What are the shoulder angle calculations in Plug-in Gait?

The first step in the shoulder modelling process is the definition of the shoulder, elbow and wrist centres and the Thorax, Clavicle and Humerus segments. The shoulder angle calculations are then based on YXZ Euler angle rotations between the Thorax and the Humerus Segments as follows:

  • LShoulderAngles 1 Flexion Anti-clockwise about Thorax Y, 2 Abduction Anti-clockwise about Thorax X, 3 Internal Rotation Anti-clockwise about Thorax Z
  • RShoulderAngles 1 Flexion Anti-clockwise about Thorax Y, 2 Abduction Clockwise about Thorax X, 3 Internal Rotation Clockwise about Thorax Z

The explanation for the sometimes strange angles seen when using the above method for determining shoulder motion is the occurrence of ‘Gimbal Lock’ and the quirk in clinical descriptions of motion known as ‘Codman’s Paradox’. ‘Gimbal Lock’. Gimbal Lock occurs when using Euler angles and any of the rotation angles becomes close to 90 degrees, for example lifting the arm to point directly sideways or in front (shoulder abduction about an anterior axis or shoulder flexion about a lateral axis respectively).

In either of these positions the other two axes of rotation become aligned with one another, making it impossible to distinguish them from one another, a singularity occurs and the solution to the calculation of angles becomes unobtainable. For example, assume that the humerus is being rotated in relation to the thorax in the order Y,X,Z and that the rotation about the X-axis is 90 degrees. In such a situation, rotation in the Y-axis is performed first and correctly. The X-axis rotation also occurs correctly BUT rotates the Z axis onto the Y axis. Thus, any rotation in the Y-axis can also be interpreted as a rotation about the Z-axis.

True gimbal lock is rare, arising only when two axes are close to perfectly aligned. ‘Codman’s Paradox’: The second issue however, is that in each non-singular case there are two possible angular solutions, giving rise to the phenomenon of “Codman’s Paradox” in anatomy (Codman, E.A. (1934). The Shoulder. Rupture of the Supraspinatus Tendon and other Lesions in or about the Subacromial Bursa. Boston: Thomas Todd Company), where different combinations of numerical values of the three angles produce similar physical orientations of the segment. This is not actually a paradox, but a consequence of the non-commutative nature of three-dimensional rotations and can be mathematically explained through the properties of rotation matrices (Politti, J.C., Goroso, G., Valentinuzzi, M.E., & Bravo, O. (1998).

Codman’s Paradox of the Arm Rotations is Not a Paradox: Mathematical Validation. Medical Engineering & Physics, 20, 257-260). Codman proposed that the completely elevated humerus could be shown to be in either extreme external rotation or in extreme internal rotation by lowering it either in the coronal or sagittal plane respectively, without allowing any rotation about the humeral longitudinal axis.

For a demonstration of this, follow the sequence below:

  1. Place the arm at the side, elbow flexed to 90 degrees and the forearm internally rotated across the stomach.
  2. Elevate the arm 180 degrees in the sagittal plane.
  3. Lower the arm 180 degrees to the side in the coronal plane.
  4. Note that the forearm now points 180 degrees externally rotated from its original position with no rotation about the humeral longitudinal axis actually having occurred.
  5. Appreciate the difficulty then in describing whether the fully elevated humerus was internally or externally rotated.

This ambiguity can cause switching between one solution and the other, resulting in sudden discontinuities. A combination of ‘Gimbal Lock’ and ‘Codman’s Paradox’ can lead to unexpected results when joint modelling is carried out.

What are the Upper Body Segment angles from Plug-in Gait?

The table below displays the Upper Body Segment angles from Plug-in Gait.

All Upper Body angles are calculate in rotation order YXZ.

As Euler angles are calculated, each rotation causes the axis for the subsequent rotation to be shifted. X’ indicates an axis which has been acted upon and shifted by one previous rotation, X’’ indicates a rotation axis which has been acted upon and shifted by two previous rotations.

Angles Positive Rotation Axis Direction Angles Positive Rotation Axis Direction
LHeadAngles 1 Backward Tilt Prg.Fm. Y Clockwise RHeadAngles 1 Backward Tilt Prg.Fm. Y Clockwise
2 Right Tilt Prg.Fm. X’ Anti-clockwise 2 Left Tilt Prg.Fm. X’ Clockwise
3 Right Rotation Prg.Fm. Z’’ Clockwise 3 Left Rotation Prg.Fm. Z’’ Anti-clockwise
LThoraxAngles 1 Backward Tilt Prg.Fm. Y Clockwise RThoraxAngles 1 Backward Tilt Prg.Fm. Y Clockwise
2 Right Tilt Prg.Fm. X’ Anti-clockwise 2 Left Tilt Prg.Fm. X’ Clockwise
3 Right Rotation Prg.Fm. Z’’ Clockwise 3 Left Rotation Prg.Fm. Z’’ Anti-clockwise
LNeckAngles 1 Forward Tilt Thorax Y Clockwise RNeckAngles 1 Forward Tilt Thorax Y Clockwise
2 Left Tilt Thorax X’ Clockwise 2 Right Tilt Thorax X’ Anti-clockwise
3 Left Rotation Thorax Z’’ Clockwise 3 Right Rotation Thorax Z’’ Anti-clockwise
LSpineAngles 1 Forward Thorax Tilt Pelvis Y Anti-clockwise RSpineAngles 1 Forward Thorax Tilt Pelvis Y Anti-clockwise
2 Left Thorax Tilt Pelvis X’ Clockwise 2 Right Thorax Tilt Pelvis X’ Anti-clockwise
3 Left Thorax Rotation Pelvis Z’’ Anti-clockwise 3 Right Thorax Rotation Pelvis Z’’ Clockwise
LShoulderAngles 1 Flexion Thorax Y Anti-clockwise RShoulderAngles 1 Flexion Thorax Y Anti-clockwise
2 Abduction Thorax X’ Anti-clockwise 2 Abduction Thorax X’ Clockwise
3 Internal Rotation Thorax Z’’ Anti-clockwise 3 Internal Rotation Thorax Z’’ Clockwise
LElbowAngles 1 Flexion Humeral Y Anti-clockwise RElbowAngles 1 Flexion Humeral Y Clockwise
2 Humeral X’ 2 Humeral X’
3 Humeral Z’’ 3 Humeral Z’’
LWristAngles 1 Ulnar Deviation Radius X Clockwise RWristAngles 1 Ulnar Deviation Radius X Anti-clockwise
2 Extension Radius Y’ Clockwise 2 Extension Radius Y’ Clockwise
3 Internal Rotation Radius Z’’ Clockwise 3 Internal Rotation Radius Z’’ Anti-clockwise

What are the Lower Body Segment angles from Plug-in Gait?

The table below displays the Lower Body Segment angles from Plug-in Gait.

All Lower Body angles are calculate in rotation order YXZ except for Ankle Angles which are calculated in order YZX.

As Euler angles are calculated, each rotation causes the axis for the subsequent rotation to be shifted. X’ indicates an axis which has been acted upon and shifted by one previous rotation, X’’ indicates a rotation axis which has been acted upon and shifted by two previous rotations.

Angles Positive Rotation Axis Direction Angles Positive Direction Axis Direction
LPelvisAngles 1 Anterior Tilt Prg.Fm. Y Anti-clockwise RPelvisAngles 1 Anterior Tilt Prg.Fm. Y Anti-clockwise
2 Upward Obliquity Prg.Fm. X’ Anti-clockwise 2 Upward Obliquity Prg.Fm. X’ Clockwise
3 Internal Rotation Prg.Fm. Z’’ Clockwise 3 Internal Rotation Prg.Fm. Z’’ Anti-clockwise
LFootProgressAngles 1 Prg.Fm. Y RFootProgressAngles 1 Prg.Fm. Y
2 Prg.Fm. X’ 2 Prg.Fm. X’
3 Internal Rotation Prg.Fm. Z’’ Clockwise 3 Internal Rotation Prg.Fm. Z’’ Anti-clockwise
LHipAngles 1 Flexion Pelvis Y Clockwise RHipAngles 1 Flexion Pelvis Y Clockwise
2 Adduction Pelvis X’ Clockwise 2 Adduction Pelvis X’ Anti-clockwise
3 Internal Rotation Pelvis Z’’ Clockwise 3 Internal Rotation Pelvis Z’’ Anti-clockwise
LKneeAngles 1 Flexion Thigh Y Anti-clockwise RKneeAngles 1 Flexion Thigh Y Anti-clockwise
2 Varus/Adduction Thigh X’ Clockwise 2 Varus/Adduction Thigh X’ Anti-clockwise
3 Internal Rotation Thigh Z’’ Clockwise 3 Internal Rotation Thigh Z’’ Anti-clockwise
LAnkleAngles 1 Dorsiflexion Tibia Y Clockwise RAnkleAngles 1 Dorsiflexion Tibia Y Clockwise
2 Inversion/ Adduction Tibia X’’ Clockwise 2 Inversion/ Adduction Tibia X’’ Anti-clockwise
3 Internal Rotation Tibia Z’ Clockwise 3 Internal Rotation Tibia Z’ Anti-clockwise

How does Nexus (Plug-in Gait) and Polygon calculate Gait Cycle Parameters (Spatial and Temporal)?

In Nexus the Generate Gait Cycle Parameters Pipeline Operation can be used in conjunction with the Gait events to calculate standard Gait Cycle Spatial and Temporal Parameters. These Parameters and available units (the units can be change in the Generate Gait Cycle Parameters Options box) are:

Cadence – 1/s; 1/min; steps/s; steps/min; strides/s; strides/min

Walking speed – m/s; cm/s; mm/s; in/s

Step Time – s; %

Foot Off/Contact events – s; %

Single/Double Support – s; %

Stride/Step Length – m; cm; mm; in

The Distance Parameters are based in the marker position at the time, by default the toe marker (LTOE for left and RTOE for right) is used for the calculation. This can be changed in the Options box of the Generate Gait Cycle Parameters Pipeline Operation.

The Parameters are based on the first cycle for each side where all the necessary events are found.

Polygon can re-calculate the parameters and can define the parameters in the first cycle or the average of all defined cycles.

Cadence: number of strides per unit time (usually per minute). The left and right cadence are first calculated separately based on either a single stride or an average of the defined gait cycles (this is a preference setting in Polygon). The overall cadence is the average of the left and the right.

Stride time: time between successive ipsilateral foot strikes.

Step time: time between contralateral and the following ipsilateral foot contact, expressed in seconds or %GC.

Foot contact/off events are all expressed relative to the ipsilateral gait cycle, either as absolute time from ipsilateral foot contact or as %GC, as per the Polygon preference. Single and double support calculations are only valid for walking, i.e. when the contralateral foot off/contact events happen within the ipsilateral stance phase.

Foot off: time of ipsilateral foot off.

Opposite foot contact: time of contralateral foot contact.

Opposite foot off: time of contralateral foot off.

Single support: time from contralateral foot off to contralateral foot contact.

Double support: time from ipsilateral foot contact to contralateral foot off plus time from contralateral foot contact to ipsilateral foot off.

Limp index: the foot contact to foot off time of the ipsilateral foot is divided by the foot off to foot contact time plus the double support time. In other words, the limp index calculates the time the ipsilateral foot is on the ground and divides it by the time the contralateral foot is on the ground during the ipsilateral GC.

All distance and speed measurements use a reference marker on each foot, by default the LTOE/RTOE markers, but this can be changed in the preferences. The marker’s position is evaluated in 3D at the time of the events.

Four 3D points are defined:

IP1 is the ipsilateral marker’s position at the first ipsilateral foot contact.

IP2 is the ipsilateral marker’s position at the second ipsilateral foot contact.

CP is the contralateral marker’s position at the contralateral foot contact.

CPP is CP projected onto the IP1 to IP2 vector.

Stride length: is the distance from IP1 to IP2.

Step length: is the distance from CPP to IP2.

Step width: is the distance from CP to CPP.

Walking speed: is stride length divided by stride time.

How do I import Data into a Polygon Report?

The Data Bar is empty until you import trial data (*.c3d files) that were processed in Vicon Nexus. Data can be imported from either the Data Manager (Eclipse) or the Home Ribbon. You can import a variety of files into Polygon reports, including web pages, videos, and more. Most files become panes within Polygon for which you can create hyperlinks. Files that you can import:

Vicon (*.c3d) Polygon External Data (*.pxd)
VCM Report (*.gcd) 3D Mesh (*.obj)
Marker Set (*.mkr) Adobe Acrobat (*.pdf)
Video (*.mpg, *.avi) PowerPoint (*.ppt, *.pptx)
Web Page HTM

Import Data from Data Manager (Eclipse)

Open the report for which you want to import data or create a new report.

On the Home ribbon, click the Data Manager button or press F2.

With Data Manager still open, double-click on the trial name you want to add to the report.

The Trial will appear in the Data Bar

When you are finished, close the Data Manager.

Import Data from the Home Ribbon

Import File:

Open the report for which you want to import data or create a new report.

On the Home ribbon, click Import File.

In the Import File dialog, browse to the location of the c3d file you want to import.

Double click on the c3d file (In the drop-down you can filter the file types – optional).

The Trial will appear in the Data Bar.

Import Video:

Open the report for which you want to import data or create a new report.

On the Home ribbon, click Import Video.

In the Import File dialog, browse to the location of the .avi or .mpg file you want to import.

Double click on the file.

The Video will appear in the Data Bar.

Import Web Page:

Click the Home button on the Ribbon.

Click the Import Web Page button.

In the window that opens, enter the web page URL.

Click OK.

The web page opens in an HTML window in the Report Workspace. Web pages can be accessed by clicking Multimedia Files in the upper portion of the Data Bar. Then double-click the web page in the lower portion of the Data Bar

Nexus General Workflow 1: Preparing your system (System Set-up, Masking, Calibration)

1. Make sure all analog and digital devices to be collected within Nexus are turned on. Wait at least 45 minutes after turning on the system to calibrate.

Please Note: Calibration should occur whenever cameras have had any movement.  Preferably, cameras are calibrated at least each day the system is used.

2. Open Nexus. All cameras will populate within the Systems tab automatically.

3. Select the appropriate System Configuration file for the data collection. Configured analog devices will populate under Devices. Add configured digital devices, right click on Devices > Add Digital Device and select the appropriate devices.

Verify analog/digital devices are set-up correctly.  For example, if there are any force plates, make sure the force vectors are correct.

4. Select all cameras and go to the Camera view. Verify all reflective material or markers have been removed from the volume. If a reflective area is unable to be removed, it will be masked.

5. Go to the Tools pane > System Preparation button > Mask Cameras. Select Start to mask the cameras. Existing masks will be removed and replaced with new masks.  Once all reflections are covered with a blue mask, select Stop.

6. Go to Calibrate Cameras and select Start. Nexus will begin calibration as the wand is moved throughout the volume. Once all cameras have recorded the wand for a specific number of frames Nexus will calculate feedback values.  Look at the Camera Calibration Feedback table to verify calibration was good.

7. Change the Camera view to 3D Perspective. Set the wand at the origin of the volume. Go to Set Volume Origin  > Start and then Set to position the cameras around the wand.

System preparation is now complete and you can move on to data capture.

Nexus General Workflow 2: Capturing Data (Calibration and Dynamic Trials)

1. Go to Data Management and make sure a Session folder has been created for the subject.

2. Go to the Resource pane > Subjects tab and create a new subject from a labeling skeleton.  The subject will be listed below with the associated labeling skeleton in parentheses.

3. Go to the Tools pane > Subject Preparation button for subject calibration. Have the subject stand in the middle of the volume in the base pose with all markers visible.  Select Start under Subject Calibration.  Only one good frame of data is needed.  Once a trial with all markers present has been captured select Stop.

Please Note: Workflow is intended for Plug-In Gait templates.  If using another you might need a Range of Motion calibration trial.

4. Nexus goes offline and opens the trial for immediate processing. Reconstruct the markers of the loaded trial. Run the AutoInitialize pipeline followed by Plug-in Gait Static to Calibrate the subject for labeling and Plug-in Gait.

Please Note: Check the accuracy of the marker labels (Hotkey: CTRL+Space) prior to running the calibration pipeline operations.

5. Save the Trial and Subject. Then go back online.

6. Dynamic Trials can now be collected. Select the Capture tab, go down to the Capture section and select Start to begin data collection.  Change the name of the trial from Subject Name Cal 02 to something that correlates with the data collection.

Can I use my Nexus 1.x Vicon Skeleton Template (VST) in Nexus 2.x?

To take advantage of the new Nexus 2.x labeling algorithms a Nexus 2.x VST must be used.  If all you have is a Nexus 1.x VST, please remake the VST within Nexus 2.x.  If you would like instructions on this process, please contact Vicon Support.

Why should I complete a subject calibration within Nexus?

Calibrating your subject allows Nexus to calculate subject-specific parameters with regards to the size of the subject and the exact placement of markers.  Calibration of the subject leads to better automatic labeling during Live capture and offline processing.  During subject calibration, subject-specific information is what enables a skeleton labeling template (VST) to be converted to a subject-specific labeling skeleton (VSK). If a VST is not calibrated to the subject then the subject markers will not label well, if at all.

The subject should be calibrated at the beginning of each capture session, not before each trial. You only need to recalibrate if the subject marker placement changes, for example, if a marker falls off, or if the markers are moved.

What does it mean to ‘Aim Cameras’ in Nexus?

Aiming cameras is useful for providing an initial, approximate calibration, before you fully calibrate the cameras.

To utilize Aim Cameras you will want to have your cameras roughly positioned within the volume.  Create a Target Volume, from the Window > Options, with the dimensions of the ideal capture volume.  Once configured, place the wand in the center of the capture volume and go to a camera view.

While in the Aim Camera mode, physically move the Vicon camera in the capture volume and check its coverage against the Target Volume.

Please Note: The Target Volume within the camera view will only be displayed if all 5 wand markers are visible.  Thus the camera might need focusing in order to circle fit the wand markers.

For step by step instructions with visualizations on this process, please refer to the Aim Vicon Cameras section of the installed Nexus help.

How do I determine a marker Status in Nexus?

When creating or modifying a template you will notice each marker has a Status property.  The Status of a marker is set to either Required, Optional or Calibration Only.  A marker status can affect the way a template reconstructs and labels.

Required: A required marker will need to be on the subject during the calibration trial as well as all dynamic trials

Calibration Only: These markers are used during the calibration trial and are then removed from the marker list for the dynamic trials.

Optional: If an optional marker is on the subject for calibration, Nexus will expect that marker to remain on the subject during all the dynamic trials.  If the marker is not present during calibration, the optional marker is removed from the marker list.

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

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

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

Please contact the above companies for the latest versions.

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.

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 [email protected] for an earlier version of the proDAQ Plug-in.

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

To download the proDAQ Plug-in please contact Prophysics AG at: [email protected]

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 [email protected]

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.

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.

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 [email protected]

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

Important

The Pylon5 driver supports:

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

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.

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.

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!

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)

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.

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.

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

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.

What is the recommended PC specification to run my Vicon Nexus System?

Vicon recommends the following three specifications for use with your Vicon Nexus System. If you are using an older version of Vicon software, please contact Vicon to ensure there are no issues or driver limitations if you are upgrading your PC. Your choice depends on your application requirements and the size of your system.

Please note the following:

  • Windows 10 (64bit) Tested and Supported OS
  • .NET Framework 4.5 above
  • 2 GB NVIDIA Quadro P620 Tested and Supported Graphics Cards
  • INTEL ETHERNET i350/i340 T4 SERVER ADAPTER RJ45 PCI−E and INTEL ETHERNET i210−T1 GBE NIC Tested and Supported Network Cards (NIC)
  • Corsair Neutron GTX CSSD 240GB 2.5 OR Samsung SSD 850 EVO 250GB – Tested and Supported

Standard PC

Dell Precision XL Tower 5820
Intel Xeon Processor W-2123 (3.6GHz, 3.9GHz Turbo, 4C, 8.25M Cache)
16GB (2x8GB) 2666MHz DDR4 RDIMM ECC
2 x 2TB 3.5inch Serial ATA (7,200 Rpm) Hard Drive
Non RAID
8x Slimline DVD+/-RW Drive
2 GB NVIDIA Quadro P620
Windows 10 Pro English
INTEL ETHERNET i350 T4 SERVER ADAPTER RJ45 PCI−E – to connect Vicon System

Dual Video PC

Dell Precision XL Tower 5820
Intel Xeon Processor W-2123 (3.6GHz, 3.9GHz Turbo, 4C, 8.25M Cache)
16GB (2x8GB) 2666MHz DDR4 RDIMM ECC
2 x 2TB 3.5inch Serial ATA (7,200 Rpm) Hard Drive
Non RAID
8x Slimline DVD+/-RW Drive
2 GB NVIDIA Quadro P620
Windows 10 Pro English
1 Samsung EVO 860 SSD 250GB 2.5 inch – to write video data
1 off INTEL ETHERNET i350 T4 SERVER ADAPTER RJ45 PCI−E – to connect Vicon System and Video Cameras

Quad Video PC

Dell Precision XL Tower 5820
Intel Xeon Processor W-2123 (3.6GHz, 3.9GHz Turbo, 4C, 8.25M Cache)
16GB (2x8GB) 2666MHz DDR4 RDIMM ECC
2 x 2TB 3.5inch Serial ATA (7,200 Rpm) Hard Drive
Non RAID
16x Slimline DVD+/-RW Drive
2 GB NVIDIA Quadro P620
Windows 10 Pro English
2 Samsung EVO 860 SSD 250GB 2.5 inch – to write video data
1 off INTEL ETHERNET i350 T4 SERVER ADAPTER RJ45 PCI−E – to connect Video Cameras
1 off INTEL ETHERNET i210−T1 GBE NIC – to connect Vicon System

What’s New in the Life Science Software?

Capture

The videos below will address capturing data within Nexus.

General Workflow for Capture

Data Capture Pane

Creating and Using Monitors

GET IN TOUCH

Vicon are here to support you on your Motion Capture journey. We’re happy to provide more information, answer questions and help you find the solution you need. Get in touch with our experts today.

STAY UP TO DATE

Get in touch

Newsletter signup

Please tell us a little more about yourself

I'm interested in:


Newsletter signup

Thanks for subscribing!

Please check your email for a confirmation message.

Catch up on the latest news

Whilst you wait for our next newsletter, maybe you would like to check out our latest news, or read our annual magazine ‘The Standard‘ for the latest industry news in detail.

Latest News

Female

Small Medium Large
Chest 78.7cm / 31in 85.1cm / 33.5in 87.6cm / 34.5in
Waist 63.5cm / 25in 68.6cm / 27in 78.7cm / 31in
Hips 81.3cm / 32in 86.4cm / 34in 91.4cm / 36in
Inside Leg 66cm / 26in 69.9cm / 27.5in 77.5cm / 30.5in

Male

Small Medium Large Extra Large
Chest 86.4cm / 34in 94cm / 37in 103cm / 40.6in 114.3cm / 44.5in
Waist 71.1cm / 28in 83.8cm / 33in 90cm / 35.4in 99.1cm / 39in
Hips 88.9cm / 35in 94cm / 37in 100cm / 39.4in 109.2cm / 43in
Inside Leg 66cm / 26in 69.2cm / 27.3in 71cm / 28.3in 81.3cm / 32in