This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nRF9160 Not connecting over LTE on custom board

I have designed my own board, based around the nRF9160 but unfortunately I am unable to connect to an LTE network. 

I am running the at_client code and using LTE Link Monitor. Below, is the log file.

2020-02-15T15:26:18.899Z DEBUG modem >> AT\x0D\x0A
2020-02-15T15:26:18.923Z DEBUG modem << OK\x0D\x0A\x00
2020-02-15T15:26:20.627Z DEBUG modem >> AT+CFUN?\x0D\x0A
2020-02-15T15:26:20.651Z DEBUG modem << +CFUN: 0\x0D\x0A
2020-02-15T15:26:20.673Z DEBUG modem << OK\x0D\x0A\x00
2020-02-15T15:26:22.754Z DEBUG modem >> AT+CFUN=1\x0D\x0A
2020-02-15T15:26:22.811Z DEBUG modem << OK\x0D\x0A\x00
2020-02-15T15:26:23.996Z DEBUG modem >> AT+CFUN?\x0D\x0A
2020-02-15T15:26:24.011Z DEBUG modem << +CFUN: 1\x0D\x0A
2020-02-15T15:26:24.024Z DEBUG modem << OK\x0D\x0A\x00
2020-02-15T15:26:24.035Z DEBUG modem >> AT+CGSN=1\x0D\x0A
2020-02-15T15:26:24.043Z DEBUG modem << +CGSN: "352656100636847"\x0D\x0A
2020-02-15T15:26:24.045Z DEBUG modem << OK\x0D
2020-02-15T15:26:24.055Z DEBUG modem >> AT+CGMI\x0D\x0A
2020-02-15T15:26:24.074Z DEBUG modem << Nordic Semiconductor ASA\x0D\x0A
2020-02-15T15:26:24.078Z DEBUG modem << OK\x0D\x0A\x00
2020-02-15T15:26:24.082Z DEBUG modem >> AT+CGMM\x0D\x0A
2020-02-15T15:26:24.094Z DEBUG modem << nRF9160-SIBA\x0D\x0A
2020-02-15T15:26:24.096Z DEBUG modem << OK\x0D\x0A\x00
2020-02-15T15:26:24.103Z DEBUG modem >> AT+CGMR\x0D\x0A
2020-02-15T15:26:24.123Z DEBUG modem << mfw_nrf9160_1.1.1\x0D\x0A
2020-02-15T15:26:24.126Z DEBUG modem << OK\x0D\x0A\x00
2020-02-15T15:26:24.129Z INFO Nordic Semiconductor ASA nRF9160-SIBA [mfw_nrf9160_1.1.1] SerNr: 352656100636847
2020-02-15T15:26:24.130Z DEBUG modem >> AT+CEMODE?\x0D\x0A
2020-02-15T15:26:24.140Z DEBUG modem << +CEMODE: 0\x0D\x0A
2020-02-15T15:26:24.143Z DEBUG modem << OK\x0D\x0A\x00
2020-02-15T15:26:24.160Z DEBUG modem >> AT%XCBAND=?\x0D\x0A
2020-02-15T15:26:24.171Z DEBUG modem << %XCBAND: (1,2,3,4,5,8,12,13,17,19,20,25,26,28,66)\x0D\x0A
2020-02-15T15:26:24.173Z DEBUG modem << OK\x0D\x0A\x00
2020-02-15T15:26:24.189Z DEBUG modem >> AT+CMEE?\x0D\x0A
2020-02-15T15:26:24.241Z DEBUG modem << +CMEE: 0\x0D\x0A
2020-02-15T15:26:24.243Z DEBUG modem << OK\x0D\x0A\x00
2020-02-15T15:26:24.253Z DEBUG modem >> AT+CMEE=1\x0D\x0A
2020-02-15T15:26:24.270Z DEBUG modem << OK\x0D\x0A\x00
2020-02-15T15:26:24.274Z DEBUG modem >> AT+CNEC?\x0D\x0A
2020-02-15T15:26:24.287Z DEBUG modem << +CNEC: 0\x0D\x0A
2020-02-15T15:26:24.295Z DEBUG modem << OK\x0D\x0A\x00
2020-02-15T15:26:24.319Z DEBUG modem >> AT+CNEC=24\x0D\x0A
2020-02-15T15:26:24.332Z DEBUG modem << OK\x0D\x0A\x00
2020-02-15T15:26:24.337Z DEBUG modem >> AT+CGEREP?\x0D\x0A
2020-02-15T15:26:24.347Z DEBUG modem << +CGEREP: 0,0\x0D\x0A
2020-02-15T15:26:24.348Z DEBUG modem << OK\x0D\x0A\x00
2020-02-15T15:26:24.357Z DEBUG modem >> AT+CGDCONT?\x0D\x0A
2020-02-15T15:26:24.379Z DEBUG modem << OK\x0D\x0A\x00
2020-02-15T15:26:24.388Z DEBUG modem >> AT+CGACT?\x0D\x0A
2020-02-15T15:26:24.395Z DEBUG modem << OK\x0D\x0A\x00
2020-02-15T15:26:24.405Z DEBUG modem >> AT+CGEREP=1\x0D\x0A
2020-02-15T15:26:24.411Z DEBUG modem << OK\x0D\x0A\x00
2020-02-15T15:26:24.413Z DEBUG modem >> AT+CIND=1,1,1\x0D\x0A
2020-02-15T15:26:24.427Z DEBUG modem << OK\x0D\x0A\x00
2020-02-15T15:26:24.434Z DEBUG modem >> AT+CEREG=2\x0D\x0A
2020-02-15T15:26:24.448Z DEBUG modem << OK\x0D\x0A\x00
2020-02-15T15:26:24.462Z DEBUG modem >> AT+CEREG?\x0D\x0A
2020-02-15T15:26:24.475Z DEBUG modem << +CEREG: 2,4,"FFFE","FFFFFFFF",9\x0D\x0A
2020-02-15T15:26:24.477Z DEBUG modem << OK\x0D\x0A\x00
2020-02-15T15:26:24.494Z DEBUG modem >> AT%CESQ=1\x0D\x0A
2020-02-15T15:26:24.507Z DEBUG modem << OK\x0D\x0A\x00
2020-02-15T15:26:24.511Z DEBUG modem >> AT+CESQ\x0D\x0A
2020-02-15T15:26:24.524Z DEBUG modem << +CESQ: 99,99,255,255,255,255\x0D\x0A
2020-02-15T15:26:24.527Z DEBUG modem << OK\x0D\x0A\x00
2020-02-15T15:26:24.550Z DEBUG modem >> AT%XSIM=1\x0D\x0A
2020-02-15T15:26:24.571Z DEBUG modem << OK\x0D\x0A\x00
2020-02-15T15:26:24.575Z DEBUG modem >> AT%XSIM?\x0D\x0A
2020-02-15T15:26:24.587Z DEBUG modem << %XSIM: 1\x0D\x0A
2020-02-15T15:26:24.590Z DEBUG modem << OK\x0D\x0A\x00
2020-02-15T15:26:24.605Z DEBUG modem >> AT+CPIN?\x0D\x0A
2020-02-15T15:26:24.621Z DEBUG modem << +CPIN: READY\x0D\x0A
2020-02-15T15:26:24.624Z DEBUG modem << OK\x0D\x0A\x00
2020-02-15T15:26:24.648Z DEBUG modem >> AT+CPINR="SIM PIN"\x0D\x0A
2020-02-15T15:26:24.683Z DEBUG modem << +CPINR: "SIM PIN",3\x0D\x0A
2020-02-15T15:26:24.686Z DEBUG modem << OK\x0D\x0A\x00
2020-02-15T15:26:24.693Z DEBUG modem >> AT+CIMI\x0D\x0A
2020-02-15T15:26:24.705Z DEBUG modem << 204080813513474\x0D\x0A
2020-02-15T15:26:24.707Z DEBUG modem << OK\x0D\x0A\x00
2020-02-15T15:26:24.709Z INFO IMSIdentity: 204080813513474
2020-02-15T15:26:32.419Z DEBUG modem >> AT+COPS=?\x0D\x0A
2020-02-15T15:27:32.425Z ERROR Network search failed: Error: 'AT+COPS=?
' timed out

