%NCELLMEAS timeout

RE: %NCELLMEAS timeout

Lily Snape — Thu, 05 Oct 2023 07:27:26 GMT

The maximum timeout for the lte_lc_neighbour_cell_measurement() function or %NCELLMEAS is determined by the settings or parameters you specify when you call the function or within your SDK. The specific timeout duration can vary based on your application's requirements and configuration. mapquest

RE: %NCELLMEAS timeout

barbiz — Sun, 26 Feb 2023 09:57:46 GMT

Thanks for your help!

Marco

RE: %NCELLMEAS timeout

Didrik Rokhaug — Wed, 22 Feb 2023 10:10:49 GMT

It depends a bit on how you use the command, and what you value most.

But if power consumption is the most important, it will be a good idea to start a timer/delayable work item that will stop the search if it takes too long.

However, most of the search types should finish very quickly anyway, so unless you use search type 2 or 5 with a high gci_count (or in a location with very few cells), I don't really expect it to be a problem.

RE: %NCELLMEAS timeout

barbiz — Wed, 22 Feb 2023 09:33:29 GMT

Ok, thanks. So I guess that, in order to have power consumption under control, it is mandatory to send the abort command. Correct?

RE: %NCELLMEAS timeout

Didrik Rokhaug — Mon, 20 Feb 2023 16:55:04 GMT

Hi,

There is no upper limit set by that function/AT command, and depending on the search type, it will keep searching until it has done a complete search on all enabled bands.

It is up to the application to decide what is "reasonable", and the command might search for longer than what the application deems "reasonable", depending on the search parameters and network conditions.

Best regards,

Didrik