Determine the distance of the desired target with VL53L5CX and PIC32MZ1024EFH064
Detect the unexpected
Published Mar 11, 2023
Click board™
Proximity 16 Click
Dev. board
PIC32MZ clicker
Compiler
NECTO Studio
MCU
PIC32MZ1024EFH064
Detect the absence or presence of an object without physical contact
A
A
Hardware Overview
How does it work?
Proximity 16 Click is based on the VL53L5CX, an 8x8 multi-zone Time-of-Flight sensor with wide FoV for each zone from STMicroelectronics. The VL53L5CX offers multi-target detection and distance measurement in each zone up to 4 meters. It integrates a SPAD array, physical infrared filters, and diffractive optical elements to achieve the best-ranging performance in various ambient lighting conditions. Also, with ST’s patented histogram algorithms, the VL53L5CX detects multiple objects within the FoV and ensures immunity to cover glass crosstalk beyond 60cm. Using diffractive optical elements above the vertical cavity surface emitting laser (VCSEL) allows a square field-of-view of 45°x45° (63° diagonal)
to be projected onto the scene, where the receiver lens focuses the light reflection onto a SPAD array. The VL53L5CX can range to 8x8 zones at 15Hz for higher resolution or 4x4 at 60Hz for faster-ranging measurements. Proximity 16 Click communicates with MCU using the standard I2C 2-Wire interface to read data and configure settings, supporting Fast Mode Plus Mode up to 1MHz. Also, this Click board™ provides the ability to use I2C communication in Low-Power mode, which activates via the setting of the LP pin routed to the PWM pin on the mikroBUS™ socket. Besides, it provides an intelligent interrupt function that generates every time a ranging measurement is available, alongside an I2C Reset feature
routed to the RST pin on the mikroBUS™ socket, which resets the sensor I2C communication only. Once the host reads the result, the interrupt is cleared, and the ranging sequence can repeat. 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.
Features overview
Development board
PIC32MZ Clicker is a compact starter development board that brings the flexibility of add-on Click boards™ to your favorite microcontroller, making it a perfect starter kit for implementing your ideas. It comes with an onboard 32-bit PIC32MZ microcontroller with FPU from Microchip, a USB connector, LED indicators, buttons, a mikroProg connector, and a header for interfacing with external electronics. Thanks to its compact design with clear and easy-recognizable silkscreen markings, it provides a fluid and immersive working experience, allowing access anywhere and under
any circumstances. Each part of the PIC32MZ Clicker development kit contains the components necessary for the most efficient operation of the same board. In addition to the possibility of choosing the PIC32MZ Clicker programming method, using USB HID mikroBootloader, or through an external mikroProg connector for PIC, dsPIC, or PIC32 programmer, the Clicker board also includes a clean and regulated power supply module for the development kit. The USB Micro-B connection can provide up to 500mA of current, which is more than enough to operate all onboard
and additional modules. All communication methods that mikroBUS™ itself supports are on this board, including the well-established mikroBUS™ socket, reset button, and several buttons and LED indicators. PIC32MZ 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.
Microcontroller Overview
MCU Card / MCU
Architecture
PIC32
MCU Memory (KB)
1024
Silicon Vendor
Microchip
Pin count
64
RAM (Bytes)
524288
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Click board™ Schematic
Step by step
Project assembly
Start by selecting your development board and Click board™. Begin with the PIC32MZ clicker as your development board.
Software Support
Library Description
This library contains API for Proximity 16 Click driver.
Key functions:
proximity16_get_int_pinThis function returns the INT pin logic state.proximity16_get_resolutionThis function gets the current resolution (4x4 or 8x8).proximity16_get_ranging_dataThis function gets the ranging data, using the selected output and the resolution.
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 Proximity 16 Click example
*
* # Description
* This example demonstrates the use of Proximity 16 Click board by reading and displaying
* 8x8 zones measurements on the USB UART.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and performs the Click default configuration.
*
* ## Application Task
* Reads all zone measurements approximately every 500ms and logs them to the USB UART as an 8x8 map.
* The silicon temperature measurement in degrees Celsius is also displayed.
*
* @author Stefan Filipovic
*
*/
#include "board.h"
#include "log.h"
#include "proximity16.h"
static proximity16_t proximity16;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
proximity16_cfg_t proximity16_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.
proximity16_cfg_setup( &proximity16_cfg );
PROXIMITY16_MAP_MIKROBUS( proximity16_cfg, MIKROBUS_1 );
if ( I2C_MASTER_ERROR == proximity16_init( &proximity16, &proximity16_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
if ( PROXIMITY16_ERROR == proximity16_default_cfg ( &proximity16 ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
if ( !proximity16_get_int_pin ( &proximity16 ) )
{
proximity16_results_data_t results;
uint8_t resolution, map_side;
err_t error_flag = proximity16_get_resolution ( &proximity16, &resolution );
error_flag |= proximity16_get_ranging_data ( &proximity16, &results );
if ( PROXIMITY16_OK == error_flag )
{
map_side = ( PROXIMITY16_RESOLUTION_4X4 == resolution ) ? 4 : 8;
log_printf ( &logger, "\r\n %ux%u MAP (mm):\r\n", ( uint16_t ) map_side, ( uint16_t ) map_side );
for ( uint16_t cnt = 1; cnt <= resolution; cnt++ )
{
log_printf ( &logger, " %u\t", results.distance_mm[ cnt - 1 ] );
if ( 0 == ( cnt % map_side ) )
{
log_printf ( &logger, "\r\n" );
}
}
log_printf ( &logger, " Silicon temperature : %d degC\r\n", ( int16_t ) results.silicon_temp_degc );
}
}
}
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
Additional Support
Resources
Category:Proximity
