nRF 9160 DK - Asset Tracker (and NTP) not working (nrf_cloud_connect_failed: 22)

RE: nRF 9160 DK - Asset Tracker (and NTP) not working (nrf_cloud_connect_failed: 22)

pastucha.grzegorz — Fri, 18 Oct 2019 06:33:56 GMT

Hi,

at the time the APN was disappearing after cutting off the power, but I was able to change it with +CGDCONT command. You need to turn off the module first (by AT command), because CID0 can't be changed otherwise. In order to make it default (I'm not sure if this is the correct way, but here's how I did it and it worked), I changed it in the config files:

- initial project config - conf in the project folder:

CONFIG_LTE_NETWORK_MODE_NBIOT=y
CONFIG_LTE_PDP_CMD=y

after building the project (it was overwritten after every change of the project config), in build_nrf9160_pca10090ns/zephyr/.config :

CONFIG_LTE_PDP_CONTEXT="0,\"IP\",\"test.nbiot\"".

After building the project once again, it should be the default APN. Good luck.

RE: nRF 9160 DK - Asset Tracker (and NTP) not working (nrf_cloud_connect_failed: 22)

Terje K Wahl — Thu, 17 Oct 2019 11:38:44 GMT

Hi, I have a similar problem of not being able to change the APN. If you could provide details on how you managed to get it to work ("I've managed to put it into the project configuration files and it worked"), that would be great!

Kind regards, Terje

RE: nRF 9160 DK - Asset Tracker (and NTP) not working (nrf_cloud_connect_failed: 22)

pastucha.grzegorz — Tue, 16 Jul 2019 12:48:57 GMT

Okay, the AT command method just didn't work, it still insisted on the old APN. I've managed to put it into the project configuration files and it worked, so the issue was about the wrong APN the whole time. Now everything works as expected, including NTP and FTP examples even through DNS, but the asset_tracker has some problems still - this time it's -111 error and honestly I don't care about it anymore. Now I'm looking forward to make the whole system compatible with our software that is using AT commands for IP traffic, so I tried to run the uart sample, but somehow even this one has some problems. I guess it's a topic for another question because I've extended this one to the extreme anyway.

Thank you for your time.

RE: nRF 9160 DK - Asset Tracker (and NTP) not working (nrf_cloud_connect_failed: 22)

Håkon Alseth — Mon, 15 Jul 2019 11:37:53 GMT

Try to only set the APN, then issue cfun=0:

1. AT+CGDCONT=...

2. AT+CFUN=0

3. Reset the board after "OK" has been printed.

If it still does not work, add it to your firmware as a startup command.

RE: nRF 9160 DK - Asset Tracker (and NTP) not working (nrf_cloud_connect_failed: 22)

pastucha.grzegorz — Mon, 15 Jul 2019 10:20:02 GMT

Yes, i've tried many combinations but the old APN is still coming back:

1. +CFUN = 0
2. +CGDCONT=0,"IP","test.nbiot",,,,0
3. +CFUN = 1
4. <connect to the network>
5. +CFUN = 0
6. <RESET>

1. +CFUN = 0
2. +CGDCONT=0,"IP","test.nbiot",,,,0
4. +CFUN = 0
5. <RESET>

None of these work.

RE: nRF 9160 DK - Asset Tracker (and NTP) not working (nrf_cloud_connect_failed: 22)

Håkon Alseth — Mon, 15 Jul 2019 10:02:52 GMT

Hi,

try setting the APN, then issuing at+cfun=0. Then reboot/reset the kit after you get the "OK" back.

[quote user="pastucha.grzegorz"]Also, are there any plans for supporting IP traffic through AT commands? [/quote]

This is not something we have at this moment. All IP traffic must be set using socket operations.

Kind regards,

Håkon

RE: nRF 9160 DK - Asset Tracker (and NTP) not working (nrf_cloud_connect_failed: 22)

pastucha.grzegorz — Mon, 15 Jul 2019 08:27:35 GMT

Also, are there any plans for supporting IP traffic through AT commands? This is a bit of a deal breaker, as we'd have to make drastic changes in our software.

