We strongly encourage users to use Package manager for sharing their code on Libstock website, because it boosts your efficiency and leaves the end user with no room for error. [more info]
Rating:
Author: MIKROE
Last Updated: 2024-10-31
Package Version: 2.1.0.12
mikroSDK Library: 2.0.0.0
Category: Biometrics
Downloaded: 271 times
Not followed.
License: MIT license
Heart rate 3 Click is a mikroBUS add-on board whose functionality is determined by two components: an OSRAM’s SFH7050 pulse oximetry and heart rate monitoring module, and a TI AFE4404 (analong-front-end) IC specialized for bio-sensing.
Do you want to subscribe in order to receive notifications regarding "Heart rate 3 Click" changes.
Do you want to unsubscribe in order to stop receiving notifications regarding "Heart rate 3 Click" changes.
Do you want to report abuse regarding "Heart rate 3 Click".
DOWNLOAD LINK | RELATED COMPILER | CONTAINS |
---|---|---|
3557_heart_rate_3_cli.zip [477.12KB] | mikroC AI for ARM GCC for ARM Clang for ARM mikroC AI for PIC mikroC AI for PIC32 XC32 GCC for RISC-V Clang for RISC-V mikroC AI for AVR mikroC AI for dsPIC XC16 |
|
Heart rate 3 Click is a mikroBUS add-on board whose functionality is determined by two components: an OSRAM’s SFH7050 pulse oximetry and heart rate monitoring module, and a TI AFE4404 (analong-front-end) IC specialized for bio-sensing.
We provide a library for the HeartRate3 Click as well as a demo application (example), developed using MikroElektronika compilers. The demo can run on all the main MikroElektronika development boards.
Package can be downloaded/installed directly form compilers IDE(recommended way), or downloaded from our LibStock, or found on mikroE github account.
This library contains API for HeartRate3 Click driver.
heartrate3_cfg_setup
Config Object Initialization function.
void heartrate3_cfg_setup ( heartrate3_cfg_t *cfg );
heartrate3_init
Initialization function.
err_t heartrate3_init ( heartrate3_t *ctx, heartrate3_cfg_t *cfg );
heartrate3_default_cfg
Click Default Configuration function.
err_t heartrate3_default_cfg ( heartrate3_t *ctx );
heartrate3_check_data_ready
Function is used to check data ready flag.
uint8_t heartrate3_check_data_ready ( heartrate3_t *ctx );
heartrate3_write_data
Function is used to write 32-bit data into register.
err_t heartrate3_write_data ( heartrate3_t *ctx, uint8_t reg_adr, uint32_t wr_data );
heartrate3_read_24bit
Function is used to read 24-bit value from register.
err_t heartrate3_read_24bit ( heartrate3_t *ctx, uint8_t reg_adr, uint32_t *data_out );
The demo application shows reflected red, green and ir values.
The demo application is composed of two sections :
Initalizes Click driver, resets the device, applies default settings and makes an initial log.
void application_init ( void )
{
log_cfg_t log_cfg;
heartrate3_cfg_t heartrate3_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( &heartrate3_cfg );
HEARTRATE3_MAP_MIKROBUS( heartrate3_cfg, MIKROBUS_1 );
if ( I2C_MASTER_ERROR == heartrate3_init( &heartrate3, &heartrate3_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
log_printf( &logger, "----------------------\r\n" );
log_printf( &logger, " Heart rate 3 Click \r\n" );
log_printf( &logger, "----------------------\r\n" );
if ( HEARTRATE3_ERROR == heartrate3_default_cfg ( &heartrate3 ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
log_printf( &logger, " Initialised! \r\n" );
log_printf( &logger, "----------------------\r\n" );
log_info( &logger, " Application Task " );
Delay_ms ( 100 );
}
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.
void application_task ( void )
{
err_t error_flag = HEARTRATE3_OK;
if ( heartrate3_check_data_ready ( &heartrate3 ) )
{
error_flag |= heartrate3_read_24bit( &heartrate3, HEARTRATE3_REG_LED2VAL, &led_2 );
error_flag |= heartrate3_read_24bit( &heartrate3, HEARTRATE3_REG_ALED2VAL, &aled_2 );
error_flag |= heartrate3_read_24bit( &heartrate3, HEARTRATE3_REG_LED1VAL, &led_1 );
error_flag |= heartrate3_read_24bit( &heartrate3, HEARTRATE3_REG_ALED1VAL, &aled_1 );
error_flag |= heartrate3_read_24bit( &heartrate3, HEARTRATE3_REG_LED2_ALED2VAL, &led_2_aled_2 );
error_flag |= heartrate3_read_24bit( &heartrate3, HEARTRATE3_REG_LED1_ALED1VAL, &led_1_aled_1 );
if ( HEARTRATE3_OK == error_flag )
{
log_printf( &logger, "%lu;%lu;%lu;%lu;%lu;%lu;\r\n",
led_2, aled_2, led_1, aled_1, led_2_aled_2, led_1_aled_1 );
}
}
}
We recommend using the SerialPlot tool for data visualizing.
The full application code, and ready to use projects can be installed directly form compilers IDE(recommneded) or found on LibStock page or mikroE GitHub accaunt.
Other mikroE Libraries used in the example:
Additional notes and informations
Depending on the development board you are using, you may need USB UART Click, USB UART 2 Click or RS232 Click to connect to your PC, for development systems with no UART to USB interface available on the board. The terminal available in all Mikroelektronika compilers, or any other terminal application of your choice, can be used to read the message.