Provide nuanced haptic feedback easily with LC898302AXA and PIC18F4515
Feel the pulse of innovation!
Published Nov 01, 2023
Click board™
HAPTIC 2 Click
Dev. board
EasyPIC v8
Compiler
NECTO Studio
MCU
PIC18F4515
Tailor alerts and notifications to individual preferences, ensuring that users receive important information in a way that resonates with them.
A
A
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.
Features overview
Development board
EasyPIC v8 is a development board specially designed for the needs of rapid development of embedded applications. It supports many high pin count 8-bit PIC microcontrollers from Microchip, regardless of their number of pins, and a broad set of unique functions, such as the first-ever embedded debugger/programmer. The development board is well organized and designed so that the end-user has all the necessary elements, such as switches, buttons, indicators, connectors, and others, in one place. Thanks to innovative manufacturing technology, EasyPIC v8 provides a fluid and immersive working experience, allowing access anywhere and under any
circumstances at any time. Each part of the EasyPIC v8 development board contains the components necessary for the most efficient operation of the same board. In addition to the advanced integrated CODEGRIP programmer/debugger module, which offers many valuable programming/debugging options and seamless integration with the Mikroe software environment, the board also includes a clean and regulated power supply module for the development board. It can use a wide range of external power sources, including a battery, an external 12V power supply, and a power source via the USB Type-C (USB-C) connector.
Communication options such as USB-UART, USB DEVICE, and CAN are also included, including the well-established mikroBUS™ standard, two display options (graphical and character-based LCD), and several different DIP sockets. These sockets cover a wide range of 8-bit PIC MCUs, from the smallest PIC MCU devices with only eight up to forty pins. EasyPIC v8 is an integral part of the Mikroe ecosystem for rapid development. Natively supported by Mikroe software tools, it covers many aspects of prototyping and development thanks to a considerable number of different Click boards™ (over a thousand boards), the number of which is growing every day.
Microcontroller Overview
MCU Card / MCU
Architecture
PIC
MCU Memory (KB)
48
Silicon Vendor
Microchip
Pin count
40
RAM (Bytes)
3968
You complete me!
Accessories
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.
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 EasyPIC v8 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 HAPTIC 2 Click driver.
Key functions:
haptic2_set_duty_cycle- Sets PWM duty cyclehaptic2_pwm_stop- Stop PWM modulehaptic2_pwm_start- Start PWM module.
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 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
