Achieve precise detection of movements, crucial for motion-based applications, with ICM-42670-P and PIC18F47K42TQFP
Motion tracking and orientation detection based on a 6-axis MEMS MotionTracking IMU
Published Mar 15, 2024
Click board™
6DOF IMU 22 Click
Development board
Curiosity Nano with PIC18F47K42
Compiler
NECTO Studio
MCU
PIC18F47K42TQFP
Accurately track and measure movements and orientations of an object by detecting how fast and in which direction it's moving or tilting
A
A
Hardware Overview
How does it work?
6DOF IMU 22 Click is based on the ICM-42670-P, a state-of-the-art 6-axis MEMS MotionTracking IMU from TDK InvenSense. This central component incorporates both a 3-axis gyroscope and a 3-axis accelerometer, making it an exceptional tool for precise motion tracking. It has a versatile host interface compatible with I2C and SPI serial communication protocols, a sizeable 2.25Kbytes FIFO, and two customizable interrupts supporting a wake-on-motion feature to reduce power consumption significantly. The gyroscope and accelerometer offer a range of programmable full-scale range settings, ensuring flexibility across various applications. The gyroscope supports four programmable full-scale range settings from ±250dps to ±2000dps, and the accelerometer supports four programmable full-scale range
settings from ±2g to ±16g. The ICM-42670-P stands out in its class for having the lowest noise levels and unparalleled stability under temperature fluctuations, physical shocks, or offsets caused by soldering or bending. It also offers protection against noise from vibrations outside its frequency band. Adding to its impressive feature set are an on-board APEX Motion Processing engine for advanced gesture and step recognition, programmable digital filters, and an integrated temperature sensor, making it ideally suited for creating wearables, smart home devices, robotics, and immersive AR/VR experiences. 6DOF IMU 22 Click supports both I2C and SPI interfaces, enabling communication at speeds up to 1MHz and 24MHz, respectively. Users can select the desired communication protocol by placing SMD jumpers
on the COMM SEL section, ensuring all jumpers align on the same side to avoid potential issues. For I2C usage, the device allows the adjustment of its I2C slave address's least significant bit via an SMD jumper marked as ADDR SEL. Additionally, the board features a data frame sync input pin routed to the FSY pin on the mikroBUS™ socket and two interrupt pins linked to the INT and IT2 pins, enabling the host MCU to detect user-specified events through the I2C/SPI interface. 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
PIC18F47K42 Curiosity Nano evaluation kit is a cutting-edge hardware platform designed to evaluate the PIC18F47K42 microcontroller (MCU). Central to its design is the inclusion of the powerful PIC18F47K42 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 2.3V to 5.1V (limited by USB input voltage), 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
40
RAM (Bytes)
8192
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
Schematic
Step by step
Project assembly
Start by selecting your development board and Click board™. Begin with the Curiosity Nano with PIC18F47K42 as your development board.
Track your results in real time
Application Output
After loading the code example, pressing the "DEBUG" button builds and programs it on the selected setup.
After programming is completed, a header with buttons for various actions available in the IDE appears. By clicking the green "PLAY "button, we start reading the results achieved with Click board™.
Upon completion of programming, the Application Output tab is automatically opened, where the achieved result can be read. In case of an inability to perform the Debug function, check if a proper connection between the MCU used by the setup and the CODEGRIP programmer has been established. A detailed explanation of the CODEGRIP-board connection can be found in the CODEGRIP User Manual. Please find it in the RESOURCES section.
Software Support
Library Description
This library contains API for 6DOF IMU 22 Click driver.
Key functions:
c6dofimu22_read_data- This function reads the accelerometer, gyroscope, and temperature measurement datac6dofimu22_get_int1_pin- This function returns the INT1 pin logic statec6dofimu22_clear_data_ready- This function clears the data ready interrupt by reading the INT_STATUS_DRDY register
Open Source
Code example
This example can be found in NECTO Studio. Feel free to download the code, or you can copy the code below.
/*!
* @file main.c
* @brief 6DOF IMU 22 Click example
*
* # Description
* This example demonstrates the use of 6DOF IMU 22 click board by reading and displaying
* the accelerometer and gyroscope data (X, Y, and Z axis) as well as a temperature measurement
* in degrees Celsius.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and performs the click default configuration.
*
* ## Application Task
* Waits for a data ready indication and then reads the accelerometer, gyroscope, and temperature
* measurements. The results are displayed on the USB UART every 80ms as per the accel and gyro
* output data rate which is set to 12.5 Hz.
*
* @author Stefan Filipovic
*
*/
#include "board.h"
#include "log.h"
#include "c6dofimu22.h"
static c6dofimu22_t c6dofimu22;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
c6dofimu22_cfg_t c6dofimu22_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.
c6dofimu22_cfg_setup( &c6dofimu22_cfg );
C6DOFIMU22_MAP_MIKROBUS( c6dofimu22_cfg, MIKROBUS_1 );
err_t init_flag = c6dofimu22_init( &c6dofimu22, &c6dofimu22_cfg );
if ( ( I2C_MASTER_ERROR == init_flag ) || ( SPI_MASTER_ERROR == init_flag ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
if ( C6DOFIMU22_ERROR == c6dofimu22_default_cfg ( &c6dofimu22 ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
static c6dofimu22_data_t meas_data;
if ( !c6dofimu22_get_int1_pin ( &c6dofimu22 ) )
{
c6dofimu22_clear_data_ready ( &c6dofimu22 );
if ( C6DOFIMU22_OK == c6dofimu22_read_data ( &c6dofimu22, &meas_data ) )
{
log_printf ( &logger, " Accel X: %.2f g\r\n", meas_data.accel.x );
log_printf ( &logger, " Accel Y: %.2f g\r\n", meas_data.accel.y );
log_printf ( &logger, " Accel Z: %.2f g\r\n", meas_data.accel.z );
log_printf ( &logger, " Gyro X: %.1f dps\r\n", meas_data.gyro.x );
log_printf ( &logger, " Gyro Y: %.1f dps\r\n", meas_data.gyro.y );
log_printf ( &logger, " Gyro Z: %.1f dps\r\n", meas_data.gyro.z );
log_printf ( &logger, " Temperature: %.2f C\r\n\n", meas_data.temperature );
}
}
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
