<?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>Power profiling kit issue on SDK14</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/26653/power-profiling-kit-issue-on-sdk14</link><description>We are using the nRF6707 power profiler kit to measure our EVB’s current consumption in advertising mode. We use the example app ble_app_pwr_profiling. The only change is the advertising interval. The interval is changed to 500ms from 100ms #define NON_CONNECTABLE_ADV_INTERVAL</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 08 Nov 2017 11:51:36 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/26653/power-profiling-kit-issue-on-sdk14" /><item><title>RE: Power profiling kit issue on SDK14</title><link>https://devzone.nordicsemi.com/thread/104866?ContentTypeID=1</link><pubDate>Wed, 08 Nov 2017 11:51:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5b08df2f-e76b-4f09-b620-bdaa753f74a5</guid><dc:creator>wlgrd</dc:creator><description>&lt;p&gt;The trigger window restarting without you telling it to seems highly irregular. I&amp;#39;ve been testing this kit for quite some time and never noticed this behavior. The reason you are experiencing drop outs from average is because you are running the trigger window for sure. Try setting the trigger level to e.g 50000 to really force it to not send you data. Also, try commenting away line 236 in ppk.py &lt;code&gt;# plotter.start_log_thread()&lt;/code&gt; if you experience delays (just as a test). But, even if you have delays, the time between events should be correct.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Power profiling kit issue on SDK14</title><link>https://devzone.nordicsemi.com/thread/104865?ContentTypeID=1</link><pubDate>Tue, 07 Nov 2017 16:59:02 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:747b0da0-68c9-4f22-8611-b2b9cec2ef89</guid><dc:creator>Rbai</dc:creator><description>&lt;p&gt;I have to stop both windows, then only start the Average window to get it to work properly. But after some time, the Trigger window starts to run by itself, at that time the Average window is showing irregularly again. Please let me know when the official fix for this is out. Thanks.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Power profiling kit issue on SDK14</title><link>https://devzone.nordicsemi.com/thread/104864?ContentTypeID=1</link><pubDate>Tue, 07 Nov 2017 10:27:01 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d2b98196-7223-4f54-b633-8fecad6a5ffe</guid><dc:creator>Stian R&amp;#248;ed Hafskjold</dc:creator><description>&lt;p&gt;There are some issues with buffer overflow with the RTT implementation. You can try to stop the trigger window when you are using the average window, and vice versa.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>