Control the speed and direction of the brushed DC motors with DRV8833 and PIC24EP512GU810
Switch the motor ON or OFF and manage its direction using simple digital signals
Published Jun 02, 2023
Click board™
DC MOTOR Click
Dev. board
EasyPIC Fusion v7
Compiler
NECTO Studio
MCU
PIC24EP512GU810
Compact, user-friendly solution for controlling brushed DC motors with minimal fuss and maximum reliability
A
A
Hardware Overview
How does it work?
DC MOTOR Click is based on the DRV8833, an H-bridge motor driver with current-control PWM circuitry from Texas Instruments. The DRV8833 has two integrated H-bridges connected in parallel for double the current of a single H-bridge rated for an operating voltage range from 3V to 10V. The output driver block of the DRV8833 consists of N-channel power MOSFETs configured as an H-bridge to drive the motor windings, where each H-bridge includes circuitry to regulate or limit the winding current. Thanks to the current sense resistors R2 and R5 of 220mΩ, the driving current is limited to 0.9A. In addition, the 74HC4053 is also incorporated into the design to run the motor with only one PWM line from the mikroBUS™ socket. Thanks to this multiplexer, in combination with the selection pins
SL1 and SL2, routed to the RST and CS pins of the mikroBUS™ socket, control of the DRV8833 driver as well as management of its operating modes (Coast/Fast Decay, Reverse, Forward, Brake/Slow Decay) is enabled. This mux can also be used for PWM control of the motor speed. The DRV8833 also has a complete set of diagnostic and protection capabilities that support robust and reliable operation, like over-current protection, short circuit protection, undervoltage lockout, and overtemperature. In any case, the user can also visually detect them, in addition to the FLT pin, through the red LED marked with FAULT. It is also possible to set the driver in low-power Sleep mode via the SLP pin routed to the AN pin of the mikroBUS™ socket. In this state, the H-bridges are
disabled, the gate drive charge pump is stopped, all internal logic is reset, and all internal clocks are stopped. This Click board™ can operate with both 3.3V and 5V logic voltage levels selected via the PWR SEL jumper. It allows both 3.3V and 5V capable MCUs to use the communication lines properly. Additionally, there is a possibility for the DRV8833 power supply selection via jumper labeled as MOTOR PWR to supply the DRV8833 from an external power supply terminal from 3V to 10V or from mikroBUS™ power rails. However, 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
EasyPIC Fusion v7 is the seventh generation of PIC development boards specially designed to develop embedded applications rapidly. It supports a wide range of 16/32-bit PIC microcontrollers from Microchip and a broad set of unique functions, such as a powerful onboard mikroProg programmer and In-Circuit debugger over USB-B. 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. With two different connectors for each port, EasyPIC Fusion v7 allows you to connect accessory boards, sensors, and custom electronics more efficiently than ever. Each part of
the EasyPIC Fusion 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, USB-HOST, CAN, and Ethernet are also included, including the well-established mikroBUS™ standard, one display option for the TFT board line of products, and a standard TQFP socket for the seventh-generation MCU cards. This socket covers a wide range of 16-bit dsPIC/PIC24 and 32-bit PIC32 MCUs. EasyPIC Fusion 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
Type
7th Generation
Architecture
dsPIC
MCU Memory (KB)
512
Silicon Vendor
Microchip
Pin count
100
RAM (Bytes)
53248
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 EasyPIC Fusion 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 Click driver.
Key functions:
dcmotor_pwm_start- Start PWM module.dcmotor_enable- Enable the motor function.dcmotor_sleep_mode- Set sleep mode function.
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 DcMotor Click example
*
* # Description
* This application change the speed and direction of DC Motor.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initialization driver enable's - GPIO,
* PWM initialization, set PWM duty cycle and PWM frequency, enable the motor, start PWM and start write log.
*
* ## Application Task
* This is a example which demonstrates the use of DC Motor Click board.
* DC Motor Click communicates with register via PWM interface.
* It shows moving in the left direction from slow to fast speed
* and from fast to slow speed.
* Results are being sent to the Usart Terminal where you can track their changes.
*
* \author Nikola Peric
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "dcmotor.h"
// ------------------------------------------------------------------ VARIABLES
static dcmotor_t dcmotor;
static log_t logger;
uint8_t dcmotor_direction = 1;
void application_init ( void )
{
log_cfg_t log_cfg;
dcmotor_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.
dcmotor_cfg_setup( &cfg );
DCMOTOR_MAP_MIKROBUS( cfg, MIKROBUS_1 );
dcmotor_init( &dcmotor, &cfg );
log_printf( &logger, " Initialization PWM \r\n" );
dcmotor_set_duty_cycle ( &dcmotor, 0.0 );
dcmotor_pwm_start( &dcmotor );
log_printf( &logger, "---------------------\r\n" );
}
void application_task ( )
{
static int8_t duty_cnt = 1;
static int8_t duty_inc = 1;
float duty = duty_cnt / 10.0;
if ( dcmotor_direction == 1 )
{
dcmotor_sleep_mode ( &dcmotor );
dcmotor_right_direction_slow ( &dcmotor );
log_printf( &logger, "> CLOCKWISE <\r\n" );
dcmotor_enable ( &dcmotor );
}
else
{
dcmotor_sleep_mode ( &dcmotor );
dcmotor_left_direction_slow ( &dcmotor );
log_printf( &logger, "> COUNTER CLOCKWISE <\r\n" );
dcmotor_enable ( &dcmotor );
}
dcmotor_set_duty_cycle ( &dcmotor, duty );
Delay_ms ( 500 );
if ( 10 == duty_cnt )
{
duty_inc = -1;
if ( dcmotor_direction == 1 )
{
dcmotor_direction = 0;
}
else if ( dcmotor_direction == 0 )
{
dcmotor_direction = 1;
}
}
else if ( 0 == duty_cnt )
{
duty_inc = 1;
}
duty_cnt += duty_inc;
}
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
