TOP Contributors

  1. MIKROE (2654 codes)
  2. Alcides Ramos (352 codes)
  3. Shawon Shahryiar (307 codes)
  4. jm_palomino (112 codes)
  5. Chisanga Mumba (90 codes)
  6. S P (73 codes)
  7. dany (71 codes)
  8. MikroBUS.NET Team (35 codes)
  9. NART SCHINACKOW (34 codes)
  10. Armstrong Subero (27 codes)

Most Downloaded

  1. Timer Calculator (136748 times)
  2. FAT32 Library (69954 times)
  3. Network Ethernet Library (55942 times)
  4. USB Device Library (46267 times)
  5. Network WiFi Library (41887 times)
  6. FT800 Library (41175 times)
  7. GSM click (28986 times)
  8. PID Library (26414 times)
  9. mikroSDK (26363 times)
  10. microSD click (25377 times)
Libstock prefers package manager

Package Manager

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]

< Back
mikroSDK Library

FLAME click

Rating:

0

Author: MIKROE

Last Updated: 2024-04-03

Package Version: 2.1.0.15

mikroSDK Library: 2.0.0.0

Category: Optical

Downloaded: 114 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.

No Abuse Reported

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".

  • mikroSDK Library 1.0.0.0
  • Comments (0)

mikroSDK Library Blog

FLAME click

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.

flame_click.png

click Product page


Click library

  • Author : MikroE Team
  • Date : dec 2019.
  • Type : GPIO type

Software Support

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.

Library Description

This library contains API for Flame Click driver.

Standard key functions :

  • 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 );

Example key functions :

  • Check the flame status function.

    uint8_t flame_check_status ( flame_t *ctx );

  • Get interrupt status.

    uint8_t flame_get_interrupt ( flame_t *ctx );

Examples Description

This application detects fire.

The demo application is composed of two sections :

Application Init

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 );
}

Application Task

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:

  • MikroSDK.Board
  • MikroSDK.Log
  • Click.Flame

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.


ALSO FROM THIS AUTHOR

ADC 17 click

0

ADC 17 Click is a compact add-on board that contains a high-performance data converter. This board features the MAX11645, a low-power two-channel 12-bit analog-to-digital converter from Analog Devices. The MAX11645 measures two single-ended or one differential input. The fully differential analog inputs are software configurable (I2C interface) for unipolar or bipolar, and single-ended or differential operation. The 2.048V internal reference determines its full-scale analog input range. This Click board™ offers complete, high accuracy solutions for the most demanding applications from energy-harvesting sensors to portable consumer electronics, point-of-load monitoring (voltage, current, and temperature), and more.

[Learn More]

I2C MUX 4 click

5

I2C MUX 4 Click is a compact add-on board that contains a dual bidirectional translating switch dedicated for applications with I2C slave address conflicts. This board features the TCA9543APWR, a low voltage 2-channel I2C bus switch with interrupt logic from Texas Instruments.

[Learn More]

Step Down 9 click

0

Step Down 9 Click is a compact add-on board that converts higher voltages into a lower voltage level. This board features the MAX20406, an automotive fully integrated synchronous silent switcher buck converter from Analog Devices.

[Learn More]