https Connect() timeout, 116

RE: https Connect() timeout, 116

egood — Sat, 27 Jan 2024 13:45:14 GMT

We never really solve this issue, but have sense moved onto using an MQTT based system. Due to the different protocol we no longer are having the issue.

RE: https Connect() timeout, 116

Michal — Tue, 05 Dec 2023 10:21:05 GMT

I have some input from the experts.

It looks like there aren't any issues on the modem FW side, but it may be more about the modem library used in application.

Could you please turn on the logging in the modem library as shown in the documentation and upload the log (as in the serial log, not modem trace, although you can upload both if you'd like).

And just to clarify: you are using offloaded sockets, is that correct? In that case NET_SOCKETS_CONNECT_TIMEOUT will not do anything, as it is a config for the Zephyr sockets and not the ones used by the Modem FW.

Best regards,

Michal

RE: https Connect() timeout, 116

Michal — Mon, 04 Dec 2023 18:09:11 GMT

Hello,

I am very sorry that it is taking time.

Me and my colleague have looked into the modem traces, but we couldn't find anything specific related to those issues.

I have now asked the modem team experts for their input as well.

As before, please let me know if you have any more information in the meantime.

Best regards,

Michal

RE: https Connect() timeout, 116

Michal — Fri, 24 Nov 2023 15:56:03 GMT

Did not progress much yet, but I am currently discussing it with my colleagues. If there is any more information from your side as well please let me know.

Best regards,

Michal

RE: https Connect() timeout, 116

egood — Wed, 15 Nov 2023 18:38:05 GMT

Thanks for the update.

RE: https Connect() timeout, 116

Michal — Wed, 15 Nov 2023 16:29:46 GMT

Hello again,

Sorry for the delays, I have been looking into it, but did not progress much with my findings. I will ask our experts if they could provide some insight as well.

Best regards,

Michal

RE: https Connect() timeout, 116

Michal — Fri, 10 Nov 2023 15:19:35 GMT

Ah, I am sorry, I thought they were some earlier test traces.

I will look more into them after the weekend.

Best regards,

Michal

RE: https Connect() timeout, 116

egood — Thu, 09 Nov 2023 21:22:41 GMT

Michal,

I have already sent over traces with the problem captured please read my above posts and see trace_2_cont.bin and trace_4.bin

RE: https Connect() timeout, 116

Michal — Thu, 09 Nov 2023 15:38:31 GMT

Hello Eric,

I took over the case from Susheel.

I can also confirm that I can display the traces as well.

Please let us know when you will have a capture of the issue.

Best regards,

Michal

RE: https Connect() timeout, 116

egood — Mon, 06 Nov 2023 15:38:18 GMT

I managed to capture one additional example. This time it happened ~82Sec after reset and logging start I stopped the trace shortly after. This one has much less data to parse through.

devzone.nordicsemi.com/.../trace_5F00_4.bin

RE: https Connect() timeout, 116

egood — Mon, 06 Nov 2023 15:22:29 GMT

Ok I managed to capture a trace with the connect() timeout occurring twice.

The first time at: 00:16:10.411

The second time at 00:34:04.603

The second one was strange in that it timed out after only 190mS? Where the first event timeout was right at the 10Sec mark which matches the socket connect timeout kconfig. This trace picks up at 841Secs just prior to these events. I had to restart the trace capture in segger RTT viewer as the command line capture tool, just stopped logging data at around that time.

I will work on getting another cleaner capture that logs from the start, but wanted to send this over to get things started.

devzone.nordicsemi.com/.../trace_5F00_2_5F00_cont.bin

RE: https Connect() timeout, 116

Susheel Nuguru — Mon, 06 Nov 2023 13:00:29 GMT

That sounds like a plan, Eric.

RE: https Connect() timeout, 116

egood — Mon, 06 Nov 2023 12:43:35 GMT

After playing around a bit more it seem that I can open these trace files via "Load Trace file.." button in Cellular Monitor v2.0.1 and they seem to be displaying trace data.

I will attempt to capture a trace while the error is happening and report back once I have capture an instance of the issue.

RE: https Connect() timeout, 116

egood — Mon, 06 Nov 2023 12:31:51 GMT

I took another stab at getting the trace collection working. I used the following https://devzone.nordicsemi.com/f/nordic-q-a/104983/how-to-capture-nrf9160-modem-traces-using-rtt As mentioned we only have one UART on our custom board and it's dedicated to the LOG console so I used RTT instead.

Everything seems to work correctly, however I can't open the .bin tracefile via the Cellular Monitor v2.0.1

I have attached two trace files that I collected. Can you verify they are correct and/or advise if these traces have been collected correctly? I want to make sure they I'm collecting them correctly before I invest the time to capture the using trace which as mentioned can be elusive. devzone.nordicsemi.com/.../modemtraces_5F00_test1.bin devzone.nordicsemi.com/.../modemtrace_5F00_test2.bin

Thanks!

RE: https Connect() timeout, 116

Susheel Nuguru — Mon, 06 Nov 2023 11:02:17 GMT

Thanks for the detail description of the issue. We need a modem trace to analyze what the problem is. Can you please enable and attach that here?