Getting issue in nRF9160 Application

RE: Getting issue in nRF9160 Application

Martin Lesund — Mon, 06 May 2019 10:17:38 GMT

Hi Mattylce,

The changes in my custom asset_tracker sample is the ones stated in my first post:

CONFIG_NRF_CLOUD_STATIC_IPV4_ADDR=<ip_address>

CONFIG_LTE_LEGACY_PCO_MODE=y

CONFIG_NRF_CLOUD_STATIC_IPV4=y

But when you say "out-of-the box" experience shows that if you have any issues with that, please first try to update the modem firmware.

Please find the newest version here: https://www.nordicsemi.com/Products/Low-power-cellular-IoT/nRF9160/Download#infotabs

IMPORTANT NOTE:

There is a bug in the modem firmware version -> "mfw_nrf9160_0.7.0-15.alpha" which makes it start in "nb-iot mode" as default.
To change to the "LTE-M" mode you need to send an AT-Command.
- AT%XSYSTEMMODE=1,0,0,0 and then AT+CFUN=0 to save the changes into the modem flash.

When you restart your device it will now go into the LTE-M mode.

Best Regards,
Martin L.

RE: Getting issue in nRF9160 Application

MattyIce — Wed, 01 May 2019 20:18:01 GMT

Out of the box, my nrf9160 never blinked LED 3 and LED 4 at the same time. I programmed Martin's `asset_tracker.hex` and was able to successfully register my nrf9160 with nrf cloud.

Martin, what was the change to the asset_tracker code? Where can I find this example project?

RE: Getting issue in nRF9160 Application

Martin Lesund — Mon, 25 Mar 2019 08:59:47 GMT

Hi,

What network are you trying to connect to?
Which modem firmware are you running?

From your at_client sample log I can see that you get a connection with the base station.

I would like you to please try this (custom) asset_tracker sample:

devzone.nordicsemi.com/.../asset_5F00_tracker.hex

If this one works, we could have a better understanding whats the issue.

Use the command line with nrfjprog to flash this sample, with this command:

nrfjprog --program asset_tracker.hex -f nrf91 --sectorerase -r --verify

RE: Getting issue in nRF9160 Application

nRF9160 — Mon, 25 Mar 2019 08:52:29 GMT

In my custom firmware, i tried to get Google IP by calling "getaddrinfo" API with "www.google.com", but i am getting same error as error 22:No more processes

RE: Getting issue in nRF9160 Application

nRF9160 — Mon, 25 Mar 2019 04:53:48 GMT

I run AT_Client sample and taken logs written below, please check.

AT+CEREG?

+CEREG: 2,5,"CB32","031A8B03",7

OK

AT+COPS=3,2

OK

AT+COPS?

+COPS: 0,2,"311480",7

OK

AT%XCBAND

%XCBAND: 13

OK

AT+CGDCONT?

+CGDCONT: 0,"IP","ibasis.iot","10.160.171.23",0,0

OK

AT+CGACT?

+CGACT: 0,1

OK

AT%CESQ=1

OK

AT+CESQ

+CESQ: 99,99,255,255,255,48

OK

AT%XSIM=1

OK

AT%XSIM?

%XSIM: 1

OK

AT+CPIN?

+CPIN: READY

OK

AT+CPINR="SIM PIN"

+CPINR: "SIM PIN",3

OK

AT+CIMI

204080813514770

RE: Getting issue in nRF9160 Application

Martin Lesund — Wed, 20 Mar 2019 08:07:29 GMT

Hi,

Please try to run the AT_Client sample and run the LTE Link Monitor to gather the information from the modem side, and post the results.

What network are you trying to connect to?

I have seen that some few providers do not properly setup DNS autoconfiguration on their side, which can cause similar issues as you see.

To confirm this you could add this to prj.conf file for asset_tracker:

CONFIG_NRF_CLOUD_STATIC_IPV4_ADDR=<ip_address>

CONFIG_LTE_LEGACY_PCO_MODE=y

CONFIG_NRF_CLOUD_STATIC_IPV4=y

You can find the ip address to nrf cloud here:

https://whatismyipaddress.com/hostname-ip

with the nrf cloud host: a2n7tk1kp18wix-ats.iot.us-east-1.amazonaws.com

Then you can add one of the ip-addresses in the prj.conf file.

Note that these IPs can change, so you may need to update this if you want to prototype with nrf cloud.

Build/flash/run

(note that this needs to be the asset_tracker from master branch)