Intermediate
30 min
0

Detect vibrations and accelerations with MC3419 and STM32F071VB for improved performance

Accelerate your world with 3D motion sensing!

Accel 18 Click with UNI Clicker

Published Oct 02, 2023

Click board™

Accel 18 Click

Development board

UNI Clicker

Compiler

NECTO Studio

MCU

STM32F071VB

Our cutting-edge 3-axis accelerometer solution plays a crucial role in improving virtual reality experiences by tracking head movements and providing immersive, responsive environments

A

A

Hardware Overview

How does it work?

Accel 18 Click is based on the MC3419, a highly reliable 16-bit digital triaxial acceleration sensor with a feature set optimized for consumer product motion sensing from MEMSIC. The MC3419 is highly configurable with a programmable acceleration range of ±2/±4/±8/±16g and a dedicated motion block that implements the latest algorithms to detect any motion, shake, tilt/flip, and tilt 35 positions. It is optimized for high-performance applications by supporting full 16-bit resolution at Output Data Rates (ODR) up to 1KHz. In addition to all these features, it also has excellent temperature stability and low power consumption/low active current. The MC3419 has two operational states: STANDBY (following a Power-Up sequence) and WAKE state. Operative

states are software-controllable, with no automatic power control. In the WAKE state, acceleration data for the X, Y, and Z axes are sampled between 0.5 and 1000 samples/second. Changing from the STANDBY to WAKE state takes one sample period (less than 10 μs). Also, digital offset and gain calibration can be performed on the Accel board, if necessary, to reduce the effects of post-assembly influences and stresses, which may cause the sensor readings to be offset from their factory values. Accel 18 Click allows the use of both I2C and SPI interfaces with a maximum frequency of 1MHz for I2C and 10MHz for SPI communication. The selection can be made by positioning SMD jumpers labeled as COMM SEL in an appropriate position. Note that all the jumpers'

positions must be on the same side, or the Click board™ may become unresponsive. While the I2C interface is selected, the MC3419 allows choosing the least significant bit (LSB) of its I2C slave address using the SMD jumper labeled ADDR SEL. The Accel 18 also possesses two interrupts, I1 and I2, routed to the AN and INT pins on the mikroBUS™ used to signal MCU that an event has been sensed. 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.

Accel 18 Click top side image
Accel 18 Click bottom side image

Features overview

Development board

UNI Clicker is a compact development board designed as a complete solution that brings the flexibility of add-on Click boards™ to your favorite microcontroller, making it a perfect starter kit for implementing your ideas. It supports a wide range of microcontrollers, such as different ARM, PIC32, dsPIC, PIC, and AVR from various vendors like Microchip, ST, NXP, and TI (regardless of their number of pins), four mikroBUS™ sockets for Click board™ connectivity, a USB connector, LED indicators, buttons, a debugger/programmer connector, and two 26-pin headers for interfacing with external electronics. Thanks to innovative manufacturing technology, it allows you to build

gadgets with unique functionalities and features quickly. Each part of the UNI Clicker development kit contains the components necessary for the most efficient operation of the same board. In addition to the possibility of choosing the UNI Clicker programming method, using a third-party programmer or CODEGRIP/mikroProg connected to onboard JTAG/SWD header, the UNI Clicker board also includes a clean and regulated power supply module for the development kit. It provides two ways of board-powering; through the USB Type-C (USB-C) connector, where onboard voltage regulators provide the appropriate voltage levels to each component on the board, or using a Li-Po/Li

Ion battery via an onboard battery connector. All communication methods that mikroBUS™ itself supports are on this board (plus USB HOST/DEVICE), including the well-established mikroBUS™ socket, a standardized socket for the MCU card (SiBRAIN standard), and several user-configurable buttons and LED indicators. UNI Clicker is an integral part of the Mikroe ecosystem, allowing you to create a new application in minutes. Natively supported by Mikroe software tools, it covers many aspects of prototyping thanks to a considerable number of different Click boards™ (over a thousand boards), the number of which is growing every day.

UNI clicker double image

Microcontroller Overview

MCU Card / MCU

default

Type

8th Generation

Architecture

ARM Cortex-M0

MCU Memory (KB)

128

Silicon Vendor

STMicroelectronics

Pin count

100

RAM (Bytes)

16384

Used MCU Pins

mikroBUS™ mapper

Interrupt 1
PC0
AN
NC
NC
RST
SPI Chip Select
PD15
CS
SPI Clock
PA5
SCK
SPI Data OUT
PA6
MISO
SPI Data IN
PA7
MOSI
Power Supply
3.3V
3.3V
Ground
GND
GND
NC
NC
PWM
Interrupt 2
PA8
INT
NC
NC
TX
NC
NC
RX
I2C Clock
PB8
SCL
I2C Data
PB9
SDA
NC
NC
5V
Ground
GND
GND
1

