https://devzone.nordicsemi.com/f/nordic-q-a/1801/mcp-dongle-packet-throughput-limitationHi, It has been mentioned in several threads that the MCP/dongle (on laptop) cannot support transmission of more than 1 packet per connection interval. Could you help clarifying whether this limitation is due to MCP implementation or is it due to theen-USTelligent Community 13Thu, 06 Mar 2014 10:10:43 GMThttps://devzone.nordicsemi.com/thread/7844?ContentTypeID=1Thu, 06 Mar 2014 10:10:43 GMT137ad170-7792-4731-bb38-c0d22fbe4515:1ab45bb8-4b75-4bb6-9f56-8df9f3061a2cOle Morten<p>This limitation is in the software running on the dongle.</p> <ol> <li> <p>The most common way to handle changing the connection interval is to send an update request from the Peripheral side. This can be done by using the ble_conn_params module, and setting up the MIN_CONN_INTERVAL and MAX_CONN_INTERVAL as wanted. The module will then send a parameter update request to the Central, if the currently used parameters are outside the range.</p> </li> <li> <p>If a characteristic has the notify or indicate property, you should see a button with two arrows above a line next to it, as the button next to the Blood Pressure in <a href="https://lh4.ggpht.com/Mytm9z1sZPEmJ2gIrmDw-oc8sj1y97SZcD4f9_YqU69ALjGwWf0o72o0DwwkNNbQRQ=h900-rw">this screenshot</a>. Pressing this should enable notifications.</p> </li> </ol> <p>If you don&#39;t see any notifications, are you sure that the peer device is actually sending them (i.e. calling sd_ble_gatts_hvx())?</p><div style="clear:both;"></div>