NRF9160 doesn't connect over NB-IoT (iBasis and T-mobile, works fine on Cat-M)

I'm using the NRF9160DK, the asset_tracker example works fine over Cat-M together with the iBasis sim.

I want to run my applications on NB-IoT, so I'm trying to connect the DK over NB-IoT, but it doesn't seem to work. It feels like I'm missing a config, but I'm not sure which one.

I'm in North CA in the US, iBasis states NB-IoT should work here.

AT-host example output with iBasis sim:

*** Booting Zephyr OS build v2.1.99-ncs1-1145-g13dc96f83bab  ***
The AT host sample started
AT%XSYSTEMMODE?
%XSYSTEMMODE: 0,1,0,0
OK
AT+CFUN?
+CFUN: 0
OK
AT+CFUN=1
OK
AT+CFUN=1
OK
AT+CFUN?
+CFUN: 1
OK
AT+CGMI
Nordic Semiconductor ASA
OK
AT+CGMM
nRF9160-SICA
OK
AT+CGMR
mfw_nrf9160_1.2.0
OK
AT+CEMODE?+CEMODE: 0
OK
AT%XCBAND=?
%XCBAND: (1,2,3,4,5,8,12,13,17,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=2
OK
AT+CEREG?
+CEREG: 2,0,"FFFE","FFFFFFFF",9
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+CIMI
204080813516911
OK
AT+CEREG=5
OK
%CESQ: 61,3,23,3
+CEREG: 2,"EBB6","0144D3C8",9,0,0,"11100000","11100000"
+CNEC_EMM: 11
+CEREG: 2,"EBB6","0144D3C8",9,0,11,"11100000","11100000"
%CESQ: 61,3,16,2
%CESQ: 55,2,11,1
+CEREG: 2,"8C3C","0A18483B",9,0,11,"11100000","11100000"
+CNEC_EMM: 15
+CEREG: 4,"8C3C","0A18483B",9,0,15,"11100000","11100000"
%CESQ: 255,0,255,0
+CEREG: 4,"FFFE","FFFFFFFF",9,0,15,"11100000","11100000"
%CESQ: 74,3,18,2
+CEREG: 2,"2080","00808C14",9,0,15,"11100000","11100000"
+CNEC_EMM: 15
+CEREG: 4,"2080","00808C14",9,0,15,"11100000","11100000"
%CESQ: 255,0,255,0
+CEREG: 4,"FFFE","FFFFFFFF",9,0,15,"11100000","11100000"
%CESQ: 75,3,18,2
+CEREG: 4,"2080","00808C14",9,0,15,"11100000","11100000"
%CESQ: 75,3,23,3
%CESQ: 70,3,23,3
AT+COPS=?
+CME ERROR: 0
AT+COPS?
+COPS: 0
OK
AT%COPS=?
%COPS: (3,"","","310260",9),(1,"","","311480",9),(1,"","","310410",9)
OK
AT+COPS=?
+CME ERROR: 0

note the `AT+COPS=?` and `+CME ERROR: 0` here. Why am I getting this error, and why does `AT%COPS=?` work instead?

AT host example output with T-mobile sim. This sim works on NB-IoT in a different brand modem, so I'm sure it's not a network issue:

*** Booting Zephyr OS build v2.1.99-ncs1-1145-g13dc96f83bab  ***
The AT host sample started
AT+CFUN?
+CFUN: 0
OK
AT+CFUN=4
OK
AT%XSYSTEMMODE?
%XSYSTEMMODE: 0,1,0,0
OK
AT+CFUN=1
OK
AT+CFUN?
+CFUN: 1
OK
AT+CGSN=1
+CGSN: "352656100381287"
OK
AT+CGMI
Nordic Semiconductor ASA
OK
AT+CGMM
nRF9160-SICA
OK
AT+CGMR
mfw_nrf9160_1.2.0
OK
AT+CEMODE?
+CEMODE: 0
OK
AT%XCBAND=?
%XCBAND: (1,2,3,4,5,8,12,13,17,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=2
OK
AT+CEREG?
+CEREG: 2,0,"FFFE","FFFFFFFF",9
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+CIMI
310240200018620
OK
AT+CEREG=5
OK
AT%XAPNSTATUS?
%XAPNSTATUS: 
OK
AT+COPS=?
+COPS: (1,"","","310260",9),(1,"","","310410",9),(1,"","","311480",9)
OK
+CEREG: 2,"FFFE","FFFFFFFF",9,0,0,"11100000","11100000"

Here `AT+COPS=?` seems to work, but it kind of gives up immediately on connecting?

Am I missing a config somewhere / what can I do to debug this?

Thanks for the help!

Parents
No Data
Reply
  • Thanks for the reply!

    The firmware I was using in the above logs was the simple AT-client (nrf9160dk_at_client_2020-04-29_bc7ade8b.hex), I was trying to connect manually. With just AT commands.

    Here are the logs of the asset tracker example, with- and without ePCO support and with the iBasis sim and t-mobile sim:

    Asset Tracker - iBasis sim - with PCO:

    *** Booting Zephyr OS build v2.1.99-ncs1-1145-g13dc96f83bab  ***
    [00:00:00.192,413] ␛[0m<dbg> nrf9160_gps.setup: MAGPIO set: AT%XMAGPIO=1,0,0,1,1,1574,1577␛[0m
    [00:00:00.201,293] ␛[0m<dbg> nrf9160_gps.setup: COEX0 set: AT%XCOEX0=1,1,1570,1580␛[0m
    [00:00:00.208,984] ␛[0m<inf> asset_tracker: Asset tracker started␛[0m
    [00:00:00.222,442] ␛[0m<dbg> nrf_cloud_transport.nct_client_id_get: client_id = nrf-352656100381287␛[0m
    [00:00:00.231,628] ␛[0m<dbg> nrf_cloud_transport.nct_topics_populate: shadow_base_topic: $aws/things/nrf-352656100381287/shadow␛[0m
    [00:00:00.243,286] ␛[0m<dbg> nrf_cloud_transport.nct_topics_populate: accepted_topic: nrf-352656100381287/shadow/get/accepted␛[0m
    [00:00:00.254,760] ␛[0m<dbg> nrf_cloud_transport.nct_topics_populate: rejected_topic: $aws/things/nrf-352656100381287/shadow/get/rejected␛[0m
    [00:00:00.267,272] ␛[0m<dbg> nrf_cloud_transport.nct_topics_populate: update_delta_topic: $aws/things/nrf-352656100381287/shadow/update/delta␛[0m
    [00:00:00.280,090] ␛[0m<dbg> nrf_cloud_transport.nct_topics_populate: update_topic: $aws/things/nrf-352656100381287/shadow/update␛[0m
    [00:00:00.291,900] ␛[0m<dbg> nrf_cloud_transport.nct_topics_populate: shadow_get_topic: $aws/things/nrf-352656100381287/shadow/get␛[0m
    [00:00:00.304,077] ␛[0m<inf> asset_tracker: Connecting to LTE network. ␛[0m
    [00:00:00.310,821] ␛[0m<inf> asset_tracker: This may take several minutes.␛[0m
    [00:00:00.326,507] ␛[0m<inf> lte_lc: Using legacy LTE PCO mode...␛[0m
    [00:00:00.332,733] ␛[0m<dbg> lte_lc.w_lte_lc_connect: Network mode: AT%XSYSTEMMODE=0,1,1,0␛[0m
    +CEREG: 2,"EBB6","0144D3C8",9,0,0,"11100000","11100000"
    [00:02:13.490,356] ␛[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 2␛[0m
    +CEREG: 2,"EBB6","0144D3C8",9,0,11,"11100000","11100000"
    [00:02:14.002,380] ␛[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 2␛[0m
    +CEREG: 2,"8C3C","0A218E39",9,0,11,"11100000","11100000"
    [00:02:18.650,665] ␛[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 2␛[0m
    +CEREG: 4,"8C3C","0A218E39",9,0,15,"11100000","11100000"
    [00:02:19.257,446] ␛[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 4␛[0m
    +CEREG: 4,"FFFE","FFFFFFFF",9,0,15,"11100000","11100000"
    [00:02:19.539,886] ␛[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 4␛[0m
    +CEREG: 2,"2080","00808C1E",9,0,15,"11100000","11100000"
    [00:02:23.809,967] ␛[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 2␛[0m
    +CEREG: 4,"2080","00808C1E",9,0,15,"11100000","11100000"
    [00:02:24.393,615] ␛[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 4␛[0m
    +CEREG: 4,"FFFE","FFFFFFFF",9,0,15,"11100000","11100000"
    [00:02:24.830,108] ␛[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 4␛[0m
    +CEREG: 4,"2080","00808C1E",9,0,15,"11100000","11100000"
    [00:02:25.311,676] ␛[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 4␛[0m
    [00:10:00.383,636] ␛[0m<inf> lte_lc: Network connection attempt timed out␛[0m
    [00:10:00.443,817] ␛[0m<inf> lte_lc: Using fallback network mode␛[0m
    [00:10:00.450,012] ␛[0m<dbg> lte_lc.w_lte_lc_connect: Network mode: AT%XSYSTEMMODE=1,0,1,0␛[0m
    +CEREG: 2,"417B","0A64020A",7,0,15,"11100000","11100000"
    [00:10:58.342,346] ␛[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 2␛[0m
    +CEREG: 2,"417B","0A64020A",7,0,11,"11100000","11100000"
    [00:10:58.555,786] ␛[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 2␛[0m
    +CEREG: 2,"2000","00808C02",7,0,11,"11100000","11100000"
    [00:11:00.242,340] ␛[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 2␛[0m
    +CEREG: 5,"2000","00808C02",7,,,"11100000","11100000"
    [00:11:06.321,960] ␛[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 5␛[0m
    [00:11:06.330,291] ␛[0m<inf> asset_tracker: Connected to LTE network␛[0m
    [00:11:06.696,166] ␛[0m<dbg> nrf_cloud_transport.nct_connect: IPv4 Address 0x557c5c03␛[0m
    [00:11:06.704,223] ␛[0m<dbg> nrf_cloud_transport.nct_mqtt_connect: mqtt_connect requesting persistent session␛[0m
    [00:11:13.104,553] ␛[0m<inf> aws_jobs: Subscribe: $aws/things/nrf-352656100381287/jobs/notify-next␛[0m
    [00:11:13.114,898] ␛[0m<inf> aws_jobs: Subscribe: $aws/things/nrf-352656100381287/jobs/$next/get/#␛[0m
    [00:11:13.124,755] ␛[0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_CONNACK␛[0m
    [00:11:13.132,965] ␛[0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 2␛[0m
    [00:11:13.140,747] ␛[0m<dbg> nrf_cloud.event_handler: NRF_CLOUD_EVT_TRANSPORT_CONNECTED␛[0m
    [00:11:13.148,834] ␛[0m<inf> asset_tracker: CLOUD_EVT_CONNECTED␛[0m
    [00:11:13.154,937] ␛[0m<inf> asset_tracker: Persistent Sessions = 0␛[0m
    [00:11:13.161,376] ␛[0m<dbg> nrf_cloud_transport.nct_cc_connect: nct_cc_connect␛[0m
    [00:11:13.169,799] ␛[0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 3␛[0m
    [00:11:13.744,384] ␛[0m<inf> aws_fota: subscribed to notify-next topic␛[0m
    [00:11:13.751,190] ␛[0m<inf> aws_jobs: Publish topic: $aws/things/nrf-352656100381287/jobs/$next/get␛[0m
    [00:11:13.760,498] ␛[0m<inf> aws_jobs: Publish payload {"clientToken": ""}␛[0m
    [00:11:14.393,859] ␛[0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_SUBACK: id = 1234 result = 0␛[0m
    [00:11:14.403,961] ␛[0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 4␛[0m
    [00:11:14.411,743] ␛[0m<dbg> nrf_cloud_transport.nct_cc_send: mqtt_publish: id = 5678 opcode = 0 len = 0␛[0m
    [00:11:14.421,966] ␛[0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 5␛[0m
    [00:11:14.429,809] ␛[0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_SUBACK: id = 2114 result = 0␛[0m
    [00:11:15.024,078] ␛[0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_PUBACK: id = 57920 result = 0␛[0m
    [00:11:15.034,637] ␛[0m<dbg> aws_fota.on_publish_evt: Received topic: $aws/things/nrf-352656100381287/jobs/$next/get/accepted␛[0m
    [00:11:15.046,081] ␛[0m<inf> aws_fota: Checking for an available job␛[0m
    [00:11:15.052,703] ␛[0m<dbg> aws_fota.get_job_execution: Job doc: {"clientToken":"","timestamp":1590192994}␛[0m
    [00:11:15.062,835] ␛[0m<dbg> aws_fota.get_job_execution: Got only one field␛[0m
    [00:11:15.069,976] ␛[0m<inf> aws_fota: No queued jobs for this device␛[0m
    [00:11:15.664,123] ␛[0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_PUBACK: id = 5678 result = 0␛[0m
    [00:11:15.674,102] ␛[0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 5␛[0m
    [00:11:15.692,260] ␛[0m<dbg> aws_fota.on_publish_evt: Received topic: nrf-352656100381287/shadow/get/accepted␛[0m
    [00:11:15.702,392] ␛[0m<dbg> aws_fota.on_publish_evt: received an unhandled MQTT publish event on topic: nrf-352656100381287/shadow/get/accepted␛[0m
    [00:11:15.715,637] ␛[0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_PUBLISH: id = 15404 len = 317␛[0m
    [00:11:15.726,531] ␛[0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 5␛[0m
    [00:11:15.734,222] ␛[0m<dbg> nrf_cloud.event_handler: NRF_CLOUD_EVT_RX_DATA␛[0m
    [00:11:15.741,333] ␛[0m<inf> asset_tracker: CLOUD_EVT_DATA_RECEIVED␛[0m
    [00:11:15.748,260] ␛[0m<inf> cloud_codec: [cloud_search_config:898] Found cfg item GPS, enable
    ␛[0m
    [00:11:15.758,911] ␛[0m<dbg> nrf_cloud_transport.nct_dc_endpoint_set: nct_dc_endpoint_set␛[0m
    [00:11:15.767,395] ␛[0m<dbg> nrf_cloud_transport.nct_dc_endpoint_get: nct_dc_endpoint_get␛[0m
    [00:11:15.776,641] ␛[0m<dbg> nrf_cloud_transport.nct_cc_send: mqtt_publish: id = 7890 opcode = 1 len = 329␛[0m
    [00:11:15.788,726] ␛[0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 7␛[0m
    [00:11:15.796,447] ␛[0m<dbg> nrf_cloud.event_handler: NRF_CLOUD_EVT_USER_ASSOCIATED␛[0m
    [00:11:15.804,229] ␛[0m<inf> asset_tracker: CLOUD_EVT_PAIR_DONE␛[0m
    [00:11:16.944,641] ␛[0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_PUBACK: id = 7890 result = 0␛[0m
    [00:11:16.954,650] ␛[0m<dbg> nrf_cloud_transport.nct_dc_connect: nct_dc_connect␛[0m
    [00:11:16.963,073] ␛[0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 8␛[0m
    [00:11:17.584,655] ␛[0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_SUBACK: id = 8765 result = 0␛[0m
    [00:11:17.594,726] ␛[0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 9␛[0m
    [00:11:17.602,416] ␛[0m<dbg> nrf_cloud.event_handler: NRF_CLOUD_EVT_READY␛[0m
    [00:11:17.609,344] ␛[0m<inf> asset_tracker: CLOUD_EVT_READY␛[0m
    [00:11:17.615,844] ␛[0m<dbg> nrf9160_gps.init: GPS socket created, fd: 1232491587␛[0m
    [00:11:17.624,450] ␛[0m<inf> gps_control: GPS initialized␛[0m
    [00:11:17.667,175] ␛[0m<dbg> nrf_cloud_transport.nct_cc_send: mqtt_publish: id = 1 opcode = 1 len = 633␛[0m
    [00:11:18.536,834] ␛[0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_PUBACK: id = 1 result = 0␛[0m
    %CESQ: 56,2,16,2
    %CESQ: 61,3,16,2

    Looks like the modem is trying several towers, then gives up and falls back to Cat-M

    Asset Tracker - iBasis sim - without PCO:

    *** Booting Zephyr OS build v2.1.99-ncs1-1145-g13dc96f83bab  ***
    [00:00:00.256,256] ␛[0m<dbg> nrf9160_gps.setup: MAGPIO set: AT%XMAGPIO=1,0,0,1,1,1574,1577␛[0m
    [00:00:00.274,597] ␛[0m<dbg> nrf9160_gps.setup: COEX0 set: AT%XCOEX0=1,1,1570,1580␛[0m
    [00:00:00.282,653] ␛[0m<inf> asset_tracker: Asset tracker started␛[0m
    [00:00:00.313,049] ␛[0m<dbg> nrf_cloud_transport.nct_client_id_get: client_id = nrf-352656100381287␛[0m
    [00:00:00.322,265] ␛[0m<dbg> nrf_cloud_transport.nct_topics_populate: shadow_base_topic: $aws/things/nrf-352656100381287/shadow␛[0m
    [00:00:00.333,923] ␛[0m<dbg> nrf_cloud_transport.nct_topics_populate: accepted_topic: nrf-352656100381287/shadow/get/accepted␛[0m
    [00:00:00.345,428] ␛[0m<dbg> nrf_cloud_transport.nct_topics_populate: rejected_topic: $aws/things/nrf-352656100381287/shadow/get/rejected␛[0m
    [00:00:00.357,971] ␛[0m<dbg> nrf_cloud_transport.nct_topics_populate: update_delta_topic: $aws/things/nrf-352656100381287/shadow/update/delta␛[0m
    [00:00:00.370,849] ␛[0m<dbg> nrf_cloud_transport.nct_topics_populate: update_topic: $aws/things/nrf-352656100381287/shadow/update␛[0m
    [00:00:00.382,720] ␛[0m<dbg> nrf_cloud_transport.nct_topics_populate: shadow_get_topic: $aws/things/nrf-352656100381287/shadow/get␛[0m
    [00:00:00.394,897] ␛[0m<inf> asset_tracker: Connecting to LTE network. ␛[0m
    [00:00:00.401,672] ␛[0m<inf> asset_tracker: This may take several minutes.␛[0m
    [00:00:00.437,988] ␛[0m<dbg> lte_lc.w_lte_lc_connect: Network mode: AT%XSYSTEMMODE=0,1,1,0␛[0m
    +CEREG: 2,"8C3C","0A14F739",9,0,0,"11100000","11100000"
    [00:02:15.252,014] ␛[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 2␛[0m
    +CEREG: 4,"8C3C","0A14F739",9,0,15,"11100000","11100000"
    [00:02:15.574,859] ␛[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 4␛[0m
    +CEREG: 4,"FFFE","FFFFFFFF",9,0,15,"11100000","11100000"
    [00:02:16.110,931] ␛[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 4␛[0m
    +CEREG: 2,"EBB6","0144D3C8",9,0,15,"11100000","11100000"
    [00:02:25.489,074] ␛[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 2␛[0m
    +CEREG: 2,"EBB6","0144D3C8",9,0,11,"11100000","11100000"
    [00:02:25.906,036] ␛[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 2␛[0m
    +CEREG: 2,"2080","00808C0A",9,0,11,"11100000","11100000"
    [00:02:30.644,256] ␛[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 2␛[0m
    +CEREG: 4,"2080","00808C0A",9,0,15,"11100000","11100000"
    [00:02:31.062,683] ␛[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 4␛[0m
    +CEREG: 4,"FFFE","FFFFFFFF",9,0,15,"11100000","11100000"
    [00:02:31.540,924] ␛[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 4␛[0m
    +CEREG: 4,"2080","00808C14",9,0,15,"11100000","11100000"
    [00:02:35.740,051] ␛[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 4␛[0m
    +CEREG: 4,"2080","00808C0A",9,0,15,"11100000","11100000"
    [00:03:48.890,167] ␛[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 4␛[0m
    +CEREG: 4,"2080","00808C14",9,0,15,"11100000","11100000"
    [00:06:26.128,112] ␛[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 4␛[0m
    +CEREG: 4,"2080","00808C1E",9,0,15,"11100000","11100000"
    [00:06:56.269,073] ␛[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 4␛[0m
    [00:10:00.605,499] ␛[0m<inf> lte_lc: Network connection attempt timed out␛[0m
    [00:10:00.707,916] ␛[0m<inf> lte_lc: Using fallback network mode␛[0m
    [00:10:00.714,050] ␛[0m<dbg> lte_lc.w_lte_lc_connect: Network mode: AT%XSYSTEMMODE=1,0,1,0␛[0m
    +CEREG: 2,"417B","0A64020A",7,0,15,"11100000","11100000"
    [00:11:00.233,734] ␛[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 2␛[0m
    +CEREG: 2,"417B","0A64020A",7,0,11,"11100000","11100000"
    [00:11:00.251,739] ␛[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 2␛[0m
    +CEREG: 2,"417B","0A64020A",7,0,11,"11100000","11100000"
    [00:11:01.687,103] ␛[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 2␛[0m
    +CEREG: 2,"2000","00808C02",7,0,11,"11100000","11100000"
    [00:11:03.306,396] ␛[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 2␛[0m
    +CEREG: 5,"2000","00808C02",7,,,"11100000","11100000"
    [00:11:09.023,651] ␛[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 5␛[0m
    [00:11:09.031,982] ␛[0m<inf> asset_tracker: Connected to LTE network␛[0m
    [00:11:09.395,477] ␛[0m<dbg> nrf_cloud_transport.nct_connect: IPv4 Address 0x60235836␛[0m
    [00:11:09.405,212] ␛[0m<dbg> nrf_cloud_transport.nct_mqtt_connect: mqtt_connect requesting persistent session␛[0m
    [00:11:15.068,481] ␛[0m<dbg> aws_fota.aws_fota_mqtt_evt_handler: Previous session valid; skipping FOTA subscriptions␛[0m
    [00:11:15.079,254] ␛[0m<inf> aws_fota: Created notify_next_topic $aws/things/nrf-352656100381287/jobs/notify-next␛[0m
    [00:11:15.090,301] ␛[0m<inf> aws_fota: Created get_topic $aws/things/nrf-352656100381287/jobs/$next/get/#␛[0m
    [00:11:15.100,067] ␛[0m<inf> aws_fota: previously subscribed to notify-next topic␛[0m
    [00:11:15.107,757] ␛[0m<inf> aws_jobs: Publish topic: $aws/things/nrf-352656100381287/jobs/$next/get␛[0m
    [00:11:15.118,255] ␛[0m<inf> aws_jobs: Publish payload {"clientToken": ""}␛[0m
    [00:11:15.148,834] ␛[0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_CONNACK␛[0m
    [00:11:15.157,348] ␛[0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 2␛[0m
    [00:11:15.165,679] ␛[0m<dbg> nrf_cloud.event_handler: NRF_CLOUD_EVT_TRANSPORT_CONNECTED␛[0m
    [00:11:15.173,919] ␛[0m<inf> asset_tracker: CLOUD_EVT_CONNECTED␛[0m
    [00:11:15.180,023] ␛[0m<inf> asset_tracker: Persistent Sessions = 1␛[0m
    [00:11:15.186,401] ␛[0m<dbg> nrf_cloud_fsm.connection_handler: Previous session valid; skipping nct_cc_connect()␛[0m
    [00:11:15.197,601] ␛[0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 4␛[0m
    [00:11:15.207,031] ␛[0m<dbg> nrf_cloud_transport.nct_cc_send: mqtt_publish: id = 5678 opcode = 0 len = 0␛[0m
    [00:11:15.232,788] ␛[0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 5␛[0m
    [00:11:16.364,318] ␛[0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_PUBACK: id = 5678 result = 0␛[0m
    [00:11:16.384,582] ␛[0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 5␛[0m
    [00:11:16.392,486] ␛[0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_PUBACK: id = 36939 result = 0␛[0m
    [00:11:16.405,364] ␛[0m<dbg> aws_fota.on_publish_evt: Received topic: $aws/things/nrf-352656100381287/jobs/$next/get/accepted␛[0m
    [00:11:16.429,229] ␛[0m<inf> aws_fota: Checking for an available job␛[0m
    [00:11:16.436,157] ␛[0m<dbg> aws_fota.get_job_execution: Job doc: {"clientToken":"","timestamp":1590186783}␛[0m
    [00:11:16.446,777] ␛[0m<dbg> aws_fota.get_job_execution: Got only one field␛[0m
    [00:11:16.453,948] ␛[0m<inf> aws_fota: No queued jobs for this device␛[0m
    [00:11:16.460,754] ␛[0m<dbg> aws_fota.on_publish_evt: Received topic: nrf-352656100381287/shadow/get/accepted␛[0m
    [00:11:16.470,825] ␛[0m<dbg> aws_fota.on_publish_evt: received an unhandled MQTT publish event on topic: nrf-352656100381287/shadow/get/accepted␛[0m
    [00:11:16.485,900] ␛[0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_PUBLISH: id = 15404 len = 317␛[0m
    [00:11:16.499,603] ␛[0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 5␛[0m
    [00:11:16.507,263] ␛[0m<dbg> nrf_cloud.event_handler: NRF_CLOUD_EVT_RX_DATA␛[0m
    [00:11:16.514,465] ␛[0m<inf> asset_tracker: CLOUD_EVT_DATA_RECEIVED␛[0m
    [00:11:16.521,392] ␛[0m<inf> cloud_codec: [cloud_search_config:898] Found cfg item GPS, enable
    ␛[0m
    [00:11:16.534,637] ␛[0m<dbg> nrf_cloud_transport.nct_dc_endpoint_set: nct_dc_endpoint_set␛[0m
    [00:11:16.543,151] ␛[0m<dbg> nrf_cloud_transport.nct_dc_endpoint_get: nct_dc_endpoint_get␛[0m
    [00:11:16.552,429] ␛[0m<dbg> nrf_cloud_transport.nct_cc_send: mqtt_publish: id = 7890 opcode = 1 len = 329␛[0m
    [00:11:16.578,765] ␛[0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 7␛[0m
    [00:11:16.586,456] ␛[0m<dbg> nrf_cloud.event_handler: NRF_CLOUD_EVT_USER_ASSOCIATED␛[0m
    [00:11:16.594,299] ␛[0m<inf> asset_tracker: CLOUD_EVT_PAIR_DONE␛[0m
    [00:11:17.709,228] ␛[0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_PUBACK: id = 7890 result = 0␛[0m
    [00:11:17.719,268] ␛[0m<dbg> nrf_cloud_fsm.cc_tx_ack_handler: Previous session valid; skipping nct_dc_connect()␛[0m
    [00:11:17.730,041] ␛[0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 9␛[0m
    [00:11:17.737,731] ␛[0m<dbg> nrf_cloud.event_handler: NRF_CLOUD_EVT_READY␛[0m
    [00:11:17.744,750] ␛[0m<inf> asset_tracker: CLOUD_EVT_READY␛[0m
    [00:11:17.752,288] ␛[0m<dbg> nrf9160_gps.init: GPS socket created, fd: 1232491587␛[0m
    [00:11:17.780,609] ␛[0m<inf> gps_control: GPS initialized␛[0m
    [00:11:17.855,194] ␛[0m<dbg> nrf_cloud_transport.nct_cc_send: mqtt_publish: id = 1 opcode = 1 len = 632␛[0m
    [00:11:18.908,172] ␛[0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_PUBACK: id = 1 result = 0␛[0m
    %CESQ: 58,2,14,2
    %CESQ: 58,2,19,2

    Looks similar as above

    Asset Tracker - T-mobile sim - with PCO:

    note -> I know this sim works in my location: a BG96 modem connects over NB-IoT within a minute

    *** Booting Zephyr OS build v2.1.99-ncs1-1145-g13dc96f83bab  ***
    [00:00:00.192,291] ␛[0m<dbg> nrf9160_gps.setup: MAGPIO set: AT%XMAGPIO=1,0,0,1,1,1574,1577␛[0m
    [00:00:00.201,171] ␛[0m<dbg> nrf9160_gps.setup: COEX0 set: AT%XCOEX0=1,1,1570,1580␛[0m
    [00:00:00.208,862] ␛[0m<inf> asset_tracker: Asset tracker started␛[0m
    [00:00:00.222,320] ␛[0m<dbg> nrf_cloud_transport.nct_client_id_get: client_id = nrf-352656100381287␛[0m
    [00:00:00.231,536] ␛[0m<dbg> nrf_cloud_transport.nct_topics_populate: shadow_base_topic: $aws/things/nrf-352656100381287/shadow␛[0m
    [00:00:00.243,164] ␛[0m<dbg> nrf_cloud_transport.nct_topics_populate: accepted_topic: nrf-352656100381287/shadow/get/accepted␛[0m
    [00:00:00.254,669] ␛[0m<dbg> nrf_cloud_transport.nct_topics_populate: rejected_topic: $aws/things/nrf-352656100381287/shadow/get/rejected␛[0m
    [00:00:00.267,181] ␛[0m<dbg> nrf_cloud_transport.nct_topics_populate: update_delta_topic: $aws/things/nrf-352656100381287/shadow/update/delta␛[0m
    [00:00:00.280,029] ␛[0m<dbg> nrf_cloud_transport.nct_topics_populate: update_topic: $aws/things/nrf-352656100381287/shadow/update␛[0m
    [00:00:00.291,839] ␛[0m<dbg> nrf_cloud_transport.nct_topics_populate: shadow_get_topic: $aws/things/nrf-352656100381287/shadow/get␛[0m
    [00:00:00.304,016] ␛[0m<inf> asset_tracker: Connecting to LTE network. ␛[0m
    [00:00:00.310,760] ␛[0m<inf> asset_tracker: This may take several minutes.␛[0m
    [00:00:00.326,385] ␛[0m<inf> lte_lc: Using legacy LTE PCO mode...␛[0m
    [00:00:00.332,611] ␛[0m<dbg> lte_lc.w_lte_lc_connect: Network mode: AT%XSYSTEMMODE=0,1,1,0␛[0m
    +CEREG: 2,"EBB6","0144D3C8",9,0,0,"11100000","11100000"
    [00:00:13.943,450] ␛[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 2␛[0m
    +CEREG: 0,"EBB6","0144D3C8",9,0,6,"11100000","11100000"
    [00:00:15.136,108] ␛[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 0␛[0m
    [00:10:00.383,514] ␛[0m<inf> lte_lc: Network connection attempt timed out␛[0m
    [00:10:00.436,614] ␛[0m<inf> lte_lc: Using fallback network mode␛[0m
    [00:10:00.442,718] ␛[0m<dbg> lte_lc.w_lte_lc_connect: Network mode: AT%XSYSTEMMODE=1,0,1,0␛[0m
    +CEREG: 2,"417B","0A64020A",7,0,6,"11100000","11100000"
    [00:10:59.121,765] ␛[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 2␛[0m
    +CEREG: 2,"417B","0A64020A",7,0,11,"11100000","11100000"
    [00:10:59.330,963] ␛[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 2␛[0m
    +CEREG: 2,"2000","09A59E03",7,0,11,"11100000","11100000"
    [00:11:01.023,651] ␛[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 2␛[0m

    Looks like the modem tries 1 tower and then bails completely, fallback on Cat-M isn't working because this sim doesn't do Cat-M

    Asset Tracker - T-mobile - without PCO:

    *** Booting Zephyr OS build v2.1.99-ncs1-1145-g13dc96f83bab  ***
    [00:00:00.256,286] ␛[0m<dbg> nrf9160_gps.setup: MAGPIO set: AT%XMAGPIO=1,0,0,1,1,1574,1577␛[0m
    [00:00:00.274,597] ␛[0m<dbg> nrf9160_gps.setup: COEX0 set: AT%XCOEX0=1,1,1570,1580␛[0m
    [00:00:00.282,623] ␛[0m<inf> asset_tracker: Asset tracker started␛[0m
    [00:00:00.312,988] ␛[0m<dbg> nrf_cloud_transport.nct_client_id_get: client_id = nrf-352656100381287␛[0m
    [00:00:00.322,204] ␛[0m<dbg> nrf_cloud_transport.nct_topics_populate: shadow_base_topic: $aws/things/nrf-352656100381287/shadow␛[0m
    [00:00:00.333,862] ␛[0m<dbg> nrf_cloud_transport.nct_topics_populate: accepted_topic: nrf-352656100381287/shadow/get/accepted␛[0m
    [00:00:00.345,367] ␛[0m<dbg> nrf_cloud_transport.nct_topics_populate: rejected_topic: $aws/things/nrf-352656100381287/shadow/get/rejected␛[0m
    [00:00:00.357,910] ␛[0m<dbg> nrf_cloud_transport.nct_topics_populate: update_delta_topic: $aws/things/nrf-352656100381287/shadow/update/delta␛[0m
    [00:00:00.370,788] ␛[0m<dbg> nrf_cloud_transport.nct_topics_populate: update_topic: $aws/things/nrf-352656100381287/shadow/update␛[0m
    [00:00:00.382,629] ␛[0m<dbg> nrf_cloud_transport.nct_topics_populate: shadow_get_topic: $aws/things/nrf-352656100381287/shadow/get␛[0m
    [00:00:00.394,836] ␛[0m<inf> asset_tracker: Connecting to LTE network. ␛[0m
    [00:00:00.401,580] ␛[0m<inf> asset_tracker: This may take several minutes.␛[0m
    [00:00:00.437,927] ␛[0m<dbg> lte_lc.w_lte_lc_connect: Network mode: AT%XSYSTEMMODE=0,1,1,0␛[0m
    +CEREG: 2,"EBB6","0144D3C8",9,0,0,"11100000","11100000"
    [00:00:10.961,425] ␛[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 2␛[0m
    +CEREG: 0,"EBB6","0144D3C8",9,0,6,"11100000","11100000"
    [00:00:12.069,671] ␛[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 0␛[0m
    [00:10:00.600,677] ␛[0m<inf> lte_lc: Network connection attempt timed out␛[0m
    [00:10:00.666,961] ␛[0m<inf> lte_lc: Using fallback network mode␛[0m
    [00:10:00.673,065] ␛[0m<dbg> lte_lc.w_lte_lc_connect: Network mode: AT%XSYSTEMMODE=1,0,1,0␛[0m
    +CEREG: 2,"2000","00808C02",7,0,6,"11100000","11100000"
    [00:10:54.273,376] ␛[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 2␛[0m
    +CEREG: 2,"2000","00808C02",7,0,11,"11100000","11100000"
    [00:10:54.287,475] ␛[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 2␛[0m
    +CEREG: 2,"417B","0A64020A",7,0,11,"11100000","11100000"
    [00:11:01.401,245] ␛[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 2␛[0m
    +CEREG: 2,"417B","0A64020A",7,0,11,"11100000","11100000"
    [00:11:02.787,963] ␛[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 2␛[0m
    +CEREG: 2,"417B","0A64020A",7,0,11,"11100000","11100000"
    [00:11:04.335,266] ␛[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 2␛[0m
    +CEREG: 2,"417B","0A64020A",7,0,11,"11100000","11100000"
    [00:11:05.887,786] ␛[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 2␛[0m
    +CEREG: 4,"417B","0A64020A",7,0,11,"11100000","11100000"
    [00:11:07.311,523] ␛[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 4␛[0m
    +CEREG: 2,"FFFE","FFFFFFFF",7,0,11,"11100000","11100000"
    [00:11:26.052,764] ␛[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 2␛[0m

    Looks similar as above

    Why does the T-Mobile sim stop scanning after 1 tower with reject cause 6?

    Best,

    Jelmer

Children
No Data
Related