Skip to content

Latest commit

 

History

History

4dotmatrixr

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 
 
 
 
 
 
 
 
 

\mainpage Main Page


4Dot-Matrix R click

4Dot-Matrix R click is a display device Click board™, which contains a four-digit dot matrix display module, labeled as SLO2016.

click Product page


Click library

  • Author : MikroE Team
  • Date : May 2020.
  • Type : I2C type

Software Support

We provide a library for the c4dotmatrixr Click as well as a demo application (example), developed using MikroElektronika compilers. The demo can run on all the main MikroElektronika development boards.

Package can be downloaded/installed directly form compilers IDE(recommended way), or downloaded from our LibStock, or found on mikroE github account.

Library Description

This library contains API for c4dotmatrixr Click driver.

Standard key functions :

  • Config Object Initialization function.

void c4dotmatrixr_cfg_setup ( c4dotmatrixr_cfg_t *cfg );

  • Initialization function.

C4DOTMATRIXR_RETVAL c4dotmatrixr_init ( c4dotmatrixr_t *ctx, c4dotmatrixr_cfg_t *cfg );

  • Click Default Configuration function.

void c4dotmatrixr_default_cfg ( c4dotmatrixr_t *ctx );

Example key functions :

  • 4DotMatrix Char Write.

void c4dot_write_char ( c4dotmatrixr_t *ctx, uint8_t char_num, uint8_t char_value );

  • 4DotMatrix Char 0 Write.

void c4dot_write_char0 ( c4dotmatrixr_t *ctx, uint8_t char_value );

  • 4DotMatrix Text Write.

void c4dot_write_text ( c4dotmatrixr_t *ctx, uint8_t *text_to_write );

Examples Description

This example demonstrates the use of 4Dot-Matrix R click board.

The demo application is composed of two sections :

Application Init

Initializes the driver and performs the click default configuration.

void application_init ( void )
{
    log_cfg_t log_cfg;
    c4dotmatrixr_cfg_t cfg;

    /** 
     * 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.

    c4dotmatrixr_cfg_setup( &cfg );
    C4DOTMATRIXR_MAP_MIKROBUS( cfg, MIKROBUS_1 );
    c4dotmatrixr_init( &c4dotmatrixr, &cfg );
    
    c4dotmatrixr_default_cfg ( &c4dotmatrixr );
    log_info( &logger, "---- Application Task ----" );
}
  

Application Task

Displays a desired text message and then numbers from -20 to 20 on the click board. Each step will be logged on the USB UART where you can track the program flow.

void application_task ( void )
{
    int8_t i;
    log_printf( &logger, "------------------------------------\r\n" );
    log_printf( &logger, "Displaying \"Mikroelektronika\" on the click board...\r\n" );
    for ( i = 0; i < 20; i++ )
    {
        c4dot_write_text(  &c4dotmatrixr, text + i );
        Delay_ms ( 150 );
    }
        
    // Clear and delay.
    c4dot_clear_display( &c4dotmatrixr );
    Delay_ms ( 500 );
        
    log_printf( &logger, "Displaying all integer numbers from -20 to 20 on the click board...\r\n" );
    // Write some numbers on the display.
    for ( i = -20; i <= 20; i++ )
    {
        c4dot_write_int_dec( &c4dotmatrixr, i );
        Delay_ms ( 150 );
    }

    // Clear and delay.
    c4dot_clear_display( &c4dotmatrixr );
    Delay_ms ( 500 );
}  

The full application code, and ready to use projects can be installed directly form compilers IDE(recommneded) or found on LibStock page or mikroE GitHub accaunt.

Other mikroE Libraries used in the example:

  • MikroSDK.Board
  • MikroSDK.Log
  • Click.4dotmatrixr

Additional notes and informations

Depending on the development board you are using, you may need USB UART click, USB UART 2 Click or RS232 Click to connect to your PC, for development systems with no UART to USB interface available on the board. The terminal available in all Mikroelektronika compilers, or any other terminal application of your choice, can be used to read the message.