<?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>Increased Peak Advertising Current</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/58711/increased-peak-advertising-current</link><description>While advertising I could see some increased current peaks on one of the three channels. Its random and is observed mostly at the first or last channel of advertising. 
 Any idea what could be the reason? Does the nearby scanning device affect the power</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 11 Mar 2020 00:45:58 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/58711/increased-peak-advertising-current" /><item><title>RE: Increased Peak Advertising Current</title><link>https://devzone.nordicsemi.com/thread/239236?ContentTypeID=1</link><pubDate>Wed, 11 Mar 2020 00:45:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bdbd8749-a6f8-4c29-99e4-f515c746beb4</guid><dc:creator>Justin</dc:creator><description>&lt;p&gt;Thanks Kenneth for the clarification.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Increased Peak Advertising Current</title><link>https://devzone.nordicsemi.com/thread/239087?ContentTypeID=1</link><pubDate>Tue, 10 Mar 2020 11:57:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:032819f4-3782-43b6-846f-0475f649f270</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;It may also be an invalid BLE packet from a central device (e.g. scan request packet with CRC errors due to interference and/or a connection request packet CRC with errors), in these cases the radio may stay in receive mode until a timeout occurs.&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><item><title>RE: Increased Peak Advertising Current</title><link>https://devzone.nordicsemi.com/thread/238956?ContentTypeID=1</link><pubDate>Mon, 09 Mar 2020 23:27:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2187a13a-cfa2-4ef3-842f-5509d16d6e40</guid><dc:creator>Justin</dc:creator><description>&lt;p&gt;&lt;img alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/image001.jpg" /&gt;&lt;/p&gt;
&lt;p&gt;Hi Kenneth,&lt;/p&gt;
&lt;p&gt;We captured 3 screenshots using the same scale that shows a normal advertising current pulse, the slightly higher pulse that we saw before which we associated with the scan response, and the new higher amplitude pulse that&amp;nbsp;we observed and don&amp;rsquo;t know what it is.&lt;/p&gt;
&lt;p&gt;We see the higher amplitude pulse occur during the channel 37 activity.&amp;nbsp;With the Ellisys BLE sniffer, it does not appear that this is linked to a scan response.&lt;/p&gt;
&lt;p&gt;Is there anything that we are not counting for?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Increased Peak Advertising Current</title><link>https://devzone.nordicsemi.com/thread/238352?ContentTypeID=1</link><pubDate>Thu, 05 Mar 2020 15:25:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3f1bfda2-b7ef-42e6-8462-1e2b7b300d54</guid><dc:creator>Justin</dc:creator><description>[quote userid="2111" url="~/f/nordic-q-a/58711/increased-peak-advertising-current/238194"]This is likely a central that is transmitting a scan request packet, and then the peripheral will reply with a scan response packet. This typically happen on 1 of the advertisement channels[/quote]
&lt;p&gt;Putting my setup into the anechoic chamber did eliminate the occasional larger advertising current peaks.&lt;/p&gt;
&lt;p&gt;As a result, the larger peaks do appear to be linked to some device behavior related to scan requests coming from central devices.&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;But in that case I would expect a longer period of a Tx --&amp;gt; Rx --&amp;gt; Tx --&amp;gt; Rx current draw rather than a higher current draw.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Is my understanding correct?&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Increased Peak Advertising Current</title><link>https://devzone.nordicsemi.com/thread/238194?ContentTypeID=1</link><pubDate>Thu, 05 Mar 2020 09:00:45 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:53364156-3d8d-473a-a7a8-36188635c1cb</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;This is likely a central that is transmitting a scan request packet, and then the peripheral will reply with a scan response packet. This typically happen on 1 of the advertisement channels, but may also happen on more than 1 channel if there are more than 1 central nearby.&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>