Nordic Thingy 91 LED won´t switch to yellow with 1NCE SIM

[Jackhead]

Hello,

I want to connect my Thingy 91 to the nRF Cloud to use LTE Link Monitor and other features. The provided iBasis SIM card isn´t supported in Germany so I got another SIM from 1NCE which has NB-IoT coverage ( I checked it with this map https://t-map.telekom.de/tmap2/mobileiot).

In the getting started guide there is mentioned that I just have to insert the SIM into the Thingy91 and then I have to wait for the LED to change to yellow but this never happens.
The LED always blinks blue or maybe white, basically the standard color when you switch it on.

The SIM is working. A colleague of mine tried the SIM in an LTE modem and it worked fine. They had to enable roaming and change the APN but the SIM seems to be alright.

Why does the Thingy91 never changes to yellow? 

I updated the firmware and due to a suggestion from an older ticket I run the thingy91_nbiot_legacy_pco_dfu_2020-04-29_bc7ade8b.hex file from the the current zip.-file on your page.

Can you please help me to bring the Thingy91 to life? I hope you have some helpful information for me.

Best regards.

[Martin Lesund]

Hi Jackhead,

I would recommend that you flash the AT client to see what you need to do on your first connection.

E.g. 

#In your case first make sure that the Modem is OFF:
AT+CFUN=4

#change to nb-iot
AT%XSYSTEMMODE=0,1,0,0

# Use legacy PCO
AT%XEPCO=0

# Set the APN correctly 
AT+CGDCONT=0,"IP","iot.1nce.net"

# Set the network notification
AT+CEREG=5

#Turn ON the modem
AT+CFUN=1

#Wait til you get connected and call the XMONITOR commant to see the additional info
AT%XMONITOR?

# Then turn OFF the modem with the following command to store the historical data in the NVS
AT+CFUN=0

# wait for OK and then reflash the device with the nb-iot_legacy application (asset_tracker)

Then you should be able to connect.

Best regards,
Martin L.

[Jackhead]

After a while waiting I get some more outputs from the Link Monitor.

I hope this is helpful. 

[00:20:00.443,084] [0m<inf> lte_lc: Network connection attempt timed out[0m
[00:20:00.449,951] [1;31m<err> asset_tracker: LTE link could not be established.[0m
*** Booting Zephyr OS build v2.1.99-ncs1-1145-g13dc96f83bab  ***
Flash regions          Domain          Permissions
00 02 0x00000 0x18000  Secure           rwxl
03 31 0x18000 0x100000 Non-Secure       rwxl
Non-secure callable region 0 placed in flash region 2 with size 32.
SRAM region            Domain           Permissions
00 07 0x00000 0x10000  Secure            rwxl
08 31 0x10000 0x40000  Non-Secure        rwxl
Peripheral             Domain            Status
00 NRF_P0               Non-Secure       OK
01 NRF_CLOCK            Non-Secure       OK 
02 NRF_RTC0             Non-Secure       OK
03 NRF_RTC1             Non-Secure       OK
04 NRF_NVMC             Non-Secure       OK
05 NRF_UARTE1           Non-Secure       OK
06 NRF_UARTE2           Secure           SKIP
07 NRF_TWIM2            Non-Secure       OK
08 NRF_SPIM3            Non-Secure       OK
09 NRF_TIMER0           Non-Secure       OK
10 NRF_TIMER1           Non-Secure       OK
" every status is OK until"
25 NRF_REGULATORS       Non-Secure       OK
SPM: NS image at 0x18200
SPM: NS MSP at 0x200305b0
SPM: NS reset vector at 0x28805
SPM: prepare to jump to Non-Secure image.
*** Booting Zephyr OS build v2.1.9[00:00:00.193,206] [0m<inf> BH1749: BH1749 initialized[0m
[00:00:00.203,918] [0m<inf> asset_tracker: Asset tracker started[0m
[00:00:00.217,193] [0m<dbg> nrf_cloud_transport.nct_client_id_get: client_id = nrf-352656100987208[0m
[00:00:00.226,287] [0m<dbg> nrf_cloud_transport.nct_topics_populate: shadow_base_topic: $aws/things/nrf-352656100987208/shadow[0m
[00:00:00.237,792] [0m<dbg> nrf_cloud_transport.nct_topics_populate: accepted_topic: nrf-352656100987208/shadow/get/accepted[0m
[00:00:00.249,114] [0m<dbg> nrf_cloud_transport.nct_topics_populate: rejected_topic: $aws/things/nrf-352656100987208/shadow/get/rejected[0m
[00:00:00.261,474] [0m<dbg> nrf_cloud_transport.nct_topics_populate: update_delta_topic: $aws/things/nrf-352656100987208/shadow/update/delta[0m
[00:00:00.274,169] [0m<dbg> nrf_cloud_transport.nct_topics_populate: update_topic: $aws/things/nrf-352656100987208/shadow/update[0m
[00:00:00.285,858] [0m<dbg> nrf_cloud_transport.nct_topics_populate: shadow_get_topic: $aws/things/nrf-352656100987208/shadow/get[0
[00:00:00.297,790] [0m<inf> asset_tracker: Connecting to LTE network. [0m
[00:00:00.304,443] [0m<inf> asset_tracker: This may take several minutes.[0m
[00:00:00.320,190] [0m<inf> lte_lc: Using legacy LTE PCO mode...[0m
[00:00:00.326,354] [0m<dbg> lte_lc.w_lte_lc_connect: Network mode: AT%XSYSTEMMODE=0,1,1,0[0m
[00:10:00.373,077] [0m<inf> lte_lc: Network connection attempt timed out[0m
[00:10:00.381,439] [0m<inf> lte_lc: Using fallback network mode[0m
[00:10:00.387,481] [0m<dbg> lte_lc.w_lte_lc_connect: Network mode: AT%XSYSTEMMODE=1,0,1,0[0m

[Martin Lesund]

Please run the plain AT Client sample that is provided in the precompiled.zip folder to avoid the automatic modem_configurations that is already in the Asset_tracker application.
See Contents.txt for information about what the different files are.

Then issue the APN commands and Xsystemmode before you turn ON the modem.