Intermediate
20 min

Elevate your remote monitoring capabilities with 32001345 and STM32F031K6

Stay connected, no matter the distance - 868MHz transceivers at your service

LR 3 Click with Nucleo 32 with STM32F031K6 MCU

Published Oct 01, 2024

Click board™

LR 3 Click

Dev. board

Nucleo 32 with STM32F031K6 MCU

Compiler

NECTO Studio

MCU

STM32F031K6

Our 868MHz long-range transceiver is designed to empower your projects with seamless, low-power, and long-distance connectivity, making it ideal for remote monitoring and IoT applications.

A

A

Hardware Overview

How does it work?

LR 3 Click is based on the 32001345, a low-power, long-range RF technology-based transceiver module from Mipot. It offers a long-range spread spectrum communication with high interference immunity. The network is implemented as a star topology, where endpoints work in duty cycle mode, significantly reducing the overall power consumption. Coupled with the AES128 message encryption and low current consumption, LR 3 Click offers an easy and reliable solution for developing low-power, highly integrated IoT networks, security systems, alarm networks, and similar applications that require simple and reliable networking solutions. This Click board™ can be configured as either END or MASTER NODE, using simple AT commands. While working as the MASTER NODE, the Click board™

can use a set of master-specific commands, such as the pairing command. This command will add the end node, which requested pairing, to the master network table. While working as the END NODE, LR 3 Click can issue slave-specific commands/requests, such as the pairing request command, allowing that end node to be paired with the master. LR 3 Click communicates with MCU using the UART interface with commonly used UART RX and TX pins at data rates up to 115200bps for data transfer. In addition to these features, the 32001345 also uses several GPIO pins connected to the mikroBUS™ socket. The WK pin routed on the CS pin of the mikroBUS™ represents the Wake-up function used for waking up the device, while the RST pin on the mikroBUS™ socket can perform a Hardware Reset

function by putting this pin in a logic low state. This Click board™ also has an indicator routed on the INT pin of the mikroBUS ™ socket, which will provide the user with feedback after a successfully received package and verified checksum. LR 3 Click features the SMA antenna connector with an impedance of 50Ω, so it can be equipped with the appropriate 868MHz compliant antenna that MIKROE offers. 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.

LR 3 Click hardware overview image

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.

Nucleo 32 with STM32F031K6 MCU double side image

Microcontroller Overview

MCU Card / MCU

default

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.

Click Shield for Nucleo-32 accessories 1 image

868MHz right-angle rubber antenna is a compact and versatile solution for wireless communication. Operating within the frequency range of 868-915MHz, it ensures optimal signal reception and transmission. With a 50-ohm impedance, it's compatible with various devices and systems. This antenna boasts a 2dB gain, enhancing signal strength and extending communication range. Its vertical polarization further contributes to signal clarity. Designed to handle up to 50W of input power, it's a robust choice for various applications. Measuring just 48mm in length, this antenna is both discreet and practical. Its SMA male connector ensures a secure and reliable connection to your equipment. Whether you're working with IoT devices, remote sensors, or other wireless technologies, the 868MHz right-angle antenna offers the performance and flexibility you need for seamless communication.

LR 3 Click accessories image

Used MCU Pins

mikroBUS™ mapper

NC
NC
AN
Reset
PA11
RST
Wake up
PA4
CS
NC
NC
SCK
NC
NC
MISO
NC
NC
MOSI
Power supply
3.3V
3.3V
Ground
GND
GND
NC
NC
PWM
Data TX indication
PA12
INT
UART TX
PA10
TX
UART RX
PA9
RX
NC
NC
SCL
NC
NC
SDA
Power supply
5V
5V
Ground
GND
GND
1

Take a closer look

Click board™ Schematic

LR 3 Click Schematic schematic

Step by step

Project assembly

Click Shield for Nucleo-144 front image hardware assembly

Start by selecting your development board and Click board™. Begin with the Nucleo 32 with STM32F031K6 MCU as your development board.

