https://devzone.nordicsemi.com/f/nordic-q-a/17792/softdevice-returned-invalid-parameter-error-for-these-parametersDuring a sd_ble_conn_param_update() call, S332 softdevice returned invalid parameter error for: min_conn_interval = 10 max_conn_interval = 800 slave_latency = 2 conn_sup_timeout = 400 According to this link, these values should be wellen-USTelligent Community 13Fri, 18 Nov 2016 10:08:19 GMThttps://devzone.nordicsemi.com/thread/68560?ContentTypeID=1Fri, 18 Nov 2016 10:08:19 GMT137ad170-7792-4731-bb38-c0d22fbe4515:c9ae0124-5ac2-40e9-a4e6-30fac764fc48Petter Myhre<p>What do you mean? That sd_ble_gap_ppcp_set() does not return an error when you use these parameters?</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/68559?ContentTypeID=1Thu, 17 Nov 2016 15:43:39 GMT137ad170-7792-4731-bb38-c0d22fbe4515:59e777db-160d-4ed3-acab-83b544ff5de3xuefei<p>Thanks for the reply. The interesting thing is these parameters are peripheral preferred connection parameters, not sure why the sensor would return this set if it&#39;s invalid</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/68558?ContentTypeID=1Thu, 17 Nov 2016 07:01:33 GMT137ad170-7792-4731-bb38-c0d22fbe4515:20ea19a7-bc75-4e83-a87a-0a6b2a4379d7Petter Myhre<p>Per spec the following equation must be valid:</p> <pre><code>connSupervisionTimeout &gt; (connInterval * 2 * (connSlaveLatency + 1)) </code></pre> <p>See <a href="https://devzone.nordicsemi.com/question/46510/how-can-the-peripheralslave-sleep-as-much-as-possible/">this</a> for more information.</p><div style="clear:both;"></div>