Building udp example from command line

RE: Building udp example from command line

Charlie — Mon, 30 Nov 2020 08:20:49 GMT

Great! You are welcome. Feel free to ask if you have other problems.

RE: Building udp example from command line

paul_tanner — Mon, 30 Nov 2020 07:56:22 GMT

Looks a bit better this morning. I loaded the asset tracker binary and got LEDs flashing. Was then able to add the device on the cloud and see it transmitting.

On reflection about why this took so long, it was probably because I begun the exercise with "Getting started with the SDK" and only later discovered "Getting started with the nRF9160". I think the former should begin with a link to the latter.

Anyway, many thanks for your help.

RE: Building udp example from command line

paul_tanner — Fri, 27 Nov 2020 15:17:45 GMT

Thx Charlie,

Once I found the option for checking the SIM card (my window had been too small) I saw that it was not activated, maybe due to some issues with nrfcloud.com 2 days ago. It is now.

%XSYSTEMMODE: 1,0,0,0
OK
AT+CEREG=1
OK
AT+CEREG?
+CEREG: 1,4
OK
AT+CFUN=1
OK
AT+CEREG?
+CEREG: 1,4
OK
+CEREG: 2
+CEREG: 5
AT+CEREG?
+CEREG: 1,5
OK
AT+CEREG?
+CEREG: 1,5
OK

So this looks OK.

Now when I click reset on the device and wait a while I still don't get any LEDs.

(The SIM card pages says "Not connected to any device".)

(and the device is not provisioned.)

RE: Building udp example from command line

Charlie — Fri, 27 Nov 2020 10:25:42 GMT

Hi Paul, Let's spend some time to confirm the cellular network connection first. I assume you have gone through this get start video I mentioned before, so you would understand what I mean in the following steps:

1. login to nrfcloud and make sure that your SIM is registered and appear on the "SIM CARDS" item.

2. Program latest nrf9160dk_fw_2020-10-30_5522ca2b\img_app_bl\nrf9160dk_at_client_2020-10-30_5522ca2b.hex and modem firmware nrf9160dk_fw_2020-10-30_5522ca2b\mfwnrf9160122.zip

2. Connect nRF9160DK to LTE Link monitor, disable "Automatic requests" option on the right down corner.

3. Input the following commands one by one

AT+CFUN=4     // Stop modem in order to do configuration
AT+CFUN?        // check modem state
AT%XSYSTEMMODE=1,0,0,0  // enable LET-M support
AT%XSYSTEMMODE? // check
AT+CEREG=1 // configure register information output 
AT+CEREG?   // check registeration info
AT+CFUN=1
AT+CEREG?  //   check registeration info

4. Check if the output is the same as the below. Keeping using "AT+CEREG?" to check register state, this may take several minutes. Here "+CEREG: 1,5" means the SIM card has registered to the local cellular network. You can read nRF91 AT Commands to learn more detail.

*** Booting Zephyr OS build v2.4.0-ncs1  ***
The AT host sample started
AT+CFUN?
+CFUN: 0
OK
AT+CFUN=4
OK
AT+CFUN?
+CFUN: 4
OK
AT%XSYSTEMMODE=1,0,0,0
OK
AT%XSYSTEMMODE?
%XSYSTEMMODE: 1,0,0,0
OK
AT+CEREG=1
OK
AT+CEREG?
+CEREG: 1,4
OK
AT+CFUN=1
OK
+CEREG: 2
+CEREG: 5
AT+CEREG?
+CEREG: 1,5
OK

Just try these steps and let me the result out "AT+CEREG?".

RE: Building udp example from command line

paul_tanner — Fri, 27 Nov 2020 08:13:21 GMT

Sorry, along the way I had deleted the application on the device.

After reloading the at_client I could switch to offline mode CFUN=4 and add the certificates.

The I reset the device and waited for LEDs.

After many minutes there was no change. Is this a range problem? Is there any way to tell?

BTW. the last thing on the Link Monitor after resetting was

  *** Booting Zephyr OS build v2.4.0-ncs1  ***

  The AT host sample started

Is it in the state where we are waiting for LEDs to come on?

RE: Building udp example from command line

Charlie — Thu, 26 Nov 2020 15:38:57 GMT

Ok, that is strange. I am not sure if this is due to uart connection. Did you see other printouts like this video shown on your screen?

RE: Building udp example from command line

paul_tanner — Thu, 26 Nov 2020 15:08:57 GMT

OK. Skipped that and tried to add device. I get error 40412.

Went to try to upload certificates again.