I have used the same SIM in the nRF9160DK and I do get a connection, all be it very weak. I am only seeing 1 bar in the LTE

Link Monitor application. 

The obvious difference is the layout of the two boards, however, I had the layout and schematics checked and "Ok'ed" by someone at Nordic so am quietly confident its OK.

Th other concern is the fact the signal is very weak.

I would appreciate any thought son how to move forward.

Thanks,

Rod

  • Hi Rod, 

    it might be that the antenna is too close to the ground to the right, but the antenna datasheet does not specify anything in this regard so it is hard to say. Have you had the antenna manufacturer look through the design as well? 

    You might just need to tune the components values on the matching network. 

    Best regards,
    Kaja

  • Hi Kaja,

    I am using the exact same antenna as used on the nRF9160DK. I spent  a lot of time back and forth with one of your apps people on reviewing the layout and design so am confident/hopeful that its OK.  

    Do you see anything in the log file that would suggest Im getting any signal.? 

    One of things I thought I could try would be to plug in an external antenna. As with the NRF9160DK, I have added an RF switch (like J1 on the DK) . Is there one you could recommend? I have tried to find one on line but cant seem to find one compatible with the connector, J1 on the DK. Do you know what you call that connector? A search for MM8130-2600 doesn't seem to help.

    Regards,

    Rod

  • Hi Kaja,

    Ok, a bit more investigating and it looks like my board has the NBIOT only part fitted. I have an nRF9160-SIBA fitted. (I see the nRF9160DK has the - SICA fitted) So, am I correct in saying that my board will only support NB-IOT? (and not LTE?)

    Can I still use the LTE Link Monitor to connected to NB-IOT?

    What changes do I need to make to the AT commands?

    Thanks,

    Rod

  • Hi Rod, 

    yes you talked to me about the HW. But as I said in the previous answer, you need to tune the antenna for your specific board. 
    The impedance of the antenna will change from design to design, because things are not always exactly the same. 

    If you have a look at this: 
    9160Ant.pdf

    This just means that you have to adjust the values of the matching components, so that the antenna is matched to 50 Ohm, withing your chosen freq. band, based on your specific board. 
    What I have done, is added ground on the DK, to have the same placement as in your design, just to see how "de-tuned" the antenna gets. 

    We still get okay signal strength, and connection shown in the LTE Link Monitor: 

    2020-02-19T12:06:27.780Z INFO Application data folder: C:\Users\hes2\AppData\Roaming\nrfconnect\pc-nrfconnect-linkmonitor
    2020-02-19T12:06:27.878Z DEBUG App pc-nrfconnect-linkmonitor v1.1.1 official
    2020-02-19T12:06:27.878Z DEBUG App path: C:\Users\hes2\.nrfconnect-apps\node_modules\pc-nrfconnect-linkmonitor
    2020-02-19T12:06:27.879Z DEBUG nRFConnect 3.3.0 is supported by the app (^3.2.0)
    2020-02-19T12:06:27.879Z DEBUG nRFConnect path: C:\Users\hes2\AppData\Local\Programs\nrfconnect\resources\app.asar
    2020-02-19T12:06:27.879Z DEBUG HomeDir: C:\Users\hes2
    2020-02-19T12:06:27.879Z DEBUG TmpDir: C:\Users\hes2\AppData\Local\Temp
    2020-02-19T12:06:27.882Z VERBOSE Could not fetch serial number for serial port at COM3
    2020-02-19T12:06:37.312Z INFO Modem port is opened
    2020-02-19T12:06:37.320Z DEBUG modem >> AT+CFUN?\x0D\x0A
    2020-02-19T12:06:37.327Z DEBUG modem << +CFUN: 1\x0D\x0A
    2020-02-19T12:06:37.329Z DEBUG modem << OK\x0D\x0A
    2020-02-19T12:06:37.368Z DEBUG modem >> AT+CGSN=1\x0D\x0A
    2020-02-19T12:06:37.375Z DEBUG modem << +CGSN: "352656100001349"\x0D
    2020-02-19T12:06:37.377Z DEBUG modem << \x0A
    2020-02-19T12:06:37.378Z DEBUG modem << OK\x0D\x0A
    2020-02-19T12:06:37.381Z DEBUG modem >> AT+CGMI\x0D\x0A
    2020-02-19T12:06:37.387Z DEBUG modem << Nordic Semiconductor ASA\x0D
    2020-02-19T12:06:37.394Z DEBUG modem << \x0A
    2020-02-19T12:06:37.396Z DEBUG modem << OK\x0D\x0A
    2020-02-19T12:06:37.403Z DEBUG modem >> AT+CGMM\x0D\x0A
    2020-02-19T12:06:37.420Z DEBUG modem << nRF9160-SICA\x0D\x0A
    2020-02-19T12:06:37.421Z DEBUG modem << OK\x0D\x0A
    2020-02-19T12:06:37.427Z DEBUG modem >> AT+CGMR\x0D\x0A
    2020-02-19T12:06:37.437Z DEBUG modem << mfw_nrf9160_1.1.1\x0D\x0A
    2020-02-19T12:06:37.438Z DEBUG modem << OK\x0D\x0A
    2020-02-19T12:06:37.440Z INFO Nordic Semiconductor ASA nRF9160-SICA [mfw_nrf9160_1.1.1] SerNr: 352656100001349
    2020-02-19T12:06:37.443Z DEBUG modem >> AT+CEMODE?\x0D\x0A
    2020-02-19T12:06:37.455Z DEBUG modem << +CEMODE: 2\x0D\x0A
    2020-02-19T12:06:37.461Z DEBUG modem << OK\x0D\x0A
    2020-02-19T12:06:37.477Z DEBUG modem >> AT%XCBAND=?\x0D\x0A
    2020-02-19T12:06:37.489Z DEBUG modem << %XCBAND: (1,2,3,4,5,8,12,13,14,17,18,19,20,25,26,28,66)\x0D\x0A
    2020-02-19T12:06:37.493Z DEBUG modem << OK\x0D\x0A
    2020-02-19T12:06:37.505Z DEBUG modem >> AT+CMEE?\x0D\x0A
    2020-02-19T12:06:37.510Z DEBUG modem << +CMEE: 0\x0D\x0A
    2020-02-19T12:06:37.511Z DEBUG modem << OK\x0D\x0A
    2020-02-19T12:06:37.519Z DEBUG modem >> AT+CMEE=1\x0D\x0A
    2020-02-19T12:06:37.524Z DEBUG modem << OK\x0D\x0A
    2020-02-19T12:06:37.529Z DEBUG modem >> AT+CNEC?\x0D\x0A
    2020-02-19T12:06:37.537Z DEBUG modem << +CNEC: 0\x0D\x0A
    2020-02-19T12:06:37.538Z DEBUG modem << OK\x0D\x0A
    2020-02-19T12:06:37.542Z DEBUG modem >> AT+CNEC=24\x0D\x0A
    2020-02-19T12:06:37.550Z DEBUG modem << OK\x0D
    2020-02-19T12:06:37.552Z DEBUG modem >> AT+CGEREP?\x0D\x0A
    2020-02-19T12:06:37.558Z DEBUG modem << +CGEREP: 0,0\x0D\x0A
    2020-02-19T12:06:37.559Z DEBUG modem << OK\x0D\x0A
    2020-02-19T12:06:37.562Z DEBUG modem >> AT+CGDCONT?\x0D\x0A
    2020-02-19T12:06:37.568Z DEBUG modem << OK\x0D\x0A
    2020-02-19T12:06:37.572Z DEBUG modem >> AT+CGACT?\x0D\x0A
    2020-02-19T12:06:37.577Z DEBUG modem << OK\x0D\x0A
    2020-02-19T12:06:37.583Z DEBUG modem >> AT+CGEREP=1\x0D\x0A
    2020-02-19T12:06:37.588Z DEBUG modem << OK\x0D\x0A
    2020-02-19T12:06:37.592Z DEBUG modem >> AT+CIND=1,1,1\x0D\x0A
    2020-02-19T12:06:37.601Z DEBUG modem << OK\x0D\x0A
    2020-02-19T12:06:37.604Z DEBUG modem >> AT+CEREG=2\x0D\x0A
    2020-02-19T12:06:37.609Z DEBUG modem << OK\x0D\x0A
    2020-02-19T12:06:37.612Z DEBUG modem >> AT+CEREG?\x0D\x0A
    2020-02-19T12:06:37.621Z DEBUG modem << +CEREG: 2,4,"FFFE","FFFFFFFF",7\x0D
    2020-02-19T12:06:37.623Z DEBUG modem << \x0A
    2020-02-19T12:06:37.625Z DEBUG modem << OK\x0D\x0A
    2020-02-19T12:06:37.639Z DEBUG modem >> AT%CESQ=1\x0D\x0A
    2020-02-19T12:06:37.643Z DEBUG modem << OK\x0D\x0A
    2020-02-19T12:06:37.653Z DEBUG modem >> AT+CESQ\x0D\x0A
    2020-02-19T12:06:37.659Z DEBUG modem << +CESQ: 99,99,255,255,255,255\x0D\x0A
    2020-02-19T12:06:37.668Z DEBUG modem << OK\x0D\x0A
    2020-02-19T12:06:37.673Z DEBUG modem >> AT%XSIM=1\x0D\x0A
    2020-02-19T12:06:37.678Z DEBUG modem << OK\x0D\x0A
    2020-02-19T12:06:37.685Z DEBUG modem >> AT%XSIM?\x0D\x0A
    2020-02-19T12:06:37.690Z DEBUG modem << %XSIM: 0\x0D
    2020-02-19T12:06:37.694Z DEBUG modem << \x0A
    2020-02-19T12:06:37.695Z DEBUG modem << OK\x0D\x0A
    2020-02-19T12:06:38.168Z DEBUG modem << %XSIM: 1\x0D\x0A
    2020-02-19T12:06:38.175Z DEBUG modem >> AT+CPIN?\x0D\x0A
    2020-02-19T12:06:38.191Z DEBUG modem << +CPIN: READY\x0D\x0A
    2020-02-19T12:06:38.192Z DEBUG modem << OK\x0D\x0A
    2020-02-19T12:06:38.201Z DEBUG modem >> AT+CPINR="SIM PIN"\x0D\x0A
    2020-02-19T12:06:38.219Z DEBUG modem << +CPINR: "SIM PIN",3\x0D
    2020-02-19T12:06:38.221Z DEBUG modem << \x0A
    2020-02-19T12:06:38.223Z DEBUG modem << OK\x0D\x0A
    2020-02-19T12:06:38.228Z DEBUG modem >> AT+CIMI\x0D\x0A
    2020-02-19T12:06:38.235Z DEBUG modem << 204080813512950\x0D\x0A
    2020-02-19T12:06:38.238Z DEBUG modem << OK\x0D\x0A
    2020-02-19T12:06:38.240Z INFO IMSIdentity: 204080813512950
    2020-02-19T12:07:56.207Z DEBUG modem >> AT+CFUN?\x0D\x0A
    2020-02-19T12:07:56.219Z DEBUG modem << +CFUN: 1\x0D\x0A
    2020-02-19T12:07:56.226Z DEBUG modem << OK\x0D\x0A
    2020-02-19T12:08:11.188Z DEBUG modem << %CESQ: 41,2,20,2\x0D
    2020-02-19T12:08:11.210Z DEBUG modem << +CEREG: 2,"76C1","014ACE00",7\x0D\x0A
    2020-02-19T12:08:11.214Z DEBUG modem << [00:01:36.038,818] \x1B[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 2\x1B[0m\x0D\x0A
    2020-02-19T12:08:12.016Z DEBUG modem << %CESQ: 46,2,20,2\x0D\x0A
    2020-02-19T12:08:13.016Z DEBUG modem << %CESQ: 46,2,25,3\x0D\x0A
    2020-02-19T12:08:13.290Z DEBUG modem << +CGEV: ME PDN ACT 0,0\x0D\x0A
    2020-02-19T12:08:13.302Z DEBUG modem << [00:01:38.138,702] \x1B[1;31m<err> lte_lc: Could not parse AT+CEREG response, error: -11\x1B[0m\x0D\x0A
    2020-02-19T12:08:13.306Z DEBUG modem << [00:01:38.146,667] \x1B[1;31m<err> lte_lc: Could not get network registration status\x1B[0m\x0D\x0A
    2020-02-19T12:08:13.310Z DEBUG modem << +CNEC_ESM: 50,0\x0D\x0A
    2020-02-19T12:08:13.322Z DEBUG modem << [00:01:38.156,005] \x1B[1;31m<err> lte_lc: Could not parse AT+CEREG response, error: -11\x1B[0m\x0D\x0A
    2020-02-19T12:08:13.323Z DEBUG modem << [00:01:38.164,001] \x1B[1;31m<err> lte_lc: Could not get network registration status\x1B[0m\x0D\x0A
    2020-02-19T12:08:13.326Z DEBUG modem << +CEREG: 5,"76C1","014ACE00",7\x0D
    2020-02-19T12:08:13.338Z DEBUG modem << [00:01:38.174,621] \x1B[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 5\x1B[0m\x0D\x0A
    2020-02-19T12:08:13.341Z DEBUG modem << [00:01:38.182,983] \x1B[0m<inf> asset_tracker: Connected to LTE network\x1B[0m\x0D\x0A
    2020-02-19T12:08:13.344Z DEBUG modem << +CIND: "service",1\x0D\x0A
    2020-02-19T12:08:13.361Z DEBUG modem << +CIND: "roam",1\x0D\x0A
    2020-02-19T12:08:13.458Z DEBUG modem << [00:01:38.297,332] \x1B[0m<dbg> nrf_cloud_transport.nct_connect: IPv4 Address 0x4a3c0534\x1B[0m\x0D\x0A
    2020-02-19T12:08:18.016Z DEBUG modem << [00:01:42.854,827] \x1B[0m<inf> aws_jobs: Subscribe: $aws/things/nrf-352656100001349/jobs/notify-next\x1B[0m\x0D\x0A
    2020-02-19T12:08:18.026Z DEBUG modem << [00:01:42.865,325] \x1B[0m<inf> aws_jobs: Subscribe: $aws/things/nrf-352656100001349/jobs/$next/get/#\x1B[0m\x0D\x0A
    2020-02-19T12:08:18.035Z DEBUG modem << [00:01:42.875,244] \x1B[0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_CONNACK\x1B[0m\x0D\x0A
    2020-02-19T12:08:18.042Z DEBUG modem << [00:01:42.883,392] \x1B[0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 2\x1B[0m\x0D\x0A
    2020-02-19T12:08:18.057Z DEBUG modem << [00:01:42.891,174] \x1B[0m<dbg> nrf_cloud.event_handler: NRF_CLOUD_EVT_TRANSPORT_CONNECTED\x1B[0m\x0D\x0A
    2020-02-19T12:08:18.059Z DEBUG modem << [00:01:42.899,291] \x1B[0m<inf> asset_tracker: CLOUD_EVT_CONNECTED\x1B[0m\x0D\x0A
    2020-02-19T12:08:18.064Z DEBUG modem << [00:01:42.905,426] \x1B[0m<dbg> nrf_cloud_transport.nct_cc_connect: nct_cc_connect\x1B[0m\x0D\x0A
    2020-02-19T12:08:18.072Z DEBUG modem << [00:01:42.913,665] \x1B[0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 3\x1B[0m\x0D
    2020-02-19T12:08:18.202Z DEBUG modem << [00:01:43.044,647] \x1B[0m<inf> aws_fota: subscribed to notify-next topic\x1B[0m\x0D\x0A
    2020-02-19T12:08:18.212Z DEBUG modem << [00:01:43.051,391] \x1B[0m<inf> aws_jobs: Publish topic: $aws/things/nrf-352656100001349/jobs/$next/get\x1B[0m\x0D
    2020-02-19T12:08:18.219Z DEBUG modem << [00:01:43.060,699] \x1B[0m<inf> aws_jobs: Publish payload {"clientToken": ""}\x1B[0m\x0D
    2020-02-19T12:08:18.368Z DEBUG modem << [00:01:43.206,787] \x1B[0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_SUBACK: id = 2114 result = 0\x1B[0m\x0D
    2020-02-19T12:08:18.418Z DEBUG modem << [00:01:43.256,591] \x1B[0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_SUBACK: id = 1234 result = 0\x1B[0m\x0D\x0A
    2020-02-19T12:08:18.426Z DEBUG modem << [00:01:43.266,662] \x1B[0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 4\x1B[0m\x0D\x0A
    2020-02-19T12:08:18.435Z DEBUG modem << [00:01:43.274,414] \x1B[0m<dbg> nrf_cloud_transport.nct_cc_send: mqtt_publish: id = 5678 opcode = 0 len = 0\x1B[0m\x0D\x0A
    2020-02-19T12:08:18.444Z DEBUG modem << [00:01:43.284,698] \x1B[0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 5\x1B[0m\x0D\x0A
    2020-02-19T12:08:18.533Z DEBUG modem << [00:01:43.371,734] \x1B[0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_PUBACK: id = 34988 result = 0\x1B[0m\x0D\x0A
    2020-02-19T12:08:18.545Z DEBUG modem << [00:01:43.382,049] \x1B[0m<dbg> aws_fota.on_publish_evt: Received topic: $aws/things/nrf-352656100001349/jobs/$next/get/accepted\x1B[0m\x0D\x0A
    2020-02-19T12:08:18.551Z DEBUG modem << [00:01:43.393,585] \x1B[0m<inf> aws_fota: Checking for an available job\x1B[0m\x0D\x0A
    


    What freq. are you using?

    Best regards,
    Kaja

  • Thanks Kaja,

    Yes, I appreciate that I need to turn the circuit. I am not sure if you saw my update below ? I have realised that my board has the NBIOT only part fitted so I can not use LTE.

    Am I correct in saying that I just need to change the AT%XSYSTEMMODE setting to enviable NBIOT?

    I live in Cambridge, do you know what the NBIOT coverage is here?

    I will go back to the DK and verify that I get a NBIOT connection. What is the best way of doing that?

    Rod

Related