H-Bridge Driver 2 click
H-Bridge Driver 2 Click is a compact add-on board that contains an H-bridge gate driver, also known as a full-bridge pre-driver. This board features the NCV7535, a monolithic H−bridge pre-driver for a DC motor with an enhanced feature set, useful in automotive systems from ON Semiconductor. The gate driver channels are independently controlled by a 24-bit SPI interface, allowing this Click board™ to be optionally configured in a single or dual H-bridge mode. It has a wide operating voltage range from 6V to 18V with built-in protection features against short-circuit, under/over voltage, overcurrent, and overtemperature conditions. This Click board™ is suitable to drive external MOSFETs, thus providing control of a DC-motor.
click Product page
Click library
- Author : Nenad Filipovic
- Date : Oct 2021.
- Type : SPI type
Software Support
We provide a library for the HBridgeDriver2 Click as well as a demo application (example), developed using MikroElektronika compilers. The demo can run on all the main MikroElektronika development boards.
Package can be downloaded/installed directly from NECTO Studio Package Manager(recommended way), downloaded from our LibStock™ or found on Mikroe github account.
Library Description
This library contains API for HBridgeDriver2 Click driver.
Standard key functions :
hbridgedriver2_cfg_setup
Config Object Initialization function.
void hbridgedriver2_cfg_setup(hbridgedriver2_cfg_t *cfg)
H-Bridge Driver 2 configuration object setup function.
H-Bridge Driver 2 Click configuration object.
Definition hbridgedriver2.h:276
hbridgedriver2_init
Initialization function.
err_t hbridgedriver2_init(hbridgedriver2_t *ctx, hbridgedriver2_cfg_t *cfg)
H-Bridge Driver 2 initialization function.
H-Bridge Driver 2 Click context object.
Definition hbridgedriver2.h:256
hbridgedriver2_default_cfg
Click Default Configuration function.
err_t hbridgedriver2_default_cfg(hbridgedriver2_t *ctx)
H-Bridge Driver 2 default configuration function.
Example key functions :
hbridgedriver2_run_forward
H-Bridge Driver 2 run forward function.
err_t hbridgedriver2_run_forward(hbridgedriver2_t *ctx, uint8_t *global_fault)
H-Bridge Driver 2 run forward function.
hbridgedriver2_run_backward
H-Bridge Driver 2 run backward function.
err_t hbridgedriver2_run_backward(hbridgedriver2_t *ctx, uint8_t *global_fault)
H-Bridge Driver 2 run backward function.
hbridgedriver2_stop_with_brake
H-Bridge Driver 2 stop with brake function.
err_t hbridgedriver2_stop_with_brake(hbridgedriver2_t *ctx, uint8_t *global_fault)
H-Bridge Driver 2 stop with brake function.
Example Description
This library contains API for the H-Bridge Driver 2 Click driver. This demo application shows the use of a H-Bridge Driver 2 Click board™.
The demo application is composed of two sections :
Application Init
Initialization of SPI, PWM module and log UART. After driver initialization and default settings, the application displays the device ID data, sets PWM duty cycle to 50% and start PWM module.
{
log_cfg_t log_cfg;
LOG_MAP_USB_UART( log_cfg );
log_init( &logger, &log_cfg );
log_info( &logger, " Application Init " );
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
Delay_ms ( 1000 );
Delay_ms ( 100 );
log_info( &logger, " Default config " );
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
Delay_ms ( 1000 );
log_printf( &logger, "--------------------------------\r\n" );
Delay_ms ( 100 );
Delay_ms ( 100 );
log_printf( &logger, " ID header : 0x%.4X \r\n", dev_id.id_header );
log_printf( &logger, " Version : 0x%.4X \r\n", dev_id.version );
log_printf( &logger, " Product Code 1 : 0x%.4X \r\n", dev_id.product_code_1 );
log_printf( &logger, " Product Code 2 : 0x%.4X \r\n", dev_id.product_code_2 );
log_printf( &logger, " SPI Frame ID : 0x%.4X \r\n", dev_id.spi_frame_id );
log_printf( &logger, "--------------------------------\r\n" );
Delay_ms ( 100 );
Delay_ms ( 100 );
log_printf( &logger, "\t>>> START <<<\r\n" );
display_status( );
Delay_ms ( 1000 );
}
#define HBRIDGEDRIVER2_MAP_MIKROBUS(cfg, mikrobus)
MikroBUS pin mapping.
Definition hbridgedriver2.h:240
err_t hbridgedriver2_pwm_start(hbridgedriver2_t *ctx)
H-Bridge Driver 2 start PWM module.
err_t hbridgedriver2_set_duty_cycle(hbridgedriver2_t *ctx, float duty_cycle)
H-Bridge Driver 2 sets PWM duty cycle.
err_t hbridgedriver2_get_device_id(hbridgedriver2_t *ctx, uint8_t *global_fault, hbridgedriver2_dev_id_t *dev_id)
H-Bridge Driver 2 get device ID function.
err_t hbridgedriver2_enable(hbridgedriver2_t *ctx)
H-Bridge Driver 2 enable function.
@ HBRIDGEDRIVER2_ERROR
Definition hbridgedriver2.h:339
void application_init(void)
Definition main.c:86
Application Task
This example demonstrates the use of the H-Bridge Driver 2 Click board™. The application turns connected MOSFETs gates high or low in order to drive the motor forward, backward, stop with brake or stop. Results are being sent to the Usart Terminal, where you can track their changes.
{
log_printf( &logger, "\t>>> Run Forward\r\n" );
display_status( );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
log_printf( &logger, "\t>>> Stop With Brake\r\n" );
display_status( );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
log_printf( &logger, "\t>>> Run Backward\r\n" );
display_status( );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
log_printf( &logger, "\t>>> Stop\r\n" );
display_status( );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
}
err_t hbridgedriver2_stop(hbridgedriver2_t *ctx, uint8_t *global_fault)
H-Bridge Driver 2 stop function.
void application_task(void)
Definition main.c:147
Additional Function
display_status
Display status function. static void display_status ( void );
The full application code, and ready to use projects can be installed directly from NECTO Studio Package Manager(recommended way), downloaded from our LibStock™ or found on Mikroe github account.
Other Mikroe Libraries used in the example:
- MikroSDK.Board
- MikroSDK.Log
- Click.HBridgeDriver2
Additional notes and informations
Depending on the development board you are using, you may need USB UART click, USB UART 2 Click or RS232 Click to connect to your PC, for development systems with no UART to USB interface available on the board. The terminal available in all MikroElektronika compilers, or any other terminal application of your choice, can be used to read the message.