• State Verified Answer
  • +2 person also asked this people also asked this
  • Replies 72 replies
  • Subscribers 71 subscribers
  • Views 15655 views
  • Users 0 members are here
Attachments (9) Download All
Nordic Case Info
  • Case ID: 235085
Options
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

T1mS_

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
  • 0

    Hi! 


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

    Best regards,

    Heidi

  • 0 in reply to Heidi-Irene Harvey Sollie

    Hi Heidi, 

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

  • 0 in reply to T1mS_

    Could you follow the list here in this Thingy:91 FAQ to update to the latest firmware. You can find both the modem firmware and application firmware packages on the Thingy:91 webpage.

    However, according to the iBasis coverage map there is limited coverage in Germany, so that could be the root of the issue. 

  • 0 in reply to Heidi-Irene Harvey Sollie

    What is meant by this:

    Connect the Thingy:91 to the nRF9160DK board’s “Debug out” port using a 10-pin JTAG cable.

    I only have a usb cable and I don't have a  nRF9160DK board

    EDIT: I found a jlink device and now the nRF Programmer recognize the device.

  • 0 in reply to T1mS_

    update process done successfully.

    Error in the nRFCloud remains the same.

    Output of the LTE Link Monitor:

    2019-08-29T11:26:48.400Z INFO Modem port is opened
