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 (141952 times)
  2. FAT32 Library (75140 times)
  3. Network Ethernet Library (59420 times)
  4. USB Device Library (49408 times)
  5. Network WiFi Library (45227 times)
  6. FT800 Library (44808 times)
  7. GSM click (31355 times)
  8. mikroSDK (30364 times)
  9. microSD click (27741 times)
  10. PID Library (27595 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

Ozone 2 Click

Rating:

0

Author: MIKROE

Last Updated: 2024-10-31

Package Version: 2.1.0.21

mikroSDK Library: 2.0.0.0

Category: Gas

Downloaded: 507 times

Not followed.

License: MIT license  

Ozone 2 Click is an Ozone detection (O3) sensor, based on the MQ131 gas sensor. This gas sensor has a sensitive layer made of SnO2, which changes its resistance when exposed to ozone.

No Abuse Reported

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

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

Do you want to report abuse regarding "Ozone 2 Click".

  • mikroSDK Library 1.0.0.0
  • Comments (0)

mikroSDK Library Blog


Ozone 2 Click

Ozone 2 Click is an Ozone detection (O3) sensor, based on the MQ131 gas sensor. This gas sensor has a sensitive layer made of SnO2, which changes its resistance when exposed to ozone.

ozone2_click.png

Click Product page


Click library

  • Author : MikroE Team
  • Date : Dec 2019.
  • Type : SPI type

Software Support

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

Standard key functions :

  • Config Object Initialization function.

    void ozone2_cfg_setup ( ozone2_cfg_t *cfg );

  • Initialization function.

    OZONE2_RETVAL ozone2_init ( ozone2_t ctx, ozone2_cfg_t cfg );

  • Click Default Configuration function.

    void ozone2_default_cfg ( ozone2_t *ctx );

Example key functions :

  • Function reads from MCP 3351 ADC and returns 32 bit read value.

    uint32_t ozone2_read ( ozone2_t *ctx );

Examples Description

This example reads data from the MCP 3351 sensor.

The demo application is composed of two sections :

Application Init

Driver initialization.


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

    ozone2_cfg_setup( &cfg );
    OZONE2_MAP_MIKROBUS( cfg, MIKROBUS_1 );
    ozone2_init( &ozone2, &cfg );
}

Application Task

Reading ADC value and displaying it via UART.


void application_task ( void )
{
    read_value = ozone2_read( &ozone2 );
    log_printf( &logger, "Read Value: %u\r\n", read_value);

    Delay_ms ( 1000 );
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );
}

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

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

8x8 Y Click

0

8x8 Y Click is a 64 LED matrix display Click board™, composed of SMD LEDs organized in 8 rows by 8 columns. It has a digital brightness control in 16 steps, it can control every LED in the display matrix independently, it blanks the display on power up to eliminate glitches and it requires a single resistor to control the current through all the LEDs at once, which simplifies the design. 8x8 Click uses a fast SPI communication protocol, allowing fast display response and no lag.

[Learn More]

ADC 11 Click

0

ADC 11 Click is a compact add-on board that contains a high-performance data converter. This board features the LTC1864, a 16-bit 250ksps analog-to-digital converter from Analog Devices. With a typical supply current of only 850µA at the maximum sampling frequency, the LTC1864 is among the lowest power consumption ADCs available. After conversion, the LTC1864 goes into a low-power Sleep mode, further reducing the supply current. That’s why it can run at proper micro-power levels in applications that do not require the maximum sampling rate of the LTC1864. This Click board™ is suitable for high-speed data acquisition, low power battery-operated instrumentation, isolated and remote data acquisition, and many other applications.

[Learn More]

GPS 3 click

5

Simple example which demonstrates usage of the GPS3 Click board with QUECTEL L80 GPS module. It displays a map of the world on the GLCD and shows the location of the GPS module on it.

[Learn More]