<?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>BLE 1M+Coded PHY connection and scanning</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/103595/ble-1m-coded-phy-connection-and-scanning</link><description>I have a project where I want to connect one central device to multiple peripheral devices using BLE. Some of the connections should use 1M PHY, some should use coded PHY. Any of the peripheral devices may be present and the connections should form in</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 13 Sep 2023 13:48:29 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/103595/ble-1m-coded-phy-connection-and-scanning" /><item><title>RE: BLE 1M+Coded PHY connection and scanning</title><link>https://devzone.nordicsemi.com/thread/445869?ContentTypeID=1</link><pubDate>Wed, 13 Sep 2023 13:48:29 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fc8b4c6b-d429-475d-be23-bc7573cabf40</guid><dc:creator>sheindel-llt</dc:creator><description>&lt;p&gt;I tried 80ms interval and 20ms window (scan and connection) but I got the same behavior. I&amp;#39;m continuing to play around with the values to see what difference it might make.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE 1M+Coded PHY connection and scanning</title><link>https://devzone.nordicsemi.com/thread/445707?ContentTypeID=1</link><pubDate>Tue, 12 Sep 2023 20:50:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5694c176-eb4a-48b9-867b-ac11e7009f40</guid><dc:creator>sheindel-llt</dc:creator><description>&lt;p&gt;Thanks for the suggestion, hopefully I will try it out tomorrow. I was not expecting that 40ms scan interval would be too aggressive but it&amp;#39;s good to check.&lt;/p&gt;
&lt;p&gt;By the way, do you have any insight into how the scan interval works when both 1M and coded PHY are in use? Does it alternate between PHYs, or can it scan on both PHYs at the same time?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE 1M+Coded PHY connection and scanning</title><link>https://devzone.nordicsemi.com/thread/445650?ContentTypeID=1</link><pubDate>Tue, 12 Sep 2023 13:31:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2644030e-7a85-434c-8cdf-048dac245f79</guid><dc:creator>Amanda Hsieh</dc:creator><description>&lt;p&gt;Hi,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Your scanning and connection parameters are quite aggressive for such a complex scenario. Could you test again with larger scan and connection intervals, and try to make the scan interval a multiple of the connection interval? For instance, try 80ms scan interval and 20ms con interval with a scan window of 20ms.&lt;/p&gt;
&lt;p&gt;-Amanda H.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE 1M+Coded PHY connection and scanning</title><link>https://devzone.nordicsemi.com/thread/445487?ContentTypeID=1</link><pubDate>Mon, 11 Sep 2023 21:31:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:33203cce-bd37-41f2-b323-c2d974302035</guid><dc:creator>Amanda Hsieh</dc:creator><description>&lt;p&gt;Hi,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I am looking into this case and will reply later.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Amanda H.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>