Control and monitor four separate loads simultaneously with the 9913-05-20TR and STM32G474RE
Four high-performance SMD reed relays with high switching capabilities
Published Nov 08, 2024
Click board™
Relay 6 Click
Dev Board
Nucleo 64 with STM32G474RE MCU
Compiler
NECTO Studio
MCU
STM32G474RE
Accurately manage four individual loads in automated test equipment, instrumentation, and telecommunications applications.
A
A
Hardware Overview
How does it work?
Relay 6 Click is based on the 9913-05-20TR, a reed relay from Coto Technology, a component known for its ultra-miniature SMD design, standing for the smallest footprint in the market. This Click board™ features four relays, each equipped with four terminals for load connections that are controlled via these relays. Beneath each relay is a blue LED indicator that illuminates to signal when the relay is active, serving as an operational status indicator. This setup provides clear and immediate feedback on the status of each relay, enhancing user control and system monitoring. This Click board™ is ideal for automated test equipment, instrumentation, and telecommunications applications, highlighting high reliability and long
life due to relays hermetically sealed contacts. The 9913-05-20TRs also feature a high insulation resistance of a minimum of 1011Ω and an external magnetic shield. Its electrical specifications include a coil voltage of 5VDC, a coil resistance of 200Ω, a single-pole single-throw normally open (SPST-NO, 1 Form A) contact form, with the contact current rating capped at 250mA and the switching voltage limited to 100VAC and 100VDC. Control and communication between the relays and the host MCU are managed via the PCA9538A port expander, which uses an I2C communication interface. This device supports both Standard and Fast modes, with frequencies up to 400kHz. The PCA9538A's I2C address can be configured
through the ADDR SEL jumpers, allowing flexible integration with various MCU systems. The PCA9538A also uses an RST pin that ensures the registers and I2C-bus state machine remain in their default settings until this pin is set to a HIGH logic state, where the device returns to normal operational status. This Click board™ can operate with either 3.3V or 5V logic voltage levels selected via the VCC SEL jumper. This way, both 3.3V and 5V capable MCUs can use the communication lines properly. Also, this Click board™ comes equipped with a library containing easy-to-use functions and an example code that can be used as a reference for further development.
Features overview
Development board
Nucleo-64 with STM32G474R MCU offers a cost-effective and adaptable platform for developers to explore new ideas and prototype their designs. This board harnesses the versatility of the STM32 microcontroller, enabling users to select the optimal balance of performance and power consumption for their projects. It accommodates the STM32 microcontroller in the LQFP64 package and includes essential components such as a user LED, which doubles as an ARDUINO® signal, alongside user and reset push-buttons, and a 32.768kHz crystal oscillator for precise timing operations. Designed with expansion and flexibility in mind, the Nucleo-64 board features an ARDUINO® Uno V3 expansion connector and ST morpho extension pin
headers, granting complete access to the STM32's I/Os for comprehensive project integration. Power supply options are adaptable, supporting ST-LINK USB VBUS or external power sources, ensuring adaptability in various development environments. The board also has an on-board ST-LINK debugger/programmer with USB re-enumeration capability, simplifying the programming and debugging process. Moreover, the board is designed to simplify advanced development with its external SMPS for efficient Vcore logic supply, support for USB Device full speed or USB SNK/UFP full speed, and built-in cryptographic features, enhancing both the power efficiency and security of projects. Additional connectivity is
provided through dedicated connectors for external SMPS experimentation, a USB connector for the ST-LINK, and a MIPI® debug connector, expanding the possibilities for hardware interfacing and experimentation. Developers will find extensive support through comprehensive free software libraries and examples, courtesy of the STM32Cube MCU Package. This, combined with compatibility with a wide array of Integrated Development Environments (IDEs), including IAR Embedded Workbench®, MDK-ARM, and STM32CubeIDE, ensures a smooth and efficient development experience, allowing users to fully leverage the capabilities of the Nucleo-64 board in their projects.
Microcontroller Overview
MCU Card / MCU
Architecture
ARM Cortex-M4
MCU Memory (KB)
512
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
128k
You complete me!
Accessories
Click Shield for Nucleo-64 comes equipped with two proprietary mikroBUS™ sockets, allowing all the Click board™ devices to be interfaced with the STM32 Nucleo-64 board with no effort. This way, Mikroe allows its users to add any functionality from our ever-growing range of Click boards™, such as WiFi, GSM, GPS, Bluetooth, ZigBee, environmental sensors, LEDs, speech recognition, motor control, movement sensors, and many more. More than 1537 Click boards™, which can be stacked and integrated, are at your disposal. The STM32 Nucleo-64 boards are based on the microcontrollers in 64-pin packages, a 32-bit MCU with an ARM Cortex M4 processor operating at 84MHz, 512Kb Flash, and 96KB SRAM, divided into two regions where the top section represents the ST-Link/V2 debugger and programmer while the bottom section of the board is an actual development board. These boards are controlled and powered conveniently through a USB connection to program and efficiently debug the Nucleo-64 board out of the box, with an additional USB cable connected to the USB mini port on the board. Most of the STM32 microcontroller pins are brought to the IO pins on the left and right edge of the board, which are then connected to two existing mikroBUS™ sockets. This Click Shield also has several switches that perform functions such as selecting the logic levels of analog signals on mikroBUS™ sockets and selecting logic voltage levels of the mikroBUS™ sockets themselves. Besides, the user is offered the possibility of using any Click board™ with the help of existing bidirectional level-shifting voltage translators, regardless of whether the Click board™ operates at a 3.3V or 5V logic voltage level. Once you connect the STM32 Nucleo-64 board with our Click Shield for Nucleo-64, you can access hundreds of Click boards™, working with 3.3V or 5V logic voltage levels.
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 Nucleo 64 with STM32G474RE MCU as your development board.
Track your results in real time
Application Output via Debug Mode
1. Once the code example is loaded, pressing the "DEBUG" button initiates the build process, programs it on the created setup, and enters Debug mode.
2. After the programming is completed, a header with buttons for various actions within the IDE becomes visible. Clicking the green "PLAY" button starts reading the results achieved with the Click board™. The achieved results are displayed in the Application Output tab.
Software Support
Library Description
This library contains API for Relay 6 Click driver.
Key functions:
relay6_reset_port_expander- Relay 6 reset port expander function.relay6_port_expander_write- Relay 6 port expander write register function.relay6_set_relay- Relay 6 set relay state 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 main.c
* @brief Relay 6 Click example
*
* # Description
* This example demonstrates the use of Relay 6 click board by toggling the relays state.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and logger.
*
* ## Application Task
* Switches all relays state every second and displays the state on the USB UART.
*
* @author Stefan Ilic
*
*/
#include "board.h"
#include "log.h"
#include "relay6.h"
static relay6_t relay6;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
relay6_cfg_t relay6_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.
relay6_cfg_setup( &relay6_cfg );
RELAY6_MAP_MIKROBUS( relay6_cfg, MIKROBUS_1 );
if ( I2C_MASTER_ERROR == relay6_init( &relay6, &relay6_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
if ( RELAY6_ERROR == relay6_default_cfg ( &relay6 ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
uint8_t relay_data;
relay_data = RELAY6_RELAY1_PIN;
log_printf( &logger, " Turning on only Relay 1 \r\n" );
log_printf( &logger, " = = = = = = = = = = = = = \r\n" );
relay6_set_relay( &relay6, relay_data, ~relay_data );
relay_data <<= 1;
Delay_ms( 1000 );
log_printf( &logger, " Turning on only Relay 2 \r\n" );
log_printf( &logger, " = = = = = = = = = = = = = \r\n" );
relay6_set_relay( &relay6, relay_data, ~relay_data );
relay_data <<= 1;
Delay_ms( 1000 );
log_printf( &logger, " Turning on only Relay 3 \r\n" );
log_printf( &logger, " = = = = = = = = = = = = = \r\n" );
relay6_set_relay( &relay6, relay_data, ~relay_data );
relay_data <<= 1;
Delay_ms( 1000 );
log_printf( &logger, " Turning on only Relay 4 \r\n" );
log_printf( &logger, " = = = = = = = = = = = = = \r\n" );
relay6_set_relay( &relay6, relay_data, ~relay_data );
relay_data <<= 1;
Delay_ms( 1000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
