Display status information in a clear and intuitive manner with HLMP-2685 and ATmega324P
Red LED bargraph display for clear and effective visual data representation
Published Oct 30, 2024
Click board™
BarGraph 5 Click
Dev Board
EasyAVR v7
Compiler
NECTO Studio
MCU
ATmega324P
Visually indicate network status, signal strength, or show messages or alerts using a bargraph format
A
A
Hardware Overview
How does it work?
BarGraph 5 Click is based on three HLMP-2685 red LED bargraph displays from Broadcom Limited controlled by the TLC5947, a 12-bit PWM LED driver with an internal oscillator from Texas Instruments. These rectangular red light bars are housed in single-in-line packages, making them perfect for various industrial and commercial applications. Each lighting segment delivers a typical luminous intensity of 83.4mcd, with a peak wavelength of 626nm, ensuring high visibility. This Click board™ is ideal for applications requiring a large, bright, uniform light source, such as typical bargraph displays, front panel process status
indicators, telecommunications equipment, machine message annunciators, and many other scenarios where clear and reliable visual feedback is needed. The TLC5947 that controls these bars communicates with the host MCU through an SPI serial interface with a maximum clock frequency of up to 30MHz. In addition to the SPI communication signals, the board uses the BLK pin from the mikroBUS™ socket, functioning as a blanking control. When the BLK pin is set to a HIGH logic level, all bargraphs are turned OFF, and when it's LOW, the bargraphs are activated. The board also includes a 2kΩ IREF resistor that sets the current
for the TLC5947's LED driver channels. This resistor ensures that the current for the bargraph LEDs is regulated at approximately 20mA, providing consistent brightness across the displays. 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
EasyAVR v7 is the seventh generation of AVR development boards specially designed for the needs of rapid development of embedded applications. It supports a wide range of 16-bit AVR microcontrollers from Microchip and has a broad set of unique functions, such as a powerful onboard mikroProg programmer and In-Circuit debugger over USB. The development board is well organized and designed so that the end-user has all the necessary elements in one place, such as switches, buttons, indicators, connectors, and others. With four different connectors for each port, EasyAVR v7 allows you to connect accessory boards, sensors, and custom electronics more
efficiently than ever. Each part of the EasyAVR v7 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-12V AC or 9-15V DC via DC connector/screw terminals, and a power source via the USB Type-B (USB-B)
connector. Communication options such as USB-UART and RS-232 are also included, alongside the well-established mikroBUS™ standard, three display options (7-segment, graphical, and character-based LCD), and several different DIP sockets which cover a wide range of 16-bit AVR MCUs. EasyAVR v7 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
Architecture
AVR
MCU Memory (KB)
32
Silicon Vendor
Microchip
Pin count
40
RAM (Bytes)
2048
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 EasyAVR v7 as your development board.
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 BarGraph 5 Click driver.
Key functions:
bargraph5_set_bar_level- This function sets the level of a selected BarGraph channel at the selected brightness.bargraph5_output_enable- This function enables the BarGraph LEDs output by setting the BLANK pin to low logic state.bargraph5_output_disable- This function disables the BarGraph LEDs output by setting the BLANK pin to high logic state.
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 BarGraph 5 Click example
*
* # Description
* This example demonstrates the use of BarGraph 5 click board by changing
* the level of all BarGraph output channels.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and performs the click default configuration.
*
* ## Application Task
* Changes the level of all BarGraph channels once per second.
* The channels level is displayed on the USB UART.
*
* @author Stefan Filipovic
*
*/
#include "board.h"
#include "log.h"
#include "bargraph5.h"
static bargraph5_t bargraph5;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
bargraph5_cfg_t bargraph5_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.
bargraph5_cfg_setup( &bargraph5_cfg );
BARGRAPH5_MAP_MIKROBUS( bargraph5_cfg, MIKROBUS_1 );
if ( SPI_MASTER_ERROR == bargraph5_init( &bargraph5, &bargraph5_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
if ( BARGRAPH5_ERROR == bargraph5_default_cfg ( &bargraph5 ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
for ( bargraph5_level_t cnt = BARGRAPH5_LEVEL_0; cnt <= BARGRAPH5_LEVEL_4; cnt++ )
{
bargraph5_set_bar_level ( &bargraph5, BARGRAPH5_BAR_0, cnt, BARGRAPH5_BRIGHTNESS_DEFAULT );
bargraph5_set_bar_level ( &bargraph5, BARGRAPH5_BAR_1, BARGRAPH5_LEVEL_4 - cnt, BARGRAPH5_BRIGHTNESS_DEFAULT );
bargraph5_set_bar_level ( &bargraph5, BARGRAPH5_BAR_2, cnt, BARGRAPH5_BRIGHTNESS_DEFAULT );
bargraph5_set_bar_level ( &bargraph5, BARGRAPH5_BAR_3, BARGRAPH5_LEVEL_4 - cnt, BARGRAPH5_BRIGHTNESS_DEFAULT );
bargraph5_set_bar_level ( &bargraph5, BARGRAPH5_BAR_4, cnt, BARGRAPH5_BRIGHTNESS_DEFAULT );
bargraph5_set_bar_level ( &bargraph5, BARGRAPH5_BAR_5, BARGRAPH5_LEVEL_4 - cnt, BARGRAPH5_BRIGHTNESS_DEFAULT );
log_printf( &logger, " Bars 0-2-4 level: %u\r\n", ( uint16_t ) cnt );
log_printf( &logger, " Bars 1-3-5 level: %u\r\n\n", ( uint16_t ) ( BARGRAPH5_LEVEL_4 - cnt ) );
Delay_ms ( 1000 );
}
}
int main ( void )
{
/* Do not remove this line or clock might not be set correctly. */
#ifdef PREINIT_SUPPORTED
preinit();
#endif
application_init( );
for ( ; ; )
{
application_task( );
}
return 0;
}
// ------------------------------------------------------------------------ END
