<?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>How to use the static length field when receiving</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/245/how-to-use-the-static-length-field-when-receiving</link><description>Hi! 
 My idea of sending a packet would be: 
 -regulary send a packet with fixed length (stated in static length field) to a base: i.e send the temperature =&amp;gt;4byte
-if something went wrong while transmitt (and this becomes recognized) in the next attempt</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 13 Aug 2013 06:44:34 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/245/how-to-use-the-static-length-field-when-receiving" /><item><title>RE: How to use the static length field when receiving</title><link>https://devzone.nordicsemi.com/thread/1324?ContentTypeID=1</link><pubDate>Tue, 13 Aug 2013 06:44:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:21a1891f-ebb2-43e4-b259-8c52a53f50f7</guid><dc:creator>Ole Morten</dc:creator><description>&lt;p&gt;Gazell have 8 pipes, each of which corresponds to one RF address, but there isn&amp;#39;t any problems with having multiple devices sending data on one pipe. To differentiate them, you can for example include an ID byte in the payload. If you do this, it should be possible to get working with an indefinite number of clients, as long as there is radio time enough for all of them.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to use the static length field when receiving</title><link>https://devzone.nordicsemi.com/thread/1323?ContentTypeID=1</link><pubDate>Mon, 12 Aug 2013 16:49:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5058ab2b-1ff2-448a-8838-6178442f7796</guid><dc:creator>Dominik Hochwimmer</dc:creator><description>&lt;p&gt;Thanks a lot for the answer!&lt;/p&gt;
&lt;p&gt;According Gazell, this will serve 8 clients max?
If so, is there a possible/quick  workaround to get it running with i.e. 100+ clients.
(Assuming the transmited data from each client is small enough to not getting troubles with the datarate.)&lt;/p&gt;
&lt;p&gt;RGDS&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to use the static length field when receiving</title><link>https://devzone.nordicsemi.com/thread/1322?ContentTypeID=1</link><pubDate>Mon, 12 Aug 2013 12:26:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ad82fc11-07d0-4d59-b775-33a3c8eb2b7e</guid><dc:creator>Ole Morten</dc:creator><description>&lt;p&gt;The static length field can be used if all packets you want to transmit are the same length. If so, you can omit sending a length field on air, saving a few bits there. If you want to dynamically change the payload length, as you say, you can not use a static length, and instead you must include the length of each packet in the on-air representation (you could in theory omit the length field here as well, and just always send the max length, but that would be very inefficient).&lt;/p&gt;
&lt;p&gt;However, in general we normally recommend users to instead build on the Gazell library for proprietary use cases, as that is normally a more flexible and worked-through solution. By doing that, you avoid having to manipulate the radio peripheral directly.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to use the static length field when receiving</title><link>https://devzone.nordicsemi.com/thread/1326?ContentTypeID=1</link><pubDate>Thu, 08 Aug 2013 18:58:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:af6eed75-90aa-4ad5-8bf8-3103b9eaf114</guid><dc:creator>Dominik Hochwimmer</dc:creator><description>&lt;p&gt;Hi Carles,&lt;/p&gt;
&lt;p&gt;it was a little late when posting the question I am afraid ;)
The question is about &lt;strong&gt;proprietary protocolls&lt;/strong&gt; and how to best(most power efficient)  define the payload length for a scenario with &amp;quot;random&amp;quot; retransmits...&lt;/p&gt;
&lt;p&gt;When I was talking about the &amp;quot;static length field&amp;quot; this means the &amp;quot;statlen&amp;quot; bits in the radios packet configuration  register.&lt;/p&gt;
&lt;p&gt;&amp;quot;If something went wrong&amp;quot; in order to the receiver couldnt receive data because the signal strength was too low, the distance to high, the channel was used by any other transceiver,... it is needed retransmit the &amp;quot;lost&amp;quot; data in addition to the new sensor data fetched.&lt;/p&gt;
&lt;p&gt;hope this now helps you to help me :)
RGDS Dominik&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to use the static length field when receiving</title><link>https://devzone.nordicsemi.com/thread/1325?ContentTypeID=1</link><pubDate>Thu, 08 Aug 2013 10:38:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3dd1e92b-1910-46f8-8146-b82d86130c0d</guid><dc:creator>Carles</dc:creator><description>&lt;p&gt;Hi there,&lt;/p&gt;
&lt;p&gt;I am afraid you&amp;#39;ll need to clarify a bit for me to be able to help you.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;-regulary send a packet with fixed length (stated in static length field)&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;What&amp;#39;s the &amp;quot;static length field&amp;quot; ? Do you mean the characteristic value length? Are you talking about fixed vs. variable length?&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;-if something went wrong while transmitt&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Nothing can go wrong while transmitting in BLE. The radio and the protocol &lt;strong&gt;guarantee&lt;/strong&gt; that the packet will be delivered, there is no need for application level retransmission schemes.&lt;/p&gt;
&lt;p&gt;Carles&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>