2019-08-29T11:26:48.406Z DEBUG modem >> AT+CFUN?\x0D\x0A
2019-08-29T11:26:48.415Z DEBUG modem << +CFUN: 1\x0D\x0A
2019-08-29T11:26:48.433Z DEBUG modem << OK\x0D\x0A\x00
2019-08-29T11:26:48.447Z DEBUG modem >> AT+CGSN=1\x0D\x0A
2019-08-29T11:26:48.454Z DEBUG modem << +CGSN: "352656100443962"\x0D
2019-08-29T11:26:48.456Z DEBUG modem << \x0A
2019-08-29T11:26:48.457Z DEBUG modem << OK\x0D\x0A\x00
2019-08-29T11:26:48.460Z DEBUG modem >> AT+CGMI\x0D\x0A
2019-08-29T11:26:48.467Z DEBUG modem << Nordic Semiconductor ASA\x0D
2019-08-29T11:26:48.469Z DEBUG modem << \x0A
2019-08-29T11:26:48.473Z DEBUG modem << OK\x0D\x0A\x00
2019-08-29T11:26:48.476Z DEBUG modem >> AT+CGMM\x0D\x0A
2019-08-29T11:26:48.482Z DEBUG modem << nRF9160-SICA\x0D
2019-08-29T11:26:48.487Z DEBUG modem << \x0A
2019-08-29T11:26:48.489Z DEBUG modem << OK\x0D\x0A\x00
2019-08-29T11:26:48.491Z DEBUG modem >> AT+CGMR\x0D\x0A
2019-08-29T11:26:48.497Z DEBUG modem << mfw_nrf9160_1.0.0\x0D\x0A
2019-08-29T11:26:48.502Z DEBUG modem << OK\x0D\x0A\x00
2019-08-29T11:26:48.504Z INFO Nordic Semiconductor ASA nRF9160-SICA [mfw_nrf9160_1.0.0] SerNr: 352656100443962
2019-08-29T11:26:48.505Z DEBUG modem >> AT+CEMODE?\x0D\x0A
2019-08-29T11:26:48.512Z DEBUG modem << +CEMODE: 2\x0D
2019-08-29T11:26:48.514Z DEBUG modem << \x0A
2019-08-29T11:26:48.516Z DEBUG modem << OK\x0D\x0A\x00
2019-08-29T11:26:48.525Z DEBUG modem >> AT%XCBAND=?\x0D\x0A
2019-08-29T11:26:48.534Z DEBUG modem << %XCBAND: (2,3,4,8,12,13,20,28)\x0D\x0A
2019-08-29T11:26:48.536Z DEBUG modem << OK\x0D\x0A\x00
2019-08-29T11:26:48.543Z DEBUG modem >> AT+CMEE?\x0D\x0A
2019-08-29T11:26:48.552Z DEBUG modem << +CMEE: 0\x0D
2019-08-29T11:26:48.556Z DEBUG modem << \x0A
2019-08-29T11:26:48.557Z DEBUG modem << OK\x0D\x0A\x00
2019-08-29T11:26:48.560Z DEBUG modem >> AT+CMEE=1\x0D\x0A
2019-08-29T11:26:48.565Z DEBUG modem << OK\x0D
2019-08-29T11:26:48.570Z DEBUG modem >> AT+CNEC?\x0D\x0A
2019-08-29T11:26:48.574Z DEBUG modem << +CNEC: 0\x0D\x0A
2019-08-29T11:26:48.576Z DEBUG modem << OK\x0D\x0A\x00
2019-08-29T11:26:48.579Z DEBUG modem >> AT+CNEC=24\x0D\x0A
2019-08-29T11:26:48.585Z DEBUG modem << OK\x0D
2019-08-29T11:26:48.587Z DEBUG modem >> AT+CGEREP?\x0D\x0A
2019-08-29T11:26:48.592Z DEBUG modem << +CGEREP: 0,0\x0D
2019-08-29T11:26:48.594Z DEBUG modem << \x0A
2019-08-29T11:26:48.595Z DEBUG modem << OK\x0D\x0A\x00
2019-08-29T11:26:48.601Z DEBUG modem >> AT+CGDCONT?\x0D\x0A
2019-08-29T11:26:48.606Z DEBUG modem << OK\x0D
2019-08-29T11:26:48.609Z DEBUG modem >> AT+CGACT?\x0D\x0A
2019-08-29T11:26:48.613Z DEBUG modem << OK\x0D
2019-08-29T11:26:48.618Z DEBUG modem >> AT+CGEREP=1\x0D\x0A
2019-08-29T11:26:48.623Z DEBUG modem << OK\x0D
2019-08-29T11:26:48.626Z DEBUG modem >> AT+CIND=1,1,1\x0D\x0A
2019-08-29T11:26:48.630Z DEBUG modem << OK\x0D
2019-08-29T11:26:48.635Z DEBUG modem >> AT+CEREG=2\x0D\x0A
2019-08-29T11:26:48.639Z DEBUG modem << OK\x0D
2019-08-29T11:26:48.643Z DEBUG modem >> AT+CEREG?\x0D\x0A
2019-08-29T11:26:48.652Z DEBUG modem << +CEREG: 2,4,"FFFE","FFFFFFFF",7\x0D
2019-08-29T11:26:48.655Z DEBUG modem << \x0A
2019-08-29T11:26:48.656Z DEBUG modem << OK\x0D\x0A\x00
2019-08-29T11:26:48.661Z DEBUG modem >> AT%CESQ=1\x0D\x0A
2019-08-29T11:26:48.665Z DEBUG modem << OK\x0D\x0A
2019-08-29T11:26:48.670Z DEBUG modem >> AT+CESQ\x0D\x0A
2019-08-29T11:26:48.676Z DEBUG modem << +CESQ: 99,99,255,255,255,255\x0D
2019-08-29T11:26:48.678Z DEBUG modem << \x0A
2019-08-29T11:26:48.679Z DEBUG modem << OK\x0D\x0A\x00
2019-08-29T11:26:48.686Z DEBUG modem >> AT%XSIM=1\x0D\x0A
2019-08-29T11:26:48.690Z DEBUG modem << OK\x0D
2019-08-29T11:26:48.693Z DEBUG modem >> AT%XSIM?\x0D\x0A
2019-08-29T11:26:48.697Z DEBUG modem << %XSIM: 1\x0D
2019-08-29T11:26:48.703Z DEBUG modem << \x0A
2019-08-29T11:26:48.704Z DEBUG modem << OK\x0D\x0A\x00
2019-08-29T11:26:48.711Z DEBUG modem >> AT+CPIN?\x0D\x0A
2019-08-29T11:26:48.718Z DEBUG modem << +CPIN: READY\x0D
2019-08-29T11:26:48.721Z DEBUG modem << \x0A
2019-08-29T11:26:48.722Z DEBUG modem << OK\x0D\x0A\x00
2019-08-29T11:26:48.727Z DEBUG modem >> AT+CPINR="SIM PIN"\x0D\x0A
2019-08-29T11:26:48.739Z DEBUG modem << +CPINR: "SIM PIN",3\x0D
2019-08-29T11:26:48.740Z DEBUG modem << \x0A
2019-08-29T11:26:48.741Z DEBUG modem << OK\x0D\x0A\x00
2019-08-29T11:26:48.745Z DEBUG modem >> AT+CIMI\x0D\x0A
2019-08-29T11:26:48.751Z DEBUG modem << 204080813515161\x0D
2019-08-29T11:26:48.753Z DEBUG modem << \x0A
2019-08-29T11:26:48.754Z DEBUG modem << OK\x0D\x0A\x00
2019-08-29T11:26:48.754Z INFO IMSIdentity: 204080813515161
2019-08-29T11:26:48.873Z INFO Modem port is closed

    Serial output:

    ***** B***** Booting Zephyr OS v1.14.99-ncs2 *****
