<?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>Sniffer unable to capture NUS and HRM data</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/38050/sniffer-unable-to-capture-nus-and-hrm-data</link><description>I had setup nRF sniffer with below software and hardware, but the Wireshark seen unable capture BLE data. 
 
 
 nRF Sniffer software nrf_sniffer_2.0.0-beta-1_51296aa.zip 
 nRF sniffer firmware “sniffer_pca10040_51296aa.hex” with nRF52 Development Kit</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 31 Aug 2018 11:37:02 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/38050/sniffer-unable-to-capture-nus-and-hrm-data" /><item><title>RE: Sniffer unable to capture NUS and HRM data</title><link>https://devzone.nordicsemi.com/thread/146747?ContentTypeID=1</link><pubDate>Fri, 31 Aug 2018 11:37:02 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9ecc528b-896d-47e6-925b-535ec6269046</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi George,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;You may need to choose a device that you want to follow in the drop down &amp;quot;Device&amp;quot; list o the sniffer tool bar. This way the sniffer can follow only that advertiser and will capture the connect request to follow the connection.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;This is described in step 2 in Chapter 3 in the sniffer manual:&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Follows one particular device and tries to catch all packets sent to or from this particular device.&lt;/em&gt;&lt;br /&gt;&lt;em&gt;This mode will catch all:&lt;/em&gt;&lt;br /&gt;&lt;em&gt;• Advertisements and Scan Responses sent from the device&lt;/em&gt;&lt;br /&gt;&lt;em&gt;• Scan Requests and Connect Requests sent to the device&lt;/em&gt;&lt;br /&gt;&lt;em&gt;• Packets in the Connection sent between the two devices in the Connection&lt;/em&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>