Enable bidirectional motor driving with AP1010 and MK64FN1M0VDC12
Power? Precision? Our H-bridge driver delivers!
Published May 31, 2023
Click board™
H-Bridge 4 Click
Dev. board
Clicker 2 for Kinetis
Compiler
NECTO Studio
MCU
MK64FN1M0VDC12
Elevate your motors, empower your solution, and unlock new possibilities with this solution by using two brushed motors or one stepper motor!
A
A
Hardware Overview
How does it work?
H-Bridge 4 Click is based on the AP1010AEN, a two-channel H-Bridge motor driver from AKM Semiconductor compatible with motor operating voltage up to. This IC is an efficient integrated H-bridge driver with low RDS ON output per switch. H-bridge, in general, allows the current to flow in one or another direction. 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 IN1, IN2, IN3, and IN4, routed to the AN, RST, INT, and PWM pins on
the mikroBUS™, respectively. Its motor operating voltage range is between 6V～18V, and the control power supply is unnecessary. Its maximum output current (DC) is 0.7A @Ta=25°C and has H-Bridge On-Resistance, which equals RON(TOP+BOT) = 1.1Ω @Ta=25°C. The Click board™ has an onboard motor supply voltage selection switch, although using the external power supply is recommended. The AP1010AEN also has a parallel connection undervoltage lockout and thermal shutdown circuits. When the current of 2.6A or more continues to flow to the
H-Bridge driver for 10μs, all H-Bridge driver outputs are set to Hi-Z and automatically return after 200ms. This Click board™ can operate with either 3.3V or 5V logic voltage levels. 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
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 4 Click driver.
Key functions:
hbridge4_motorAStandby- Function is used to put motor A into standby.hbridge4_motorACW- Function is used to put motor A into clockwise motion.hbridge4_motorABrake- Function is used to brake motor A to a halt.
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
* \brief H-Bridge 4 Click example
*
* # Description
* This application is used to turn on DC or Stepper motors.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initialization driver enables GPIO and also starts write log.
*
* ## Application Task
* This example demonstrates the use of H-Bridge 4 click board by putting A motor
* in standby mode, then spining it in clockwise direction and applying brake function, and then
* spining it in counter-clockwise direction and applying brake function again.
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "hbridge4.h"
// ------------------------------------------------------------------ VARIABLES
static hbridge4_t hbridge4;
static log_t logger;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
hbridge4_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 ----\r\n" );
// Click initialization.
hbridge4_cfg_setup( &cfg );
HBRIDGE4_MAP_MIKROBUS( cfg, MIKROBUS_1 );
hbridge4_init( &hbridge4, &cfg );
hbridge4_enable( &hbridge4, 1 );
Delay_ms( 100 );
log_printf( &logger, "------------------- \r\n" );
log_printf( &logger, " H-Bridge 4 click \r\n" );
log_printf( &logger, "------------------- \r\n" );
}
void application_task ( )
{
log_printf( &logger, "The motor A is in standby mode \r\n" );
hbridge4_motor_a_standby( &hbridge4 );
Delay_ms( 100 );
log_printf( &logger, "The motor A turns clockwise \r\n" );
hbridge4_motor_acw( &hbridge4 );
Delay_ms( 2000 );
log_printf( &logger, "The motor A applies brake \r\n" );
hbridge4_motor_a_brake( &hbridge4 );
Delay_ms( 1000 );
log_printf( &logger, "The motor A turns counter-clockwise \r\n" );
hbridge4_motor_accw( &hbridge4 );
Delay_ms( 2000 );
log_printf( &logger, "The motor A applies brake \r\n" );
hbridge4_motor_a_brake( &hbridge4 );
Delay_ms( 1000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
