Experience a seamless blend of power and elegance with TB67H481FNG and TM4C1294KCPDT
Powering tomorrow's movements
Published Nov 10, 2023
Click board™
DC Motor 13 Click
Dev Board
UNI Clicker
Compiler
NECTO Studio
MCU
TM4C1294KCPDT
Enhance your engineering endeavors with our DC motor driver, a solution meticulously crafted to bring efficiency, precision, and innovation to your projects.
A
A
Hardware Overview
How does it work?
DC Motor 13 Click is based on the TB67H481FNG, a dual-channel, H-bridge, brushed DC motor driver from Toshiba Semiconductor. The TB67H481FNG has a current limit function that monitors the current flowing in the motor and performs constant current PWM control. When the motor current reaches the set current value, determined using onboard VREF trimmers (VREFA and VREFB), the TB67H481FNG shifts to Decay mode and annotates the current. Various Decay mode functions are selectable by positioning the SMD jumper, labeled as DECAY, to an appropriate position marked as 0 and 1. Also, Mixed Decay Mode can be selected by removing the JP2 jumper for the board. The TB67H481FNG has a built-in regulator that allows the motor to be driven by a single power supply, provides a motor output voltage rating of around 40V, and has integrated protection mechanisms such as over-current, over-temperature, and under-voltage
lockout for error detection. The setting current value can be adjusted with the torque function (100%, 71%, 38%, or 0%), controlled through the PCA9538A port expander, which establishes communication with the MCU via the I2C serial interface. Lowering the torque setting can suppress the motor current when high torque is unnecessary. In addition to these torque setting pins, with the help of the expander, it is also possible to control some other signals, such as the control signals for selecting the operating mode of the motor driver. These pins, in combination with AI1 and BI1 pins, routed to default positions of CS and PWM pins of the mikroBUS™ socket, enable operational modes like CW, CCW, or short-brake. The PCA9538A also allows choosing the least significant bit (LSB) of its I2C slave address by positioning SMD jumpers labeled as ADDR SEL to an appropriate position marked as 0 and 1, alongside its interrupt feature routed to the INT
pin of the mikroBUS™ socket. Besides, all circuits can be stopped using the Sleep function, routed to default positions of the AN pin of the mikroBUS™ socket, and thus enable power saving mode, while the RST pin provides a general-purpose reset function. The DC Motor 13 Click supports an external power supply for the TB67H481FNG, which can be connected to the input terminal labeled as VM and should be within the range of 8.2V to 44V, while the two brushed or one stepping motor coils can be connected to the terminals labeled as B+, B-, A-, and A+. 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 as a reference for further development.
Features overview
Development board
UNI Clicker is a compact development board designed as a complete solution that brings the flexibility of add-on Click boards™ to your favorite microcontroller, making it a perfect starter kit for implementing your ideas. It supports a wide range of microcontrollers, such as different ARM, PIC32, dsPIC, PIC, and AVR from various vendors like Microchip, ST, NXP, and TI (regardless of their number of pins), four mikroBUS™ sockets for Click board™ connectivity, a USB connector, LED indicators, buttons, a debugger/programmer connector, and two 26-pin headers for interfacing with external electronics. Thanks to innovative manufacturing technology, it allows you to build
gadgets with unique functionalities and features quickly. Each part of the UNI Clicker development kit contains the components necessary for the most efficient operation of the same board. In addition to the possibility of choosing the UNI Clicker programming method, using a third-party programmer or CODEGRIP/mikroProg connected to onboard JTAG/SWD header, the UNI Clicker board also includes a clean and regulated power supply module for the development kit. It provides two ways of board-powering; through the USB Type-C (USB-C) connector, where onboard voltage regulators provide the appropriate voltage levels to each component on the board, or using a Li-Po/Li
Ion battery via an onboard battery connector. All communication methods that mikroBUS™ itself supports are on this board (plus USB HOST/DEVICE), including the well-established mikroBUS™ socket, a standardized socket for the MCU card (SiBRAIN standard), and several user-configurable buttons and LED indicators. UNI Clicker 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
Type
8th Generation
Architecture
ARM Cortex-M4
MCU Memory (KB)
512
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
Schematic
Step by step
Project assembly
Start by selecting your development board and Click board™. Begin with the UNI Clicker as your development board.
Track your results in real time
Application Output
After loading the code example, pressing the "DEBUG" button builds and programs it on the selected setup.
After programming is completed, a header with buttons for various actions available in the IDE appears. By clicking the green "PLAY "button, we start reading the results achieved with Click board™.
Upon completion of programming, the Application Output tab is automatically opened, where the achieved result can be read. In case of an inability to perform the Debug function, check if a proper connection between the MCU used by the setup and the CODEGRIP programmer has been established. A detailed explanation of the CODEGRIP-board connection can be found in the CODEGRIP User Manual. Please find it in the RESOURCES section.
Software Support
Library Description
This library contains API for DC Motor 13 Click driver.
Key functions:
dcmotor13_set_outa_mode- This function sets the OUTA mode.dcmotor13_set_outb_mode- This function sets the OUTB mode.dcmotor13_set_outa_torque- This function sets the OUTA torque.
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 main.c
* @brief DCMotor13 Click example
*
* # Description
* This example demonstrates the use of DC Motor 13 click board by driving the motors
* in both direction in the span of 9 seconds.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and performs the click default configuration which sets the output
* torque to 100%.
*
* ## Application Task
* Drives the motors in the clockwise direction, then switches to the counter-clockwise direction,
* and after that pulls the motors brake with a 3 seconds delay after each change.
* Each step will be logged on the USB UART where you can track the program flow.
*
* @author Stefan Filipovic
*
*/
#include "board.h"
#include "log.h"
#include "dcmotor13.h"
static dcmotor13_t dcmotor13;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
dcmotor13_cfg_t dcmotor13_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.
dcmotor13_cfg_setup( &dcmotor13_cfg );
DCMOTOR13_MAP_MIKROBUS( dcmotor13_cfg, MIKROBUS_1 );
if ( I2C_MASTER_ERROR == dcmotor13_init( &dcmotor13, &dcmotor13_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
if ( DCMOTOR13_ERROR == dcmotor13_default_cfg ( &dcmotor13 ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
if ( DCMOTOR13_OK == dcmotor13_set_outa_mode ( &dcmotor13, DCMOTOR13_MODE_CW ) )
{
log_printf ( &logger, " OUTA: Clockwise\r\n" );
}
if ( DCMOTOR13_OK == dcmotor13_set_outb_mode ( &dcmotor13, DCMOTOR13_MODE_CW ) )
{
log_printf ( &logger, " OUTB: Clockwise\r\n\n" );
}
Delay_ms ( 3000 );
if ( DCMOTOR13_OK == dcmotor13_set_outa_mode ( &dcmotor13, DCMOTOR13_MODE_CCW ) )
{
log_printf ( &logger, " OUTA: Counter-Clockwise\r\n" );
}
if ( DCMOTOR13_OK == dcmotor13_set_outb_mode ( &dcmotor13, DCMOTOR13_MODE_CCW ) )
{
log_printf ( &logger, " OUTB: Counter-Clockwise\r\n\n" );
}
Delay_ms ( 3000 );
if ( DCMOTOR13_OK == dcmotor13_set_outa_mode ( &dcmotor13, DCMOTOR13_MODE_SHORT_BRAKE ) )
{
log_printf ( &logger, " OUTA: Short brake\r\n" );
}
if ( DCMOTOR13_OK == dcmotor13_set_outb_mode ( &dcmotor13, DCMOTOR13_MODE_SHORT_BRAKE ) )
{
log_printf ( &logger, " OUTB: Short brake\r\n\n" );
}
Delay_ms ( 3000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
