Control and monitor four separate loads simultaneously with the 9913-05-20TR and EasyMx PRO v7 for Tiva MCU card with TM4C123GH6PMI
Four high-performance SMD reed relays with high switching capabilities
Published May 21, 2024
Click board™
Relay 6 Click
Dev. board
EasyMx PRO v7 for Tiva
Compiler
NECTO Studio
MCU
TM4C123GH6PMI
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
EasyMx PRO v7 for TIVA is the seventh generation of ARM development boards specially designed for the needs of rapid development of embedded applications. It supports a wide range of 32-bit ARM microcontrollers from Texas Instruments and a broad set of unique functions, such as a powerful onboard mikroProg programmer and In-Circuit debugger over USB-B. 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. With two different connectors for each port, EasyMx PRO v7 for TIVA allows you to connect accessory boards, sensors, and custom electronics more efficiently than ever. Each part of the EasyMx
PRO v7 for TIVA development board contains the components necessary for the most efficient operation of the same board. An integrated mikroProg, a fast USB 2.0 programmer with mikroICD hardware In-Circuit Debugger, offers many valuable programming/debugging options and seamless integration with the Mikroe software environment. Besides it also includes a clean and regulated power supply block for the development board. It can use a wide range of external power sources, including an external 12V power supply, 7-23V AC or 9-32V DC via DC connector/screw terminals, and a power source via the USB Type-B (USB-B) connector. Communication options such as USB-UART, USB-HOST/DEVICE, CAN, and
Ethernet are also included, including the well-established mikroBUS™ standard, one display option for the TFT board line of products, and a standard TQFP socket for the seventh-generation MCU cards. This socket covers a wide range of 32-bit TIVA-series ARM Cortex-M4 MCUs. EasyMx PRO v7 for TIVA 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
Type
7th Generation
Architecture
ARM Cortex-M4
MCU Memory (KB)
256
Silicon Vendor
Texas Instruments
Pin count
64
RAM (Bytes)
32k
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 EasyMx PRO v7 for Tiva 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 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
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 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
