RE: Scheduling with multi role coexist

ovrebekk — Mon, 01 Apr 2019 11:06:49 GMT

My pleasure 🙂

RE: Scheduling with multi role coexist

shijh — Mon, 01 Apr 2019 03:21:43 GMT

Thanks for your explanation ovrebekk.

RE: Scheduling with multi role coexist

ovrebekk — Fri, 29 Mar 2019 09:22:09 GMT

Sorry for the slow reply, I have been out on travel this week.

It is true that peripheral connections will be asynchronous to the central connections, and will slowly drift over time as the timers in the different central devices will not be 100% accurate.

The point of the comment is that you get less conflicts if you make sure that your connection intervals for all links is larger than the sum of time needed to service all the roles (central links, peripheral links, plus scanning and advertiser activities).

As an example, say you have 4 connections with event length 2.5ms and you also have one scanner with scan window 10ms, you want to ensure all your connection intervals are larger than 20ms.

Central links should definitely have a common factor, while for peripheral links this is less important since they will not be synchronized.

I discussed this statement with one of the software developers, and he agreed that it was a bit confusing. I can request internally if we can improve this in a future documentation update.

Regarding question 2, new central connections will not take heed of existing peripheral connections, since they are expected to drift anyway.

Best regards
Torbjørn