<?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>L2CAP fragmentation with a data length of 251 bytes</title><link>https://test-devzone.nordicsemi.com/f/nordic-q-a/85631/l2cap-fragmentation-with-a-data-length-of-251-bytes</link><description>Hello all, 
 Background: -NRF5340 -NRF SDK 1.9 -Zephyr 2.7.99 
 My objective is to send a data of 768 bytes by BLE. I use 4 notify to send this 768 bytes data (192 packets) I configured the bt ctlr with a data length of 251 byte. The peripheral is my</description><dc:language>en-US</dc:language><generator>Telligent Community 13 Non-Production</generator><lastBuildDate>Thu, 12 May 2022 11:05:36 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://test-devzone.nordicsemi.com/f/nordic-q-a/85631/l2cap-fragmentation-with-a-data-length-of-251-bytes" /><item><title>RE: L2CAP fragmentation with a data length of 251 bytes</title><link>https://test-devzone.nordicsemi.com/thread/367577?ContentTypeID=1</link><pubDate>Thu, 12 May 2022 11:05:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2f0a26af-dc80-40b5-b7fe-cfe07af6f04e</guid><dc:creator>user77782</dc:creator><description>&lt;p&gt;Hi,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Sorry for the late reply.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;The problem here is that the client PC has Max Rx time set to 328 microseconds which don&amp;#39;t allow our nRF5340 to transmit the 251 bytes in one packet. The suitable time for 251 bytes packet would be 2120us. Our device set such value for the Rx and Tx max time in a response to LL_LENGTH_REQ. But in request from the PC, our device gets that PC max Rx time is 328 microsecond even if max Rx octets size is 251 bytes. For 1MB PHY the 328 microsecond allows our SoC to set packets not longer than 27 bytes because we cannot transmit packets that transmission time would be greater than PC Rx max time. But in a reverse direction from PC to our SoC, it should be possible to send a packet of 251bytes.&amp;nbsp; I hope that this clarifies your issue.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;To improve the throughput the client PC needs to request the data length update with Rx time set to 2120us (for 1M PHY). This is only possible when the client PC BLE controller supports such Rx max time. The other solution can be switching to use 2M PHY it will increase throughput in all cases even with the dongle which can handle a packet of 251 bytes. In your case if increasing Rx max time on the PC side is not possible then you can try to use 2M PHY, it gives you faster data transmission in the air and you will send about two times more data in one packet.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;-Amanda&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: L2CAP fragmentation with a data length of 251 bytes</title><link>https://test-devzone.nordicsemi.com/thread/358253?ContentTypeID=1</link><pubDate>Tue, 15 Mar 2022 14:35:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1076df71-d50c-4587-a2ea-fe47dc26d3eb</guid><dc:creator>user77782</dc:creator><description>&lt;p&gt;Thanks for the tip. We are looking into the issue and will be back if we find anything.&lt;/p&gt;
&lt;p&gt;-Amanda&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: L2CAP fragmentation with a data length of 251 bytes</title><link>https://test-devzone.nordicsemi.com/thread/357595?ContentTypeID=1</link><pubDate>Fri, 11 Mar 2022 10:04:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0c366e9a-c73e-4108-bba7-70cacacfb2f9</guid><dc:creator>user114027</dc:creator><description>&lt;p&gt;Hi Amanda,&lt;/p&gt;
&lt;p&gt;On my first post I already put a trace file. The connection with the PC starts time = 262.381 s. I put you an image of the answer of the PC.&lt;/p&gt;
&lt;p&gt;&lt;img src="https://test-devzone.nordicsemi.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/RSP_5F00_DATA_5F00_LENGTH.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;Hichem Ghandri&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: L2CAP fragmentation with a data length of 251 bytes</title><link>https://test-devzone.nordicsemi.com/thread/357550?ContentTypeID=1</link><pubDate>Fri, 11 Mar 2022 08:21:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1c9b154b-f625-4acc-aa61-2623f8c0657f</guid><dc:creator>user77782</dc:creator><description>&lt;p&gt;Hi,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Sounds&amp;nbsp;&lt;span&gt;the nRF52840 dongle can accept and update the&amp;nbsp;data length of 251 bytes instead of&amp;nbsp;the PC. This is decided by the connected central&amp;nbsp;ble. Guess PC ble rejects to update&amp;nbsp;data length to 251. Needs the sniffer log to prove it. Please capture the sniffer starting before the connecting.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Regards,&lt;br /&gt;Amanda&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>