[00:00:00.388,580] <dbg> board_nonsecure.pca20035_magpio_configure: AT CMD: AT%XMODEMTRACE=0
[00:00:00.398,468] <dbg> board_nonsecure.pca20035_magpio_configure: AT RESP: OK

[00:00:00.406,341] <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
[00:00:00.422,119] <dbg> board_nonsecure.pca20035_magpio_configure: AT RESP: OK

[00:00:00.429,992] <dbg> board_nonsecure.pca20035_magpio_configure: MAGPIO successfully configured
Asset tracker started
[00:00:00.442,108] <dbg> nrf_cloud_transport.nct_client_id_get: client_id = nrf-352656100443962
[00:00:00.451,202] <dbg> nrf_cloud_transport.nct_topics_populate: shadow_base_topic: $aws/things/nrf-352656100443962/shadow
[00:00:00.462,707] <dbg> nrf_cloud_transport.nct_topics_populate: accepted_topic: $aws/things/nrf-352656100443962/shadow/get/accepted
[00:00:00.475,067] <dbg> nrf_cloud_transport.nct_topics_populate: rejected_topic: $aws/things/nrf-352656100443962/shadow/get/rejected
[00:00:00.487,426] <dbg> nrf_cloud_transport.nct_topics_populate: update_delta_topic: $aws/things/nrf-352656100443962/shadow/update/delta
[00:00:00.500,122] <dbg> nrf_cloud_transport.nct_topics_populate: update_topic: $aws/things/nrf-352656100443962/shadow/update
[00:00:00.511,810] <dbg> nrf_cloud_transport.nct_topics_populate: shadow_get_topic: $aws/things/nrf-352656100443962/shadow/get
Connecting to LTE network. This may take several minutes.
[00:00:46.705,657] <dbg> lte_lc.at_handler: recv: +CEREG: 2,"FFFE","FFFFFFFF",7


  • 0 in reply to T1mS_

    Yes, the reason you can't connect is that iBasis only has limited LTE-M coverage in Germany.

    I would suggest using a SIM card from a local carrier that supports NB-IoT and flashing this firmware to the Thingy:91. 

     thingy91_nbiot_legacy_pco_v0.2.2.hex

  • 0 in reply to Heidi-Irene Harvey Sollie

    Flashed the firmware and will report back.

    My second sim is from 1nce.com. It should support NB-IoT:

    They are using the telekom network which is, regarding to the map, available at my location:

Reply Children
No Data
Related