<?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>Cumulative Crank Revs Explained</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/9479/cumulative-crank-revs-explained</link><description>Hi, 
 I am wondering about the Cumulative crank revs for service 0x1816 &amp;amp; 0x1818 
 Cycling Cadence and Speed, Cycling Power Services 
 I dont understand why the crank revs are to be sent out as cumulative values in a 16 bit field.. 
 Does this mean</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 29 Sep 2015 06:11:47 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/9479/cumulative-crank-revs-explained" /><item><title>RE: Cumulative Crank Revs Explained</title><link>https://devzone.nordicsemi.com/thread/35005?ContentTypeID=1</link><pubDate>Tue, 29 Sep 2015 06:11:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9831750d-8a7e-4002-b18f-b9ccb0ce2c73</guid><dc:creator>RK</dc:creator><description>&lt;p&gt;The crank revolutions are sent out as cumulative vales in a 16 bit field because that&amp;#39;s what the bluetooth spec as adopted by the Bluetooth SIG for the service mandates.&lt;/p&gt;
&lt;p&gt;if you read the full spec, which can be downloaded &lt;a href="https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=261449"&gt;here&lt;/a&gt;, it notes this value can roll over and documents that the collector shall take that into consideration, it also specifies an optional control point for setting it to a known value.&lt;/p&gt;
&lt;p&gt;The spec doesn&amp;#39;t have the working group&amp;#39;s deliberations, so you can only guess why they did it that way, I would guess it was a tradeoff between utility and packet size.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>