nRF9160 HTTP clien slow response

RE: nRF9160 HTTP clien slow response

user2115 — 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

user116806 — 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

user2115 — 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

user116806 — 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

user116806 — 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

user2115 — 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

user116806 — 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

user2115 — 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