Attachments (9) Download All
Nordic Case Info
  • Case ID: 231284
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nRF9160 DK Connecting problems with nRF Cloud

Bergmann

Hello, I tried to set up my nRF9160 with this tutorial and there is a problem:

https://www.youtube.com/watch?v=jZQcmU3KIMY&t=216s

According to the tutorial, LED 3 and the LED 4 should be blinking after 3 minutes, what means that the board is connected to the nRF Cloud.
However on my nRF9160, the LED 4  never starts blinking, even if I wait 10 minutes longer than required.
I tried to push the reset button a few times, I turned the nRF9160 on and off a few times and I also started the "Add LTE Device" on nRF Cloud a few times.

But LED 4 still remains dark.

There were 2 things different compared to the tutorial video:


1) The Sim Card Registration worked fine, but when I came to the window in the picture below, I had an IMEI, but I found no PIN. So, I tried the option without a pin (Red mark in the picture).

Maybe I need a PIN, but where do I get it? I tried to insert every possible number I found on my nRF9160, but none of them worked. 

I have already installed the latest firmware update for the nRF9160 successfully. So what did I do wrong? Or how can I finally connect the nRF9160 to the nRF Cloud?

- Thanks for your answers

- Bergmann

Parents
  • 0

    Hi Bergmann, 

    Bergmann said:
    I have already installed the latest firmware update for the nRF9160 successfully

    You have updated the modem firmware to the latest version that is found here?

    I assume that you are using a iBasis SIM, since you activated it through the nRF Cloud site. Where are you based? Have you verified that you have LTE-M coverage in your area(see this page)?

    Best regards

    Bjørn

  • 0 in reply to bjorn-spockeli

    Ok, the country where I am based isn't in that list.
    So I might need a Sim Card of local provider. :)

    Thanks for your answer!

  • 0 in reply to Bergmann

    Hi, if you get -111 there is an issue with the certificates. Try running through this tutorial and trying again.

    Yes, the IP address will change constantly, which is why this is just a workaround to see if the DNS lookup was the actual problem.

    For developing and testing, you should be on a network that supports this.

  • 0 in reply to Heidi

    Hi, I updated the certificate successfully:

    On the last step, where you must delete the device from the nrf cloud, it said:

    But my nrf never got connected to the cloud anyway, so I might ignore this error message.

    Then I flashed the nrf with the asset_tracker again and I updated the host IP address to the prj.conf, but there is error -111 again:

    Fullscreen 2019-10-13T07_19_15.499Z-log.txt Download

    Do you have any ideas?

    Another question: The goal of my project with the nrf is to send some data from the nrf to a server. Should this be already be possible in this state? So, I could skip the step of getting into the nrf cloud and focus on sending the data to a server.

    Thanks for your help and answers!

  • 0 in reply to Bergmann

    Hi, did you remember to re-add the device to nRF Cloud before connecting?

    You don't have to be able to connect to nRF Cloud to send data to an external server. But I recommend it, so you are sure there is nothing wrong with your device or the connection.

  • 0 in reply to Heidi

    Hi, do you mean like this:

    Now I have to insert the HWID and then it says the device has to be connected to nrf Cloud. I tried this step a couple of times, but every time I get the error message.

    Or do I have to re-add the device somewhere else?

    Thanks for your help and answers!

  • 0 in reply to Bergmann

    You are getting this error because the device isn't connected to nRF Cloud. It has to be connected before you can re-add the device.

    I see from your log you are only waiting three minutes for a connection. On average, this takes much longer. Please wait at least 60 minutes before closing the modem. If it still hasn't connected, please attach the output log again.

Reply
  • 0 in reply to Bergmann

    You are getting this error because the device isn't connected to nRF Cloud. It has to be connected before you can re-add the device.

    I see from your log you are only waiting three minutes for a connection. On average, this takes much longer. Please wait at least 60 minutes before closing the modem. If it still hasn't connected, please attach the output log again.

Children
  • 0 in reply to Heidi

    Hi, in the last time, i talked a bit with my local Sim Card provider about the problem and he said the Sim Card is provided with 2 APNs: alliot.nbiot.at and m2m.nbiot.t-mobile.at. The alliot.nbiot.at is the default one and goes over an iot-gateway, which needs to be configurated. The second m2m.nbiot.t-mobile.at is an public APN and doesn't go over the iot-gateway. When I opened the AT client in the LTE Monitor, i was able to connect to the second APN with the command AT+CGDCONT=0,"IP","m2m.nbiot.t-mobile.at".

    Is there a command, that I can add to the prj.conf file of my asset_tracker project, so that it takes the second APN? When I use the asset_tracker, it always takes the first APN.

    Thanks for your answers!

  • 0 in reply to Bergmann

    Hi! 

    As this question does not directly relate to the original issue, please make a new ticket. This will make it easier for other users to find questions similar to theirs.

    Best regards,

    Heidi

  • +1 in reply to Heidi

    Hi, I was now finally able to send data from the nRF with a Sim Card from a local provider to my TCP Server. This was the goal, I wanted to accomplish with this ticket and I want to close it now. I wasn't able to connect to nRF Cloud, but for my use-case, that is now not important anymore.

    To set up the connection with a TCP Server, I opened a new ticket here, which includes a test project to connect to the Google server:

    https://devzone.nordicsemi.com/f/nordic-q-a/53940/connection-problems-to-a-tcp-server

    I want to thank you Heidi and bjorn-spockeli for your big help and persistence with me. The Devzone Forum has the best admins I have ever seen!

    Thanks for your help and your time! You really helped me a lot with my project!

Terms of service