Xsens / Mbed 2 deprecated MTi-1_example

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:

• ST Nucleo F302R8
• Freescale FRDM-KL46Z
• NXP EA LPC4088

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

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.

Add support for parsing individual xbus messages.



Most xbus messages, except from MTData2 messages have a fixed format. To

make life easy for the user we will parse these and return the parsed

data in the memory pointed to by the XbusMessage data pointer. This way

we can just define structs for the different messages and users can

switch on the mid to decide how to cast the data pointer.