RRC mode / Are there debugging options to find out why RRC mode changed to connected

RE: RRC mode / Are there debugging options to find out why RRC mode changed to connected

Charlie — Thu, 05 May 2022 13:09:36 GMT

For PDP functions in NCS1.9.1, you can refer to

PDN — nRF Connect SDK 1.9.1 documentation (nordicsemi.com)

nRF9160: PDN — nRF Connect SDK 1.9.1 documentation (nordicsemi.com)

Best regards,

Charlie

RE: RRC mode / Are there debugging options to find out why RRC mode changed to connected

Hidastelija — Thu, 05 May 2022 12:31:23 GMT

Hi Charlie,

I don't have a response from DNA yet and may not get anything from them for some time due to a ICT labor strike in Finland.

While studying the sim card properties I noticed I'm using default APN iot.dna.fi. Other option would be nat.iot.dna.fi which doesn't have public ports open. Is it possible to select the APN using LTE modem library?

The intro chapter here says that it should be possible:
developer.nordicsemi.com/.../lte_lc.html

But lte_lc_pdp_context_set-function as mentioned here is not available anymore in NCS1.9.1.
developer.nordicsemi.com/.../lte_lc.html

Br,
Ilkka

RE: RRC mode / Are there debugging options to find out why RRC mode changed to connected

Hidastelija — Wed, 04 May 2022 09:07:30 GMT

Thank you for the reply. I will share the information with DNA. Maybe they can change the visibility of the IP address.

Br,

Ilkka

RE: RRC mode / Are there debugging options to find out why RRC mode changed to connected

Charlie — Wed, 04 May 2022 08:17:38 GMT

Hi Ilkka,

I have an internal discussion with our modem developer.

After analyzing the recording you shared, we found there is Paging always in the log before PSM can be entered. Probably the reason is that the IP address in DNA SIM is public and there is a lot of polling coming in. The Network pages the modem and it just responds.

The possible solution from the device side which I know is to set up IPv6 to avoid these Pagings from NW. As the source of the issue is from the network side, I suggest you contact DNA to get more information. Just turn back to us if you need any assistance.

Best regards,

Charlie

RE: RRC mode / Are there debugging options to find out why RRC mode changed to connected

Charlie — Fri, 29 Apr 2022 13:43:31 GMT

Hi IIkka,

Thanks for the detailed explanation. I think I have collected enough information, I will let you know if there are any further findings.

Best regards,

Charlie

RE: RRC mode / Are there debugging options to find out why RRC mode changed to connected

Hidastelija — Fri, 29 Apr 2022 13:35:38 GMT

Hi Charlie,

Thank you for the reply. Are you referring to the ticket https://devzone.nordicsemi.com/f/nordic-q-a/80120/asset-tracker-v2-power-consumption-with-thingy-91 or would you like me to build Asset_tracker_v2 (NCS 1.9.1) with modem traces to test this issue?

My tests at the moment are with a more purpose built FW. I have Event Manager based implementation like the Asset Tracker v2, but the FW only implements AWS shadow communication. With the test FW I can change PSM/eDRX parameters and the FW reports network response back to shadow. In addition I can turn on/off uart logs using shadow. I have done the implementation to test different configurations while the HW is connected to Power Profiler Kit II in source mode.

The test FW is built using NCS 1.9.0 and I'm using MFW 1.3.1. I have nRF9160DK with B1 version of nRF9160 SIP and Thingy:91 v1.4.0 and Circuitdojo nRF9160 Feather V4. These two both have nRF9160 SIP B0 version.

I don't see any functional difference between the devices in this test. All three devices have the same issue, in Telia network RRC idle is ok, but in DNA network RRC constantly changes to connected.

I am not using Asset_tracker_v2 from NCS 1.6.0 for testing anymore. I have implemented a FW that expands the asset_tracker_v2 functionality and uses also the nRF52 chip on Thingy:91. This FW is built using NCS 1.7.1. With this asset_tracker_v2 modification I can see similar issue with DNA network as I see with the simple test FW.

Br,

Ilkka

RE: RRC mode / Are there debugging options to find out why RRC mode changed to connected

Charlie — Fri, 29 Apr 2022 12:37:32 GMT

Hi IIKKA,

I am waiting for the reply from some LTE RRC protocol expert, in the mean time, I want to confirm something that may related, are you still testing with the following configuration?

- Thingy:91 (1.4.0 & MFW 1.3.0)
- Asset_tracker_v2 (low_power_conf + GPS disabled) under NCS1.6.0

Are you able to verify with MFW1.3.1+NCS1.9.1? Just share another recording with DNA network if it sitll have same issue.

Best regards,

Charlie

RE: RRC mode / Are there debugging options to find out why RRC mode changed to connected

Hidastelija — Thu, 28 Apr 2022 11:25:25 GMT

Ok, the logs look better when using nRF9160DK. Now I can convert the logs and open in Wireshark. I've attached again logs from DNA and Telia networks.

Application functionality in the logs:

- log begin

- Reset (using button on DK)

- AWS IoT Connection

- 4min idle

- at 4min data/shadow update to AWS

devzone.nordicsemi.com/.../DNA_5F00_modem_5F00_trace_5F00_nRF91DK.bin devzone.nordicsemi.com/.../Telia_5F00_modem_5F00_trace_5F00_nRF91DK.bin

Br,

Ilkka

RE: RRC mode / Are there debugging options to find out why RRC mode changed to connected

Charlie — Thu, 28 Apr 2022 10:35:32 GMT

Hi IIKKA,

I also failed to convert these two recordings. The reason is that Circuitdojo nRF9160 Feather HW may not support the current tracing configuration since it is not a Nordic Devkits. I am looking forward to seeing your recordings with nRF9160DK.

Best regards,

Charlie

RE: RRC mode / Are there debugging options to find out why RRC mode changed to connected

Hidastelija — Thu, 28 Apr 2022 08:44:58 GMT

Hi Charlie,

This is the first time I've used modem traces, I hope the attached files are ok. Attached is traces from two networks. The traces should have AWS connection at boot, then 4min idle and at 4min a data update.

I am using Circuitdojo nRF9160 Feather HW in my measurements. Using Trace Collector V2 I wasn't able to trace using a board that is not Nordic DK. I took the traces using Trace Collector v1.1.2 and then tried to convert to Wireshark using Trace Collector V2. I couldn't verify the logs as "Convert RAW trace to PCAP" displays this error:

11:39:15.459

Failed conversion to pcap: end of file reached while searching db uid plugin path: C:\Users\ilkka\.nrfconnect-apps\node_modules\pc-nrfconnect-tracecollector-preview\node_modules\@nordicsemiconductor\nrf-monitor-lib-js\Release\win32-ia32\nrfml-insight-source.nrfmldevzone.nordicsemi.com/.../Telia_5F00_modem_5F00_trace.bin

devzone.nordicsemi.com/.../DNA_5F00_modem_5F00_trace.bin

If the logs are not good, I can try to trace again using nRF9160DK.

Br,

Ilkka

RE: RRC mode / Are there debugging options to find out why RRC mode changed to connected

Charlie — Wed, 27 Apr 2022 14:12:20 GMT

Hi IIKKA,

Modem trace can help to analyze such kind of communication between device and cell station.

Can you record modem traces with the DNA network and another normal network for your application?

Best regards,

Charlie

RE: RRC mode / Are there debugging options to find out why RRC mode changed to connected

Hidastelija — Wed, 27 Apr 2022 05:58:51 GMT

devzone.nordicsemi.com/.../dna_5F00_psm.txt

Minicom log file with .cap extension didn't upload. Chaged the extension to .txt and trying again.