nRF9160 HTTP clien slow response

RE: nRF9160 HTTP clien slow response

Håkon Alseth — Fri, 01 Jul 2022 13:11:25 GMT

If you do not properly close() former sockets, this can happen. Is your code updated compared to the initial code you posted? if yes, can you share the updated project?

Have you implemented the event handler for the lte_lc library, which can give you notifications on what is happening on the network side?

Kind regards,

Håkon

RE: nRF9160 HTTP clien slow response

nicekey — Fri, 01 Jul 2022 02:04:01 GMT

CONFIG_LTE_AUTO_INIT_AND_CONNECT is set to 'n' in my project.

When "Failed to open socket" appears, I make socket link every 20 seconds, but can't recover from "Failed to open socket", what should I do?

When CONFIG_LTE_AUTO_INIT_AND_CONNECT is set to 'y', when "Failed to open socket" appears, it will always stop at "Failed to open socket" and cannot be recovered.

RE: nRF9160 HTTP clien slow response

Håkon Alseth — Thu, 30 Jun 2022 12:12:58 GMT

Hi,

[quote user="nicekey"]

As in the above code, when the modem is turned on, epd_init() is executed,

Will other tasks interrupt the execution of epd_init()?

[/quote]

You need to evaluate your own firmware and how it runs in general.

Any interrupt that occurs in your application can potentially interrupt that function. However, it seems that very little else is running in your main function at the time of calling that function.

[quote user="nicekey"]

When the modem function is turned on, it takes a long time to boot to the application, it takes four minutes, is this normal?

[/quote]

It can be if you're waiting for the LTE Link to connect, ie. if CONFIG_LTE_AUTO_INIT_AND_CONNECT is set to 'y'.

[quote user="nicekey"]If Failed to open socket occurs, I find that calling lte_lc_init_and_connect() has no effect. Do I need to power off and restart the modem at this time?[/quote]

Calling that function again will not help. You're already enabled and have previously been connected, and the modem is highly likely trying to reconnect to the network. However:

Without any debug information about the link status at this time, it is hard to say what happens.

Please see my former responses on how to get detailed information about your link, ie. via CEREG or possibly the lte_lc handler.

Kind regards,

Håkon

RE: nRF9160 HTTP clien slow response

nicekey — Thu, 30 Jun 2022 08:47:39 GMT

