Accurate light measurement capabilities for automotive, display backlighting control, industrial, and various scenarios requiring precise light sensing.
A
A
Hardware Overview
How does it work?
Light 2 Click is based on the ISL76682, an automotive low-power, high-sensitivity, light-to-digital sensor with an I2C interface from Renesas. Designed for precise light measurement, the ISL76682 features a state-of-the-art photodiode array that closely mimics the human eye's response while effectively rejecting UV and infrared light. It includes an ADC that eliminates flickers at 50Hz and 60Hz from artificial lighting. Users can adjust the light measurement range through the I2C interface, with four selectable ranges from as low as 0.015lux up to 64.000lux, enhancing the flexibility and accuracy of light intensity readings. It's ideally suited for automotive interior lighting
adjustment, display backlighting control, and light measurement in industrial and medical environments. The ISL76682 operates with low energy consumption, typically around 55µA in its Standard mode. It includes options for further reducing power usage through two power-down modes. The automatic power-down function turns off the sensor after each light measurement cycle when set to polling mode, while a software-controlled mode via the I2C interface can lower the power draw to less than 1µA. The ISL76682 outputs a simple code corresponding to the lux level, offers up to 16-bit resolution, and adapts to various lighting conditions, including direct sunlight.
Light 2 Click uses a standard 2-wire I2C interface to communicate with the host MCU, supporting Standard mode with up to 400kHz of frequency clock. In addition to I2C pins, the device allows the selection of I2C slave address between 0x44 and 0x45 via an SMD jumper marked as ADDR SEL. This Click board™ can be operated only with a 3.3V logic voltage level. The board must perform appropriate logic voltage level conversion before using MCUs with different logic levels. Also, it 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
EasyAVR v7 is the seventh generation of AVR development boards specially designed for the needs of rapid development of embedded applications. It supports a wide range of 16-bit AVR microcontrollers from Microchip and has a broad set of unique functions, such as a powerful onboard mikroProg programmer and In-Circuit debugger over USB. The development board is well organized and designed so that the end-user has all the necessary elements in one place, such as switches, buttons, indicators, connectors, and others. With four different connectors for each port, EasyAVR v7 allows you to connect accessory boards, sensors, and custom electronics more
efficiently than ever. Each part of the EasyAVR v7 development board contains the components necessary for the most efficient operation of the same board. An integrated mikroProg, a fast USB 2.0 programmer with mikroICD hardware In-Circuit Debugger, offers many valuable programming/debugging options and seamless integration with the Mikroe software environment. Besides it also includes a clean and regulated power supply block for the development board. It can use a wide range of external power sources, including an external 12V power supply, 7-12V AC or 9-15V DC via DC connector/screw terminals, and a power source via the USB Type-B (USB-B)
connector. Communication options such as USB-UART and RS-232 are also included, alongside the well-established mikroBUS™ standard, three display options (7-segment, graphical, and character-based LCD), and several different DIP sockets which cover a wide range of 16-bit AVR MCUs. EasyAVR v7 is an integral part of the Mikroe ecosystem for rapid development. Natively supported by Mikroe software tools, it covers many aspects of prototyping and development 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
AVR
MCU Memory (KB)
32
Silicon Vendor
Microchip
Pin count
40
RAM (Bytes)
2048
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Click board™ Schematic

Step by step
Project assembly
Track your results in real time
Application Output
1. Application Output - In Debug mode, the 'Application Output' window enables real-time data monitoring, offering direct insight into execution results. Ensure proper data display by configuring the environment correctly using the provided tutorial.

2. UART Terminal - Use the UART Terminal to monitor data transmission via a USB to UART converter, allowing direct communication between the Click board™ and your development system. Configure the baud rate and other serial settings according to your project's requirements to ensure proper functionality. For step-by-step setup instructions, refer to the provided tutorial.

3. Plot Output - The Plot feature offers a powerful way to visualize real-time sensor data, enabling trend analysis, debugging, and comparison of multiple data points. To set it up correctly, follow the provided tutorial, which includes a step-by-step example of using the Plot feature to display Click board™ readings. To use the Plot feature in your code, use the function: plot(*insert_graph_name*, variable_name);. This is a general format, and it is up to the user to replace 'insert_graph_name' with the actual graph name and 'variable_name' with the parameter to be displayed.

Software Support
Library Description
This library contains API for Light 2 Click driver.
Key functions:
light2_read_raw_data
- This function reads raw data from the ADC of Light 2 click board.light2_get_cal_const
- This function is used to get a calculation constant depending on Light 2 click board configuration.light2_get_light_data
- This function is used to read light data of Light 2 click board configuration.
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 Light 2 Click example
*
* # Description
* This example demonstrates the use of Light 2 click board by measuring
* the ambient light level in Lux.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and performs the click default configuration.
*
* ## Application Task
* Reads the ADC voltage and then calculates the illuminance from it.
* The calculated value of illuminance in lux is being displayed on the USB UART approximately once per second.
*
* @author Stefan Ilic
*
*/
#include "board.h"
#include "log.h"
#include "light2.h"
static light2_t light2;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
light2_cfg_t light2_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.
light2_cfg_setup( &light2_cfg );
LIGHT2_MAP_MIKROBUS( light2_cfg, MIKROBUS_1 );
if ( I2C_MASTER_ERROR == light2_init( &light2, &light2_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
if ( LIGHT2_ERROR == light2_default_cfg ( &light2 ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
float lux_data = 0;
light2_get_light_data( &light2, &lux_data );
log_printf( &logger, " LUX data: %.2f LUX \r\n", lux_data );
Delay_ms ( 1000 );
}
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