<?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>NRF52840 reducing minimum connection event length</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/69063/nrf52840-reducing-minimum-connection-event-length</link><description>Hi all, 
 In my current project I have 7 sensors, each hooked up to an own nrf52. I am polling between 8 and 28 byte(depending on operation mode) of data in 10ms intervals. Currently, I have 6 of them set up as peripherals and one of them as their Master</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 04 Dec 2020 15:33:07 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/69063/nrf52840-reducing-minimum-connection-event-length" /><item><title>RE: NRF52840 reducing minimum connection event length</title><link>https://devzone.nordicsemi.com/thread/283363?ContentTypeID=1</link><pubDate>Fri, 04 Dec 2020 15:33:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:63a9f980-1695-4590-814d-f38e66f5a582</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
[quote user=""]Is it possible to reduce the connection event length below this 2.5ms? At least for the case I only want to transmit 8 byte?[/quote]
&lt;p&gt;Not possible with S140, but with SoftDevice variant S122(central-only &lt;span&gt;SoftDevice&amp;nbsp;&lt;/span&gt;), you have the possibility to use 1.25ms event length for 2Mbps PHY.&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;/**@defgroup BLE_GAP_EVENT_LENGTH GAP event length defines.
 *
 * If the link is configured with an event length above the minimum,
 * the SoftDevice will guarantee the link will not be allocated more time than specified.
 * If the configured event length is too short for the current PHY, more time will be allocated to be able to transmit at least one packet pair.
 * Notice that this may lead to scheduling conflicts. See the SoftDevice Specification for more details.
 * @{ */
#define BLE_GAP_EVENT_LENGTH_MIN            (2)  /**&amp;lt; Minimum event length, in 1.25 ms units. */
#define BLE_GAP_EVENT_LENGTH_1MBPS_PHY_MIN  (2)  /**&amp;lt; Minimum event length on 1 Mbps PHY, in 1.25 ms units. */
#define BLE_GAP_EVENT_LENGTH_2MBPS_PHY_MIN  (1)  /**&amp;lt; Minimum event length on 2 Mbps PHY, in 1.25 ms units. */
#define BLE_GAP_EVENT_LENGTH_DEFAULT        (3)  /**&amp;lt; Default event length, in 1.25 ms units. */
/**@} */&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;But since S122 is central only, you wont be able to transmit this data to another central device, and S122 supports&amp;nbsp;&lt;span&gt;nRF52811, nRF52820 and nRF52833. i.e. not nRF52840. Depending on what timeline you have and what resources you have available for this project, you could alternatively skip the&amp;nbsp;BLED112, and create e.g. a nRF52833 dongle instead.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Yes, advertising the data instead is an alternative, but note that minimum advertising interval is 20 ms (Set by the Bleutooth spec), and that with advertising you are not guaranteed&amp;nbsp;that the scanner will be able to scan all the packets that are sent.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF52840 reducing minimum connection event length</title><link>https://devzone.nordicsemi.com/thread/283167?ContentTypeID=1</link><pubDate>Thu, 03 Dec 2020 16:04:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:56076148-b88d-4a97-8b41-fa355562ec20</guid><dc:creator>Mammutbaum</dc:creator><description>&lt;p&gt;There was a mistake in the sketch, can someone delete this?&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/69061/reducing-minimum-connection-event-length"&gt;https://devzone.nordicsemi.com/f/nordic-q-a/69061/reducing-minimum-connection-event-length&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF52840 reducing minimum connection event length</title><link>https://devzone.nordicsemi.com/thread/283153?ContentTypeID=1</link><pubDate>Thu, 03 Dec 2020 14:58:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:77d886a6-d529-4ed6-9c88-9f2f8d25a63d</guid><dc:creator>awneil</dc:creator><description>&lt;p&gt;&lt;strong&gt;Duplicate:&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/69061/reducing-minimum-connection-event-length"&gt;devzone.nordicsemi.com/.../reducing-minimum-connection-event-length&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>