NB-IoT - nRF91DK

RE: NB-IoT - nRF91DK

Øyvind — Wed, 23 Nov 2022 10:13:22 GMT

[quote user="dival"]I'll get back to you on the remaining aspects of debugging.[/quote]

Yes, please do.

Where are you located? How is the network coverage in that area? What local network providers are available?

Kind regards,
Øyvind

RE: NB-IoT - nRF91DK

dival — Tue, 22 Nov 2022 19:36:52 GMT

Hello Øyvind, thanks for getting back to me 🙂

When I tried with a Serial LTE monitor (AT client), I didn't observe any network problems, but I couldn't ping. I noticed I used the incorrect AT commands; thank you for pointing this up.

I'll see if I can use modem shell; it offers more testing choices, like pinging. I'm reading the following: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/samples/nrf9160/modem_shell/README.html and I would just want to confirm with you, under "LTE link control", how are the APN set up? With AT commands AT+CGDCONT=1,"IP","<APN>" is this correct? I thought I would attempt to test by pinging by using MoSh command: ping to see if any problems occur, if so then the problem is with the network

I'll get back to you on the remaining aspects of debugging. Finally, I have not yet received a standard SIM card. I bought one and am waiting for it to come. I appreciate the assistance thus far.

Thanks.

RE: NB-IoT - nRF91DK

Øyvind — Tue, 22 Nov 2022 18:29:43 GMT

Hello dival ,

You will need to choose either Asset Tracker v2 or Serial LTE Modem with regards to AT commands. The AT commands you are using, e.g. AT#XCONNECT is part of the SLM-specific AT commands. For the Asset Tracker v2 you will need to use the AT commands from nRF9160 AT Commands Reference commands. AT-CIPPING? is not a supported AT Command in our cellular modem.

A better way of testing your network issues will be to use Serial LTE Modem, at_client, or even Modem Shell.

From the Wireshark modem trace you have attached the following AT command informs me that you are using a test network: %XMONITOR: 1,"Software Radio Systems LTE","srsLTE","99970","0007",9,4,"00000002",99,2399,84,31,"","11100000","11100000","00111110". This also shows that you are connected to your test network using NB-IoT, but from the wireshark log it does not look like you are connected out of the test network.

Have you verified that this network is connected to internet? As this network is yours please provide network logs showing that network traffic is routed correctly from the device to the internet through your test network.

From the modem trace collector, please provide the .bin file in order for us to see what is going on in the modem. The wireshark log (.pcapng) shows that you have bad signal qulity with AT+CESQ.

If you device does not have an internet connection it will not be able to provision to nRF Cloud and you will not be able to add your device.

I will ask for the last time, but please acquire a standard network provided SIM to verify device functionality. It is very difficult for us to debug any test network that we are not familiar with.

Kind regards,
Øyvind

RE: NB-IoT - nRF91DK

dival — Tue, 22 Nov 2022 12:24:24 GMT

I'd also like to highlight that I filed a new ticket (this one) since I wasn't getting the support I needed on a private ticket, and @Charlie S left my primary questions unanswered for a few weeks. He urged me today to message sales, but I clarified that this was a technical matter, not a sales question. That's why I made a public ticket instead, and this will be my last ticket. I hope you understand, and please accept my apologies for any inconvenience.

In the private ticket, he mentioned testing out with another sim card. However, I have mentioned that this is not an option for me to access one now. However, I'll be looking to get one soon, but I would like to try to solve this issue first and then proceed to purchase a data plan and sim card from another local provider. First, I'd like to test out or try to work out the issue I mentioned above before moving on to testing with a local sim card. I think if I reduce the timeout for the cloud perhaps it can work (?). I'll have to look into that

RE: NB-IoT - nRF91DK

dival — Tue, 22 Nov 2022 12:12:03 GMT

1. I tried the following: https://infocenter.nordicsemi.com/pdf/nRF9160_DK_Getting_Started_Guide_v1.1.pdf section "Provisioning the nRF Connect for Cloud certificate" by opening the nRF connect, deselecting automatic requests, removed the sim card, entering AT+CFUN?4 to put the modem to offline state (and checked the state of the modem to ensure that it is off). I have loaded the JSON certificate and ensured that the security tag is set to "16842753" and then updated the certificate. The log message states "certificate updated completed.

2. Then I tried to power cycle the nRF9160DK and then inserted the SIM card to let the automatic requests run. It seems like it tries to connect to the nRF cloud but fails. I am not quite sure why this happens.

3. I also tried to add the LTE device to the nRF connection, but this was not working

The image that I have flashed to the board is nrf9160dk_asset_tracker_v2_nbiot_2022-06-02_880c82db.

RE: NB-IoT - nRF91DK

dival — Tue, 22 Nov 2022 12:05:45 GMT

In the asset tracker V2, it received a "modem evt_lte connected" however, it was not able to connect to the cloud. And, as I mentioned: It attempts to connect to the nrfcloud and then when it is not able to, then it stops working and searches for a new network. Hence I received "Extended Signal Quality +CESQ: 99,99,255,255,255,255.".

To sum up, these are the questions I have.

1) Is the ping command I used in the AT client correct? I got an error message in the log: 2022-11-21T10:36:41.114Z ERROR Error: AT#XPING="www.google.com",45,5000,5,1000
failed: phone failure (I posted it above as well).

2) Is there a way to stop certain DNS queries or just simply connect to the nrfcloud. I see it does a DNS query to NTP.UIO.NO and TIME.GOOGLE.COM

3) Is there a way to adjust the speed, perhaps slow down the queries or something? what I encountered is that when it tries to connect to the nRF cloud, and it doesn't connect then it disconnects. Is there a way to increase the timeout for the connection?

I am currently running ASSET TRACKER V2. and using LTE LINK MONITOR.

Looking forward to your reply.

RE: NB-IoT - nRF91DK

dival — Tue, 22 Nov 2022 09:04:37 GMT

devzone.nordicsemi.com/.../nrf91_5F00_logs-_2800_2_2900_.pcapngHere are the modem trace, when running asset tracker v2. As you can see, it detects to the network, connects to the network, tries to connect to the nRF cloud, and when it is not able to, then it disconnects from the network, and starts searching for a new network.

When I flashed with the AT client, it didnt disconnect from the network, however it was just connected, but when I tried to ping (using the ping commando that I showed from my previous reply) it gave me an error.

Can you kindly provide me with the right AT command to ping google.com I attempted to execute the AT command XPING as described above, but I received an error. If this ping succeeds, there is no issue with the network connection itself. Can we test this first? I believe that may be advantageous for debugging.