Achieve precise load control with LCA717 and STM32F215RE
Elevate your control: Unleash the power of solid-state relays!
Published Oct 18, 2023
Click board™
Relay2 Click
Dev Board
UNI Clicker
Compiler
NECTO Studio
MCU
STM32F215RE
Our solid-state relay solution is designed to enhance your electrical control with efficiency and reliability, making it ideal for a wide range of applications
A
A
Hardware Overview
How does it work?
Relay 2 Click is based on two LCA717s, single-pole, normally open OptoMos relays from IXYSIC. These SSRs are normally open, meaning no current flows through the output terminals if no power is applied at the input - the output stage is in an open circuit state. The LCA717 itself is built with the patented OptoMOS® technology, which allows for a reasonably fast switching time to be achieved by the output stage. The input stage of the device is comprised of a highly efficient GaAIAs infrared
LED, used to drive the photovoltaic elements of the SSR. The output stage has two N-type MOSFETs, which allow both DC and AC to be switched to the output stage. The input and output stages are galvanically isolated with up to 3.5kV of breakdown voltage. Relay 2 Click uses two GPIO pins to allow the host MCU to control the relays. Those pins are labeled RL1 and RL2, and the relays are activated by writing the High logic on those pins. At the same time the relays are
activated, two LEDs (REL1, REL2) will indicate the relays states. The load can be connected to Relay 2 Click over the screw terminals. 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. However, the Click board™ 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
UNI Clicker is a compact development board designed as a complete solution that brings the flexibility of add-on Click boards™ to your favorite microcontroller, making it a perfect starter kit for implementing your ideas. It supports a wide range of microcontrollers, such as different ARM, PIC32, dsPIC, PIC, and AVR from various vendors like Microchip, ST, NXP, and TI (regardless of their number of pins), four mikroBUS™ sockets for Click board™ connectivity, a USB connector, LED indicators, buttons, a debugger/programmer connector, and two 26-pin headers for interfacing with external electronics. Thanks to innovative manufacturing technology, it allows you to build
gadgets with unique functionalities and features quickly. Each part of the UNI Clicker development kit contains the components necessary for the most efficient operation of the same board. In addition to the possibility of choosing the UNI Clicker programming method, using a third-party programmer or CODEGRIP/mikroProg connected to onboard JTAG/SWD header, the UNI Clicker board also includes a clean and regulated power supply module for the development kit. It provides two ways of board-powering; through the USB Type-C (USB-C) connector, where onboard voltage regulators provide the appropriate voltage levels to each component on the board, or using a Li-Po/Li
Ion battery via an onboard battery connector. All communication methods that mikroBUS™ itself supports are on this board (plus USB HOST/DEVICE), including the well-established mikroBUS™ socket, a standardized socket for the MCU card (SiBRAIN standard), and several user-configurable buttons and LED indicators. UNI Clicker 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
Type
8th Generation
Architecture
ARM Cortex-M3
MCU Memory (KB)
512
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
131072
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Schematic
Step by step
Project assembly
Start by selecting your development board and Click board™. Begin with the UNI Clicker as your development board.
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.
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™.
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.
Software Support
Library Description
This library contains API for Relay2 Click driver.
Key functions:
relay2_relay2Control- Controls the Relay 2 pinrelay2_relay1Control- Controls the Relay 1 pin
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 Relay 2 Click example
*
* # Description
* The application is composed of three sections :
*
* ## Application Init
* Initializes driver.
*
* ## Application Task
* Turns relays on and off.
*
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "relay2.h"
// ------------------------------------------------------------------ VARIABLES
static relay2_t relay2;
static log_t logger;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
relay2_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.
relay2_cfg_setup( &cfg );
RELAY2_MAP_MIKROBUS( cfg, MIKROBUS_1 );
relay2_init( &relay2, &cfg );
log_info( &logger, "---- App Init Done ----" );
}
void application_task ( void )
{
relay2_relay2_control(&relay2, 1 );
relay2_relay1_control(&relay2, 1 );
Delay_ms( 1000 );
relay2_relay2_control(&relay2, 0 );
relay2_relay1_control(&relay2, 0 );
Delay_ms( 1000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
