This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Impact on of DLE on scheduling S132 v3

Hi,

I'm using the S132 v3 and wonder about the impact of DLE on scheduling.

In the chapter on Scheduling in the softdevive specification is writen that multiple peripherals connected to a central are spaced tEEO apart. Table 25 states that tEEO is either 1750, 3700 or 6560 us.

Now if I want to use DLE packets the duration of a 251 bytes packets is 2120us.

How does this match with the tEEO? How does the use of DLE impact the scheduling?

Parents
  • Thank you for pointing me to S132v4. Do I undertand it correctly that in S132v3 there were three fixed options for tEEO, resulting in three bandwidth options (#packtes per interval) and only the connection interval could be used to modify throughput. Now in S132v4, tEEO is gone and replaced by tevent, which is controlled at application level. This gives users in the central (still need to figure out how) control over the maximum connection event duration for each peripheral? (It is then of course also up to user to creat a valid configuration.)

Reply
  • Thank you for pointing me to S132v4. Do I undertand it correctly that in S132v3 there were three fixed options for tEEO, resulting in three bandwidth options (#packtes per interval) and only the connection interval could be used to modify throughput. Now in S132v4, tEEO is gone and replaced by tevent, which is controlled at application level. This gives users in the central (still need to figure out how) control over the maximum connection event duration for each peripheral? (It is then of course also up to user to creat a valid configuration.)

Children
No Data
Related