Enhance augmented reality (AR) experiences by accurately tracking user movements and surroundings, providing more realistic and interactive applications
A
A
Hardware Overview
How does it work?
6DOF IMU 7 Click is based on the ICM-20649, a high-performance, 6-axis MEMS MotionTracking™ from TDK InvenSense. It is an advanced, integrated microelectromechanical gyroscope and accelerometer sensor (MEMS). This allows very high integration and very small dimensions, at an affordable cost. The IC contains a MEMS structure hermetically sealed and bonded at wafer level. The ICM-20649 is the world’s first wide-range 6-axis MotionTracking device for Sports and other High Impact applications. It is available in a 3x3x0.9 mm 24-pin QFN package. Many of today’s wearable and sports solutions, which analyze the motion of a user’s golf or tennis swings, soccer ball kicks, or basketball activities, require higher than currently available ±2000 dps (degrees per second) FSR for gyroscope and ±16g FSR for accelerometer to better insure that critical data is not lost at the point of high impact or high speed rotation. The
ICM-20649 - 6-axis inertial sensor used on the 6DOF IMU 7 click offers the smallest size, lowest profile and lowest power in conjunction with industry leading high FSR. With an extended FSR range of ±4000 dps for gyroscope and ±30g for accelerometer, it enables precise analysis of contact sports applications providing continuous motion sensor data before, during and after impact providing more accurate feedback. ICM-20649 devices, with their 6-axis integration, on-chip DMP, and run-time calibration firmware, enable manufacturers to eliminate the costly and complex selection, qualification, and system level integration of discrete devices, guaranteeing optimal motion performance for consumers. The gyroscope has a programmable full-scale range up to ±4000 dps. The accelerometer has a user-programmable accelerometer full-scale range up to ±30g. Factory-calibrated initial sensitivity of
both sensors reduces production-line calibration requirements. Other key features include on-chip 16-bit ADCs, programmable digital filters, an embedded temperature sensor, and programmable interrupts. The embedded Digital Motion Processor (DMP) within the ICM-20649 offloads computation of motion processing algorithms from the host processor. The DMP acquires data from accelerometers, gyroscopes, and additional third party sensors such as magnetometers, and processes the data. The resulting data can be read from the 512 bytes FIFO that is accessible via the I2C Serial Interface. The FIFO configuration register determines which data is written into the FIFO. The interrupt function may be used to determine when new data is available.
Features overview
Development board
Nucleo-64 with STM32L073RZ MCU offers a cost-effective and adaptable platform for developers to explore new ideas and prototype their designs. This board harnesses the versatility of the STM32 microcontroller, enabling users to select the optimal balance of performance and power consumption for their projects. It accommodates the STM32 microcontroller in the LQFP64 package and includes essential components such as a user LED, which doubles as an ARDUINO® signal, alongside user and reset push-buttons, and a 32.768kHz crystal oscillator for precise timing operations. Designed with expansion and flexibility in mind, the Nucleo-64 board features an ARDUINO® Uno V3 expansion connector and ST morpho extension pin
headers, granting complete access to the STM32's I/Os for comprehensive project integration. Power supply options are adaptable, supporting ST-LINK USB VBUS or external power sources, ensuring adaptability in various development environments. The board also has an on-board ST-LINK debugger/programmer with USB re-enumeration capability, simplifying the programming and debugging process. Moreover, the board is designed to simplify advanced development with its external SMPS for efficient Vcore logic supply, support for USB Device full speed or USB SNK/UFP full speed, and built-in cryptographic features, enhancing both the power efficiency and security of projects. Additional connectivity is
provided through dedicated connectors for external SMPS experimentation, a USB connector for the ST-LINK, and a MIPI® debug connector, expanding the possibilities for hardware interfacing and experimentation. Developers will find extensive support through comprehensive free software libraries and examples, courtesy of the STM32Cube MCU Package. This, combined with compatibility with a wide array of Integrated Development Environments (IDEs), including IAR Embedded Workbench®, MDK-ARM, and STM32CubeIDE, ensures a smooth and efficient development experience, allowing users to fully leverage the capabilities of the Nucleo-64 board in their projects.
Microcontroller Overview
MCU Card / MCU

Architecture
ARM Cortex-M0
MCU Memory (KB)
192
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
20480
You complete me!
Accessories
Click Shield for Nucleo-64 comes equipped with two proprietary mikroBUS™ sockets, allowing all the Click board™ devices to be interfaced with the STM32 Nucleo-64 board with no effort. This way, Mikroe allows its users to add any functionality from our ever-growing range of Click boards™, such as WiFi, GSM, GPS, Bluetooth, ZigBee, environmental sensors, LEDs, speech recognition, motor control, movement sensors, and many more. More than 1537 Click boards™, which can be stacked and integrated, are at your disposal. The STM32 Nucleo-64 boards are based on the microcontrollers in 64-pin packages, a 32-bit MCU with an ARM Cortex M4 processor operating at 84MHz, 512Kb Flash, and 96KB SRAM, divided into two regions where the top section represents the ST-Link/V2 debugger and programmer while the bottom section of the board is an actual development board. These boards are controlled and powered conveniently through a USB connection to program and efficiently debug the Nucleo-64 board out of the box, with an additional USB cable connected to the USB mini port on the board. Most of the STM32 microcontroller pins are brought to the IO pins on the left and right edge of the board, which are then connected to two existing mikroBUS™ sockets. This Click Shield also has several switches that perform functions such as selecting the logic levels of analog signals on mikroBUS™ sockets and selecting logic voltage levels of the mikroBUS™ sockets themselves. Besides, the user is offered the possibility of using any Click board™ with the help of existing bidirectional level-shifting voltage translators, regardless of whether the Click board™ operates at a 3.3V or 5V logic voltage level. Once you connect the STM32 Nucleo-64 board with our Click Shield for Nucleo-64, you can access hundreds of Click boards™, working with 3.3V or 5V logic voltage levels.
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Click board™ Schematic

