TOP Contributors

  1. MIKROE (2663 codes)
  2. Alcides Ramos (358 codes)
  3. Shawon Shahryiar (307 codes)
  4. jm_palomino (112 codes)
  5. Chisanga Mumba (90 codes)
  6. S P (73 codes)
  7. dany (71 codes)
  8. MikroBUS.NET Team (35 codes)
  9. NART SCHINACKOW (34 codes)
  10. Armstrong Subero (27 codes)

Most Downloaded

  1. Timer Calculator (137116 times)
  2. FAT32 Library (70239 times)
  3. Network Ethernet Library (56131 times)
  4. USB Device Library (46445 times)
  5. Network WiFi Library (42094 times)
  6. FT800 Library (41409 times)
  7. GSM click (29124 times)
  8. mikroSDK (26567 times)
  9. PID Library (26509 times)
  10. microSD click (25491 times)
Libstock prefers package manager

Package Manager

We strongly encourage users to use Package manager for sharing their code on Libstock website, because it boosts your efficiency and leaves the end user with no room for error. [more info]

< Back
mikroSDK Library

4G LTE-E click

Rating:

0

Author: MIKROE

Last Updated: 2024-04-03

Package Version: 2.1.0.14

mikroSDK Library: 2.0.0.0

Category: GSM/LTE

Downloaded: 109 times

Not followed.

License: MIT license  

4G LTE click is an LTE Cat 1 / 2G multimode cellular network solution, featuring the compact LARA-R2 series modem from u-blox. This module supports up to three LTE bands and GSM bands. It also features a full range of options for the high speed cellular networking and communication, such as the network indication, full embedded TCP/UDP stack, HTTP and HTTPS transfer protocols, IPv4/IPv6 dual-stack support, secondary antenna for the RX diversity, antenna detection, jamming signal detection, embedded TLS 1.2 protocol for the improved security and more. 4G LARA click can achieve data rates up to 10.3 Mbps/5.2 Mbps (downlink/uplink).

No Abuse Reported

Do you want to subscribe in order to receive notifications regarding "4G LTE-E click" changes.

Do you want to unsubscribe in order to stop receiving notifications regarding "4G LTE-E click" changes.

Do you want to report abuse regarding "4G LTE-E click".

  • mikroSDK Library 1.0.0.0
  • Comments (0)

mikroSDK Library Blog


4G LTE-E click

4G LTE click is an LTE Cat 1 / 2G multimode cellular network solution, featuring the compact LARA-R2 series modem from u-blox. This module supports up to three LTE bands and GSM bands. It also features a full range of options for the high speed cellular networking and communication, such as the network indication, full embedded TCP/UDP stack, HTTP and HTTPS transfer protocols, IPv4/IPv6 dual-stack support, secondary antenna for the RX diversity, antenna detection, jamming signal detection, embedded TLS 1.2 protocol for the improved security and more. 4G LARA click can achieve data rates up to 10.3 Mbps/5.2 Mbps (downlink/uplink).

4g-lte-e-click.png

click Product page


Click library

  • Author : Stefan Ilic
  • Date : Jun 2021.
  • Type : UART type

Software Support

We provide a library for the C4GLTEE 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 from NECTO Studio Package Manager(recommended way), downloaded from our LibStock™ or found on Mikroe github account.

Library Description

This library contains API for C4GLTEE Click driver.

Standard key functions :

  • c4gltee_cfg_setup Config Object Initialization function.

    void c4gltee_cfg_setup ( c4gltee_cfg_t *cfg );
  • c4gltee_init Initialization function.

    err_t c4gltee_init ( c4gltee_t *ctx, c4gltee_cfg_t *cfg );

Example key functions :

  • c4gltee_module_power_on This function powers ON the module.

    void c4gltee_module_power_on ( c4gltee_t *ctx );
  • c4gltee_send_cmd_with_parameter This function sends a command with specified parameter to the click module.

    void c4gltee_send_cmd_with_parameter ( c4gltee_t *ctx, char *at_cmd_buf, char *param_buf );
  • c4gltee_send_cmd_parameter_check This function checks the command that is sent.

    void c4gltee_send_cmd_parameter_check ( c4gltee_t *ctx, char *at_cmd_buf );

