<?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>Why the mouse report rate down after bonding??</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/2237/why-the-mouse-report-rate-down-after-bonding</link><description>Hi all, 
 I used the ble_app_hids_mouse example in SDK 4.4.1 and found:
1.when the mouse does the first bonding with the master, the report rate could reach 125Hz(I set one timer with 8ms interrupt interval to toggle the mouse_key_send());
2.re-start</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 24 Apr 2014 09:30:25 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/2237/why-the-mouse-report-rate-down-after-bonding" /><item><title>RE: Why the mouse report rate down after bonding??</title><link>https://devzone.nordicsemi.com/thread/9422?ContentTypeID=1</link><pubDate>Thu, 24 Apr 2014 09:30:25 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8b610351-ecaf-4ff3-9975-70f5dcbba484</guid><dc:creator>jimlin</dc:creator><description>&lt;p&gt;Clear!
It needs the master to support so that to some master not support so fast interval, the slave could not use at all. I think this is the compatibility problem on bluetooth.&lt;/p&gt;
&lt;p&gt;Thanks again.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Why the mouse report rate down after bonding??</title><link>https://devzone.nordicsemi.com/thread/9421?ContentTypeID=1</link><pubDate>Thu, 24 Apr 2014 09:08:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:94c71120-9fee-49c4-b4a3-87d1f3d6f21d</guid><dc:creator>H&amp;#229;kon Alseth</dc:creator><description>&lt;p&gt;You could do that, however, if the central (master) does not give you the desired interval, the mouse will disconnect the link immediately.
To be able to work with all central devices, I would recommend having a larger difference between min and max connection interval.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Why the mouse report rate down after bonding??</title><link>https://devzone.nordicsemi.com/thread/9420?ContentTypeID=1</link><pubDate>Thu, 24 Apr 2014 08:07:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6bc474e5-43d4-4e02-91e7-077a2fca0579</guid><dc:creator>jimlin</dc:creator><description>&lt;p&gt;So, if I want to keep it at 125Hz which is 8ms, and the minimum connection interval is 7.5ms, that means it need to set the MIN_CONN_INTERVAL as 7.5ms while MAX_CONN_INTERVAL as 8ms. It will bring up the working current.
Could I do it as this?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Why the mouse report rate down after bonding??</title><link>https://devzone.nordicsemi.com/thread/9419?ContentTypeID=1</link><pubDate>Thu, 24 Apr 2014 07:26:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d6d7c447-b273-48dd-a48d-ac39ef507c48</guid><dc:creator>H&amp;#229;kon Alseth</dc:creator><description>&lt;p&gt;Yes, that will guarantee that the mouse report rate follows the connection interval that you have.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Why the mouse report rate down after bonding??</title><link>https://devzone.nordicsemi.com/thread/9418?ContentTypeID=1</link><pubDate>Thu, 24 Apr 2014 03:45:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e3c424ef-623b-42f7-878d-1f4196bd0fff</guid><dc:creator>jimlin</dc:creator><description>&lt;p&gt;Hi Hakon,&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;Do you mean it should send mouse sensor data when radio_active is false to guarantee the report rate?
&lt;/code&gt;&lt;/pre&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Why the mouse report rate down after bonding??</title><link>https://devzone.nordicsemi.com/thread/9417?ContentTypeID=1</link><pubDate>Wed, 23 Apr 2014 12:59:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bd27f887-fb63-4977-ad53-7536a5c55b4c</guid><dc:creator>H&amp;#229;kon Alseth</dc:creator><description>&lt;p&gt;Hi.&lt;/p&gt;
&lt;p&gt;Initially, the slave and master will connect with a low connection interval in order to make the bonding/discovery procedure go fast. After a given period, you will negotiate updated connection parameters (usually set by &amp;quot;FIRST_CONN_PARAMS_UPDATE_DELAY&amp;quot; define on the slave side)&lt;/p&gt;
&lt;p&gt;The connection interval given from the master must then be between your minimum and maximum connection interval (defines MIN_CONN_INTERVAL and MAX_CONN_INTERVAL). If the master does not give you a interval between min and max, the slave will disconnect the link.&lt;/p&gt;
&lt;p&gt;In order to scale the mouse properly according to your connection interval, you should then use &amp;quot;radio notification&amp;quot; library to send mouse-sensor-data.&lt;/p&gt;
&lt;p&gt;Best regards
Håkon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Why the mouse report rate down after bonding??</title><link>https://devzone.nordicsemi.com/thread/9416?ContentTypeID=1</link><pubDate>Wed, 16 Apr 2014 03:26:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:53069622-372e-4fe2-b003-5423cf94c895</guid><dc:creator>jimlin</dc:creator><description>&lt;p&gt;Whether something wrong happen when the SoftDevice store the bonding info so that the info is incorrect when reload on power on???&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>