nRF9160: Odd results from +CEREG

Our device connects to a cell tower and then creates a socket to our gateway. I monitor +CEREG to see what it goes through to connect to a cell tower. Below is the meaning of the first two values. I'm mostly concerned with the second parameter.

+CEREG: <n>,<stat>[,[<tac>],[<ci>],[<AcT>][,<cause_type>],[<reject_cause>][,[<Active-Time>],[<Periodic-TAU>]]]]
<n>
0 – Unsubscribe unsolicited result codes
1 – Subscribe unsolicited result codes +CEREG:<stat>
2 – Subscribe unsolicited result codes +CEREG:<stat>[,<tac>,<ci>,<AcT>]
3 – Subscribe unsolicited result codes +CEREG:<stat>[,<tac>,<ci>,<AcT>[,<cause_type>,<reject_cause>]]
4 – Subscribe unsolicited result codes +CEREG: <stat>[,[<tac>],[<ci>],[<AcT>][,,[,[<Active-Time>],[<Periodic-TAU>]]]]
5 – Subscribe unsolicited result codes +CEREG: <stat>[,[<tac>],[<ci>],[<AcT>][,[<cause_type>],[<reject_cause>][,[<Active-Time>],[<Periodic-TAU>]]]]
<stat>
0 – Not registered. User Equipment (UE) is not currently searching for an operator to register to.
1 – Registered, home network
2 – Not registered, but UE is currently trying to attach or searching an operator to register to
3 – Registration denied
4 – Unknown (for example, out of Evolved Terrestrial Radio Access Network (E-UTRAN) coverage)
5 – Registered, roaming
90 – Not registered due to Universal Integrated Circuit Card (UICC) failure

Any idea why I would see the below +CEREG?

+CEREG: 0,4
+CEREG: 0,2

It may go on for a while with the above values until it connects with a +CEREG: 0,1.

Why would it return "2 – Not registered" or "4 – Unknown"?

  • Hi Howard,

    What is your current MFW version? Have you updated to the latest? Compatible Downloads - nordicsemi.com

    Can you share the log of your whole test? You can find a log like below with LTE Link Monitor.

    2022-02-17T10:18:32.371Z INFO Application data folder: C:\Users\chs1\AppData\Roaming\nrfconnect\pc-nrfconnect-linkmonitor
    2022-02-17T10:18:32.434Z DEBUG App pc-nrfconnect-linkmonitor v2.0.0 official
    2022-02-17T10:18:32.434Z DEBUG App path: C:\Users\chs1\.nrfconnect-apps\node_modules\pc-nrfconnect-linkmonitor
    2022-02-17T10:18:32.434Z DEBUG nRFConnect 3.10.0, required by the app is (^3.8.0)
    2022-02-17T10:18:32.435Z DEBUG nRFConnect path: C:\Users\chs1\AppData\Local\Programs\nrfconnect\resources\app.asar
    2022-02-17T10:18:32.435Z DEBUG HomeDir: C:\Users\chs1
    2022-02-17T10:18:32.435Z DEBUG TmpDir: C:\Users\chs1\AppData\Local\Temp
    2022-02-17T10:18:34.638Z INFO Modem port is opened
    2022-02-17T10:18:42.840Z DEBUG modem >> AT+CFUN?
    2022-02-17T10:18:42.855Z DEBUG modem << +CFUN: 4
    2022-02-17T10:18:42.866Z DEBUG modem << OK
    2022-02-17T10:18:55.352Z DEBUG modem >> AT+CEREG=2
    2022-02-17T10:18:55.365Z DEBUG modem << OK
    2022-02-17T10:19:01.103Z DEBUG modem >> AT+CFUN?
    2022-02-17T10:19:01.116Z DEBUG modem << +CFUN: 4
    2022-02-17T10:19:01.124Z DEBUG modem << OK
    2022-02-17T10:19:02.751Z DEBUG modem >> AT+CFUN=1
    2022-02-17T10:19:02.792Z DEBUG modem << OK
    2022-02-17T10:19:03.496Z DEBUG modem << +CEREG: 2,"7789","031B4300",7
    2022-02-17T10:19:04.266Z DEBUG modem << +CEREG: 1,"7789","031B4300",7
    

    Best regards,

    Charlie

  • MFW version is 1.3.0. Didn't know of the LTE Link Monitor. Will have to try it out.

  • Hi Howard,

    The latest MFW version is 1.3.1, please update it and share your log file after trying it.

    Best regards,

    Charlie

Related