Example Description

This example reads and processes data from 4G LTE E click.

The demo application is composed of two sections :

Application Init

Initializes the driver and powers up the module, then sets default configuration for connecting the device to network.


void application_init ( void ) {
    log_cfg_t log_cfg;  /**< Logger config object. */
    c4gltee_cfg_t c4gltee_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.

    c4gltee_cfg_setup( &c4gltee_cfg );
    C4GLTEE_MAP_MIKROBUS( c4gltee_cfg, MIKROBUS_1 );
    c4gltee_init( &c4gltee, &c4gltee_cfg );

    c4gltee_module_power_on( &c4gltee );

    // dummy read
    c4gltee_process( );
    c4gltee_clear_app_buf( );

    // AT
    c4gltee_send_cmd( &c4gltee, C4GLTEE_CMD_AT );
    app_error_flag = c4gltee_rsp_check( );
    c4gltee_error_check( app_error_flag );
    Delay_ms ( 500 );

    // ATI - product information
    c4gltee_send_cmd( &c4gltee, C4GLTEE_CMD_ATI );
    app_error_flag = c4gltee_rsp_check(  );
    c4gltee_error_check( app_error_flag );
    Delay_ms ( 500 );

    // CGMR - firmware version
    c4gltee_send_cmd( &c4gltee, C4GLTEE_CMD_CGMR );
    app_error_flag = c4gltee_rsp_check(  );
    c4gltee_error_check( app_error_flag );
    Delay_ms ( 500 );

    // CMEE - Report Mobile Equipment Error
    c4gltee_send_cmd_with_parameter( &c4gltee, C4GLTEE_CMD_CMEE, "2" );
    app_error_flag = c4gltee_rsp_check(  );
    c4gltee_error_check( app_error_flag );
    Delay_ms ( 500 );

    // COPS - deregister from network
    c4gltee_send_cmd_with_parameter( &c4gltee, C4GLTEE_CMD_COPS, "2" );
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );
    app_error_flag = c4gltee_rsp_check(  );
    c4gltee_error_check( app_error_flag );
    Delay_ms ( 500 );

    // CGDCONT - set sim apn
    c4gltee_set_sim_apn( &c4gltee, SIM_APN );
    app_error_flag = c4gltee_rsp_check(  );
    c4gltee_error_check( app_error_flag );
    Delay_ms ( 500 );

    // CFUN - full funtionality
    c4gltee_send_cmd_with_parameter( &c4gltee, C4GLTEE_CMD_CFUN, "1" );
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );
    app_error_flag = c4gltee_rsp_check(  );
    c4gltee_error_check( app_error_flag );
    Delay_ms ( 500 );

    // COPS - automatic mode
    c4gltee_send_cmd_with_parameter( &c4gltee, C4GLTEE_CMD_COPS, "0" );
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );
    app_error_flag = c4gltee_rsp_check(  );
    c4gltee_error_check( app_error_flag );
    Delay_ms ( 500 );

    // CREG - network registration status
    c4gltee_send_cmd_with_parameter( &c4gltee, C4GLTEE_CMD_CREG, "1" );
    app_error_flag = c4gltee_rsp_check(  );
    c4gltee_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 ( 1000 );
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );
}

Application Task

Waits for device to connect to network and then sends a desired SMS to the selected phone number approximately every 30 seconds.


