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.17
mikroSDK Library: 2.0.0.0
Category: Proximity
Downloaded: 172 times
Not followed.
License: MIT license
Proximity 11 Click is a close-range proximity sensing Click board™, equipped with the RPR-0521RS, a very accurate and power-efficient proximity and ambient Light Sensor with IrLED.
Do you want to subscribe in order to receive notifications regarding "Proximity 11 Click" changes.
Do you want to unsubscribe in order to stop receiving notifications regarding "Proximity 11 Click" changes.
Do you want to report abuse regarding "Proximity 11 Click".
DOWNLOAD LINK | RELATED COMPILER | CONTAINS |
---|---|---|
3995_proximity_11_cli.zip [430.94KB] | 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 |
|
Proximity 11 Click is a close-range proximity sensing Click board™, equipped with the RPR-0521RS, a very accurate and power-efficient proximity and ambient Light Sensor with IrLED.
We provide a library for the Proximity11 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 Proximity11 Click driver.
Config Object Initialization function.
void proximity11_cfg_setup ( proximity11_cfg_t *cfg );
Initialization function.
PROXIMITY11_RETVAL proximity11_init ( proximity11_t ctx, proximity11_cfg_t cfg );
Click Default Configuration function.
void proximity11_default_cfg ( proximity11_t *ctx );
This function reads proximity values from the desired registers.
uint8_t proximity11_get ( proximity11_t ctx, uint8_t register_address, uint8_t output_buffer, uint8_t n_bytes );
This function updates data used to calculate Lux. This function should be called if changing als measurement time and als gain.
void proximity11_update ( proximity11_t *ctx );
This function sets High ALS threshold value
void proximity11_set_als_threshold_high ( proximity11_t *ctx, uint16_t threshold_value );
This appication enables usage of the proximity and ambient light sensors
The demo application is composed of two sections :
Initializes I2C driver and performs device initialization
void application_init ( void )
{
log_cfg_t log_cfg;
proximity11_cfg_t cfg;
uint8_t init_status;
/**
* 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.
proximity11_cfg_setup( &cfg );
PROXIMITY11_MAP_MIKROBUS( cfg, MIKROBUS_4 );
proximity11_init( &proximity11, &cfg );
Delay_ms ( 500 );
init_status = proximity11_default_cfg( &proximity11 );
if ( init_status == 1 )
{
log_printf( &logger, "> app init fail\r\n" );
while( 1 );
}
else if ( init_status == 0 )
{
log_printf( &logger, "> app init done\r\n" );
}
}
Gets ALS and PS values and logs those values
void application_task ( void )
{
// Task implementation
uint16_t ps_value;
float als_value;
proximity11_get_ps_als_values( &proximity11, &ps_value, &als_value );
log_printf( &logger, "PS : %ld [count]\r\n", ps_value );
log_printf( &logger, "ALS : %.2f [Lx]\r\n\r\n", als_value );
Delay_ms ( 500 );
}
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.