Discover the science of pressure like never before with HSCMAND060PA3A3 and PIC18LF26K40
Pressurize with confidence: The ultimate manometer solution!
Published Jan 23, 2024
Click board™
Manometer Click
Dev. board
Curiosity HPC
Compiler
NECTO Studio
MCU
PIC18LF26K40
Our state-of-the-art manometer solution is engineered to deliver unparalleled accuracy, ensuring your pressure measurements are always on point
A
A
Hardware Overview
How does it work?
Manometer Click is based on the HSCMAND060PA3A3, a piezoresistive silicon pressure sensor from Honeywell, an industry-leading module with an extremely high accuracy of ±0.25%FSS BFSL. The click is designed to run on a 3.3V power supply. It communicates with the target MCU over the I2C interface. The HSCMAND060PA3A3 has an industry-leading, extremely high accuracy of ±0.25%FSS BFSL. An absolute pressure range from 0 to 60 PSI makes it suitable for various applications. Beyond the
measurement range, the sensor has a high burst pressure threshold, increasing reliability. The sensor on the Manometer Click is a highly reliable and robust unit. It's also easy to use and implement. It requires no calibration and compensates for environmental conditions by relying on its internal temperature sensor. The HSC Series is calibrated over the temperature range of 0 °C to 50 °C (32 °F to 122 °F). The temperature sensor can also be accessed independently through the I2C interface. The
barbed port accepts 4.93 mm (0.19") tubing, which connects directly (no special extensions required). 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
Curiosity HPC, standing for Curiosity High Pin Count (HPC) development board, supports 28- and 40-pin 8-bit PIC MCUs specially designed by Microchip for the needs of rapid development of embedded applications. This board has two unique PDIP sockets, surrounded by dual-row expansion headers, allowing connectivity to all pins on the populated PIC MCUs. It also contains a powerful onboard PICkit™ (PKOB), eliminating the need for an external programming/debugging tool, two mikroBUS™ sockets for Click board™ connectivity, a USB connector, a set of indicator LEDs, push button switches and a variable potentiometer. All
these features allow you to combine the strength of Microchip and Mikroe and create custom electronic solutions more efficiently than ever. Each part of the Curiosity HPC development board contains the components necessary for the most efficient operation of the same board. An integrated onboard PICkit™ (PKOB) allows low-voltage programming and in-circuit debugging for all supported devices. When used with the MPLAB® X Integrated Development Environment (IDE, version 3.0 or higher) or MPLAB® Xpress IDE, in-circuit debugging allows users to run, modify, and troubleshoot their custom software and hardware
quickly without the need for additional debugging tools. Besides, it includes a clean and regulated power supply block for the development board via the USB Micro-B connector, alongside all communication methods that mikroBUS™ itself supports. Curiosity HPC development board allows you to create a new application in just a few steps. Natively supported by Microchip software tools, it covers many aspects of prototyping thanks to many number of different Click boards™ (over a thousand boards), the number of which is growing daily.
Microcontroller Overview
MCU Card / MCU
Architecture
PIC
MCU Memory (KB)
64
Silicon Vendor
Microchip
Pin count
28
RAM (Bytes)
3728
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 Curiosity HPC 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 Manometer Click driver.
Key functions:
manometer_generic_write- Generic write functionmanometer_generic_read- Generic read functionmanometer_get_pressure- Function read 16-bit data and convert to pressure in mbar
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
* \brief Manometer Click example
*
* # Description
* This application carries a piezoresistive silicon pressure sensor.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initialization driver enable's - I2C and start write log to Usart Terminal.
*
* ## Application Task
* This is a example which demonstrates the use of Manometer Click board.
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "manometer.h"
// ------------------------------------------------------------------ VARIABLES
static manometer_t manometer;
static log_t logger;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
manometer_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.
manometer_cfg_setup( &cfg );
MANOMETER_MAP_MIKROBUS( cfg, MIKROBUS_1 );
manometer_init( &manometer, &cfg );
}
void application_task ( void )
{
// Task implementation.
float read_data;
read_data = manometer_get_pressure( &manometer );
Delay_10ms( );
log_printf( &logger, " Pressure: %.2f mbar\r\n", read_data );
read_data = manometer_get_temperature( &manometer );
Delay_10ms( );
log_printf( &logger, " Temperature: %.2f C\r\n", read_data );
log_printf( &logger, "--------------------------\r\n" );
Delay_1sec( );
Delay_1sec( );
}
int main ( void )
{
/* Do not remove this line or clock might not be set correctly. */
#ifdef PREINIT_SUPPORTED
preinit();
#endif
application_init( );
for ( ; ; )
{
application_task( );
}
return 0;
}
// ------------------------------------------------------------------------ END
