This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

nRF9160DK can't connect to LTE Network (iBasis and Altice SIM)

Hello, DevZoners!

Hope you all doing great!

I have 2 9160DK's and for a few weeks now I've been trying to connect to the LTE network and then connect to the nRF Cloud (for the example of the at client and asset tracker) and so far without success.

I'm located in the north of Portugal, and reading the threads on DevZone about iBasis SIM a question came up: In the issue of network coverage NETWORK COVERAGE | iBASIS in Portgual, iBasis SIM says it's LTE-M national coverage, but when I look at Mobile IoT deployment Map GSMA | Mobile IoT Deployment Map | Internet of Things in Portugal shows NB-IoT nationwide coverage, so when loading .hex file to asset tracker DK should I load LTE-M or NB-IoT example?

With the previous question, I purchased an Altice M2M SIM to try to connect using the NB-IoT network (which I'm sure the NB-IoT coverage is supported), the connection attempts were also made with the iBasis SIM, and by the example of the AT Client it is always looking for the network and the connection never is established.

I don't know what is the issue for not getting the connection. 

Any help I would appreciate a lot!!!

Best Regards, Caio.

Below I attach the logs and photos of the AT client using iBasis. I will soon send the log and photos using Altice's SIM.

2021-09-20T14_50_01.694Z-log.txtibasis SIM

Parents
  • Hello Caio, 

    From the logs you provided, the first thing that pops out is:

    2021-09-20T15:02:21.659Z DEBUG modem << +CEREG: 2,"BAC2","0012316F",9
    2021-09-20T15:02:24.672Z DEBUG modem << +CNEC_ESM: 111,0
    2021-09-20T15:02:24.679Z DEBUG modem << +CNEC_EMM: 15
    2021-09-20T15:02:24.687Z DEBUG modem << +CEREG: 2,"BAC2","0012316F",9,0,15

    Looking at the CEREG documentation we see that it is returning with a reject cause 15 - from 3GPP TS 24.301 Annex A this is described as:

    Cause #15 – No suitable cells in tracking area
    This EMM cause is sent to the UE if it requests service, or if the network initiates a detach request, in a tracking
    area where the UE, by subscription, is not allowed to operate, but when it should find another allowed tracking
    area or location area in the same PLMN or an equivalent PLMN.

    From 3GPP TS 24.008 - Annex H, subclause H.6.8 - Cause No. 111 "protocol error, unspecified", This cause is used to report a protocol error event only when no other cause in the protocol error class applies.

    With what SIM did you get this log? Do you get the same with the Altice M2M SIM?

    Kind regards,
    Øyvind

Reply
  • Hello Caio, 

    From the logs you provided, the first thing that pops out is:

    2021-09-20T15:02:21.659Z DEBUG modem << +CEREG: 2,"BAC2","0012316F",9
    2021-09-20T15:02:24.672Z DEBUG modem << +CNEC_ESM: 111,0
    2021-09-20T15:02:24.679Z DEBUG modem << +CNEC_EMM: 15
    2021-09-20T15:02:24.687Z DEBUG modem << +CEREG: 2,"BAC2","0012316F",9,0,15

    Looking at the CEREG documentation we see that it is returning with a reject cause 15 - from 3GPP TS 24.301 Annex A this is described as:

    Cause #15 – No suitable cells in tracking area
    This EMM cause is sent to the UE if it requests service, or if the network initiates a detach request, in a tracking
    area where the UE, by subscription, is not allowed to operate, but when it should find another allowed tracking
    area or location area in the same PLMN or an equivalent PLMN.

    From 3GPP TS 24.008 - Annex H, subclause H.6.8 - Cause No. 111 "protocol error, unspecified", This cause is used to report a protocol error event only when no other cause in the protocol error class applies.

    With what SIM did you get this log? Do you get the same with the Altice M2M SIM?

    Kind regards,
    Øyvind

Children
No Data
Related