<?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 Profiler Kit incorrectly reporting max current.</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/18290/power-profiler-kit-incorrectly-reporting-max-current</link><description>I have the PPK measuring a custom nRF52-based board. The board consists of the nRF52, a I2C sensor, and bunch of caps (210uF worth). We built a custom board to do current measurement (this was before the PPK was released). The custom board does essentially</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 14 Dec 2016 11:59:10 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/18290/power-profiler-kit-incorrectly-reporting-max-current" /><item><title>RE: Power Profiler Kit incorrectly reporting max current.</title><link>https://devzone.nordicsemi.com/thread/70639?ContentTypeID=1</link><pubDate>Wed, 14 Dec 2016 11:59:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:068e6c56-dee0-4843-bc64-19942941a7a8</guid><dc:creator>wlgrd</dc:creator><description>&lt;p&gt;The ramp up in the beginning of the trigger plot actually looks quite sane to me, but then again, I don&amp;#39;t exactly know which part of the application that is measured. The average window peaks seems abnormal, and of course, the average is good since the peaks are so short.
The only way to see how many samples is to zoom in and count every 13µs in the trigger window, 130µs for the average window. It looks like it is a short burst and can be explained by the switches. We will look into this for the next release, so hopefully you&amp;#39;ll get a new fw/sw pack that will fix this.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Power Profiler Kit incorrectly reporting max current.</title><link>https://devzone.nordicsemi.com/thread/70638?ContentTypeID=1</link><pubDate>Mon, 12 Dec 2016 12:25:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:77abcfa4-3cee-4c79-9d92-e1ad92268fe5</guid><dc:creator>CurtisHx</dc:creator><description>&lt;p&gt;I updated m question with a screenshot.
How can I determine the sample count?&lt;/p&gt;
&lt;p&gt;I let the PPK and DUT sit over weekend unpowered, and when I started it up this morning, it&amp;#39;s bouncing between 3 mA and 22-24mA.  One peak will be 3mA, but then next one might be 22mA, then 18mA.  The average current consumption is still right where I expected it to be, so I&amp;#39;m not super worried.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Power Profiler Kit incorrectly reporting max current.</title><link>https://devzone.nordicsemi.com/thread/70637?ContentTypeID=1</link><pubDate>Mon, 12 Dec 2016 10:30:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:717ee028-7fd7-47fb-9574-8cfdc62d854c</guid><dc:creator>wlgrd</dc:creator><description>&lt;p&gt;Good to hear that the average current is at least within acceptable limits for your application. With regards to the peak current; do you see this in both the average and the trigger window? We know that due to higher sampling rate, the trigger window may some times report high peaks when there actually aren&amp;#39;t any.
These peaks comes from the fact that the hardware is doing its automatic switching which may cause false, larger peaks to show in the trigger window.&lt;/p&gt;
&lt;p&gt;How many samples are the peak currents in each application?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>