void main(void)
{
int err;
int fd;
char *p;
int bytes;
size_t off;
struct addrinfo *res;
struct addrinfo hints = {
.ai_family = AF_INET,
.ai_socktype = SOCK_STREAM,
};
struct timeval timeout;//666
int data_len;
int link_status = 0;
int recv_data_len = 0;
int result;
//int result_bit;
uint32_t connect_attempt = 0;
cJSON *root = NULL, *object = NULL, *item = NULL;

printk("http link onenet sample started\n\r");

epd_spi_init();
//k_sched_lock();
epd_init();

As in the above code, when the modem is turned on, epd_init() is executed,

Will other tasks interrupt the execution of epd_init()?

If so, how to protect it. In my project, there are no other threads.

When the modem function is turned on, it takes a long time to boot to the application, it takes four minutes, is this normal?

If Failed to open socket occurs, I find that calling lte_lc_init_and_connect() has no effect. Do I need to power off and restart the modem at this time?

RE: nRF9160 HTTP clien slow response

Håkon Alseth — Thu, 30 Jun 2022 08:18:12 GMT

[quote user="nicekey"]will the operation of the modem affect my initialization of the screen? For example to interrupt?[/quote]

That depends on your local settings. But, yes; there's communication between the modem and the application, so you can get interrupts when things happen on the LTE Network side of things (for instance, receive a packet etc) that needs to be handled.

Kind regards,

Håkon

RE: nRF9160 HTTP clien slow response

nicekey — Thu, 30 Jun 2022 00:24:41 GMT

thanks.

I use an OLED screen with SPI interface, will the operation of the modem affect my initialization of the screen? For example to interrupt?

RE: nRF9160 HTTP clien slow response

Håkon Alseth — Wed, 29 Jun 2022 09:22:09 GMT

Hi,

[quote user="nicekey"]1. I encountered the 9160 frequently reporting "Failed to open socket" when reconnecting to the network, what should I do?[/quote]

You should wait until the network connection (and your PDN connection) is established.

[quote user="nicekey"]2. The screen is used in my project, and the "blinky" routine can light up the screen 100%. But the same screen code, I tap the screen in the "https_client" routine, and occasionally the phenomenon cannot be turned on. Will my screen initialization part be interrupted by the modem? How do I deal with it?[/quote]

I assume screen here is your uart console?

When you enable modem trace, by setting prj.conf::CONFIG_NRF_MODEM_LIB_TRACE_ENABLED=y, the firmware will push data on uart1.

This is a different UART than the log output (uart console):

https://github.com/nrfconnect/sdk-zephyr/blob/v2.7.99-ncs1/boards/arm/nrf9160dk_nrf9160/nrf9160dk_nrf9160_common.dts#L178-L179

If you use the lte_lc library, you will get events (derived from AT+CEREG notifications) when network goes down and comes up again:

https://github.com/nrfconnect/sdk-nrf/blob/v2.0.0/samples/nrf9160/aws_iot/src/main.c#L350-L352

You can implement logic in the handler there to ensure that the status is checked.

Kind regards,

Håkon

RE: nRF9160 HTTP clien slow response

nicekey — Wed, 29 Jun 2022 08:38:48 GMT

Hi，I have two questions:

1. I encountered the 9160 frequently reporting "Failed to open socket" when reconnecting to the network, what should I do?

2. The screen is used in my project, and the "blinky" routine can light up the screen 100%. But the same screen code, I tap the screen in the "https_client" routine, and occasionally the phenomenon cannot be turned on. Will my screen initialization part be interrupted by the modem? How do I deal with it?

RE: nRF9160 HTTP clien slow response

Håkon Alseth — Fri, 24 Jun 2022 08:19:01 GMT

Hi,

Could you share which mfw version you are using?

Could you take a modem trace and share this?

Kind regards,

Håkon

RE: nRF9160 HTTP clien slow response

nicekey — Fri, 24 Jun 2022 05:38:37 GMT

I have encountered a problem, one of the 9160s cannot be connected to the Internet

The log information is as follows：

[13:35:33.097]收←◆[00:00:00.670,257] [0m<inf> mqtt_simple: The MQTT simple sample started[0m
[00:00:00.670,288] [0m<inf> mqtt_simple: Disabling PSM and eDRX[0m
[00:00:00.670,959] [0m<inf> mqtt_simple: LTE Link Connecting...[0m
[00:00:00.671,356] [1;31m<err> lte_lc: Failed to get system mode, error: -77[0m
[00:00:00.671,356] [1;31m<err> lte_lc: Could not get current system mode, error: -14[0m
[00:00:00.671,356] [0m<inf> mqtt_simple: Failed to establish LTE connection: -14[0m
[00:00:00.671,386] [0m<inf> mqtt_simple: Retrying in 120 seconds[0m

RE: nRF9160 HTTP clien slow response

nicekey — Fri, 24 Jun 2022 03:13:19 GMT

Thank you for your reply. I have encountered a problem, one of the 9160s cannot be connected to the Internet, and the log information contains "Disabling PSM and eDRX". What are the reasons for this result? I have tried updating the modem firmware.

RE: nRF9160 HTTP clien slow response

Håkon Alseth — Wed, 15 Jun 2022 11:33:00 GMT

Hi,

That return is ETIMEDOUT - you'll need to close the socket and reconnect.

Kind regards,

Håkon

RE: nRF9160 HTTP clien slow response

nicekey — Wed, 15 Jun 2022 08:24:06 GMT

Hello, when using the recv() function to read data, errno 116 is often returned, how to deal with it. Continue reading after waiting? Or reconnect?

RE: nRF9160 HTTP clien slow response

Håkon Alseth — Thu, 09 Jun 2022 11:36:08 GMT

As I have already mentioned, this can potentially take time, depending on your signal strength, the amount of towers in your area, the amount of bands that you're searching etc.

What mfw version are you using?

Could you run the at_client firmware on your end, in the LTE Link Monitor application, and issue these AT commands?

AT%XSYSTEMMODE=your-settings

AT+CEREG=5

AT+CFUN=1

AT+CFUN?

Wait until the CEREG has returned that you're connected, which should be printed like this:

+CEREG: 1,"76C1","014ACE00",7,,,"00001010","11000001"

And then attach the log file, which is opened here:

Kind regards,

Håkon

RE: nRF9160 HTTP clien slow response

nicekey — Thu, 09 Jun 2022 08:59:51 GMT

You can also use the v1.9.1\nrf\samples\nrf9160\https_client routine to request data and verify the response time.

The hardware development board I am using is PCA10090 0.9.0.

Transfer rate is important for my project. thanks

RE: nRF9160 HTTP clien slow response

nicekey — Thu, 09 Jun 2022 08:45:31 GMT

How to check the running information of the modem.

In the same environment, the same process, cloud platform. Using other NB modules the link is fine and the data rate is fine.

From the log information of 9160, it takes 70S from sending GET to receiving data packets, which is not normal.

It has been analyzed from these aspects: network settings, sleep mechanism, sim card, signal, power supply, etc.

RE: nRF9160 HTTP clien slow response

Håkon Alseth — Thu, 09 Jun 2022 08:13:54 GMT

[quote user="nicekey"]OK, thanks. Regarding the problem of returning errno 128, the cloud platform did not actively disconnect. Why does it return errno 128 when sending the second packet, and why does the modem disconnect?[/quote]

Where exactly is it failing, and what are the LTE conditions at this time? Have you checked XMONITOR output before and after the specific function call?

[quote user="nicekey"]I use NB1, but the rate of 2 minutes per packet is unacceptable compared to GPRS.[/quote]

Have you identified what call that takes time? As mentioned, you are also connecting to the LTE network within this function, which can take longer time based on your current conditions (signal strength, amount of cell towers in the area, etc)

Kind regards,

Håkon

RE: nRF9160 HTTP clien slow response

nicekey — Thu, 09 Jun 2022 02:01:01 GMT

OK, thanks. Regarding the problem of returning errno 128, the cloud platform did not actively disconnect. Why does it return errno 128 when sending the second packet, and why does the modem disconnect? Reconnecting to the cloud platform every time is time consuming.
I use NB1, but the rate of 2 minutes per packet is unacceptable compared to GPRS.

RE: nRF9160 HTTP clien slow response

Håkon Alseth — Wed, 08 Jun 2022 10:34:15 GMT

Hi,

It seems that you have two issues, one errno returned, and the second that the process (when successful) takes up to 2 minutes.

[quote user=""]The errno returns as 128, which can confirm that the cloud platform is not disconnected. [/quote]

That errno indicates that your LTE connection is lost, and sockets are also lost:

https://github.com/eblot/newlib/blob/master/newlib/libc/include/sys/errno.h#L161

What is the LTE connection status at this point? Are you using LTE-M or NB1?

[quote user=""]In addition, the time from sending the request to getting the response is nearly 2 minutes, which is too long to receive. How can I improve the problem I'm encountering now, thank you[/quote]

In your function, you also connect to the LTE network before opening a stream socket. That can take time, depending on the coverage near your area and the signal strength of the connected LTE cell tower.

If you are using NB1, this is a much slower transport compared to LTE-M, which again adds time to the overall process.

Kind regards,

Håkon