Beginner
10 min

Comprehensive heart monitoring based on SFH7050 and dsPIC33EP512MU814

Your heart, in real-time

Heart Rate 3 Click with UNI Clicker

Published Jul 01, 2023

Click board™

Heart Rate 3 Click

Dev Board

UNI Clicker

Compiler

NECTO Studio

MCU

dsPIC33EP512MU814

Develop algorithms for pulse oximetry and heart rate readings through the tip of a finger

A

A

Hardware Overview

How does it work?

Heart Rate 3 Click is based on the SFH7050, a pulse oximetry and heart rate sensor from ams OSRAM. This multi-chip package consists of three emitters and one detector, with a light barrier to block crosstalk between the LEDs and the detector. These emitters are green, red, and infrared LEDs pointed toward the measuring objects (human skin, finger). The green LED is most commonly used to measure the dilatation of the blood vessels. The red and the infrared LED light are absorbed differently by oxygen-rich and oxygen-poor blood; therefore, the SFH7050 consists of both of them. The peak wavelength differs from each LED, but the half angle is the same for all three LEDs, ± 60°. As a detector, separated by a block barrier, the photodiode detects the intensity of light returned. As mentioned, this Click board™ uses three LEDs and a photodiode to detect the intensity of light returned, and besides them, it also features the AFE4404, an integrated AFE for optical heart-rate monitoring and bio-sensing from Texas Instruments. The AFE4404 includes a 6-bit

programmable LED current for all three LEDs and individual DC offset subtraction DAC at TIA (Transimpedance Amplifier) input for each LED and ambient phase, allowing to increase sensor's accuracy and remove the noise from the signal. There is also a way to average the 24-bit output from the photodiode before sending it to the BPM algorithm for better noise cancellation. To communicate to the host MCU, the Heart Rate 3 Click uses the I2C interface of the AFE4404 over the mikroBUS™ socket. Every time all three LEDs have finished sampling and converting, the interrupt is triggered over the RDY pin, thus saving the host MCU from constantly polling the sensor for data. This pin is set to a high logic level when the PRF (a pulse repetition frequency) cycle ends, allowing four output data register to be read. The PRF can vary between 10 to 1000 samples per second. The clock input can be selected over the CLK pin, as the AFE4404 can be clocked both internally and externally. The input clock can go up to 60MHz, but the internal divider of the IC has to be set so that the clock stays within the range

from 4MHz to 6MHz. When driven by the internal clock, the device runs at 4MHz. By default, the external clock input is selected. The users can choose one of the clock options over the R5 and R6 resistors (R5 for external clock mode and R6 for internal oscillator mode). After the Power-on sequence, the AFE requires a reset. The RST pin of the mikroBUS™ socket allows the AFE to be reset by the host MCU. Pulling this pin to a low logic state for more than 200µs will put the device into the Power Down mode. The AFE can also be reset by setting a bit in the appropriate register via the I2C interface. This Click board™ can only be operated with a 3.3V logic voltage level. The board must perform appropriate logic voltage level conversion before using MCUs with different logic levels. However, the Click board™ comes equipped with a library containing functions and an example code that can be used, as a reference, for further development. Although the Heart Rate 3 Click is a 3.3V logic level only, the onboard LED SUP jumper allows you to set the voltage for driving the SFH7050 LEDs at either 3.3V or 5V.

Heart Rate 3 Click top side image
Heart Rate 3 Click bottom side image

Features overview

Development board

UNI Clicker is a compact development board designed as a complete solution that brings the flexibility of add-on Click boards™ to your favorite microcontroller, making it a perfect starter kit for implementing your ideas. It supports a wide range of microcontrollers, such as different ARM, PIC32, dsPIC, PIC, and AVR from various vendors like Microchip, ST, NXP, and TI (regardless of their number of pins), four mikroBUS™ sockets for Click board™ connectivity, a USB connector, LED indicators, buttons, a debugger/programmer connector, and two 26-pin headers for interfacing with external electronics. Thanks to innovative manufacturing technology, it allows you to build

gadgets with unique functionalities and features quickly. Each part of the UNI Clicker development kit contains the components necessary for the most efficient operation of the same board. In addition to the possibility of choosing the UNI Clicker programming method, using a third-party programmer or CODEGRIP/mikroProg connected to onboard JTAG/SWD header, the UNI Clicker board also includes a clean and regulated power supply module for the development kit. It provides two ways of board-powering; through the USB Type-C (USB-C) connector, where onboard voltage regulators provide the appropriate voltage levels to each component on the board, or using a Li-Po/Li

Ion battery via an onboard battery connector. All communication methods that mikroBUS™ itself supports are on this board (plus USB HOST/DEVICE), including the well-established mikroBUS™ socket, a standardized socket for the MCU card (SiBRAIN standard), and several user-configurable buttons and LED indicators. UNI Clicker is an integral part of the Mikroe ecosystem, allowing you to create a new application in minutes. Natively supported by Mikroe software tools, it covers many aspects of prototyping thanks to a considerable number of different Click boards™ (over a thousand boards), the number of which is growing every day.

UNI clicker double image

Microcontroller Overview

MCU Card / MCU

default

Type

8th Generation

Architecture

dsPIC

MCU Memory (KB)

512

Silicon Vendor

Microchip

Pin count

144

RAM (Bytes)

53248

Used MCU Pins

mikroBUS™ mapper

