<?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>Optimizing L2CAP throughput</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/120931/optimizing-l2cap-throughput</link><description>On the nRF5350 I&amp;#39;m currently seeing about 30 kB throughput via bt_l2cap_chan_send. It seems that could be optimized to over 100 kB. I&amp;#39;m looking at some values in the l2cap struts to check if things are setup correctly. See below. One thing I noticed is</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 30 Apr 2025 11:07:18 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/120931/optimizing-l2cap-throughput" /><item><title>RE: Optimizing L2CAP throughput</title><link>https://devzone.nordicsemi.com/thread/533545?ContentTypeID=1</link><pubDate>Wed, 30 Apr 2025 11:07:18 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9b2a2a56-851a-4d90-bbc1-670cf45b2a76</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;Here is a screenshot from the wireshark trace:&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/pastedimage1746010836523v1.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;From what I can tell, the nRF5 device have the MD-bit (MoreData) set at the end of each connection event, so from the nRF5-side of things, the packet exchange can continue.&amp;nbsp;&lt;span style="font-family:inherit;"&gt;But the central ends the connection event. Looks like the central only support up-to 5 pack-pair each connection event. Maybe the central is doing something else, other connections, scanning for other devices at the same time, that is causing this, or maybe the&amp;nbsp;central simply only support 5 packet-pair each connection event.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Optimizing L2CAP throughput</title><link>https://devzone.nordicsemi.com/thread/532874?ContentTypeID=1</link><pubDate>Thu, 24 Apr 2025 14:57:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:125674b9-4d3b-4a86-8f19-ce310388d45c</guid><dc:creator>denis</dc:creator><description>&lt;p&gt;Here is the Wireshark capture for a transaction. &amp;nbsp;The&amp;nbsp;&lt;span&gt;bt_l2cap_chan_send sequences we are trying to optimize are in the second half of the capture.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/bt_5F00_l2cap_5F00_chan_5F00_send.pcapng"&gt;devzone.nordicsemi.com/.../bt_5F00_l2cap_5F00_chan_5F00_send.pcapng&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Optimizing L2CAP throughput</title><link>https://devzone.nordicsemi.com/thread/532823?ContentTypeID=1</link><pubDate>Thu, 24 Apr 2025 12:34:16 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6183b9c6-6f9f-4c8a-af2d-f4b6df7cc569</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;Hi!&lt;/p&gt;
&lt;p&gt;Could you post a sniffer log?&amp;nbsp;&lt;a href="https://www.nordicsemi.com/Products/Development-tools/nrf-sniffer-for-bluetooth-le"&gt;https://www.nordicsemi.com/Products/Development-tools/nrf-sniffer-for-bluetooth-le&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>