Compact time-tracking solution that maintains accurate time records, suitable for applications like IoT, wearables, data logging, and industrial devices
A
A
Hardware Overview
How does it work?
RTC 2 Click is based on the DS1307, a 64x8 serial I2C Real-Time clock from Analog Devices. It is a low-power, full binary-coded decimal (BCD) clock/calendar with 56 bytes of NV SRAM. The end of months is automatically adjusted for months with fewer than 31 days, including corrections for the leap year. The clock can operate in either a 24-hour or 12-hour format with an AM/PM indicator. The RTC has a built-in power-sense circuit that automatically switches to the backup power
supply when it detects a power failure. The RTC 2 comes equipped with a 3V/230mA lithium battery, ensuring timekeeping continues even when the main power supply goes OFF. The RTC 2 Click uses an I2C 2-Wire interface for communication with the host MCU, with a clock rate of up to 400kHz. The interrupt INT pin of this Click board™ outputs one of four square-wave frequencies (1Hz, 4kHz, 8kHz, and 32kHz). When enabled, it outputs frequency depending on values set in configuration
bits. 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, 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
PIC18F57Q43 Curiosity Nano evaluation kit is a cutting-edge hardware platform designed to evaluate microcontrollers within the PIC18-Q43 family. Central to its design is the inclusion of the powerful PIC18F57Q43 microcontroller (MCU), offering advanced functionalities and robust performance. Key features of this evaluation kit include a yellow user LED and a responsive
mechanical user switch, providing seamless interaction and testing. The provision for a 32.768kHz crystal footprint ensures precision timing capabilities. With an onboard debugger boasting a green power and status LED, programming and debugging become intuitive and efficient. Further enhancing its utility is the Virtual serial port (CDC) and a debug GPIO channel (DGI
GPIO), offering extensive connectivity options. Powered via USB, this kit boasts an adjustable target voltage feature facilitated by the MIC5353 LDO regulator, ensuring stable operation with an output voltage ranging from 1.8V to 5.1V, with a maximum output current of 500mA, subject to ambient temperature and voltage constraints.
Microcontroller Overview
MCU Card / MCU
Architecture
PIC
MCU Memory (KB)
128
Silicon Vendor
Microchip
Pin count
48
RAM (Bytes)
8196
You complete me!
Accessories
Curiosity Nano Base for Click boards is a versatile hardware extension platform created to streamline the integration between Curiosity Nano kits and extension boards, tailored explicitly for the mikroBUS™-standardized Click boards and Xplained Pro extension boards. This innovative base board (shield) offers seamless connectivity and expansion possibilities, simplifying experimentation and development. Key features include USB power compatibility from the Curiosity Nano kit, alongside an alternative external power input option for enhanced flexibility. The onboard Li-Ion/LiPo charger and management circuit ensure smooth operation for battery-powered applications, simplifying usage and management. Moreover, the base incorporates a fixed 3.3V PSU dedicated to target and mikroBUS™ power rails, alongside a fixed 5.0V boost converter catering to 5V power rails of mikroBUS™ sockets, providing stable power delivery for various connected devices.
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Schematic
Step by step
Project assembly
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 RTC 2 Click driver.
Key functions:
rtc2_read_byte
- Generic read byte of data functionrtc2_write_byte
- Generic write byte of data functionrtc2_enable_counting
- Enable counting 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
* \brief Rtc2 Click example
*
* # Description
* This application give time and date information.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initialization driver enable's - I2C,set start time and date, enable counting and start write log.
*
* ## Application Task
* This is a example which demonstrates the use of RTC 2 Click board.
* RTC 2 Click communicates with register via I2C by write to register and read from register,
* set time and date, get time and date, enable and disable counting
* and set frequency by write configuration register.
* Results are being sent to the Usart Terminal where you can track their changes.
* All data logs write on usb uart changes for every 1 sec.
*
* *note:*
* Additional Functions :
*
* - void displayDayOfTheWeek( uint8_t dayOfTheWeek ) - Write day of the week log on USART terminal.
* - void displayLogUart( uint8_t value ) - Write the value ( time or date ) of a two-digit number.
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "rtc2.h"
// ------------------------------------------------------------------ VARIABLES
static rtc2_t rtc2;
static log_t logger;
static rtc2_data_t date;
uint8_t time_hours;
uint8_t time_minutes;
uint8_t time_seconds;
uint8_t day_of_the_week;
uint8_t date_day;
uint8_t date_month;
uint16_t date_year;
uint8_t time_seconds_new = 0;
void display_day_of_the_week ( uint8_t day_of_the_week )
{
if ( day_of_the_week == 1 )
{
log_printf( &logger, " Monday " );
}
if ( day_of_the_week == 2 )
{
log_printf( &logger, " Tuesday " );
}
if ( day_of_the_week == 3 )
{
log_printf( &logger, " Wednesday " );
}
if ( day_of_the_week == 4 )
{
log_printf( &logger, " Thursday " );
}
if ( day_of_the_week == 5 )
{
log_printf( &logger, " Friday " );
}
if ( day_of_the_week == 6 )
{
log_printf( &logger, " Saturday " );
}
if ( day_of_the_week == 7 )
{
log_printf( &logger, " Sunday " );
}
}
void display_log_uart ( uint8_t value )
{
log_printf( &logger,"%u", ( uint16_t )( value / 10 ) );
log_printf( &logger,"%u", ( uint16_t )( value % 10 ) );
}
void application_init ( void )
{
log_cfg_t log_cfg;
rtc2_cfg_t cfg;
date.day_of_the_week = 1;
date.date_day = 31;
date.date_month = 12;
date.date_year = 2018;
/**
* 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.
rtc2_cfg_setup( &cfg );
RTC2_MAP_MIKROBUS( cfg, MIKROBUS_1 );
rtc2_init( &rtc2, &cfg );
rtc2_set_time( &rtc2, 23, 59, 50 );
rtc2_set_date( &rtc2, &date );
rtc2_enable_counting( &rtc2 );
}
void application_task ( void )
{
rtc2_get_time( &rtc2, &time_hours, &time_minutes, &time_seconds );
rtc2_get_date( &rtc2, &date );
if ( time_seconds_new != time_seconds )
{
log_printf( &logger, " Time : " );
display_log_uart( time_hours );
log_printf( &logger, ":" );
display_log_uart( time_minutes );
log_printf( &logger, ":" );
display_log_uart( time_seconds );
log_printf( &logger, "" );
display_day_of_the_week( date.day_of_the_week );
log_printf( &logger, " Date: " );
display_log_uart( date.date_day );
log_printf( &logger, "." );
display_log_uart( date.date_month );
log_printf( &logger, "." );
log_printf( &logger, "20" );
display_log_uart( date.date_year );
log_printf( &logger, ".\r\n" );
log_printf( &logger, "-------------------\r\n" );
time_seconds_new = time_seconds;
}
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
Additional Support
Resources
Category:RTC