Create whisper-quiet operation of your DC motor with TB9051FTG and PIC32MZ2048EFH100
Powerful portable motor control
Published Jul 23, 2023
Click board™
DC Motor 18 Click
Dev. board
Flip&Click PIC32MZ
Compiler
NECTO Studio
MCU
PIC32MZ2048EFH100
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
Flip&Click PIC32MZ 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 comes with an onboard 32-bit PIC32MZ microcontroller, the PIC32MZ2048EFH100 from Microchip, four mikroBUS™ sockets for Click board™ connectivity, two USB connectors, LED indicators, buttons, debugger/programmer connectors, and two headers compatible with Arduino-UNO pinout. Thanks to innovative manufacturing technology,
it allows you to build gadgets with unique functionalities and features quickly. Each part of the Flip&Click PIC32MZ development kit contains the components necessary for the most efficient operation of the same board. In addition, there is the possibility of choosing the Flip&Click PIC32MZ programming method, using the chipKIT bootloader (Arduino-style development environment) or our USB HID bootloader using mikroC, mikroBasic, and mikroPascal for PIC32. This kit includes a clean and regulated power supply block through the USB Type-C (USB-C) connector. All communication
methods that mikroBUS™ itself supports are on this board, including the well-established mikroBUS™ socket, user-configurable buttons, and LED indicators. Flip&Click PIC32MZ development kit allows 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
Architecture
PIC32
MCU Memory (KB)
2048
Silicon Vendor
Microchip
Pin count
100
RAM (Bytes)
524288
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 Flip&Click PIC32MZ 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 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
