The ultimate solution for precision motor control and seamless switching
A
A
Hardware Overview
How does it work?
H-Bridge 10 Click is based on the MP6523, a triple, half-bridge motor driver from Monolithic Power Systems (MPS). The MP6523 contains three MOSFET half-bridge outputs that can drive up to three different loads with separate controls for high-side or low-side MOSFETs from a standard serial data interface. It has a low quiescent current in standby mode, making it suitable for many applications. The input voltage ranges from 7V to 28V, with up to 0.9A output current capability per channel. Complete protection features include short-circuiting protection, under-voltage protection, and thermal shutdown.
This Click board™ communicates with MCU through a standard SPI interface and operates at clock rates up to 3MHz, providing data in a digital format of 16 bits. It also can be enabled or disabled through the EN pin of the mikroBUS™ socket, hence, offering a switch operation to turn ON/OFF power delivery to the MP6523. It also provides a fault status indication signal, labeled as FLT and routed to the INT pin of the mikroBUS™ socket, alongside its red LED indicator marked as FLT to indicate different fault conditions such as current limit and thermal shutdown. A unique addition that this board has is checking the
existence of an external power supply. By adding resistors R4 and R5, the user can monitor and check the presence of an external power supply on the VS terminal via the voltage divider routed to the AN pin of the mikroBUS™ socket. 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
EasyAVR v7 is the seventh generation of AVR development boards specially designed for the needs of rapid development of embedded applications. It supports a wide range of 16-bit AVR microcontrollers from Microchip and has a broad set of unique functions, such as a powerful onboard mikroProg programmer and In-Circuit debugger over USB. The development board is well organized and designed so that the end-user has all the necessary elements in one place, such as switches, buttons, indicators, connectors, and others. With four different connectors for each port, EasyAVR v7 allows you to connect accessory boards, sensors, and custom electronics more
efficiently than ever. Each part of the EasyAVR v7 development board contains the components necessary for the most efficient operation of the same board. An integrated mikroProg, a fast USB 2.0 programmer with mikroICD hardware In-Circuit Debugger, offers many valuable programming/debugging options and seamless integration with the Mikroe software environment. Besides it also includes a clean and regulated power supply block for the development board. It can use a wide range of external power sources, including an external 12V power supply, 7-12V AC or 9-15V DC via DC connector/screw terminals, and a power source via the USB Type-B (USB-B)
connector. Communication options such as USB-UART and RS-232 are also included, alongside the well-established mikroBUS™ standard, three display options (7-segment, graphical, and character-based LCD), and several different DIP sockets which cover a wide range of 16-bit AVR MCUs. EasyAVR v7 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
AVR
MCU Memory (KB)
128
Silicon Vendor
Microchip
Pin count
40
RAM (Bytes)
16384
You complete me!
Accessories
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
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 H-Bridge 10 Click driver.
Key functions:
hbridge10_set_output_state
This function sets the output channel state.hbridge10_get_status
This function reads the status of output register.hbridge10_get_fault_pin
This function returns the fault (FLT) pin logic state.
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 HBridge10 Click example
*
* # Description
* This example demonstrates the use of the H-Bridge 10 click board by
* driving the motors connected between OUT1-OUT2 and OUT2-OUT3 in both directions.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and performs the click default configuration.
*
* ## Application Task
* Drives the motors connected between OUT1-OUT2 and OUT2-OUT3 in both directions
* in the span of 6 seconds, and displays the status messages on the USB UART.
*
* @author Stefan Filipovic
*
*/
#include "board.h"
#include "log.h"
#include "hbridge10.h"
static hbridge10_t hbridge10;
static log_t logger;
/**
* @brief H-Bridge 10 display status function.
* @details This function parses the status from output register and displays it on the USB UART.
* @param[in] status : 16-bit status value.
* @return None.
* @note None.
*/
void hbridge10_display_status ( uint16_t status );
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
hbridge10_cfg_t hbridge10_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.
hbridge10_cfg_setup( &hbridge10_cfg );
HBRIDGE10_MAP_MIKROBUS( hbridge10_cfg, MIKROBUS_1 );
if ( SPI_MASTER_ERROR == hbridge10_init( &hbridge10, &hbridge10_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
if ( HBRIDGE10_ERROR == hbridge10_default_cfg ( &hbridge10 ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
uint16_t status;
if ( ( HBRIDGE10_OK == hbridge10_set_output_state ( &hbridge10, HBRIDGE10_CHANNEL_OUT1, HBRIDGE10_OUT_HIGH ) ) &&
( HBRIDGE10_OK == hbridge10_set_output_state ( &hbridge10, HBRIDGE10_CHANNEL_OUT2, HBRIDGE10_OUT_LOW ) ) &&
( HBRIDGE10_OK == hbridge10_set_output_state ( &hbridge10, HBRIDGE10_CHANNEL_OUT3, HBRIDGE10_OUT_HIGH ) ) )
{
Delay_ms ( 100 );
if ( HBRIDGE10_OK == hbridge10_get_status ( &hbridge10, &status ) )
{
hbridge10_display_status ( status );
Delay_ms ( 3000 );
}
}
if ( ( HBRIDGE10_OK == hbridge10_set_output_state ( &hbridge10, HBRIDGE10_CHANNEL_OUT1, HBRIDGE10_OUT_LOW ) ) &&
( HBRIDGE10_OK == hbridge10_set_output_state ( &hbridge10, HBRIDGE10_CHANNEL_OUT2, HBRIDGE10_OUT_HIGH ) ) &&
( HBRIDGE10_OK == hbridge10_set_output_state ( &hbridge10, HBRIDGE10_CHANNEL_OUT3, HBRIDGE10_OUT_LOW ) ) )
{
Delay_ms ( 100 );
if ( HBRIDGE10_OK == hbridge10_get_status ( &hbridge10, &status ) )
{
hbridge10_display_status ( status );
Delay_ms ( 3000 );
}
}
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
void hbridge10_display_status ( uint16_t status )
{
if ( HBRIDGE10_OUT_OVER_TEMP_SD == status )
{
log_printf ( &logger, " Over temperature shutdown! \r\n" );
return;
}
if ( status & HBRIDGE10_OUT_OVER_TEMP_WARNING )
{
log_printf ( &logger, " Over temperature pre-warning! \r\n" );
}
log_printf ( &logger, " OUT1 : " );
if ( status & HBRIDGE10_OUT_STATUS_LS1_ON )
{
log_printf ( &logger, "LOW \r\n" );
}
else if ( status & HBRIDGE10_OUT_STATUS_HS1_ON )
{
log_printf ( &logger, "HIGH \r\n" );
}
else
{
log_printf ( &logger, "OFF \r\n" );
}
log_printf ( &logger, " OUT2 : " );
if ( status & HBRIDGE10_OUT_STATUS_LS2_ON )
{
log_printf ( &logger, "LOW \r\n" );
}
else if ( status & HBRIDGE10_OUT_STATUS_HS2_ON )
{
log_printf ( &logger, "HIGH \r\n" );
}
else
{
log_printf ( &logger, "OFF \r\n" );
}
log_printf ( &logger, " OUT3 : " );
if ( status & HBRIDGE10_OUT_STATUS_LS3_ON )
{
log_printf ( &logger, "LOW \r\n" );
}
else if ( status & HBRIDGE10_OUT_STATUS_HS3_ON )
{
log_printf ( &logger, "HIGH \r\n" );
}
else
{
log_printf ( &logger, "OFF \r\n" );
}
if ( status & HBRIDGE10_OUT_SHORT_CIRCUIT_DETECTED )
{
log_printf ( &logger, " Short circuit detected! \r\n" );
}
log_printf ( &logger, " Power : " );
if ( HBRIDGE10_OUT_NORMAL_OPERATION != ( status & HBRIDGE10_OUT_NORMAL_OPERATION ) )
{
log_printf ( &logger, "Standby \r\n" );
}
else if ( status & HBRIDGE10_OUT_VS_UNDER_VOLTAGE )
{
log_printf ( &logger, "Under-voltage at VS detected \r\n" );
}
else
{
log_printf ( &logger, "Normal operation \r\n" );
}
log_printf ( &logger, "\r\n" );
}
// ------------------------------------------------------------------------ END