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
UNI-DS v8 is a development board specially designed for the needs of rapid development of embedded applications. It supports a wide range of microcontrollers, such as different STM32, Kinetis, TIVA, CEC, MSP, PIC, dsPIC, PIC32, and AVR MCUs regardless of their number of pins, and a broad set of unique functions, such as the first-ever embedded debugger/programmer over WiFi. 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, UNI-DS v8 provides a fluid and immersive working experience, allowing access anywhere and under any
circumstances at any time. Each part of the UNI-DS v8 development board contains the components necessary for the most efficient operation of the same board. An advanced integrated CODEGRIP programmer/debugger module offers many valuable programming/debugging options, including support for JTAG, SWD, and SWO Trace (Single Wire Output)), and seamless integration with the Mikroe software environment. Besides, it 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
HOST/DEVICE, CAN (on the MCU card, if supported), and Ethernet is also included. In addition, it also has the well-established mikroBUS™ standard, a standardized socket for the MCU card (SiBRAIN standard), and two display options for the TFT board line of products and character-based LCD. UNI-DS 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
Type
8th Generation
Architecture
ARM Cortex-M4
MCU Memory (KB)
1024
Silicon Vendor
Texas Instruments
Pin count
128
RAM (Bytes)
262144
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
Schematic
Step by step
Project assembly
Track your results in real time
Application Output via UART Mode
1. Once the code example is loaded, pressing the "FLASH" button initiates the build process, and programs it on the created setup.
2. After the programming is completed, click on the Tools icon in the upper-right panel, and select the UART Terminal.
3. After opening the UART Terminal tab, first check the baud rate setting in the Options menu (default is 115200). If this parameter is correct, activate the terminal by clicking the "CONNECT" button.
4. Now terminal status changes from Disconnected to Connected in green, and the data is displayed in the Received data field.
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
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 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