AT+CFUN=4 does not return anything, neither does AT+CFUN? they apparently timed out.

Also, I'm not sure what the LEDs on 9160DK should be showing. LED5 is power I think. No other LEDS are visible and lit.

RE: Building udp example from command line

Charlie — Thu, 26 Nov 2020 13:39:39 GMT

See red circles in the pictures. Please follow instructions step by step to run this nrfcloud application. infocenter.nordicsemi.com/index.jsp

RE: Building udp example from command line

paul_tanner — Thu, 26 Nov 2020 13:14:09 GMT

3 screenshots. The home screen has shown 1 SIM card but nowhere to check it.

no devices showing.

Click to add a device

Wants me to enter the SIM card again - not asking for device information.

RE: Building udp example from command line

Charlie — Thu, 26 Nov 2020 12:59:47 GMT

Can you send some screenshots regarding the above SIM card issue?

For the connection issue debugging, did you get any result from the nRF9160DK get start guide based on prebuild firmware? I mean see some information from the nrfcloud.com device page.

RE: Building udp example from command line

paul_tanner — Thu, 26 Nov 2020 12:23:14 GMT

Going back into nrfcloud.com I can see that there is one SIM card but can't see details to check it.

It says there are no devices. When I go to register a device it prompts me for the SIM card (which I have already registered).

RE: Building udp example from command line

paul_tanner — Thu, 26 Nov 2020 12:11:31 GMT

OK. I have now registered the iBasis SIM on the nRF Cloud site.

Same output:

*** Booting Zephyr OS build v2.4.0-ncs1 ***
UDP sample has started
LTE cell changed: Cell ID: 128073592, Tracking area: 1328
PSM parameter update: TAU: -1, Active time: -1RRC mode: Connected
RRC mode: Idle
LTE cell changed: Cell ID: 131531896, Tracking area: 1328

So we are still not seeing:

Network registration status: Connected - roaming

Is this still a problem with the SIM or something else?

RE: Building udp example from command line

Charlie — Thu, 26 Nov 2020 11:25:15 GMT

Hi Paul,

Glad to hear your update. I agree that it is confusing, but Kconfig and prj.conf have different formats.

nRF Cloud could be slow in some regions and areas, we are keeping improve its server. You can start from this page to connect nRF9160DK to nRF Cloud and register SIM card. infocenter.nordicsemi.com/index.jsp

RE: Building udp example from command line

paul_tanner — Wed, 25 Nov 2020 13:34:39 GMT

I just got an answer from iBasis about this. The LTE/M coverage map https://www.o2.co.uk/business/iot/lte-m shows that we are in range. However they also say "if you are in the coverage range, please also make sure that you register and activate the card on the Nordic nRF Cloud before it can be used.". I kind of expected this but still didn't know how to do it. I found this https://nrfcloud.com/ and tried to create an account. Suspiciously slow. Is this for real?

RE: Building udp example from command line

paul_tanner — Wed, 25 Nov 2020 13:15:51 GMT

correction: after a long time it did come back with something:

```

The MQTT simple sample startedLTE Link Connecting ...
+CEREG: 2,"0530","07D70478",7,0,0,"11100000","11100000"
+CSCON: 1+CEREG: 2,"0530","07D70478",7,0,19,"11100000","11100000"
+CSCON: 0+CEREG: 0,"0530","07D70478",7,0,19,"11100000","11100000"
+CEREG: 2,"FFFE","FFFFFFFF",9,0,19,"11100000","11100000
"LTE Link Connected!
ERROR: getaddrinfo failed -11

```

My Kconfig:

```

#
# Copyright (c) 2020 Nordic Semiconductor ASA
#
# SPDX-License-Identifier: LicenseRef-BSD-5-Clause-Nordic
#

menu "MQTT simple sample"
config MQTT_PUB_TOPIC
string "MQTT publish topic"
default "my/publish/topic"

config MQTT_SUB_TOPIC
string "MQTT subscribe topic"
default "my/subscribe/topic"

config MQTT_CLIENT_ID
string "MQTT Client ID"
default "devzone_client"

config MQTT_BROKER_HOSTNAME
string "MQTT broker hostname"
default "test.mosqitto.org" #"mqtt.eclipse.org"

config MQTT_BROKER_PORT
int "MQTT broker port"
default 8884 #1883

config MQTT_MESSAGE_BUFFER_SIZE
int "MQTT message buffer size"
default 128

config MQTT_PAYLOAD_BUFFER_SIZE
int "MQTT payload buffer size"
default 128

config MQTT_TLS_SEC_TAG
int "TLS credentials security tag"
default 16842753 #24

config MQTT_TLS_SESSION_CACHING
bool "Enable TLS session caching"

config MQTT_TLS_PEER_VERIFY
int "Set peer verification level"
default 1 #2
help
Set to 0 for VERIFY_NONE, 1 for VERIFY_OPTIONAL, and 2 for
VERIFY_REQUIRED.

endmenu

menu "Zephyr Kernel"
source "Kconfig.zephyr"
endmenu

```

