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.17
mikroSDK Library: 2.0.0.0
Category: LED Drivers
Downloaded: 233 times
Not followed.
License: MIT license
This application controls the brightness.
Do you want to subscribe in order to receive notifications regarding "LED DRIVER Click" changes.
Do you want to unsubscribe in order to stop receiving notifications regarding "LED DRIVER Click" changes.
Do you want to report abuse regarding "LED DRIVER Click".
DOWNLOAD LINK | RELATED COMPILER | CONTAINS |
---|---|---|
3573_led_driver_click.zip [447.89KB] | 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 |
|
LED driver Click carries the MCP1662 high-voltage step-up voltage driver from Microchip. The Click is designed to run on either 3.3V or 5V power supply. It communicates with the target microcontroller over PWM pin on the mikroBUS™ line
We provide a library for the LedDriver 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 LedDriver Click driver.
Config Object Initialization function.
void leddriver_cfg_setup ( leddriver_cfg_t *cfg );
Initialization function.
LEDDRIVER_RETVAL leddriver_init ( leddriver_t ctx, leddriver_cfg_t cfg );
This library contains API for the LED Driver Click driver. This application controls the brightness.
The demo application is composed of two sections :
PWM initialization set PWM duty cycle and PWM frequency and start PWM.
void application_init ( void )
{
log_cfg_t log_cfg;
leddriver_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.
leddriver_cfg_setup( &cfg );
LEDDRIVER_MAP_MIKROBUS( cfg, MIKROBUS_1 );
if ( LEDDRIVER_OK != leddriver_init( &leddriver, &cfg ) )
{
log_info( &logger, "---- Init Error ----" );
log_info( &logger, "---- Run program again ----" );
for ( ; ; );
}
log_info( &logger, "---- Init Done ----\r\n" );
leddriver_set_duty_cycle ( &leddriver, 0.0 );
leddriver_pwm_start( &leddriver );
Delay_ms ( 100 );
log_info( &logger, "---- Application Task ----\r\n" );
}
This is an example that demonstrates the use of the LED Driver Click board. LED Driver Click communicates with register via PWM interface. This example shows the automatic control halogen bulb light intensity, the first intensity of light is rising and then the intensity of light 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;
leddriver_set_duty_cycle ( &leddriver, duty );
log_printf( &logger, "> Duty: %d%%\r\n", ( uint16_t )( duty_cnt * 10 ) );
Delay_ms ( 100 );
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.