From motion to magic, our gesture-based solution ushers in a new era of handheld applications, where your gestures become commands
A
A
Hardware Overview
How does it work?
Air Motion Click is based on the ICM-40627, a 6-axis MotionTracking™ 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-40627 guarantees optimal motion performance for customers. The ICM-40627 comes bundled with TDK's Air Motion Library that enables precise mouse pointing, swipe, roll, gesture wake-up, and other motion gestures, making this Click board™ a suitable solution for gesture-based handheld applications. The gyroscope supports eight programmable full-scale range settings from ±15.65dps to ±2000dps, and the accelerometer supports four
programmable full-scale range settings from ±2g to ±16g. Other industry-leading features include InvenSense on-chip APEX Motion Processing engine for gesture recognition, activity classification, and pedometer, along with on-chip 16-bit ADCs, programmable digital filters, an embedded temperature sensor, and programmable interrupts. Air Motion Click allows 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. Note: All jumpers' positions must be on the same side, or the Click board™ may become unresponsive. When the I2C interface is selected, the ICM-40627 allows the choice of the least significant bit (LSB) of its I2C slave address, using the ADDR SEL SMD jumper set to an appropriate
position marked 0 and 1. The ICM-40627 also has a programmable interrupt system, configured via the Interrupt Configuration register, that can generate an interrupt signal on the INT pins, INT1 and INT2 pins routed on the INT and AN pins of the mikroBUS™ socket. Events like new read-data availability (from the FIFO and Data registers), accelerometer events, FIFO watermark, and overflow can all trigger an interrupt. 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
Arduino UNO is a versatile microcontroller board built around the ATmega328P chip. It offers extensive connectivity options for various projects, featuring 14 digital input/output pins, six of which are PWM-capable, along with six analog inputs. Its core components include a 16MHz ceramic resonator, a USB connection, a power jack, an
ICSP header, and a reset button, providing everything necessary to power and program the board. The Uno is ready to go, whether connected to a computer via USB or powered by an AC-to-DC adapter or battery. As the first USB Arduino board, it serves as the benchmark for the Arduino platform, with "Uno" symbolizing its status as the
first in a series. This name choice, meaning "one" in Italian, commemorates the launch of Arduino Software (IDE) 1.0. Initially introduced alongside version 1.0 of the Arduino Software (IDE), the Uno has since become the foundational model for subsequent Arduino releases, embodying the platform's evolution.
Microcontroller Overview
MCU Card / MCU
Architecture
AVR
MCU Memory (KB)
32
Silicon Vendor
Microchip
Pin count
28
RAM (Bytes)
2048
You complete me!
Accessories
Click Shield for Arduino UNO has two proprietary mikroBUS™ sockets, allowing all the Click board™ devices to be interfaced with the Arduino UNO board without effort. The Arduino Uno, a microcontroller board based on the ATmega328P, provides an affordable and flexible way for users to try out new concepts and build prototypes with the ATmega328P microcontroller from various combinations of performance, power consumption, and features. The Arduino Uno has 14 digital input/output pins (of which six can be used as PWM outputs), six analog inputs, a 16 MHz ceramic resonator (CSTCE16M0V53-R0), a USB connection, a power jack, an ICSP header, and reset button. Most of the ATmega328P 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 Arduino UNO board with our Click Shield for Arduino UNO, 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
Schematic
Step by step
Project assembly
Track your results in real time
Application Output via Debug Mode
1. Once the code example is loaded, pressing the "DEBUG" button initiates the build process, programs it on the created setup, and enters Debug mode.
2. After the programming is completed, a header with buttons for various actions within the IDE becomes visible. Clicking the green "PLAY" button starts reading the results achieved with the Click board™. The achieved results are displayed in the Application Output tab.
Software Support
Library Description
This library contains API for Air Motion Click driver.
Key functions:
airmotion_set_reg_bank
- Air Motion set register bank functionairmotion_sw_reset
- Air Motion software reset functionairmotion_get_data_from_register
- Air Motion read data function
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 Air Motion Click example
*
* # Description
* This example demonstrates the use of Air Motion Click board.
*
* 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
* When the device is in Tap Detection Mode, Air Motion Click board will read and display the direction,
* axis, and number of taps that it detected.
* If Tap Detection mode is disabled, the device will read accel, gyro, and temperature data.
*
* @author Stefan Ilic
*
*/
#include "board.h"
#include "log.h"
#include "airmotion.h"
#define TAP_DETECTION_MODE
static airmotion_t airmotion;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
airmotion_cfg_t airmotion_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.
airmotion_cfg_setup( &airmotion_cfg );
AIRMOTION_MAP_MIKROBUS( airmotion_cfg, MIKROBUS_1 );
err_t init_flag = airmotion_init( &airmotion, &airmotion_cfg );
if ( ( I2C_MASTER_ERROR == init_flag ) || ( SPI_MASTER_ERROR == init_flag ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
if ( AIRMOTION_OK != airmotion_default_cfg ( &airmotion ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
uint8_t id = 0;
airmotion_reg_read( &airmotion, AIRMOTION_BANK0_SEL, AIRMOTION_WHO_AM_I, &id, 1);
log_printf( &logger, " WHO AM I = 0X%.2X\r\n", (uint16_t)id );
#if defined TAP_DETECTION_MODE
log_printf( &logger, " Tap Detection Mode \r\n" );
airmotion_set_basic_tap_detection( &airmotion );
#endif
}
void application_task ( void )
{
if ( airmotion_get_int1_state( &airmotion) )
{
#if defined TAP_DETECTION_MODE
uint8_t tap_num;
uint8_t tap_axis;
uint8_t tap_dir;
airmotion_get_tap_detection( &airmotion, &tap_num, &tap_axis, &tap_dir );
if ( AIRMOTION_TAP_SINGLE == tap_num )
{
log_printf( &logger, " SINGLE TAP" );
}
else
{
log_printf( &logger, " DOUBLE TAP" );
}
if ( AIRMOTION_TAP_DIR_POSITIVE == tap_dir )
{
log_printf( &logger, " IN POSITIVE" );
}
else
{
log_printf( &logger, " IN NEGATIVE" );
}
if ( AIRMOTION_TAP_AXIS_X == tap_axis )
{
log_printf( &logger, " X AXIS DIRECTION \r\n" );
}
else if ( AIRMOTION_TAP_AXIS_Y == tap_axis )
{
log_printf( &logger, " Y AXIS DIRECTION \r\n" );
}
else
{
log_printf( &logger, " Z AXIS DIRECTION \r\n" );
}
#else
airmotion_data_t accel_data;
airmotion_data_t gyro_data;
float temp_data;
uint32_t tmst_data;
airmotion_get_data_from_register( &airmotion, &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);
#endif
}
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END