Pwm Driver Click demo application is developed using the NECTO Studio, ensuring compatibility with mikroSDK's open-source libraries and tools. Designed for plug-and-play implementation and testing, the demo is fully compatible with all development, starter, and mikromedia boards featuring a mikroBUS™ socket.
- Author : Nikola Peric
- Date : Feb 2022.
- Type : PWM type
This application is controls the speed DC motors.
- MikroSDK.Board
- MikroSDK.Log
- Click.PwmDriver
pwmdriver_cfg_setupConfig Object Initialization function.
void pwmdriver_cfg_setup ( pwmdriver_cfg_t *cfg );pwmdriver_initInitialization function.
err_t pwmdriver_init ( pwmdriver_t *ctx, pwmdriver_cfg_t *cfg );pwmdriver_default_cfgClick Default Configuration function.
void pwmdriver_default_cfg ( pwmdriver_t *ctx );pwmdriver_set_duty_cycleGeneric sets PWM duty cycle.
void pwmdriver_set_duty_cycle ( pwmdriver_t *ctx, pwm_data_t duty_cycle );pwmdriver_pwm_stopStop PWM module.
void pwmdriver_pwm_stop ( pwmdriver_t *ctx );pwmdriver_pwm_startStart PWM module.
void pwmdriver_pwm_start ( pwmdriver_t *ctx );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;
}
This Click board can be interfaced and monitored in two ways:
- Application Output - Use the "Application Output" window in Debug mode for real-time data monitoring. Set it up properly by following this tutorial.
- UART Terminal - Monitor data via the UART Terminal using a USB to UART converter. For detailed instructions, check out this tutorial.
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.