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.18
mikroSDK Library: 2.0.0.0
Category: Brushed
Downloaded: 263 times
Not followed.
License: MIT license
This application is controls the speed DC motors.
Do you want to subscribe in order to receive notifications regarding "Pwm Driver Click" changes.
Do you want to unsubscribe in order to stop receiving notifications regarding "Pwm Driver Click" changes.
Do you want to report abuse regarding "Pwm Driver Click".
DOWNLOAD LINK | RELATED COMPILER | CONTAINS |
---|---|---|
3655_pwm_driver_click.zip [445.28KB] | 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 |
|
If you need to control DC motors with loads up to 10A, PWM driver Click is the perfect solution, thanks to the Silicon Lab Si8711CC one-channel isolator.
We provide a library for the PwmDriver 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 PwmDriver Click driver.
Config Object Initialization function.
void pwmdriver_cfg_setup ( pwmdriver_cfg_t *cfg );
Initialization function.
PWMDRIVER_RETVAL pwmdriver_init ( pwmdriver_t ctx, pwmdriver_cfg_t cfg );
Click Default Configuration function.
void pwmdriver_default_cfg ( pwmdriver_t *ctx );
Generic sets PWM duty cycle
void pwmdriver_set_duty_cycle ( pwmdriver_t *ctx, pwm_data_t duty_cycle );
Stop PWM module.
void pwmdriver_pwm_stop ( pwmdriver_t *ctx );
Start PWM module
void pwmdriver_pwm_start ( pwmdriver_t *ctx );
This application is controls the speed DC motors.
The demo application is composed of two sections :
Initialization driver enables - GPIO, PWM initialization set PWM duty cycle and PWM frequency, start PWM, enable the engine, and start to write log.
void application_init ( void )
{
log_cfg_t log_cfg;
pwmdriver_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.
pwmdriver_cfg_setup( &cfg );
PWMDRIVER_MAP_MIKROBUS( cfg, MIKROBUS_1 );
pwmdriver_init( &pwmdriver, &cfg );
Delay_ms ( 100 );
log_printf( &logger, " Initialization PWM \r\n " );
pwmdriver_set_duty_cycle( &pwmdriver, 0.0 );
pwmdriver_pwm_start( &pwmdriver );
Delay_ms ( 1000 );
log_info( &logger, "---- Application Task ----" );
}
This is an example that demonstrates the use of the PWM driver Click board. This example shows the automatic control of PWM, the first increases duty cycle and then the duty cycle is falling. Results are being sent to the Usart Terminal where you can track their changes.
void application_task ( void )
{
static int8_t duty_cnt = 1;
static int8_t duty_inc = 1;
float duty = duty_cnt / 10.0;
pwmdriver_set_duty_cycle ( &pwmdriver, duty );
log_printf( &logger, "Duty: %d%%\r\n", ( uint16_t )( duty_cnt * 10 ) );
Delay_ms ( 500 );
if ( 10 == duty_cnt )
{
duty_inc = -1;
}
else if ( 0 == duty_cnt )
{
duty_inc = 1;
}
duty_cnt += duty_inc;
}
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.