Experience uninterrupted communication over extended distances with our 868MHz transceivers, ensuring that your data is reliably transmitted even in challenging environments.
A
A
Hardware Overview
How does it work?
LR 4 Click is based on the 32001353, 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. This Click board™ features an embedded LoRaWAN Class A and Class C compliant stack, offering 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. To join a LoRaWAN network, the 32001353 requires a LoRaWAN concentrator/gateway. The endpoint device has to use a unique endpoint address, an application session key, and a network session key.
The first method is called over-the-air activation (OTAA), where these keys are issued after a specific join procedure. The second method is to assign these keys manually, using UART commands. This method is called activation by personalization (ABP) and can be prone to some security issues. In any case, before an end device can communicate on the LoRaWAN network, it must be activated. LR 4 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 32001353 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 4 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.
Features overview
Development board
Nucleo-64 with STM32G071RB 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-M0
MCU Memory (KB)
128
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
36864
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.
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.
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Click board™ Schematic

Step by step
Project 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 4 Click driver.
Key functions:
lr4_factory_reset
- Function performs the recovery of EEPROM default values.lr4_write_eeprom
- Function writes data to EEPROM.lr4_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 LR4 Click example
*
* # Description
* This example reads and processes data from LR 4 clicks.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver, and resets the click board to factory default configuration.
* Then performs a group of commands for getting the FW version, the serial number, and the DevEUI.
* After that executes the join activation by personalization command.
*
* ## Application Task
* Checks the activation and session status and displays the results on the USB UART.
*
* ## Additional Function
* - response_handler - Parses and logs all the module responses on the USB UART.
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "lr4.h"
#include "string.h"
// ------------------------------------------------------------------ VARIABLES
static lr4_t lr4;
static lr4_tx_msg_t lr4_tx_msg;
static log_t logger;
// -------------------------------------------------------- ADDITIONAL FUNCTIONS
static void response_handler( uint8_t *cmd, uint8_t *pl_size, uint8_t *pl_buffer )
{
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" );
}
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
lr4_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.
lr4_cfg_setup( &cfg );
LR4_MAP_MIKROBUS( cfg, MIKROBUS_1 );
lr4_init( &lr4, &cfg );
Delay_ms( 100 );
lr4_set_ind_handler( &lr4, response_handler );
log_printf( &logger, "Hard reset!\r\n" );
lr4_hard_reset( &lr4 );
log_printf( &logger, "------------------------\r\n" );
log_printf( &logger, "Factory reset!\r\n" );
lr4_factory_reset( &lr4 );
log_printf( &logger, "------------------------\r\n" );
Delay_ms( 1000 );
uint32_t tmp_data = 0;
log_printf( &logger, "Get FW version!\r\n" );
lr4_get_fw_version( &lr4, &tmp_data );
log_printf( &logger, "FW vesion is: 0x%.8LX\r\n", tmp_data );
log_printf( &logger, "------------------------\r\n" );
Delay_ms( 1000 );
log_printf( &logger, "Get Serial Number!\r\n" );
lr4_get_serial_no( &lr4, &tmp_data );
log_printf( &logger, "Serial Number is: 0x%.8LX\r\n", tmp_data );
log_printf( &logger, "------------------------\r\n" );
Delay_ms( 1000 );
uint8_t tmp_buf[ 8 ] = { 0 };
log_printf( &logger, "Get Dev EUI!\r\n" );
lr4_get_dev_eui( &lr4, tmp_buf );
log_printf( &logger, "Dev EUI is: 0x%.2X%.2X%.2X%.2X%.2X%.2X%.2X%.2X\r\n", ( uint16_t ) tmp_buf[ 7 ],
( uint16_t ) tmp_buf[ 6 ],
( uint16_t ) tmp_buf[ 5 ],
( uint16_t ) tmp_buf[ 4 ],
( uint16_t ) tmp_buf[ 3 ],
( uint16_t ) tmp_buf[ 2 ],
( uint16_t ) tmp_buf[ 1 ],
( uint16_t ) tmp_buf[ 0 ] );
log_printf( &logger, "------------------------\r\n" );
Delay_ms( 1000 );
log_printf( &logger, "Join Network!\r\n" );
lr4_join_network( &lr4, LR4_JOIN_ACTIVATION_BY_PERSONALIZATION_MODE );
log_printf( &logger, "------------------------\r\n" );
Delay_ms( 1000 );
}
void application_task ( void )
{
log_printf( &logger, "Get Activation Status!\r\n" );
uint8_t status = lr4_get_status( &lr4, LR4_GET_ACTIVATION_MODE );
log_printf( &logger, "Status: " );
switch ( status )
{
case LR4_STATUS_NOT_ACTIVATED :
{
log_printf( &logger, "Not activated.\r\n" );
break;
}
case LR4_STATUS_JOINING :
{
log_printf( &logger, "Joining...\r\n" );
break;
}
case LR4_STATUS_JOINED :
{
log_printf( &logger, "Joined.\r\n" );
break;
}
case LR4_STATUS_MAC_ERROR :
{
log_printf( &logger, "MAC ERROR.\r\n" );
break;
}
default :
{
break;
}
}
log_printf( &logger, "------------------------\r\n" );
Delay_ms( 1000 );
log_printf( &logger, "Get Session Status!\r\n" );
status = lr4_get_status( &lr4, LR4_GET_SESSION_STATUS_MODE );
log_printf( &logger, "Status: " );
switch ( status )
{
case LR4_STATUS_IDLE :
{
log_printf( &logger, "Idle.\r\n" );
break;
}
case LR4_STATUS_BUSY :
{
log_printf( &logger, "Busy (LR session running).\r\n" );
break;
}
case LR4_STATUS_DEV_NOT_ACTIVATED :
{
log_printf( &logger, "Device not activated.\r\n" );
break;
}
case LR4_STATUS_DELAYED :
{
log_printf( &logger, "Delayed (LR session paused due to Duty-cycle).\r\n" );
break;
}
default :
{
break;
}
}
log_printf( &logger, "------------------------\r\n" );
Delay_ms( 1000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END