void application_task ( void ) {
    if ( app_connection_status == WAIT_FOR_CONNECTION ) {
        // CREG - network registration status
        c4gltee_send_cmd_check( &c4gltee, C4GLTEE_CMD_CREG );
        app_error_flag = c4gltee_rsp_check(  );
        c4gltee_error_check( app_error_flag );
        Delay_ms ( 500 );

        // CSQ - signal quality
        c4gltee_send_cmd( &c4gltee, C4GLTEE_CMD_CSQ );
        app_error_flag = c4gltee_rsp_check(  );
        c4gltee_error_check( app_error_flag );
        Delay_ms ( 1000 );
        Delay_ms ( 1000 );
        Delay_ms ( 1000 );
    } else {
        log_info( &logger, "CONNECTED TO NETWORK" );

        // SMS message format - PDU mode
        c4gltee_send_cmd_with_parameter( &c4gltee, C4GLTEE_CMD_CMGF, "0" );
        app_error_flag = c4gltee_rsp_check(  );
        c4gltee_error_check( app_error_flag );
        Delay_ms ( 1000 );
        Delay_ms ( 1000 );
        Delay_ms ( 1000 );

        for( ; ; ) {   
            log_printf( &logger, "> Sending message to phone number...\r\n" );
            c4gltee_send_sms_pdu ( &c4gltee, SIM_SMSC, PHONE_NUMBER_TO_MESSAGE, MESSAGE_CONTENT );
            app_error_flag = c4gltee_rsp_check(  );
            c4gltee_error_check( app_error_flag );
            Delay_ms ( 1000 );
            Delay_ms ( 1000 );
            Delay_ms ( 1000 );
            Delay_ms ( 1000 );
            Delay_ms ( 1000 );
            Delay_ms ( 1000 );
            Delay_ms ( 1000 );
            Delay_ms ( 1000 );
            Delay_ms ( 1000 );
            Delay_ms ( 1000 );
            Delay_ms ( 1000 );
            Delay_ms ( 1000 );
            Delay_ms ( 1000 );
            Delay_ms ( 1000 );
            Delay_ms ( 1000 );
            Delay_ms ( 1000 );
            Delay_ms ( 1000 );
            Delay_ms ( 1000 );
            Delay_ms ( 1000 );
            Delay_ms ( 1000 );
            Delay_ms ( 1000 );
            Delay_ms ( 1000 );
            Delay_ms ( 1000 );
            Delay_ms ( 1000 );
            Delay_ms ( 1000 );
            Delay_ms ( 1000 );
            Delay_ms ( 1000 );
            Delay_ms ( 1000 );
            Delay_ms ( 1000 );
            Delay_ms ( 1000 );
        }
    }
}

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 (required for PDU mode only) 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"

The full application code, and ready to use projects can be installed directly from NECTO Studio Package Manager(recommended way), downloaded from our LibStock™ or found on Mikroe github account.

Other Mikroe Libraries used in the example:

  • MikroSDK.Board
  • MikroSDK.Log
  • Click.4GLTEE

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. UART terminal is available in all MikroElektronika compilers.


ALSO FROM THIS AUTHOR

Stepper 10 click

0

Stepper 10 Click is a two-phase bipolar stepping motor driver capable of controlling one stepper motor with PWM constant current drive. Click's featured chip TB67S128FTG, from Toshiba Semiconductor, fabricated with BiCD process with an output rating of 50V/5A and a built-in decoder can supply the motor with voltage of up to 44V. Toshiba's innovative technology process results in low-power consumption with low on-resistance (0.25Ω) on the integrated MOSFET output stage. The stepper motor can be driven in both directions from full step to 1/128 micro-steps.

[Learn More]

mikromedia for dsPIC33EP - Examples

0

Set of examples for mikromedia for dsPIC33EP.. Provided examples demonstrate working with mikromedia's various features and modules:

- Accelerometer
- MMC SD card
- MP3
- Serial Flash
- TFT
- Touch Panel
- USB

[Learn More]

eFuse 5 click

0

eFuse 5 Click is a compact add-on board with a power path protection solution that limits circuit currents and voltages to safe levels during fault conditions. This board features the TPS16530, an easy-to-use, positive 58V, 4.5A eFuse with a 31mΩ integrated FET from Texas Instruments. This industrial eFuse has programmable undervoltage, overcurrent, inrush current protection, and output current monitoring features. Besides, it allows flexibility to configure the device between the two current-limiting fault responses (latch off and auto-retry).

[Learn More]