Take a closer look

Schematic

Accel 18 Click Schematic schematic

Step by step

Project assembly

UNI Clicker front image hardware assembly

Start by selecting your development board and Click board™. Begin with the UNI Clicker as your development board.

UNI Clicker front image hardware assembly
Thermo 28 Click front image hardware assembly
SiBRAIN for STM32F745VG front image hardware assembly
Prog-cut hardware assembly
UNI Clicker MB 1 - upright/with-background hardware assembly
Necto image step 2 hardware assembly
Necto image step 3 hardware assembly
Necto image step 4 hardware assembly
Necto image step 5 hardware assembly
Necto image step 6 hardware assembly
Necto image step 7 hardware assembly
Necto No Display image step 8 hardware assembly
Necto image step 9 hardware assembly
Necto image step 10 hardware assembly
Debug Image Necto Step hardware assembly

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.

Application Output Step 1

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™.

Application Output Step 3

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.

Application Output Step 4

Software Support

Library Description

This library contains API for Accel 18 Click driver.

Key functions:

  • accel18_read_axes - Accel data reading

  • accel18_set_range - Set range configuration

  • accel18_get_interrupt_1 - Get interrupt 1 pin state

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 Accel18 Click example
 *
 * # Description
 * This example application showcases ability of the device
 * to read axes values on detected interrupt, and check detected
 * motion.
 *
 * The demo application is composed of two sections :
 *
 * ## Application Init
 * Initialization of comunication modules(SPI/I2C, UART) and additional
 * two interrupt pins. Then configures device and sets 8g range and 25
 * data rate, with interrupt enabled.
 *
 * ## Application Task
 * Whenever interrupt is detected checks interrupt status for motion
 * detection, and then reads x, y, and z axes, calculates value and
 * logs result.
 *
 * @author Luka Filipovic
 *
 */

#include "board.h"
#include "log.h"
#include "accel18.h"

static accel18_t accel18;
static log_t logger;

void application_init ( void )
{
    log_cfg_t log_cfg;  /**< Logger config object. */
    accel18_cfg_t accel18_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.
    accel18_cfg_setup( &accel18_cfg );
    ACCEL18_MAP_MIKROBUS( accel18_cfg, MIKROBUS_1 );
    err_t init_flag  = accel18_init( &accel18, &accel18_cfg );
    if ( ( I2C_MASTER_ERROR == init_flag ) || ( SPI_MASTER_ERROR == init_flag ) )
    {
        log_error( &logger, " Application Init Error. " );
        log_info( &logger, " Please, run program again... " );

        for ( ; ; );
    }

    if ( accel18_default_cfg ( &accel18 ) )
    {
        log_error( &logger, " Default configuration. " );
        log_info( &logger, " Please, run program again... " );
        for ( ; ; );
    }

    log_info( &logger, " Application Task " );
}

void application_task ( void )
{
    if ( !accel18_get_interrupt_1( &accel18 ) )
    {
        //Interrupt detected check
        uint8_t int_flag = 0;
        uint8_t interrupt_state = 0;
        accel18_byte_read( &accel18, ACCEL18_REG_INTERRUPT_STATUS, &interrupt_state );
        if ( interrupt_state & ACCEL18_INT_TILT_EN )
        {
            int_flag++;
            log_printf( &logger, ">Tilt<\t" );
        }
        if ( interrupt_state & ACCEL18_INT_FLIP_EN )
        {
            int_flag++;
            log_printf( &logger, ">Flip<\t" );
        }
        if ( interrupt_state & ACCEL18_INT_SHAKE_EN )
        {
            int_flag++;
            log_printf( &logger, ">Shake<\t" );
        }
        if ( int_flag )
        {
            log_printf( &logger, "\r\n" );
        }

        //Axis read
        accel18_axes_t axes_data;
        accel18_read_axes( &accel18, &axes_data );
        log_printf( &logger, " > X[g]: %.2f\r\n", axes_data.x );
        log_printf( &logger, " > Y[g]: %.2f\r\n", axes_data.y );
        log_printf( &logger, " > Z[g]: %.2f\r\n", axes_data.z );
        log_printf( &logger, "**************************\r\n" );
        Delay_ms( 300 );
    }
}

void main ( void )
{
    application_init( );

    for ( ; ; )
    {
        application_task( );
    }
}

// ------------------------------------------------------------------------ END

Additional Support

Resources