Decode complex pressure data with ABP2LANT060PG2A3XX and ATmega1284

Crack the code of pressure

Published Jul 09, 2024

Click board™

Pressure 14 Click

Dev. board

EasyAVR v8

Compiler

NECTO Studio

MCU

ATmega1284

Delve into the expansive world of possibilities made accessible by digital pressure sensors

Hardware Overview

How does it work?

Pressure 14 Click is based on the ABP2LANT060PG2A3XX, a piezoresistive silicon pressure sensor from Honeywell offering a digital output for reading pressure over the specified full-scale pressure span. It is characterized by long-term stability and accuracy, ultra-low power consumption, a wide pressure range from 0 to 60 psi, and compatibility with plenty of liquid media. Also, it is a perfect choice for pressure measurements in automotive, industrial, and consumer applications. The ABP2LANT060PG2A3XX defines an I2C configurable ABP2 Series Amplified Basic pressure sensor calibrated and temperature compensated

for sensor offset, sensitivity, temperature effects, and accuracy errors. ABP2 series represents flexible and versatile sensors with calibrated output values for pressure and temperature updates at approximately 200 Hz. The liquid media option includes an additional silicone-based gel coating to protect the electronics under pressure port, enabling usage with non-corrosive liquids (e.g., water and saline) and in applications where condensation can occur. Pressure 14 Click communicates with MCU using the standard I2C 2-Wire interface and supports both Standard and Fast Mode with a transfer rate of 100 and 400kbit/s. Following the address and read bit from

the MCU, the ABP2 Series digital pressure sensors can output up to 7 bytes of data using a default I2C address of 40 (28h). Also, it uses an additional pin, the INT pin of the mikroBUS™ socket, as an ‘end-of-conversion’ indicator. This pin sets HIGH when measurement and calculation have been completed and the data is ready to be clocked out. 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

EasyAVR v8 is a development board designed to rapidly develop embedded applications based on 8-bit AVR microcontrollers (MCUs). Redesigned from the ground up, EasyAVR v8 offers a familiar set of standard features, as well as some new and unique features standard for the 8th generation of development boards: programming and debugging over the WiFi network, connectivity provided by USB-C connectors, support for a wide range of different MCUs, and more. The development board is designed so that the developer has everything that might be needed for the application development, following the Swiss Army knife concept: a highly advanced programmer/debugger module, a reliable power supply module, and a USB-UART connectivity option. EasyAVR v8 board offers several different DIP sockets, covering a wide range of 8-bit AVR MCUs, from the smallest

AVR MCU devices with only eight pins, all the way up to 40-pin "giants". The development board supports the well-established mikroBUS™ connectivity standard, offering five mikroBUS™ sockets, allowing access to a huge base of Click boards™. EasyAVR v8 offers two display options, allowing even the basic 8-bit AVR MCU devices to utilize them and display graphical or textual content. One of them is the 1x20 graphical display connector, compatible with the familiar Graphical Liquid Crystal Display (GLCD) based on the KS108 (or compatible) display driver, and EasyTFT board that contains TFT Color Display MI0283QT-9A, which is driven by ILI9341 display controller, capable of showing advanced graphical content. The other option is the 2x16 character LCD module, a four-bit display module with an embedded character-based display controller. It

requires minimal processing power from the host MCU for its operation. There is a wide range of useful interactive options at the disposal: high-quality buttons with selectable press levels, LEDs, pull-up/pulldown DIP switches, and more. All these features are packed on a single development board, which uses innovative manufacturing technologies, delivering a fluid and immersive working experience. The EasyAVR v8 development board is also integral to the MIKROE rapid development ecosystem. Natively supported by the MIKROE Software toolchain, backed up by hundreds of different Click board™ designs with their number growing daily, it covers many different prototyping and development aspects, thus saving precious development time.

Microcontroller Overview

MCU Card / MCU

Architecture

AVR

MCU Memory (KB)

128

Silicon Vendor

Microchip

Pin count

RAM (Bytes)

16384

Used MCU Pins

mikroBUS™ mapper

RST

SCK

MISO

MOSI

Power Supply

3.3V

Ground

GND

PWM

Interrupt

PD2

