<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://test-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>nRF Sniffer and Periodic Advertising Sync Transfer (PAST)</title><link>https://test-devzone.nordicsemi.com/f/nordic-q-a/88678/nrf-sniffer-and-periodic-advertising-sync-transfer-past</link><description>Hi, While testing the new nrf5340 Audio DK and BIS example, I wanted to see how the Periodic Advertising Sync Transfer (PAST) data looks on the nRF Sniffer version 4.1.0. The release notes states that the latest version supports capture/following Periodic</description><dc:language>en-US</dc:language><generator>Telligent Community 13 Non-Production</generator><lastBuildDate>Thu, 09 Jun 2022 11:54:21 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://test-devzone.nordicsemi.com/f/nordic-q-a/88678/nrf-sniffer-and-periodic-advertising-sync-transfer-past" /><item><title>RE: nRF Sniffer and Periodic Advertising Sync Transfer (PAST)</title><link>https://test-devzone.nordicsemi.com/thread/371646?ContentTypeID=1</link><pubDate>Thu, 09 Jun 2022 11:54:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ab96def1-5c14-49c6-a06e-12b30be7c085</guid><dc:creator>user77782</dc:creator><description>&lt;p&gt;Hi,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;BIGinfo and BIS are part of Audio which is not supported in the sniffer currently. Although the sniffer can understand the SyncInfo, it would cause an issue while&amp;nbsp;receiving an AUX_SYNC_IND with BIGInfo in the &lt;span&gt;packet&lt;/span&gt;.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;From the log, it appears that this packet is not received from the sniffer firmware. So it must have been dropped or not received.&lt;/p&gt;
&lt;p&gt;The clock accuracy is set through Kconfig (assuming they are testing using NCS). For example `CONFIG_CLOCK_CONTROL_NRF_K32SRC_50PPM=y` would set 50 ppm instead of 20.&lt;/p&gt;
&lt;p&gt;-Amanda&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF Sniffer and Periodic Advertising Sync Transfer (PAST)</title><link>https://test-devzone.nordicsemi.com/thread/371446?ContentTypeID=1</link><pubDate>Wed, 08 Jun 2022 13:48:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6ea79aba-11e6-4f72-9d77-5f7acdc6a4e6</guid><dc:creator>user72892</dc:creator><description>&lt;p&gt;Hi Amanda,&lt;br /&gt;&lt;br /&gt;The thing that I am trying to do here is to receive the messages that contain&amp;nbsp;the BIGInfo structure (Needed to initiate Broadcast ISO&amp;nbsp;stream). And if I am not wrong, they come in&amp;nbsp;&lt;span&gt;AUX_SYNC_IND messages. Does the nRF Sniffer understand SyncInfo and can use that to sync on the messages?&lt;br /&gt;&lt;br /&gt;&lt;/span&gt;The log from the nRF Sniffer tool just says &amp;quot;INFO: Packet read timed out.&amp;quot; as soon as I try to follow it.&lt;br /&gt;&lt;br /&gt;How can I set 20ppm&amp;nbsp;&lt;span&gt;sleep clock accuracy?&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;Best,&lt;br /&gt;/Eriks&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF Sniffer and Periodic Advertising Sync Transfer (PAST)</title><link>https://test-devzone.nordicsemi.com/thread/371326?ContentTypeID=1</link><pubDate>Wed, 08 Jun 2022 08:59:18 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:349c463e-581b-4951-9a89-a1c8d4f8d9ea</guid><dc:creator>user77782</dc:creator><description>&lt;p&gt;Hi,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;We don&amp;#39;t support the Periodic Advertising Sync Transfer control procedure in 4.1.0. But it seems that the question is about Periodic Advertising Data? If so, are you able to follow a connection using the device you are following?&amp;nbsp;It could be that the device you are following does not have a correct set sleep clock accuracy, it is set to 0-20 ppm.&amp;nbsp;If that value is too low for the clock used it could be sending outside of the transmit window.&amp;nbsp;Could you also provide the&amp;nbsp;capture log of the sniffer?&amp;nbsp;(&amp;quot;Log&amp;quot; button on the nRF Sniffer toolbar).&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Amanda&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>