Intermediate
30 min

Achieve a deeper understanding of UVB radiation with GUVB-C31SM and STM32F031K6

Safeguarding your skin: The game-changing UVB sensing solution

UVB Click with Nucleo 32 with STM32F031K6 MCU

Published Oct 01, 2024

Click board™

UVB Click

Dev Board

Nucleo 32 with STM32F031K6 MCU

Compiler

NECTO Studio

MCU

STM32F031K6

Discover how our solution delivers accurate UVB data for informed decisions and healthier living

A

A

Hardware Overview

How does it work?

UVB Click is based on GUVB-C31SM, a digital UV sensor from GenUV. The sensor detects UVB light, as it includes on-chip GaN Sensors for UVB. The current generated by photo detectors is converted and measured by ADC and changed to 16-bit resolution digital data. The measured data can be delivered to host via I2C serial interface. Spectral responsivity of sensor is from 240nm up to 320nm which covers full range of UVB spectrum that's defined as light with wavelength from 280nm up to 315nm. The atmosphere blocks about 77% of the Sun's UV, of the ultraviolet radiation that reaches the Earth's surface, more than 95% is the longer

wavelengths of UVA, with the small remainder UVB. Overexposure to UVB radiation not only can cause sunburn but also some forms of skin cancer. UVB radiation can cause direct DNA damage. This cancer connection is one reason for concern about ozone depletion and the ozone hole. One of the benefits of UV light is that it causes the body to produce vitamin D (specifically, UVB), which is essential for life. The human body needs some UV radiation to maintain adequate vitamin D levels; however, excess exposure produces harmful effects that typically outweigh the benefits. With all of this in mind it's very useful to know the

amount of UVB radiation that you are exposed to, and UVB Click board™ is perfect solution for such purpose, and perfect tool for developing wearable devices or weather stations that can report amount of UVB light intensity. Since sensor is supplied with 3.3V only, also featured on this Click board™ is voltage level shifter. For the level shifting, the PCA9306 dual bidirectional I2C bus and SMBus voltage level shifter is used. This level shifter IC allows shifting (converting) the I2C signal levels to the voltage level selected by the VCC SEL onboard SMD jumper. This allows both 3.3V and 5V capable MCUs to be interfaced with the UVB Click.

UVB Click top side image
UVB Click bottom side image

Features overview

Development board

Nucleo 32 with STM32F031K6 MCU board provides an affordable and flexible platform for experimenting with STM32 microcontrollers in 32-pin packages. Featuring Arduino™ Nano connectivity, it allows easy expansion with specialized shields, while being mbed-enabled for seamless integration with online resources. The

board includes an on-board ST-LINK/V2-1 debugger/programmer, supporting USB reenumeration with three interfaces: Virtual Com port, mass storage, and debug port. It offers a flexible power supply through either USB VBUS or an external source. Additionally, it includes three LEDs (LD1 for USB communication, LD2 for power,

and LD3 as a user LED) and a reset push button. The STM32 Nucleo-32 board is supported by various Integrated Development Environments (IDEs) such as IAR™, Keil®, and GCC-based IDEs like AC6 SW4STM32, making it a versatile tool for developers.

Nucleo 32 with STM32F031K6 MCU double side image

Microcontroller Overview

MCU Card / MCU

default

Architecture

ARM Cortex-M0

MCU Memory (KB)

32

Silicon Vendor

STMicroelectronics

Pin count

32

RAM (Bytes)

4096

You complete me!

Accessories

Click Shield for Nucleo-32 is the perfect way to expand your development board's functionalities with STM32 Nucleo-32 pinout. The Click Shield for Nucleo-32 provides two mikroBUS™ sockets to add any functionality from our ever-growing range of Click boards™. We are fully stocked with everything, from sensors and WiFi transceivers to motor control and audio amplifiers. The Click Shield for Nucleo-32 is compatible with the STM32 Nucleo-32 board, providing an affordable and flexible way for users to try out new ideas and quickly create prototypes with any STM32 microcontrollers, choosing from the various combinations of performance, power consumption, and features. The STM32 Nucleo-32 boards do not require any separate probe as they integrate the ST-LINK/V2-1 debugger/programmer and come with the STM32 comprehensive software HAL library and various packaged software examples. This development platform provides users with an effortless and common way to combine the STM32 Nucleo-32 footprint compatible board with their favorite Click boards™ in their upcoming projects.

