30 min

Support object stability control with KXTJ3-1057 and PIC18F46K20

Motion in focus: Where every move counts

Accel 7 click with Curiosity HPC

Published Nov 01, 2023

Click board™

Accel 7 click

Development board

Curiosity HPC


NECTO Studio



This solution precisely measures and records changes in an object's velocity, making them invaluable in fields like robotics, automotive safety, and more



Hardware Overview

How does it work?

Accel 7 Click is based on the KXTJ3-1057, ±2g / ±4g / ±8g / ±16g tri-axis digital accelerometer from Rohm Semiconductor. This sensor utilizes an advanced acceleration sensing method, based on the differential capacitance. The integrated MEMS, produced with the proprietary Kionix technology, is composed of two plates. One is fixed to the substrate, while the other can move freely along a single axis. The acceleration causes the change in the capacitance between these plates, which is then processed by an integrated ASIC. The ASIC incorporates a capacitance-to-voltage amplifier which converts the differential capacitance of the MEMS sensor into an analog voltage, used as the input for the low-noise A/D converter (ADC). The integrated ASIC also contains the logic section used to set all the operational parameters of the KXTJ3-1057, such as the data rate, filter settings, interrupts, ADC resolution, and more. The ASIC also incorporates an OTP memory that contains the calibration parameters and other device-specific settings used on each power-on reset (POR) cycle. The ADC can be operated with the resolution of 8, 12, or 14 bits. This allows power consumption to be managed, as the lower resolution typically allows less power consumption. The power consumption is also affected by the output data rate value (ODR). The ODR value above 400Hz forces the high-resolution mode (14-bits) so the power consumption rises

exponentially as the ODR changes from 0.781Hz to 1600Hz. The ADC resolution, as well as the other operating parameters of the KXTJ3-1057 IC can be adjusted by using two configuration registers. Some options can only be altered while the IC operates in the Stand-by mode. The acceleration range can be selected from ±2g to ±16g. The choice of the ADC resolution is directly related with the number of counts for a certain acceleration range. For example, using ±2g range with the 8-bit ADC resolution means that the whole range between -2g and +2g will be covered by 255 values, from -127 to +127. Therefore, the output of 127 will be equivalent of 2g acceleration (more precisely, 1.984g). The datasheet of the KXTJ3-1057 offers a comprehensive set of tables with these settings. However, the Accel 7 click comes with the library that contains simple to use functions which simplify the acceleration measurements. The interrupt engine allows interrupt reporting on a dedicated INT pin. There are multiple interrupt status registers, allowing both combined and individual events to be read. This allows the INT pin to be used more flexible. Depending on the settings, it is possible to pulse and latch this pin. When latched, it will stay asserted until the specific register is read (INT_REL in the datasheet). Pulsed operation will produce a short pulse on this pin, but the status bits will remain set, until the INT_REL register is read.

Un-latched mode allows the status bits to be cleared automatically, so there is no need to read the INT_REL register. One distinctive feature of the KXTJ3-1057 is that it can generate a Wake-up (motion detection) interrupt, when the acceleration measurement exceeds the value stored in the Wake-up threshold registers. In this case, a bit in the interrupt status register will indicate that a Wake-up event occurred. The Wake-up interrupt features a debouncing counter: if an acceleration value has exceeded the threshold and remained above this threshold during a programmed number of counts, an interrupt event will be reported. To distinguish between two successive movement events, there is yet another countdown timer, which sets the non-activity time interval before another Wake-up event can be reported. Note that the thresholds use fixed g-range and resolution, regardless of user settings. Each KXTJ3-1057 device is factory calibrated, and its calibration parameters are stored in the one-time programmable memory (OTP). These parameters include the gain corrections and offset calibration. After each POR cycle, these calibration values are automatically applied, reducing the output error. Along with the used MEMS differential sensing technology, this reduces the measurement error to a virtually unmeasurable value. A built-in self-test function allows reliable operation of the Accel 7 click.

Accel 7 Click top side image
Accel 7 Click bottom side image

Features overview

Development board

