Drive external MOSFETs to control DC motors! Take the first step towards engineering greatness.
A
A
Hardware Overview
How does it work?
H-Bridge Driver 2 Click is based on the NCV7535, H-bridge gate driver (or full-bridge pre-driver) with independent high and low-side driver channels from ON Semiconductor. This monolithic H−bridge pre-driver has an enhanced feature set helpful in various applications for a DC motor drive. It allows bi-directional or uni-directional motor operations with integrated MOSFET and load protection. The onboard VIN terminal is the device's power supply input, allowing a wide operating voltage range from 6V to 18V. The NCV7535 also has built-in protection against short-circuit and overtemperature conditions,
under-voltage (UV), overvoltage (OV), and overcurrent events. When the supply returns to a level above the UV threshold or below the OV threshold, the device resumes regular operation according to the established condition of the input pins. H-Bridge Driver 2 Click communicates with MCU through a standard SPI interface supporting the common SPI mode, SPI Mode 0, providing data in a digital format of 24 bits. It also uses the Enable pin labeled as EN and routed to the RST pin of the mikroBUS™ socket to optimize power consumption, used for its power ON/OFF purposes. Besides, the user can use the PWM
signal from the mikroBUS™ socket, combined with the SPI interface and its control register, and use active or passive free-wheeling bridge configurations. This Click board™ can operate with either 3.3V or 5V logic voltage levels selected via the VCC SEL jumper. This way, both 3.3V and 5V capable MCUs can use the communication lines properly. The Click board™ comes equipped with a library containing easy-to-use functions and an example code that can be used, as a reference, for further development.
Features overview
Development board
Nucleo-64 with STM32G071RB MCU offers a cost-effective and adaptable platform for developers to explore new ideas and prototype their designs. This board harnesses the versatility of the STM32 microcontroller, enabling users to select the optimal balance of performance and power consumption for their projects. It accommodates the STM32 microcontroller in the LQFP64 package and includes essential components such as a user LED, which doubles as an ARDUINO® signal, alongside user and reset push-buttons, and a 32.768kHz crystal oscillator for precise timing operations. Designed with expansion and flexibility in mind, the Nucleo-64 board features an ARDUINO® Uno V3 expansion connector and ST morpho extension pin
headers, granting complete access to the STM32's I/Os for comprehensive project integration. Power supply options are adaptable, supporting ST-LINK USB VBUS or external power sources, ensuring adaptability in various development environments. The board also has an on-board ST-LINK debugger/programmer with USB re-enumeration capability, simplifying the programming and debugging process. Moreover, the board is designed to simplify advanced development with its external SMPS for efficient Vcore logic supply, support for USB Device full speed or USB SNK/UFP full speed, and built-in cryptographic features, enhancing both the power efficiency and security of projects. Additional connectivity is
provided through dedicated connectors for external SMPS experimentation, a USB connector for the ST-LINK, and a MIPI® debug connector, expanding the possibilities for hardware interfacing and experimentation. Developers will find extensive support through comprehensive free software libraries and examples, courtesy of the STM32Cube MCU Package. This, combined with compatibility with a wide array of Integrated Development Environments (IDEs), including IAR Embedded Workbench®, MDK-ARM, and STM32CubeIDE, ensures a smooth and efficient development experience, allowing users to fully leverage the capabilities of the Nucleo-64 board in their projects.
Microcontroller Overview
MCU Card / MCU
Architecture
ARM Cortex-M0
MCU Memory (KB)
128
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
36864
You complete me!
Accessories
Click Shield for Nucleo-64 comes equipped with two proprietary mikroBUS™ sockets, allowing all the Click board™ devices to be interfaced with the STM32 Nucleo-64 board with no effort. This way, Mikroe allows its users to add any functionality from our ever-growing range of Click boards™, such as WiFi, GSM, GPS, Bluetooth, ZigBee, environmental sensors, LEDs, speech recognition, motor control, movement sensors, and many more. More than 1537 Click boards™, which can be stacked and integrated, are at your disposal. The STM32 Nucleo-64 boards are based on the microcontrollers in 64-pin packages, a 32-bit MCU with an ARM Cortex M4 processor operating at 84MHz, 512Kb Flash, and 96KB SRAM, divided into two regions where the top section represents the ST-Link/V2 debugger and programmer while the bottom section of the board is an actual development board. These boards are controlled and powered conveniently through a USB connection to program and efficiently debug the Nucleo-64 board out of the box, with an additional USB cable connected to the USB mini port on the board. Most of the STM32 microcontroller pins are brought to the IO pins on the left and right edge of the board, which are then connected to two existing mikroBUS™ sockets. This Click Shield also has several switches that perform functions such as selecting the logic levels of analog signals on mikroBUS™ sockets and selecting logic voltage levels of the mikroBUS™ sockets themselves. Besides, the user is offered the possibility of using any Click board™ with the help of existing bidirectional level-shifting voltage translators, regardless of whether the Click board™ operates at a 3.3V or 5V logic voltage level. Once you connect the STM32 Nucleo-64 board with our Click Shield for Nucleo-64, you can access hundreds of Click boards™, working with 3.3V or 5V logic voltage levels.
H-Bridge MOSFET board represents an easy-to-use adapter board that allows the user to exercise all the functions of the H-Bridge Driver Click board™. This board has five 5.08mm pitch screw terminals to connect power and loads easily. Three of them on the left side of the board are suitable for a target H-Bridge Driver Click board™ connection with appropriate high and low side gate drive channels used to control the outputs or functions inside the circuit. The first VIN terminal on the upper-left board side represents the PSMN019-100YLX MOSFET’s power supply connector, allowing an operating voltage range like the connected H-Bridge Driver Click board™. On the right side of the board, the OUT terminal is used to drive a load, such as a brushed DC motor. This board also provides two LED indicators labeled REVERSE and FORWARD to indicate when output operates reverse or forward.
DC Gear Motor - 430RPM (3-6V) represents an all-in-one combination of a motor and gearbox, where the addition of gear leads to a reduction of motor speed while increasing the torque output. This gear motor has a spur gearbox, making it a highly reliable solution for applications with lower torque and speed requirements. The most critical parameters for gear motors are speed, torque, and efficiency, which are, in this case, 520RPM with no load and 430RPM at maximum efficiency, alongside a current of 60mA and a torque of 50g.cm. Rated for a 3-6V operational voltage range and clockwise/counterclockwise rotation direction, this motor represents an excellent solution for many functions initially performed by brushed DC motors in robotics, medical equipment, electric door locks, and much more.
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Click board™ Schematic
Step by step
Project assembly
Track your results in real time
Application Output via Debug Mode
1. Once the code example is loaded, pressing the "DEBUG" button initiates the build process, programs it on the created setup, and enters Debug mode.
2. After the programming is completed, a header with buttons for various actions within the IDE becomes visible. Clicking the green "PLAY" button starts reading the results achieved with the Click board™. The achieved results are displayed in the Application Output tab.
Software Support
Library Description
This library contains API for H-Bridge Driver 2 Click driver.
Key functions:
hbridgedriver2_run_forward
- H-Bridge Driver 2 run forward functionhbridgedriver2_run_backward
- H-Bridge Driver 2 run backward functionhbridgedriver2_stop_with_brake
- H-Bridge Driver 2 stop with brake function
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 HBridgeDriver2 Click 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.
*
* ## 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.
*
* ## Additional Function
* - static void display_status ( void )
*
* @author Nenad Filipovic
*
*/
#include "board.h"
#include "log.h"
#include "hbridgedriver2.h"
static hbridgedriver2_t hbridgedriver2;
static log_t logger;
static uint8_t global_fault;
static hbridgedriver2_dev_id_t dev_id;
static void display_status ( void )
{
uint16_t status;
log_printf( &logger, "- - - - - - - - - - - - - - - -\r\n" );
log_printf( &logger, " Status :" );
hbridgedriver2_get_status( &hbridgedriver2, &status );
if ( HBRIDGEDRIVER2_STAT_0_OCHS1 == status )
{
log_printf( &logger, " HS1 Over−current detected\r\n" );
}
if ( HBRIDGEDRIVER2_STAT_0_OCLS1 == status )
{
log_printf( &logger, " LS1 Over−current detected\r\n" );
}
if ( HBRIDGEDRIVER2_STAT_0_OCHS2 == status )
{
log_printf( &logger, " HS2 Over−current detected\r\n" );
}
if ( HBRIDGEDRIVER2_STAT_0_OCLS2 == status )
{
log_printf( &logger, " LS2 Over−current detected\r\n" );
}
if ( HBRIDGEDRIVER2_STAT_0_VSUV == status )
{
log_printf( &logger, " Under−voltage detected\r\n" );
}
if ( HBRIDGEDRIVER2_STAT_0_VSOV == status )
{
log_printf( &logger, " Overvoltage detected\r\n" );
}
if ( HBRIDGEDRIVER2_STAT_0_OK == status )
{
log_printf( &logger, " Normal Operation\r\n" );
}
log_printf( &logger, "--------------------------------\r\n" );
Delay_ms ( 100 );
}
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
hbridgedriver2_cfg_t hbridgedriver2_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.
hbridgedriver2_cfg_setup( &hbridgedriver2_cfg );
HBRIDGEDRIVER2_MAP_MIKROBUS( hbridgedriver2_cfg, MIKROBUS_1 );
if ( SPI_MASTER_ERROR == hbridgedriver2_init( &hbridgedriver2, &hbridgedriver2_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
Delay_ms ( 1000 );
hbridgedriver2_enable( &hbridgedriver2 );
Delay_ms ( 100 );
log_info( &logger, " Default config " );
if ( HBRIDGEDRIVER2_ERROR == hbridgedriver2_default_cfg ( &hbridgedriver2 ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
Delay_ms ( 1000 );
log_printf( &logger, "--------------------------------\r\n" );
Delay_ms ( 100 );
hbridgedriver2_get_device_id( &hbridgedriver2, &global_fault, &dev_id );
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 );
hbridgedriver2_set_duty_cycle ( &hbridgedriver2, 0.5 );
hbridgedriver2_pwm_start( &hbridgedriver2 );
Delay_ms ( 100 );
log_printf( &logger, "\t>>> START <<<\r\n" );
display_status( );
Delay_ms ( 1000 );
}
void application_task ( void )
{
log_printf( &logger, "\t>>> Run Forward\r\n" );
hbridgedriver2_run_forward( &hbridgedriver2, &global_fault );
display_status( );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
log_printf( &logger, "\t>>> Stop With Brake\r\n" );
hbridgedriver2_stop_with_brake( &hbridgedriver2, &global_fault );
display_status( );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
log_printf( &logger, "\t>>> Run Backward\r\n" );
hbridgedriver2_run_backward( &hbridgedriver2, &global_fault );
display_status( );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
log_printf( &logger, "\t>>> Stop\r\n" );
hbridgedriver2_stop( &hbridgedriver2, &global_fault );
display_status( );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
}
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