Thingy:91

Hello!

I am trying to connect my Thingy91 to nrfCloud, but after successfully activating the SIM card, I receive error 40412: No device found for this id. The device has not yet been provisioned.

My device was to begin with registered and could be found under “Devices” in nrfCloud. When updating it with the newest release FW, it just would not connect to the cloud, and it only said, “Please connect your device”, even though the device was on. I then deleted the device from nrfCloud, and tried to add it again, and received error 40412.

When updating the FW I followed the steps in the Getting started with Thingy:91 guide and used the newest release from Nordic Thingy:91 Downloads. After receiving the error, I did so again, in order to verify that I did it correctly the first time, but I still received the error. I repeated this process a lot of times, and still got the same result.

I noted that every time I performed the process of the guide, my device never blinked the way the guide said it should. When trying to connect LTE device to the cloud (step 5-8 in “Connecting to nRF Cloud”) , my device goes directly into blinking green three times, which according to the User Interface page indicates trying to connect to cloud. The guide says that it should blink double white for this step of the setup process, cloud association.

I also had a look at the LTE Link Monitor and noticed that the signaling connection status notification (+CSCON) switches between idle and connected mode. Could this be related to the error code? 

The SIM card was successfully added, when I tried to add the device, and is listed under “SIM card” in nrfCloud. I am also located in Norway, which according to IBASIS should have national LTE-M coverage.  The thingy:91 I am using is version 1.6.0. 

Am I doing something wrong here, that I am just not able to see myself? Or do you have any other suggestion as to why the device won’t connect to nrfCloud?

Thank you in advance!

Best Regards

Martha

  • Hi Martha,

    Thank you for the detailed description. We have started looking at this and will get back to you.

    Best Regards,

    Håkon

  • Which application firmware image did you program into nRF9160, and from which folder?

  • When you update the firmware in the nRF52840 SoC, what does the device look like in the "Select device" menu? Would you be able to take a screenshot?

    I also had a look at the LTE Link Monitor and noticed that the signaling connection status notification (+CSCON) switches between idle and connected mode. Could this be related to the error code? 

    Could you please share the log from LTE Link Monitor? (Click "Open log file" at the bottom.) 

  • I used the folder 2022-09-15_7a358cb7 [Latest version], from Nordic Thingy:91 - Downloads - nordicsemi.com, for programming connectivity bridge, modem and application, as the guide suggested. 

    So: 

    Asset Tracker v2

    Modem Firmware v1.3.2

    Did that answer your question?

  • When pressing SW4 while switching SW1 to ON, for programming of nRF52, the device looks like this, under "Select device": 

     

    Here is the log: 

    2022-11-17T09:30:35.218Z DEBUG modem << +CSCON: 0
    2022-11-17T09:30:35.517Z DEBUG modem << +CSCON: 1
    2022-11-17T09:30:42.882Z DEBUG modem << +CSCON: 0
    2022-11-17T09:30:43.941Z DEBUG modem << [00:00:34.053,741] [0m<inf> app_event_manager: CLOUD_EVT_CONNECTING[0m
    2022-11-17T09:30:45.008Z DEBUG modem << +CSCON: 1
    2022-11-17T09:30:45.961Z DEBUG modem << [00:00:36.048,675] [0m<inf> app_event_manager: CLOUD_EVT_CONNECTION_TIMEOUT[0m
    2022-11-17T09:30:45.962Z DEBUG modem << [00:00:36.049,224] [1;33m<wrn> cloud_module: Cloud connection establishment in progress[0m
    2022-11-17T09:30:45.962Z DEBUG modem << [00:00:36.049,255] [1;33m<wrn> cloud_module: New connection attempt in 64 seconds if not successful[0m
    2022-11-17T09:30:45.963Z DEBUG modem << [00:00:36.049,407] [0m<inf> app_event_manager: CLOUD_EVT_CONNECTING[0m
    2022-11-17T09:30:52.244Z DEBUG modem << +CSCON: 0
    2022-11-17T09:30:52.518Z DEBUG modem << +CSCON: 1
    2022-11-17T09:30:59.779Z DEBUG modem << +CSCON: 0
    2022-11-17T09:31:00.018Z DEBUG modem << +CSCON: 1
    2022-11-17T09:31:01.317Z DEBUG modem << %CESQ: 44,2,16,2
    2022-11-17T09:31:07.371Z DEBUG modem << +CSCON: 0
    2022-11-17T09:31:07.518Z DEBUG modem << +CSCON: 1
    2022-11-17T09:31:07.923Z DEBUG modem << %CESQ: 46,2,21,3
    2022-11-17T09:31:14.651Z DEBUG modem << +CSCON: 0
    2022-11-17T09:31:14.994Z DEBUG modem << %CESQ: 44,2,16,2
    2022-11-17T09:31:15.940Z DEBUG modem << [00:01:06.054,290] [0m<inf> app_event_manager: CLOUD_EVT_CONNECTING[0m
    2022-11-17T09:31:38.668Z DEBUG modem << %CESQ: 48,2,21,3
    2022-11-17T09:31:49.011Z DEBUG modem << +CSCON: 1
    2022-11-17T09:31:49.953Z DEBUG modem << [00:01:40.049,407] [0m<inf> app_event_manager: CLOUD_EVT_CONNECTION_TIMEOUT[0m
    2022-11-17T09:31:49.958Z DEBUG modem << [00:01:40.049,957] [1;33m<wrn> cloud_module: Cloud connection establishment in progress[0m
    2022-11-17T09:31:49.961Z DEBUG modem << [00:01:40.049,987] [1;33m<wrn> cloud_module: New connection attempt in 128 seconds if not successful[0m
    2022-11-17T09:31:49.964Z DEBUG modem << [00:01:40.050,140] [0m<inf> app_event_manager: CLOUD_EVT_CONNECTING[0m
    2022-11-17T09:31:56.157Z DEBUG modem << +CSCON: 0
    2022-11-17T09:31:56.521Z DEBUG modem << +CSCON: 1

    Let me know if you need more of the log. 

Related