Asset Tracker application in NB-IoT mode

[amessner]

Hi everyone.
I'm using a Thingy:91 and the asset tracker application. I can compile and flash (using SES and a Segger J-Link) the application and the device connects to the nRF cloud.

But when I change the "network mode" from LTE-M + GPS to NB-IOT + GPS it stops working. I'm located in Canada where we do not have NB-IOT coverage, but the device should switch to fallback mode which is LTE-M. If I use the asset tracker NB-IOT binaries provided by nRF (thingy91_nbiot_dfu_2020-04-29_bc7ade8b.hex) I see exactly that: the device tries to connect, times out and falls back to LTE-M and then connects just fine.

What configuration settings do I have to change to switch the default asset tracker application from LTE-M to NB-IOT?

Below is the output of the link monitor of my test build with network mode set to NB-IOT:
%CESQ: 255,0,255,0
+CEREG: 2,"FFFE","FFFFFFFF",
[00:00:30.588,684] [0m<dbg> lte_lc.at_handler: +CEREG notification: +CEREG: 2,"FFFE","FFFFFFFF",9
[0m
[00:00:30.598,144] [1;31m<err> lte_lc: Could not get TAU, error: -22[0m
[00:00:30.604,736] [1;31m<err> lte_lc: Failed to parse PSM configuration, error: -22[0m
[00:00:30.612,792] [1;31m<err> lte_lc: Failed to parse notification (error -22): +CEREG: 2,"FFFE","FFFFFFFF",9
[0m
%CESQ: 255,0,255,0
%CESQ: 255,0,255,0
%CESQ: 255,0,255,0

Thanks

[Øyvind]

Hello, 
 

I'm using a Thingy:91 and the asset tracker application. I can compile and flash (using SES and a Segger J-Link) the application and the device connects to the nRF cloud.

What NCS version are you compiling the asset tracker with?  

If I use the asset tracker NB-IOT binaries provided by nRF (thingy91_nbiot_dfu_2020-04-29_bc7ade8b.hex) I see exactly that: the device tries to connect, times out and falls back to LTE-M and then connects just fine.

 These files were built with nRF Connect SDK version v1.2.0-406-gbc7ade8b. 

 

when I change the "network mode" from LTE-M + GPS to NB-IOT + GPS it stops working. I'm located in Canada where we do not have NB-IOT coverage, but the device should switch to fallback mode which is LTE-M.

 How do you change from LTE-M to NB-IoT?

Kind regards,
Øyvind

[amessner]

Hi Øyvind

Øyvind said:

What NCS version are you compiling the asset tracker with?  

I used the toolchain manager and installed nRF Connect SDC v1.3.0, looking at my installation it should be ncs-toolchain-v1.3.0-20200618-509f057 

Øyvind said:

How do you change from LTE-M to NB-IoT?

I use the unmodified asset tracker application from the SDK. In SES I open the "Configure nRF Connect SDK Project...", and navigate to

menuconfig: Zephyr Kernel -> Modules -> Nordic nRF Connect -> Libraries -> nRF91 LTE Link control library -> Select network mode

and changed "LTE-M and GPS" to "NB-IoT and GPS" and confirm by clicking on "Configure".

Then I clean and re-build the solution which is successful.

Finally I flash the new image using the SES menu Target -> Download zephyr/merged.hex. As mentioned earlier, the Thingy91 is programmed to my PC using a SEGGER J-Link. The flash is successful and the Thingy91 starts up (breathing LED).

Are these the correct steps to change the build to NB-IoT network mode?

Your help is much appreciated.

Thanks

[amessner]

I just switched to the nRF Connect SDK v1.2.0 and repeated the steps above to switch to NB-IoT mode as the default network mode and now it connects successfully once it switches to the fallback mode.

It seems like the asset tracker application using NCS toolchain v1.3.0 does only work if the default network mode is configured to LTE-M, but not NB-IoT.  

Also now (with SDK v1.2.0) another issue shows up: If I enable "Automatic start of GPS on CLOUD_EVT_READY event after reset" the GPS doesn't seem to start properly. Looking at it closely I never seem to get the "CLOUD_EVT_READY" event. A long press on the user button produces the output below. There were no other GPS related messages before that. This tells me that the GPS did not start properly. Another long press after that and the GPS module starts (with some initial "Invalid PVT frame, discarding" messages).

[00:01:59.213,195] [0m<inf> asset_tracker: Stopping GPS[0m
[00:01:59.218,750] [0m<dbg> nrf9160_gps.stop: Stopping GPS[0m
[00:01:59.224,487] [1;31m<err> nrf9160_gps: Failed to stop GPS[0m
[00:01:59.230,560] [1;31m<err> gps_control: GPS could not be stopped, error: -5[0m

[Øyvind]

Hello, 

amessner said:

It seems like the asset tracker application using NCS toolchain v1.3.0 does only work if the default network mode is configured to LTE-M, but not NB-IoT.  

Can you please try to run another sample from NCS v1.3.0, to see if it connects as it should. You could try the at_client sample and issue CFUN? to get more information regarding your connection. Please provide a full log from the LTE Link Monitor. I also recommend running a modem trace to see what is going on under the hood of the modem.

 

amessner said:

Also now (with SDK v1.2.0) another issue shows up: If I enable "Automatic start of GPS on CLOUD_EVT_READY event after reset" the GPS doesn't seem to start properly. Looking at it closely I never seem to get the "CLOUD_EVT_READY" event. A long press on the user button produces the output below. There were no other GPS related messages before that. This tells me that the GPS did not start properly. Another long press after that and the GPS module starts (with some initial "Invalid PVT frame, discarding" messages).

 Can you provide a full log the from LTE Link Monitor when you encounter this issue? What happens if you do not enable "Automatic start of GPS on CLOUD_EVT_READY event after reset"? We might need a modem trace for this as well. 

Kind regards, 

Øyvind

[amessner]

Hi Øyvind

Øyvind said:

Can you please try to run another sample from NCS v1.3.0, to see if it connects as it should. You could try the at_client sample and issue CFUN? to get more information regarding your connection. Please provide a full log from the LTE Link Monitor. I also recommend running a modem trace to see what is going on under the hood of the modem.

Will do that later today and post the results here

Øyvind said:

 Can you provide a full log the from LTE Link Monitor when you encounter this issue? What happens if you do not enable "Automatic start of GPS on CLOUD_EVT_READY event after reset"? We might need a modem trace for this as well. 

Below is a LTE Link Monitor log. The asset tracker application was configured to:
- Default Network Mode: LTE-M (I'm located in Canada which has LTE-M coverage)
- "Automatic start of GPS on CLOUD_EVT_READY event after reset": disabled

The trace looks exactly the same if "Automatic start of GPS on CLOUD_EVT_READY event after reset" is enabled.

If the default network mode is set to NB-IoT it looks similar, only difference are the failed connection attempts and then the switch to fallback mode upon timeout.

I left the system sitting for a while after the last log line showed up in LTE Link Monitor, but no other log was registered. The interesting part is that I can see events like button press and flip events show up in the nRF Cloud, but the LTE Link Monitor seems frozen.

And as you can see below, there is no CLOUD_EVT_READY event.

2020-07-23T15:33:12.087Z DEBUG modem << *** Booting Zephyr OS build v2.1.99-ncs1 ***
2020-07-23T15:33:12.202Z DEBUG modem << Flash regionDomainPermissions
2020-07-23T15:33:12.208Z DEBUG modem << 00 0x00000 0x08000 Securerwxl
2020-07-23T15:33:12.210Z DEBUG modem << 01 0x08000 0x10000 Securerwxl
2020-07-23T15:33:12.211Z DEBUG modem << 02 0x10000 0x18000 Securerwxl
2020-07-23T15:33:12.213Z DEBUG modem << 03 0x18000 0x20000 Non-Securerwxl
2020-07-23T15:33:12.215Z DEBUG modem << 04 0x20000 0x28000 Non-Securerwxl
2020-07-23T15:33:12.216Z DEBUG modem << 05 0x28000 0x30000 Non-Securerwxl
2020-07-23T15:33:12.218Z DEBUG modem << 06 0x30000 0x38000 Non-Securerwxl
2020-07-23T15:33:12.220Z DEBUG modem << 07 0x38000 0x40000 Non-Securerwxl
2020-07-23T15:33:12.221Z DEBUG modem << 08 0x40000 0x48000 Non-Securerwxl
2020-07-23T15:33:12.223Z DEBUG modem << 09 0x48000 0x50000 Non-Securerwxl
2020-07-23T15:33:12.224Z DEBUG modem << 10 0x50000 0x58000 Non-Securerwxl
2020-07-23T15:33:12.226Z DEBUG modem << 11 0x58000 0x60000 Non-Securerwxl
2020-07-23T15:33:12.227Z DEBUG modem << 12 0x60000 0x68000 Non-Securerwxl
2020-07-23T15:33:12.238Z DEBUG modem << 13 0x68000 0x70000 Non-Securerwxl
2020-07-23T15:33:12.241Z DEBUG modem << 14 0x70000 0x78000 Non-Securerwxl
2020-07-23T15:33:12.242Z DEBUG modem << 15 0x78000 0x80000 Non-Securerwxl
2020-07-23T15:33:12.243Z DEBUG modem << 16 0x80000 0x88000 Non-Securerwxl
2020-07-23T15:33:12.245Z DEBUG modem << 17 0x88000 0x90000 Non-Securerwxl
2020-07-23T15:33:12.246Z DEBUG modem << 18 0x90000 0x98000 Non-Securerwxl
2020-07-23T15:33:12.247Z DEBUG modem << 19 0x98000 0xa0000 Non-Securerwxl
2020-07-23T15:33:12.248Z DEBUG modem << 20 0xa0000 0xa8000 Non-Securerwxl
2020-07-23T15:33:12.249Z DEBUG modem << 21 0xa8000 0xb0000 Non-Securerwxl
2020-07-23T15:33:12.251Z DEBUG modem << 22 0xb0000 0xb8000 Non-Securerwxl
2020-07-23T15:33:12.252Z DEBUG modem << 23 0xb8000 0xc0000 Non-Securerwxl
2020-07-23T15:33:12.253Z DEBUG modem << 24 0xc0000 0xc8000 Non-Securerwxl
2020-07-23T15:33:12.255Z DEBUG modem << 25 0xc8000 0xd0000 Non-Securerwxl
2020-07-23T15:33:12.256Z DEBUG modem << 26 0xd0000 0xd8000 Non-Securerwxl
2020-07-23T15:33:12.257Z DEBUG modem << 27 0xd8000 0xe0000 Non-Securerwxl
2020-07-23T15:33:12.257Z DEBUG modem << 28 0xe0000 0xe8000 Non-Securerwxl
2020-07-23T15:33:12.258Z DEBUG modem << 29 0xe8000 0xf0000 Non-Securerwxl
2020-07-23T15:33:12.259Z DEBUG modem << 30 0xf0000 0xf8000 Non-Securerwxl
2020-07-23T15:33:12.260Z DEBUG modem << 31 0xf8000 0x100000 Non-Securerwxl
2020-07-23T15:33:12.261Z DEBUG modem << Non-secure callable region 0 placed in flash region 2 with size 32.
2020-07-23T15:33:12.381Z DEBUG modem << SRAM regionDomainPermissions
2020-07-23T15:33:12.387Z DEBUG modem << 00 0x00000 0x02000Securerwxl
2020-07-23T15:33:12.388Z DEBUG modem << 01 0x02000 0x04000Securerwxl
2020-07-23T15:33:12.389Z DEBUG modem << 02 0x04000 0x06000Securerwxl
2020-07-23T15:33:12.561Z DEBUG modem << 03 0x06000 0x08000Securerwxl
2020-07-23T15:33:12.565Z DEBUG modem << 04 0x08000 0x0a000Securerwxl
2020-07-23T15:33:12.583Z DEBUG modem << 05 0x0a000 0x0c000Securerwxl
2020-07-23T15:33:12.585Z DEBUG modem << 06 0x0c000 0x0e000Securerwxl
2020-07-23T15:33:12.587Z DEBUG modem << 07 0x0e000 0x10000Securerwxl
2020-07-23T15:33:12.589Z DEBUG modem << 08 0x10000 0x12000Non-Securerwxl
2020-07-23T15:33:12.590Z DEBUG modem << 09 0x12000 0x14000Non-Securerwxl
2020-07-23T15:33:12.591Z DEBUG modem << 10 0x14000 0x16000Non-Securerwxl
2020-07-23T15:33:12.592Z DEBUG modem << 11 0x16000 0x18000Non-Securerwxl
2020-07-23T15:33:12.594Z DEBUG modem << 12 0x18000 0x1a000Non-Securerwxl
2020-07-23T15:33:12.596Z DEBUG modem << 13 0x1a000 0x1c000Non-Securerwxl
2020-07-23T15:33:12.597Z DEBUG modem << 14 0x1c000 0x1e000Non-Securerwxl
2020-07-23T15:33:12.598Z DEBUG modem << 15 0x1e000 0x20000Non-Securerwxl
2020-07-23T15:33:12.599Z DEBUG modem << 16 0x20000 0x22000Non-Securerwxl
2020-07-23T15:33:12.600Z DEBUG modem << 17 0x22000 0x24000Non-Securerwxl
2020-07-23T15:33:12.601Z DEBUG modem << 18 0x24000 0x26000Non-Securerwxl
2020-07-23T15:33:12.601Z DEBUG modem << 19 0x26000 0x28000Non-Securerwxl
2020-07-23T15:33:12.602Z DEBUG modem << 20 0x28000 0x2a000Non-Securerwxl
2020-07-23T15:33:12.602Z DEBUG modem << 21 0x2a000 0x2c000Non-Securerwxl
2020-07-23T15:33:12.603Z DEBUG modem << 22 0x2c000 0x2e000Non-Securerwxl
2020-07-23T15:33:12.603Z DEBUG modem << 23 0x2e000 0x30000Non-Securerwxl
2020-07-23T15:33:12.606Z DEBUG modem << 24 0x30000 0x32000Non-Securerwxl
2020-07-23T15:33:12.607Z DEBUG modem << 25 0x32000 0x34000Non-Securerwxl
2020-07-23T15:33:12.608Z DEBUG modem << 26 0x34000 0x36000Non-Securerwxl
2020-07-23T15:33:12.608Z DEBUG modem << 27 0x36000 0x38000Non-Securerwxl
2020-07-23T15:33:12.610Z DEBUG modem << 28 0x38000 0x3a000Non-Securerwxl
2020-07-23T15:33:12.610Z DEBUG modem << 29 0x3a000 0x3c000Non-Securerwxl
2020-07-23T15:33:12.611Z DEBUG modem << 30 0x3c000 0x3e000Non-Securerwxl
2020-07-23T15:33:12.612Z DEBUG modem << 31 0x3e000 0x40000Non-Securerwxl
2020-07-23T15:33:12.613Z DEBUG modem << PeripheralDomainStatus
2020-07-23T15:33:12.614Z DEBUG modem << 00 NRF_P0 Non-SecureOK
2020-07-23T15:33:12.615Z DEBUG modem << 01 NRF_CLOCK Non-SecureOK
2020-07-23T15:33:12.615Z DEBUG modem << 02 NRF_RTC0 Non-SecureOK
2020-07-23T15:33:12.616Z DEBUG modem << 03 NRF_RTC1 Non-SecureOK
2020-07-23T15:33:12.619Z DEBUG modem << 04 NRF_NVMC Non-SecureOK
2020-07-23T15:33:12.620Z DEBUG modem << 05 NRF_UARTE1 Non-SecureOK
2020-07-23T15:33:12.622Z DEBUG modem << 06 NRF_UARTE2 SecureSKIP
2020-07-23T15:33:12.624Z DEBUG modem << 07 NRF_TWIM2 Non-SecureOK
2020-07-23T15:33:12.625Z DEBUG modem << 08 NRF_SPIM3 Non-SecureOK
2020-07-23T15:33:12.625Z DEBUG modem << 09 NRF_TIMER0 Non-SecureOK
2020-07-23T15:33:12.626Z DEBUG modem << 10 NRF_TIMER1 Non-SecureOK
2020-07-23T15:33:12.627Z DEBUG modem << 11 NRF_TIMER2 Non-SecureOK
2020-07-23T15:33:12.628Z DEBUG modem << 12 NRF_SAADC Non-SecureOK
2020-07-23T15:33:12.629Z DEBUG modem << 13 NRF_PWM0 Non-SecureOK
2020-07-23T15:33:12.630Z DEBUG modem << 14 NRF_PWM1 Non-SecureOK
2020-07-23T15:33:12.631Z DEBUG modem << 15 NRF_PWM2 Non-SecureOK
2020-07-23T15:33:12.632Z DEBUG modem << 16 NRF_PWM3 Non-SecureOK
2020-07-23T15:33:12.633Z DEBUG modem << 17 NRF_WDT Non-SecureOK
2020-07-23T15:33:12.633Z DEBUG modem << 18 NRF_IPC Non-SecureOK
2020-07-23T15:33:12.633Z DEBUG modem << 19 NRF_VMC Non-SecureOK
2020-07-23T15:33:12.634Z DEBUG modem << 20 NRF_FPU Non-SecureOK
2020-07-23T15:33:12.635Z DEBUG modem << 21 NRF_EGU1 Non-SecureOK
2020-07-23T15:33:12.636Z DEBUG modem << 22 NRF_EGU2 Non-SecureOK
2020-07-23T15:33:12.638Z DEBUG modem << 23 NRF_DPPIC Non-SecureOK
2020-07-23T15:33:12.639Z DEBUG modem << 24 NRF_GPIOTE1 Non-SecureOK
2020-07-23T15:33:12.653Z DEBUG modem << 25 NRF_REGULATORS Non-SecureOK
2020-07-23T15:33:12.655Z DEBUG modem << SPM: NS image at 0x18200
2020-07-23T15:33:12.656Z DEBUG modem << SPM: NS MSP at 0x2002e848
2020-07-23T15:33:12.658Z DEBUG modem << SPM: NS reset vector at 0x1fd8d
2020-07-23T15:33:12.659Z DEBUG modem << SPM: prepare to jump to Non-Secure image.
2020-07-23T15:33:12.782Z DEBUG modem << *** Booting Zephyr OS build v2.1.9[00:00:00.194,702] [0m<inf> BH1749: BH1749 initialized[0m
2020-07-23T15:33:12.783Z DEBUG modem << 9-ncs1 ***
2020-07-23T15:33:12.823Z DEBUG modem << [00:00:00.216,094] [0m<inf> asset_tracker: Asset tracker started[0m
2020-07-23T15:33:12.824Z DEBUG modem << [00:00:00.222,381] [0m<inf> watchdog: Watchdog timeout installed. Timeout: 10000[0m
2020-07-23T15:33:12.825Z DEBUG modem << [00:00:00.230,041] [0m<inf> watchdog: Watchdog started[0m
2020-07-23T15:33:12.832Z DEBUG modem << [00:00:00.235,443] [0m<inf> watchdog: Watchdog feed enabled. Timeout: 5000[0m
2020-07-23T15:33:12.926Z DEBUG modem << [00:00:00.249,542] [0m<dbg> nrf_cloud_transport.nct_client_id_get: client_id = nrf-352656100880619[0m
2020-07-23T15:33:12.928Z DEBUG modem << [00:00:00.258,789] [0m<dbg> nrf_cloud_transport.nct_topics_populate: shadow_base_topic: $aws/things/nrf-352656100880619/shadow[0m
2020-07-23T15:33:12.929Z DEBUG modem << [00:00:00.270,477] [0m<dbg> nrf_cloud_transport.nct_topics_populate: accepted_topic: nrf-352656100880619/shadow/get/accepted[0m
2020-07-23T15:33:12.940Z DEBUG modem << [00:00:00.281,951] [0m<dbg> nrf_cloud_transport.nct_topics_populate: rejected_topic: $aws/things/nrf-352656100880619/shadow/get/rejected[0m
2020-07-23T15:33:12.941Z DEBUG modem << [00:00:00.294,525] [0m<dbg> nrf_cloud_transport.nct_topics_populate: update_delta_topic: $aws/things/nrf-352656100880619/shadow/update/delta[0m
2020-07-23T15:33:12.942Z DEBUG modem << [00:00:00.307,434] [0m<dbg> nrf_cloud_transport.nct_topics_populate: update_topic: $aws/things/nrf-352656100880619/shadow/update[0m
2020-07-23T15:33:12.943Z DEBUG modem << [00:00:00.319,305] [0m<dbg> nrf_cloud_transport.nct_topics_populate: shadow_get_topic: $aws/things/nrf-352656100880619/shadow/get[0m
2020-07-23T15:33:12.944Z DEBUG modem << [00:00:00.331,481] [0m<inf> asset_tracker: Connecting to LTE network. [0m
2020-07-23T15:33:12.945Z DEBUG modem << [00:00:00.338,226] [0m<inf> asset_tracker: This may take several minutes.[0m
2020-07-23T15:33:12.947Z DEBUG modem << [00:00:00.353,607] [0m<dbg> lte_lc.w_lte_lc_connect: Network mode: AT%XSYSTEMMODE=1,0,1,0[0m
2020-07-23T15:33:14.212Z DEBUG modem << +CEREG: 2,"7F58","0642A00A",7,0,0,"11100000","11100000"
2020-07-23T15:33:14.226Z DEBUG modem << [00:00:01.625,335] [0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 2[0m
2020-07-23T15:33:16.031Z DEBUG modem << +CEREG: 5,"7F58","0642A00A",7,,,"11100000","11100000"
2020-07-23T15:33:16.043Z DEBUG modem >> AT+COPS=3,2
2020-07-23T15:33:16.045Z DEBUG modem << [00:00:03.444,366] [0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 5[0m
2020-07-23T15:33:16.047Z DEBUG modem << [00:00:03.452,667] [0m<inf> asset_tracker: Connected to LTE network[0m
2020-07-23T15:33:16.050Z DEBUG modem << OK
2020-07-23T15:33:16.053Z DEBUG modem >> AT+COPS?
2020-07-23T15:33:16.062Z DEBUG modem << +COPS: 0,2,"302720",7
2020-07-23T15:33:16.063Z DEBUG modem << OK
2020-07-23T15:33:16.069Z DEBUG modem >> AT%XCBAND
2020-07-23T15:33:16.080Z DEBUG modem << %XCBAND: 12
2020-07-23T15:33:16.082Z DEBUG modem << OK
2020-07-23T15:33:16.094Z DEBUG modem >> AT+CGDCONT?
2020-07-23T15:33:16.105Z DEBUG modem << +CGDCONT: 0,"IP","ibasis.iot","10.165.49.39",0,0
2020-07-23T15:33:16.107Z DEBUG modem << OK
2020-07-23T15:33:16.118Z DEBUG modem >> AT+CGACT?
2020-07-23T15:33:16.126Z DEBUG modem << +CGACT: 0,1
2020-07-23T15:33:16.127Z DEBUG modem << OK
2020-07-23T15:33:17.007Z DEBUG modem << [00:00:04.418,334] [0m<dbg> nrf_cloud_transport.nct_connect: IPv4 Address 0x8c81d136[0m
2020-07-23T15:33:24.280Z DEBUG modem << [00:00:11.633,178] [0m<inf> aws_jobs: Subscribe: $aws/things/nrf-352656100880619/jobs/notify-next[0m
2020-07-23T15:33:24.281Z DEBUG modem << [00:00:11.643,554] [0m<inf> aws_jobs: Subscribe: $aws/things/nrf-352656100880619/jobs/$next/get/#[0m
2020-07-23T15:33:24.282Z DEBUG modem << [00:00:11.653,503] [0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_CONNACK[0m
2020-07-23T15:33:24.294Z DEBUG modem << [00:00:11.661,651] [0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 2[0m
2020-07-23T15:33:24.298Z DEBUG modem << [00:00:11.669,372] [0m<dbg> nrf_cloud.event_handler: NRF_CLOUD_EVT_TRANSPORT_CONNECTED[0m
2020-07-23T15:33:24.299Z DEBUG modem << [00:00:11.677,490] [0m<inf> asset_tracker: CLOUD_EVT_CONNECTED[0m
2020-07-23T15:33:24.300Z DEBUG modem << [00:00:11.683,593] [0m<dbg> nrf_cloud_transport.nct_cc_connect: nct_cc_connect[0m
2020-07-23T15:33:24.303Z DEBUG modem << [00:00:11.691,741] [0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 3[0m
2020-07-23T15:33:24.559Z DEBUG modem << [00:00:11.955,017] [0m<inf> aws_fota: subscribed to notify-next topic[0m
2020-07-23T15:33:24.561Z DEBUG modem << [00:00:11.961,822] [0m<inf> aws_jobs: Publish topic: $aws/things/nrf-352656100880619/jobs/$next/get[0m
2020-07-23T15:33:24.562Z DEBUG modem << [00:00:11.971,099] [0m<inf> aws_jobs: Publish payload {"clientToken": ""}[0m
2020-07-23T15:33:24.865Z DEBUG modem << [00:00:12.275,054] [0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_SUBACK: id = 2114 result = 0[0m
2020-07-23T15:33:24.933Z DEBUG modem << [00:00:12.316,528] [0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_SUBACK: id = 1234 result = 0[0m
2020-07-23T15:33:24.933Z DEBUG modem << [00:00:12.326,507] [0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 4[0m
2020-07-23T15:33:24.935Z DEBUG modem << [00:00:12.334,197] [0m<dbg> nrf_cloud_transport.nct_cc_send: mqtt_publish: id = 5678 opcode = 0 len = 0[0m
2020-07-23T15:33:24.937Z DEBUG modem << [00:00:12.344,512] [0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 5[0m
2020-07-23T15:33:25.184Z DEBUG modem << [00:00:12.593,048] [0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_PUBACK: id = 64819 result = 0[0m
2020-07-23T15:33:25.226Z DEBUG modem << [00:00:12.633,666] [0m<dbg> aws_fota.on_publish_evt: Received topic: $aws/things/nrf-352656100880619/jobs/$next/get/accepted[0m
2020-07-23T15:33:25.246Z DEBUG modem << [00:00:12.645,111] [0m<inf> aws_fota: Checking for an available job[0m

Thanks in advance