<?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 UART receive path - what is the rough increase of power consumption? Alternative solutions?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/71167/enable-uart-receive-path---what-is-the-rough-increase-of-power-consumption-alternative-solutions</link><description>Hello, 
 we are currently using NRF_LOG_INFO over UART. We print out some values from time to time (seldom). Assume we never go manually to some of the sleep modes. 
 We use deferred mode. I think UARTE is used. 
 Now we want to enable additionally also</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 02 Feb 2021 15:22:18 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/71167/enable-uart-receive-path---what-is-the-rough-increase-of-power-consumption-alternative-solutions" /><item><title>RE: Enable UART receive path - what is the rough increase of power consumption? Alternative solutions?</title><link>https://devzone.nordicsemi.com/thread/292532?ContentTypeID=1</link><pubDate>Tue, 02 Feb 2021 15:22:18 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e30e25c2-cefa-431a-b2bc-885d97e6c65c</guid><dc:creator>Kenneth</dc:creator><description>[quote user=""](Some quick hack test implementation showed 1mA only for enabling reception path over UARTE. Could this be real? Same with UART CLI?)[/quote]
&lt;p&gt;While TASK_STARTRX is active, then it will draw this&amp;nbsp;amount of current yes. So typically you need some handshaking mechanism, such that you can use a pin that the system can wakeup and execute TASK_STARTRX on, and as soon as possible execute TASK_STOPRX when reception is complete. How you implement and solve this will be very unique for your requirements. You can find one implementation in our nRF Connect SDK that you may use as reference:&lt;/p&gt;
&lt;p&gt;&lt;a href="http://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/drivers/uart_nrf_sw_lpuart.html?highlight=lpuart"&gt;http://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/drivers/uart_nrf_sw_lpuart.html?highlight=lpuart&lt;/a&gt;&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>