Bypass slave latency locally?

RE: Bypass slave latency locally?

Thomas — Tue, 02 May 2017 09:33:59 GMT

Accidentally clicked the wrong button... See devzone.nordicsemi.com/.../ for Ulrich anser. Ulrich, thanks for answering my question, I think the information is a good addition to this post.

RE: Bypass slave latency locally?

Ulrich Myhre — Tue, 02 May 2017 09:10:30 GMT

Yes, that was my thought. It's been some time since I used the S110 8.0, so I do not remember if it has some activation time before the local slave latency is effective. You could test it out and see if it something you can use.

RE: Bypass slave latency locally?

Thomas — Tue, 02 May 2017 08:08:25 GMT

Thanks for the quick response, I made a mistake in my comment, I meant a "low response time". So I could use a low connection interval with a low slave latency and a high supervision timeout to get a high throughput and use ble_gap_opt_local_conn_latency_t before requesting a timeslot to create a timeslot longer than the original connection parameters allowed?

RE: Bypass slave latency locally?

Ulrich Myhre — Tue, 02 May 2017 08:00:54 GMT

That is sort of the opposite problem. What you can do is to use a slave latency of e.g. 1 combined with a very long supervision timeout, then adjust the local connection latency to a longer one. See ble_gap_opt_local_conn_latency_t in the GAP module. It is set through the options API.

RE: Bypass slave latency locally?

Thomas — Tue, 02 May 2017 05:54:41 GMT

Hi, is this still not possible (SoftDevice s110)? Our use-case is that we only want to utilize the slave latency during our timeslot, outside of that we need a low response time and throughput both ways.

RE: Bypass slave latency locally?

TBone — Wed, 13 May 2015 11:08:35 GMT

Thanks for the reply. The situation is a peripheral on coin battery that must last months, but must report event data vey quickly. So we have a connection interval of 10 ms, and a slave latency of 100. So the peripheral only needs to fire up its radio every second. But when bonding, this process can take many seconds since the peripheral only gets each discovery message every second. If our bonding process can be triggered by a button press, then I'll have the peripheral request a 0 slave latency during the pre-bonded connection, and then after bonding it can request a big slave latency.

RE: Bypass slave latency locally?

Ulrich Myhre — Wed, 13 May 2015 08:15:36 GMT

Hi!

No, this is not possible, short of sending something the connection intervals you want to be awake.

What is the use-case for this though? If the central wants to send burst data, but seldom, it could simply change the connection parameters back and forth when this is needed (without any negotiation). Changing the connection parameters will take at least 6 connection intervals, so you need to do this slightly in advance.