<?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 mesh 5.0 couldn&amp;#39;t send 255 bytes of data from client to server</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/75977/ble-mesh-5-0-couldn-t-send-255-bytes-of-data-from-client-to-server</link><description>Hi there, 
 For my POC test, I need to send a max 255 bytes payload data from a client to one or many servers. I use two nrf52832 DK boards, BLE sdk 17.0 and BLE mesh 5.0 light_switch example project on SES. both client and server boards are provisioned</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 04 Jun 2021 10:08:32 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/75977/ble-mesh-5-0-couldn-t-send-255-bytes-of-data-from-client-to-server" /><item><title>RE: ble mesh 5.0 couldn't send 255 bytes of data from client to server</title><link>https://devzone.nordicsemi.com/thread/313598?ContentTypeID=1</link><pubDate>Fri, 04 Jun 2021 10:08:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9356d8b6-0410-4da8-a96e-875592f61052</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Helen,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;The&amp;nbsp;&lt;span&gt;trs_seg_packet_in() will call&amp;nbsp;upper_transport_packet_in() when all the segments of the message has been received.&amp;nbsp;&lt;br /&gt;The Bluetooth Mesh protocol is not really designed for sending large amount of data at once. When the payload is above 11bytes it will be split into segments. Transmitting segment would require ACK on the transport layer. And it would cause more traffic to the network (if the ACK message is missing, the whole segments would need to be re-transferred)&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;However you should be able to send above 50 bytes. I would suggest to try debugging by using some log inside&amp;nbsp;trs_seg_packet_in() to check what you receive. Please print the log on the sender side as well.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;2. Please make sure you don&amp;#39;t&amp;nbsp;call&amp;nbsp;generic_onoff_client_set_unack() multiple times before the packet is received on the server side. You can have only one segmented message transmitting at a time.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;3.&amp;nbsp;Could you check if you receive any ACK on the client ? If you set the publication address to the unicast address of the server do you see the same issue ? It&amp;#39;s not recommended to use reliable message to the ALL node address.&amp;nbsp;&lt;/span&gt;&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>