INT

I2C Clock

PC0

SCL

I2C Data

PC1

SDA

Ground

GND

Take a closer look

Click board™ Schematic

Step by step

Project assembly

EasyAVR v8 front image hardware assembly

Start by selecting your development board and Click board™. Begin with the EasyAVR v8 as your development board.

NECTO Output Selection Step Image hardware assembly

In the advanced settings, pay special attention to the Redirect standard output field. By default, it is set to Application output as the method of displaying final results. To show results via a UART terminal, select the “UART” option in that field and click the “SAVE” button. You will be returned to the Compiler field, and now you can move on to the next step by pressing the “NEXT” button.

Stepper 24 Click front image hardware assembly

Stepper 24 Click complete accessories setup image hardware assembly

EasyAVR v8 Access DIP MB 1 - upright/background hardware assembly

NECTO Compiler Selection Step Image hardware assembly

Necto DIP image step 7 hardware assembly

EasyPIC PRO v7a Display Selection Necto Step hardware 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 14 Click driver.

Key functions:

pressure14_measure_cmd - This function sends output measurement command that causes the ABP2 series pressure sensor to exit standby mode and enter operating mode
pressure14_check_busy_flag_int - This function returns the INT pin state which indicates the End-of-conversion for ABP2 series pressure sensor on Pressure 14 Click
pressure14_read_press_and_temp - This function reads 24-bit pressure, 24-bit temperature data and 8-bit status register from the ABP2 series pressure sensor on Pressure 14 Click

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 Pressure14 Click example
 *
 * # Description
 * This examples used ABP2 Series are piezoresistive silicon pressure sensors offering a digital output for reading pressure over the specified full scale pressure 
 * span and temperature range. They are calibrated and temperature compensated for sensor offset, sensitivity, temperature effects and accuracy errors (which include
 * non-linearity, repeatability and hysteresis) using an on-board Application Specific Integrated
 * Circuit (ASIC).
 * 
 * The demo application is composed of two sections :
 *
 * ## Application Init
 * Initialization driver enables I2C.
 *
 * ## Application Task
 * The output measurement command is sent first forcing the ABP2 pressure sensor to exit standby mode and enter operating mode. The device busy state is evaluated via 
 * the end-of-conversion pin ( INT ) following the pressure and temperature data acquisition and calculation. The results are being sent to the Usart Terminaland repeats every 5 seconds.
 *
 * @author Jelena Milosavljevic
 *
 */

// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "pressure14.h"


// ------------------------------------------------------------------ VARIABLES
static pressure14_t pressure14;
static log_t logger;
static uint8_t status;
static uint32_t pressure_tmp;
static uint32_t temperature_tmp;
static float pressure;
static float temperature;

void application_init ( void ) {
    log_cfg_t log_cfg;                  /**< Logger config object. */
    pressure14_cfg_t pressure14_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.
    pressure14_cfg_setup( &pressure14_cfg );
    PRESSURE14_MAP_MIKROBUS( pressure14_cfg, MIKROBUS_1 );
    err_t init_flag = pressure14_init( &pressure14, &pressure14_cfg );
    if ( I2C_MASTER_ERROR == init_flag ) {       
        log_error( &logger, " Application Init Error. " );
        log_info( &logger, " Please, run program again... " );

        for ( ; ; );
    }
    log_info( &logger, " Application Task " );
}

void application_task ( void ) {
    pressure14_measure_cmd( &pressure14 );
    Delay_ms ( 10 );
    
    if ( pressure14_check_busy_flag_int( &pressure14 ) == 1 ) {
        pressure14_read_press_and_temp ( &pressure14, &status, &pressure_tmp, &temperature_tmp );    
        pressure = pressure14_get_pressure( pressure_tmp, PRESSURE14_CONV_UNIT_MILIBAR );
        temperature = pressure14_get_temperature( temperature_tmp, PRESSURE14_CONV_UNIT_CELSIUS );
    
        log_printf( &logger, " Pressure    : %.2f mbar \r\n", pressure );
        log_printf( &logger, " Temperature : %.2f C \r\n", temperature );
        log_printf( &logger, "-------------------------\r\n" );
    }
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );
}

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