S132, Scan interval/window, ADV interval.

RE: S132, Scan interval/window, ADV interval.

Anders Strand — Fri, 24 Jun 2016 12:56:19 GMT

This happens internally, and is not documented. Of you want to advertise with a certain interval, you can not scan 100% of the time.

RE: S132, Scan interval/window, ADV interval.

HakJae — Fri, 24 Jun 2016 12:50:06 GMT

Then, how many times need to raise priority?

RE: S132, Scan interval/window, ADV interval.

HakJae — Fri, 24 Jun 2016 12:13:10 GMT

Thank you. It is a help for me.

RE: S132, Scan interval/window, ADV interval.

Anders Strand — Fri, 24 Jun 2016 09:20:46 GMT

The softdevice will schedule this ahead of time. If you try to scan 100% of the time, the advertisement will be blocked a certain amount of times until i has its priority raised enough. Then the advertisement will occur. So you will have some advertisement, but not as often as stated in the advertising interval.

RE: S132, Scan interval/window, ADV interval.

HakJae — Fri, 24 Jun 2016 08:27:54 GMT

Thank you for your anwer. Then, while Scaning evt occur and handling, ADV evt occur. ADV evt impliment after Scaning evt ? or blocked ?

RE: S132, Scan interval/window, ADV interval.

shibshab — Fri, 24 Jun 2016 06:32:12 GMT

The S132 is only capable of running one role (in this case, scanner or advertiser) at a time, so scheduling must be performed to select which role should be active at a given time.

See chapter 16 "Scheduling" in the S132 SoftDevice Specification. Here it states that the Scanner and Advertiser will be in the same priority (table 30), in which case the following statement will apply:

If both timing-activity A and timing-activity B have same priority, the timing-activity which was requested first will get the timing-event.

In other words, whichever sent the request first will get the timing-event.

However, as neither scanning nor advertising are timing-sensitive tasks, this should not impose any problems.

In your case even though the scanner is trying to take all the radio time (by having Scan Window = Scan Interval) the advertiser role should also get some radio time, although no guarantees are given. If you see an issue with not enough advertisements being sent, you could decrease the scan window to reduce the amount of scheduling conflicts.

Edit: In the aforementioned table 30, it is stated that an advertiser or scanner which has been blocked several times will have its priority raised to Third Priority. This is what ensures that both scanner and advertiser roles gets radio time.