Step by step
Project assembly
Track your results in real time
Application Output
1. Application Output - In Debug mode, the 'Application Output' window enables real-time data monitoring, offering direct insight into execution results. Ensure proper data display by configuring the environment correctly using the provided tutorial.

2. UART Terminal - Use the UART Terminal to monitor data transmission via a USB to UART converter, allowing direct communication between the Click board™ and your development system. Configure the baud rate and other serial settings according to your project's requirements to ensure proper functionality. For step-by-step setup instructions, refer to the provided tutorial.

3. Plot Output - The Plot feature offers a powerful way to visualize real-time sensor data, enabling trend analysis, debugging, and comparison of multiple data points. To set it up correctly, follow the provided tutorial, which includes a step-by-step example of using the Plot feature to display Click board™ readings. To use the Plot feature in your code, use the function: plot(*insert_graph_name*, variable_name);. This is a general format, and it is up to the user to replace 'insert_graph_name' with the actual graph name and 'variable_name' with the parameter to be displayed.

Software Support
Library Description
This library contains API for 6DOF IMU 7 Click driver.
Key functions:
c6dofimu7_get_gyro_data
- This function reads gyroscope axis data and configures the gyro axis structc6dofimu7_get_accel_data
- This function reads accelerometer axis data and configures the accel axis structc6dofimu7_get_temp_data
- This function reads and returns temperature data
Open Source
Code example
The complete application code and a ready-to-use project are available through the NECTO Studio Package Manager for direct installation in the NECTO Studio. The application code can also be found on the MIKROE GitHub account.
/*!
* \file
* \brief 6DofImu7 Click example
*
* # Description
* This example showcases how to initialize and configure the logger and click modules and read
* and display temperature measurements and axis data from the gyroscope and accelerometer.
*
* The demo application is composed of two sections :
*
* ## Application Init
* This function initializes and configures the logger and click modules.
*
* ## Application Task
* This function reads and displays accelerometer, gyroscope and temperature data every second.
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "c6dofimu7.h"
// ------------------------------------------------------------------ VARIABLES
static c6dofimu7_t c6dofimu7;
static log_t logger;
static c6dofimu7_axis_t gyro;
static c6dofimu7_axis_t accel;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( )
{
log_cfg_t log_cfg;
c6dofimu7_cfg_t cfg;
/**
* Logger initialization.
* Default baud rate: 115200
* Default log level: LOG_LEVEL_DEBUG
* @note If USB_UART_RX and USB_UART_TX
* are defined as HAL_PIN_NC, you will
* need to define them manually for log to work.
* See @b LOG_MAP_USB_UART macro definition for detailed explanation.
*/
LOG_MAP_USB_UART( log_cfg );
log_init( &logger, &log_cfg );
log_info( &logger, "---- Application Init ----" );
// Click initialization.
c6dofimu7_cfg_setup( &cfg );
C6DOFIMU7_MAP_MIKROBUS( cfg, MIKROBUS_1 );
c6dofimu7_init( &c6dofimu7, &cfg );
c6dofimu7_default_cfg( &c6dofimu7 );
}
void application_task ( )
{
float temperature;
c6dofimu7_get_gyro_data( &c6dofimu7, &gyro, C6DOFIMU7_GYRO_SENSITIVITY );
log_printf( &logger, " * Gyro_X: %.5f * \r\n", gyro.x_axis );
log_printf( &logger, " * Gyro_Y: %.5f * \r\n", gyro.y_axis );
log_printf( &logger, " * Gyro_Z: %.5f * \r\n", gyro.z_axis );
log_printf( &logger, " ---------------------------- \r\n" );
c6dofimu7_get_accel_data( &c6dofimu7, &accel, C6DOFIMU7_ACCEL_SENSITIVITY );
log_printf( &logger, " * Accel_X: %.5f * \r\n", accel.x_axis );
log_printf( &logger, " * Accel_Y: %.5f * \r\n", accel.y_axis );
log_printf( &logger, " * Accel_Z: %.5f * \r\n", accel.z_axis );
log_printf( &logger, " ---------------------------- \r\n" );
temperature = c6dofimu7_get_temp_data( &c6dofimu7, C6DOFIMU7_TEMPERATURE_SENSITIVITY,
C6DOFIMU7_TEMPERATURE_OFFSET );
log_printf( &logger, " * Temperature: %.5f C * \r\n\r\n", temperature );
Delay_ms( 1000 );
}
void main ( )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END