• State Not Answered
  • Replies 1 reply
  • Subscribers 86 subscribers
  • Views 506 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 277102
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Can not register my new NRF9160 DK on Cloud

danielb1194

Just the title, the cloud website returns error code 40412

Just like in the instructions, input field is nrf-XXXXXXXXXXXXXXX where "X" is the 15 digit IMEI on the back of the DK.

Any help is appreciated.

Parents
  • 0

    Hello, 

    The error code 40412 links to a description of the error with the following information:

    40412
    		 No device found for this id. The device has not yet been provisioned. The device cannot be found in the device registry, i.e., it is not 'known' by the IoT cloud platform. Possible reasons:

    1. You entered the device id and/or ownership code (PIN or HWID) incorrectly.
    2. Before attempting association, you did not wait for the LEDs to indicate the device was provisioned.
    3. Corrupt modem firmware.
    4. Corrupt, wrongly flashed, or illegitimate device certificates.
    5. Poor LTE connection
    		 Solutions that match the possible reasons are listed here. For items 2-4, refer to the nRF9160 DK Getting Started Guide or Thingy:91 Getting Started Guide.

    1. Verify the values and try again. For Nordic Semiconductor products, please see the solution for nRF Code 40411, above.
    2. Check the LED status indicators to ensure the device indicates it was provisioned.
    3. (Re-)flash the latest modem firmware.
    4. Flash new device certificates obtained from the CreateDeviceCertificate endpoint.
    5. Move to a location with a better LTE connection.

    Have you followed the instructions provided? The LEDs that the instructions refer to are found under nRF9160: Asset Tracker application user interface. We also encourage using the LTE Link Monitor app found in nRF Connect for Desktop

    Kind regards,
    Øyvind

Reply
  • 0

    Hello, 

    The error code 40412 links to a description of the error with the following information:

    40412
    		 No device found for this id. The device has not yet been provisioned. The device cannot be found in the device registry, i.e., it is not 'known' by the IoT cloud platform. Possible reasons:

    1. You entered the device id and/or ownership code (PIN or HWID) incorrectly.
    2. Before attempting association, you did not wait for the LEDs to indicate the device was provisioned.
    3. Corrupt modem firmware.
    4. Corrupt, wrongly flashed, or illegitimate device certificates.
    5. Poor LTE connection
    		 Solutions that match the possible reasons are listed here. For items 2-4, refer to the nRF9160 DK Getting Started Guide or Thingy:91 Getting Started Guide.

    1. Verify the values and try again. For Nordic Semiconductor products, please see the solution for nRF Code 40411, above.
    2. Check the LED status indicators to ensure the device indicates it was provisioned.
    3. (Re-)flash the latest modem firmware.
    4. Flash new device certificates obtained from the CreateDeviceCertificate endpoint.
    5. Move to a location with a better LTE connection.

    Have you followed the instructions provided? The LEDs that the instructions refer to are found under nRF9160: Asset Tracker application user interface. We also encourage using the LTE Link Monitor app found in nRF Connect for Desktop

    Kind regards,
    Øyvind

Children
No Data
Related
Terms of service