TOP Contributors

  1. MIKROE (2784 codes)
  2. Alcides Ramos (405 codes)
  3. Shawon Shahryiar (307 codes)
  4. jm_palomino (133 codes)
  5. Bugz Bensce (97 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 (141793 times)
  2. FAT32 Library (74938 times)
  3. Network Ethernet Library (59299 times)
  4. USB Device Library (49297 times)
  5. Network WiFi Library (45093 times)
  6. FT800 Library (44653 times)
  7. GSM click (31274 times)
  8. mikroSDK (30204 times)
  9. microSD click (27654 times)
  10. PID Library (27559 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

Smoke Click

Rating:

0

Author: MIKROE

Last Updated: 2024-10-31

Package Version: 2.1.0.17

mikroSDK Library: 2.0.0.0

Category: Optical

Downloaded: 477 times

Not followed.

License: MIT license  

Smoke Click carries the MAX30105 high-sensitivity optical sensor for smoke detection. The Click is designed to run on either 3.3V or 5V power supply. It communicates with the target MCU over I2C interface with additional functionality provided by the INT pin on the mikroBUS™ line.

No Abuse Reported

Do you want to subscribe in order to receive notifications regarding "Smoke Click" changes.

Do you want to unsubscribe in order to stop receiving notifications regarding "Smoke Click" changes.

Do you want to report abuse regarding "Smoke Click".

  • mikroSDK Library 1.0.0.0
  • Comments (0)

mikroSDK Library Blog


Smoke Click

Smoke Click carries the MAX30105 high-sensitivity optical sensor for smoke detection. The Click is designed to run on either 3.3V or 5V power supply. It communicates with the target MCU over I2C interface with additional functionality provided by the INT pin on the mikroBUS™ line.

smoke_click.png

Click Product page


Click library

  • Author : MikroE Team
  • Date : Feb 2020.
  • Type : I2C type

Software Support

We provide a library for the Smoke 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 Smoke Click driver.

Standard key functions :

  • Config Object Initialization function.

    void smoke_cfg_setup ( smoke_cfg_t *cfg );

  • Initialization function.

    SMOKE_RETVAL smoke_init ( smoke_t ctx, smoke_cfg_t cfg );

  • Click Default Configuration function.

    void smoke_default_cfg ( smoke_t *ctx );

Example key functions :

  • Set registers values function.

    uint8_t smoke_set_registers ( smoke_t ctx, smoke_set_registers_t registers );

  • Enable or disable interrupt function.

    uint8_t smoke_enable_disable_interrupts ( smoke_t *ctx, uint8_t interrupt_flag, uint8_t enable_flag );

  • Function for reading enabled led values.

    uint8_t smoke_read_leds ( smoke_t *ctx );

Examples Description

This Click includes internal LEDs, photodetectors, optical elements, and low-noise electronics with ambient light rejection. The sensor can detect a wide variety of smoke particle sizes. It also has an on-chip temperature sensor for calibrating the temperature dependence of the particle sensing subsystem. The temperature sensor has an inherent resolution 0.0625°C.

The demo application is composed of two sections :

Application Init

Initalizes I2C driver, and sets default configuration of device.


void application_init ( void )
{
    log_cfg_t log_cfg;
    smoke_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.

    smoke_cfg_setup( &cfg );
    SMOKE_MAP_MIKROBUS( cfg, MIKROBUS_1 );
    smoke_init( &smoke, &cfg );

    smoke_reset( &smoke );
    smoke_default_cfg ( &smoke );

    log_info( &logger, "---- Application Task ----" );
    Delay_ms ( 100 );
    if ( smoke_read_leds( &smoke ) != SMOKE_OK )
    {
        log_info( &logger, "---- Init Error ----" );
        for( ; ; );
    }
}

Application Task

This example demonstrates the use of Smoke Click board. It reads reflected red, ir, green and temperature values from an internal sensor and displays and logs it.


void application_task ( void )
{
    smoke_read_leds( &smoke );

    log_printf( &logger, "Red : %llu\r\n", smoke.red_value );
    log_printf( &logger, "IR : %llu\r\n", smoke.ir_value );
    log_printf( &logger, "Green : %llu\r\n", smoke.green_value );
    log_printf( &logger, "------------------------------\r\n" );

    temperature = smoke_read_temp( &smoke );

    log_printf( &logger, "Read Temperature[ degC ]: %.2f\r\n",  temperature );
    log_printf( &logger, "------------------------------\r\n" );

    Delay_ms ( 500 );
}

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

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

Haptic 4 Click

0

Haptic 4 Click is a compact add-on board that enables precise haptic feedback in various electronic projects. This board features the DA7280, a haptic driver designed to drive linear resonant actuator (LRA) and eccentric rotating mass (ERM) actuators from Renesas. The DA7280 boasts a differential output drive and continuous motion sensing for calibration-free operation, coupled with wide-band support to leverage the capabilities of modern LRAs. It supports six independent haptic sequences activated directly via mikroBUS™ pins or externally through I2C or PWM signals, offering extensive flexibility for haptic configuration. Ideal for enhancing user experience in wearables, electronic peripherals, automotive interfaces, industrial controls, and AR/VR controllers, this Click board™ opens new possibilities for interactive and tactile-responsive technology.

[Learn More]

nRF S click - Example

6

This is a sample program which demonstrates the use of nRF S click. Programmer uses RF module for communication between two development systems. Each module can be used as transmitter and receiver.

[Learn More]

GSM/GNSS Click

0

GSM/GNSS Click combines GPS/GLONASS location tracking with GSM module capability for mobile communication. The Click features Quectel’s MC60 quad-band module.

[Learn More]