Enhance your projects with accurate motion detection, capturing its speed and direction with precision
A
A
Hardware Overview
How does it work?
Accel Click is based on the ADXL345, a complete 3-axis acceleration measurement system that operates at low power consumption levels from Analog Devices. It measures both dynamic accelerations, resulting from motion or shock, and static acceleration, such as gravity, and allows selectable full-scale acceleration measurements in ranges of ±2g, ±4g, ±8g, or ±16g with a resolution of 4mg/LSB on the ±2g range. Acceleration is reported digitally, communicating via the SPI or the I2C protocol and providing 16-bit output resolution. Its high resolution also enables the measurement of inclination changes less than 1.0°. The ADXL345 supports several special sensing functions. Activity and inactivity sensing detect the presence or lack
of motion by comparing the acceleration on any axis with user-set thresholds, while tap sensing detects single and double taps in any direction. Besides, a free-fall sensing feature detects if the device is falling. All these functions can be mapped to the interrupt pin routed on the INT pin of the mikroBUS™ socket. Accel Click allows the use of both I2C and SPI interfaces. 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 ADXL345 allows choosing the least significant bit (LSB) of its I2C slave address using the SMD jumper labeled ADDR
SEL. An integrated memory management system with a 32-level first in, first out (FIFO) buffer can store data to minimize host processor activity and lower overall system power consumption. Low power modes enable intelligent motion-based power management with threshold sensing and active acceleration measurement at low power dissipation. 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
Curiosity PIC32 MZ EF development board is a fully integrated 32-bit development platform featuring the high-performance PIC32MZ EF Series (PIC32MZ2048EFM) that has a 2MB Flash, 512KB RAM, integrated FPU, Crypto accelerator, and excellent connectivity options. It includes an integrated programmer and debugger, requiring no additional hardware. Users can expand
functionality through MIKROE mikroBUS™ Click™ adapter boards, add Ethernet connectivity with the Microchip PHY daughter board, add WiFi connectivity capability using the Microchip expansions boards, and add audio input and output capability with Microchip audio daughter boards. These boards are fully integrated into PIC32’s powerful software framework, MPLAB Harmony,
which provides a flexible and modular interface to application development a rich set of inter-operable software stacks (TCP-IP, USB), and easy-to-use features. The Curiosity PIC32 MZ EF development board offers expansion capabilities making it an excellent choice for a rapid prototyping board in Connectivity, IOT, and general-purpose applications.
Microcontroller Overview
MCU Card / MCU
![default](https://dbp-cdn.mikroe.com/catalog/mcus/resources/PIC32MZ2048EFM100/PIC32MZ2048EFM100.jpg)
Architecture
PIC32
MCU Memory (KB)
2048
Silicon Vendor
Microchip
Pin count
100
RAM (Bytes)
524288
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Schematic
![Accel Click Schematic schematic](https://dbp-cdn.mikroe.com/catalog/click-boards/resources/1eeba245-7575-6afa-bdec-0242ac120004/Accel-click-v101-MikroID-Schematic-1.png)
Step by step
Project 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](https://dbp-cdn.mikroe.com/cms/shared-resources/1eed554e-d80f-6694-8cb9-02420a000272/AP-Step1.jpg)
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](https://dbp-cdn.mikroe.com/cms/shared-resources/1eed5550-3c0f-6800-a19f-02420a000272/AP-Step3.jpg)
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](https://dbp-cdn.mikroe.com/cms/shared-resources/1eed5550-d4d0-6b20-a348-02420a000272/AP-Step4.jpg)
Software Support
Library Description
This library contains API for Accel Click driver.
Key functions:
accel_read_x_axis
- This function reads X axis value from Accelaccel_read_y_axis
- This function reads Y axis value from Accelaccel_read_z_axis
- This function reads Z axis value from Accel
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
* \brief Accel Click example
*
* # Description
* This example demonstrates the use of Accel click board by reading and
* displaying the accelerometer data (X, Y, and Z axis).
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes SPI/I2C driver and settings data read format,
* power mode, FIFO control and baud rate ( 100Hz default ).
*
* ## Application Task
* Reads X, Y and Z axis and logs on usbuart every 100 ms.
*
* \author Jovan Stajkovic
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "accel.h"
// ------------------------------------------------------------------ VARIABLES
static accel_t accel;
static log_t logger;
static uint8_t tmp;
static int16_t val_x;
static int16_t val_y;
static int16_t val_z;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
accel_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 " );
accel_cfg_setup( &cfg );
ACCEL_MAP_MIKROBUS( cfg, MIKROBUS_1 );
accel_init( &accel, &cfg );
accel_generic_read( &accel, ACCEL_REG_DEVID, &tmp, 1 );
if ( tmp == ACCEL_DEVID )
{
log_printf( &logger, "---- Comunication OK!!! ----\r\n" );
}
else
{
log_printf( &logger, "---- Comunication ERROR!!! ----\r\n" );
for ( ; ; );
}
accel_default_cfg ( &accel );
}
void application_task ( void )
{
val_x = accel_read_x_axis( &accel );
log_printf( &logger, "Axis X : %.3f g\r\n", val_x / ACCEL_DATA_RES_LSB_PER_G );
val_y = accel_read_y_axis( &accel );
log_printf( &logger, "Axis Y : %.3f g\r\n", val_y / ACCEL_DATA_RES_LSB_PER_G );
val_z = accel_read_z_axis( &accel );
log_printf( &logger, "Axis Z : %.3f g\r\n", val_z / ACCEL_DATA_RES_LSB_PER_G );
log_printf( &logger, "-------------------\r\n" );
Delay_ms( 100 );
}
int main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
return 0;
}
// ------------------------------------------------------------------------ END