Our absolute pressure sensor is not just resistant; it thrives in chlorine-rich environments, offering a solution that endures, measures, and repeats with unwavering precision in the face of challenging conditions.
A
A
Hardware Overview
How does it work?
Pressure 23 Click is based on the MS5849-30BA, an ultra-compact chlorine-resistant absolute pressure sensor from TE Connectivity. It provides precise digital 24-bit pressure and temperature values and different operation modes, allowing users to optimize conversion speed and current consumption. The sensor features built-in automatic conversion, signaling state by interrupt, a programmable filter, and more. The sensor delivers a decent pressure sensing accuracy, which depends on the pressure measuring range. On lower pressures, it is as low as ±50mbar. In addition to pressure, this sensor can measure the temperature, which is needed for temperature compensation in a range of -20 up to 85°C with a temperature sensing accuracy of ±2°C. The MS5849-30BA includes a high linearity pressure sensor and an ultra-low power delta-sigma ADC
with internal factory-calibrated coefficients. The sensor consists of a piezo-resistive sensor and a sensor interface integrated circuit. It converts the sensor's uncompensated analog output value voltage to a 24-bit digital value. The sensor is individually factory calibrated, where, as a result, ten coefficients necessary to compensate for process variations and temperature variations are calculated and stored in the 256-bit NVRAM of the sensor. The sensor and the sealing gel on it shouldn't be touched or damaged in any way. In applications such as outdoor watches, the electronics must be protected against direct water or humidity. For such applications, the MS5849-30BA provides the possibility to seal with an O-ring. Pressure 23 Click can communicate with the host MCU using the 4-Wire SPI serial and I2C interfaces. The SPI interface supports clock
frequencies up to 20MHz, while the I2C clock supports up to 3.4MHz. The desired communication interface can be chosen over the 5 COMM SEL jumpers, where the SPI is set by default. If your goal is the I2C, you can choose the I2C address over the ADDR SEL jumper (0 set by default). The interrupt on the INT pin will be raised for different conditions, such as pressure and temperature thresholds, finished ADC conversion, and more. This Click board™ can be operated only with a 3.3V 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 STM32F091RC 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)
256
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
32768
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
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 23 Click - 30BA driver.
Key functions:
pressure2330ba_get_measurement_data
- Pressure 23 gets the measurement data function.pressure2330ba_get_calibration_data
- Pressure 23 gets the calibration data function.pressure2330ba_read_adc
- Pressure 23 ADC data reading 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 23 Click example
*
* # Description
* This example demonstrates the use of Pressure 23 Click board™ by reading and displaying
* the pressure and temperature measurements.
*
* The demo application is composed of two sections :
*
* ## Application Init
* The initialization of I2C or SPI module and log UART.
* After driver initialization, the app sets the default configuration.
*
* ## Application Task
* The demo application reads and displays the Pressure [mBar]
* and Temperature [degree Celsius] data.
* Results are being sent to the UART Terminal, where you can track their changes.
*
* @author Nenad Filipovic
*
*/
#include "board.h"
#include "log.h"
#include "pressure23.h"
static pressure23_t pressure23;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
pressure23_cfg_t pressure23_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.
pressure23_cfg_setup( &pressure23_cfg );
PRESSURE23_MAP_MIKROBUS( pressure23_cfg, MIKROBUS_1 );
err_t init_flag = pressure23_init( &pressure23, &pressure23_cfg );
if ( ( I2C_MASTER_ERROR == init_flag ) || ( SPI_MASTER_ERROR == init_flag ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
if ( PRESSURE23_ERROR == pressure23_default_cfg ( &pressure23 ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
log_printf( &logger, " _______________________ \r\n" );
Delay_ms( 100 );
}
void application_task ( void )
{
static float temperature, pressure;
if ( PRESSURE23_OK == pressure23_get_measurement_data( &pressure23, &pressure, &temperature ) )
{
log_printf( &logger, " Pressure : %.2f mBar \r\n", pressure );
log_printf( &logger, " Temperature : %.2f degC \r\n", temperature );
log_printf( &logger, " _______________________ \r\n" );
Delay_ms( 1000 );
}
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END