BTW. should "config MQTT_BROKER_HOSTNAME" be written as

"CONFIG_MQTT_BROKER_HOSTNAME"

RE: Building udp example from command line

paul_tanner — Wed, 25 Nov 2020 12:56:56 GMT

Thx Charlie,

I think the iBasis looks like a non-starter as even LTE/M has limited coverage in the UK but they do not give any kind of coverage map. Testing without knowing about coverage is probably a waste of time.

I believe that Vodafone have some NB-IoT coverage in the UK so I think we need one of their SIMs.

RE: Building udp example from command line

Charlie — Wed, 25 Nov 2020 09:09:40 GMT

NCS document has a section about how to select and verify Network Mode. You can add CONFIG_LTE_NETWORK_MODE_NBIOT=y and CONFIG_LTE_NETWORK_MODE_LTE_M=n to prj.conf, or change through menuconfig. IBasis have LTE-M coverage in most countries, but NB-IoT is less supported, you can check this IBasis coverage page, so confirm and check with a local operator seems more promised.

RE: Building udp example from command line

paul_tanner — Tue, 24 Nov 2020 12:55:39 GMT

Maybe I need to register the iBasis SIM that comes with the 9160DK?

And maybe the coverage on iBasis is too limited.

I've ordered Vodafore SIMs.

RE: Building udp example from command line

paul_tanner — Tue, 24 Nov 2020 10:18:06 GMT

Thx Charlie,

Yes, I see several LTE-related parameters in prj.conf

Anyone know where the parameters for NB-IoT are documented?

Also, whereas I get:

```

LTE call changed: Cell ID: etc

RRC mode: Connected

```

I never get:

```
Network registration status: Connected - roaming

```

Despite going to a place where I believe there is some coverage (albeit NB-IoT)

RE: Building udp example from command line

Charlie — Tue, 24 Nov 2020 09:04:53 GMT

It is configured for LTE-M as default.

RE: Building udp example from command line

paul_tanner — Mon, 23 Nov 2020 15:25:37 GMT

Thx Charlie,

Looks a lot more promising now.

```

UDP sample has started

LTE cell changed: Cell ID: 131531896, Tracking area: 1328

PSM parameter update: TAU: -1, Active time: -1

RRC mode: Connected

RRC mode: Idle

```

I am probably not in range here. Will try again somewhere else.

By default, is this example configured for LTE/M or NB-IoT?

RE: Building udp example from command line

Charlie — Mon, 23 Nov 2020 12:17:13 GMT

Hi Paul,

You should use the following command to build a non-secure application like this UDP sample.

ncs\v1.4.0\nrf\samples\nrf9160\udp> west build -b nrf9160dk_nrf9160ns -p

prj.conf is used by default in the building process. Try to set CONFIG_SERIAL=y in prj.conf. This will enable the printout information in the program. You should see something like below if you connect a serial monitor.

*** Booting Zephyr OS build v2.4.0-ncs1  ***
UDP sample has started
LTE cell changed: Cell ID: 17019393, Tracking area: 31201
PSM parameter update: TAU: -1, Active time: -1
RRC mode: Connected
Network registration status: Connected - roaming

PSM parameter update: TAU: 3600, Active time: 0
Transmitting UDP/IP payload of 38 bytes to the IP address 8.8.8.8, port number 2469
RRC mode: Idle

RE: Building udp example from command line

paul_tanner — Mon, 23 Nov 2020 09:16:47 GMT

The README says

```

Configuration files
===================

The sample provides predefined configuration files for the following development kits:

* ``prj.conf`` : For nRF9160 DK and Thingy:91
* ``prj_qemu_x86``: For x86 Emulation (QEMU)

They are located in ``samples/nrf9160/udp`` folder.

Building and running
********************

.. |sample path| replace:: :file:`samples/nrf9160/udp`

.. include:: /includes/build_and_run.txt

.. include:: /includes/spm.txt

```

I don't understand what this is telling me. Do I need to remove one of the .conf files or add in some includes?