Switch to a world of convenience and reliability with our power PCB relay – the smart choice for your electrical control needs
A
A
Hardware Overview
How does it work?
Flicker Click is based on the G6D-ASI, a power PCB relay from OMRON. It has a long service life with up to 300.000 operations at maximum rated loads. Its contact resistance is 100mΩ, with 5ms of release time, and it is designed to withstand 500VDC. Its coil is powered by 5V from the mikroBUS™ socket. The load can be connected to the relay over the onboard screw terminal and isolated from the board. Remember not to touch the board while the external power supply is on; the Flicker Click has exposed pins/pads. Thanks to
the onboard NE556, a dual precision timer from Texas Instruments, and two onboard 500K potentiometers, you can easily set the on/off periods. You will need a fine screwdriver to set the desired position of the potentiometers. A stopwatch can measure the ON/OFF periods if you need precise time. This way, you can set different or the same periods for both on and off states. The onboard LED stands for the visual presentation of the status of the relay. The Flicker Click uses a FON pin of the mikroBUS™ socket to communicate
with the host MCU. Over this pin, you can turn the NE556 ON and OFF. This Click board™ can be operated only with a 5V 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
Fusion for KINETIS v8 is a development board specially designed for the needs of rapid development of embedded applications. It supports a wide range of microcontrollers, such as different 32-bit ARM® Cortex®-M based MCUs from NXP Semiconductor, regardless of their number of pins, and a broad set of unique functions, such as the first-ever embedded debugger/programmer over a WiFi network. The development board is well organized and designed so that the end-user has all the necessary elements, such as switches, buttons, indicators, connectors, and others, in one place. Thanks to innovative manufacturing technology, Fusion for KINETIS v8 provides a fluid and immersive working experience, allowing
access anywhere and under any circumstances at any time. Each part of the Fusion for KINETIS v8 development board contains the components necessary for the most efficient operation of the same board. An advanced integrated CODEGRIP programmer/debugger module offers many valuable programming/debugging options, including support for JTAG, SWD, and SWO Trace (Single Wire Output)), and seamless integration with the Mikroe software environment. Besides, it also includes a clean and regulated power supply module for the development board. It can use a wide range of external power sources, including a battery, an external 12V power supply, and a power source via the USB Type-C (USB-C) connector.
Communication options such as USB-UART, USB HOST/DEVICE, CAN (on the MCU card, if supported), and Ethernet is also included. In addition, it also has the well-established mikroBUS™ standard, a standardized socket for the MCU card (SiBRAIN standard), and two display options for the TFT board line of products and character-based LCD. Fusion for KINETIS v8 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
![default](https://cdn.mikroe.com/rent-a-product/request-setup/mcu-cards/mcu-card-2-for-kinetis-mk20dn128vfm5.png)
Type
8th Generation
Architecture
ARM Cortex-M4
MCU Memory (KB)
128
Silicon Vendor
NXP
Pin count
32
RAM (Bytes)
16384
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Schematic
![FLICKER Click Schematic schematic](https://dbp-cdn.mikroe.com/catalog/click-boards/resources/1ee79096-49b3-63f0-bad9-0242ac120009/schematic.webp)
Step by step
Project assembly
Track your results in real time
Application Output
After pressing the "FLASH" button on the left-side panel, it is necessary to open the UART terminal to display the achieved results. By clicking on the Tools icon in the right-hand panel, multiple different functions are displayed, among which is the UART Terminal. Click on the offered "UART Terminal" icon.
![UART Application Output Step 1](https://dbp-cdn.mikroe.com/cms/shared-resources/1eed703a-40a0-6b58-88de-02420a00029a/UART-AO-Step-1.jpg)
Once the UART terminal is opened, the window takes on a new form. At the top of the tab are two buttons, one for adjusting the parameters of the UART terminal and the other for connecting the UART terminal. The tab's lower part is reserved for displaying the achieved results. Before connecting, the terminal has a Disconnected status, indicating that the terminal is not yet active. Before connecting, it is necessary to check the set parameters of the UART terminal. Click on the "OPTIONS" button.
![UART Application Output Step 2](https://dbp-cdn.mikroe.com/cms/shared-resources/1eed703a-eb29-62fa-ba91-02420a00029a/UART-AO-Step-2.jpg)
In the newly opened UART Terminal Options field, we check if the terminal settings are correct, such as the set port and the Baud rate of UART communication. If the data is not displayed properly, it is possible that the Baud rate value is not set correctly and needs to be adjusted to 115200. If all the parameters are set correctly, click on "CONFIGURE".
![UART Application Output Step 3](https://dbp-cdn.mikroe.com/cms/shared-resources/1eed703b-7543-6fbc-9c69-0242ac120003/UART-AO-Step-3.jpg)
The next step is to click on the "CONNECT" button, after which the terminal status changes from Disconnected to Connected in green, and the data is displayed in the Received data field.
![UART Application Output Step 4](https://dbp-cdn.mikroe.com/cms/shared-resources/1eed703c-068c-66a4-a4fc-0242ac120003/UART-AO-Step-4.jpg)
Software Support
Library Description
This library contains API for FLICKER Click driver.
Key functions:
flicker_engage
- Flicker engage function
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 Flicker Click example
*
* # Description
* This application simple solution if you need to turn a device on and off at specific time intervals.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initialization driver enables GPIO and also starts write log.
*
* ## Application Task
* This example demonstrates capabilities of Flicker Click board.
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "flicker.h"
// ------------------------------------------------------------------ VARIABLES
static flicker_t flicker;
static log_t logger;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
flicker_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.
flicker_cfg_setup( &cfg );
FLICKER_MAP_MIKROBUS( cfg, MIKROBUS_1 );
flicker_init( &flicker, &cfg );
}
void application_task ( void )
{
// Task implementation.
log_printf( &logger, " *Flicker on!* \r\n" );
Delay_ms( 500 );
flicker_engage( &flicker );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END