With our H-Bridge motor driver solution, you can effortlessly control the rotation and torque of your DC motors, allowing for smooth and precise movement in robotics, automation, and more
A
A
Hardware Overview
How does it work?
H-Bridge 3 Click is based on the TLE9201SG, an H-Bridge DC motor driver, with up to 28V and 6A, from Infineon. This IC is an efficient integrated H-bridge driver with a low RDS ON output per switch. H-bridge, in general, allows the current to flow in one or another direction. All internal supply voltages are derived from the external VIN connector. A charge pump provides the gate voltage for the high-side switches. The output buffer of the digital output SO is supplied by the pin VSO. Therefore the output logic level at SO can be easily configured for 3.3 V or 5 V logic by moving the VCC SEL jumper to the respective voltage. The output stages consist of four n-channel MOSFETs in an H-bridge configuration.
The outputs are protected against short circuits and over-temperature. The bridge is controlled using the inputs PWM and DIR. The signal at DIR defines the direction of the driven DC motor, whereas the PWM signal sets the duty cycle. The outputs can be set tristate (i.e., high side and low side switches are turned off) by setting DIS to a high level. The TLE9201SG is equipped with a “Serial Peripheral Interface“ (SPI) for diagnosis purposes. The H-bridge 3 click is configured as a “slave” device. This means that the host microcontroller, as the master, is providing the chip select (CS) and the clock signal (SCK). A data transfer on the SPI bus is initiated with a falling edge on CS and is terminated by a rising edge
on CS. The serial input pin SI data is sampled with the falling edge of SCK, and the rising clock edge determines the serial data output at MISO. The data is transferred “MSB first. The word length of the SPI is 8-bit. Please note that there is no check for the number of clocks within an SPI frame. Any low pulse at the CS line will be regarded as one frame. 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. However, 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
Arduino UNO is a versatile microcontroller board built around the ATmega328P chip. It offers extensive connectivity options for various projects, featuring 14 digital input/output pins, six of which are PWM-capable, along with six analog inputs. Its core components include a 16MHz ceramic resonator, a USB connection, a power jack, an
ICSP header, and a reset button, providing everything necessary to power and program the board. The Uno is ready to go, whether connected to a computer via USB or powered by an AC-to-DC adapter or battery. As the first USB Arduino board, it serves as the benchmark for the Arduino platform, with "Uno" symbolizing its status as the
first in a series. This name choice, meaning "one" in Italian, commemorates the launch of Arduino Software (IDE) 1.0. Initially introduced alongside version 1.0 of the Arduino Software (IDE), the Uno has since become the foundational model for subsequent Arduino releases, embodying the platform's evolution.
Microcontroller Overview
MCU Card / MCU
Architecture
AVR
MCU Memory (KB)
32
Silicon Vendor
Microchip
Pin count
32
RAM (Bytes)
2048
You complete me!
Accessories
Click Shield for Arduino UNO has two proprietary mikroBUS™ sockets, allowing all the Click board™ devices to be interfaced with the Arduino UNO board without effort. The Arduino Uno, a microcontroller board based on the ATmega328P, provides an affordable and flexible way for users to try out new concepts and build prototypes with the ATmega328P microcontroller from various combinations of performance, power consumption, and features. The Arduino Uno has 14 digital input/output pins (of which six can be used as PWM outputs), six analog inputs, a 16 MHz ceramic resonator (CSTCE16M0V53-R0), a USB connection, a power jack, an ICSP header, and reset button. Most of the ATmega328P 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 Arduino UNO board with our Click Shield for Arduino UNO, you can access hundreds of Click boards™, working with 3.3V or 5V logic voltage levels.
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
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 3 Click driver.
Key functions:
hbridge3_set_duty_cycle
- This function sets the PWM duty cyclehbridge3_spi
- This function sends SPI command and receives response to command senthbridge3_generic_transfer
- Generic SPI transfer, for sending and receiving packages
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 HBridge3 Click example
*
* # Description
* H-bridge in general, allows the current to flow in one or another direction.
* This click is used for driving a H-Bridge motor by changing output states.
* The outputs can be pulse width modulated at frequencies up to 20kHz by means of PWM/DIR control.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes SPI and LOG modules, AN, RST, CS and PWM pins
*
* ## Application Task
* This example demonstrates the use of H-Bridge 3 Click board,
* by running dc motor in both directions - increasing and decreasing PWM duty cycle.
* Results are being sent to the Usart Terminal where you can track their changes.
*
*
* @author Nikola Peric
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "hbridge3.h"
// ------------------------------------------------------------------ VARIABLES
static hbridge3_t hbridge3;
static log_t logger;
uint8_t motor_direction = 0;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
hbridge3_cfg_t cfg;
/**
* 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.
hbridge3_cfg_setup( &cfg );
HBRIDGE3_MAP_MIKROBUS( cfg, MIKROBUS_1 );
hbridge3_init( &hbridge3, &cfg );
Delay_ms( 500 );
hbridge3_pwm_start( &hbridge3 );
log_info( &logger, "---- Application Task ----" );
log_printf( &logger, "> CLOCKWISE <\r\n" );
}
void application_task ( void )
{
static int8_t duty_cnt = 1;
static int8_t duty_inc = 1;
float duty = duty_cnt / 10.0;
hbridge3_set_duty_cycle ( &hbridge3, 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;
if ( motor_direction == 1 )
{
log_printf( &logger, "> COUNTER CLOCKWISE <\r\n" );
motor_direction = 0;
hbridge3_dir_set ( &hbridge3 , 0 );
}
else if ( motor_direction == 0 )
{
log_printf( &logger, "> CLOCKWISE <\r\n" );
motor_direction = 1;
hbridge3_dir_set ( &hbridge3 , 1 );
}
}
duty_cnt += duty_inc;
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END