Enable reliable, low-latency wireless connectivity with global LTE and GNSS support perfect for metering, asset tracking, and remote monitoring in IoT applications
A
A
Hardware Overview
How does it work?
LTE IoT 14 Click is based on the SIM7090G, a multi-band LTE module from SIMCom suitable for global connectivity. The SIM7090G supports Cat-M/Cat-NB wireless communication modes, has multiple built-in network protocols, and has a maximum 0.589Mbps downlink rate and 1.119Mbps uplink rate. Besides, it also supports multiple Cat-M bands (B1/B2/B3/B4/B5/B8/B12/B13/B14/B18/B19/B20/
B25/B26/B27/B28/B66/B85), and Cat-NB (B1/B2/B3/B4/B5/B8/B12/B13/B18/B19/B20/
B25/B26/B28/ B66/B71/B85), as well as multi-constellation GNSS support (GPS/GLONASS/Galileo/BeiDou). Based on its broad features, this Click board™ is ideal for M2M applications that need low latency, low throughput data communication in various radio propagation conditions, such as metering, asset tracking, remote monitoring, E-health, and more. Communication between the SIM7090G and the host MCU is made through a UART interface, using standard UART RX and TX pins and hardware flow control pins (CTS/RTS/RI - Clear to Send/Ready to Send/Ring Indicator) for efficient data transfer. The module defaults to a communication speed of 115200bps, allowing for seamless data exchange over AT commands. Users can change it to the I2C interface supporting up to 400kbps in Fast Mode for the same purpose. This Click board™ also includes a USB Type C connector for both power and data
transfer, which is compliant with the USB 2.0 specification (peripheral only). In addition to this interface, the board also features a USB FW upgrade switch on the back of the board labeled USB BOOT to manage firmware upgrades. This switch has positions 0 for normal operation and 1 for firmware upgrades over USB, ensuring a straightforward upgrade process. The LTE IoT 14 Click includes several additional functionalities that enhance its usability and control. The PWR button allows users to easily power the module ON or OFF, while the RESET button provides a quick way to reset the module. These functions can also be controlled digitally via the mikroBUS™ pins PWR and RST, offering greater flexibility. Moreover, this board also has dedicated test points (TP3/TP4 for DBG_UART, TP5/TP6 for NMEA data output for GNSS) for easier debugging and testing and two visual indicators to provide real-time status updates. The first red NET LED indicates the current network status of the module. When the LED blinks slowly, with 64ms ON and 3000ms OFF, the device has successfully registered on the network, specifically in the PS domain. If the LED blinks at a normal pace, with 64ms ON and 800ms OFF, the device has not yet registered to a network. A fast blinking pattern, with 64ms ON and 300ms OFF, signals data transmission occurs, such as during a PPP dial-up connection or when using data services like internal TCP, FTP, or HTTP.
When the LED is completely OFF, it indicates that the device is either powered off or in Power Saving Mode (PSM). The second yellow STAT LED indicates the module's power status, which stays off when the module is OFF and turns ON when the module is powered on or firmware ready. The board features two SMA connectors for LTE and GNSS antennas that MIKROE offers, like the LTE Flat Rotation Antenna and Active GPS Antenna, for efficient connectivity options. In addition, the user can easily choose the power supply of the optional GNSS antenna by choosing between 3.3V and 5V on the GNSS ANT jumper at the back of the board. The board also has a micro SIM card holder that supports only 1.8V uSIM cards, allowing users to select the most appropriate service provider for their particular use case. This Click board™ can operate with both 3.3V and 5V logic voltage levels selected via the VCC SEL jumper. Since the SIM7090G module operates at 3.8V, a logic-level translators, the TXB0106 and PCA9306, are also used for proper operation and an accurate signal-level translation. 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.
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.
Active GPS antenna is designed to enhance the performance of your GPS and GNSS Click boards™. This external antenna boasts a robust construction, making it ideal for various weather conditions. With a frequency range of 1575.42MHz and a 50Ohm impedance, it ensures reliable signal reception. The antenna delivers a gain of greater than -4dBic within a wide angular range, securing over 75% coverage. The bandwidth of +/- 5MHz further guarantees precise data acquisition. Featuring a Right-Hand Circular Polarization (RHCP), this antenna offers stable signal reception. Its compact dimensions of 48.53915mm and a 2-meter cable make it easy to install. The magnetic antenna type with an SMA male connector ensures a secure and convenient connection. If you require a dependable external antenna for your locator device, our active GPS antenna is the perfect solution.
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 LTE IoT 14 Click driver.
Key functions:
lteiot14_set_sim_apn
- This function sets APN for sim card.lteiot14_send_sms_text
- This function sends text message to a phone number.lteiot14_send_cmd
- This function sends a specified command to the click module.
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 LTE IoT 14 Click Example.
*
* # Description
* Application example shows device capability of connecting to the network and
* sending SMS or TCP/UDP messages, or retrieving data from GNSS using standard "AT" commands.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and logger.
*
* ## Application Task
* Application task is split in few stages:
* - LTEIOT14_POWER_UP:
* Powers up the device, performs a device reset and reads system information.
*
* - LTEIOT14_CONFIG_CONNECTION:
* Sets configuration to device to be able to connect to the network (used only for SMS or TCP/UDP demo examples).
*
* - LTEIOT14_CHECK_CONNECTION:
* Waits for the network registration indicated via CREG command and then checks the signal quality report
* (used only for SMS or TCP/UDP demo examples).
*
* - LTEIOT14_CONFIG_EXAMPLE:
* Configures device for the selected example.
*
* - LTEIOT14_EXAMPLE:
* Depending on the selected demo example, it sends an SMS message (in PDU or TXT mode) or TCP/UDP message or
* waits for the GPS fix to retrieve location info from GNSS.
*
* By default, the TCP/UDP example is selected.
*
* ## Additional Function
* - static void lteiot14_clear_app_buf ( void )
* - static void lteiot14_log_app_buf ( void )
* - static err_t lteiot14_process ( lteiot14_t *ctx )
* - static err_t lteiot14_read_response ( lteiot14_t *ctx, uint8_t *rsp )
* - static err_t lteiot14_power_up ( lteiot14_t *ctx )
* - static err_t lteiot14_config_connection ( lteiot14_t *ctx )
* - static err_t lteiot14_check_connection ( lteiot14_t *ctx )
* - static err_t lteiot14_config_example ( lteiot14_t *ctx )
* - static err_t lteiot14_example ( lteiot14_t *ctx )
*
* @note
* In order for the examples to work (except GNSS example), user needs to set the APN and SMSC (SMS PDU mode only)
* of entered SIM card as well as the phone number (SMS mode only) to which he wants to send an SMS.
* Enter valid values for the following macros: SIM_APN, SIM_SMSC and PHONE_NUMBER_TO_MESSAGE.
* Example:
SIM_APN "internet"
SIM_SMSC "+381610401"
PHONE_NUMBER_TO_MESSAGE "+381659999999"
*
* @author Stefan Filipovic
*
*/
#include "board.h"
#include "log.h"
#include "lteiot14.h"
#include "conversions.h"
// Example selection macros
#define EXAMPLE_TCP_UDP 0 // Example of sending messages to a TCP/UDP echo server
#define EXAMPLE_SMS 1 // Example of sending SMS to a phone number
#define EXAMPLE_GNSS 2 // Example of retrieving location info from GNSS
#define DEMO_EXAMPLE EXAMPLE_TCP_UDP // Example selection macro
// SIM APN config
#define SIM_APN "internet" // Set valid SIM APN
// SMS example parameters
#define SIM_SMSC "" // Set valid SMS Service Center Address - only in SMS PDU mode
#define PHONE_NUMBER_TO_MESSAGE "" // Set Phone number to message
#define SMS_MODE "1" // SMS mode: "0" - PDU, "1" - TXT
// TCP/UDP example parameters
#define REMOTE_IP "77.46.162.162" // TCP/UDP echo server IP address
#define REMOTE_PORT "51111" // TCP/UDP echo server port
// Message content
#define MESSAGE_CONTENT "LTE IoT 14 click board - demo example."
// Application buffer size
#define APP_BUFFER_SIZE 256
#define PROCESS_BUFFER_SIZE 256
/**
* @brief Example states.
* @details Predefined enum values for application example state.
*/
typedef enum
{
LTEIOT14_POWER_UP = 1,
LTEIOT14_CONFIG_CONNECTION,
LTEIOT14_CHECK_CONNECTION,
LTEIOT14_CONFIG_EXAMPLE,
LTEIOT14_EXAMPLE
} lteiot14_app_state_t;
/**
* @brief Application example variables.
* @details Variables used in application example.
*/
static uint8_t app_buf[ APP_BUFFER_SIZE ] = { 0 };
static int32_t app_buf_len = 0;
static lteiot14_app_state_t app_state = LTEIOT14_POWER_UP;
static lteiot14_t lteiot14;
static log_t logger;
/**
* @brief LTE IoT 14 clearing application buffer.
* @details This function clears memory of application buffer and reset its length.
* @note None.
*/
static void lteiot14_clear_app_buf ( void );
/**
* @brief LTE IoT 14 log application buffer.
* @details This function logs data from application buffer to USB UART.
* @note None.
*/
static void lteiot14_log_app_buf ( void );
/**
* @brief LTE IoT 14 data reading function.
* @details This function reads data from device and concatenates data to application buffer.
* @param[in] ctx : Click context object.
* See #lteiot14_t object definition for detailed explanation.
* @return @li @c 0 - Read some data.
* @li @c -1 - Nothing is read.
* See #err_t definition for detailed explanation.
* @note None.
*/
static err_t lteiot14_process ( lteiot14_t *ctx );
/**
* @brief LTE IoT 14 read response function.
* @details This function waits for a response message, reads and displays it on the USB UART.
* @param[in] ctx : Click context object.
* See #lteiot14_t object definition for detailed explanation.
* @param[in] rsp Expected response.
* @return @li @c 0 - OK response.
* @li @c -2 - Timeout error.
* @li @c -3 - Command error.
* @li @c -4 - Unknown error.
* See #err_t definition for detailed explanation.
* @note None.
*/
static err_t lteiot14_read_response ( lteiot14_t *ctx, uint8_t *rsp );
/**
* @brief LTE IoT 14 power up function.
* @details This function powers up the device, performs device hardware reset and reads system information.
* @param[in] ctx : Click context object.
* See #lteiot14_t object definition for detailed explanation.
* @return @li @c 0 - OK.
* @li @c != 0 - Read response error.
* See #err_t definition for detailed explanation.
* @note None.
*/
static err_t lteiot14_power_up ( lteiot14_t *ctx );
/**
* @brief LTE IoT 14 config connection function.
* @details This function configures and enables connection to the specified network.
* @param[in] ctx : Click context object.
* See #lteiot14_t object definition for detailed explanation.
* @return @li @c 0 - OK.
* @li @c != 0 - Read response error.
* See #err_t definition for detailed explanation.
* @note None.
*/
static err_t lteiot14_config_connection ( lteiot14_t *ctx );
/**
* @brief LTE IoT 14 check connection function.
* @details This function checks the connection to network.
* @param[in] ctx : Click context object.
* See #lteiot14_t object definition for detailed explanation.
* @return @li @c 0 - OK.
* @li @c != 0 - Read response error.
* See #err_t definition for detailed explanation.
* @note None.
*/
static err_t lteiot14_check_connection ( lteiot14_t *ctx );
/**
* @brief LTE IoT 14 config example function.
* @details This function configures device for the selected example.
* @param[in] ctx : Click context object.
* See #lteiot14_t object definition for detailed explanation.
* @return @li @c 0 - OK.
* @li @c != 0 - Read response error.
* See #err_t definition for detailed explanation.
* @note None.
*/
static err_t lteiot14_config_example ( lteiot14_t *ctx );
/**
* @brief LTE IoT 14 example function.
* @details This function executes SMS, TCP/UDP or GNSS example depending on the DEMO_EXAMPLE macro.
* @param[in] ctx : Click context object.
* See #lteiot14_t object definition for detailed explanation.
* @return @li @c 0 - OK.
* @li @c != 0 - Read response error.
* See #err_t definition for detailed explanation.
* @note None.
*/
static err_t lteiot14_example ( lteiot14_t *ctx );
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
lteiot14_cfg_t lteiot14_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 " );
// Click initialization.
lteiot14_cfg_setup( <eiot14_cfg );
LTEIOT14_MAP_MIKROBUS( lteiot14_cfg, MIKROBUS_1 );
if ( UART_ERROR == lteiot14_init( <eiot14, <eiot14_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
app_state = LTEIOT14_POWER_UP;
log_printf( &logger, ">>> APP STATE - POWER UP <<<\r\n\n" );
}
void application_task ( void )
{
switch ( app_state )
{
case LTEIOT14_POWER_UP:
{
if ( LTEIOT14_OK == lteiot14_power_up( <eiot14 ) )
{
app_state = LTEIOT14_CONFIG_CONNECTION;
log_printf( &logger, ">>> APP STATE - CONFIG CONNECTION <<<\r\n\n" );
}
break;
}
case LTEIOT14_CONFIG_CONNECTION:
{
if ( LTEIOT14_OK == lteiot14_config_connection( <eiot14 ) )
{
app_state = LTEIOT14_CHECK_CONNECTION;
log_printf( &logger, ">>> APP STATE - CHECK CONNECTION <<<\r\n\n" );
}
break;
}
case LTEIOT14_CHECK_CONNECTION:
{
if ( LTEIOT14_OK == lteiot14_check_connection( <eiot14 ) )
{
app_state = LTEIOT14_CONFIG_EXAMPLE;
log_printf( &logger, ">>> APP STATE - CONFIG EXAMPLE <<<\r\n\n" );
}
break;
}
case LTEIOT14_CONFIG_EXAMPLE:
{
if ( LTEIOT14_OK == lteiot14_config_example( <eiot14 ) )
{
app_state = LTEIOT14_EXAMPLE;
log_printf( &logger, ">>> APP STATE - EXAMPLE <<<\r\n\n" );
}
break;
}
case LTEIOT14_EXAMPLE:
{
lteiot14_example( <eiot14 );
break;
}
default:
{
log_error( &logger, " APP STATE." );
break;
}
}
}
int main ( void )
{
/* Do not remove this line or clock might not be set correctly. */
#ifdef PREINIT_SUPPORTED
preinit();
#endif
application_init( );
for ( ; ; )
{
application_task( );
}
return 0;
}
static void lteiot14_clear_app_buf ( void )
{
memset( app_buf, 0, app_buf_len );
app_buf_len = 0;
}
static void lteiot14_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 ] );
}
}
static err_t lteiot14_process ( lteiot14_t *ctx )
{
uint8_t rx_buf[ PROCESS_BUFFER_SIZE ] = { 0 };
int32_t overflow_bytes = 0;
int32_t rx_cnt = 0;
int32_t rx_size = lteiot14_generic_read( ctx, rx_buf, PROCESS_BUFFER_SIZE );
if ( ( rx_size > 0 ) && ( rx_size <= APP_BUFFER_SIZE ) )
{
if ( ( app_buf_len + rx_size ) > APP_BUFFER_SIZE )
{
overflow_bytes = ( app_buf_len + rx_size ) - APP_BUFFER_SIZE;
app_buf_len = APP_BUFFER_SIZE - rx_size;
memmove ( app_buf, &app_buf[ overflow_bytes ], app_buf_len );
memset ( &app_buf[ app_buf_len ], 0, overflow_bytes );
}
for ( rx_cnt = 0; rx_cnt < rx_size; rx_cnt++ )
{
if ( rx_buf[ rx_cnt ] )
{
app_buf[ app_buf_len++ ] = rx_buf[ rx_cnt ];
}
}
return LTEIOT14_OK;
}
return LTEIOT14_ERROR;
}
static err_t lteiot14_read_response ( lteiot14_t *ctx, uint8_t *rsp )
{
#define READ_RESPONSE_TIMEOUT_MS 120000
uint32_t timeout_cnt = 0;
lteiot14_clear_app_buf ( );
lteiot14_process( ctx );
while ( ( 0 == strstr( app_buf, rsp ) ) &&
( 0 == strstr( app_buf, LTEIOT14_RSP_ERROR ) ) )
{
lteiot14_process( ctx );
if ( timeout_cnt++ > READ_RESPONSE_TIMEOUT_MS )
{
lteiot14_clear_app_buf( );
log_error( &logger, " Timeout!" );
return LTEIOT14_ERROR_TIMEOUT;
}
Delay_ms( 1 );
}
Delay_ms ( 200 );
lteiot14_process( ctx );
if ( strstr( app_buf, rsp ) )
{
lteiot14_log_app_buf( );
log_printf( &logger, "--------------------------------\r\n" );
return LTEIOT14_OK;
}
else if ( strstr( app_buf, LTEIOT14_RSP_ERROR ) )
{
log_error( &logger, " CMD!" );
return LTEIOT14_ERROR_CMD;
}
log_error( &logger, " Unknown!" );
return LTEIOT14_ERROR_UNKNOWN;
}
static err_t lteiot14_power_up ( lteiot14_t *ctx )
{
err_t error_flag = LTEIOT14_OK;
log_printf( &logger, ">>> Power up device.\r\n" );
lteiot14_set_power_state ( ctx, LTEIOT14_POWER_STATE_ON );
log_printf( &logger, ">>> Perform device hardware reset.\r\n" );
lteiot14_set_power_state ( ctx, LTEIOT14_POWER_STATE_RESET );
log_printf( &logger, ">>> Check communication.\r\n" );
lteiot14_process( ctx );
lteiot14_clear_app_buf ( );
for ( uint8_t num_tries = 0; ; num_tries++ )
{
// Wake up AT interface
lteiot14_send_cmd( ctx, LTEIOT14_CMD_AT );
Delay_ms ( 1000 );
if ( LTEIOT14_OK == lteiot14_process( ctx ) )
{
break;
}
if ( num_tries > 10 )
{
lteiot14_set_power_state ( ctx, LTEIOT14_POWER_STATE_ON );
lteiot14_process( ctx );
lteiot14_clear_app_buf ( );
num_tries = 0;
}
}
lteiot14_send_cmd( ctx, LTEIOT14_CMD_AT );
error_flag |= lteiot14_read_response( ctx, LTEIOT14_RSP_OK );
log_printf( &logger, ">>> Get device model ID.\r\n" );
lteiot14_send_cmd( ctx, LTEIOT14_CMD_GET_MODEL_ID );
error_flag |= lteiot14_read_response( ctx, LTEIOT14_RSP_OK );
log_printf( &logger, ">>> Get device software version ID.\r\n" );
lteiot14_send_cmd( ctx, LTEIOT14_CMD_GET_SW_VERSION );
error_flag |= lteiot14_read_response( ctx, LTEIOT14_RSP_OK );
log_printf( &logger, ">>> Get device serial number.\r\n" );
lteiot14_send_cmd( ctx, LTEIOT14_CMD_GET_SERIAL_NUM );
error_flag |= lteiot14_read_response( ctx, LTEIOT14_RSP_OK );
return error_flag;
}
static err_t lteiot14_config_connection ( lteiot14_t *ctx )
{
err_t error_flag = LTEIOT14_OK;
#if ( ( DEMO_EXAMPLE == EXAMPLE_TCP_UDP ) || ( DEMO_EXAMPLE == EXAMPLE_SMS ) )
log_printf( &logger, ">>> Deregister from network.\r\n" );
#define DEREGISTER_FROM_NETWORK "2"
lteiot14_send_cmd_par( ctx, LTEIOT14_CMD_OPERATOR_SELECTION, DEREGISTER_FROM_NETWORK );
error_flag |= lteiot14_read_response( ctx, LTEIOT14_RSP_OK );
log_printf( &logger, ">>> Set SIM APN.\r\n" );
lteiot14_set_sim_apn( <eiot14, SIM_APN );
error_flag |= lteiot14_read_response( ctx, LTEIOT14_RSP_OK );
log_printf( &logger, ">>> Enable full functionality.\r\n" );
#define FULL_FUNCTIONALITY "1"
lteiot14_send_cmd_par( ctx, LTEIOT14_CMD_SET_PHONE_FUNCTIONALITY, FULL_FUNCTIONALITY );
error_flag |= lteiot14_read_response( ctx, LTEIOT14_RSP_OK );
log_printf( &logger, ">>> Enable network registration.\r\n" );
#define ENABLE_REG "2"
lteiot14_send_cmd_par( ctx, LTEIOT14_CMD_NETWORK_REGISTRATION, ENABLE_REG );
error_flag |= lteiot14_read_response( ctx, LTEIOT14_RSP_OK );
log_printf( &logger, ">>> Set automatic registration.\r\n" );
#define AUTOMATIC_REGISTRATION "0"
lteiot14_send_cmd_par( ctx, LTEIOT14_CMD_OPERATOR_SELECTION, AUTOMATIC_REGISTRATION );
error_flag |= lteiot14_read_response( ctx, LTEIOT14_RSP_OK );
#endif
return error_flag;
}
static err_t lteiot14_check_connection ( lteiot14_t *ctx )
{
err_t error_flag = LTEIOT14_OK;
#if ( ( DEMO_EXAMPLE == EXAMPLE_TCP_UDP ) || ( DEMO_EXAMPLE == EXAMPLE_SMS ) )
log_printf( &logger, ">>> Check network registration.\r\n" );
#define CONNECTED "+CREG: 2,1"
lteiot14_send_cmd_check ( <eiot14, LTEIOT14_CMD_NETWORK_REGISTRATION );
error_flag |= lteiot14_read_response( ctx, LTEIOT14_RSP_OK );
if ( strstr( app_buf, CONNECTED ) )
{
Delay_ms ( 1000 );
log_printf( &logger, ">>> Check signal quality.\r\n" );
lteiot14_send_cmd( <eiot14, LTEIOT14_CMD_SIGNAL_QUALITY_REPORT );
error_flag |= lteiot14_read_response( ctx, LTEIOT14_RSP_OK );
}
else
{
error_flag = LTEIOT14_ERROR;
Delay_ms ( 1000 );
Delay_ms ( 1000 );
}
#endif
return error_flag;
}
static err_t lteiot14_config_example ( lteiot14_t *ctx )
{
err_t error_flag = LTEIOT14_OK;
#if ( DEMO_EXAMPLE == EXAMPLE_TCP_UDP )
log_printf( &logger, ">>> Activate PDP context.\r\n" );
#define ACTIVATE_PDP_CONTEXT "1,1"
lteiot14_send_cmd_par( <eiot14, LTEIOT14_CMD_ACTIVATE_PDP_CONTEXT, ACTIVATE_PDP_CONTEXT );
error_flag |= lteiot14_read_response( ctx, LTEIOT14_RSP_OK );
log_printf( &logger, ">>> Show PDP address.\r\n" );
#define PDP_CID "1"
lteiot14_send_cmd_par( <eiot14, LTEIOT14_CMD_SHOW_PDP_ADDRESS, PDP_CID );
error_flag |= lteiot14_read_response( ctx, LTEIOT14_RSP_OK );
log_printf( &logger, ">>> Activate APP network.\r\n" );
#define ACTIVATE_APP_NETWORK "1,1"
lteiot14_send_cmd_par( <eiot14, LTEIOT14_CMD_APP_NETWORK_ACTIVE, ACTIVATE_APP_NETWORK );
error_flag |= lteiot14_read_response( ctx, LTEIOT14_RSP_OK );
#elif ( DEMO_EXAMPLE == EXAMPLE_SMS )
log_printf( &logger, ">>> Select SMS format.\r\n" );
lteiot14_send_cmd_par( <eiot14, LTEIOT14_CMD_SELECT_SMS_FORMAT, SMS_MODE );
error_flag |= lteiot14_read_response( ctx, LTEIOT14_RSP_OK );
#elif ( DEMO_EXAMPLE == EXAMPLE_GNSS )
log_printf( &logger, ">>> Turn on GNSS power supply.\r\n" );
#define GNNS_TURN_ON "1"
lteiot14_send_cmd_par( <eiot14, LTEIOT14_CMD_GNSS_POWER_CONTROL, GNNS_TURN_ON );
error_flag |= lteiot14_read_response( ctx, LTEIOT14_RSP_OK );
#endif
return error_flag;
}
static err_t lteiot14_example ( lteiot14_t *ctx )
{
err_t error_flag = LTEIOT14_OK;
#if ( DEMO_EXAMPLE == EXAMPLE_TCP_UDP )
uint8_t cmd_buf[ 100 ] = { 0 };
log_printf( &logger, ">>> Set TCP ID.\r\n" );
#define TCP_CID "1"
lteiot14_send_cmd_par ( <eiot14, LTEIOT14_CMD_SET_TCP_UDP_ID, TCP_CID );
error_flag |= lteiot14_read_response( ctx, LTEIOT14_RSP_OK );
log_printf( &logger, ">>> Open TCP connection.\r\n" );
#define PDP_CID "1"
#define TCP_CONN_TYPE "TCP"
strcpy( cmd_buf, TCP_CID );
strcat( cmd_buf, "," );
strcat( cmd_buf, PDP_CID );
strcat( cmd_buf, ",\"" );
strcat( cmd_buf, TCP_CONN_TYPE );
strcat( cmd_buf, "\",\"" );
strcat( cmd_buf, REMOTE_IP );
strcat( cmd_buf, "\"," );
strcat( cmd_buf, REMOTE_PORT );
lteiot14_send_cmd_par ( <eiot14, LTEIOT14_CMD_OPEN_TCP_UDP_CONNECTION, cmd_buf );
error_flag |= lteiot14_read_response( ctx, LTEIOT14_RSP_OK );
log_printf( &logger, ">>> Set UDP ID.\r\n" );
#define UDP_CID "2"
lteiot14_send_cmd_par ( <eiot14, LTEIOT14_CMD_SET_TCP_UDP_ID, UDP_CID );
error_flag |= lteiot14_read_response( ctx, LTEIOT14_RSP_OK );
log_printf( &logger, ">>> Open UDP connection.\r\n" );
#define UDP_CONN_TYPE "UDP"
strcpy( cmd_buf, UDP_CID );
strcat( cmd_buf, "," );
strcat( cmd_buf, PDP_CID );
strcat( cmd_buf, ",\"" );
strcat( cmd_buf, UDP_CONN_TYPE );
strcat( cmd_buf, "\",\"" );
strcat( cmd_buf, REMOTE_IP );
strcat( cmd_buf, "\"," );
strcat( cmd_buf, REMOTE_PORT );
lteiot14_send_cmd_par ( <eiot14, LTEIOT14_CMD_OPEN_TCP_UDP_CONNECTION, cmd_buf );
error_flag |= lteiot14_read_response( ctx, LTEIOT14_RSP_OK );
// Get message length
uint8_t message_len_buf[ 5 ] = { 0 };
uint16_t message_len = strlen( MESSAGE_CONTENT );
uint16_to_str( message_len, message_len_buf );
l_trim( message_len_buf );
r_trim( message_len_buf );
log_printf( &logger, ">>> Write message to TCP connection.\r\n" );
strcpy( cmd_buf, TCP_CID );
strcat( cmd_buf, "," );
strcat( cmd_buf, message_len_buf );
lteiot14_send_cmd_par ( <eiot14, LTEIOT14_CMD_SEND_DATA_VIA_CONNECTION, cmd_buf );
Delay_ms ( 100 );
lteiot14_generic_write ( <eiot14, MESSAGE_CONTENT, message_len );
error_flag |= lteiot14_read_response( ctx, LTEIOT14_URC_RECEIVED_DATA );
log_printf( &logger, ">>> Read response from TCP connection.\r\n" );
lteiot14_send_cmd_par( <eiot14, LTEIOT14_CMD_RECEIVE_DATA_VIA_CONNECTION, cmd_buf );
error_flag |= lteiot14_read_response( ctx, LTEIOT14_RSP_OK );
log_printf( &logger, ">>> Write message to UDP connection.\r\n" );
strcpy( cmd_buf, UDP_CID );
strcat( cmd_buf, "," );
strcat( cmd_buf, message_len_buf );
lteiot14_send_cmd_par ( <eiot14, LTEIOT14_CMD_SEND_DATA_VIA_CONNECTION, cmd_buf );
Delay_ms ( 100 );
lteiot14_generic_write ( <eiot14, MESSAGE_CONTENT, message_len );
error_flag |= lteiot14_read_response( ctx, LTEIOT14_URC_RECEIVED_DATA );
log_printf( &logger, ">>> Read response from UDP connection.\r\n" );
lteiot14_send_cmd_par( <eiot14, LTEIOT14_CMD_RECEIVE_DATA_VIA_CONNECTION, cmd_buf );
error_flag |= lteiot14_read_response( ctx, LTEIOT14_RSP_OK );
log_printf( &logger, ">>> Close TCP connection.\r\n" );
lteiot14_send_cmd_par ( <eiot14, LTEIOT14_CMD_CLOSE_TCP_UDP_CONNECTION, TCP_CID );
error_flag |= lteiot14_read_response( ctx, LTEIOT14_RSP_OK );
log_printf( &logger, ">>> Close UDP connection.\r\n" );
lteiot14_send_cmd_par ( <eiot14, LTEIOT14_CMD_CLOSE_TCP_UDP_CONNECTION, UDP_CID );
error_flag |= lteiot14_read_response( ctx, LTEIOT14_RSP_OK );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
#elif ( DEMO_EXAMPLE == EXAMPLE_SMS )
// Check SMS mode
#define CMGF_PDU "+CMGF: 0"
#define CMGF_TXT "+CMGF: 1"
lteiot14_send_cmd_check( <eiot14, LTEIOT14_CMD_SELECT_SMS_FORMAT );
error_flag |= lteiot14_read_response( ctx, LTEIOT14_RSP_OK );
if ( strstr( app_buf, CMGF_PDU ) )
{
// Send SMS in PDU mode
lteiot14_send_sms_pdu( <eiot14, SIM_SMSC, PHONE_NUMBER_TO_MESSAGE, MESSAGE_CONTENT );
error_flag |= lteiot14_read_response( ctx, LTEIOT14_RSP_OK );
}
else if ( strstr( app_buf, CMGF_TXT ) )
{
// Send SMS in TXT mode
lteiot14_send_sms_text ( <eiot14, PHONE_NUMBER_TO_MESSAGE, MESSAGE_CONTENT );
error_flag |= lteiot14_read_response( ctx, LTEIOT14_RSP_OK );
}
// 30 seconds delay
for ( uint8_t delay_cnt = 0; delay_cnt < 30; delay_cnt++ )
{
Delay_ms ( 1000 );
}
#elif ( DEMO_EXAMPLE == EXAMPLE_GNSS )
log_printf( &logger, ">>> Get GNSS info.\r\n" );
lteiot14_send_cmd ( <eiot14, LTEIOT14_CMD_GET_GNSS_INFO );
error_flag |= lteiot14_read_response( ctx, LTEIOT14_RSP_OK );
Delay_ms ( 1000 );
#else
#error "No demo example selected"
#endif
return error_flag;
}
// ------------------------------------------------------------------------ END
Additional Support
Resources
Category:LTE IoT