Curiosity HPC, standing for Curiosity High Pin Count (HPC) development board, supports 28- and 40-pin 8-bit PIC MCUs specially designed by Microchip for the needs of rapid development of embedded applications. This board has two unique PDIP sockets, surrounded by dual-row expansion headers, allowing connectivity to all pins on the populated PIC MCUs. It also contains a powerful onboard PICkit™ (PKOB), eliminating the need for an external programming/debugging tool, two mikroBUS™ sockets for Click board™ connectivity, a USB connector, a set of indicator LEDs, push button switches and a variable potentiometer. All

these features allow you to combine the strength of Microchip and Mikroe and create custom electronic solutions more efficiently than ever. Each part of the Curiosity HPC development board contains the components necessary for the most efficient operation of the same board. An integrated onboard PICkit™ (PKOB) allows low-voltage programming and in-circuit debugging for all supported devices. When used with the MPLAB® X Integrated Development Environment (IDE, version 3.0 or higher) or MPLAB® Xpress IDE, in-circuit debugging allows users to run, modify, and troubleshoot their custom software and hardware

quickly without the need for additional debugging tools. Besides, it includes a clean and regulated power supply block for the development board via the USB Micro-B connector, alongside all communication methods that mikroBUS™ itself supports. Curiosity HPC development board allows you to create a new application in just a few steps. Natively supported by Microchip software tools, it covers many aspects of prototyping thanks to many number of different Click boards™ (over a thousand boards), the number of which is growing daily.

Curiosity HPC double image

Microcontroller Overview

MCU Card / MCU




MCU Memory (KB)


Silicon Vendor


Pin count


RAM (Bytes)


Used MCU Pins

mikroBUS™ mapper

Power Supply
I2C Clock
I2C Data

Take a closer look


Accel 7 click Schematic schematic

Step by step

Project assembly

Curiosity HPC front no-mcu image hardware assembly

Start by selecting your development board and Click board™. Begin with the Curiosity HPC as your development board.

Curiosity HPC front no-mcu image hardware assembly
Thermo 28 Click front image hardware assembly
MCU DIP 40 hardware assembly
Prog-cut hardware assembly
Curiosity HPC 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 DIP 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 7 Click driver.

Key functions:

  • accel7_get_axis - This function reads two bytes of data from the desired axis register

  • accel7_res_range_cfg - This function calculates the resolution and range values which are used in the default_cfg() function

  • accel7_get_interrupt_state - This function reads the state of the interrupt pin

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 Accel7 Click example
 * # Description
 * This example shows how data from all three axes is collected, processed and later
 * displayed in the logger module.
 * The demo application is composed of two sections :
 * ## Application Init 
 * This is where the logger and the click modules get initialised and configured.
 * ## Application Task  
 * This is where the data gets collected, processed and printed out.
 * \author MikroE Team
// ------------------------------------------------------------------- INCLUDES

#include "board.h"
#include "log.h"
#include "accel7.h"

// ------------------------------------------------------------------ VARIABLES

static accel7_t accel7;
static log_t logger;

// ------------------------------------------------------ APPLICATION FUNCTIONS

void application_init (  )
    log_cfg_t log_cfg;
    accel7_cfg_t cfg;

    uint8_t resolution = ACCEL7_DATA_RESP_14bit;
    uint8_t range = ACCEL7_RANGE_8g;

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

    accel7_cfg_setup( &cfg );
    accel7_init( &accel7, &cfg );
    accel7_default_cfg( &accel7, resolution, range );

    Delay_ms( 100 );

void application_task (  )
    int16_t x_axis;
    int16_t y_axis;
    int16_t z_axis;

    x_axis = accel7_get_axis( &accel7, ACCEL7_AXIS_X );
    y_axis = accel7_get_axis( &accel7, ACCEL7_AXIS_Y );
    z_axis = accel7_get_axis( &accel7, ACCEL7_AXIS_Z );

    log_printf( &logger, "X axis: %d\r\n", x_axis );
    log_printf( &logger, "Y axis: %d\r\n", y_axis );
    log_printf( &logger, "Z axis: %d\r\n", z_axis );   
    log_printf( &logger, "------------------\r\n" );

    Delay_ms( 1000 );

void main (  )
    application_init(  );

    for ( ; ; )
        application_task(  );

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

Additional Support