Ensure optimal performance for your DC motor applications with DRV8823 and MK64FN1M0VDC12
Experience DC motor control like never before with our H-Bridge solution, a powerhouse of innovation.
Published Nov 11, 2023
Click board™
H-Bridge 12 Click
Dev Board
Clicker 2 for Kinetis
Compiler
NECTO Studio
MCU
MK64FN1M0VDC12
Transform your motors into marvels of motion with our innovative H-Bridge solution. Unleash the potential of N-channel power MOSFETs configured in a full-bridge layout, delivering a symphony of power and precision to elevate your motor control experience to unparalleled heights.
A
A
Hardware Overview
How does it work?
H-Bridge 12 Click is based on the DRV8823, a four-bridge serial interface motor driver from Texas Instruments. Internally, the motor driver consists of four NMOS H-Bridges, a micro-stepping indexer, and various fault-protecting features. The motor driver is fully protected against overcurrent, overtemperature, undervoltage, and comes in a thermally-enhanced package. It can control motors that operate in an 8V to 32V voltage range, with up to 1.5A of current per winding. For this, it uses an internal charge pump for the gate drives. Eight current levels set through the serial interface allow micro-stepping with bipolar stepper motors. H-Bridge 12 Click uses a simple 3-Wire SPI
serial interface to communicate with the host MCU. In addition, this Click board™ uses some other pins from the mikroBUS™ socket, such as the RST pin for the device reset. The motor driver outputs can be turned off with the STB's pin LOW logic state while resetting the serial interface. Another neat feature is sleep, which can be activated with logic LOW on the SLP pin of the mikroBUS™ socket. There are two precision potentiometers labeled VREFA and VREFC. The VREFA supplies the referent voltage for setting the current trip threshold for bridges A and B, while the VREFC supplies the referent voltage for setting the current trip threshold for bridges C and D.
H-Bridge 12 Click comes with screw terminals for connecting an external motor power supply, labeled with ground and VM. The motors can be connected to 8 terminals appropriately labeled for every single motor output channel. The motor driver supports Brushed DC, Brushless DC, and Stepper motors. 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. Also, this 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
Clicker 2 for Kinetis is a compact starter development board that brings the flexibility of add-on Click boards™ to your favorite microcontroller, making it a perfect starter kit for implementing your ideas. It comes with an onboard 32-bit ARM Cortex-M4F microcontroller, the MK64FN1M0VDC12 from NXP Semiconductors, two mikroBUS™ sockets for Click board™ connectivity, a USB connector, LED indicators, buttons, a JTAG programmer connector, and two 26-pin headers for interfacing with external electronics. Its compact design with clear and easily recognizable silkscreen markings allows you to build gadgets with unique functionalities and
features quickly. Each part of the Clicker 2 for Kinetis development kit contains the components necessary for the most efficient operation of the same board. In addition to the possibility of choosing the Clicker 2 for Kinetis programming method, using a USB HID mikroBootloader or an external mikroProg connector for Kinetis programmer, the Clicker 2 board also includes a clean and regulated power supply module for the development kit. It provides two ways of board-powering; through the USB Micro-B cable, where onboard voltage regulators provide the appropriate voltage levels to each component on the board, or
using a Li-Polymer battery via an onboard battery connector. All communication methods that mikroBUS™ itself supports are on this board, including the well-established mikroBUS™ socket, reset button, and several user-configurable buttons and LED indicators. Clicker 2 for Kinetis is an integral part of the Mikroe ecosystem, allowing you to create a new application in minutes. Natively supported by Mikroe software tools, it covers many aspects of prototyping 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
ARM Cortex-M4
MCU Memory (KB)
1024
Silicon Vendor
NXP
Pin count
121
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
Click board™ Schematic
Step by step
Project assembly
Start by selecting your development board and Click board™. Begin with the Clicker 2 for Kinetis as your development board.
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 12 Click driver.
Key functions:
hbridge12_write_config- H-Bridge 12 write settings function.hbridge12_set_current_scale- H-Bridge 12 set current scale function.hbridge12_turn_clockwise- H-Bridge 12 turn motor clockwise function.
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 H-Bridge 12 Click example
*
* # Description
* This example demonstrates the use of the H-Bridge 12 click board by
* driving the motor connected to OUT A and OUT B, in both directions with braking and freewheeling.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and performs the click default configuration.
*
* ## Application Task
* Driving motor in both directions for 5 seconds with a motor braking and freewheeling in between.
*
* @author Stefan Ilic
*
*/
#include "board.h"
#include "log.h"
#include "hbridge12.h"
static hbridge12_t hbridge12;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
hbridge12_cfg_t hbridge12_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.
hbridge12_cfg_setup( &hbridge12_cfg );
HBRIDGE12_MAP_MIKROBUS( hbridge12_cfg, MIKROBUS_1 );
if ( SPI_MASTER_ERROR == hbridge12_init( &hbridge12, &hbridge12_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
if ( HBRIDGE12_ERROR == hbridge12_default_cfg ( &hbridge12 ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
log_printf( &logger, " Turning motor counterclockwise \r\n" );
hbridge12_turn_counterclockwise( &hbridge12, HBRIDGE12_AB_BRIDGE_SEL );
Delay_ms( 5000 );
log_printf( &logger, " Turning motor brake on \r\n" );
hbridge12_turn_brake_on( &hbridge12, HBRIDGE12_AB_BRIDGE_SEL );
Delay_ms( 5000 );
log_printf( &logger, " Turning motor clockwise \r\n" );
hbridge12_turn_clockwise( &hbridge12, HBRIDGE12_AB_BRIDGE_SEL );
Delay_ms( 5000 );
log_printf( &logger, " Motor freewheeling \r\n" );
hbridge12_freewheeling_on( &hbridge12, HBRIDGE12_AB_BRIDGE_SEL );
Delay_ms( 5000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
