Hi
In the mqtt_simple example there is a line "modem_configure();" which establishes the LTE Link connection. If connecting the LTE link is not possible (for example no signal), this function never returns.
1. Is this the intention of this function or is there a possibility to configure a timeout?
2. Is it normal, that this function needs several minutes to establish the LTE link, if a provider is present?
regards
ExAg
1. Is this the intention of this function or is there a possibility to configure a timeout?
The reason it is blocking is due to some semaphores inside w_lte_lc_init_and_connect(..) in lte_lc.c. It will wait for the at_handler() to run and if the response is appropriate it will give up the semaphore and the program continues. See code below
//From w_lte_lc_init_and_connect() in lte_lc.c
k_sem_init(&link, 0, 1);
//k_sem_init(&link, 1, 2);
at_cmd_set_notification_handler(at_handler);
if (at_cmd_write(normal, NULL, 0, NULL) != 0) {
return -EIO;
}
k_sem_take(&link, K_FOREVER);
You can set a timeout, by running k_sem_take(&link, timeout_in_ms); where you specify the timeout in timeout_in_ms.
Be aware that this may cause some unwanted results/race conditions etc., but I am not sure specifically what may happen.
2. Is it normal, that this function needs several minutes to establish the LTE link, if a provider is present?
I will look into this and come back to you.
Best regards,
Simon
2. Is it normal, that this function needs several minutes to establish the LTE link, if a provider is present?
The time to establish an LTE link varies depending on the signal strength and the network, it may more than 5 minutes at worst. If the network settings are stored on the modem, the connection only takes some few seconds. The network settings are automatically stored to the modem when the modem is turned off, through the call to AT+CFUN=0.
Best regards,
Simon
Hi Simon
I have attached the modem trace-2019-10-21T12-15-37.075Z.bintrace file. It took several minutes to establish the LTE connection for this trace file.
Best regards
Michael
Thank you. I have informed the ones responsible about the modem trace, and I will keep you updated when I get answers.
Best regards,
Simon
I got a reply. The reason for the long connection time is because the network rejects the Attach Procedure, due to cause #26 - insufficient resources (See 3GPP TS 24.301 Annex B, B.1). A timer with a timeout of 12 minutes is then started, and a new attempt to attach is done when the timer expires.
You should check with the operator if there is any plans to add more resources.
Best regards,
Simon
Hi Simon
Thank you for this analysis. So it's our national provider who has not enough capacity. But this changes from minute to minute...
The only thing strange are theese 12 minutes you mentioned, because the duration until the connection can be everything between some seconds, some minutes to over 10 minutes. It's not always fix 12 minutes.
Best regards and thank you again
Michael
Sorry for the delay, I will ask internally tomorrow about this when I'm in office.
Best regards,
Simon
Sorry for the delay, I will ask internally tomorrow about this when I'm in office.
Best regards,
Simon
I got the following reply:
"Without log from different delays not possible to say what is the reason in that case but sounds like failures are not always because of ESM cause #26.
If same SIM is always used then there is no difference in "NAS Signalling Low Priority", that is one factor defining UE behavior. If UE is configured for "NAS Signalling Low Priority" next attempt for ESM cause #26 will be done after 10 seconds.
Network can include backoff timer value in reject and in that case delay given by network is used.
With different EMM and ESM reject causes UE might be allowed to retry after 10 seconds."
Hi Simon
Thank you for your reply. What exactly does this mean for us? I do not really understand, i am not an expert on LTE network connections. Are we doing something wrong?
The only thing I can say is that we are always using the same SIM for all our tests.
regards Michael
Nothing is pointing to anything wrong on your side (nRF91), the network seems to have some capacity issues or other issues causing temporary registration failures.
However, without seeing additional logs from various delays we are not able to say anything for sure, there are always possibilities for errors in modem SW or maybe we can suggest workarounds for certain problems.
If you can provide more logs we can check those.
One thing I would suggest is to check with the operator that the SIM they are using is intended for IoT devices and is expected to work in the M1 network.
Best regards,
Simon
Hi Simon
Thank you for your answers. So its most likely an issue of our national telecom provider. I will discuss this with them. Because these long connection times have a big influence of the total power consumption of an battery powered IoT device out in the field.
The SIM card is specially for IoT purpose (for the M1 Network; NB is not yet supported at the moment).
Best regards
Michael
ExAg said:Thank you for your answers. So its most likely an issue of our national telecom provider
Yes, based on the trace you sent. If you sent more traces from other delays, we can confirm this with more certainty.
Best regards,
Simon