Click Shield for Nucleo-144 front image hardware assembly
Nucleo 144 with STM32L4A6ZG MCU front image hardware assembly
Stepper 22 Click front image hardware assembly
Prog-cut hardware assembly
Stepper 22 Click complete accessories setup image hardware assembly
Nucleo-32 with STM32 MCU Access MB 1 - upright/background hardware assembly
Necto image step 2 hardware assembly
Necto image step 3 hardware assembly
Necto image step 4 hardware assembly
Necto image step 5 hardware assembly
Necto image step 6 hardware assembly
STM32 M4 Clicker HA MCU/Select Step hardware assembly
Necto No Display image step 8 hardware assembly
Necto image step 9 hardware assembly
Necto image step 10 hardware assembly
Debug Image Necto Step hardware assembly

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 LR 3 Click driver.

Key functions:

  • lr3_factory_reset - Function performs the recovery of EEPROM default values.

  • lr3_write_eeprom - Function writes data to EEPROM.

  • lr3_tx_message - Function performs the transmission of radio frames.

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 
 * \brief LR3 Click example
 * 
 * # Description
 * This example reads and processes data from LR 3 clicks.
 *
 * The demo application is composed of two sections :
 * 
 * ## Application Init 
 * Initializes the driver, enables the click board and configures it for the selected mode.
 * 
 * ## Application Task  
 * Depending on the selected mode, it reads all the received data or sends a desired message
 * every 3 seconds. All data is being displayed on the USB UART.
 * 
 * ## Additional Function
 * - indication_handler - Logs results on USB UART when device gets indication status.
 * 
 * \author MikroE Team
 *
 */
// ------------------------------------------------------------------- INCLUDES

#include "board.h"
#include "log.h"
#include "lr3.h"
#include "string.h"

// ------------------------------------------------------------------ VARIABLES

#define MASTER
// #define END_NODE

#define TEXT_TO_SEND "MikroE"

static lr3_t lr3;
static lr3_tx_msg_t lr3_tx_msg;
static log_t logger;

static lr3_message_t tmp_msg;

// -------------------------------------------------------- ADDITIONAL FUNCTIONS

static void indication_handler( uint8_t *cmd, uint8_t *pl_size, uint8_t *pl_buffer )
{
    if ( *cmd == LR3_INDICATES_RX_MSG )
    {
        if ( pl_buffer[ 0 ] == 0x00 )
        {
            log_printf( &logger, "Message received!\r\n" );
            int16_t rssi = ( pl_buffer[ 2 ] << 8 ) | pl_buffer[ 1 ];
            log_printf( &logger, "RSSI in dBm: %d\r\n", rssi );
            log_printf( &logger, "Signal-to-Noise Ratio: %u\r\n", ( uint16_t ) pl_buffer[ 3 ] );
            log_printf( &logger, "Source ID: 0x%.2X%.2X%.2X%.2X\r\n", ( uint16_t ) pl_buffer[ 7 ],
                                                                      ( uint16_t ) pl_buffer[ 6 ],
                                                                      ( uint16_t ) pl_buffer[ 5 ],
                                                                      ( uint16_t ) pl_buffer[ 4 ] );
            log_printf( &logger, "Message content: " );
            for ( uint8_t cnt = 8; cnt < *pl_size; cnt++ )
            {
                log_printf( &logger, "%c", ( uint16_t ) pl_buffer[ cnt ] );
            }
            log_printf( &logger, "\r\nChecksum: %u", ( uint16_t ) pl_buffer[ *pl_size ] );
            log_printf( &logger, "\r\n------------------------\r\n" );
        }
        else
        {
            log_printf( &logger, "Error!\r\n" );
        }
    }
    else
    {
        log_printf( &logger, "IND TYPE: 0x%.2X\r\n", ( uint16_t ) *cmd );
        log_printf( &logger, "PAYLOAD : " );
        
        for ( uint8_t cnt = 0; cnt <= *pl_size; cnt++ )
        {
            log_printf( &logger, "0x%.2X ", ( uint16_t ) pl_buffer[ cnt ] );
        }
        log_printf( &logger, "\r\n------------------------\r\n" );
    }
        
}

