30 min

Provide nuanced haptic feedback easily with LC898302AXA and PIC18LF26K80

Feel the pulse of innovation!

HAPTIC 2 Click with Curiosity HPC

Published Jan 23, 2024

Click board™

HAPTIC 2 Click

Development board

Curiosity HPC


NECTO Studio



Tailor alerts and notifications to individual preferences, ensuring that users receive important information in a way that resonates with them.



Hardware Overview

How does it work?

HAPTIC 2 Click is based on the LC898302AXA, a linear vibration motor driver dedicated to LRA (Linear Resonant Actuator) and ERM (Eccentric Rotating Mass) applications from ON Semiconductor. The original driving waveform enables low power consumption, and it is helpful to maintain battery lifetime. It allows crisp vibration thanks to automatic braking and over-driving features. The drive frequency automatically adjusts to the resonance frequency of the linear vibrator without the use of other external parts. As a result of this very effective drive, the vibration is as powerful as possible, using minimal energy compared to classical solutions. It also ignores the deviation of resonance frequency thanks to the

auto-tuning function. This function can increase the perceived vibration force by over 20%, making it far more efficient than conventional haptic driving solutions. They require minimal power but can maintain a high level of vibration. The LRA motors rely on a magnet attached to the case by a spring where a magnetic field from the coil causes vibration activity initiation. Compared to ERM, the LRA has better responsiveness, improving system performance. The ERM type of haptic motor causes the off-balance mass to rotate. The mass movement results in an asymmetric centripetal force displacing the motor. The ERM motor can adjust the ERM driving voltage through an adjustment resistor connected between the

OUT1 pin of the Click board™ terminal and the ERM motor pin. HAPTIC 2 Click operates only with the PWM signal from the mikroBUS™ socket that drives the LC898302AXA and offers fully configurable drive and brake functions. Also, it has a jumper setting labeled MODE SEL, which is used to choose between LRA or ERM motor to drive. 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.

HAPTIC 2 Click top side image
HAPTIC 2 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)


You complete me!


Vibration ERM Motor 9K RPM 3V (VC1026B002F - old MPN C1026B002F) represents a compact-size Eccentric Rotating Mass (ERM) motor designed by Vybronics. This type of motor contains a small eccentric weight on its rotor, so while rotating, it also produces a vibration effect often used for haptic feedback on many small handheld devices. Due to its circular shape with a diameter of 10mm, the VC1026B002F is often referred to as a coin motor. The main characteristics of this vibration motor are its supply voltage, in this case, 3VDC, maximum rated current of 85mA, and the rated speed of 9000RPM, which produces the highest G force/vibration energy of 0.80GRMS. It can also be used with self-adhesive tape to mount it on your PCB or the inner wall of your product's housing.

HAPTIC 2 Click accessories image

Used MCU Pins

mikroBUS™ mapper

Power Supply
PWM Signal

Take a closer look


HAPTIC 2 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
LTE Cat.1 2 Click front image hardware assembly
MCU DIP 28 hardware assembly
Prog-cut hardware assembly
LTE Cat.1 2 Click complete accessories setup image hardware assembly
Curiosity HPC Access 28pin-DIP - upright/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 HAPTIC 2 Click driver.

Key functions:

  • haptic2_set_duty_cycle - Sets PWM duty cycle

  • haptic2_pwm_stop - Stop PWM module

  • haptic2_pwm_start - Start PWM module.

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 Haptic2 Click example
 * # Description
 * This app shows some of the functions that Haptic 2 click has.
 * The demo application is composed of two sections :
 * ## Application Init
 * Initialization driver enables - PWM,
 * PWM signal is set to 8000 HZ and to give a 0% duty cycle
 * and start PWM module.
 * ## Application Task
 * This is an example that demonstrates the use of the Haptic 2 Click board.
 * In this example, we switched PWM signal back and forth 
 * from 10% duty cycle to 90% duty cycle every 500 milliseconds.
 * Results are being sent to the Usart Terminal where you can track their changes.
 * @author Nikola Peric

#include "board.h"
#include "log.h"
#include "haptic2.h"

static haptic2_t haptic2;
static log_t logger;

void application_init ( void ) 
    log_cfg_t log_cfg;          /**< Logger config object. */
    haptic2_cfg_t haptic2_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_printf( &logger, "\r\n" );
    log_info( &logger, " Application Init " );

    // Click initialization.

    haptic2_cfg_setup( &haptic2_cfg );
    HAPTIC2_MAP_MIKROBUS( haptic2_cfg, MIKROBUS_1 );
    err_t init_flag  = haptic2_init( &haptic2, &haptic2_cfg );
    if ( init_flag == PWM_ERROR ) 
        log_error( &logger, " Application Init Error. " );
        log_info( &logger, " Please, run program again... " );

        for ( ; ; );

    haptic2_default_cfg ( &haptic2 );

    haptic2_set_duty_cycle ( &haptic2, 0.0 );
    haptic2_pwm_start( &haptic2 );

    log_info( &logger, " Application Task " );

void application_task ( void ) 
    static int8_t duty_cnt = 1;
    static int8_t duty_inc = 1;
    float duty = duty_cnt / 10.0;

    haptic2_set_duty_cycle ( &haptic2, duty );
    log_printf( &logger, "Duty: %d%%\r\n", ( uint16_t )( duty_cnt * 10 ) );
    Delay_ms( 500 );
    if ( 10 == duty_cnt ) 
        duty_inc = -1;
    else if ( 0 == duty_cnt ) 
        duty_inc = 1;
    duty_cnt += duty_inc;

void main ( void ) 
    application_init( );

    for ( ; ; ) 
        application_task( );

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

Additional Support