<div dir="ltr">Chip,<div><br></div><div>Thanks for the great information. That does seem like a lot of overhead. It sounds like collecting the data and sending up a group of data points at one time might be required to make the most of a modest data plan. Any idea how much data it would take to send the 51 data points at one time? Guessing from the numbers it might be only 6-7k.</div><div><br></div><div>Shane</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Nov 23, 2014 at 11:47 PM, Charles McClelland <span dir="ltr"><<a href="mailto:chip@mcclellands.org" target="_blank">chip@mcclellands.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div>Shane, </div><div><br></div><div>I fired up my IOT device and did a test to see how much data is used on the GPRS network when a data packet is sent. </div><div><br></div><div>I sent data 51 times and used 215kb of data traffic according to my T-Mobile portal. Here is the payload from one of those transmissions:</div><div><span style="white-space:pre-wrap"> </span>- Traffic count - “10"</div><div><span style="white-space:pre-wrap"> </span>- Location - "<span style="font-family:'Open Sans',sans-serif;line-height:20px;text-align:center">lat:35.89, </span><span style="font-family:'Open Sans',sans-serif;line-height:20px;text-align:center">lng:-78.81"</span></div><div><span style="font-family:'Open Sans',sans-serif;line-height:20px;text-align:center"><span style="white-space:pre-wrap"> </span>- Battery - “4083"</span></div><div><span style="font-family:'Open Sans',sans-serif;line-height:20px;text-align:center"><span style="white-space:pre-wrap"> </span>- Retries - “0”</span></div><div><span style="font-family:'Open Sans',sans-serif;line-height:20px;text-align:center"><br></span></div><div><span style="font-family:'Open Sans',sans-serif;line-height:20px;text-align:center">Seems like a lot of overhead - ~</span><span style="font-family:'Open Sans',sans-serif;line-height:20px;text-align:center">4kb to send about 28 bytes. Here is what I can see in looking at the code:</span></div><div><span style="font-family:'Open Sans',sans-serif;line-height:20px;text-align:center"><span style="white-space:pre-wrap"> </span>- There is a 64 bit API key</span></div><div><span style="font-family:'Open Sans',sans-serif;line-height:20px;text-align:center"><span style="white-space:pre-wrap"> </span>- Then a 16 bit identifier for each data stream</span></div><div><span style="font-family:'Open Sans',sans-serif;line-height:20px;text-align:center"><span style="white-space:pre-wrap"> </span>- There is also limited back and forth exchanging commands and result codes</span></div><div><span style="font-family:'Open Sans',sans-serif;line-height:20px;text-align:center"><span style="white-space:pre-wrap"> </span>- Looking at T-Mobile’s numbers, it may be that they count their data in chunks and round up. Kind of like billing a 30 second call as 1 minute.</span></div><div><span style="font-family:'Open Sans',sans-serif;line-height:20px;text-align:center"><br></span></div><div><span style="font-family:'Open Sans',sans-serif;line-height:20px;text-align:center">I hope this helps with your planning.</span></div><div><span style="font-family:'Open Sans',sans-serif;line-height:20px;text-align:center"><br></span></div><div><span style="font-family:'Open Sans',sans-serif;line-height:20px;text-align:center">Chip</span></div><div style="text-align:center"><br></div><div><br></div><br><div><blockquote type="cite"><div>On Nov 21, 2014, at 8:26 PM, <a href="mailto:triembed-request@triembed.org" target="_blank">triembed-request@triembed.org</a> wrote:</div><br><div><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">Re: Did anyone discuss M2M data plans?</span></div></blockquote></div><br></div><br>_______________________________________________<br>
Triangle, NC Embedded Computing mailing list<br>
<a href="mailto:TriEmbed@triembed.org">TriEmbed@triembed.org</a><br>
<a href="http://mail.triembed.org/mailman/listinfo/triembed_triembed.org" target="_blank">http://mail.triembed.org/mailman/listinfo/triembed_triembed.org</a><br>
TriEmbed web site: <a href="http://TriEmbed.org" target="_blank">http://TriEmbed.org</a><br>
<br></blockquote></div><br></div>