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: Optical
Downloaded: 457 times
Not followed.
License: MIT license
Flame Click is a fire detection solution. It carries a PT334-6B silicon phototransistor that’s covered in black epoxy and therefore sensitive only to infrared light.
Do you want to subscribe in order to receive notifications regarding "FLAME Click" changes.
Do you want to unsubscribe in order to stop receiving notifications regarding "FLAME Click" changes.
Do you want to report abuse regarding "FLAME Click".
| DOWNLOAD LINK | RELATED COMPILER | CONTAINS |
|---|---|---|
| 3516_flame_click.zip [430.99KB] | 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 |
|
Flame Click is a fire detection solution. It carries a PT334-6B silicon phototransistor that’s covered in black epoxy and therefore sensitive only to infrared light.
We provide a library for the Flame 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 Flame Click driver.
Config Object Initialization function.
void flame_cfg_setup ( flame_cfg_t *cfg );
Initialization function.
FLAME_RETVAL flame_init ( flame_t ctx, flame_cfg_t cfg );
Check the flame status function.
uint8_t flame_check_status ( flame_t *ctx );
Get interrupt status.
uint8_t flame_get_interrupt ( flame_t *ctx );
This application detects fire.
The demo application is composed of two sections :
Initialization driver enable's - GPIO and start write log.
void application_init ( void )
{
log_cfg_t log_cfg;
flame_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.
flame_cfg_setup( &cfg );
FLAME_MAP_MIKROBUS( cfg, MIKROBUS_1 );
flame_init( &flame, &cfg );
}
This is a example which demonstrates the use of Flame Click board.
void application_task ( void )
{
// Task implementation.
flame_state = flame_check_status ( &flame );
if ( ( flame_state == 1 ) && ( flame_state_old == 0) )
{
log_printf( &logger, " ~ FLAME ~ \r\n " );
flame_state_old = 1;
}
if ( ( flame_state == 0 ) && ( flame_state_old == 1 ) )
{
log_printf( &logger, " NO FLAME \r\n " );
flame_state_old = 0;
}
}
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.
