We strongly encourage users to use Package manager for sharing their code on Libstock website, because it boosts your efficiency and leaves the end user with no room for error. [more info]
Rating:
Author: MIKROE
Last Updated: 2024-10-31
Package Version: 2.1.0.14
mikroSDK Library: 2.0.0.0
Category: Brushed
Downloaded: 176 times
Not followed.
License: MIT license
This IC includes one channel of motor output block, using a wide range of supply voltages, while delivering reasonably high current to the connected DC motors.
Do you want to subscribe in order to receive notifications regarding "DC Motor 14 Click" changes.
Do you want to unsubscribe in order to stop receiving notifications regarding "DC Motor 14 Click" changes.
Do you want to report abuse regarding "DC Motor 14 Click".
DOWNLOAD LINK | RELATED COMPILER | CONTAINS |
---|---|---|
4358_dc_motor_14_clic.zip [459.19KB] | mikroC AI for ARM GCC for ARM Clang for ARM mikroC AI for PIC mikroC AI for PIC32 XC32 GCC for RISC-V Clang for RISC-V mikroC AI for AVR mikroC AI for dsPIC XC16 |
|
DC MOTOR 14 Click is a PWM chopper type brushed DC motor driver, labeled as TB67H450FNG.
We provide a library for the Dcmotor14 Click as well as a demo application (example), developed using MikroElektronika compilers. The demo can run on all the main MikroElektronika development boards.
Package can be downloaded/installed directly form compilers IDE(recommended way), or downloaded from our LibStock, or found on mikroE github account.
This library contains API for Dcmotor14 Click driver.
Config Object Initialization function.
void dcmotor14_cfg_setup ( dcmotor14_cfg_t *cfg );
Initialization function.
DCMOTOR14_RETVAL dcmotor14_init ( dcmotor14_t ctx, dcmotor14_cfg_t cfg );
This functio is used to drive the motor forward.
void dcmotor14_forward ( dcmotor14_t *ctx );
This functio is used to drive the motor in reverse.
dcmotor14_reverse ( dcmotor14_t *ctx );
This functio is used to brake the motor.
dcmotor14_brake ( dcmotor14_t *ctx );
This example demonstrates the use of DC Motor 14 Click board.
The demo application is composed of two sections :
Initializes the driver and makes an initial log.
void application_init ( void )
{
log_cfg_t log_cfg;
dcmotor14_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.
dcmotor14_cfg_setup( &cfg );
DCMOTOR14_MAP_MIKROBUS( cfg, MIKROBUS_1 );
dcmotor14_init( &dcmotor14, &cfg );
}
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.
void application_task ( void )
{
log_printf( &logger, "The motor turns forward! \r\n" );
dcmotor14_forward( &dcmotor14 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
log_printf( &logger, "Pull brake! \r\n" );
dcmotor14_brake( &dcmotor14 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
log_printf( &logger, "The motor turns in reverse! \r\n" );
dcmotor14_reverse( &dcmotor14 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
log_printf( &logger, "The motor is disconnected (High-Z)! \r\n" );
dcmotor14_stop( &dcmotor14 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
}
The full application code, and ready to use projects can be installed directly form compilers IDE(recommneded) or found on LibStock page or mikroE GitHub accaunt.
Other mikroE Libraries used in the example:
Additional notes and informations
Depending on the development board you are using, you may need USB UART Click, USB UART 2 Click or RS232 Click to connect to your PC, for development systems with no UART to USB interface available on the board. The terminal available in all Mikroelektronika compilers, or any other terminal application of your choice, can be used to read the message.