// ------------------------------------------------------ APPLICATION FUNCTIONS

void application_init ( void )
{
    log_cfg_t log_cfg;
    lr3_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.

    lr3_cfg_setup( &cfg );
    LR3_MAP_MIKROBUS( cfg, MIKROBUS_1 );
    lr3_init( &lr3, &cfg );

    Delay_ms( 100 );
    lr3_set_ind_handler( &lr3, indication_handler );
    lr3_hard_reset( &lr3 );
    lr3_factory_reset( &lr3 );
    Delay_ms( 1000 );
    
#ifdef MASTER
    // Set device as MASTER
    tmp_msg.payload[ 0 ] = 0;

    if( lr3_write_eeprom( &lr3, 0x00, 1, &tmp_msg.payload[ 0 ] ) )
    {
        log_error( &logger, "Setting device as MASTER!\r\n" );
        for( ; ; );
    }
    
    log_printf( &logger, "Device configured as MASTER!\r\n" );
    Delay_ms( 1000 );
    
    // Delete all network table
    if( lr3_delete_all_network_table( &lr3 ) )
    {
        log_error( &logger, "Deleting all paired devices!\r\n" );
        for( ; ; );
    }
    log_printf( &logger, "All paired devices deleted!\r\n" );
    Delay_ms( 1000 );
    
    // Enable pairing
    if( lr3_enable_pairing( &lr3, 1 ) )
    {
        log_error( &logger, "Pairing not enabled!\r\n" );
        for( ; ; );
    }
    log_printf( &logger, "Pairing enabled!\r\n" );
    Delay_ms( 1000 );
#endif

#ifdef END_NODE
    // Set device as END_NODE
    tmp_msg.payload[ 0 ] = 1;
    
    if( lr3_write_eeprom( &lr3, 0x00, 1, &tmp_msg.payload[ 0 ] ) )
    {
        log_error( &logger, "Setting device as END_NODE!\r\n" );
        for( ; ; );
    }
    
    log_printf( &logger, "Device configured as END_NODE!\r\n" );
    Delay_ms( 1000 );
    
    // Send pairing request and displays MASTER ID
    uint8_t master_id[ 4 ] = { 0 };
    do
    {
        lr3_get_pairing_request( &lr3 );
        Delay_ms( 1000 );
    }
    while ( lr3_get_activation_status( &lr3, master_id ) != 1 );
    log_printf( &logger, "Paired to a network!\r\n" );
    log_printf( &logger, "Master ID: 0x%.2X%.2X%.2X%.2X\r\n", ( uint16_t ) master_id[ 3 ],
                                                              ( uint16_t ) master_id[ 2 ],
                                                              ( uint16_t ) master_id[ 1 ],
                                                              ( uint16_t ) master_id[ 0 ] );
    
#endif
}

void application_task ( void )
{
#ifdef END_NODE
    strcpy( tmp_msg.payload, TEXT_TO_SEND );
   
    lr3_tx_msg.data_in = &tmp_msg.payload[ 0 ];
    lr3_tx_msg.n_bytes = strlen( TEXT_TO_SEND );
    lr3_tx_msg.destination_id = LR3_BROADCAST_MESSAGE;
    lr3_tx_msg.option = LR3_UNCONFIRMED_DATA_TX;
    if ( lr3_tx_message( &lr3, &lr3_tx_msg ) == 0 )
    {
        log_printf( &logger, "Message: \"%s\" sent to MASTER...\r\n", ( uint8_t * ) TEXT_TO_SEND );
        log_printf( &logger, "------------------------\r\n" );
    }
    
    Delay_ms( 3000 );
#endif
#ifdef MASTER
    lr3_read_message_process( &lr3 );
#endif
}

void main ( void )
{
    application_init( );

    for ( ; ; )
    {
        application_task( );
    }
}


// ------------------------------------------------------------------------ END

Additional Support

Resources

Love this project?

'Buy This Kit' button takes you directly to the shopping cart where you can easily add or remove products.