In our timer-controlled world, switch on time, every time. Our solution aligns control with the tick of the clock, providing you with seamless and reliable load management for a variety of applications.
A
A
Hardware Overview
How does it work?
Timer Relay Click is based on the NE5555, a precision timer from Diodes Incorporated. It works so that when the trigger is in a LOW logic state, it will start a delay regarding the threshold and then activate the relay. The TPL0501, a 256-tap single-channel digital potentiometer from Texas Instruments, determines the threshold. By setting a desired value on this digital potentiometer, you are setting a threshold on the NE5555 for the
delay. When you hit the onboard trigger button, you activate the relay regarding the delay you set by the digital potentiometer. Timer Relay Click uses a 3-wire SPI serial interface of the TPL0501 to allow the host MCU to set the threshold. Besides the trigger button, you can trigger the NE5555 over the TRG pin of the mikroBUS™ socket. When the timer hits the threshold and after delay activates the relay, it will also turn the TIMER LED
ON. The relay itself can withstand up to 10A and 220VAC/28VDC. 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 32 with STM32F031K6 MCU board provides an affordable and flexible platform for experimenting with STM32 microcontrollers in 32-pin packages. Featuring Arduino™ Nano connectivity, it allows easy expansion with specialized shields, while being mbed-enabled for seamless integration with online resources. The
board includes an on-board ST-LINK/V2-1 debugger/programmer, supporting USB reenumeration with three interfaces: Virtual Com port, mass storage, and debug port. It offers a flexible power supply through either USB VBUS or an external source. Additionally, it includes three LEDs (LD1 for USB communication, LD2 for power,
and LD3 as a user LED) and a reset push button. The STM32 Nucleo-32 board is supported by various Integrated Development Environments (IDEs) such as IAR™, Keil®, and GCC-based IDEs like AC6 SW4STM32, making it a versatile tool for developers.
Microcontroller Overview
MCU Card / MCU
Architecture
ARM Cortex-M0
MCU Memory (KB)
32
Silicon Vendor
STMicroelectronics
Pin count
32
RAM (Bytes)
4096
You complete me!
Accessories
Click Shield for Nucleo-32 is the perfect way to expand your development board's functionalities with STM32 Nucleo-32 pinout. The Click Shield for Nucleo-32 provides two mikroBUS™ sockets to add any functionality from our ever-growing range of Click boards™. We are fully stocked with everything, from sensors and WiFi transceivers to motor control and audio amplifiers. The Click Shield for Nucleo-32 is compatible with the STM32 Nucleo-32 board, providing an affordable and flexible way for users to try out new ideas and quickly create prototypes with any STM32 microcontrollers, choosing from the various combinations of performance, power consumption, and features. The STM32 Nucleo-32 boards do not require any separate probe as they integrate the ST-LINK/V2-1 debugger/programmer and come with the STM32 comprehensive software HAL library and various packaged software examples. This development platform provides users with an effortless and common way to combine the STM32 Nucleo-32 footprint compatible board with their favorite Click boards™ in their upcoming projects.
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
This Click board can be interfaced and monitored in two ways:
Application Output
- Use the "Application Output" window in Debug mode for real-time data monitoring. Set it up properly by following this tutorial.
UART Terminal
- Monitor data via the UART Terminal using a USB to UART converter. For detailed instructions, check out this tutorial.
Software Support
Library Description
This library contains API for Timer Relay Click driver.
Key functions:
timerrelay_set_wiper_pos
- Timer Relay set wiper position function.timerrelay_activate_reset
- Timer Relay reset timer function.timerrelay_activate_trigger
- Timer Relay activate trigger 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 Timer Relay Click example
*
* # Description
* This example demonstrates the use of the Timer Relay Click board by
* setting the relay timer to 2 seconds ON time, then holding it OFF for 2 more seconds.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and performs the click default configuration,
* then setting the ON time to 2 seconds.
*
* ## Application Task
* This example is activating the trigger every 4 seconds activating the relay timer.
*
* @author Stefan Ilic
*
*/
#include "board.h"
#include "log.h"
#include "timerrelay.h"
static timerrelay_t timerrelay;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
timerrelay_cfg_t timerrelay_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.
timerrelay_cfg_setup( &timerrelay_cfg );
TIMERRELAY_MAP_MIKROBUS( timerrelay_cfg, MIKROBUS_1 );
if ( SPI_MASTER_ERROR == timerrelay_init( &timerrelay, &timerrelay_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
if ( TIMERRELAY_ERROR == timerrelay_default_cfg ( &timerrelay ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
if ( TIMERRELAY_ERROR == timerrelay_set_delay( &timerrelay, 2 ) )
{
log_error( &logger, " Value configuration." );
for ( ; ; );
}
timerrelay_activate_reset( &timerrelay );
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
timerrelay_activate_trigger( &timerrelay );
log_printf( &logger, " Trigger activated. \r\n" );
Delay_ms( 4000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END