Deliver clear and efficient data representation with TLC59283 and STM32F103RB
Visualize data with ease!
Published Oct 08, 2024
Click board™
BarGraph 4 Click
Dev. board
Nucleo 64 with STM32F103RB MCU
Compiler
NECTO Studio
MCU
STM32F103RB
Captivate your audience with dynamic, attention-grabbing green bar graph that provide real-time insights and keep users engaged
A
A
Hardware Overview
How does it work?
BarGraph 4 Click is based on the TLC59283, a 16-channel, constant-current sink light-emitting diode (LED) driver from Texas Instruments. Each channel can be individually controlled with a simple serial communications protocol compatible with 3.3V or 5V logic levels, depending on the operating VCC. It also comes with a constant-current value of all 16 channels, determined by an external resistor R2 with a value of 2.2kΩ, limiting the current to 24mA. You can find the exact value of the current per channel, as well as the corresponding resistance value for a given current, in the attached datasheet. In the upper part on the front side of the board, marked with the characters A, B, C, and D, four green four-segment LED bar graph displays, the HLMP-2550 are placed. The Green HLMP-2500 series LEDs use
a liquid phase GaPepitaxial layer on a GaP substrate. These light bars are designed for various applications requiring a large bright light source, making this Click board™ suitable for creating different VU meters, status indicators, counters, and similar devices. The TLC59283 communicates with MCU using the standard SPI serial interface with a maximum frequency of 35MHz. It has a 16-bit shift register and an output ON/OFF data latch. Both shift register and data latch are 16 bits long and used to turn the constant-current outputs on and off. It also comes with one GPIO pin, routed on the RST pin of the mikroBUS™ socket, used to turn off all outputs during Power-On and output data latching to prevent unwanted image displays during these times. When the device is powered on, the data in the 16-bit shift register and output
on or off data latch are not set to default values. Therefore, the output ON/PFF data must be written to the data latch before turning the constant-current output ON. The RST pin should be high when powered on because the constant current may be turned ON due to random data in the output on or off data latch. 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 STM32F103RB 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-M3
MCU Memory (KB)
128
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
20480
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 STM32F103RB MCU 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 BarGraph 4 Click driver.
Key functions:
bargraph4_enable_output- This function enables all outputsbargraph4_set_output- This function sets all outputs to desired value by using SPI serial interfacebargraph4_set_channel_level- This function sets the level of a desired bar graph channel.
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 BarGraph4 Click example
*
* # Description
* This example demonstrates the use of BarGraph 4 click board.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and enables output.
*
* ## Application Task
* Changes the level of all bar graph channels every second.
* The channels level will be logged on the USB UART.
*
* @author Stefan Filipovic
*
*/
#include "board.h"
#include "log.h"
#include "bargraph4.h"
static bargraph4_t bargraph4;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
bargraph4_cfg_t bargraph4_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 );
Delay_ms( 100 );
log_info( &logger, " Application Init " );
// Click initialization.
bargraph4_cfg_setup( &bargraph4_cfg );
BARGRAPH4_MAP_MIKROBUS( bargraph4_cfg, MIKROBUS_1 );
err_t init_flag = bargraph4_init( &bargraph4, &bargraph4_cfg );
if ( SPI_MASTER_ERROR == init_flag )
{
log_error( &logger, " Application Init Error. " );
log_info( &logger, " Please, run program again... " );
for ( ; ; );
}
bargraph4_enable_output( &bargraph4 );
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
for ( bargraph4_level_t cnt = BARGRAPH4_LEVEL_0; cnt <= BARGRAPH4_LEVEL_4; cnt++ )
{
bargraph4_set_channel_level( &bargraph4, BARGRAPH4_CHANNEL_A, cnt );
bargraph4_set_channel_level( &bargraph4, BARGRAPH4_CHANNEL_B, cnt );
bargraph4_set_channel_level( &bargraph4, BARGRAPH4_CHANNEL_C, cnt );
bargraph4_set_channel_level( &bargraph4, BARGRAPH4_CHANNEL_D, cnt );
log_printf( &logger, " All channels set to level %u\r\n\n", ( uint16_t ) cnt );
Delay_ms( 1000 );
}
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
Additional Support
Resources
Category:LED Segment
