Embrace the versatility of brushed motor control, offering four dynamic operational modes: forward, reverse, short brake, and full stop!
A
A
Hardware Overview
How does it work?
DC MOTOR 14 Click is based on the TB67H450AFNG, a PWM chopper-type brushed DC motor driver from Toshiba Semiconductor. This IC uses a proprietary BiCD manufacturing process, allowing this IC to be powered by a wide range of supply voltages, from 4.5 up to 44V. Due to the very low ON resistance of the MOSFETs, it can deliver up to 3.5A of current to the connected load. However, many external parameters affect both the maximum voltage and the current specifications, especially when the connected load is complex, such as the DC motor. In using TB67H450AFNG, the voltage should be applied to the pins of VM and VREF. The absolute maximum rating of VM supply voltage is 50V (no active). The usage range is 4.5 to 44V. The absolute maximum rating of VREF supply voltage is 5V. The usage range is 0 to 4V. There are no special procedures for inputting a power supply and shutdown feature because the TB67H450AFNG incorporates the under voltage lockout (UVLO). However, setting the motor operation to OFF is recommended under the unstable state of inputting the power supply (VM) and shutdown (transient area). After the power supply is stable, the motor should be operated by switching the input signal. The absolute maximum rating of motor output current is 3.5A. Its operating range is 3A or less. The maximum current of the actual usage is limited depending on the usage conditions (the ambient temperature, the wiring pattern of the board, the radiation path, and the exciting design).
Configure the most appropriate current value after calculating the heat and evaluating the board under the operating environment. When the logic signal is input under the condition that the voltage of the VM is not supplied, the electromotive force by an input signal is not generated. The speed of the motor can be controlled by Inputting the PWM signal to pins IN1 and IN2 and operating them with PWM control. When both IN1 and IN2 pins are set to L for 1 ms (typ.) or more, the operation mode enters the Standby mode. When IN1 or IN2 is set to H, the mode returns from the standby mode and enters the operation mode. When the constant current function is disabled, the RS pin should be connected to GND, and a voltage of 1 to 5V should be applied to the VREF pin. Maximum 30μs are required for the return time from the standby release. The OUT1 and OUT2 outputs operate after 30 μs (max) from the standby release. In this product, the current detection resistor sets a constant current threshold between RS and GND and VREF input voltage. When the constant current function is disabled, the RS pin should be connected to GND, and a voltage of 1 to 5V should be applied to the VREF pin. The constant current control is performed in Mixed Decay mode when the output current reaches the threshold due to forward and reverse rotation. In the case of the constant current control, the OFF time (toff) is fixed to 25 μs (typ.) to determine the pulse width of the current (current pulsating flow).
The percentage of Mixed Decay Mode is as follows; Fast Mode: 50% to Slow Mode: 50%. If the output current is zero-detected in Fast Mode, the outputs are in High impedance. When the junction temperature of the IC reaches the specified value, the internal detection circuit (TSD) operates to turn off the output block. It has a dead band time to prevent the IC from malfunctioning, caused by switching, and so on. Since the temperature has a hysteresis range when the junction temperature falls to the return temperature, the operation returns automatically to the normal operation. The TSD is triggered when the device is overheated irregularly. Make sure not to use the TSD function aggressively. When the IC detects an overcurrent, the internal circuit turns off the output block. It has a dead band time to avoid ISD misdetection, which may be triggered by external noise. The undervoltage detection circuit operates when the applied voltage of the VM pin falls 3.8V (typ.) or less. All output power transistors are turned off. The UVLO operation is released when the voltage applied to the VM pin rises 4.0V (typ.) or more. Although the TB67H450AFNG IC requires an external PSU, this Click board™ can operate with 5V MCUs only. The current detection resistor (R2) installed on click is 0.51 Ohm, set for a range from 0 to 1.5A. In the case of a range from 1.5 to 3A, that can be achieved by replacing it with a 0.22 Ohm resistor.
Features overview
Development board
EasyPIC v8 is a development board specially designed for the needs of rapid development of embedded applications. It supports many high pin count 8-bit PIC microcontrollers from Microchip, regardless of their number of pins, and a broad set of unique functions, such as the first-ever embedded debugger/programmer. 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, EasyPIC v8 provides a fluid and immersive working experience, allowing access anywhere and under any
circumstances at any time. Each part of the EasyPIC v8 development board contains the components necessary for the most efficient operation of the same board. In addition to the advanced integrated CODEGRIP programmer/debugger module, which offers many valuable programming/debugging options and seamless integration with the Mikroe software environment, the board 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 DEVICE, and CAN are also included, including the well-established mikroBUS™ standard, two display options (graphical and character-based LCD), and several different DIP sockets. These sockets cover a wide range of 8-bit PIC MCUs, from the smallest PIC MCU devices with only eight up to forty pins. EasyPIC 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
![default](https://dbp-cdn.mikroe.com/catalog/mcus/resources/PIC18F26K40.jpeg)
Architecture
PIC
MCU Memory (KB)
64
Silicon Vendor
Microchip
Pin count
28
RAM (Bytes)
3728
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
![DC Motor 14 Click Schematic schematic](https://dbp-cdn.mikroe.com/catalog/click-boards/resources/1ee790ad-d2dc-66e2-b4df-0242ac120009/schematic.webp)
Step by step
Project assembly
Track your results in real time
Application Output
After pressing the "FLASH" button on the left-side panel, it is necessary to open the UART terminal to display the achieved results. By clicking on the Tools icon in the right-hand panel, multiple different functions are displayed, among which is the UART Terminal. Click on the offered "UART Terminal" icon.
![UART Application Output Step 1](https://dbp-cdn.mikroe.com/cms/shared-resources/1eed703a-40a0-6b58-88de-02420a00029a/UART-AO-Step-1.jpg)
Once the UART terminal is opened, the window takes on a new form. At the top of the tab are two buttons, one for adjusting the parameters of the UART terminal and the other for connecting the UART terminal. The tab's lower part is reserved for displaying the achieved results. Before connecting, the terminal has a Disconnected status, indicating that the terminal is not yet active. Before connecting, it is necessary to check the set parameters of the UART terminal. Click on the "OPTIONS" button.
![UART Application Output Step 2](https://dbp-cdn.mikroe.com/cms/shared-resources/1eed703a-eb29-62fa-ba91-02420a00029a/UART-AO-Step-2.jpg)
In the newly opened UART Terminal Options field, we check if the terminal settings are correct, such as the set port and the Baud rate of UART communication. If the data is not displayed properly, it is possible that the Baud rate value is not set correctly and needs to be adjusted to 115200. If all the parameters are set correctly, click on "CONFIGURE".
![UART Application Output Step 3](https://dbp-cdn.mikroe.com/cms/shared-resources/1eed703b-7543-6fbc-9c69-0242ac120003/UART-AO-Step-3.jpg)
The next step is to click on the "CONNECT" button, after which the terminal status changes from Disconnected to Connected in green, and the data is displayed in the Received data field.
![UART Application Output Step 4](https://dbp-cdn.mikroe.com/cms/shared-resources/1eed703c-068c-66a4-a4fc-0242ac120003/UART-AO-Step-4.jpg)
Software Support
Library Description
This library contains API for DC Motor 14 Click driver.
Key functions:
void dcmotor14_forward ( );
- Function is used to drive the motor forward.void dcmotor14_reverse ( );
- Function is used to drive the motor reverse.void dcmotor14_brake ( );
- Function is used to brake the motor.
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
* \brief DC MOTOR 14 Click example
*
* # Description
* This example demonstrates the use of DC Motor 14 click board.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and makes an initial log.
*
* ## Application Task
* Drives the motor in the forward direction for 5 seconds, then pulls brake for 2 seconds,
* and after that drives it in the reverse direction for 5 seconds, and finally,
* disconnects the motor for 2 seconds. Each step will be logged on the USB UART where
* you can track the program flow.
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "dcmotor14.h"
// ------------------------------------------------------------------ VARIABLES
static dcmotor14_t dcmotor14;
static log_t logger;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
dcmotor14_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 ----");
// Click initialization.
dcmotor14_cfg_setup( &cfg );
DCMOTOR14_MAP_MIKROBUS( cfg, MIKROBUS_1 );
dcmotor14_init( &dcmotor14, &cfg );
}
void application_task ( void )
{
log_printf( &logger, "The motor turns forward! \r\n" );
dcmotor14_forward( &dcmotor14 );
Delay_ms( 5000 );
log_printf( &logger, "Pull brake! \r\n" );
dcmotor14_brake( &dcmotor14 );
Delay_ms( 2000 );
log_printf( &logger, "The motor turns in reverse! \r\n" );
dcmotor14_reverse( &dcmotor14 );
Delay_ms( 5000 );
log_printf( &logger, "The motor is disconnected (High-Z)! \r\n" );
dcmotor14_stop( &dcmotor14 );
Delay_ms( 2000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END