<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AT%CONEVAL response time</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/91759/at-coneval-response-time</link><description>In my application I call AT%CONEVAL periodically to gather data about the current connection. Sometimes it takes many seconds to respond, which causes problems for my application. Here is the example code I&amp;#39;m using (NCS v1.7.0): 
 
 I have a timer set</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 06 Nov 2023 05:42:14 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/91759/at-coneval-response-time" /><item><title>RE: AT%CONEVAL response time</title><link>https://devzone.nordicsemi.com/thread/454107?ContentTypeID=1</link><pubDate>Mon, 06 Nov 2023 05:42:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0f190255-9a86-4be3-857e-a9e656c842d0</guid><dc:creator>optical</dc:creator><description>&lt;p&gt;Would be pretty helpful if the nordic AT Command reference documentation contained this type of information. Instead of us just trying it and hoping that we find it out...&lt;br /&gt;&lt;br /&gt;We simply cannot test all of the situations when the deployed devices are all around the world.&lt;br /&gt;&lt;br /&gt;Could nordic try to add the min-max-arg response time to the AT Command reference guide? Or at least mark the one that might block in certain situations?&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: AT%CONEVAL response time</title><link>https://devzone.nordicsemi.com/thread/387364?ContentTypeID=1</link><pubDate>Wed, 21 Sep 2022 19:16:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a2059731-eba4-4abf-bdff-413a841e7008</guid><dc:creator>Chris Burns</dc:creator><description>&lt;p&gt;I have discovered that using the AT%CONEVAL command asynchronously ensures my thread doesn&amp;#39;t block while waiting for the response. The response can still take a long time to respond, and this method results in other issues sometimes (see &amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/92195/nrf_modem_at_cmd_async-callback-passes-bad-pointer"&gt;nrf_modem_at_cmd_async callback passes bad pointer&lt;/a&gt;).&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: AT%CONEVAL response time</title><link>https://devzone.nordicsemi.com/thread/386061?ContentTypeID=1</link><pubDate>Tue, 13 Sep 2022 20:35:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4fc750c7-29b3-450b-bce3-4f30f5777a22</guid><dc:creator>Kazi Afroza Sultana</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;&lt;span&gt;CONEVAL depends on the network conditions, and if there&amp;#39;s a disrupt in the LTE link, things can take longer time or even time out due to the network being not available at that specific time. You can test with AT Client to see what the response is and can send us the output log. Our modem team can have a look.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Thanks.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Best Regards,&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Kazi Afroza Sultana&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: AT%CONEVAL response time</title><link>https://devzone.nordicsemi.com/thread/386054?ContentTypeID=1</link><pubDate>Tue, 13 Sep 2022 18:06:29 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2c82eb07-366d-41db-869f-8f18f2ef6821</guid><dc:creator>Achim Kraus</dc:creator><description>&lt;p&gt;OK, if AT%CONEVAL is only used after CEREG=1 then that startup assumption doesn&amp;#39;t work.&lt;/p&gt;
