Problems connecting to LTE

I am having problems connecting to LTE and AWS.

We had consultants developing the prototype code, and it worked perfectly on our 3 first hardware revisions (custom product, fixed antenna matching without RF switch). In revision 4 and 5, we added RF switches (like the Thingy91, different switch, but same passive values). And we also changed developers to a professional house for production code. After that it didn't work.

We see this:

00> +CEREG notification: +CEREG: 2,"0EDC","0211A81C",9
00> Network registration status: 2LTE mode: 9Dispatching events: - handler=0x00022F85 - handler=0x0000D189DoneDispatching events: - handler=0x00022F85 - handler=0x0000D189Done+CSCON notificationDispatching events: - handler=0x00022F85 - handler=0x0000D189Done+CEREG notification: +CEREG: 2,"0EDC","0211A81C",9,0,14
00> Network registration status: 2LTE mode: 9+CSCON notificationDispatching events: - handler=0x00022F85 - handler=0x0000D189Done+CEREG notification: +CEREG: 2
00> Network registration status: 2LTE mode not found, error code: -22Dispatching events: - handler=0x00022F85 - handler=0x0000D189DoneDispatching events: - handler=0x00022F85 - handler=0x0000D189Done

I ran network scan and connect in LTE Link Monitor, and all revisions work. Modem, UICC, LTE, PDN are all green, and I see network and signal strength.

What could be the problem?

Parents
  • Hello,

    it's better if you include a modem trace, and the full AT log.

  • I'll supply Trace Collector in a few hours.

    AT log is new to me :) How do I proceed? The log I sent in the initial post is from the debug console (RTT viewer).

  • okwestern said:
    AT log is new to me :) How do I proceed?

    Enable "automatic requests in Link Monitor

    Then run AT+CFUN=1 and AT+CFUN?.

  • Sorry for the delay. The AT log (with at_client sample):

    AT+CFUN?
    +CFUN: 1
    OK
    AT+CGSN=1+CGSN: "351358811350120"
    OK
    AT+CGMINordic Semiconductor ASA
    OK
    AT+CGMMnRF9160-SICA
    OK
    AT+CGMRmfw_nrf9160_1.3.6
    OK
    AT+CEMODE?
    +CEMODE: 2
    OK
    AT%XCBAND=?
    %XCBAND: (1,2,3,4,5,8,12,13,18,19,20,25,26,28,66)
    OK
    AT+CMEE?
    +CMEE: 0
    OK
    AT+CMEE=1
    OK
    AT+CNEC?
    +CNEC: 0
    OK
    AT+CNEC=24
    OK
    AT+CGEREP?
    +CGEREP: 0,0
    OK
    AT+CGDCONT?
    OK
    AT+CGACT?
    OK
    AT+CGEREP=1
    OK
    AT+CIND=1,1,1
    OK
    AT+CEREG=5
    OK
    AT+CEREG?
    +CEREG: 5,4
    OK
    AT%CESQ=1
    OK
    AT+CESQ+CESQ: 99,99,255,255,255,255
    OK
    AT%XSIM=1
    OK
    AT%XSIM?
    %XSIM: 1
    OK
    AT+CPIN?
    +CPIN: READY
    OK
    AT+CPINR="SIM PIN"+CPINR: "SIM PIN",3
    OK
    AT+CIMI242050801135499
    OK
    14:37:17.305	Using nrf-device-lib-js version: 0.6.12
    14:37:17.305	Using nrf-device-lib version: 0.15.3
    14:37:17.305	Using nrfjprog DLL version: 10.19.1
    14:37:17.305	Using JLink version: JLink_V7.94e
    14:37:20.942	Modem port is opened
    14:37:21.144	Nordic Semiconductor ASA nRF9160-SICA [mfw_nrf9160_1.3.6] SerNr: 351358811350120
    14:37:21.806	IMSIdentity: 242050801135499

    I need some guidance with modem trace. Do I need to call trace functions within my application code?

    Or can I get results with the at_client sample?

    I compiled both (my app + at_client) with these flags, but don't see any trace output:

    CONFIG_NRF_MODEM_LIB_TRACE=y
    CONFIG_AT_HOST_LIBRARY=y
    CONFIG_NRF_MODEM_LIB_TRACE_BACKEND_RTT=y
     

    And how do I connect Cellular Monitor to see/dump the trace output (since it's over RTT)? If I select J-Link, it shows the J-Link "on-board" serial interface as "Cellular Monitor - modem trace serial port". Should I  CONFIG_NRF_MODEM_LIB_TRACE_BACKEND_RTT=n  and use the debug/console serial port from dts-file?

Reply
  • Sorry for the delay. The AT log (with at_client sample):

    AT+CFUN?
    +CFUN: 1
    OK
    AT+CGSN=1+CGSN: "351358811350120"
    OK
    AT+CGMINordic Semiconductor ASA
    OK
    AT+CGMMnRF9160-SICA
    OK
    AT+CGMRmfw_nrf9160_1.3.6
    OK
    AT+CEMODE?
    +CEMODE: 2
    OK
    AT%XCBAND=?
    %XCBAND: (1,2,3,4,5,8,12,13,18,19,20,25,26,28,66)
    OK
    AT+CMEE?
    +CMEE: 0
    OK
    AT+CMEE=1
    OK
    AT+CNEC?
    +CNEC: 0
    OK
    AT+CNEC=24
    OK
    AT+CGEREP?
    +CGEREP: 0,0
    OK
    AT+CGDCONT?
    OK
    AT+CGACT?
    OK
    AT+CGEREP=1
    OK
    AT+CIND=1,1,1
    OK
    AT+CEREG=5
    OK
    AT+CEREG?
    +CEREG: 5,4
    OK
    AT%CESQ=1
    OK
    AT+CESQ+CESQ: 99,99,255,255,255,255
    OK
    AT%XSIM=1
    OK
    AT%XSIM?
    %XSIM: 1
    OK
    AT+CPIN?
    +CPIN: READY
    OK
    AT+CPINR="SIM PIN"+CPINR: "SIM PIN",3
    OK
    AT+CIMI242050801135499
    OK
    14:37:17.305	Using nrf-device-lib-js version: 0.6.12
    14:37:17.305	Using nrf-device-lib version: 0.15.3
    14:37:17.305	Using nrfjprog DLL version: 10.19.1
    14:37:17.305	Using JLink version: JLink_V7.94e
    14:37:20.942	Modem port is opened
    14:37:21.144	Nordic Semiconductor ASA nRF9160-SICA [mfw_nrf9160_1.3.6] SerNr: 351358811350120
    14:37:21.806	IMSIdentity: 242050801135499

    I need some guidance with modem trace. Do I need to call trace functions within my application code?

    Or can I get results with the at_client sample?

    I compiled both (my app + at_client) with these flags, but don't see any trace output:

    CONFIG_NRF_MODEM_LIB_TRACE=y
    CONFIG_AT_HOST_LIBRARY=y
    CONFIG_NRF_MODEM_LIB_TRACE_BACKEND_RTT=y
     

    And how do I connect Cellular Monitor to see/dump the trace output (since it's over RTT)? If I select J-Link, it shows the J-Link "on-board" serial interface as "Cellular Monitor - modem trace serial port". Should I  CONFIG_NRF_MODEM_LIB_TRACE_BACKEND_RTT=n  and use the debug/console serial port from dts-file?

Children
Related