Accurate alcohol detection based on the MiCS-5524 and STM32L073RZ
Alcohol awareness simplified: Our detection, your safe passage
Published Feb 26, 2024
Click board™
Alcohol 3 Click
Dev Board
Nucleo-64 with STM32L073RZ MCU
Compiler
NECTO Studio
MCU
STM32L073RZ
Develop top-of-the-line alcohol breath tester and early fire and gas leakage detection applications easily
A
A
Hardware Overview
How does it work?
Alcohol 3 Click is based on the MiCS-5524 sensor, a compact MOS sensor from SGX Sensortech. This sensor comprises a micromachined metal oxide semiconductor diaphragm with an integrated heating resistor. The resistor produces heat, which catalyzes the reaction, affecting the electrical resistance of the oxide layer itself. The temperature of the heater is quite high: it ranges from 350 °C to 550 °C. After the initial preheating period, the sensor can detect gas changes in intervals below two seconds. The resistance of the MiCS-5524 sensor does not change linearly with the gas concentration, so a proper calibration must be performed before using it for absolute gas concentration measurement applications. The impedance changes the most when used with low gas concentrations. As the atmosphere gets saturated with gas, the impedance changes slowly. This should be considered, especially when
developing applications for estimating blood alcohol content (BAC) from a breath sample (also known as a breathalyzer). The MiCS-5524 sensor is a simple device: it has only four connections. Two pins are the connections of the internal heating element, while the other two are the MOS sensor connections. The application is reduced to calculating a proper resistor for the voltage divider. The datasheet of the MiCS-5524 sensor offers typical values for its resistance when used in clean air (artificial conditions). The sensitivity is then expressed as the ratio between the sensor's resistance in clean air and resistance at a concentration of 60 ppm CO. The middle tap between the sensor (as a resistor) and the fixed resistance provides an output voltage. It depends on the sensor's resistance, allowing it to be used as the input into the MCP3221, a low-power 12-bit A/D converter with an I2C interface, from Microchip.
This ADC allows the output voltage to be translated into digital information, accessed over the I2C pins on the mikroBUS™ socket. By using the power supply voltage as the voltage reference for the conversion, this ADC further reduces the complexity of the design, still offering a good conversion quality, thanks to its low noise input. Due to the sensor's inert nature, this ADC is more than fast enough, although it can provide up to 22.3ksps when operated in the I2C Fast mode. This Click board™ can operate with either 3.3V or 5V logic voltage levels selected via the VCC SEL jumper. This way, both 3.3V and 5V capable MCUs can use the communication lines properly. Also, this Click board™ comes equipped with a library containing easy-to-use functions and an example code that can be used as a reference for further development.
Features overview
Development board
Nucleo-64 with STM32L073RZ MCU offers a cost-effective and adaptable platform for developers to explore new ideas and prototype their designs. This board harnesses the versatility of the STM32 microcontroller, enabling users to select the optimal balance of performance and power consumption for their projects. It accommodates the STM32 microcontroller in the LQFP64 package and includes essential components such as a user LED, which doubles as an ARDUINO® signal, alongside user and reset push-buttons, and a 32.768kHz crystal oscillator for precise timing operations. Designed with expansion and flexibility in mind, the Nucleo-64 board features an ARDUINO® Uno V3 expansion connector and ST morpho extension pin
headers, granting complete access to the STM32's I/Os for comprehensive project integration. Power supply options are adaptable, supporting ST-LINK USB VBUS or external power sources, ensuring adaptability in various development environments. The board also has an on-board ST-LINK debugger/programmer with USB re-enumeration capability, simplifying the programming and debugging process. Moreover, the board is designed to simplify advanced development with its external SMPS for efficient Vcore logic supply, support for USB Device full speed or USB SNK/UFP full speed, and built-in cryptographic features, enhancing both the power efficiency and security of projects. Additional connectivity is
provided through dedicated connectors for external SMPS experimentation, a USB connector for the ST-LINK, and a MIPI® debug connector, expanding the possibilities for hardware interfacing and experimentation. Developers will find extensive support through comprehensive free software libraries and examples, courtesy of the STM32Cube MCU Package. This, combined with compatibility with a wide array of Integrated Development Environments (IDEs), including IAR Embedded Workbench®, MDK-ARM, and STM32CubeIDE, ensures a smooth and efficient development experience, allowing users to fully leverage the capabilities of the Nucleo-64 board in their projects.
Microcontroller Overview
MCU Card / MCU
Architecture
ARM Cortex-M0
MCU Memory (KB)
192
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
20480
You complete me!
Accessories
Click Shield for Nucleo-64 comes equipped with two proprietary mikroBUS™ sockets, allowing all the Click board™ devices to be interfaced with the STM32 Nucleo-64 board with no effort. This way, Mikroe allows its users to add any functionality from our ever-growing range of Click boards™, such as WiFi, GSM, GPS, Bluetooth, ZigBee, environmental sensors, LEDs, speech recognition, motor control, movement sensors, and many more. More than 1537 Click boards™, which can be stacked and integrated, are at your disposal. The STM32 Nucleo-64 boards are based on the microcontrollers in 64-pin packages, a 32-bit MCU with an ARM Cortex M4 processor operating at 84MHz, 512Kb Flash, and 96KB SRAM, divided into two regions where the top section represents the ST-Link/V2 debugger and programmer while the bottom section of the board is an actual development board. These boards are controlled and powered conveniently through a USB connection to program and efficiently debug the Nucleo-64 board out of the box, with an additional USB cable connected to the USB mini port on the board. Most of the STM32 microcontroller pins are brought to the IO pins on the left and right edge of the board, which are then connected to two existing mikroBUS™ sockets. This Click Shield also has several switches that perform functions such as selecting the logic levels of analog signals on mikroBUS™ sockets and selecting logic voltage levels of the mikroBUS™ sockets themselves. Besides, the user is offered the possibility of using any Click board™ with the help of existing bidirectional level-shifting voltage translators, regardless of whether the Click board™ operates at a 3.3V or 5V logic voltage level. Once you connect the STM32 Nucleo-64 board with our Click Shield for Nucleo-64, you can access hundreds of Click boards™, working with 3.3V or 5V logic voltage levels.
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Schematic
Step by step
Project assembly
Start by selecting your development board and Click board™. Begin with the Nucleo-64 with STM32L073RZ MCU as your development board.
Track your results in real time
Application Output
After loading the code example, pressing the "DEBUG" button builds and programs it on the selected setup.
After programming is completed, a header with buttons for various actions available in the IDE appears. By clicking the green "PLAY "button, we start reading the results achieved with Click board™.
Upon completion of programming, the Application Output tab is automatically opened, where the achieved result can be read. In case of an inability to perform the Debug function, check if a proper connection between the MCU used by the setup and the CODEGRIP programmer has been established. A detailed explanation of the CODEGRIP-board connection can be found in the CODEGRIP User Manual. Please find it in the RESOURCES section.
Software Support
Library Description
This library contains API for Alcohol 3 Click driver.
Key functions:
alcohol3_get_co_in_ppm- This function reads CO (Carbon monoxide) data in ppm (1 ppm - 1000 ppm)alcohol3_get_percentage_bac- This function reads percentage of alcohol in the blood (BAC)alcohol3_get_adc_data- This function reads 12bit ADC value.
Open Source
Code example
This example can be found in NECTO Studio. Feel free to download the code, or you can copy the code below.
/*!
* \file
* \brief Alcohol3 Click example
*
* # Description
* Code of this sensor reacts to the presence of deoxidizing and reducing gases,
* such as ethanol (also known as alcohol).
*
* The demo application is composed of two sections :
*
* ## Application Init
* Application Init performs Logger and Click initialization.
*
* ## Application Task
* Reads percentage of alcohol in the blood (BAC)
* and this data logs to USBUART every 1 sec.
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "alcohol3.h"
// ------------------------------------------------------------------ VARIABLES
static alcohol3_t alcohol3;
static log_t logger;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
alcohol3_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 ----" );
Delay_ms ( 100 );
// Click initialization.
alcohol3_cfg_setup( &cfg );
ALCOHOL3_MAP_MIKROBUS( cfg, MIKROBUS_1 );
alcohol3_init( &alcohol3, &cfg );
log_printf( &logger, "--------------------------\r\n\n" );
log_printf( &logger, " ---- Alcohol 3 Click ----\r\n" );
log_printf( &logger, "--------------------------\r\n\n" );
Delay_ms ( 1000 );
log_printf( &logger, " ---- Initialization ---\r\n" );
log_printf( &logger, "--------------------------\r\n\n" );
Delay_ms ( 1000 );
}
void application_task ( void )
{
uint16_t co_ppm;
uint16_t p_bac;
float temp_bac;
// Task implementation.
log_printf( &logger, " --- Alcohol diagnostics ---- \r\n" );
co_ppm = alcohol3_get_co_in_ppm ( &alcohol3 );
log_printf( &logger, " co in ppm %d | \r\n", co_ppm );
temp_bac = alcohol3_get_percentage_bac( &alcohol3 );
p_bac = ( uint16_t )( temp_bac * 1000 );
if ( 10 > p_bac && p_bac < 100 )
{
log_printf( &logger, " BAC | 0.00%d\r\n", p_bac );
}
else if ( 100 <= p_bac && 1000 > p_bac )
{
log_printf( &logger, " BAC | 0.0%d\r\n", p_bac );
}
else if ( p_bac >= 1000 )
{
log_printf( &logger, " BAC | 0.%d\r\n", p_bac );
}
else
{
log_printf( &logger, " BAC | 0.0000\r\n" );
}
log_printf( &logger, " ---------------------------- \r\n" );
Delay_ms( 1000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
