Harness the full potential of your DC motors with TB67H450AFNG and TM4C129ENCPDT
Elevate your motor's efficiency
Published May 31, 2023
Click board™
DC Motor 6 Click
Dev. board
Fusion for Tiva v8
Compiler
NECTO Studio
MCU
TM4C129ENCPDT
Upgrade your engineering solution and stay ahead of the curve. Operate your DC motor with up to 44V!
A
A
Hardware Overview
How does it work?
DC MOTOR 6 Click is based on the TB67H451AFNG, 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 MOSFETs' very low ON resistance, the TB67H451AFNG can deliver up to 3A 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 TB67H451AFNG, 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 shut down because the TB67H451AFNG
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. This IC controls a motor operation by PWM constant current control. The peak current value (setting current value) can be determined by the settings of the current-sensing resistor (R2) and the reference voltage (Vref).
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. The TB67H451AFNG not only can be controlled by constant current PWM but also by direct PWM; with IN control signals. When the supply voltage to the VM pin is 3.8V or less, the internal circuit is triggered; the internal reset circuit then turns off the output transistors. Once the UVLO is triggered, it can be cleared by reasserting the VM supply voltage to 4.0V or more. This Click board™ can only be operated with a 5V logic voltage level. The board must perform appropriate logic voltage level conversion before using MCUs with different logic levels. However, the Click board™ comes equipped with a library containing functions and an example code that can be used as a reference for further development.
Features overview
Development board
Fusion for TIVA v8 is a development board specially designed for the needs of rapid development of embedded applications. It supports a wide range of microcontrollers, such as different 32-bit ARM® Cortex®-M based MCUs from Texas Instruments, regardless of their number of pins, and a broad set of unique functions, such as the first-ever embedded debugger/programmer over a WiFi network. 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, Fusion for TIVA v8 provides a fluid and immersive working experience, allowing access
anywhere and under any circumstances at any time. Each part of the Fusion for TIVA v8 development board contains the components necessary for the most efficient operation of the same board. An advanced integrated CODEGRIP programmer/debugger module offers many valuable programming/debugging options, including support for JTAG, SWD, and SWO Trace (Single Wire Output)), and seamless integration with the Mikroe software environment. Besides, it 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 HOST/DEVICE, CAN (on the MCU card, if supported), and Ethernet is also included. In addition, it also has the well-established mikroBUS™ standard, a standardized socket for the MCU card (SiBRAIN standard), and two display options for the TFT board line of products and character-based LCD. Fusion for TIVA 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
Type
8th Generation
Architecture
ARM Cortex-M4
MCU Memory (KB)
1024
Silicon Vendor
Texas Instruments
Pin count
128
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 Fusion for Tiva v8 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 DC Motor 6 Click driver.
Key functions:
void dcmotor6_set_direction( uint8_t dir )- Set motor Direction
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 DC Motor 6 Click example
*
* # Description
* This example demonstrates the use of DC Motor 6 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 "dcmotor6.h"
// ------------------------------------------------------------------ VARIABLES
static dcmotor6_t dcmotor6;
static log_t logger;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
dcmotor6_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.
dcmotor6_cfg_setup( &cfg );
DCMOTOR6_MAP_MIKROBUS( cfg, MIKROBUS_1 );
dcmotor6_init( &dcmotor6, &cfg );
}
void application_task ( void )
{
log_printf( &logger, "The motor turns forward! \r\n" );
dcmotor6_set_direction( &dcmotor6, DCMOTOR6_MOTOR_FORWARD );
Delay_ms( 5000 );
log_printf( &logger, "Pull brake! \r\n" );
dcmotor6_set_direction( &dcmotor6, DCMOTOR6_MOTOR_BRAKE );
Delay_ms( 2000 );
log_printf( &logger, "The motor turns in reverse! \r\n" );
dcmotor6_set_direction( &dcmotor6, DCMOTOR6_MOTOR_REVERSE );
Delay_ms( 5000 );
log_printf( &logger, "The motor is disconnected (High-Z)! \r\n" );
dcmotor6_set_direction( &dcmotor6, DCMOTOR6_MOTOR_STOP );
Delay_ms( 2000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
