The next-gen DC brushed driver based on the TC78H651AFNG and ATmega1284
Elevate your automation
Published Jul 25, 2023
Click board™
DC Motor 20 Click
Dev. board
EasyAVR v7
Compiler
NECTO Studio
MCU
ATmega1284
Supercharge your motors, enhance performance, and engineer with precision. Add brushed motor control to your projects now!
A
A
Hardware Overview
How does it work?
DC Motor 20 Click is based on the TC78H651AFNG, a dual H-bridge driver for one or two DC brushed motors from Toshiba Semiconductor. The integrated MOSFETs, configured with an H-Bridge circuit inside the TC78H651AFNG, use DMOS elements with low-on resistance (0.22Ω typical with a 5V power supply). It has a wide operating voltage range with an output current capacity of 2A maximum and control functions, including motor-related functions and built-in detection circuits for overcurrent, overheat, and low/high voltage. As mentioned in the product description, DC Motor 20 Click communicates with MCU using
several GPIO pins. Also, this Click board™ has a Standby function that switches to Standby mode by setting all motor control pins to a low logic state. When the Standby mode is active, the TC78H651AFNG stops supplying the power to the logic circuit. The Standby current is significantly reduced because all circuits in the IC are configured with CMOS/DMOS elements, and the current consumption in this mode is 0μA typical. To turn ON the internal MOSFETs of the TC78H651AFNG, they need to be switched by the logic level, which is input to the control input pins: IN1, IN2, IN3, and IN4 pins routed to the RST, AN,
PWM, and INT pins of the mikroBUS™ socket. The Forward/Reverse/Stop rotation direction mode can be selected according to the state of its input control signals. More information on the Motor Rotation Mode Selection can be found in the attached datasheet. 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
EasyAVR v7 is the seventh generation of AVR development boards specially designed for the needs of rapid development of embedded applications. It supports a wide range of 16-bit AVR microcontrollers from Microchip and has a broad set of unique functions, such as a powerful onboard mikroProg programmer and In-Circuit debugger over USB. The development board is well organized and designed so that the end-user has all the necessary elements in one place, such as switches, buttons, indicators, connectors, and others. With four different connectors for each port, EasyAVR v7 allows you to connect accessory boards, sensors, and custom electronics more
efficiently than ever. Each part of the EasyAVR v7 development board contains the components necessary for the most efficient operation of the same board. An integrated mikroProg, a fast USB 2.0 programmer with mikroICD hardware In-Circuit Debugger, offers many valuable programming/debugging options and seamless integration with the Mikroe software environment. Besides it also includes a clean and regulated power supply block for the development board. It can use a wide range of external power sources, including an external 12V power supply, 7-12V AC or 9-15V DC via DC connector/screw terminals, and a power source via the USB Type-B (USB-B)
connector. Communication options such as USB-UART and RS-232 are also included, alongside the well-established mikroBUS™ standard, three display options (7-segment, graphical, and character-based LCD), and several different DIP sockets which cover a wide range of 16-bit AVR MCUs. EasyAVR v7 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
Architecture
AVR
MCU Memory (KB)
128
Silicon Vendor
Microchip
Pin count
40
RAM (Bytes)
16384
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 EasyAVR v7 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 20 Click driver.
Key functions:
dcmotor20_drive_motor- This function drives the motor for a certian time specified by time_ms at the desired speeddcmotor20_set_channel_mode- This function sets the active channel and mode which will be used by the dcmotor20_drive_motor functiondcmotor20_set_standby_mode- This function sets the chip to the standby mode which affects both channels
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 DC Motor 20 Click Example.
*
* # Description
* This example demonstrates the use of DC Motor 20 click board by driving the motors
* in both direction in the span of 14 seconds.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and sets the click board to standby mode.
*
* ## Application Task
* Drives the motors in the forward direction for 5 seconds, and then switches the direction,
* with a brake time of 2 seconds between switching the direction.
* 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 "dcmotor20.h"
static dcmotor20_t dcmotor20; /**< DC Motor 20 Click driver object. */
static log_t logger; /**< Logger object. */
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
dcmotor20_cfg_t dcmotor20_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.
dcmotor20_cfg_setup( &dcmotor20_cfg );
DCMOTOR20_MAP_MIKROBUS( dcmotor20_cfg, MIKROBUS_1 );
if ( DIGITAL_OUT_UNSUPPORTED_PIN == dcmotor20_init( &dcmotor20, &dcmotor20_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
dcmotor20_set_standby_mode ( &dcmotor20 );
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
log_printf ( &logger, " Driving motors forward...\r\n" );
dcmotor20_set_channel_mode ( &dcmotor20, DCMOTOR20_CHANNEL_1 | DCMOTOR20_CHANNEL_2, DCMOTOR20_MODE_FORWARD );
dcmotor20_drive_motor ( &dcmotor20, DCMOTOR20_SPEED_DEFAULT, 5000 );
log_printf ( &logger, " Pull brake!\r\n" );
dcmotor20_set_standby_mode ( &dcmotor20 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
log_printf ( &logger, " Driving motors in reverse...\r\n" );
dcmotor20_set_channel_mode ( &dcmotor20, DCMOTOR20_CHANNEL_1 | DCMOTOR20_CHANNEL_2, DCMOTOR20_MODE_REVERSE );
dcmotor20_drive_motor ( &dcmotor20, DCMOTOR20_SPEED_DEFAULT, 5000 );
log_printf ( &logger, " Pull brake!\r\n\n" );
dcmotor20_set_standby_mode ( &dcmotor20 );
Delay_ms ( 1000 );
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 DC Motor 20 Click Example.
*
* # Description
* This example demonstrates the use of DC Motor 20 click board by driving the motors
* in both direction in the span of 14 seconds.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and sets the click board to standby mode.
*
* ## Application Task
* Drives the motors in the forward direction for 5 seconds, and then switches the direction,
* with a brake time of 2 seconds between switching the direction.
* 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 "dcmotor20.h"
static dcmotor20_t dcmotor20; /**< DC Motor 20 Click driver object. */
static log_t logger; /**< Logger object. */
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
dcmotor20_cfg_t dcmotor20_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.
dcmotor20_cfg_setup( &dcmotor20_cfg );
DCMOTOR20_MAP_MIKROBUS( dcmotor20_cfg, MIKROBUS_1 );
if ( DIGITAL_OUT_UNSUPPORTED_PIN == dcmotor20_init( &dcmotor20, &dcmotor20_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
dcmotor20_set_standby_mode ( &dcmotor20 );
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
log_printf ( &logger, " Driving motors forward...\r\n" );
dcmotor20_set_channel_mode ( &dcmotor20, DCMOTOR20_CHANNEL_1 | DCMOTOR20_CHANNEL_2, DCMOTOR20_MODE_FORWARD );
dcmotor20_drive_motor ( &dcmotor20, DCMOTOR20_SPEED_DEFAULT, 5000 );
log_printf ( &logger, " Pull brake!\r\n" );
dcmotor20_set_standby_mode ( &dcmotor20 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
log_printf ( &logger, " Driving motors in reverse...\r\n" );
dcmotor20_set_channel_mode ( &dcmotor20, DCMOTOR20_CHANNEL_1 | DCMOTOR20_CHANNEL_2, DCMOTOR20_MODE_REVERSE );
dcmotor20_drive_motor ( &dcmotor20, DCMOTOR20_SPEED_DEFAULT, 5000 );
log_printf ( &logger, " Pull brake!\r\n\n" );
dcmotor20_set_standby_mode ( &dcmotor20 );
Delay_ms ( 1000 );
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 DC Motor 20 Click Example.
*
* # Description
* This example demonstrates the use of DC Motor 20 click board by driving the motors
* in both direction in the span of 14 seconds.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and sets the click board to standby mode.
*
* ## Application Task
* Drives the motors in the forward direction for 5 seconds, and then switches the direction,
* with a brake time of 2 seconds between switching the direction.
* 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 "dcmotor20.h"
static dcmotor20_t dcmotor20; /**< DC Motor 20 Click driver object. */
static log_t logger; /**< Logger object. */
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
dcmotor20_cfg_t dcmotor20_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.
dcmotor20_cfg_setup( &dcmotor20_cfg );
DCMOTOR20_MAP_MIKROBUS( dcmotor20_cfg, MIKROBUS_1 );
if ( DIGITAL_OUT_UNSUPPORTED_PIN == dcmotor20_init( &dcmotor20, &dcmotor20_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
dcmotor20_set_standby_mode ( &dcmotor20 );
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
log_printf ( &logger, " Driving motors forward...\r\n" );
dcmotor20_set_channel_mode ( &dcmotor20, DCMOTOR20_CHANNEL_1 | DCMOTOR20_CHANNEL_2, DCMOTOR20_MODE_FORWARD );
dcmotor20_drive_motor ( &dcmotor20, DCMOTOR20_SPEED_DEFAULT, 5000 );
log_printf ( &logger, " Pull brake!\r\n" );
dcmotor20_set_standby_mode ( &dcmotor20 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
log_printf ( &logger, " Driving motors in reverse...\r\n" );
dcmotor20_set_channel_mode ( &dcmotor20, DCMOTOR20_CHANNEL_1 | DCMOTOR20_CHANNEL_2, DCMOTOR20_MODE_REVERSE );
dcmotor20_drive_motor ( &dcmotor20, DCMOTOR20_SPEED_DEFAULT, 5000 );
log_printf ( &logger, " Pull brake!\r\n\n" );
dcmotor20_set_standby_mode ( &dcmotor20 );
Delay_ms ( 1000 );
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
