Optimize your motors, maximize efficiency, and engineer with confidence. Embrace brushed motor control up to 5A of current!
A
A
Hardware Overview
How does it work?
DC Motor 18 Click is based on the TB9051FTG, a motor driver incorporating the output driver for the direct drive of a DC brushed motor intended for automotive use from Toshiba Semiconductor. While primarily targeting vehicle engine applications, such as electronic throttle and valve control, the TB9051FTG can also be suitable for controlling onboard systems operating at up to 5A, such as control of wing mirrors and trunk locks. Control functions include motor-related (forward, reverse, brake), PWM control, current limit control, H-side current monitor, diagnosis output, and built-in detection circuits for overcurrent, overheat, and low/high voltage. DC Motor 18 Click communicates with MCU using several GPIO pins. The Enable pin, labeled as EN and routed to the CS pin of the mikroBUS™ socket, optimizes power consumption and is used for power ON/OFF purposes (driver operation permission). The
Forward/Reverse/Brake mode can be selected according to PWM control signals routed to the PWN and RST pins of the mikroBUS™ socket. The current, which flows to the high side in the H-bridge of motor-driven output, is monitored in real time, where the user can select the way of the current monitoring. In the case of a 5V VCC power supply, the current can be monitored using an AN pin on the mikroBUS™ socket. In the case of a lesser power supply (3.3V), monitoring is possible with the help of an added voltage divider between the OCM pin and GND. Selection can be performed by onboard SMD jumper labeled as ADC SEL. This Click board™ also has an additional LED for anomaly indication. Suppose a state such as an overtemperature or overcurrent/under voltage is detected. In that case, such anomaly is indicated by a red LED marked as DIAG, which is also connected to the interrupt INT pin through
which the user can also monitor the state of the diagnostic pin. In addition, the motor control output can be controlled at the time of the overcurrent detection, which is realized through an onboard switch labeled as OCC. This switch judges whether the motor control output is ON(1) or OFF(0). This board supports an external power supply for the TB9051FTG, which can be connected to the input terminal labeled as VM within the range of 4.5V to 28V, while the DC motor coils can be connected to the terminals labeled as OUT1 and OUT2. 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. 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
Nucleo-64 with STM32F410RB MCU offers a cost-effective and adaptable platform for developers to explore new ideas and prototype their designs. This board harnesses the versatility of the STM32 microcontroller, enabling users to select the optimal balance of performance and power consumption for their projects. It accommodates the STM32 microcontroller in the LQFP64 package and includes essential components such as a user LED, which doubles as an ARDUINO® signal, alongside user and reset push-buttons, and a 32.768kHz crystal oscillator for precise timing operations. Designed with expansion and flexibility in mind, the Nucleo-64 board features an ARDUINO® Uno V3 expansion connector and ST morpho extension pin
headers, granting complete access to the STM32's I/Os for comprehensive project integration. Power supply options are adaptable, supporting ST-LINK USB VBUS or external power sources, ensuring adaptability in various development environments. The board also has an on-board ST-LINK debugger/programmer with USB re-enumeration capability, simplifying the programming and debugging process. Moreover, the board is designed to simplify advanced development with its external SMPS for efficient Vcore logic supply, support for USB Device full speed or USB SNK/UFP full speed, and built-in cryptographic features, enhancing both the power efficiency and security of projects. Additional connectivity is
provided through dedicated connectors for external SMPS experimentation, a USB connector for the ST-LINK, and a MIPI® debug connector, expanding the possibilities for hardware interfacing and experimentation. Developers will find extensive support through comprehensive free software libraries and examples, courtesy of the STM32Cube MCU Package. This, combined with compatibility with a wide array of Integrated Development Environments (IDEs), including IAR Embedded Workbench®, MDK-ARM, and STM32CubeIDE, ensures a smooth and efficient development experience, allowing users to fully leverage the capabilities of the Nucleo-64 board in their projects.
Microcontroller Overview
MCU Card / MCU

