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: Relay
Downloaded: 369 times
Not followed.
License: MIT license
FLICKER Click is the perfect, simple solution if you need to turn a device on and off at specific time intervals, like blinking LED commercials, alarm system lights, or any other signalling lights.
Do you want to subscribe in order to receive notifications regarding "Flicker Click" changes.
Do you want to unsubscribe in order to stop receiving notifications regarding "Flicker Click" changes.
Do you want to report abuse regarding "Flicker Click".
| DOWNLOAD LINK | RELATED COMPILER | CONTAINS |
|---|---|---|
| 3520_flicker_click.zip [530.61KB] | 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 |
|
FLICKER Click is the perfect, simple solution if you need to turn a device on and off at specific time intervals, like blinking LED commercials,alarm system lights, or any other signalling lights.
We provide a library for the Flicker 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 Flicker Click driver.
Config Object Initialization function.
void flicker_cfg_setup ( flicker_cfg_t *cfg );
Initialization function.
FLICKER_RETVAL flicker_init ( flicker_t ctx, flicker_cfg_t cfg );
Click Default Configuration function.
void flicker_default_cfg ( flicker_t *ctx );
void flicker_engage ( flicker_t *ctx );
This application simple solution if you need to turn a device on and off at specific time intervals.
The demo application is composed of two sections :
Initialization driver enables GPIO and also starts write log.
void application_init ( void )
{
log_cfg_t log_cfg;
flicker_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.
flicker_cfg_setup( &cfg );
FLICKER_MAP_MIKROBUS( cfg, MIKROBUS_1 );
flicker_init( &flicker, &cfg );
}
This example demonstrates capabilities of Flicker Click board.
void application_task ( void )
{
log_printf( &logger, " *Flicker on!* r/n/" );
flicker_engage( &flicker );
}
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.
