Elevate your IoT connectivity to new heights with a platform that combines the benefits of NB-IoT technology, including power efficiency and extended coverage, for a reliable and secure IoT experience
A
A
Hardware Overview
How does it work?
5G NB IoT Click is based on the ENS22, an NB-IoT Wireless Module platform from Thales that boosts highly efficient future 5G connectivity for the IoT. The ENS22 IoT wireless module marries future 5G connectivity with expanded coverage and enhanced security features to connect and protect industrial IoT solutions. Delivering data speeds up to 27 Kbit/s downlink and 63 Kbit/s uplink, the ENS22 IoT module is ideal for long life data-only solutions such as utility meters and smart city solutions. 5G NB IoT Click features an integrated NB-IoT transceiver, multi-band mobile cellular devices. The module can operate over 698-960 MHz and 1695-2180MHz with a 200 kHz system bandwidth. It is designed to communicate with
mobile network operator (MNO) infrastructure equipment using the 3GPP NB-IoT radio protocol. The ENS22 IoT module platform offers a suite of NB-IoT connectivity solutions optimized specifically for IoT applications and prepared to support release 14 without the need to migrate to a new chipset. It delivers Five Band LTE (3, 5, 8, 20, 28) connectivity with deep indoor coverage and extended range in rural areas. The module offers a built-in IP stack which supports a range of internet services protected by an enhanced security concept. Incremental Firmware Over The Air (FOTA) updates allow revision of only the portion of code that needs updating, saving power and bandwidth to extend the life span of IoT solutions.
The module’s simplified power supply design and advanced management system extends battery lifetime and improves TCO. This Click board™ is equipped with the USB type C connector. It allows the module to be powered and configured by a personal computer. The FT230X IC requires drivers in order to work. FTDI offers drivers for all major OSes on their official driver download web page. Also, Windows OS drivers are included in the download section, below. 5G NB IoT Click have fully-integrated Li-Ion or Li-Polymer battery charger witch in combination with module up to 10 ~ 15 years of battery life allow user using it completely standalone and battery powered ony.
Features overview
Development board
Nucleo-64 with STM32F091RC 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)
256
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
32768
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.
LTE Flat Rotation Antenna is a versatile choice for boosting the performance of 3G/4G LTE devices. With a wide frequency range of 700-2700MHz, it ensures optimal connectivity on major cellular bands worldwide. This flat antenna features an SMA male connector, making it easy to attach directly to your device or SMA module connector. One of its standout features is its adjustable angle, which can be set in 45⁰ increments (0⁰/45⁰/90⁰), allowing you to fine-tune the antenna's orientation for maximum signal reception. With an impedance of 50Ω and a VSW Ratio of <2.0:1, this antenna ensures a reliable and efficient connection. Its 5dB gain, vertical polarization, and omnidirectional radiation pattern enhance signal strength, making it suitable for various applications. Measuring 196mm in length and 38mm in width, this antenna offers a compact yet effective solution for improving your connectivity. With a maximum input power of 50W, it can handle the demands of various devices.
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 5G NB IoT Click driver.
Key functions:
c5gnbiot_send_cmd
- Send command functionc5gnbiot_set_sim_apn
- Set sim card APN functionc5gnbiot_send_text_message
- Send SMS in PDU mode function
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 5gNbIot Click example
*
* # Description
* This example reads and processes data from 5G NB IoT click.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes driver and wake-up module and sets default configuration for connecting device to network.
*
* ## Application Task
* Waits for device to connect to network and then sends an SMS to the selected phone number.
*
* ## Additional Function
* - static void c5gnbiot_clear_app_buf ( void )
* - static void c5gnbiot_error_check( err_t error_flag )
* - static void c5gnbiot_log_app_buf ( void )
* - static void c5gnbiot_check_connection( void )
* - static err_t c5gnbiot_rsp_check ( void )
* - static err_t c5gnbiot_process ( void )
*
* @note
* In order for the example to work, user needs to set the phone number to which he wants
* to send an SMS, and also will need to set an APN and SMSC of entered SIM card.
* Enter valid data for the following macros: SIM_APN, SIM_SMSC and PHONE_NUMBER_TO_MESSAGE.
* E.g.
SIM_APN "vipmobile"
SIM_SMSC "+381610401"
PHONE_NUMBER_TO_MESSAGE "+381659999999"
*
* @author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "c5gnbiot.h"
#define APP_OK 0
#define APP_ERROR_DRIVER -1
#define APP_ERROR_OVERFLOW -2
#define APP_ERROR_TIMEOUT -3
#define RSP_OK "OK"
#define RSP_ERROR "ERROR"
#define SIM_APN "" // Set valid SIM APN
#define SIM_SMSC "" // Set valid SMS Service Center Address
#define PHONE_NUMBER_TO_MESSAGE "" // Set Phone number to message
#define MESSAGE_CONTENT "5G NB IoT Click" // Messege content
#define PROCESS_BUFFER_SIZE 300
#define WAIT_FOR_CONNECTION 0
#define CONNECTED_TO_NETWORK 1
static c5gnbiot_t c5gnbiot;
static log_t logger;
static char app_buf[ PROCESS_BUFFER_SIZE ] = { 0 };
static int32_t app_buf_len = 0;
static int32_t app_buf_cnt = 0;
static uint8_t app_connection_status = WAIT_FOR_CONNECTION;
static err_t app_error_flag;
/**
* @brief 5G NB IoT clearing application buffer.
* @details This function clears memory of application buffer and reset its length and counter.
* @note None.
*/
static void c5gnbiot_clear_app_buf ( void );
/**
* @brief 5G NB IoT data reading function.
* @details This function reads data from device and concats data to application buffer.
*
* @return @li @c 0 - Read some data.
* @li @c -1 - Nothing is read.
* @li @c -2 - Application buffer overflow.
*
* See #err_t definition for detailed explanation.
* @note None.
*/
static err_t c5gnbiot_process ( void );
/**
* @brief 5G NB IoT check for errors.
* @details This function checks for different types of errors and logs them on UART.
* @note None.
*/
static void c5gnbiot_error_check( err_t error_flag );
/**
* @brief 5G NB IoT logs application buffer.
* @details This function logs data from application buffer.
* @note None.
*/
static void c5gnbiot_log_app_buf ( void );
/**
* @brief 5G NB IoT response check.
* @details This function checks for response and returns the status of response.
*
* @return application status.
* See #err_t definition for detailed explanation.
* @note None.
*/
static err_t c5gnbiot_rsp_check ( void );
/**
* @brief 5G NB IoT chek connection.
* @details This function checks connection to the network and
* logs that status to UART.
*
* @note None.
*/
static void c5gnbiot_check_connection( void );
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
c5gnbiot_cfg_t c5gnbiot_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 " );
Delay_ms( 1000 );
// Click initialization.
c5gnbiot_cfg_setup( &c5gnbiot_cfg );
C5GNBIOT_MAP_MIKROBUS( c5gnbiot_cfg, MIKROBUS_1 );
err_t init_flag = c5gnbiot_init( &c5gnbiot, &c5gnbiot_cfg );
if ( init_flag == UART_ERROR )
{
log_error( &logger, " Application Init Error. " );
log_info( &logger, " Please, run program again... " );
for ( ; ; );
}
log_info( &logger, " Power on device... " );
Delay_ms( 1000 );
c5gnbiot_power_on( &c5gnbiot );
// dummy read
c5gnbiot_process( );
c5gnbiot_clear_app_buf( );
// AT
c5gnbiot_send_cmd( &c5gnbiot, C5GNBIOT_CMD_AT );
app_error_flag = c5gnbiot_rsp_check( );
c5gnbiot_error_check( app_error_flag );
Delay_ms( 500 );
// ATI - product information
c5gnbiot_send_cmd( &c5gnbiot, C5GNBIOT_CMD_ATI );
app_error_flag = c5gnbiot_rsp_check( );
c5gnbiot_error_check( app_error_flag );
Delay_ms( 500 );
// CGMR - firmware version
c5gnbiot_send_cmd( &c5gnbiot, C5GNBIOT_CMD_CGMR );
app_error_flag = c5gnbiot_rsp_check( );
c5gnbiot_error_check( app_error_flag );
Delay_ms( 500 );
// COPS - deregister from network
c5gnbiot_send_cmd_with_parameter( &c5gnbiot, C5GNBIOT_CMD_COPS, "2" );
app_error_flag = c5gnbiot_rsp_check( );
c5gnbiot_error_check( app_error_flag );
Delay_ms( 500 );
// CGDCONT - set sim apn
c5gnbiot_set_sim_apn( &c5gnbiot, SIM_APN );
app_error_flag = c5gnbiot_rsp_check( );
c5gnbiot_error_check( app_error_flag );
Delay_ms( 500 );
// CFUN - full funtionality
c5gnbiot_send_cmd_with_parameter( &c5gnbiot, C5GNBIOT_CMD_CFUN, "1" );
app_error_flag = c5gnbiot_rsp_check( );
c5gnbiot_error_check( app_error_flag );
Delay_ms( 500 );
// COPS - automatic mode
c5gnbiot_send_cmd_with_parameter( &c5gnbiot, C5GNBIOT_CMD_COPS, "0" );
app_error_flag = c5gnbiot_rsp_check( );
c5gnbiot_error_check( app_error_flag );
Delay_ms( 2000 );
// CEREG - network registration status
c5gnbiot_send_cmd_with_parameter( &c5gnbiot, C5GNBIOT_CMD_CEREG, "2" );
app_error_flag = c5gnbiot_rsp_check( );
c5gnbiot_error_check( app_error_flag );
Delay_ms( 500 );
// CIMI - request IMSI
c5gnbiot_send_cmd( &c5gnbiot, C5GNBIOT_CMD_CIMI );
app_error_flag = c5gnbiot_rsp_check( );
c5gnbiot_error_check( app_error_flag );
Delay_ms( 500 );
app_buf_len = 0;
app_buf_cnt = 0;
app_connection_status = WAIT_FOR_CONNECTION;
log_info( &logger, " Application Task " );
Delay_ms( 5000 );
}
void application_task ( void )
{
if ( app_connection_status == WAIT_FOR_CONNECTION )
{
// CGATT - request IMSI
c5gnbiot_send_cmd_check( &c5gnbiot, C5GNBIOT_CMD_CGATT );
app_error_flag = c5gnbiot_rsp_check( );
c5gnbiot_error_check( app_error_flag );
Delay_ms( 500 );
// CEREG - network registration status
c5gnbiot_send_cmd_check( &c5gnbiot, C5GNBIOT_CMD_CEREG );
app_error_flag = c5gnbiot_rsp_check( );
c5gnbiot_error_check( app_error_flag );
Delay_ms( 500 );
// CSQ - signal quality
c5gnbiot_send_cmd( &c5gnbiot, C5GNBIOT_CMD_CESQ );
app_error_flag = c5gnbiot_rsp_check( );
c5gnbiot_error_check( app_error_flag );
Delay_ms( 5000 );
}
else
{
log_info( &logger, "CONNECTED TO NETWORK" );
for( ; ; )
{
log_printf( &logger, "> Sending message to phone number...\r\n" );
c5gnbiot_send_text_message( &c5gnbiot, SIM_SMSC, PHONE_NUMBER_TO_MESSAGE, MESSAGE_CONTENT );
app_error_flag = c5gnbiot_rsp_check( );
c5gnbiot_error_check( app_error_flag );
Delay_ms( 10000 );
Delay_ms( 10000 );
Delay_ms( 10000 );
}
}
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
static void c5gnbiot_clear_app_buf ( void )
{
memset( app_buf, 0, app_buf_len );
app_buf_len = 0;
app_buf_cnt = 0;
}
static err_t c5gnbiot_process ( void )
{
err_t return_flag = APP_ERROR_DRIVER;
int32_t rx_size;
char rx_buff[ PROCESS_BUFFER_SIZE ] = { 0 };
rx_size = c5gnbiot_generic_read( &c5gnbiot, rx_buff, PROCESS_BUFFER_SIZE );
if ( rx_size > 0 )
{
int32_t buf_cnt = 0;
return_flag = APP_OK;
if ( app_buf_len + rx_size >= PROCESS_BUFFER_SIZE )
{
c5gnbiot_clear_app_buf( );
return_flag = APP_ERROR_OVERFLOW;
}
else
{
buf_cnt = app_buf_len;
app_buf_len += rx_size;
}
for ( int32_t rx_cnt = 0; rx_cnt < rx_size; rx_cnt++ )
{
if ( rx_buff[ rx_cnt ] != 0 )
{
app_buf[ ( buf_cnt + rx_cnt ) ] = rx_buff[ rx_cnt ];
}
else
{
app_buf_len--;
buf_cnt--;
}
}
}
return return_flag;
}
static err_t c5gnbiot_rsp_check ( void )
{
uint16_t timeout_cnt = 0;
uint16_t timeout = 10000;
err_t error_flag = c5gnbiot_process( );
if ( ( error_flag != 0 ) && ( error_flag != -1 ) )
{
return error_flag;
}
while ( ( strstr( app_buf, RSP_OK ) == 0 ) && ( strstr( app_buf, RSP_ERROR ) == 0 ) )
{
error_flag = c5gnbiot_process( );
if ( ( error_flag != 0 ) && ( error_flag != -1 ) )
{
return error_flag;
}
timeout_cnt++;
if ( timeout_cnt > timeout )
{
while ( ( strstr( app_buf, RSP_OK ) == 0 ) && ( strstr( app_buf, RSP_ERROR ) == 0 ) )
{
c5gnbiot_send_cmd( &c5gnbiot, C5GNBIOT_CMD_AT );
c5gnbiot_process( );
Delay_ms( 100 );
}
c5gnbiot_clear_app_buf( );
return APP_ERROR_TIMEOUT;
}
Delay_ms( 1 );
}
c5gnbiot_check_connection();
c5gnbiot_log_app_buf();
log_printf( &logger, "-----------------------------------\r\n" );
return APP_OK;
}
static void c5gnbiot_error_check( err_t error_flag )
{
if ( ( error_flag != 0 ) && ( error_flag != -1 ) )
{
switch ( error_flag )
{
case -2:
log_error( &logger, " Overflow!" );
break;
case -3:
log_error( &logger, " Timeout!" );
break;
default:
break;
}
}
}
static void c5gnbiot_log_app_buf ( void )
{
for ( int32_t buf_cnt = 0; buf_cnt < app_buf_len; buf_cnt++ )
{
log_printf( &logger, "%c", app_buf[ buf_cnt ] );
}
log_printf( &logger, "\r\n" );
c5gnbiot_clear_app_buf( );
}
static void c5gnbiot_check_connection( void )
{
#define CONNECTED "+CGATT: 1"
if ( strstr( app_buf, CONNECTED ) != 0 )
{
app_connection_status = CONNECTED_TO_NETWORK;
}
}
// ------------------------------------------------------------------------ END