<?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>Mixed coded and uncoded PHY on central side with NCS</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/84547/mixed-coded-and-uncoded-phy-on-central-side-with-ncs</link><description>My use case: There are different but similar peripherals advertising with 1M uncoded or coded PHY. Some of them are even advertising in mixed mode. 
 Question: How to connect to each of them with my central? 
 What I did until now: I initialized scanning</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 16 Feb 2022 08:20:44 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/84547/mixed-coded-and-uncoded-phy-on-central-side-with-ncs" /><item><title>RE: Mixed coded and uncoded PHY on central side with NCS</title><link>https://devzone.nordicsemi.com/thread/353264?ContentTypeID=1</link><pubDate>Wed, 16 Feb 2022 08:20:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2e402066-9e1a-494e-a8f9-f1e4c40c5b39</guid><dc:creator>OliverB</dc:creator><description>[quote userid="6207" url="~/f/nordic-q-a/84547/mixed-coded-and-uncoded-phy-on-central-side-with-ncs/353079#353079"]Please go ahead with your scan info decoding of the phy and send the connect request appropriately on the phy.[/quote]
&lt;p&gt;Since this works, I&amp;#39;m glad to have&amp;nbsp;a solution. Thanks for your support!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Mixed coded and uncoded PHY on central side with NCS</title><link>https://devzone.nordicsemi.com/thread/353079?ContentTypeID=1</link><pubDate>Tue, 15 Feb 2022 11:57:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:427b793e-3304-42ab-bd67-cd5f65ed1d19</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;it looks like you are right about the behavior, just tested it, but it is unclear to me if this is the behavior from the spec or the limitation on our stack. Need to dig a bit more which might take some time. But it looks like you need to filter the scan info to decode the phy and send the correct request.&amp;nbsp; Please go ahead with your scan info decoding of the phy and send the connect request appropriately on the phy.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Mixed coded and uncoded PHY on central side with NCS</title><link>https://devzone.nordicsemi.com/thread/352613?ContentTypeID=1</link><pubDate>Fri, 11 Feb 2022 13:06:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b2fe6bb6-2f25-46f7-a7f2-fdc60819c17d</guid><dc:creator>Susheel Nuguru</dc:creator><description>[quote user=""]Is this expected behavior? Do I miss some config or anything else? Or do I have to parse the&amp;nbsp;bt_scan_device_info and setup the connection create parameter dependent to the received phy in&amp;nbsp;bt_scan_device_info?[/quote]
&lt;p&gt;I am not sure if we need to do that. It might be that&amp;nbsp;bt_conn_le_create somehow has the dependency on knowing what phy it is sending to. I will check few things on Monday and come back later to with info. Thanks for your patience.&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>