30 min

Streamline pressure measurement in various settings with KP229E2701 and PIC18F86J50

Pressure's best friend: Your reliable wingman in the digital realm

Pressure 13 Click with Fusion for PIC v8

Published Oct 13, 2023

Click board™

Pressure 13 Click

Development board

Fusion for PIC v8


NECTO Studio



Experience the future of pressure measurement with our digital sensor, which empowers you with real-time, high-precision data to streamline your operations and enhance decision-making



Hardware Overview

How does it work?

Pressure 13 Click is based on the KP229E2701, a miniaturized analog absolute pressure sensor based on a capacitive principle from Infineon. The pressure is detected by an array of capacitive surface micromachined sensor cells (a monolithic integrated signal conditioning circuit implemented in BiCMOS technology). The sensor cell output is amplified, temperature compensated, and linearized to obtain an output voltage proportional to the applied pressure. The manifold air pressure (MAP) is a principal parameter to compute the air-fuel ratio provided to the engine for lower emission due to better combustion and increased efficiency. For cost-sensitive engine systems, a MAP sensor shows the potential to complement or even substitute mass airflow (MAF) sensors. The accuracy of the KP229E2701 sensor is influenced by the supply

voltage (ratiometric error) and pressure, temperature, and aging effects. All parameters needed for the complete calibration algorithm - such as offset, gain, temperature coefficients of offset and gain, and linearization parameters - are determined after the assembly. These parameters are stored in an integrated E²PROM protected with forwarding error correction (a one-bit error is detected and corrected, more than one-bit errors are detected, and the output signal is switched to ground potential). In automotive applications where high production volumes are custom, there is substantial interest in precision, low-cost, and fully integrated sensors. That’s why the manifold pressure data can be used to compute diagnostics of leakages and malfunctions of the exhaust gas recirculation valve. Pressure 13 Click communicates with MCU using only one GPIO

pin routed on the AN pin of the mikroBUS™ socket. The KP229E2701 sensor possesses several digital pins used only during calibration and testing. That’s why it’s recommended and done to leave these pins floating. The output circuit acts as a low-pass decoupling filter between the sensor output and the A/D input of the MCU because it’s recommended to protect the pressure sensor against overload and electromagnetic interferences. This Click board™ can be operated only with a 5V 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.

Pressure 13 Click top side image
Pressure 13 Click bottom side image

Features overview

Development board

Fusion for PIC v8 is a development board specially designed for the needs of rapid development of embedded applications. It supports a wide range of microcontrollers, such as different PIC, dsPIC, PIC24, and PIC32 MCUs regardless of their number of pins, and a broad set of unique functions, such as the first-ever embedded debugger/programmer over WiFi. The development board is well organized and designed so that the end-user has all the necessary elements, such as switches, buttons, indicators, connectors, and others, in one place. Thanks to innovative manufacturing technology, Fusion for PIC v8 provides a fluid and immersive working experience, allowing access anywhere and under any

circumstances at any time. Each part of the Fusion for PIC v8 development board contains the components necessary for the most efficient operation of the same board. In addition to the advanced integrated CODEGRIP programmer/debugger module, which offers many valuable programming/debugging options and seamless integration with the Mikroe software environment, the board also includes a clean and regulated power supply module for the development board. It can use a wide range of external power sources, including a battery, an external 12V power supply, and a power source via the USB Type-C (USB-C) connector. Communication options such as USB-UART, USB

HOST/DEVICE, CAN (on the MCU card, if supported), and Ethernet are also included, including the well-established mikroBUS™ standard, a standardized socket for the MCU card (SiBRAIN standard), and two display options (graphical and character-based LCD). Fusion for PIC v8 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.

Fusion for PIC v8 horizontal image

Microcontroller Overview

MCU Card / MCU



8th Generation



MCU Memory (KB)


Silicon Vendor


Pin count


RAM (Bytes)


Used MCU Pins

mikroBUS™ mapper

Analog Output
Power Supply

Take a closer look


Pressure 13 Click Schematic schematic

Step by step

Project assembly

Fusion for PIC v8 front image hardware assembly

Start by selecting your development board and Click board™. Begin with the Fusion for PIC v8 as your development board.

Fusion for PIC v8 front image hardware assembly
Buck 22 Click front image hardware assembly
SiBRAIN for PIC32MZ1024EFK144 front image hardware assembly
v8 SiBRAIN MB 1 - upright/background hardware assembly
Necto image step 2 hardware assembly
Necto image step 3 hardware assembly
Necto image step 4 hardware assembly
NECTO Compiler Selection Step Image hardware assembly
NECTO Output Selection Step Image hardware assembly
Necto image step 6 hardware assembly
Necto image step 7 hardware assembly
Necto image step 8 hardware assembly
Necto image step 9 hardware assembly
Necto image step 10 hardware assembly
Necto PreFlash Image hardware assembly

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.

UART Application Output Step 1

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.

UART Application Output Step 2

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".

UART Application Output Step 3

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.

UART Application Output Step 4

Software Support

Library Description

This library contains API for Pressure 13 Click driver.

Key functions:

  • pressure13_read_an_pin_value - Pressure 13 read AN pin value function

  • pressure13_read_an_pin_voltage - Pressure 13 read AN pin voltage level function

  • pressure13_get_pressure - Pressure 13 read AN pin voltage level 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 main.c
 * @brief Pressure 13 Click Example.
 * # Description
 * This is an example which demonstrates the use of Pressure 13 Click board.
 * The demo application is composed of two sections :
 * ## Application Init
 * Initialization driver enables - GPIO, initializes ADC, also write log.
 * ## Application Task
 * Measure and display pressure ( mBar ). Results are being sent to the 
 * Usart Terminal where you can track their changes.
 * All data logs on usb uart approximately every sec.
 * @author Stefan Ilic

#include "board.h"
#include "log.h"
#include "pressure13.h"

static pressure13_t pressure13;   /**< Pressure 13 Click driver object. */
static log_t logger;    /**< Logger object. */

static uint16_t adc_val;
static float pressure_val;
static float voltage_val;

void application_init ( void ) {
    log_cfg_t log_cfg;  /**< Logger config object. */
    pressure13_cfg_t pressure13_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.
    pressure13_cfg_setup( &pressure13_cfg );
    PRESSURE13_MAP_MIKROBUS( pressure13_cfg, MIKROBUS_1 );
    if ( ADC_ERROR == pressure13_init( &pressure13, &pressure13_cfg ) )
        log_error( &logger, " Application Init Error. " );
        log_info( &logger, " Please, run program again... " );

        for ( ; ; );
    log_info( &logger, " Application Task " );
    log_printf( &logger, "-------------------------\r\n", voltage_val );

void application_task ( void ) {
    if ( pressure13_get_pressure( &pressure13, &pressure_val ) != ADC_ERROR ) {
        log_printf( &logger, " Pressure: %.3f [mBar]\r\n", pressure_val );
    log_printf( &logger, "-------------------------\r\n" );
    Delay_ms( 1000 );

void main ( void ) {
    application_init( );

    for ( ; ; ) {
        application_task( );

// ------------------------------------------------------------------------ END

Additional Support