&lt;p&gt;I guess you prefer an answer from the modem developers and not some ideas to try out.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: AT%CONEVAL response time</title><link>https://devzone.nordicsemi.com/thread/386053?ContentTypeID=1</link><pubDate>Tue, 13 Sep 2022 17:56:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a59731f9-af61-4127-b5a5-66af1b621aac</guid><dc:creator>Chris Burns</dc:creator><description>&lt;p&gt;To clarify: The AT%CONEVAL is send periodically (like every 500 msec for example) while the connection is active. It is only sent after a CEREG=1 is received from the modem.&lt;/p&gt;
&lt;p&gt;A large majority of the time it returns very quickly.&lt;/p&gt;
&lt;p&gt;But every once in a while it takes many seconds to return. This is the behavior I am trying to understand - why would the response time vary so wildly sometimes? And is there a way to use AT%CONEVAL which would never result in a long response time?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: AT%CONEVAL response time</title><link>https://devzone.nordicsemi.com/thread/385836?ContentTypeID=1</link><pubDate>Tue, 13 Sep 2022 05:28:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bfd0aeb0-83e5-4c0f-b993-2bde234af082</guid><dc:creator>Achim Kraus</dc:creator><description>&lt;p&gt;&amp;gt; PSM is not enabled&lt;/p&gt;
&lt;p&gt;Do you apply +CFUN=0/1 (power off/on) for energy management?&lt;/p&gt;
&lt;p&gt;Just to say: in my opinion, that&amp;#39;s not the intended way and the energy, that requires, will be disappointing.&lt;/p&gt;
&lt;p&gt;In my experience, AT%CONEVAL returns always immediately, but I have the device &amp;quot;always on&amp;quot; and use PSM.&lt;/p&gt;
&lt;p&gt;Reading the documentation, I&amp;#39;m not sure, if the &lt;strong&gt;data&lt;/strong&gt; CONEVAL is based on, are kept over off/on. If not, then the device need to search for a network after it&amp;#39;s enabled before it can return from CONEVAL. How long a full attach requires, is out of my scope.&lt;/p&gt;
&lt;p&gt;A reattach to the network takes in my experience with NB-IoT (germany) usually 2-3s. Sometimes also up to 15s and in rare cases even longer. Maybe you wait, until the device reports LTE_LC_RRC_MODE_CONNECTED and LTE_LC_NW_REG_REGISTERED_HOME or LTE_LC_NW_REG_REGISTERED_ROAMING before calling AT%CONEVAL.&lt;/p&gt;
&lt;p&gt;Not sure if that helps. As mentioned, I don&amp;#39;t see these delays of CONEVAL on my devices.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: AT%CONEVAL response time</title><link>https://devzone.nordicsemi.com/thread/385818?ContentTypeID=1</link><pubDate>Mon, 12 Sep 2022 21:12:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:67cc8c96-5f05-425e-9d80-2cc723af0377</guid><dc:creator>Chris Burns</dc:creator><description>&lt;p&gt;The problem definitely occurs with NB-IOT - Cat-M has not been tested as extensively so I can&amp;#39;t say whether it occurs at the same rate. PSM is not enabled.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: AT%CONEVAL response time</title><link>https://devzone.nordicsemi.com/thread/385597?ContentTypeID=1</link><pubDate>Sun, 11 Sep 2022 05:54:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7a9287a0-917f-4ca4-97a8-a652ae2e5853</guid><dc:creator>Achim Kraus</dc:creator><description>&lt;p&gt;Does the nRF9160 use LTE-M or NB-IoT? Is PSM enabled?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: AT%CONEVAL response time</title><link>https://devzone.nordicsemi.com/thread/385551?ContentTypeID=1</link><pubDate>Fri, 09 Sep 2022 15:31:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b4d28ea2-fbeb-4de1-a86f-74767a78ffa4</guid><dc:creator>Chris Burns</dc:creator><description>&lt;p&gt;I only mentioned the timer to say that sometimes the response to the AT%CONEVAL command took longer than 12 seconds. Often it returns very quickly, but sometimes it takes quite a long time.&lt;/p&gt;
&lt;p&gt;I&amp;#39;m trying to understand if there are best practices regarding the AT%CONEVAL command. If there is a way to prevent the cases where it takes a long time I want to know so I can avoid them.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: AT%CONEVAL response time</title><link>https://devzone.nordicsemi.com/thread/385445?ContentTypeID=1</link><pubDate>Fri, 09 Sep 2022 08:23:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:eeff6983-54f7-492a-8182-24ba1f289d0b</guid><dc:creator>Kazi Afroza Sultana</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;There are several factors related for the accuracy of the evaluation result. You can try to run the AT command and show us the output log. &amp;#39;&amp;#39;&lt;span&gt;I have a timer set for 12 seconds that will reboot the nRF9160 if it trips, and it trips with some regularity.&amp;#39; - Do you get the return from timer?&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Thanks.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Best Regards,&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Kazi Afroza Sultana&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>