Empower your projects with 6DOF IMU, the ultimate solution for capturing and controlling motion in three-dimensional space
A
A
Hardware Overview
How does it work?
6DOF IMU 18 Click is based on the ICM-42605, a 6-axis motion tracking device that combines a 3-axis gyroscope and a 3-axis accelerometer from TDK InvenSense. It features a 2K-byte FIFO that can lower the traffic on the selected serial bus interface and reduce power consumption by allowing the system processor to burst read sensor data and then go into a low-power mode. With its 6-axis integration, the ICM-42605 guarantees optimal motion performance for customers. The IICM-42605 supports an extended operating temperature range, allowing customers to design it into various industrial IoT applications, including navigation and stabilizing industrial machinery and robots. The gyroscope supports eight programmable full-scale range settings from ±15.625dps to ±2000dps, and the accelerometer
supports four programmable full-scale range settings from ±2g to ±16g. Other industry-leading features include on-chip 16-bit ADCs, programmable digital filters, an embedded temperature sensor, and programmable interrupts. The ICM-42605 also provides high robustness by supporting 20,000g shock reliability. This Click board™ allows the use of both I2C and SPI interfaces at a maximum frequency of 1MHz for I2C and 24MHz for SPI communication. Selection is made by positioning SMD jumpers marked COMM SEL to the appropriate position. All jumpers must be on the same side, or the Click board™ may become unresponsive. When the I2C interface is selected, the ICM-42605 allows the choice of its I2C slave address, using the ADDR SEL SMD jumper set to an appropriate position
marked 1 or 0. In addition to communication pins, this board also possesses additional interrupt pins, routed to the INT and IT2 pins on the mikroBUS™ socket, to signal MCU that an event, such as specific tap or sample acquisition conditions, has happened. Besides the standard interrupt function, the IT2 pin can also be used as a Frame Synchronization signal for synchronization with an external digital signal. This Click board™ can be operated only with a 3.3V logic voltage level. The board must perform appropriate logic voltage level conversion before using MCUs with different logic levels. Also, it comes equipped with a library containing functions and an example code that can be used as a reference for further development.
Features overview
Development board
PIC18F57Q43 Curiosity Nano evaluation kit is a cutting-edge hardware platform designed to evaluate microcontrollers within the PIC18-Q43 family. Central to its design is the inclusion of the powerful PIC18F57Q43 microcontroller (MCU), offering advanced functionalities and robust performance. Key features of this evaluation kit include a yellow user LED and a responsive
mechanical user switch, providing seamless interaction and testing. The provision for a 32.768kHz crystal footprint ensures precision timing capabilities. With an onboard debugger boasting a green power and status LED, programming and debugging become intuitive and efficient. Further enhancing its utility is the Virtual serial port (CDC) and a debug GPIO channel (DGI
GPIO), offering extensive connectivity options. Powered via USB, this kit boasts an adjustable target voltage feature facilitated by the MIC5353 LDO regulator, ensuring stable operation with an output voltage ranging from 1.8V to 5.1V, with a maximum output current of 500mA, subject to ambient temperature and voltage constraints.
Microcontroller Overview
MCU Card / MCU

Architecture
PIC
MCU Memory (KB)
128
Silicon Vendor
Microchip
Pin count
48
RAM (Bytes)
8196
You complete me!
Accessories
Curiosity Nano Base for Click boards is a versatile hardware extension platform created to streamline the integration between Curiosity Nano kits and extension boards, tailored explicitly for the mikroBUS™-standardized Click boards and Xplained Pro extension boards. This innovative base board (shield) offers seamless connectivity and expansion possibilities, simplifying experimentation and development. Key features include USB power compatibility from the Curiosity Nano kit, alongside an alternative external power input option for enhanced flexibility. The onboard Li-Ion/LiPo charger and management circuit ensure smooth operation for battery-powered applications, simplifying usage and management. Moreover, the base incorporates a fixed 3.3V PSU dedicated to target and mikroBUS™ power rails, alongside a fixed 5.0V boost converter catering to 5V power rails of mikroBUS™ sockets, providing stable power delivery for various connected devices.
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 18 Click driver.
Key functions:
c6dofimu18_set_reg_bank
- 6DOF IMU 18 set register bank functionc6dofimu18_get_int1_state
- 6DOF IMU 18 read INT1 pin state functionc6dofimu18_get_data_from_register
- 6DOF IMU 18 read data function.
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 main.c
* @brief 6DOF IMU 18 Click example
*
* # Description
* This library contains API for 6DOF IMU 18 Click driver.
* The library initializes and defines the I2C and SPI bus drivers to
* write and read data from registers, as well as the default
* configuration for reading gyroscope and accelerator data, and temperature.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver after that resets the device and
* performs default configuration and reads the device id.
*
* ## Application Task
* This example demonstrates the use of the 6DOF IMU 18 Click board by
* measuring and displaying acceleration and gyroscope data for X-axis,
* Y-axis, and Z-axis as well as temperature in degrees Celsius.
*
* @author Stefan Ilic
*
*/
#include "board.h"
#include "log.h"
#include "c6dofimu18.h"
static c6dofimu18_t c6dofimu18;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
c6dofimu18_cfg_t c6dofimu18_cfg; /**< Click config object. */
/**
* 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.
c6dofimu18_cfg_setup( &c6dofimu18_cfg );
C6DOFIMU18_MAP_MIKROBUS( c6dofimu18_cfg, MIKROBUS_1 );
err_t init_flag = c6dofimu18_init( &c6dofimu18, &c6dofimu18_cfg );
if ( ( I2C_MASTER_ERROR == init_flag ) || ( SPI_MASTER_ERROR == init_flag ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
Delay_ms( 100 );
uint8_t id = 0;
c6dofimu18_reg_read( &c6dofimu18, C6DOFIMU18_BANK0_SEL, C6DOFIMU18_REG_WHO_AM_I, &id, 1);
log_printf( &logger, " Device ID : 0x%.2X \r\n", ( uint16_t ) id );
if ( C6DOFIMU18_WHO_AM_I_VALUE != id )
{
log_error( &logger, " Communication error." );
for ( ; ; );
}
Delay_ms( 100 );
if ( C6DOFIMU18_OK != c6dofimu18_default_cfg ( &c6dofimu18 ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
if ( c6dofimu18_get_int1_state( &c6dofimu18) )
{
c6dofimu18_data_t accel_data;
c6dofimu18_data_t gyro_data;
float temp_data;
uint32_t tmst_data;
c6dofimu18_get_data_from_register( &c6dofimu18, &temp_data, &accel_data, &gyro_data, &tmst_data );
log_printf( &logger, " TEMP: %.2f \r\n", temp_data );
log_printf( &logger, " GYRO: x:%d y:%d z:%d \r\n", gyro_data.data_x,gyro_data.data_y,gyro_data.data_z );
log_printf( &logger, " ACCEL: x:%d y:%d z:%d \r\n", accel_data.data_x,accel_data.data_y,accel_data.data_z );
log_printf( &logger, "========================== \r\n" );
Delay_ms( 1000 );
}
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
Additional Support
Resources
Category:Motion