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

Problem adding Thingy:91 in the nRF Cloud

Hello,

I try to add a Thingy:91 to the nRF Cloud after I received it today. The sim card got's activated without a problem. When I try to key in my IMEI and the Pin which is printed on the label I receive this error: "There was an error adding your device. It wasn't found. Is it connected?"

How to solve this and add the device to my account?

Parents
  • Hi! 


    Can you confirm that the Thingy:91 is on and the LED is blue and blinking.

    Best regards,

    Heidi

  • Hi Heidi, 

    I think it is more like a blue-withe breathing in a two seconds on and around 5 seconds off interval. 

  • Now it says that it is connected:

    But I still cannot add it in the cloud?!

  • With the same error message as earlier?

  • Could you supply the serial output again?

  • Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    ***** B***** Booting Zephyr OS v1.14.99-ncs2 *****
    [00:00:00.255,615] ·[0m<dbg> board_nonsecure.pca20035_magpio_configure: AT CMD: AT%XMODEMTRACE=0·[0m
    [00:00:00.265,502] ·[0m<dbg> board_nonsecure.pca20035_magpio_configure: AT RESP: OK
    ·[0m
    [00:00:00.273,345] ·[0m<dbg> board_nonsecure.pca20035_magpio_configure: AT CMD: AT%XMAGPIO=1,1,1,7,1,746,803,2,698,748,2,1710,2200,3,824,894,4,880,960,5,791,849,7,1574,1577·[0m
    [00:00:00.289,154] ·[0m<dbg> board_nonsecure.pca20035_magpio_configure: AT RESP: OK
    ·[0m
    [00:00:00.297,027] ·[0m<dbg> board_nonsecure.pca20035_magpio_configure: MAGPIO successfully configured·[0m
    Asset tracker started
    [00:00:00.309,173] ·[0m<dbg> nrf_cloud_transport.nct_client_id_get: client_id = nrf-352656100443962·[0m
    [00:00:00.318,298] ·[0m<dbg> nrf_cloud_transport.nct_topics_populate: shadow_base_topic: $aws/things/nrf-352656100443962/shadow·[0m
    [00:00:00.329,772] ·[0m<dbg> nrf_cloud_transport.nct_topics_populate: accepted_topic: $aws/things/nrf-352656100443962/shadow/get/accepted·[0m
    [00:00:00.342,132] ·[0m<dbg> nrf_cloud_transport.nct_topics_populate: rejected_topic: $aws/things/nrf-352656100443962/shadow/get/rejected·[0m
    [00:00:00.354,492] ·[0m<dbg> nrf_cloud_transport.nct_topics_populate: update_delta_topic: $aws/things/nrf-352656100443962/shadow/update/delta·[0m
    [00:00:00.367,187] ·[0m<dbg> nrf_cloud_transport.nct_topics_populate: update_topic: $aws/things/nrf-352656100443962/shadow/update·[0m
    [00:00:00.378,875] ·[0m<dbg> nrf_cloud_transport.nct_topics_populate: shadow_get_topic: $aws/things/nrf-352656100443962/shadow/get·[0m
    Connecting to LTE network. This may take several minutes.
    [00:00:00.397,369] ·[0m<inf> lte_lc: Using legacy LTE PCO mode...·[0m
    [00:00:06.166,839] ·[0m<dbg> lte_lc.at_handler: recv: +CEREG: 2,"D2F5","01B3850B",9
    ·[0m
    [00:00:08.606,384] ·[0m<dbg> lte_lc.at_handler: recv: +CER[00:00:14.483,215] ·[0m<dbg> lte_lc.at_handler: recv: +CEREG: 2,"D2F5","01B3850B",9
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Reply
  • Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    ***** B***** Booting Zephyr OS v1.14.99-ncs2 *****
    [00:00:00.255,615] ·[0m<dbg> board_nonsecure.pca20035_magpio_configure: AT CMD: AT%XMODEMTRACE=0·[0m
    [00:00:00.265,502] ·[0m<dbg> board_nonsecure.pca20035_magpio_configure: AT RESP: OK
    ·[0m
    [00:00:00.273,345] ·[0m<dbg> board_nonsecure.pca20035_magpio_configure: AT CMD: AT%XMAGPIO=1,1,1,7,1,746,803,2,698,748,2,1710,2200,3,824,894,4,880,960,5,791,849,7,1574,1577·[0m
    [00:00:00.289,154] ·[0m<dbg> board_nonsecure.pca20035_magpio_configure: AT RESP: OK
    ·[0m
    [00:00:00.297,027] ·[0m<dbg> board_nonsecure.pca20035_magpio_configure: MAGPIO successfully configured·[0m
    Asset tracker started
    [00:00:00.309,173] ·[0m<dbg> nrf_cloud_transport.nct_client_id_get: client_id = nrf-352656100443962·[0m
    [00:00:00.318,298] ·[0m<dbg> nrf_cloud_transport.nct_topics_populate: shadow_base_topic: $aws/things/nrf-352656100443962/shadow·[0m
    [00:00:00.329,772] ·[0m<dbg> nrf_cloud_transport.nct_topics_populate: accepted_topic: $aws/things/nrf-352656100443962/shadow/get/accepted·[0m
    [00:00:00.342,132] ·[0m<dbg> nrf_cloud_transport.nct_topics_populate: rejected_topic: $aws/things/nrf-352656100443962/shadow/get/rejected·[0m
    [00:00:00.354,492] ·[0m<dbg> nrf_cloud_transport.nct_topics_populate: update_delta_topic: $aws/things/nrf-352656100443962/shadow/update/delta·[0m
    [00:00:00.367,187] ·[0m<dbg> nrf_cloud_transport.nct_topics_populate: update_topic: $aws/things/nrf-352656100443962/shadow/update·[0m
    [00:00:00.378,875] ·[0m<dbg> nrf_cloud_transport.nct_topics_populate: shadow_get_topic: $aws/things/nrf-352656100443962/shadow/get·[0m
    Connecting to LTE network. This may take several minutes.
    [00:00:00.397,369] ·[0m<inf> lte_lc: Using legacy LTE PCO mode...·[0m
    [00:00:06.166,839] ·[0m<dbg> lte_lc.at_handler: recv: +CEREG: 2,"D2F5","01B3850B",9
    ·[0m
    [00:00:08.606,384] ·[0m<dbg> lte_lc.at_handler: recv: +CER[00:00:14.483,215] ·[0m<dbg> lte_lc.at_handler: recv: +CEREG: 2,"D2F5","01B3850B",9
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Children
  • Try to flash the at_client example, which makes it easier to read information from the modem. 

    thingy91_at_client.hex

    Start with

    AT%XSYSTEMMODE = 0,1,1,0

    to set the supported system modes of the modem.

    Then

    AT%XPCO=0

    to unsubscribe to PCO notifications, because a lot of base stations don't support this yet. 

    Then

    AT+CFUN?

    to read the current functional mode. 

    It can take up to five minutes, so be patient.

    Then attach the output here, thanks!

    Edit:

    AT%XEPCO=0

    is the correct command to unsubscribe to ePCO notifications.

  • The command AT%XSYSTEMMODE = 0,1,1,0 and AT%XPCO=0 fails and AT+CFUN? timed out. Also in the LTE Link Monitor the Modem port gets closed automatically quiet often...

    Here the log file:

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    2019-08-30T07:13:28.034Z INFO Application data folder: C:\Users\TimSahr\AppData\Roaming\nrfconnect\pc-nrfconnect-linkmonitor
    2019-08-30T07:13:28.098Z DEBUG App pc-nrfconnect-linkmonitor v1.1.0 official
    2019-08-30T07:13:28.098Z DEBUG App path: C:\Users\TimSahr\.nrfconnect-apps\node_modules\pc-nrfconnect-linkmonitor
    2019-08-30T07:13:28.099Z DEBUG nRFConnect 3.1.0 is supported by the app (^3.0.0)
    2019-08-30T07:13:28.099Z DEBUG nRFConnect path: C:\Users\TimSahr\AppData\Local\Programs\nrfconnect\resources\app.asar
    2019-08-30T07:13:28.099Z DEBUG HomeDir: C:\Users\TimSahr
    2019-08-30T07:13:28.099Z DEBUG TmpDir: C:\Users\TimSahr\AppData\Local\Temp
    2019-08-30T07:13:39.471Z INFO Modem port is opened
    2019-08-30T07:13:39.479Z DEBUG modem >> AT+CFUN?\x0D\x0A
    2019-08-30T07:13:39.502Z DEBUG modem << +CFUN: 4\x0D
    2019-08-30T07:13:39.505Z DEBUG modem << \x0A
    2019-08-30T07:13:39.506Z DEBUG modem << OK\x0D\x0A\x00
    2019-08-30T07:13:39.519Z DEBUG modem >> AT+CFUN=1\x0D\x0A
    2019-08-30T07:13:39.562Z DEBUG modem << OK\x0D
    2019-08-30T07:13:48.933Z DEBUG modem >> AT%XSYSTEMMODE = 0,1,1,0\x0D\x0A
    2019-08-30T07:13:48.939Z DEBUG modem << ERROR\x0D
    2019-08-30T07:13:48.942Z ERROR Error: AT%XSYSTEMMODE = 0,1,1,0
    failed
    2019-08-30T07:13:52.549Z INFO Modem port is closed
    2019-08-30T07:13:58.469Z INFO Modem port is opened
    2019-08-30T07:13:58.474Z DEBUG modem >> AT+CFUN?\x0D\x0A
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX