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

How to

Hi Nordic team

At sdk connect sample/mqtt_simple, it called lte_lc_init_and_connect() to connect NBIOT or LTE-M.

If this call was not successful, could we read error code to analyze the root cause?

For example,

1. SIM card interface issue.

2. Base station didn't response.

3. The strength of signal from base station was too weak to communicate.

4. And so on.

Thanks.

Jeff 

Parents
  • Hi,

    When using lte_lc_init_and_connect, there unfortunately aren't much other feedback than ETIMEDOUT.

    However, if you register an event handler, you can get more information.

    SIM card issues usually causes a +CEREG: 90 notification. If the device was not allowed to connect to the networks, you can find the reject cause in the +CEREG notifications, and the registration status will usually be 3 or 4.

    Using the at_notif library, you can also subscribe to %MDMEV notifications, which also can contain useful information.

    Best regards,

    Didrik

Reply
  • Hi,

    When using lte_lc_init_and_connect, there unfortunately aren't much other feedback than ETIMEDOUT.

    However, if you register an event handler, you can get more information.

    SIM card issues usually causes a +CEREG: 90 notification. If the device was not allowed to connect to the networks, you can find the reject cause in the +CEREG notifications, and the registration status will usually be 3 or 4.

    Using the at_notif library, you can also subscribe to %MDMEV notifications, which also can contain useful information.

    Best regards,

    Didrik

Children
Related