Our brushed DC motor driver puts you in command, ensuring your motors dance to your tune with precision and reliability.
A
A
Hardware Overview
How does it work?
DC Motor 27 Click is based on the DRV8143, an automotive half-bridge driver with integrated current sense and diagnostic from Texas Instruments. The driver integrates an N-channel half-bridge charge pump regulator, high-side current sensing with regulation, current proportional output, and protection circuitry. It offers configurable current regulation, slew rate, spread spectrum clocking for low EMI, PWM frequency operation up to 125KHz with automatic dead time assertion, and more. The integrated current sense eliminates the need for a shunt resistor, and the driver supports a wide range of
output currents for various types of motors and loads. The device operates from a single power supply input (VM) available on the output terminal. The DC Motor 27 Click offers a VM SEL jumper that allows you to choose the power supply input from the external over the VEXT terminal and a 5V from the power rail of the mikroBUS™ socket. The EXT is set by default, so you should apply the appropriate voltage on the VEXT terminal. DC Motor 27 Click uses a static pulse-width modulated (PWM) voltage signal to communicate with the host MCU, supporting either 100% or PWM drive modes. By resetting the
driver over the RST pin, you also turn OFF a controller input for bridge Hi-Z. You can always monitor the load current over the IP pin as an analog output of the driver. The driver uses the FLT pin to inform the host MCU of faults caused by load, overvoltage, and under-voltage on the VM pin. 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 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
28
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
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 DC Motor 27 Click driver.
Key functions:
dcmotor27_set_duty_cycle
- DC Motor 27 sets PWM duty cycle.dcmotor27_get_flt_pin
- DC Motor 27 get flt pin state.dcmotor27_set_coast
- DC Motor 27 set coast mode funtion.
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 DC Motor 27 Click example
*
* # Description
* This example demonstrates the use of the DC Motor 27 Click board by driving
* the motor at different speeds, enabling brake and coast modes.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and performs the click default configuration.
*
* ## Application Task
* Controls the motor speed by changing the PWM duty cycle every second,
* places the motor into coast or braking mode.
*
* @author Stefan Ilic
*
*/
#include "board.h"
#include "log.h"
#include "dcmotor27.h"
static dcmotor27_t dcmotor27;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
dcmotor27_cfg_t dcmotor27_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.
dcmotor27_cfg_setup( &dcmotor27_cfg );
DCMOTOR27_MAP_MIKROBUS( dcmotor27_cfg, MIKROBUS_1 );
if ( PWM_ERROR == dcmotor27_init( &dcmotor27, &dcmotor27_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
if ( DCMOTOR27_ERROR == dcmotor27_default_cfg ( &dcmotor27 ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
for ( uint8_t speed_cnt = 10; speed_cnt <= 100; speed_cnt += 10 )
{
float speed = ( float ) speed_cnt / 100;
dcmotor27_set_duty_cycle( &dcmotor27, speed );
log_printf( &logger, " Motor speed %d%% \r\n", ( uint16_t ) speed_cnt );
Delay_ms( 1000 );
}
log_printf( &logger, " Motor coasting \r\n" );
dcmotor27_set_coast( &dcmotor27, DCMOTOR27_SET_COAST_ON );
Delay_ms( 2000 );
dcmotor27_set_coast( &dcmotor27, DCMOTOR27_SET_COAST_OFF );
for ( uint8_t speed_cnt = 10; speed_cnt <= 100; speed_cnt += 10 )
{
float speed = ( float ) speed_cnt / 100;
dcmotor27_set_duty_cycle( &dcmotor27, speed );
log_printf( &logger, " Motor speed %d%% \r\n", ( uint16_t ) speed_cnt );
Delay_ms( 1000 );
}
log_printf( &logger, " Motor brake is on \r\n" );
dcmotor27_pwm_stop( &dcmotor27 );
Delay_ms( 2000 );
dcmotor27_pwm_start( &dcmotor27 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
Additional Support
Resources
Category:Brushed