Streamline pressure measurement in various settings with KP229E2701 and STM32G071RB
Pressure's best friend: Your reliable wingman in the digital realm
Published Oct 08, 2024
Click board™
Pressure 13 Click
Dev. board
Nucleo 64 with STM32G071RB MCU
Compiler
NECTO Studio
MCU
STM32G071RB
Experience the future of pressure measurement with our digital sensor, which empowers you with real-time, high-precision data to streamline your operations and enhance decision-making
A
A
Hardware Overview
How does it work?
Pressure 13 Click is based on the KP229E2701, a miniaturized analog absolute pressure sensor based on a capacitive principle from Infineon. The pressure is detected by an array of capacitive surface micromachined sensor cells (a monolithic integrated signal conditioning circuit implemented in BiCMOS technology). The sensor cell output is amplified, temperature compensated, and linearized to obtain an output voltage proportional to the applied pressure. The manifold air pressure (MAP) is a principal parameter to compute the air-fuel ratio provided to the engine for lower emission due to better combustion and increased efficiency. For cost-sensitive engine systems, a MAP sensor shows the potential to complement or even substitute mass airflow (MAF) sensors. The accuracy of the KP229E2701 sensor is influenced by the supply
voltage (ratiometric error) and pressure, temperature, and aging effects. All parameters needed for the complete calibration algorithm - such as offset, gain, temperature coefficients of offset and gain, and linearization parameters - are determined after the assembly. These parameters are stored in an integrated E²PROM protected with forwarding error correction (a one-bit error is detected and corrected, more than one-bit errors are detected, and the output signal is switched to ground potential). In automotive applications where high production volumes are custom, there is substantial interest in precision, low-cost, and fully integrated sensors. That’s why the manifold pressure data can be used to compute diagnostics of leakages and malfunctions of the exhaust gas recirculation valve. Pressure 13 Click communicates with MCU using only one GPIO
pin routed on the AN pin of the mikroBUS™ socket. The KP229E2701 sensor possesses several digital pins used only during calibration and testing. That’s why it’s recommended and done to leave these pins floating. The output circuit acts as a low-pass decoupling filter between the sensor output and the A/D input of the MCU because it’s recommended to protect the pressure sensor against overload and electromagnetic interferences. This Click board™ can be operated only with a 5V logic voltage level. The board must perform appropriate logic voltage level conversion before using MCUs with different logic levels. Also, it comes equipped with a library containing functions and an example code that can be used as a reference for further development.
Features overview
Development board
Nucleo-64 with STM32G071RB 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)
128
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
36864
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
Click board™ Schematic
Step by step
Project assembly
Start by selecting your development board and Click board™. Begin with the Nucleo 64 with STM32G071RB MCU as your development board.
Track your results in real time
Application Output
1. Application Output - In Debug mode, the 'Application Output' window enables real-time data monitoring, offering direct insight into execution results. Ensure proper data display by configuring the environment correctly using the provided tutorial.
2. UART Terminal - Use the UART Terminal to monitor data transmission via a USB to UART converter, allowing direct communication between the Click board™ and your development system. Configure the baud rate and other serial settings according to your project's requirements to ensure proper functionality. For step-by-step setup instructions, refer to the provided tutorial.
3. Plot Output - The Plot feature offers a powerful way to visualize real-time sensor data, enabling trend analysis, debugging, and comparison of multiple data points. To set it up correctly, follow the provided tutorial, which includes a step-by-step example of using the Plot feature to display Click board™ readings. To use the Plot feature in your code, use the function: plot(*insert_graph_name*, variable_name);. This is a general format, and it is up to the user to replace 'insert_graph_name' with the actual graph name and 'variable_name' with the parameter to be displayed.
Software Support
Library Description
This library contains API for Pressure 13 Click driver.
Key functions:
pressure13_read_an_pin_value- Pressure 13 read AN pin value functionpressure13_read_an_pin_voltage- Pressure 13 read AN pin voltage level functionpressure13_get_pressure- Pressure 13 read AN pin voltage level function
Open Source
Code example
The complete application code and a ready-to-use project are available through the NECTO Studio Package Manager for direct installation in the NECTO Studio. The application code can also be found on the MIKROE GitHub account.
/*!
* @file main.c
* @brief Pressure 13 Click Example.
*
* # Description
* This is an example which demonstrates the use of Pressure 13 Click board.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initialization driver enables - GPIO, initializes ADC, also write log.
*
* ## Application Task
* Measure and display pressure ( mBar ). Results are being sent to the
* Usart Terminal where you can track their changes.
* All data logs on usb uart approximately every sec.
*
*
* @author Stefan Ilic
*
*/
#include "board.h"
#include "log.h"
#include "pressure13.h"
static pressure13_t pressure13; /**< Pressure 13 Click driver object. */
static log_t logger; /**< Logger object. */
static uint16_t adc_val;
static float pressure_val;
static float voltage_val;
void application_init ( void ) {
log_cfg_t log_cfg; /**< Logger config object. */
pressure13_cfg_t pressure13_cfg; /**< Click config object. */
/**
* 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.
pressure13_cfg_setup( &pressure13_cfg );
PRESSURE13_MAP_MIKROBUS( pressure13_cfg, MIKROBUS_1 );
if ( ADC_ERROR == pressure13_init( &pressure13, &pressure13_cfg ) )
{
log_error( &logger, " Application Init Error. " );
log_info( &logger, " Please, run program again... " );
for ( ; ; );
}
log_info( &logger, " Application Task " );
log_printf( &logger, "-------------------------\r\n", voltage_val );
}
void application_task ( void ) {
if ( pressure13_get_pressure( &pressure13, &pressure_val ) != ADC_ERROR ) {
log_printf( &logger, " Pressure: %.3f [mBar]\r\n", pressure_val );
}
log_printf( &logger, "-------------------------\r\n" );
Delay_ms( 1000 );
}
void main ( void ) {
application_init( );
for ( ; ; ) {
application_task( );
}
}
// ------------------------------------------------------------------------ END
