Trust in MS5525DSO and PIC18LF2458 combo to deliver the real-time pressure data you need
Manometer: Pressure's best friend
Published Nov 01, 2023
Click board™
Manometer 2 Click
Dev Board
EasyPIC v7
Compiler
NECTO Studio
MCU
PIC18LF2458
Step into the world of precise pressure measurement with our innovative manometer, engineered to enhance the quality and performance of your systems and processes.
A
A
Hardware Overview
How does it work?
Manometer 2 Click is based on the MS5525DSO, a digital pressure sensor based on leading MEMS technology from TE Connectivity. The click is designed to run on a 3.3V power supply. It communicates with the target microcontroller over an I2C or SPI interface. The MS5525DSO is a new Digital Small Outline pressure sensor generation with SPI and I2C bus interface designed for high-volume OEM users. The sensor module includes a pressure sensor and an ultra
low power 24-bit ∆Σ ADC with internal factory-calibrated coefficients. It provides a 24-bit digital pressure and temperature value and different operation modes that allow users to optimize conversion speed and current consumption. The MS5525DSO consists of a piezo-resistive sensor and a sensor interface IC. The main function of the MS5525DSO is to convert the uncompensated analog output voltage from the piezo-resistive pressure sensor to a 24-bit digital value and
provide a 24-bit digital value for the temperature of the sensor. Manometer 2 click measures the absolute pressure of 1PSI max through the barbed port. 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
EasyPIC v7 is the seventh generation of PIC development boards specially designed to develop embedded applications rapidly. It supports a wide range of 8-bit PIC microcontrollers from Microchip and has a broad set of unique functions, such as a powerful onboard mikroProg programmer and In-Circuit debugger over USB-B. The development board is well organized and designed so that the end-user has all the necessary elements in one place, such as switches, buttons, indicators, connectors, and others. With four different connectors for each port, EasyPIC v7 allows you to connect accessory boards, sensors, and custom electronics more efficiently than ever. Each part of
the EasyPIC v7 development board contains the components necessary for the most efficient operation of the same board. An integrated mikroProg, a fast USB 2.0 programmer with mikroICD hardware In-Circuit Debugger, offers many valuable programming/debugging options and seamless integration with the Mikroe software environment. Besides it also includes a clean and regulated power supply block for the development board. It can use various external power sources, including an external 12V power supply, 7-23V AC or 9-32V DC via DC connector/screw terminals, and a power source via the USB Type-B (USB-B) connector. Communication options such as
USB-UART and RS-232 are also included, alongside the well-established mikroBUS™ standard, three display options (7-segment, graphical, and character-based LCD), and several different DIP sockets. These sockets cover a wide range of 8-bit PIC MCUs, from PIC10F, PIC12F, PIC16F, PIC16Enh, PIC18F, PIC18FJ, and PIC18FK families. EasyPIC v7 is an integral part of the Mikroe ecosystem for rapid development. Natively supported by Mikroe software tools, it covers many aspects of prototyping and development thanks to a considerable number of different Click boards™ (over a thousand boards), the number of which is growing every day.
Microcontroller Overview
MCU Card / MCU
Architecture
PIC
MCU Memory (KB)
24
Silicon Vendor
Microchip
Pin count
28
RAM (Bytes)
2048
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 EasyPIC v7 as your development board.
Track your results in real time
Application Output
After pressing the "FLASH" button on the left-side panel, it is necessary to open the UART terminal to display the achieved results. By clicking on the Tools icon in the right-hand panel, multiple different functions are displayed, among which is the UART Terminal. Click on the offered "UART Terminal" icon.
Once the UART terminal is opened, the window takes on a new form. At the top of the tab are two buttons, one for adjusting the parameters of the UART terminal and the other for connecting the UART terminal. The tab's lower part is reserved for displaying the achieved results. Before connecting, the terminal has a Disconnected status, indicating that the terminal is not yet active. Before connecting, it is necessary to check the set parameters of the UART terminal. Click on the "OPTIONS" button.
In the newly opened UART Terminal Options field, we check if the terminal settings are correct, such as the set port and the Baud rate of UART communication. If the data is not displayed properly, it is possible that the Baud rate value is not set correctly and needs to be adjusted to 115200. If all the parameters are set correctly, click on "CONFIGURE".
The next step is to click on the "CONNECT" button, after which the terminal status changes from Disconnected to Connected in green, and the data is displayed in the Received data field.
Software Support
Library Description
This library contains API for Manometer 2 Click driver.
Key functions:
manometer2_read_coef- Generic read data function
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 Manometer2 Click example
*
* # Description
* This application is digital pressure sensor.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initialization driver enable's - I2C,
* initialization Manometer 2 sensor MS5525DSO-SB001GS by read coeffitient value
* and start write log.
*
* ## Application Task
* This is a example which demonstrates the use of Manometer 2 Click board.
* Measured pressure and temperature value from sensor, calculate pressure [ PSI ] and temperature [ �C ],
* results are being sent to the Usart Terminal where you can track their changes.
* All data logs on usb uart for aproximetly every 3 sec when the data value changes.
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "manometer2.h"
// ------------------------------------------------------------------ VARIABLES
static manometer2_t manometer2;
static log_t logger;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
manometer2_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.
manometer2_cfg_setup( &cfg );
MANOMETER2_MAP_MIKROBUS( cfg, MIKROBUS_1 );
manometer2_init( &manometer2, &cfg );
manometer2_read_coef( &manometer2 );
log_printf( &logger, " Initialization \r\n" );
log_printf( &logger, "----------------------------- \r\n" );
Delay_100ms( );
}
void application_task ( )
{
float temperature;
float pressure;
temperature = manometer2_get_temperature( &manometer2, MANOMETER2_CONVERT_4096 );
Delay_10ms( );
pressure = manometer2_get_pressure( &manometer2, MANOMETER2_CONVERT_4096 );
Delay_10ms( );
log_printf( &logger, " Pressure : %.2f PSI \r\n", pressure );
log_printf( &logger, " Temperature: %.2f C \r\n", temperature );
log_printf( &logger, "----------------------------- \r\n" );
Delay_1sec( );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
