Upgrade your pressure monitoring game with 2513130810401 and STM32F446RE
Beyond filters, beyond gas: Our sensors excel in every application!
Published Oct 08, 2024
Click board™
Diff Press 3 Click
Dev. board
Nucleo 64 with STM32F446RE MCU
Compiler
NECTO Studio
MCU
STM32F446RE
In the world of fluid dynamics, our sensors emerge as the silent heroes, transforming pressure differentials into actionable data with unmatched precision
A
A
Hardware Overview
How does it work?
Diff Press 3 Click is based on the WSEN-PDUS ( 2513130810401 ), a differential pressure sensor from Würth Elektronik. The sensor has high accuracy, can measure different transfer pressure ranges from -100kPa up to 1000kPa, and has a response time of 2.2ms. Two pots accept ∅2.2 hoses, where one of them is a high-pressure side, and the other is designated as the vacuum side. The hoses are not included with the Diff Press 3 Click. As for temperature, this sensor can measure temperatures in a range of 0 up to 70°C and in ADC resolution of 15 bits. Diff Press 3 Click can use
a standard 2-Wire I2C interface to communicate with the host MCU, where you can read both the pressure and the temperature measurements. In addition to the I2C interface, the pressure output of the sensor can be read over the analog AN pin of the mikroBUS™ socket, where you can read only pressure measurements. As the 2513130810401 WSEN-PDUS sensor works on 5V, this Click board™ comes equipped with the PCA9306, a dual bidirectional I2C bus and SMBus voltage-level translator from Texas Instruments, which allows the use of this Click board™
with systems with 3.3V logic level. AN SEL jumper allows you to use a 5V or 2.5V logic level over a voltage divider, where 2.5V is set by default. 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 STM32F446RE 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-M4
MCU Memory (KB)
512
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
131072
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 STM32F446RE 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 Diff Press 3 Click driver.
Key functions:
diffpress3_get_pressure- Diff Press 3 get pressure function.diffpress3_get_temperature- Diff Press 3 get temperature function.diffpress3_read_raw_adc- Diff Press 3 read raw ADC value 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 Diff Press 3 Click Example.
*
* # Description
* This library contains API for the Diff Press 3 Click driver.
* This demo application shows an example of
* differential pressure and temperature measurement.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initialization of I2C and ADC module and log UART.
*
* ## Application Task
* This example demonstrates the use of the Diff Press 3 Click board™.
* The demo application measures and display the Differential Pressure [kPa]
* 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 "diffpress3.h"
static diffpress3_t diffpress3; /**< Diff Press 3 Click driver object. */
static log_t logger; /**< Logger object. */
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
diffpress3_cfg_t diffpress3_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.
diffpress3_cfg_setup( &diffpress3_cfg );
DIFFPRESS3_MAP_MIKROBUS( diffpress3_cfg, MIKROBUS_1 );
err_t init_flag = diffpress3_init( &diffpress3, &diffpress3_cfg );
if ( ( ADC_ERROR == init_flag ) || ( I2C_MASTER_ERROR == init_flag ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
log_printf( &logger, "---------------------\r\n" );
Delay_ms( 100 );
}
void application_task ( void )
{
float pressure, temperature;
if ( DIFFPRESS3_OK == diffpress3_get_pressure( &diffpress3, &pressure ) )
{
log_printf( &logger, " Diff Pressure: %.3f [kPa]\r\n", pressure );
Delay_ms( 100 );
}
if ( DIFFPRESS3_OK == diffpress3_get_temperature( &diffpress3, &temperature ) )
{
log_printf( &logger, " Temperature: %.2f [C]\r\n", temperature );
Delay_ms( 100 );
}
log_printf( &logger, "---------------------\r\n" );
Delay_ms( 1000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
