Enhance energy efficiency with MLX75305 and PIC18F2682 by tailoring illumination to the available natural light
Let there be light data
Published Jan 23, 2024
Click board™
Ambient Click
Dev Board
Curiosity HPC
Compiler
NECTO Studio
MCU
PIC18F2682
Unlock the ability to monitor and control environmental conditions effortlessly, making your space more comfortable and energy-efficient
A
A
Hardware Overview
How does it work?
Ambient Click is based on the MLX75305, a light-to-voltage SensorEyeC™ from Melexis Technologies. The MLX75305 is the second member of the SensorEyeC™ series of optical sensors designed for high-volume automotive, industrial, and consumer applications. It includes a photodiode, a trans-impedance amplifier to convert and amplify the photocurrent of the photodiode, and an open drain output buffer stage which gives a voltage value that varies
linearly with incident light, available on the AN pin of the mikroBUS™ socket. An internal configuration like this guarantees stable light responsivity over time and temperature and drastically improves noise behavior compared to discrete photodiode designs. Covering a spectral bandwidth from 500nm up to 1000nm, the MLX75305 maintains ±2% linearity across its whole output voltage range with a typical responsiveness of 70mV/(µW/cm²). Its unique features make it
suitable for measuring ambient light or controlling LED light in LCD backlight dimming applications. This Click board™ can operate with either 3.3V or 5V logic voltage levels selected via the PWR SEL jumper. This way, both 3.3V and 5V capable MCUs can use the communication lines properly. Also, this Click board™ comes equipped with a library containing easy-to-use functions and an example code that can be used as a reference for further development.
Features overview
Development board
Curiosity HPC, standing for Curiosity High Pin Count (HPC) development board, supports 28- and 40-pin 8-bit PIC MCUs specially designed by Microchip for the needs of rapid development of embedded applications. This board has two unique PDIP sockets, surrounded by dual-row expansion headers, allowing connectivity to all pins on the populated PIC MCUs. It also contains a powerful onboard PICkit™ (PKOB), eliminating the need for an external programming/debugging tool, two mikroBUS™ sockets for Click board™ connectivity, a USB connector, a set of indicator LEDs, push button switches and a variable potentiometer. All
these features allow you to combine the strength of Microchip and Mikroe and create custom electronic solutions more efficiently than ever. Each part of the Curiosity HPC development board contains the components necessary for the most efficient operation of the same board. An integrated onboard PICkit™ (PKOB) allows low-voltage programming and in-circuit debugging for all supported devices. When used with the MPLAB® X Integrated Development Environment (IDE, version 3.0 or higher) or MPLAB® Xpress IDE, in-circuit debugging allows users to run, modify, and troubleshoot their custom software and hardware
quickly without the need for additional debugging tools. Besides, it includes a clean and regulated power supply block for the development board via the USB Micro-B connector, alongside all communication methods that mikroBUS™ itself supports. Curiosity HPC development board allows you to create a new application in just a few steps. Natively supported by Microchip software tools, it covers many aspects of prototyping thanks to many number of different Click boards™ (over a thousand boards), the number of which is growing daily.
Microcontroller Overview
MCU Card / MCU
Architecture
PIC
MCU Memory (KB)
80
Silicon Vendor
Microchip
Pin count
28
RAM (Bytes)
3328
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Schematic
Step by step
Project assembly
Start by selecting your development board and Click board™. Begin with the Curiosity HPC as your development board.
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.
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™.
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.
Software Support
Library Description
This library contains API for Ambient Click driver.
Key functions:
ambient_read_an_pin_voltage- This function reads results of AD conversion of the AN pin and converts them to proportional voltage levelambient_get_light_intensity- Calculates the light intensity from analog voltage measurement of the Melexis MLX75305 on Ambient Click
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 Ambient Click example
*
* # Description
* This application turns light intensity into voltage.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initialization driver enables GPIO,initializationADC, also write log.
*
* ## Application Task
* This is an example which demonstrates the use of Ambient click board.
* Ambient click reads ADC value and converts to light intensity [ uW/cm2 ].
* Results are being sent to the Usart Terminal where you can track their changes.
* All data logs on USB uart change for every 1 sec.
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "ambient.h"
// ------------------------------------------------------------------ VARIABLES
static ambient_t ambient;
static log_t logger;
uint16_t value_adc;
uint16_t light;
void application_init ( void )
{
log_cfg_t log_cfg;
ambient_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.
ambient_cfg_setup( &cfg );
AMBIENT_MAP_MIKROBUS( cfg, MIKROBUS_1 );
ambient_init( &ambient, &cfg );
log_printf( &logger, " Initialization ADC " );
Delay_ms( 100 );
}
void application_task ( void )
{
ambient_data_t tmp;
// Task implementation.
tmp = ambient_generic_read ( &ambient );
light = ambient_calculate_light_intensity( &ambient, tmp, AMBIENT_VCC_3_3, AMBIENT_RES_12_BIT );
log_printf( &logger, "** ADC value : [DEC]- %d, [HEX]- 0x%x \r\n", tmp, tmp );
log_printf( &logger, "Light Intensity: %d uW/cm2 \r\n", light );
Delay_ms( 1000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
