<?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>What is the process of sending long (chunked) messages over NUS?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/82613/what-is-the-process-of-sending-long-chunked-messages-over-nus</link><description>Hiya. We&amp;#39;re building a custom appliance on top of a Nordic chip that talks to an Android/iOS app developed with Flutter and a custom cross-platform Bluetooth plugin. 
 We use Nordic UART Service extensively and just noticed that some of our messages are</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 14 Dec 2021 08:25:25 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/82613/what-is-the-process-of-sending-long-chunked-messages-over-nus" /><item><title>RE: What is the process of sending long (chunked) messages over NUS?</title><link>https://devzone.nordicsemi.com/thread/343320?ContentTypeID=1</link><pubDate>Tue, 14 Dec 2021 08:25:25 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:951f98db-c6f3-4896-b3c6-c197c1e15102</guid><dc:creator>luopio</dc:creator><description>&lt;p&gt;Thanks Edvin! This is good advice. I think I got sidetracked by seeing things like:&amp;nbsp;&lt;a href="https://github.com/NordicSemiconductor/Android-BLE-Library/blob/master/ble/src/main/java/no/nordicsemi/android/ble/data/DataSplitter.java#L28-L29"&gt;https://github.com/NordicSemiconductor/Android-BLE-Library/blob/master/ble/src/main/java/no/nordicsemi/android/ble/data/DataSplitter.java#L28-L29&lt;/a&gt;&amp;nbsp;in the code and assumed there is some internal logic in splitting a long NUS message to several pieces.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I&amp;#39;ve added requestMtu() calls to our library now and let&amp;#39;s see if that resolves the issue.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: What is the process of sending long (chunked) messages over NUS?</title><link>https://devzone.nordicsemi.com/thread/342964?ContentTypeID=1</link><pubDate>Fri, 10 Dec 2021 14:55:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ef524cb4-7f6e-4d83-b942-b1347b716a86</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;Perhaps you need to look in the other end, and check how Flutter handles long messages in BLE. 20 bytes is not a hard limit. Typically devices will negotiate a higher message length (MTU) after connection. Perhaps this doesn&amp;#39;t happen when you are using flutter?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;You can always try to capture a sniffer trace using the nRF Sniffer for Bluetooth Low Energy and compare the data on air when you are using the Nordic app.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;But my guess is that you need to look into the Flutter library, and see how it handles a larger MTU/MTU updates.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Edvin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>