nRF9160 does not connect to network

I have a nRF9160-DK but it will not connect to the network. I also have a Thingy:91 that will connect to the network.

Thingy:91 test:

> AT+CEREG=5

OK
> AT+CSCON=1

OK
> AT%XSYSTEMMODE=1,1,1,0

OK
> AT+CFUN=1

OK

+CEREG: 2,"7B0D","000A150C",7

+CSCON: 1

+CEREG: 1,"7B0D","000A150C",7,,,"00001010","11000010"

+CSCON: 0

nRF9160-DK test:

> AT+CEREG=5

OK
> AT+CSCON=1

OK
> AT%XSYSTEMMODE=1,1,1,0

OK
> AT+CFUN=1

OK

+CEREG: 2,"7B0D","000A150C",7

The nRF9160-DK is stuck on stat 2, "2 – Not registered, but UE is currently trying to attach or searching an operator to register to", while the Thingy:91 with the same simcard will go to stat 1, "1 – Registered, home network".

What can be the problem and how to fix this, having the problem with the nRF9160-DK all day now and for debugging purposes I programmed them both with newest modem firmware and Serial LTE Modem to find out this difference with the same simcard at the same location?

  • What happens if you power-cycle the device?

  • Also, if that does not help. Could you try programming the AT Client sample and issue the following commands:

  • It does not help, you just have to wait for 30 minutes I think, after that it starts working again, but if I reset the device too much I think it is in this RESET LOOP again.

    Like my last question;

    In the attachment you can see the Asset Tracker has the same problem with the RESET LOOP. It says 'Power-cycle the device to circumvent this restriction.' but the documentation you send says 'When the reset count reaches the limit, the blocking restriction is written to Non-volatile Memory (NVM). The wait time cannot be bypassed after the wait has started. If the modem is reset during the wait period, the wait period is restarted with the initial wait period.'?

    I think the last is correct and the first not, so I do not think you can circumvent it?

  • Just waiting for half an hour solves the problem.

  • Happy to hear! Thumbsup

1 2