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
  • That shouldn't be a problem. If RAM isn't an issue I would just configure the SoftDevice to support 2 connections as a central with high bandwidth. If RAM is an issue, I would still start off with high bandwidth to see if you achieve the throughput you need, if you do, you can try to lower the bandwidth for the connections (decreasing RAM) and see if you still get the throughput that you need. Using 100ms for both connections should be fine.

    I also want to mention that we improved the method/API of handling this quite a bit with S132 v4, so you might want to consider migrating to that.

Reply
  • That shouldn't be a problem. If RAM isn't an issue I would just configure the SoftDevice to support 2 connections as a central with high bandwidth. If RAM is an issue, I would still start off with high bandwidth to see if you achieve the throughput you need, if you do, you can try to lower the bandwidth for the connections (decreasing RAM) and see if you still get the throughput that you need. Using 100ms for both connections should be fine.

    I also want to mention that we improved the method/API of handling this quite a bit with S132 v4, so you might want to consider migrating to that.

Children
No Data
Related