Detect vibrations and accelerations with MC3419 and PIC32MZ2048EFM100 for improved performance
Accelerate your world with 3D motion sensing!
Published Oct 02, 2023
Click board™
Accel 18 Click
Dev. board
Curiosity PIC32 MZ EF
Compiler
NECTO Studio
MCU
PIC32MZ2048EFM100
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.
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
Architecture
PIC32
MCU Memory (KB)
2048
Silicon Vendor
Microchip
Pin count
100
RAM (Bytes)
524288
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 Curiosity PIC32 MZ EF as your development board.
Track your results in real time
Application Output
1. Application Output - In Debug mode, the 'Application Output' window enables real-time data monitoring, offering direct insight into execution results. Ensure proper data display by configuring the environment correctly using the provided tutorial.
2. UART Terminal - Use the UART Terminal to monitor data transmission via a USB to UART converter, allowing direct communication between the Click board™ and your development system. Configure the baud rate and other serial settings according to your project's requirements to ensure proper functionality. For step-by-step setup instructions, refer to the provided tutorial.
3. Plot Output - The Plot feature offers a powerful way to visualize real-time sensor data, enabling trend analysis, debugging, and comparison of multiple data points. To set it up correctly, follow the provided tutorial, which includes a step-by-step example of using the Plot feature to display Click board™ readings. To use the Plot feature in your code, use the function: plot(*insert_graph_name*, variable_name);. This is a general format, and it is up to the user to replace 'insert_graph_name' with the actual graph name and 'variable_name' with the parameter to be displayed.
Software Support
Library Description
This library contains API for Accel 18 Click driver.
Key functions:
accel18_read_axes- Accel data readingaccel18_set_range- Set range configurationaccel18_get_interrupt_1- Get interrupt 1 pin state
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 main.c
* @brief Accel18 Click example
*
* # Description
* This example application showcases ability of the device
* to read axes values on detected interrupt.
*
* 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 10 Hz
* data rate, with interrupt enabled.
*
* ## Application Task
* Whenever interrupt is detected checks interrupt status for data ready,
* 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 )
{
accel18_axes_t axes_data;
if ( !accel18_get_interrupt_1( &accel18 ) )
{
// Check interrupts
uint8_t interrupt_state = 0;
accel18_byte_read( &accel18, ACCEL18_REG_INTERRUPT_STATUS, &interrupt_state );
if ( interrupt_state & ACCEL18_INT_ACQ_EN )
{
// Axis read
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" );
}
// Clear interrupts
if ( interrupt_state )
{
accel18_byte_write( &accel18, ACCEL18_REG_INTERRUPT_STATUS, ~interrupt_state );
}
}
}
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
