This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

LED 3 blinking and LTE connection not successfull

Hi , 

I followed the getting started steps and enabled the global sim. Now the LED 3 is blinking . 

In the LTE Link Monitor ,  I see the following : 

2020-07-22T03:16:51.579Z DEBUG modem << [00:00:00.243,988] \x1B[0m<dbg> nrf_cloud_transport.nct_topics_populate: accepted_topic: nrf-352656100365454/shadow/get/accepted\x1B[0m\x0D\x0A
2020-07-22T03:16:51.581Z DEBUG modem << [00:00:00.255,523] \x1B[0m<dbg> nrf_cloud_transport.nct_topics_populate: rejected_topic: $aws/things/nrf-352656100365454/shadow/get/rejected\x1B[0m\x0D\x0A
2020-07-22T03:16:51.603Z DEBUG modem << [00:00:00.268,096] \x1B[0m<dbg> nrf_cloud_transport.nct_topics_populate: update_delta_topic: $aws/things/nrf-352656100365454/shadow/update/delta\x1B[0m\x0D\x0A
2020-07-22T03:16:51.606Z DEBUG modem << [00:00:00.280,975] \x1B[0m<dbg> nrf_cloud_transport.nct_topics_populate: update_topic: $aws/things/nrf-352656100365454/shadow/update\x1B[0m\x0D\x0A
2020-07-22T03:16:51.614Z DEBUG modem << [00:00:00.292,816] \x1B[0m<dbg> nrf_cloud_transport.nct_topics_populate: shadow_get_topic: $aws/things/nrf-352656100365454/shadow/get\x1B[0m\x0D\x0A
2020-07-22T03:16:51.637Z DEBUG modem << [00:00:00.305,053] \x1B[0m<inf> asset_tracker: Connecting to LTE network. \x1B[0m\x0D\x0A
2020-07-22T03:16:51.639Z DEBUG modem << [00:00:00.311,828] \x1B[0m<inf> asset_tracker: This may take several minutes.\x1B[0m\x0D\x0A
2020-07-22T03:16:51.644Z DEBUG modem << [00:00:00.326,843] \x1B[0m<dbg> lte_lc.w_lte_lc_connect: Network mode: AT%XSYSTEMMODE=1,0,1,0\x1B[0m\x0D\x0A
2020-07-22T03:17:52.486Z DEBUG modem << +CEREG: 2,"FFFE","FFFFFFFF",7,0,0,"11100000","11100000"\x0D\x0A
2020-07-22T03:17:52.516Z DEBUG modem << [00:01:01.177,795] \x1B[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 2\x1B[0m\x0D\x0A

How to establish the LTE connection ? Am I missing anything ?

Parents Reply Children
  • Hi , 

    I tried flashing all the firmwares . But still this is the output:

    2020-07-22T09:28:18.574Z DEBUG modem >> AT+CEREG?\x0D\x0A
    2020-07-22T09:28:18.591Z DEBUG modem << +CEREG: 5,2,"FFFE","FFFFFFFF",9,0,0,"11100000","11100000"\x0D\x0A
    2020-07-22T09:28:18.594Z DEBUG modem << OK\x0D\x0A
    2020-07-22T09:28:42.880Z DEBUG modem << [00:10:00.376,861] \x1B[0m<inf> lte_lc: Network connection attempt timed out\x1B[0m\x0D\x0A
    2020-07-22T09:28:42.915Z DEBUG modem << +CEREG: 0,"FFFE","FFFFFFFF",9,0,0,"11100000","11100000"\x0D\x0A
    2020-07-22T09:28:42.927Z DEBUG modem << [00:10:00.420,623] \x1B[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 0\x1B[0m\x0D\x0A
    2020-07-22T09:28:42.931Z DEBUG modem << [00:10:00.429,016] \x1B[0m<inf> lte_lc: Using fallback network mode\x1B[0m\x0D\x0A
    2020-07-22T09:28:42.945Z DEBUG modem << [00:10:00.435,150] \x1B[0m<dbg> lte_lc.w_lte_lc_connect: Network mode: AT%XSYSTEMMODE=1,0,1,0\x1B[0m\x0D\x0A

  • My apologies for referring to the wrong hex image. You should use nrf9160dk_asset_tracker_nbiot_2020-04-29_bc7ade8b.hex or nrf9160dk_asset_tracker_nbiot_legacy_pco_2020-04-29_bc7ade8b.hex.

    If this still does not work, I will need to have a full log from the LTE Link Monitor. Also, can you issue the command CFUN? in the command line of LTE Link Monitor? 

    Do you have access to a SIM from your local network provider? This needs to be enabled for NB-IoT. iBasis might not be supported in your country. 

    Kind regards,
    Øyvind

  • OKay fine. will flash and collect the logs,

    BTW ,  i was using the iBasis SIM. I will check with the local network provided for NB-IoT . 

Related