Architecture
ARM Cortex-M4
MCU Memory (KB)
128
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
32768
You complete me!
Accessories
Click Shield for Nucleo-64 comes equipped with two proprietary mikroBUS™ sockets, allowing all the Click board™ devices to be interfaced with the STM32 Nucleo-64 board with no effort. This way, Mikroe allows its users to add any functionality from our ever-growing range of Click boards™, such as WiFi, GSM, GPS, Bluetooth, ZigBee, environmental sensors, LEDs, speech recognition, motor control, movement sensors, and many more. More than 1537 Click boards™, which can be stacked and integrated, are at your disposal. The STM32 Nucleo-64 boards are based on the microcontrollers in 64-pin packages, a 32-bit MCU with an ARM Cortex M4 processor operating at 84MHz, 512Kb Flash, and 96KB SRAM, divided into two regions where the top section represents the ST-Link/V2 debugger and programmer while the bottom section of the board is an actual development board. These boards are controlled and powered conveniently through a USB connection to program and efficiently debug the Nucleo-64 board out of the box, with an additional USB cable connected to the USB mini port on the board. Most of the STM32 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 STM32 Nucleo-64 board with our Click Shield for Nucleo-64, 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 18 Click driver.
Key functions:
dcmotor18_set_speed_percentage
- Set speed output percentagedcmotor18_set_enable
- Set enable pin statedcmotor18_read_an_pin_current
- Read AN pin current
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 DCMotor18 Click example
*
* # Description
* This example application showcases ability of click
* board to control DC motors using PWM modulation in
* both directions and different speeds.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initialization of MCU communication modules (PWM, ADC, UART)
* and additioal gpio for control of the device. Then sets
* default configuration that enables device to control the DC motor.
*
* ## Application Task
* Drives motor in one direction from 0 to 100% of the speed using
* PWM, and then returns it back to 0. Then changes the rotation
* direction and repeats the process of increasing and decreasing
* acceleration.
*
* @author Luka Filipovic
*
*/
#include "board.h"
#include "log.h"
#include "dcmotor18.h"
static dcmotor18_t dcmotor18;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
dcmotor18_cfg_t dcmotor18_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.
dcmotor18_cfg_setup( &dcmotor18_cfg );
DCMOTOR18_MAP_MIKROBUS( dcmotor18_cfg, MIKROBUS_1 );
err_t init_flag = dcmotor18_init( &dcmotor18, &dcmotor18_cfg );
if ( PWM_ERROR == init_flag )
{
log_error( &logger, " Application Init Error. " );
log_info( &logger, " Please, run program again... " );
for ( ; ; );
}
dcmotor18_default_cfg ( &dcmotor18 );
log_info( &logger, " Application Task " );
Delay_ms ( 500 );
}
void application_task ( void )
{
static int8_t duty_cnt = 1;
static int8_t duty_inc = 1;
float speed = duty_cnt / 10.0;
static uint8_t direction = 1;
dcmotor18_set_direction( &dcmotor18, direction );
dcmotor18_set_speed_percentage ( &dcmotor18, speed );
if ( dcmotor18.direction )
{
log_printf( &logger, "<<< " );
}
else
{
log_printf( &logger, ">>> " );
}
log_printf( &logger, "Speed: %d%%\r\n", ( uint16_t )( duty_cnt * 10 ) );
if ( 10 == duty_cnt )
{
duty_inc = -1;
}
else if ( 0 == duty_cnt )
{
duty_inc = 1;
direction = !direction;
}
duty_cnt += duty_inc;
Delay_ms ( 1000 );
}
int main ( void )
{
/* Do not remove this line or clock might not be set correctly. */
#ifdef PREINIT_SUPPORTED
preinit();
#endif
application_init( );
for ( ; ; )
{
application_task( );
}
return 0;
}
// ------------------------------------------------------------------------ END
/*!
* @file main.c
* @brief DCMotor18 Click example
*
* # Description
* This example application showcases ability of click
* board to control DC motors using PWM modulation in
* both directions and different speeds.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initialization of MCU communication modules (PWM, ADC, UART)
* and additioal gpio for control of the device. Then sets
* default configuration that enables device to control the DC motor.
*
* ## Application Task
* Drives motor in one direction from 0 to 100% of the speed using
* PWM, and then returns it back to 0. Then changes the rotation
* direction and repeats the process of increasing and decreasing
* acceleration.
*
* @author Luka Filipovic
*
*/
#include "board.h"
#include "log.h"
#include "dcmotor18.h"
static dcmotor18_t dcmotor18;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
dcmotor18_cfg_t dcmotor18_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.
dcmotor18_cfg_setup( &dcmotor18_cfg );
DCMOTOR18_MAP_MIKROBUS( dcmotor18_cfg, MIKROBUS_1 );
err_t init_flag = dcmotor18_init( &dcmotor18, &dcmotor18_cfg );
if ( PWM_ERROR == init_flag )
{
log_error( &logger, " Application Init Error. " );
log_info( &logger, " Please, run program again... " );
for ( ; ; );
}
dcmotor18_default_cfg ( &dcmotor18 );
log_info( &logger, " Application Task " );
Delay_ms ( 500 );
}
void application_task ( void )
{
static int8_t duty_cnt = 1;
static int8_t duty_inc = 1;
float speed = duty_cnt / 10.0;
static uint8_t direction = 1;
dcmotor18_set_direction( &dcmotor18, direction );
dcmotor18_set_speed_percentage ( &dcmotor18, speed );
if ( dcmotor18.direction )
{
log_printf( &logger, "<<< " );
}
else
{
log_printf( &logger, ">>> " );
}
log_printf( &logger, "Speed: %d%%\r\n", ( uint16_t )( duty_cnt * 10 ) );
if ( 10 == duty_cnt )
{
duty_inc = -1;
}
else if ( 0 == duty_cnt )
{
duty_inc = 1;
direction = !direction;
}
duty_cnt += duty_inc;
Delay_ms ( 1000 );
}
int main ( void )
{
/* Do not remove this line or clock might not be set correctly. */
#ifdef PREINIT_SUPPORTED
preinit();
#endif
application_init( );
for ( ; ; )
{
application_task( );
}
return 0;
}
// ------------------------------------------------------------------------ END