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.16
mikroSDK Library: 2.0.0.0
Category: LED Drivers
Downloaded: 141 times
Not followed.
License: MIT license
LED driver 2 Click carries the MCP1643 - LED constant current regulator, made by Microchip. It is a compact, high-efficiency, fixed frequency, synchronous step-up converter, optimized to drive one LED with the constant current.
Do you want to subscribe in order to receive notifications regarding "LED Driver 2 Click" changes.
Do you want to unsubscribe in order to stop receiving notifications regarding "LED Driver 2 Click" changes.
Do you want to report abuse regarding "LED Driver 2 Click".
DOWNLOAD LINK | RELATED COMPILER | CONTAINS |
---|---|---|
4225_led_driver_2_cli.zip [584.91KB] | 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 2 Click carries the MCP1643 - LED constant current regulator, made by Microchip. It is a compact, high-efficiency, fixed frequency, synchronous step-up converter, optimized to drive one LED with the constant current.
We provide a library for the LedDriver2 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 LedDriver2 Click driver.
Config Object Initialization function.
void leddriver2_cfg_setup ( leddriver2_cfg_t *cfg );
Initialization function.
LEDDRIVER2_RETVAL leddriver2_init ( leddriver2_t ctx, leddriver2_cfg_t cfg );
This function sets the PWM duty cycle
void leddriver2_set_duty_cycle ( leddriver2_t *ctx, pwm_data_t duty_cycle );
This function stops PWM module.
void leddriver2_pwm_stop ( leddriver2_t *ctx );
This function starts PWM module.
void leddriver2_pwm_start ( leddriver2_t *ctx );
This app enables usage of compact, high-efficiency, fixed frequency, synchronous step-up converter, optimized to drive one LED with the constant current.
The demo application is composed of two sections :
Initialization driver enables - GPIO, PWM initialization set PWM duty cycle and start PWM.
void application_init ( void )
{
log_cfg_t log_cfg;
leddriver2_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.
leddriver2_cfg_setup( &cfg );
LEDDRIVER2_MAP_MIKROBUS( cfg, MIKROBUS_1 );
leddriver2_init( &leddriver2, &cfg );
leddriver2_pwm_start( &leddriver2 );
}
This is an example that demonstrates the use of the LED Driver 2 Click board. 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;
leddriver2_set_duty_cycle ( &leddriver2, 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.