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

Asset Tracker not connecting to nRF Cloud

Hello,

I have an nRF9160 DK and a Thingy:91. Both have been running asset_tracker for more than 3 hours, but none achieved an LTE Connection. I have installed the latest firmware available (mfw_nrf9160_1.2.0) on both. I have updated their certificates on nRF Cloud. I have tested: 2 iBasis SIM Cards, a Vodafone SIM Card and a Telefonica SIM Card at different locations. Approximately a month ago I was able to connect successfully to the nRF Cloud with the Thingy:91 using both iBasis SIM card and Vodafone SIM card from one of the locations (my home).

When using at_client, I was able to see a Vodafone Network with the DK, but not with the Thingy. I tried to manually connect to Vodafone and iBasis networks by using:

AT+CGDCONT=1,"IP","ep.inetd.gdsp" and AT+COPS=1,2,"21401" for Vodafone on the Thingy and on the DK, unsuccessfully.

AT+CGDCONT=1,"IP","ibasis.iot" and AT+COPS=1,2,"21403" for iBasis on the Thingy and on the DK, unsuccessfully.

I have also tried to connect to any network automatically using COPS = 0, unsuccessfully.

My purpose is not to connect to nRF Cloud, but to check internet connection successfully (by doing a ping or sending a udp packet). With at_client I am unable to do a ping nor a udp packet (using the LTE Link Monitor). Also, the combination of LTE Link Monitor + Serial LTE Monitor is horribly slow. That's why I chose to test asset_tracker.

When I call the AT+COPS=? command. I am only able to see Vodafone when I am using the DK, not with the Thingy.

Could you provide me a list of tests I should perform that would help me debugging this problem?

Thank you,

Aleix.

Parents Reply Children
No Data
Related