Advertiser (connectable and non-connectable) timing

Advertiser is started as early as possible, after a random delay in the range of 3 - 13 ms, asynchronously to any other role timing-events. If no roles are running, advertiser timing-evens are able to start and run without any collision.

Figure 1. Advertiser

When other role timing-events are running in addition, the advertiser role timing-event may collide with those. Figure 2 shows a scenario of Advertiser colliding with Peripheral (P).

Figure 2. Advertiser collide

Directed advertiser is different compared to other advertiser types because it is not periodic. The scheduling of the single timing-event required by directed advertiser is done in the same way as other advertiser type timing-events. Directed advertiser timing-event is also started as early as possible, and its priority (refer to Table 1) is raised if it is blocked by other role timing-events multiple times.


Documentation feedback | Developer Zone | Subscribe | Updated 2017-03-10