<?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>Enable/Disable CLI+Logging Programmatically?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/44926/enable-disable-cli-logging-programmatically</link><description>I&amp;#39;m trying to place my device in a low power mode for shipping. I used Logging and CLI while its in operation, but I&amp;#39;d like a way to enable/disable the CLI+Logging over BLE. As the UART backend consumes power, I would like a way to disable these modules</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 16 May 2019 17:34:39 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/44926/enable-disable-cli-logging-programmatically" /><item><title>RE: Enable/Disable CLI+Logging Programmatically?</title><link>https://devzone.nordicsemi.com/thread/187591?ContentTypeID=1</link><pubDate>Thu, 16 May 2019 17:34:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ae4958f2-dad5-4054-9dc3-4a42613b34a6</guid><dc:creator>Christian B.</dc:creator><description>&lt;p&gt;Hi. I`ve had the same issue here (SDK 14.2) and finally managed to do a workaround when doing an cli_uninit() call after stop and for waking up again first cli_init() then cli_start(). Maybe it could be helpful for you too.&lt;/p&gt;
&lt;p&gt;Regards&lt;/p&gt;
&lt;p&gt;Chris&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Enable/Disable CLI+Logging Programmatically?</title><link>https://devzone.nordicsemi.com/thread/182783?ContentTypeID=1</link><pubDate>Thu, 18 Apr 2019 22:35:31 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3f6a506d-581e-40ad-ab47-9bc180e8c62c</guid><dc:creator>Dave_couling</dc:creator><description>&lt;p&gt;Unfortunately that does not seem to reduce the current consumption, nor the CLI Blocking/waiting to receive&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Enable/Disable CLI+Logging Programmatically?</title><link>https://devzone.nordicsemi.com/thread/176733?ContentTypeID=1</link><pubDate>Mon, 18 Mar 2019 13:26:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1304056e-6fc2-4d60-ab0d-0ae789e95048</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;Can you try to manually start/stop RX do the trick? E.g.:&lt;/p&gt;
&lt;p&gt;So the the current consumption is high after calling:&lt;/p&gt;
&lt;p&gt;NRF_UART0-&amp;gt;TASKS_STARTRX = 1; // Ready to receive data.&lt;/p&gt;
&lt;p&gt;And the current consumption will go low when calling:&lt;/p&gt;
&lt;p&gt;NRF_UART0-&amp;gt;TASKS_STOPRX= 1; // Stop receive UART data.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;br /&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>