Can not activate SIM

[KevinA]

There was an error submitting your user information. This SIM cannot be activated.

Again and again I get the same crap, I can't activate my nRF9160-DK without the SIM working and this excuse for a user interface will not accept my information.

It has taken all day to get here just to fail. I can not imagine provisioning having to be this complex.

[Øyvind]

Hello, 

I fully acknowledge the anger and disappointment of not being able to register and activate the SIM. Can you please add what error message you are receiving when it fails? Maybe I can help to clear the confusion. You are right, the provisioning part should not be this complicated. 

What SIM are you trying to activate? Can you please go through the steps that you have done?

Thank you! 

Kind regards,
Øyvind

[KevinA]

The Error: There was an error submitting your user information. This SIM cannot be activated.

It appears you have to register the SIM that comes with the nRF9160-DK from iBASIS then on another page install the device information after the SIM has been registered.

Here is the error as an image:

I filled out the required information, the first time I used by PO BOX which causes problems with people do not understand rural living, when the process rejected my user information I deleted the SIM and closed the browser then started over using my street address, same error.

[KevinA]

The Video is the main Unbox and get your Nordic nRF9160 DK up and running. I was created when you were shipping 0.9.0 boards with v1.4.0 SDK, since then you have installed certs allowing the end users to by-pass that (jump to the 9:36 minute mark), you have nRF Connect Desktop 3.6.1 which installs everything for Windows 10 users and the tools which making dealing with this complex hardware as easy as running Arduino. The message: " Perhaps if the error spoke English:" an example of an Error message I would have used instead of "Trouble shoot nRF code 40412".

The images are from " LTE Link Monitor" Great tool, lots of information now if you could add scripting to it.. Last year there was only Verizon here, looks like Sprint and T-Mobile moved in. Thanks for the help!

[Øyvind]

KevinA said:

The images are from " LTE Link Monitor"

You are completely correct, my brain did not connect. With regards to the error message that you received in nRF Cloud (Trouble shoot nRF code 40412), the terminal window should provide some information regarding current status. 

KevinA said:

Trouble shoot nRF code 40412

 Clicking on the link embedded in 40412  will lead you to nRF Cloud Error Codes

nRF Code	Error	Reason	Solution
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: You entered the device id and/or ownership code (PIN or HWID) incorrectly. Before attempting association, you did not wait for the LEDs to indicate the device was provisioned. Corrupt modem firmware. Corrupt, wrongly flashed, or illegitimate device certificates. Poor LTE connection	Solutions that match the possible reasons are listed here. For items 2-4, refer to the nRF9160 DK Getting Started Guide. Verify the values and try again. For Nordic Semiconductor products, please see the solution for nRF Code 40411, above. Check the LED status indicators to ensure the device indicates it was provisioned. (Re-)flash the latest modem firmware. Flash new device certificates obtained from the CreateDeviceCertificate endpoint. Move to a location with a better LTE connection.

Also, the LEDs on the DK will indicate current status as described under "User Interface" in Asset Tracker documentation.

 

KevinA said:

The Video is the main Unbox and get your Nordic nRF9160 DK up and running

 I will report the video to product marketing and have them verify the information provided.

Have a good day!

Kind regards,
Øyvind

[eabase]

Can you guys please update the nice flow diagram above, with the new colors and functionalities in the latest FW? (RIght now there is only a text table... and several link to new docs are dead.

[Øyvind]

Hello, the updated information about the application  Asset Tracker, now in version 2 can be found in our nRF Connect SDK documentation. Unfortunately, the flow diagram has been removed. The LED indications are found under the User Interface module.

For nRF Cloud, the nRF Cloud error codes are found under nRF Cloud REST API, with documentation available under docs.nrfcloud.com.

Kind regards,
Øyvind

[eabase]

Thank you Øyvind.

What is the meaning of Active/Passive modes, in that table?

Also it seem that that there is no indication for the connected state?

[Øyvind]

eabase , it is better to open a new ticket with your questions as these do not fit the title of the current ticket. Also, the ticket is fairly old and includes some outdated information as you have seen.

The active/passive modes are described under Application behavior and functionality --> Real-Time configurations.

eabase said:

Also it seem that that there is no indication for the connected state?

Connected in what way? To LTE or to the cloud? 

[eabase]

Indication for connection to LTE.

[Øyvind]

For the application that would be all other than yellow and red IMO. 

State	Thingy:91 RGB LED	nRF9160 DK solid LEDs
LTE connection search	Yellow, blinking	LED1 blinking
Location search	Purple, blinking	LED2 blinking
Cloud association	White, double pulse blinking	LED3 double pulse blinking
Connecting to cloud	Green, triple pulse blinking	LED3 triple pulse blinking
Publishing data	Green, blinking	LED3 blinking
Active mode	Light blue, blinking	LED4 blinking
Passive mode	Dark blue, blinking	LED3 and LED4 blinking
Error	Red, static	All 4 LEDs blinking
FOTA update	Orange, rapid blinking	LED1 and LED2 blinking
Completion of FOTA update	Orange, static	LED1 and LED2 static