RE: nRF 9160 DK - Asset Tracker (and NTP) not working (nrf_cloud_connect_failed: 22)

pastucha.grzegorz — Mon, 15 Jul 2019 06:35:23 GMT

Well, it doesn't work. The APN is remembered after changing the mode to offline (4), but power off just resets it to the default one.

at+cgdcont?
+CGDCONT: 0,"IP","aiut.nbiot","10.12.0.2",0,0
OK
at+cfun=0
OK
AT+CFUN?
+CFUN: 4
OK
at+cgdcont=0,"IP","test.nbiot",,,,0
OK
AT+CFUN=1
OK
at+cgdcont?
+CGDCONT: 0,"IP","test.nbiot","100.120.208.204",0,0
OK
at+cgcontrdp=0
+CGCONTRDP: 0,,"test.nbiot","","","213.158.199.1","213.158.199.5",,,,,1500
OK
at+cfun=4
OK
AT+CFUN?
+CFUN: 4
OK
AT+CFUN=1
OK
at+cgdcont?
+CGDCONT: 0,"IP","test.nbiot","100.120.208.206",0,0
OK
at+cfun=0
OK
at+cfun=1
OK
AT+CFUN?
+CFUN: 1
OK
at+cgdcont?
+CGDCONT: 0,"IP","aiut.nbiot","10.12.0.2",0,0
OK

RE: nRF 9160 DK - Asset Tracker (and NTP) not working (nrf_cloud_connect_failed: 22)

Håkon Alseth — Fri, 12 Jul 2019 14:01:39 GMT

Set the APN manually, then issue "AT+CFUN=0" to store it persistently.

When you reboot, it should now have the APN that you set.

Kind regards,

Håkon

RE: nRF 9160 DK - Asset Tracker (and NTP) not working (nrf_cloud_connect_failed: 22)

pastucha.grzegorz — Fri, 12 Jul 2019 13:38:59 GMT

No, I don't have the iBasis SIM. I'm trying to use different APN now. I'm able to do that manually in at_client and it does connect successfully:

at+cgdcont?
+CGDCONT: 0,"IP","test.nbiot","100.88.198.213",0,0

However, after restarting the module it just insists to use the old APN (aiut.nbiot), even when I didn't specify it. I guess the same is happening when loading a program and it connects to the network automatically (like the ftp you've sent me to test). Is there a way to stop it from connecting to the old APN?

RE: nRF 9160 DK - Asset Tracker (and NTP) not working (nrf_cloud_connect_failed: 22)

Håkon Alseth — Fri, 12 Jul 2019 08:41:07 GMT

Hi,

Thank you for the log.

Do you have a iBasis SIM card you can try with nb-iot to see if this works better?

Have you contacted your current local carrier and asked about the issues you are seeing? DNS does not seem to be provided by the network, and I would also recommend asking if they have any restriction in TCP based traffic on NB-IoT.

Kind regards,

Håkon

RE: nRF 9160 DK - Asset Tracker (and NTP) not working (nrf_cloud_connect_failed: 22)

pastucha.grzegorz — Fri, 12 Jul 2019 07:47:22 GMT

Here's the log:

