Example of using Xbus library to communicate with an MTi-1 series device using a full-duplex UART connection.

Dependencies:   mbed-rtos mbed Xbus

Fork of MTi-1_example by Alex Young

Important Information

This example is deprecated and no longer maintained. There are new embedded examples available in the MT SDK folder of the MT Software Suite. For more information please visit: https://xsenstechnologies.force.com/knowledgebase/s/article/Introduction-to-the-MT-SDK-programming-examples-for-MTi-devices

Overview

The example program demonstrates connecting to an MTi-1 series device, restoring communications settings to default if necessary, and configuring the MTi to send data. For an MTi-1 the device is configured to send inertial sensor data, while MTi-2 and MTi-3 devices are configured to output orientation data using the onboard XKF3i filter.

Communication with the MTi-1 series device is implemented using a either a full-duplex UART, I2C or SPI bus. A reset line is used to reset the MTi during initialization. Data is output to a host PC terminal using a second UART.

For more information on the MTi-1 series communication protocol please refer to the datasheet: https://www.xsens.com/download/pdf/documentation/mti-1/mti-1-series_datasheet.pdf

Supported Platforms

The program has been tested on the following mbed platforms:

Using the Example

  1. To use the example program connect one of the supported mbed boards to the host PC and download the application from the mbed online compiler to the target device.
  2. With the mbed board unpowered (USB disconnected) wire the mbed board to the MTi-1 development board. The following connections are required:
    • In all cases:
      • 5V (or 3V3) main supply to VDD (P300-1)
      • MCU IO voltage (IORef) to VDDIO (P300-2)
      • GND to GND (P300-3)
      • MT_NRESET to nRST (P300-5)
    • For I2C communication:
      • MT_SCL to I2C_SCL (P300-9)
      • MT_SDA to I2C_SDA (P300-11)
      • MT_DRDY to DRDY (P300-15)
      • MT_ADD0 to ADD0 (P300-17)
      • MT_ADD1 to ADD1 (P300-19)
      • MT_ADD2 to ADD2 (P300-21)
    • For SPI communication:
      • MT_DRDY to DRDY (P300-15)
      • MT_SCLK to SPI_SCK (P300-17)
      • MT_MISO to SPI_MISO (P300-19)
      • MT_MOSI to SPI_MOSI (P300-21)
      • MT_nCS to SPI_nCS (P300-23)
    • For UART communication:
      • MT_RX to UART_TX (P300-9)
      • MT_TX to UART_RX (P300-11)

For more information on the MTi-1 development board please refer to the MTi-1 series user manual: https://www.xsens.com/download/pdf/documentation/mti-1/mti-1-series_dk_user_manual.pdf

Information

Check the defines at the top of main.cpp to determine which IO pins are used for the MT_xxx connections on each mbed platform.

Information

The active peripheral (I2C, SPI or UART) is selected on the MTi-1 development board through the PSEL0 and PSEL1 switches. Look on the bottom of the development board for the correct settings.

  1. Connect to the target using a serial terminal. The application is configured for:
    • Baudrate = 921600
    • Stop bits = 1
    • No parity bits
    • No flow control
  2. Reset the mbed board.
  3. You should be presented with a simple user interface as shown below:
MTi-1 series embedded example firmware.
Device ready for operation.
Found device with ID: 03880011.
Device is an MTi-3: Attitude Heading Reference System.
Output configuration set to:
        Packet counter: 65535 Hz
        Sample time fine: 65535 Hz
        Quaternion: 100 Hz
        Status word: 65535 Hz

Press 'm' to start measuring and 'c' to return to config mode.
Committer:
Alex Young
Date:
Fri May 22 15:40:27 2015 +0200
Revision:
50:f581d5428ea6
Parent:
45:67203918bec9
Child:
61:b9d3e7e5ba0c
Change definition for Xbus bus ID for consistency with LLCP documentation

Who changed what in which revision?

UserRevisionLine numberNew contents of line
Alex Young 10:18a6661b7e59 1 /*!
Alex Young 10:18a6661b7e59 2 * \file
Alex Young 10:18a6661b7e59 3 * \copyright
Alex Young 10:18a6661b7e59 4 * Copyright (C) Xsens Technologies B.V., 2015. All rights reserved.
Alex Young 10:18a6661b7e59 5 *
Alex Young 10:18a6661b7e59 6 * This source code is intended for use only by Xsens Technologies BV and
Alex Young 10:18a6661b7e59 7 * those that have explicit written permission to use it from
Alex Young 10:18a6661b7e59 8 * Xsens Technologies BV.
Alex Young 10:18a6661b7e59 9 *
Alex Young 10:18a6661b7e59 10 * THIS CODE AND INFORMATION IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY
Alex Young 10:18a6661b7e59 11 * KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE
Alex Young 10:18a6661b7e59 12 * IMPLIED WARRANTIES OF MERCHANTABILITY AND/OR FITNESS FOR A
Alex Young 10:18a6661b7e59 13 * PARTICULAR PURPOSE.
Alex Young 10:18a6661b7e59 14 */
Alex Young 10:18a6661b7e59 15
Alex Young 10:18a6661b7e59 16 #ifndef __XBUSDEF_H
Alex Young 10:18a6661b7e59 17 #define __XBUSDEF_H
Alex Young 10:18a6661b7e59 18
Alex Young 45:67203918bec9 19 /*! \brief Xbus message preamble byte. */
Alex Young 10:18a6661b7e59 20 #define XBUS_PREAMBLE (0xFA)
Alex Young 50:f581d5428ea6 21 /*! \brief Xbus message bus ID for master devices. */
Alex Young 50:f581d5428ea6 22 #define XBUS_MASTERDEVICE (0xFF)
Alex Young 45:67203918bec9 23 /*! \brief Xbus length byte for messages without payload. */
Alex Young 10:18a6661b7e59 24 #define XBUS_NO_PAYLOAD (0x00)
Alex Young 45:67203918bec9 25 /*! \brief Xbus length byte for message with an extended payload. */
Alex Young 10:18a6661b7e59 26 #define XBUS_EXTENDED_LENGTH (0xFF)
Alex Young 10:18a6661b7e59 27
Alex Young 10:18a6661b7e59 28 #endif // __XBUSDEF_H