https://devzone.nordicsemi.com/f/nordic-q-a/12329/beacon-advertising-with-20msec-intervalHi, As discussed here a way to advertise each 20msec is changing the mode to BLE_GAP_ADV_TYPE_ADV_IND. This is a connectable mode and assume we do not want a connection happen at all. I don&#39;t know if there are ways to program the advertiser to rejecten-USTelligent Community 13Fri, 04 Mar 2016 13:23:54 GMThttps://devzone.nordicsemi.com/thread/46657?ContentTypeID=1Fri, 04 Mar 2016 13:23:54 GMT137ad170-7792-4731-bb38-c0d22fbe4515:625924ce-234e-495a-9448-a0aaae2fbe90Phil Young<p>I have been considering the same issues since the BT specification states that the minimum gap for ADV_NONCONN_IND should be 100ms, however I also noted that CSR state a latency of 15ms node to node in CSRMesh, yet they also state in their webinar that they are using this packet format, and in their patent application also. I read elsewhere that there was to be a rev4.3 spec for Bluetooth which would include support for meshing in BT_LE, so is it possible that this parameter will be reviewed in the next spec revision ?.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/46656?ContentTypeID=1Fri, 04 Mar 2016 09:05:55 GMT137ad170-7792-4731-bb38-c0d22fbe4515:c1a8c4a3-d4c1-48ae-91cc-41ad3dc2fa3bendnode<p>Hi, I find this possible (beside the fact that you might have problem to tune starting procedure in order to match your desired interval - btw. will you also add timing variance as expected by BLE spec or you are planning to violate this as well?;). However you can also go with standard way: use connectable advertisement @20ms and if anyone connects terminate it straight away at <code>BLE_GAP_EVT_CONNECTED</code> event.</p> <p>Cheers Jan</p><div style="clear:both;"></div>