2019-07-12T07:44:12.005Z DEBUG modem << ***** Booting Zephyr OS v1.14.99-ncs1 *****\x0D
2019-07-12T07:44:12.009Z DEBUG modem << \x0A
2019-07-12T07:44:12.012Z DEBUG modem << Flash region\x09\x09Domain\x09\x09Permissions\x0D
2019-07-12T07:44:12.024Z DEBUG modem << \x0A
2019-07-12T07:44:12.035Z DEBUG modem << 00 0x00000 0x08000 \x09Secure\x09\x09rwxl\x0D\x0A
2019-07-12T07:44:12.065Z DEBUG modem << 01 0x08000 0x10000 \x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.069Z DEBUG modem << 02 0x10000 0x18000 \x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.074Z DEBUG modem << 03 0x18000 0x20000 \x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.079Z DEBUG modem << 04 0x20000 0x28000 \x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.083Z DEBUG modem << 05 0x28000 0x30000 \x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.085Z DEBUG modem << 06 0x30000 0x38000 \x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.088Z DEBUG modem << 07 0x38000 0x40000 \x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.090Z DEBUG modem << 08 0x40000 0x48000 \x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.092Z DEBUG modem << 09 0x48000 0x50000 \x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.097Z DEBUG modem << 10 0x50000 0x58000 \x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.100Z DEBUG modem << 11 0x58000 0x60000 \x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.117Z DEBUG modem << 12 0x60000 0x68000 \x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.120Z DEBUG modem << 13 0x68000 0x70000 \x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.126Z DEBUG modem << 14 0x70000 0x78000 \x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.129Z DEBUG modem << 15 0x78000 0x80000 \x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.133Z DEBUG modem << 16 0x80000 0x88000 \x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.135Z DEBUG modem << 17 0x88000 0x90000 \x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.137Z DEBUG modem << 18 0x90000 0x98000 \x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.139Z DEBUG modem << 19 0x98000 0xa0000 \x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.143Z DEBUG modem << 20 0xa0000 0xa8000 \x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.146Z DEBUG modem << 21 0xa8000 0xb0000 \x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.151Z DEBUG modem << 22 0xb0000 0xb8000 \x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.152Z DEBUG modem << 23 0xb8000 0xc0000 \x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.154Z DEBUG modem << 24 0xc0000 0xc8000 \x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.155Z DEBUG modem << 25 0xc8000 0xd0000 \x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.157Z DEBUG modem << 26 0xd0000 0xd8000 \x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.158Z DEBUG modem << 27 0xd8000 0xe0000 \x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.160Z DEBUG modem << 28 0xe0000 0xe8000 \x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.180Z DEBUG modem << 29 0xe8000 0xf0000 \x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.183Z DEBUG modem << 30 0xf0000 0xf8000 \x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.187Z DEBUG modem << 31 0xf8000 0x100000 \x09Non-Secure\x09rwxl\x0D\x0A\x0D\x0A
2019-07-12T07:44:12.191Z DEBUG modem << SRAM region\x09\x09Domain\x09\x09Permissions\x0D\x0A
2019-07-12T07:44:12.194Z DEBUG modem << 00 0x00000 0x02000\x09Secure\x09\x09rwxl\x0D\x0A
2019-07-12T07:44:12.197Z DEBUG modem << 01 0x02000 0x04000\x09Secure\x09\x09rwxl\x0D\x0A
2019-07-12T07:44:12.199Z DEBUG modem << 02 0x04000 0x06000\x09Secure\x09\x09rwxl\x0D\x0A
2019-07-12T07:44:12.200Z DEBUG modem << 03 0x06000 0x08000\x09Secure\x09\x09rwxl\x0D\x0A
2019-07-12T07:44:12.201Z DEBUG modem << 04 0x08000 0x0a000\x09Secure\x09\x09rwxl\x0D\x0A
2019-07-12T07:44:12.205Z DEBUG modem << 05 0x0a000 0x0c000\x09Secure\x09\x09rwxl\x0D\x0A
2019-07-12T07:44:12.206Z DEBUG modem << 06 0x0c000 0x0e000\x09Secure\x09\x09rwxl\x0D\x0A
2019-07-12T07:44:12.208Z DEBUG modem << 07 0x0e000 0x10000\x09Secure\x09\x09rwxl\x0D\x0A
2019-07-12T07:44:12.210Z DEBUG modem << 08 0x10000 0x12000\x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.211Z DEBUG modem << 09 0x12000 0x14000\x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.214Z DEBUG modem << 10 0x14000 0x16000\x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.216Z DEBUG modem << 11 0x16000 0x18000\x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.217Z DEBUG modem << 12 0x18000 0x1a000\x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.219Z DEBUG modem << 13 0x1a000 0x1c000\x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.220Z DEBUG modem << 14 0x1c000 0x1e000\x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.241Z DEBUG modem << 15 0x1e000 0x20000\x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.243Z DEBUG modem << 16 0x20000 0x22000\x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.246Z DEBUG modem << 17 0x22000 0x24000\x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.248Z DEBUG modem << 18 0x24000 0x26000\x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.250Z DEBUG modem << 19 0x26000 0x28000\x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.252Z DEBUG modem << 20 0x28000 0x2a000\x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.255Z DEBUG modem << 21 0x2a000 0x2c000\x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.258Z DEBUG modem << 22 0x2c000 0x2e000\x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.261Z DEBUG modem << 23 0x2e000 0x30000\x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.264Z DEBUG modem << 24 0x30000 0x32000\x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.266Z DEBUG modem << 25 0x32000 0x34000\x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.268Z DEBUG modem << 26 0x34000 0x36000\x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.269Z DEBUG modem << 27 0x36000 0x38000\x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.271Z DEBUG modem << 28 0x38000 0x3a000\x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.273Z DEBUG modem << 29 0x3a000 0x3c000\x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.275Z DEBUG modem << 30 0x3c000 0x3e000\x09Non-Secure\x09rwxl\x0D\x0A
2019-07-12T07:44:12.277Z DEBUG modem << 31 0x3e000 0x40000\x09Non-Secure\x09rwxl\x0D\x0A\x0D\x0A
2019-07-12T07:44:12.279Z DEBUG modem << Peripheral\x09\x09Domain\x09\x09Status\x0D\x0A
2019-07-12T07:44:12.280Z DEBUG modem << 00 NRF_P0\x09\x09Non-Secure\x09OK\x0D\x0A
2019-07-12T07:44:12.299Z DEBUG modem << 01 NRF_CLOCK\x09\x09Non-Secure\x09OK\x0D\x0A
2019-07-12T07:44:12.302Z DEBUG modem << 02 NRF_RTC1\x09\x09Non-Secure\x09OK\x0D\x0A
2019-07-12T07:44:12.306Z DEBUG modem << 03 NRF_NVMC\x09\x09Non-Secure\x09OK\x0D\x0A
2019-07-12T07:44:12.308Z DEBUG modem << 04 NRF_UARTE1\x09\x09Non-Secure\x09OK\x0D\x0A
2019-07-12T07:44:12.310Z DEBUG modem << 05 NRF_UARTE2\x09\x09Secure\x09\x09SKIP\x0D\x0A
2019-07-12T07:44:12.312Z DEBUG modem << 06 NRF_IPC\x09\x09Non-Secure\x09OK\x0D\x0A
2019-07-12T07:44:12.314Z DEBUG modem << 07 NRF_VMC\x09\x09Non-Secure\x09OK\x0D\x0A
2019-07-12T07:44:12.315Z DEBUG modem << 08 NRF_FPU\x09\x09Non-Secure\x09OK\x0D\x0A
2019-07-12T07:44:12.316Z DEBUG modem << 09 NRF_EGU1\x09\x09Non-Secure\x09OK\x0D\x0A
2019-07-12T07:44:12.317Z DEBUG modem << 10 NRF_EGU2\x09\x09Non-Secure\x09OK\x0D\x0A
2019-07-12T07:44:12.318Z DEBUG modem << 11 NRF_TWIM2\x09\x09Non-Secure\x09OK\x0D\x0A
2019-07-12T07:44:12.320Z DEBUG modem << 12 NRF_SPIM3\x09\x09Non-Secure\x09OK\x0D\x0A
2019-07-12T07:44:12.321Z DEBUG modem << 13 NRF_TIMER0\x09\x09Non-Secure\x09OK\x0D\x0A
2019-07-12T07:44:12.322Z DEBUG modem << 14 NRF_TIMER1\x09\x09Non-Secure\x09OK\x0D\x0A
2019-07-12T07:44:12.324Z DEBUG modem << 15 NRF_TIMER2\x09\x09Non-Secure\x09OK\x0D\x0A
2019-07-12T07:44:12.325Z DEBUG modem << 16 NRF_SAADC\x09\x09Non-Secure\x09OK\x0D\x0A
2019-07-12T07:44:12.326Z DEBUG modem << 17 NRF_GPIOTE1\x09\x09Non-Secure\x09OK\x0D\x0A\x0D\x0A
2019-07-12T07:44:12.327Z DEBUG modem << SPM: NS image at 0x8000\x0D\x0A
2019-07-12T07:44:12.330Z DEBUG modem << SPM: NS MSP at 0x200236d8\x0D\x0A
2019-07-12T07:44:12.332Z DEBUG modem << SPM: NS reset vector at 0xa2f5\x0D\x0A
2019-07-12T07:44:12.333Z DEBUG modem << SPM: prepare to jump to Non-Secure image.\x0D\x0A
2019-07-12T07:44:13.815Z DEBUG modem << ***** Booting Zephyr OS v1.14.99-ncs1 *****\x0D\x0A
2019-07-12T07:44:36.594Z DEBUG modem << The AT host sample started\x0D\x0A
2019-07-12T07:44:46.038Z INFO Modem port is closed
2019-07-12T07:44:46.048Z INFO Modem port is opened
2019-07-12T07:44:46.055Z DEBUG modem >> AT+CFUN?\x0D\x0A
2019-07-12T07:44:46.086Z DEBUG modem << +CFUN: 1\x0D\x0A
2019-07-12T07:44:46.089Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T07:44:46.129Z DEBUG modem >> AT+CGSN=1\x0D\x0A
2019-07-12T07:44:46.161Z DEBUG modem << +CGSN: "352656100002867"\x0D\x0A
2019-07-12T07:44:46.163Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T07:44:46.168Z DEBUG modem >> AT+CGMI\x0D\x0A
2019-07-12T07:44:46.199Z DEBUG modem << Nordic Semiconductor ASA\x0D\x0A
2019-07-12T07:44:46.202Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T07:44:46.207Z DEBUG modem >> AT+CGMM\x0D\x0A
2019-07-12T07:44:46.233Z DEBUG modem << nRF9160-SICA\x0D\x0A
2019-07-12T07:44:46.237Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T07:44:46.242Z DEBUG modem >> AT+CGMR\x0D\x0A
2019-07-12T07:44:46.264Z DEBUG modem << mfw_nrf9160_1.0.0\x0D\x0A
2019-07-12T07:44:46.266Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T07:44:46.269Z INFO Nordic Semiconductor ASA nRF9160-SICA [mfw_nrf9160_1.0.0] SerNr: 352656100002867
2019-07-12T07:44:46.271Z DEBUG modem >> AT+CEMODE?\x0D\x0A
2019-07-12T07:44:46.299Z DEBUG modem << +CEMODE: 0\x0D\x0A
2019-07-12T07:44:46.304Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T07:44:46.331Z DEBUG modem >> AT%XCBAND=?\x0D\x0A
2019-07-12T07:44:46.356Z DEBUG modem << %XCBAND: (1,2,3,4,5,8,12,13,17,19,20,25,26,28,66)\x0D\x0A
2019-07-12T07:44:46.359Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T07:44:46.387Z DEBUG modem >> AT+CMEE?\x0D\x0A
2019-07-12T07:44:46.417Z DEBUG modem << +CMEE: 0\x0D\x0A
2019-07-12T07:44:46.419Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T07:44:46.422Z DEBUG modem >> AT+CMEE=1\x0D\x0A
2019-07-12T07:44:46.448Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T07:44:46.453Z DEBUG modem >> AT+CNEC?\x0D\x0A
2019-07-12T07:44:46.478Z DEBUG modem << +CNEC: 0\x0D\x0A
2019-07-12T07:44:46.505Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T07:44:46.510Z DEBUG modem >> AT+CNEC=24\x0D\x0A
2019-07-12T07:44:46.529Z DEBUG modem << OK\x0D\x0A
2019-07-12T07:44:46.551Z DEBUG modem >> AT+CGEREP?\x0D\x0A
2019-07-12T07:44:46.575Z DEBUG modem << +CGEREP: 0,0\x0D\x0A
2019-07-12T07:44:46.577Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T07:44:46.598Z DEBUG modem >> AT+CGDCONT?\x0D\x0A
2019-07-12T07:44:46.621Z DEBUG modem << +CGDCONT: 0,"IP","aiut.nbiot","10.12.0.2",0,0\x0D\x0A
2019-07-12T07:44:46.624Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T07:44:46.660Z DEBUG modem >> AT+CGACT?\x0D\x0A
2019-07-12T07:44:46.684Z DEBUG modem << +CGACT: 0,1\x0D
2019-07-12T07:44:46.707Z DEBUG modem << \x0A
2019-07-12T07:44:46.709Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T07:44:46.738Z DEBUG modem >> AT+CGEREP=1\x0D\x0A
2019-07-12T07:44:46.760Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T07:44:46.783Z DEBUG modem >> AT+CIND=1,1,1\x0D\x0A
2019-07-12T07:44:46.804Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T07:44:46.826Z DEBUG modem >> AT+CEREG=2\x0D\x0A
2019-07-12T07:44:46.853Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T07:44:46.876Z DEBUG modem >> AT+CEREG?\x0D\x0A
2019-07-12T07:44:46.905Z DEBUG modem << +CEREG: 2,1,"A9D1","0204556F",9\x0D\x0A
2019-07-12T07:44:46.909Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T07:44:46.937Z DEBUG modem >> AT+COPS=3,2\x0D\x0A
2019-07-12T07:44:46.963Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T07:44:46.987Z DEBUG modem >> AT+COPS?\x0D\x0A
2019-07-12T07:44:47.016Z DEBUG modem << +COPS: 0,2,"26002",9\x0D\x0A
2019-07-12T07:44:47.023Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T07:44:47.058Z DEBUG modem >> AT%XCBAND\x0D\x0A
2019-07-12T07:44:47.084Z DEBUG modem << %XCBAND: 20\x0D
2019-07-12T07:44:47.110Z DEBUG modem << \x0A
2019-07-12T07:44:47.114Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T07:44:47.142Z DEBUG modem >> AT+CGDCONT?\x0D\x0A
2019-07-12T07:44:47.169Z DEBUG modem << +CGDCONT: 0,"IP","aiut.nbiot","10.12.0.2",0,0\x0D\x0A
2019-07-12T07:44:47.172Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T07:44:47.199Z DEBUG modem >> AT+CGACT?\x0D\x0A
2019-07-12T07:44:47.229Z DEBUG modem << +CGACT: 0,1\x0D\x0A
2019-07-12T07:44:47.233Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T07:44:47.243Z DEBUG modem >> AT%CESQ=1\x0D\x0A
2019-07-12T07:44:47.266Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T07:44:47.291Z DEBUG modem >> AT+CESQ\x0D\x0A
2019-07-12T07:44:47.320Z DEBUG modem << +CESQ: 99,99,255,255,255,52\x0D\x0A
2019-07-12T07:44:47.323Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T07:44:47.351Z DEBUG modem >> AT%XSIM=1\x0D\x0A
2019-07-12T07:44:47.375Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T07:44:47.401Z DEBUG modem >> AT%XSIM?\x0D\x0A
2019-07-12T07:44:47.426Z DEBUG modem << %XSIM: 1\x0D\x0A
2019-07-12T07:44:47.451Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T07:44:47.481Z DEBUG modem >> AT+CPIN?\x0D\x0A
2019-07-12T07:44:47.510Z DEBUG modem << +CPIN: READY\x0D\x0A
2019-07-12T07:44:47.513Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T07:44:47.547Z DEBUG modem >> AT+CPINR="SIM PIN"\x0D\x0A
2019-07-12T07:44:47.574Z DEBUG modem << +CPINR: "SIM PIN",3\x0D\x0A
2019-07-12T07:44:47.577Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T07:44:47.603Z DEBUG modem >> AT+CIMI\x0D\x0A
2019-07-12T07:44:47.629Z DEBUG modem << 260021171774100\x0D\x0A
2019-07-12T07:44:47.631Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T07:44:47.633Z INFO IMSIdentity: 260021171774100
2019-07-12T07:44:52.540Z DEBUG modem >> at+cesq\x0D\x0A
2019-07-12T07:44:52.559Z DEBUG modem << +CESQ: 99,99,255,255,255,52\x0D\x0A
2019-07-12T07:44:52.574Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T07:44:53.568Z DEBUG modem << +CEREG: 1,"A9DB","0203B571",9\x0D\x0A\x00
2019-07-12T07:44:53.592Z DEBUG modem >> AT+COPS=3,2\x0D\x0A
2019-07-12T07:44:53.616Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T07:44:53.640Z DEBUG modem >> AT+COPS?\x0D\x0A
2019-07-12T07:44:53.664Z DEBUG modem << +COPS: 0,2,"26002",9\x0D\x0A
2019-07-12T07:44:53.668Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T07:44:53.676Z DEBUG modem >> AT%XCBAND\x0D\x0A
2019-07-12T07:44:53.703Z DEBUG modem << %XCBAND: 20\x0D\x0A
2019-07-12T07:44:53.706Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T07:44:53.737Z DEBUG modem >> AT+CGDCONT?\x0D\x0A
2019-07-12T07:44:53.763Z DEBUG modem << +CGDCONT: 0,"IP","aiut.nbiot","10.12.0.2",0,0\x0D\x0A
2019-07-12T07:44:53.766Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T07:44:53.792Z DEBUG modem >> AT+CGACT?\x0D\x0A
2019-07-12T07:44:53.819Z DEBUG modem << +CGACT: 0,1\x0D\x0A
2019-07-12T07:44:53.821Z DEBUG modem << OK\x0D\x0A\x00

