Restoring communication with your MTi

There are various reasons why you may not be able to (properly) communicate with your MTi. This article acts as a set of guidelines to (re-)gain communication with your device. It addresses the MTi 1-series, 10-series and 100-series. If you are facing issues that are not covered in this article, or if these guidelines have not solved your communication issue, please contact Support


For the MTi 10-series and 100-series:

  • If you are using a USB to serial converter that is not supplied by Xsens, you will have to set the baud rate, specify its COM port and scan for that single port in MT Manager with the "Scan Single Port" button. When using the "Scan All Ports" button, MT Manager only scans for devices connected using Xsens converter cables.


It is important that you have the correct drivers installed.

  • If you are using the MTi with a cable that includes a USB to serial converter (i.e. CA-USB#-MTi), the correct drivers are included in the MT Software Suite, by default at: 
    C:\Program Files\Common Files\Xsens USB-serial converter driver
    If you require separate drivers, you can download them here
  • If you are using the MTi with the standard USB cable (CA-USB-MTi) (i.e. without a USB to serial converter) the correct drivers have to be installed.
    • For Windows: 
      • Make sure to have WinUSB installed.
    • For Linux:
      • libusb is included in the latest Linux kernel (Ubuntu).
      • In case the MTi is not recognized, visit to install the driver manually (e.g. on some versions of embedded Linux).

Correct version MTSS

Make sure that you have installed the correct version of the MT Software Suite. Refer to the following article:

Firmware Updater

Check whether your device is detected by the Firmware Updater, and whether it is possible to upgrade the Firmware to its latest available version. In some cases this may solve communication issues. The Firmware Updater can be downloaded at:

Restore communication tool

MT Manager features a Restore Communication tool. It can be found under the Tools tab. 

  • If you are using an MTi 10-series or 100-series:
    • The Restore Communication tool only works if you are using the COM interface.
    • Open the Restore Communication tool and simply follow the guidelines.
    • Communication should be restored. 
  • If you are using the MTi 1-series in combination with the Development Kit: 

    • You can use MTManager, but you will have to reset the device while not disconnecting the USB (the COM port should stay alive). To do this you need a jumper wire which you can use to temporary connect the nRST pin to GND (pins 5 and 3 of the header).

    • Connect the DK to the PC using the micro USB cable. 
    • Open MTManager and start the restore communication process on the COM port of the DK. 
    • Connect pins 3 and 5 (make nRST low). 
    • Disconnect pins 3 and 5. 
    • Communication should be restored.
  • If you are using the MTi 1-series and it is soldered in place, the procedure is described in section 7.2 of the Low Level Communication Document but this might require some translation to the MTi-1 as the USB-serial converter cable does not apply:
    • Switch PSEL to "00" to enable UART_FD. 
    • Open the UART to the MTi on 115200 8N1. 
    • Start sending repeatedly the value 0xDE with ~500us delay between them. 
    • Reset the MTi-1. Either pull the nRST line low for a short time or power cycle the MTi-1 (if possible). 
    • Keep sending 0xDE until Wakeup message to comes in. 
    • Communication should be restored.


Was this article helpful?
0 out of 0 found this helpful
Do you have a question? Please post your question in our Community Forum