Custom board with nRF9160 - +CEREG=5,4

[shak2300]

Hi I created a custom board with nRF9160SiP

I follow the same schematic og Thingy:91

I ran some tests with VNA to see if the antenna matching was correct, and I see that I have a VSWR of 2.5:1, so it should be fine.

The problem occurs when I run the following commands:

[shak2300]

Now I have this



It seems like: 

• AT+CEREG? returns:
  +CEREG: 5,2,"0A2B","010C0102",7
  This means you are subscribed to level 5 notifications, and the current status is 2 (searching for operator).

  Then:
  
  

  • Later, you see:
    +CEREG: 2
+CEREG: 4
    This means the modem is first searching for an operator (2), then enters an unknown state (4), which typically means it is out of E-UTRAN coverage or cannot find a suitable network.

[Øyvind]

Hello, 

What SIM card are you testing with? Do you get the same results on the Thingy:91 or nRF9160DK when running the same SIM and code?

Kind regards,
Øyvind

[shak2300]

Hi,

I'm using the same SIM of nRF9160DK the iBasis SIM.

With the nRF9160DK I have no issues.

[Øyvind]

Have you had your custom board reviewed? Is the design the same as Thingy:91?

A modem trace would be beneficial in this case. While running the AT client on the nRF9160 SiP, collect modem traces using the cellular monitor.

[shak2300]

Hi, I found the problem. The confugartion of MAGPIO are wrong.
I invert MSB with LSB.
Now I have issues with security tags

%CMNG: 12,3,"9B0C8FE7D4B23027A282FBDDAA4A8FE6640C6E6F5D85F9005ACA8AE0BCED1ED4"
%CMNG: 12,4,"ED75D2209650827687DFC4F68F33ADF1A74E591253F694D80EFD63085C113B22"
%CMNG: 4294967293,10,"2C43952EE9E000FF2ACC4E2ED0897C0A72AD5FA72C3D934E81741CBD54F05BD1"
%CMNG: 4294967294,6,"7A9AF8725C83AE0BA1FBC3ADFB18499264B18A01A0773836C5DF12CF26BA46D7"
%CMNG: 4294967292,11,"2027C4699EAA90A414D33FA81B975C0FDEDEFB04A19CEA1ED43A8876CAD31E89"
OK

I don't know what can I erase. Another thing I don't know what is the procedure for have the connection with nrfcloud. I need for the cellular localisation

[Øyvind]

Hi, please open a new ticket for the issue with the security tags. Add information on what exactly the issue is. Please make sure to follow our documentation for both nRF Connect SDK and nRF Cloud under docs.nordicsemi.com

Kind regards,
Øyvind