RE: nRF 9160 DK - Asset Tracker (and NTP) not working (nrf_cloud_connect_failed: 22)

Håkon Alseth — Thu, 11 Jul 2019 12:32:52 GMT

60 resolves to ETIMEDOUT. Could you try to use the at_client and LTE Link Monitor, and post the log? Your return err codes leads towards low signal strength, and if you post the log when connecting over at_client, it should hold alot of debug info.

Kind regards,

Håkon

RE: nRF 9160 DK - Asset Tracker (and NTP) not working (nrf_cloud_connect_failed: 22)

pastucha.grzegorz — Thu, 11 Jul 2019 11:24:04 GMT

It doesn't either:

FTP example
connect err: 60

All i've changed is the network mode to NBIoT.

RE: nRF 9160 DK - Asset Tracker (and NTP) not working (nrf_cloud_connect_failed: 22)

Håkon Alseth — Thu, 11 Jul 2019 11:04:14 GMT

You can try this sample, as it hard codes the IP address, and doesn't call getaddrinfo:

https://github.com/Rallare/fw-nrfconnect-nrf/blob/nrf9160_samples/samples/nrf9160/ftp/src/main.c

Does this one work as intended? (it should print out the robots.txt file)

Kind regards,

Håkon

RE: nRF 9160 DK - Asset Tracker (and NTP) not working (nrf_cloud_connect_failed: 22)

pastucha.grzegorz — Thu, 11 Jul 2019 10:27:15 GMT

Hi,

thank you for your response. I'm still trying to make the NTP sample work. At this moment I'm fine with providing an exact IP address . So i've changed the NTP_HOST domain name to IP address (tried many, 129.240.2.6 for example) and figured that it could work without any other changes, as I looked it up in udp_with_psm sample and it's done the same way there (just an IP address as an getaddrinfo function argument). Looks like it works:

client_fd: 2
bind err: 0

sendto ret: 48

and iirc the return value of sendto is supposed to represent octets sent. But there's no response from the NTP server.

I've also tried sending it to our private server but without success (no packets received on server side).

Making the asset_tracker work would be nice but i'm not sure how to make it work without the DNS server and it's not my priority.

RE: nRF 9160 DK - Asset Tracker (and NTP) not working (nrf_cloud_connect_failed: 22)

Håkon Alseth — Wed, 10 Jul 2019 10:55:55 GMT

Hi,

Your problem is the dns resolution, as "getaddrinfo err: 22" indicates that your local carrier does not provide you with a DNS server.

You can try to hardcode the IP address if you want, and in addition, I would recommend that you contact your carrier to let them know about this issue.

Kind regards,

Håkon