Enhance workplace safety and reduce the risk of UV-C exposure with 3535UVC1W and MK64FN1M0VDC12
See what's unseen
Published Sep 05, 2023
Click board™
UVC Light Click
Dev. board
Clicker 2 for Kinetis
Compiler
NECTO Studio
MCU
MK64FN1M0VDC12
Our innovative solution combines two 275nm UV-C LEDs with a green LED to provide a visual indicator, helping users identify and avoid direct exposure to potentially harmful UV-C light
A
A
Hardware Overview
How does it work?
UVC Light Click uses two 0.7W, 275nm LEDs and one green LED that allow users to see the approximate area where UVC light is shining since these UV wavelengths are not visible to the human eye and should avoid direct exposure to the eye. UVC Light Click can be used as a disinfection tool because DNA, RNA, and proteins absorb UV light in the range of 200 nm to 300 nm. Absorption by proteins can lead to the rupture of cell walls and the organism's death. Absorption by DNA or RNA (specifically by thymine bases) is
known to cause inactivation of the DNA or RNA double helix strands by forming thymine dimers. If enough of these dimers are created in DNA, the DNA replication process is disrupted, and the cell cannot replicate. It is widely accepted that it is not necessary to kill pathogens with UV light but rather apply enough UV light to prevent the organism from replicating. The UV doses required to prevent replication are orders of magnitude lower than required to kill, making the cost of UV treatment to prevent infection commercially
viable. UVC Light Click is implementing a TPS61169 LED driver with PWM brightness control to drive LEDs in series and an MC34671 battery charger to allow charging of battery when Click board™ is inserted in the mikroBUS™ socket; CHG LED will indicate the charging in progress and will turn off once the battery charging is finished. When the PWR SEL jumper is repositioned to the right position, you can use UVC Light and click standalone if no dimming is necessary or high mobility is needed.
Features overview
Development board
Clicker 2 for Kinetis 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 ARM Cortex-M4F microcontroller, the MK64FN1M0VDC12 from NXP Semiconductors, two mikroBUS™ sockets for Click board™ connectivity, a USB connector, LED indicators, buttons, a JTAG programmer connector, and two 26-pin headers for interfacing with external electronics. Its compact design with clear and easily recognizable silkscreen markings allows you to build gadgets with unique functionalities and
features quickly. Each part of the Clicker 2 for Kinetis development kit contains the components necessary for the most efficient operation of the same board. In addition to the possibility of choosing the Clicker 2 for Kinetis programming method, using a USB HID mikroBootloader or an external mikroProg connector for Kinetis programmer, the Clicker 2 board also includes a clean and regulated power supply module for the development kit. It provides two ways of board-powering; through the USB Micro-B cable, where onboard voltage regulators provide the appropriate voltage levels to each component on the board, or
using a Li-Polymer battery via an onboard battery connector. All communication methods that mikroBUS™ itself supports are on this board, including the well-established mikroBUS™ socket, reset button, and several user-configurable buttons and LED indicators. Clicker 2 for Kinetis 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
ARM Cortex-M4
MCU Memory (KB)
1024
Silicon Vendor
NXP
Pin count
121
RAM (Bytes)
262144
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 Clicker 2 for Kinetis as your development board.
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 UVC Light Click driver.
Key functions:
uvclight_pwm_start- This function starts PWM moduleuvclight_set_duty_cycle- This function sets the PWM duty cycleuvclight_pwm_stop- This function stops PWM module.
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
* @brief UvcLight Click example
*
* # Description
* This click has ultraviolet LEDs with 275nm wavelength. UVC radiation refers to wavelengths
* shorter than 280 nm. Because of the spectral sensitivity of DNA, only the UVC region
* demonstrates significant germicidal properties.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver.
*
* ## Application Task
* Increases and decreases the pwm duty cycle.
* Results are being sent to the Usart Terminal where you can track their changes.
*
* CAUTION! High intensity UV Light - avoid eye and skin exposure. Avoid looking direclty at light!
*
* @author Nikola Peric
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "uvclight.h"
// ------------------------------------------------------------------ VARIABLES
static uvclight_t uvclight;
static log_t logger;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
uvclight_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.
uvclight_cfg_setup( &cfg );
UVCLIGHT_MAP_MIKROBUS( cfg, MIKROBUS_1 );
uvclight_init( &uvclight, &cfg );
uvclight_set_duty_cycle ( &uvclight, 0.0 );
uvclight_pwm_start( &uvclight );
Delay_ms( 100 );
log_info( &logger, "---- Application Task ----" );
}
void application_task ( void )
{
static int8_t duty_cnt = 1;
static int8_t duty_inc = 1;
float duty = duty_cnt / 10.0;
uvclight_set_duty_cycle ( &uvclight, duty );
log_printf( &logger, "Duty: %d%%\r\n", ( uint16_t )( duty_cnt * 10 ) );
Delay_ms( 500 );
if ( 10 == duty_cnt )
{
duty_inc = -1;
}
else if ( 0 == duty_cnt )
{
log_printf( &logger, "Cooldown 2 SEC\r\n");
Delay_ms( 2000 );
duty_inc = 1;
}
duty_cnt += duty_inc;
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
