<?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 5 compatibility with smartphones having BLE 4.0</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/22243/ble-5-compatibility-with-smartphones-having-ble-4-0</link><description>Hie, 
 Is it compulsary for us to send only 20 bytes of data or less than that in one packet in BT5 as we used to do it in BT4 to make BT5 compatible in communicating with smartphones having BT4. 
 Thank You. 
 Regards
Deepak</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 22 May 2017 12:48:51 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/22243/ble-5-compatibility-with-smartphones-having-ble-4-0" /><item><title>RE: BLE 5 compatibility with smartphones having BLE 4.0</title><link>https://devzone.nordicsemi.com/thread/87397?ContentTypeID=1</link><pubDate>Mon, 22 May 2017 12:48:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a78f1716-3d45-42ec-8f2d-ec3226813a23</guid><dc:creator>RK</dc:creator><description>&lt;p&gt;no, everything needs to be negotiated. Backwards compatibility is a blessing and a curse.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE 5 compatibility with smartphones having BLE 4.0</title><link>https://devzone.nordicsemi.com/thread/87396?ContentTypeID=1</link><pubDate>Mon, 22 May 2017 12:47:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7292a7b7-79bb-4a65-a799-9007ed072efa</guid><dc:creator>endnode</dc:creator><description>&lt;p&gt;Does BT5 allow starting connection directly with non-default PDU and ATT_MTU sizes?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE 5 compatibility with smartphones having BLE 4.0</title><link>https://devzone.nordicsemi.com/thread/87398?ContentTypeID=1</link><pubDate>Mon, 22 May 2017 12:44:24 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9ced7353-c9ce-434d-9a76-ef4414f57dbc</guid><dc:creator>endnode</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;BT4.0 indeed supports PDU length extension (on Link Layer) as well as MTU extension on ATT/GATT layer. The fact that we all stick to default ATT_MTU size of 23B (from which 3 bytes are &amp;quot;eaten&amp;quot; by GATT header overhead) is just the way we deal with the fact that many deices (as well as Nordic stacks!) haven&amp;#39;t supported these features originally. All these concepts (PDU and MTU extensions) are indeed valid in BT5.0 so there is no problem to be backward compatible (= support features from BT5.0 but by default use &amp;quot;legacy&amp;quot; modes to support connection with devices supporting only older BT versions).&lt;/p&gt;
&lt;p&gt;Cheers Jan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE 5 compatibility with smartphones having BLE 4.0</title><link>https://devzone.nordicsemi.com/thread/87395?ContentTypeID=1</link><pubDate>Mon, 22 May 2017 12:41:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b07e71bc-59fd-4b71-9a29-c9b45d376c47</guid><dc:creator>RK</dc:creator><description>&lt;p&gt;No not at all. There are procedures involved in trying to increase the MTU and if you&amp;#39;re talking to another device (whether BT4 or 5) which doesn&amp;#39;t support longer MTUs, the procedures will fail and you&amp;#39;ll need to fall back to the required minimum.&lt;/p&gt;
&lt;p&gt;Just write your code to offer a larger MTU, attempt to negotiate a larger MTU and if they work, you use it, if they don&amp;#39;t, you stick with the default.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>