Click Shield for Nucleo-32 accessories 1 image

Used MCU Pins

mikroBUS™ mapper

NC
NC
AN
NC
NC
RST
NC
NC
CS
NC
NC
SCK
NC
NC
MISO
NC
NC
MOSI
Power Supply
3.3V
3.3V
Ground
GND
GND
NC
NC
PWM
NC
NC
INT
NC
NC
TX
NC
NC
RX
I2C Clock
PB6
SCL
I2C Data
PB7
SDA
Power Supply
5V
5V
Ground
GND
GND
1

Take a closer look

Schematic

UVB Click Schematic schematic

Step by step

Project assembly

Click Shield for Nucleo-144 front image hardware assembly

Start by selecting your development board and Click board™. Begin with the Nucleo 32 with STM32F031K6 MCU as your development board.

Click Shield for Nucleo-144 front image hardware assembly
Nucleo 144 with STM32L4A6ZG MCU front image hardware assembly
2x4 RGB Click front image hardware assembly
Prog-cut hardware assembly
Nucleo-32 with STM32 MCU MB 1 - upright/background hardware assembly
Necto image step 2 hardware assembly
Necto image step 3 hardware assembly
Necto image step 4 hardware assembly
Necto image step 5 hardware assembly
Necto image step 6 hardware assembly
Clicker 4 for STM32F4 HA MCU Step hardware assembly
Necto No Display image step 8 hardware assembly
Necto image step 9 hardware assembly
Necto image step 10 hardware assembly
Debug Image Necto Step hardware assembly

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.

Application Output Step 1

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™.

Application Output Step 3

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.

Application Output Step 4

Software Support

Library Description

This library contains API for UVB Click driver.

Key functions:

  • uvb_configuration - Configuration register

  • uvb_read_byte - Read one byte data from register

  • uvb_get_uv_data - Get UVB data

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 main.c
 * @brief UVB Click example
 *
 * # Description
 * This Click is ultraviolet sensing board, capable of measuring UV index between 0 to 16. 
 * UVB Click supports integrated functions of ultraviolet light sensors.
 *
 * The demo application is composed of two sections :
 *
 * ## Application Init
 * Initialization driver init, check communication and configuration module for measurement.
 *
 * ## Application Task
 * Reads UVB data and logs to the USBUART every 1500ms.
 *
 * @author Mikroe Team
 *
 */

#include "board.h"
#include "log.h"
#include "uvb.h"

static uvb_t uvb;
static log_t logger;

static uint16_t uvb_data;

void application_init ( void ) 
{
    log_cfg_t log_cfg;  /**< Logger config object. */
    uvb_cfg_t uvb_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.
    uvb_cfg_setup( &uvb_cfg );
    UVB_MAP_MIKROBUS( uvb_cfg, MIKROBUS_1 );
    err_t init_flag = uvb_init( &uvb, &uvb_cfg );
    if ( I2C_MASTER_ERROR == init_flag ) {
        log_error( &logger, " Application Init Error. " );
        log_info( &logger, " Please, run program again... " );

        for ( ; ; );
    }

    uvb_default_cfg ( &uvb );
    log_info( &logger, " Application Task " );
    log_printf( &logger, "--------------------------\r\n" );
}

void application_task ( void ) 
{
    uvb_data = uvb_get_uv_data( &uvb );

    log_printf( &logger, ">> UVB data: %d\r\n", uvb_data );

    log_printf( &logger, "--------------------------\r\n" );
    Delay_ms( 1500 );
}

void main ( void ) 
{
    application_init( );

    for ( ; ; ) {
        application_task( );
    }
}

// ------------------------------------------------------------------------ END

Additional Support

Resources

Love this project?

'Buy This Kit' button takes you directly to the shopping cart where you can easily add or remove products.