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: 224 times
Not followed.
License: MIT license
MCP1664 Click contains 4 high-power white LEDs. It carries the MCP1664, a high-voltage step-up LED driver from Microchip.
Do you want to subscribe in order to receive notifications regarding "MCP1664 Click" changes.
Do you want to unsubscribe in order to stop receiving notifications regarding "MCP1664 Click" changes.
Do you want to report abuse regarding "MCP1664 Click".
DOWNLOAD LINK | RELATED COMPILER | CONTAINS |
---|---|---|
3609_mcp1664_click.zip [540.30KB] | 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 |
|
MCP1664 Click contains 4 high-power white LEDs. It carries the MCP1664, a high-voltage step-up LED driver from Microchip.
We provide a library for the Mcp1664 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 Mcp1664 Click driver.
Config Object Initialization function.
void mcp1664_cfg_setup ( mcp1664_cfg_t *cfg );
Initialization function.
MCP1664_RETVAL mcp1664_init ( mcp1664_t ctx, mcp1664_cfg_t cfg );
Start PWM module.
void mcp1664_pwm_start ( mcp1664_t *ctx );
Stop PWM module.
void mcp1664_pwm_stop ( mcp1664_t *ctx );
This application turn on and turn off white LEDs.
The demo application is composed of two sections :
Enables GPIO and PWM, sets the frequency and duty cycle and enables PWM.
void application_init ( void )
{
log_cfg_t log_cfg;
mcp1664_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.
mcp1664_cfg_setup( &cfg );
MCP1664_MAP_MIKROBUS( cfg, MIKROBUS_1 );
mcp1664_init( &mcp1664, &cfg );
mcp1664_set_duty_cycle( &mcp1664, duty_cycle );
mcp1664_pwm_start( &mcp1664 );
Delay_ms ( 1000 );
log_printf( &logger, "------------------ \r\n" );
log_printf( &logger, " MCP1664 Click \r\n" );
log_printf( &logger, "------------------ \r\n" );
Delay_ms ( 100 );
}
This is a example which demonstrates the use of MCP1664 Click board. It shows how to enable the device and gradualy increase the duty cycle.
void application_task ( void )
{
// Task implementation.
if ( duty_cycle > mcp1664.pwm_period )
{
duty_cycle = 5000;
}
mcp1664_set_duty_cycle ( &mcp1664, duty_cycle );
duty_cycle += 50;
Delay_100ms();
log_printf( &logger, " Duty cycle is : %d \r\n", duty_cycle );
}
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.