Easily create a remote switch that can turn things ON and OFF, like lights or motors, in your projects
A
A
Hardware Overview
How does it work?
RELAY Click is based on two G6D1AASIDC5s, slim miniature relays from OMRON. Despite its size, the G6D-1A-ASI DC5 relay can withstand up to 5A and 220V AC/30V DC. It can endure up to 300,000 operations, with 30V DC and 2A. This relay has a single pole only - when the coil is energized, it will attract the internal switching elements and close the circuit, similarly to a switch. These relays are designed so relatively low currents and voltages
can easily activate their coils. For the G6D-1A-ASI DC5 relay operated at 5V, the coil current is 40mA. This makes them a perfect choice for activating them by an MCU. RELAY Click uses GPIO pins RL1 and RL2 to be controlled by the host MCU. Since RELAY Click uses an NPN RET and resistors, the host MCU is safe from the current spikes driving the relay's coils. In addition, there is an LED for every relay, each of a different color,
representing the relays' status. 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
EasyPIC v8 is a development board specially designed for the needs of rapid development of embedded applications. It supports many high pin count 8-bit PIC microcontrollers from Microchip, regardless of their number of pins, and a broad set of unique functions, such as the first-ever embedded debugger/programmer. 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, EasyPIC v8 provides a fluid and immersive working experience, allowing access anywhere and under any
circumstances at any time. Each part of the EasyPIC v8 development board contains the components necessary for the most efficient operation of the same board. In addition to the advanced integrated CODEGRIP programmer/debugger module, which offers many valuable programming/debugging options and seamless integration with the Mikroe software environment, the board 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 DEVICE, and CAN are also included, including the well-established mikroBUS™ standard, two display options (graphical and character-based LCD), and several different DIP sockets. These sockets cover a wide range of 8-bit PIC MCUs, from the smallest PIC MCU devices with only eight up to forty pins. EasyPIC 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

Architecture
PIC
MCU Memory (KB)
24
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 RELAY Click driver.
Key functions:
relay_set_state
- Relay set state
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 Relay Click example
*
* # Description
* Demo application is used to shows basic controls Relay click
*
* The demo application is composed of two sections :
*
* ## Application Init
* Configuring clicks and log objects.
* Settings the click in the default configuration.
*
* ## Application Task
* Alternately sets relays to ON-OFF state...
*
* \author Katarina Perendic
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "relay.h"
// ------------------------------------------------------------------ VARIABLES
static relay_t relay;
static log_t logger;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
relay_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.
relay_cfg_setup( &cfg );
RELAY_MAP_MIKROBUS( cfg, MIKROBUS_1 );
relay_init( &relay, &cfg );
relay_default_cfg ( &relay );
Delay_ms( 1500 );
}
void application_task ( void )
{
uint8_t cnt;
// Task implementation.
for ( cnt = 1; cnt <= 2; cnt++)
{
log_info( &logger, "*** Relay %d state is ON \r\n", (uint16_t)cnt);
relay_set_state( &relay, cnt, RELAY_STATE_ON );
Delay_ms ( 1000 );
log_info( &logger, "*** Relay %d state is OFF \r\n", (uint16_t)cnt);
relay_set_state( &relay, cnt, RELAY_STATE_OFF );
Delay_ms ( 200 );
}
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END