NC
NC
AN
Reset
RJ5
RST
NC
NC
CS
NC
NC
SCK
NC
NC
MISO
NC
NC
MOSI
Power Supply
3.3V
3.3V
Ground
GND
GND
External Clock Mode
RF0
PWM
Ready Interrupt
RA14
INT
NC
NC
TX
NC
NC
RX
I2C Clock
RA2
SCL
I2C Data
RA3
SDA
Power Supply
5V
5V
Ground
GND
GND
1

Take a closer look

Schematic

Heart Rate 3 Click Schematic schematic

Step by step

Project assembly

UNI Clicker front image hardware assembly

Start by selecting your development board and Click board™. Begin with the UNI Clicker as your development board.

UNI Clicker front image hardware assembly
Thermo 28 Click front image hardware assembly
SiBRAIN for STM32F745VG front image hardware assembly
Prog-cut hardware assembly
UNI Clicker MB 1 - upright/with-background hardware assembly
Necto image step 2 hardware assembly
Necto image step 3 hardware assembly
Necto image step 4 hardware assembly
Necto image step 5 hardware assembly
Necto image step 6 hardware assembly
Necto image step 7 hardware assembly
Necto No Display image step 8 hardware assembly
Necto image step 9 hardware assembly
Necto image step 10 hardware assembly
Debug Image Necto Step hardware assembly

Track your results in real time

Application Output

After loading the code example, pressing the "DEBUG" button builds and programs it on the selected setup.

Application Output Step 1

After programming is completed, a header with buttons for various actions available in the IDE appears. By clicking the green "PLAY "button, we start reading the results achieved with Click board™.

Application Output Step 3

Upon completion of programming, the Application Output tab is automatically opened, where the achieved result can be read. In case of an inability to perform the Debug function, check if a proper connection between the MCU used by the setup and the CODEGRIP programmer has been established. A detailed explanation of the CODEGRIP-board connection can be found in the CODEGRIP User Manual. Please find it in the RESOURCES section.

Application Output Step 4

Software Support

Library Description

This library contains API for Heart Rate 3 Click driver.

Key functions:

  • heartrate3_check_data_ready - Function is used to check data ready flag

  • heartrate3_write_data - Function is used to write 32-bit data into register

  • heartrate3_read_24bit - Function is used to read 24-bit value from register

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 HeartRate3 Click example
 * 
 * # Description
 * The demo application shows reflected red, green and ir values.
 *
 * The demo application is composed of two sections :
 * 
 * ## Application Init 
 * Initalizes click driver, resets the device, applies default settings
 * and makes an initial log.
 * 
 * ## Application Task  
 * This example demonstrates the use of Heart rate 3 board. It is set in default
 * mode, and reads reflected red, green and ir values and displays the results 
 * on USART terminal.
 * 
 * \author Jovan Stajkovic
 *
 */
// ------------------------------------------------------------------- INCLUDES

#include "board.h"
#include "log.h"
#include "heartrate3.h"

// ------------------------------------------------------------------ VARIABLES

static heartrate3_t heartrate3;
static log_t logger;

static uint32_t led_2;
static uint32_t aled_2;
static uint32_t led_1;
static uint32_t aled_1;
static uint32_t led_2_aled_2;
static uint32_t led_1_aled_1;

// ------------------------------------------------------ APPLICATION FUNCTIONS

void application_init ( void )
{
    log_cfg_t log_cfg;
    heartrate3_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.

    heartrate3_cfg_setup( &cfg );
    HEARTRATE3_MAP_MIKROBUS( cfg, MIKROBUS_1 );
    heartrate3_init( &heartrate3, &cfg );
    log_printf( &logger, "----------------------\r\n" );
    log_printf( &logger, "  Heart rate 3 Click  \r\n" );
    log_printf( &logger, "----------------------\r\n" );
    
    heartrate3_rst_state ( &heartrate3, HEARTRATE3_PIN_STATE_LOW );
    Delay_us( 100 );
    
    heartrate3_rst_state ( &heartrate3, HEARTRATE3_PIN_STATE_HIGH );
    Delay_ms( 1000 );
    
    heartrate3_default_cfg ( &heartrate3 );
    Delay_ms( 100 );
    
    log_printf( &logger, "     Initialised!     \r\n" );
    log_printf( &logger, "----------------------\r\n" );
    Delay_ms(100);
}

void application_task ( void )
{
    led_2 = heartrate3_read_u32( &heartrate3, HEARTRATE3_LED2VAL );
    aled_2 = heartrate3_read_u32( &heartrate3, HEARTRATE3_ALED2VAL );
    led_1 = heartrate3_read_u32( &heartrate3, HEARTRATE3_LED1VAL );
    aled_1 = heartrate3_read_u32( &heartrate3, HEARTRATE3_ALED1VAL );
    led_2_aled_2 = heartrate3_read_u32( &heartrate3, HEARTRATE3_LED2_ALED2VAL );
    led_1_aled_1 = heartrate3_read_u32( &heartrate3, HEARTRATE3_LED1_ALED1VAL );
    
    log_printf( &logger, "%.0f,%.0f,%.0f,%.0f,%.0f,%.0f \r\n", (float)led_2, (float)aled_2, 
                (float)led_1, (float)aled_1, (float)led_2_aled_2, (float)led_1_aled_1 );
    Delay_ms(3);
}

void main ( void )
{
    application_init( );

    for ( ; ; )
    {
        application_task( );
    }
}


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

Additional Support

Resources