Experience next-generation of motion sensing through IIS3DWB and STM32F031K6
Precision in every dimension: Elevate your motion sensing experience
Published Oct 01, 2024
Click board™
Accel 14 Click
Dev. board
Nucleo 32 with STM32F031K6 MCU
Compiler
NECTO Studio
MCU
STM32F031K6
We aim to empower your projects with the precision of three-axis acceleration technology, allowing you to measure, analyze, and excel in motion-related tasks
A
A
Hardware Overview
How does it work?
Accel 14 Click is based on the IIS3DWB, an ultra-wide bandwidth, low-noise, 3-axis digital vibration sensor from STMicroelectronics. The wide bandwidth, low noise, and very stable and repeatable sensitivity, together with the capability of operating over an extended temperature range, make this device particularly suitable for vibration monitoring in industrial applications. The IIS3DWB has a selectable full-scale acceleration range of ±2/±4/±8/±16 g and is capable of measuring accelerations with a bandwidth of up to 6 kHz with an output data rate of 26.7 kHz. A 3 kB first-in, first-out (FIFO) buffer is integrated into the device to avoid any data loss and limit the host processor's intervention. Accel 14 Click offers two possible operating configurations: Power-Down and Normal Mode. IIS3DWB has a voltage supply range from 2.1V to 3.6V. To avoid potential conflicts, it is recommended to set the lines connected to the device IO pins to a high-impedance state on the
host side during the power-on sequence. Furthermore, to guarantee the proper power-off of the device, it is recommended to maintain the duration of the VDD line to GND for at least 100 μs. After the power supply is applied, the IIS3DWB performs a 10 ms boot procedure to load the trimming parameters. After the boot is completed, the accelerometer is automatically configured in Power-Down mode. When the sensor is in Power-Down mode, almost all internal blocks of the device are switched off. The SPI digital interface remains active to allow communication with the device. The content of the configuration registers is preserved, and the output data registers are not updated, keeping the last data sampled in memory before going into Power-Down mode. When Accel 14 Click is set in Normal Mode, all three axes (X, Y, Z) are simultaneously active, and acceleration data can be read from the sensor concurrently for the 3-axis. The sensor provides
acceleration data at an output data rate of 26.667kHz. The IIS3DWB has been specifically designed to provide a wide bandwidth with a very flat frequency response in the passband and very high attenuation in the stopband to eliminate any frequency aliasing virtually. The device's functionality and measured acceleration data are accessible through the SPI interface. Also, the user can completely program functions such as the threshold and the timing of the two interrupt pins through the SPI digital 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
Nucleo 32 with STM32F031K6 MCU board provides an affordable and flexible platform for experimenting with STM32 microcontrollers in 32-pin packages. Featuring Arduino™ Nano connectivity, it allows easy expansion with specialized shields, while being mbed-enabled for seamless integration with online resources. The
board includes an on-board ST-LINK/V2-1 debugger/programmer, supporting USB reenumeration with three interfaces: Virtual Com port, mass storage, and debug port. It offers a flexible power supply through either USB VBUS or an external source. Additionally, it includes three LEDs (LD1 for USB communication, LD2 for power,
and LD3 as a user LED) and a reset push button. The STM32 Nucleo-32 board is supported by various Integrated Development Environments (IDEs) such as IAR™, Keil®, and GCC-based IDEs like AC6 SW4STM32, making it a versatile tool for developers.
Microcontroller Overview
MCU Card / MCU
Architecture
ARM Cortex-M0
MCU Memory (KB)
32
Silicon Vendor
STMicroelectronics
Pin count
32
RAM (Bytes)
4096
You complete me!
Accessories
Click Shield for Nucleo-32 is the perfect way to expand your development board's functionalities with STM32 Nucleo-32 pinout. The Click Shield for Nucleo-32 provides two mikroBUS™ sockets to add any functionality from our ever-growing range of Click boards™. We are fully stocked with everything, from sensors and WiFi transceivers to motor control and audio amplifiers. The Click Shield for Nucleo-32 is compatible with the STM32 Nucleo-32 board, providing an affordable and flexible way for users to try out new ideas and quickly create prototypes with any STM32 microcontrollers, choosing from the various combinations of performance, power consumption, and features. The STM32 Nucleo-32 boards do not require any separate probe as they integrate the ST-LINK/V2-1 debugger/programmer and come with the STM32 comprehensive software HAL library and various packaged software examples. This development platform provides users with an effortless and common way to combine the STM32 Nucleo-32 footprint compatible board with their favorite Click boards™ in their upcoming projects.
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Click board™ Schematic
Step by step
Project assembly
Start by selecting your development board and Click board™. Begin with the Nucleo 32 with STM32F031K6 MCU as your development board.
Software Support
Library Description
This library contains API for Accel 14 Click driver.
Key functions:
accel14_check_accel_data_ready- Check accel data ready functionaccel14_get_temperature- Get temperature functionaccel14_read_accel- Read Accel 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
* \brief Accel14 Click example
*
* # Description
* This application measures accelermeter data.
*
* The demo application is composed of two sections :
*
* ## Application Init
* SPI, check device ID, sets default configuration, also write log.
*
* ## Application Task
* This is an example which demonstrates the use of Accel 14 Click board.
* Measured and display Acceleration data for X-axis, Y-axis and Z-axis.
* Results are being sent to the Usart Terminal where you can track their changes.
* All data logs write on USB uart changes for every 1 sec.
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "accel14.h"
// ------------------------------------------------------------------ VARIABLES
static accel14_t accel14;
static log_t logger;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
accel14_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.
accel14_cfg_setup( &cfg );
ACCEL14_MAP_MIKROBUS( cfg, MIKROBUS_1 );
accel14_init( &accel14, &cfg );
Delay_ms ( 100 );
log_printf( &logger, " Driver init done \r\n" );
log_printf( &logger, "--------------------- \r\n" );
log_printf( &logger, " Communication check \r\n" );
if ( accel14_check_communication( &accel14 ) == ACCEL14_CHECK_ID_SUCCESS )
{
log_printf( &logger, " SUCCESS \r\n" );
log_printf( &logger, "--------------------- \r\n" );
}
else
{
log_printf( &logger, " ERROR \r\n" );
log_printf( &logger, " Reset the device \r\n" );
log_printf( &logger, "--------------------- \r\n" );
for ( ; ; );
}
log_printf( &logger, " Set default config. \r\n" );
log_printf( &logger, "--------------------- \r\n" );
accel14_default_cfg( &accel14 );
Delay_ms ( 100 );
log_printf( &logger, " Acceleration data: \r\n" );
log_printf( &logger, "--------------------- \r\n" );
}
void application_task ( void )
{
accel14_accel_t accel_data;
uint8_t data_ready_flag;
data_ready_flag = accel14_check_accel_data_ready( &accel14 );
Delay_ms ( 10 );
if ( data_ready_flag == ACCEL14_NEW_DATA_AVAILABLE )
{
accel14_get_data ( &accel14, &accel_data );
log_printf( &logger, " Accel X : %d \r\n", accel_data.x );
log_printf( &logger, " Accel Y : %d \r\n", accel_data.y );
log_printf( &logger, " Accel Z : %d \r\n", accel_data.z );
log_printf( &logger, "--------------------- \r\n" );
Delay_ms ( 1000 );
}
}
int main ( void )
{
/* Do not remove this line or clock might not be set correctly. */
#ifdef PREINIT_SUPPORTED
preinit();
#endif
application_init( );
for ( ; ; )
{
application_task( );
}
return 0;
}
// ------------------------------------------------------------------------ END
Additional Support
Resources
Category:Motion
